Silo branches should be public

[Michał Sawicz]

The silo branches need to be published somewhere to ease resolving issues. When you have multiple branches, and the order in which they merge is determined by the silo, it's really painful to be able to reproduce the same branch.

[Michał Sawicz (saviq)]

I just saw ps-jenkins pushes to:

https://code.launchpad.net/~ps-jenkins

But only on publication, this would be a nice place to push on build, too.

[Robert Bruce Park (robru)]

Yes, I do intend to make those branches get pushed at build time, unfortunately the build job is currently a big hairy beast, but refactoring it is on my to-do list and once it's refactored it will be easy to implement something like this.

The branches now get pushed to https://code.launchpad.net/~ci-train-bot at publish time.

[Robert Bruce Park (robru)]

My build.py rewrite has just landed, which means it is now easy to implement something like this. I might have some time soon to shift the existing branch-pushing code from the publish job to the build job.

[Gerry Boland (gerboland)]

I'd find this very useful!

[Robert Bruce Park (robru)]

Ok, I just landed the fix for this in trunk, should land in production within the hour. Next time you build a silo in the train you should see your branch appear here:

https://code.launchpad.net/~ci-train-bot

[Michał Sawicz (saviq)]

Awesome, thanks!