No you should not push with latest tag. The initial push should have tag '1.0.0-liberty-000'. After we validate that is a good build we can add additional tags '1.0.0' and '1.0.0-liberty'
If the build is not good we will rebuild and repush with tag '1.0.0-liberty-001'. We should never be overwriting a tag or pushing a 'latest' tag. On Oct 22, 2015 10:00 AM, "Paul Bourke" <paul.bou...@oracle.com> wrote: > Ok so now liberty is tagged we can nail down the process here. Suggest we > push first with latest, then when happy add the following tags: > > * 1.0.0 > * 1.0.0-liberty > * 1.0.0-liberty-release-001 > > === > git clone https://github.com/openstack/kolla > cd kolla > git checkout tags/1.0.0-liberty > tools/build.py \ > --type source \ > -- base < ... > \ # e.g. centos / ubuntu / oraclelinux / ... > --no-cache \ > --push > === > > Please respond with whether you're happy or not with the above. Would be > nice to get images pushed before the summit. > > Cheers, > -Paul > > On 20/10/15 23:19, Steven Dake (stdake) wrote: > >> >> >> On 10/20/15, 9:06 AM, "Paul Bourke" <paul.bou...@oracle.com> wrote: >> >> Kolla core team, >>> >>> Here's a link to an etherpad created just now for deciding the process >>> on getting release builds to dockerhub: >>> >>> https://etherpad.openstack.org/p/kolla-release-builds >>> >>> Please review and revise. Steve, can you follow up to this mail when >>> you'd like volunteers to kick off builds? >>> >> >> Paul, >> >> Thanks for the initiative here! We actually had one last minute patch >> that needs to go into the tree related to Ceph failing to build >> occasionally because of timers, so I decided to not push the tag until it >> was resolved. This was compounded by a node pool restart which broke >> about 4 hours of CI testing of the patch that needs to go in to fix the >> problem. >> >> Once the release is tagged, we can go ahead and build for direct >> consumption from the docker hub. >> >> Regards, >> -steve >> >> >> >> >>> Cheers, >>> -Paul >>> >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
