[Gluster-Maintainers] Moving release job off master

[Nigel Babu]

Hello folks,

I'd like to move the release job[1] off the master server. This is so that
we're more resilient in case of Jenkins failures. I can make the tar file an
artifact of the build and linked from the email. Is this an acceptable
solution?

We're planning on moving the Jenkins server onto a new Centos 7 machine and
upgrade to Jenkins 2. Solving this is important to the server move.

If there are security concerns around the build, I'm happy to have a specific
node where builds are done.

Shyam, Kaushal, Niels, and Jiffin - as maintainers of a currently supported
release, please chime in. I'll check in with you again if you haven't said
anything.

Niels and Kaleb - as packagers, please let me know if this change will
significantly impact your workflow at release time.

Please send in your thoughts by 7th April. I don't yet have a deadline on
*when* this will be done. That will be shaped by how much this impacts
everyone's workflow.

[1]: https://build.gluster.org/job/release/

--
nigelb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20170322/6a2930cd/attachment-0001.sig>