Hi, On 10-07-15 20:17, Pierre-Luc Dion wrote: > Hi, I've create a collection of jenkins jobs [1] allowing to create > packages of a release and publish them on cloudstack.apt-get.eu so > current community yum and apt repos get updated. > > I've also add pgp signature[2] for RPM's and generate MD5sum. > > The idea is to make the packaging generation super easy for Release > Manager once RC voted. So now, to create packages we just need to > fire Create-Release-Packages > <http://jenkins.buildacloud.org/view/build-release/job/Create-Release-Packages/>specifying > > the git > tag (ex: 4.4.4) the release branch name (ex:4.4) and if new > systemvm template is required. Then it triggered 4 jenkins jobs > automatically. > >
I moved the directories around a bit and now we have: * /centos/6/ * /centos/7/ The directories like /centos7 and /centos/4.X still point to the right place using symlinks. For the RPMs we should have a Jenkins job which builds for both CentOS 6 and 7 and pushes them there. For Ubuntu we only need to build for 14.04 since those also work on 12.04, but I think we should drop the release for 12.04 at some point due to very old libvirt versions. > Make sense? > > Do we have a release to build now? :-D Just did 4.4.4 > > > [1] http://jenkins.buildacloud.org/view/build-release/ [2] > http://cloudstack.apt-get.eu/RPM-GPG-KEY >
