ubuntu-phone team mailing list archive

[Łukasz 'sil2100' Zemczak <lukasz.zemczak@xxxxxxxxxxxxx>]

Hello everyone!

There's one small change in the queue right now in the CI Train. We will
most probably change the DO_NOT_APPEND_RTM_TO_VERSION flag to
APPEND_RTM_TO_VERSION, which basically implies that from that time the
merge gets landed, the default behavior for source builds for ubuntu-rtm
in our silos will be *not* to append the ~rtm prefix to the version number.

So, no longer checking DO_NOT_APPEND_RTM_TO_VERSION will be required for
those that land in ubuntu-rtm first and do not want the ~rtm bits in the
version. Yay.

But you can still specify the APPEND_RTM_TO_VERSION flag if this
behavior is wanted.

https://code.launchpad.net/~sil2100/cupstream2distro/do_not_append_rtm_by_default/+merge/235846

Cheers!


W dniu 23.09.2014 o 18:36, Łukasz 'sil2100' Zemczak pisze:
> Hi everyone,
> 
> We would like to announce some changes that just happened in the CI
> Train that will probably interest all landers and, possibly, also some
> developers using our phones and our release process. Please read on!
> 
> The RTM Landing Approaches document will be updated as well [1].
> 
> 
> ***
> * CI Train sync: functionality using binary source copies by default
> ***
> 
> So, as most of you know, in the past whenever someone wanted to request
> a sync from for instance ubuntu to ubuntu-rtm, CI Train was doing a
> source copy, changing the version number (adding the ~rtm) and
> retargeting to 14.09. This was to be safe that the package is rebuilt
> with the build-dependencies that were in the selected distribution.
> 
> But after some discussions, we decided that in 95% of cases the
> additional rebuild is not required and a binary copy would be
> sufficient. So, to make the process faster and cleaner, we decided now
> to switch to making binary copies for sync: silos by default. This
> should decrease the time needed when a sync is happening.
> 
> Please be advised to properly test the sync packages on the target
> archive though. Binary copies carry some risk, so make sure everything
> runs correctly on the new distribution.
> 
> The functionality to do source copies as before is still there under the
> REBUILD_SOURCES_FOR_SYNC flag in the jenkins Build job. Once switched,
> the old way of things is enabled and the packages will be rebuilt in the
> PPA.
> 
> 
> ***
> * Flag to disable version mangling for RTM
> ***
> 
> In case someone needs to do a source copy instead of a binary copy, we
> have added a flag that enables to not mangle the version number during
> rebuild (i.e. not adding the ~rtm bit to the package). This can also be
> useful when you notice that CI Train appends this ~rtm bit in the wrong
> place of the version number. All that is needed is setting the
> DO_NOT_APPEND_RTM_TO_VERSION checkbox in the Build job.
> 
> 
> ***
> * Sync from silo working both ways
> ***
> 
> This is rather old news but worth mentioning here as well. CI Train
> sync: always supported syncing ubuntu -> ubuntu-rtm and ubuntu-rtm ->
> ubuntu, but the sync:<silo_number> functionality only worked one way
> (from ubuntu to ubuntu-rtm). We modified it so that you can now sync
> from any silo for any distro. So, if you have an ubuntu-rtm silo which
> you want to sync to ubuntu, you can do that now freely.
> 
> This mean some people can now try landing things to RTM first and then
> syncing that up to ubuntu.
> 
> 
> Thanks!
> 
> 
> [1] https://wiki.ubuntu.com/citrain/RTMLandingApproaches
> 
> Best regards,
> 


-- 
Łukasz 'sil2100' Zemczak
 lukasz.zemczak@xxxxxxxxxxxxx
 www.canonical.com