-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/14/2015 11:40 PM, Pierre-Luc Dion wrote:
> 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
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 a
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 MD5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/10/2015 08:17 PM, 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 als
great work Pierre-Luc, no we are working on 4.5.2, nothing yet
On Fri, Jul 10, 2015 at 8:17 PM, 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
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
