cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre-Luc Dion <pdion...@apache.org>
Subject Re: Jenkin automated job to create release package
Date Tue, 14 Jul 2015 21:40:06 GMT
I've updated jenkins jobs for release to put rpms in centos/{6|7} instead
of centos7|rhel
although, centos/6 differ from rhel folder and documentation refer to URL
with rhel,  so should we replace centos/6 content by rhel and make rhel a
symlink ?

For debian, the build create a set of .deb files and it copy them in
precise and trusty, it's also running index-ubuntu-archive.sh which take
close to 1hour to run. Is there a way to optimize it ?

Let's update documentation URLs at the next main release. Hope this add
pressure on 4.6 to go out ;-)

For 12.04: I agree, maybe we could drop support of it at the next release?


On Tue, Jul 14, 2015 at 6:02 AM, Wido den Hollander <wido@widodh.nl> wrote:

> 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
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message