I don't think there's anything else to do. If I could figure out what it means (in terms of archivable artifacts) to build more than one branch, I'd suggest we have P5 build both dev and master, but I would assume that would cause one to overwrite the other. How's your Jinks for disk space? Mine is a bit low, so I'm going to get it expanded when I go back. I'll have space for an extra P5 Master job then. Could yours do the same? It would build very rarely, so as long as theirs disk space for the artifacts it wouldn't be much of a drag on the system. Cheers, Martin On 2015-10-29 05:55 PM, James Cummings wrote:
Hi Martin.
To do this I just changed the configuration for the following jobs:
TEIP5 TEIP5-Documentation TEIP5-Test Stylesheets
to be */dev instead of */master
Is there anything else I need to do?
-James
On 29/10/15 12:23, Martin Holmes wrote:
I've just changed my Jinks to build dev branches. However, this now means we have no Jenkins build that we can use as a distribution source when we do a release. We will need to add another job, I think.
Cheers, Martin
On 2015-10-29 10:33 AM, Hugh Cayless wrote:
To switch to work on the dev branch, you should be able to just:
git fetch git checkout dev
Future pushes should be to dev, so
git push origin dev
You need to do this in both the TEI and Stylesheets repos.
Thanks all, Hugh