-----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 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. > > > Make sense? > Awesome! I think we should review the directory structure though. Eg: http://cloudstack.apt-get.eu/centos/6/4.5 http://cloudstack.apt-get.eu/centos/7/4.5 Instead of having http://cloudstack.apt-get.eu/centos/ and http://cloudstack.apt-get.eu/centos7/ Wido > 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 > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVoD0yAAoJEAGbWC3bPspCHmUP/R8rjMLmNpAh12LYVNAnVafd xQHOqOrzOwUSB9Did2WgcxWhiWsYZZ29PN2qJlPNc2rBnBBlGw9d/4MAkLIxUzaW Cag55fr1M/vheqaEtg5xc6+cwr9jkmDmTHPWyvJ0uJt4djTSw5nwDCSw9+mLXYFS HYfHRMCFai0xdRKxGYrFmIjWQjhF8pdiiOIvJZbHxOEwXYP4h58vCuK9rWd8pVof W0vFjc4DqNP5VllIpaqpkH5BqLvP7C2MqI8a6I1K17gzTc6/d16FX85ShoZu76uL ZSCpIg4KFlysvHaerAcI8l1KuZrw0saWDsa9iMEK1Y2VyBYvR+2HTuU0tWyNuloC E0sIGPtweTXwfIUPQCNb1N1+/ywKvDa1ec9XwXHjtJ9hkvamlAMnGVorNYMlO73S Qq09EKmwpUh2e7RvPUUXQrbDzzDelFHGbKjNHNc6CPiqXHcNLt7HwNuQOr3TrOYP FUD7UtAsMdpaFZ6SrWWUujEQG44K0s3RCFU0cfrcYGXjILglGa4ehwH2U6DIC1Z0 CqpoFzb58UI29ljqF9BO9MX3ShTTtuTLsFjaUvwTkSYQSFrWmHB9VaCszS6WaPzh p807Ekuj5Ku5G2c7s+MRWhA2NlQrkdAhsO0LAmk0BdLEeDcxeoSBX0q2KXPRg3O8 U2EpdTnuT8aAp/XHE2WC =Soxt -----END PGP SIGNATURE-----
