Page MenuHomePhabricator

Make the master branch a synonym of current for the purpose of running Jenkins jobs
Closed, ResolvedPublicBUG


The reason we are using the "current" branch where git's default is master is that the master branch of the original codebase was messed up beyond any repair.
It was never intended to be permanent, and the plan is to move away from it to using master like everyone else as we get rid of the old packages.

However, we need a solution for correctly pushing packages built from the master branch to the repository of the "current" release.


Difficulty level
Unknown (require assessment)
Why the issue appeared?
Will be filled on close
dmbaturin closed this task as Resolved.May 3 2018, 12:25 PM
dmbaturin claimed this task.

Just tested it on hvinfo and it seems to work as expected. The change is in the jenkins script,

RELEASE=`echo $GIT_BRANCH | sed 's/origin\//* /g' |sed -n 's/^\* \(.*\)$/\1/p'`
if [ "$RELEASE" == "master" ]; then
c-po added a subscriber: c-po.May 3 2018, 2:05 PM

Why not "repairing" the master branch by first deleting its content in one commit and the merging current into master?

dmbaturin mentioned this in Unknown Object (Ponder Answer).May 8 2018, 10:57 AM