No git branch for MOODLE_39_STABLE

No git branch for MOODLE_39_STABLE

by Ray Havlin -
Number of replies: 4

I have been successfully upgrading with each minor release and each major release since 3.5.0 with no problems.  I do know the difference between a minor and major upgrade.

When trying to move from 3.8.3 to the current release 3.9.1

     git branch -a

doesn't show a branch for

     MOODLE_39_STABLE   (it only shows MOODLE_38_STABLE as the current branch)

If I use the git command anyway with

     git branch --track MOODLE_39_STABLE origin/MOODLE_39_STABLE

I get the error message

     error: the requested upstream branch 'origin/MOODLE_39_STABLE' does not exist


Has something changed?  I've doubled checked all the current release docs and nothing new is reflected from this standard process.

Thanks

Ray


Average of ratings: -
In reply to Ray Havlin

Re: No git branch for MOODLE_39_STABLE

by Ken Task -
Picture of Particularly helpful Moodlers

git pull first

Then check git branch -a

You should see the 39 branch but the * is on 38.

You could then do the

git branch --track MOODLE_39_STABLE origin/MOODLE_39_STABLE

and

git checkout MOODLE_39_STABLE

Probably a good practice to always update to the highest of the branch you are in first, then upgrade to next.

My 2 'git' cents?

'SoS', Ken

Average of ratings: Useful (1)
In reply to Ken Task

Re: No git branch for MOODLE_39_STABLE

by Ray Havlin -
Ken,

Once again you have filled the gap in my knowledge - THANK YOU.

Updating to 3.8.4 did the trick. After that highest branch update, the branch was available to MOODLE_39_STABLE. Now current at 3.9.1!

Thanks again
Ray
Average of ratings: -
In reply to Ray Havlin

Re: No git branch for MOODLE_39_STABLE

by Ken Task -
Picture of Particularly helpful Moodlers

Welcome!  I take it you have done the safe thing ...  a minimal site backup (code/db/filedir of moodledata) after the update to 3.8.highest, before pulling the trigger on upgrading to 3.9.1.

Did you do the upgrade 100% command line?

Any issues?

'SoS', Ken

Average of ratings: -
In reply to Ken Task

Re: No git branch for MOODLE_39_STABLE

by Ray Havlin -
Yep I've been building an extensive best practices doc for Moodle beginning with 3.5.

So the steps I have are:

php admin/cli/maintenance.php --enable

php admin/cli/kill_all_sessions.php

Use phpMyAdmin to backup SQL database

Backup MoodleData and Moodle directories

su - username (prevents file permission errors with git usage)

For minor release of existing branch:
git pull

For major release to next branch: (make sure you've updated the branch to the highest release first)
git pull
git branch -a
git branch --track MOODLE_39_STABLE origin/MOODLE_39_STABLE
git checkout MOODLE_39_STABLE

php admin/cli/upgrade.php --non-interactive

php admin/cli/maintenance.php --disable


So far this command line process has been flawless, until I didn't know to always update to the current branch to the highest release first. Thanks to you, I now know this gap in my knowledge.

Ray
Average of ratings: Useful (1)