Alright, this is live and looking good! Please do not hesitate to ping me on IRC if you have any questions or problems.
Thanks! On Tue, May 31, 2016 at 2:06 PM, Robert Park <[email protected]> wrote: > This is to inform you that the CI Train will be taken offline at UTC > 01:00 (that is, 4 hours from now) in order to roll out new features. I > expect the outage to last 1 to 2 hours. > > This is a BIG rollout with many bug fixes and features, here are some > of the highlights: > > * Source package build parallelization, allowing source packages to be > prepared & uploaded to the PPA in parallel, for which you should see > dramatic speedups for silos containing 2 or more source packages. > Particularly large silos (*cough* Timo, *cough*) become I/O bound and > will only see a small speedup. Silos containing a handful of "small" > packages should see the largest speedup. In my testing I've seen silos > branch, merge, build source, upload, and diff in just 3 minutes. > > * First step of jenkins replacement. The build job now no longer runs > in Jenkins but runs directly inside Bileto. This provides a > significantly nicer interface (no more of that pesky "I clicked Build > but nothing happened because the Build button redirected through SSO > and dropped me back at the build form" bug, at least for building. > other jobs will come in the next iterations). > > * No git support yet, but the aforementioned parallelization also > brings with it an encapsulation layer around bzr that should make git > support much easier to add in the coming months. > > * Totally new debian/changelog generation, for those of you who have > complained about your debian/changelogs recently, it is now guaranteed > that the debian/changelog will match exactly the commit messages of > the input MPs (previously there were some weird corner cases causing > strange changelogs that have now been eliminated). > > * Build logs will now explicitely tell you what order your MPs will be > merged in (as this can sometimes differ from the order you specify in > the ticket), as well as more specifically tell you exactly the > destination that each package is targetted at, as some people have > complained that this was unclear in the past. > > * MP field on the ticket now supports comments, so eg, if you want to > disable an MP temporarily, you can prefix it with '#'. You can also > write arbitrary comments this way, eg you can prefix a block of MPs > with a header like "# foo feature" to make it more clear what you're > doing with your MP list, which in some cases can get quite large. > > * probably lots of other fun things you'll discover as you go. > > > > As usual, a rollout this large carries with it some risk of > regressions, so please do inform me at the first sign of trouble and > I'll do my best to make sure everything goes smoothly for everybody. > I've timed this rollout for early in the OTA cycle so nobody should be > in that last-second release rush at least. > > Thanks! > > -- > robru -- robru -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
