On 03/22/2017 12:30 PM, Niels de Vos wrote:
On Wed, Mar 22, 2017 at 01:05:09PM +0530, Nigel Babu wrote:
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.
It really does not matter where the tarball is hosted. As long as the
emails sent to the packagers list contains the URL and it is archived on
an additional FTP/HTTP server (not only as a Jenkins artifact).
+1, no worries, as long as it is available and the mail to packagers
calls it out appropriately, as Niels put it.
Many distributions include packages for Gluster where we are not
directly involved (Arch, NetBSD, Debian, ...). We need to make sure
those packagers are informed as well.
HTH,
Niels
[1]: https://build.gluster.org/job/release/
--
nigelb
_______________________________________________
maintainers mailing list
[email protected]
http://lists.gluster.org/mailman/listinfo/maintainers
_______________________________________________
maintainers mailing list
[email protected]
http://lists.gluster.org/mailman/listinfo/maintainers
_______________________________________________
maintainers mailing list
[email protected]
http://lists.gluster.org/mailman/listinfo/maintainers
