[Gluster-Maintainers] Please help test the new release job
srangana at redhat.com
Thu Apr 13 17:47:56 UTC 2017
Tested 2 jobs with my mail ID. Looks fine, nothing of note discovered.
job 1: https://build.gluster.org/job/release-new/14/
job 2: https://build.gluster.org/job/release-new/15/
The artifacts will be stored as before once the bits.gluster.org
integration is complete? Asking out of curiosity.
On 04/13/2017 02:54 AM, Nigel Babu wrote:
> I overestimated the amount of effort it would take to get email notifications
> working. They do work now. So please set your own email address in the
> ANNOUNCE_EMAIL parameter to test the output.
> On Thu, Apr 13, 2017 at 10:15:06AM +0530, Nigel Babu wrote:
>> Hello folks,
>> Current and past release managers + package maintainers, please take special
>> Please test the new release job. I'm working on making email notifications
>> ready. I've eliminated a lot of code we used to run to get releases out. It
>> doesn't yet archive to bits.gluster.org. That's for next round of testing.
>> Please take a look at the script as well.
>> * Is the GERRIT_SPEC and RELEASE_VERSION largely different other than adding
>> the lack of preceding 'v'?
>> * The sed line (L77) in the current script seems unnecessary. It didn't have
>> any effect with my tests and we already get version number in ./configure
>> * The Changelog seems to be unused as well, so I got rid of it.
>> The git clone and the email notification will be handled by Jenkins. The git
>> clone, obviously works already. I'm working on getting the email bit working,
>> so you can safely test without fear that someone will be emailed.
>> : https://build.gluster.org/job/release-new/
>> : https://review.gluster.org/#/c/17047/1/build-gluster-org/scripts/release.sh
>> : https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/release.sh
> maintainers mailing list
> maintainers at gluster.org
More information about the maintainers