I hadn't noticed the tar file, thank you for pointing it out. On Wed, Mar 22, 2017 at 10:22:50AM -0400, Kaleb Keithley wrote: > > I have no issues with fetching the tar file from somewhere other than > bits.gluster.org. > > Remember though that besides the tar file there is also the SHA256sum that > goes with the tar file. > > > ----- Original Message ----- > > From: "Nigel Babu" <[email protected]> > > > > 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 > > > > _______________________________________________ > > maintainers mailing list > > [email protected] > > http://lists.gluster.org/mailman/listinfo/maintainers > >
-- nigelb
signature.asc
Description: PGP signature
_______________________________________________ maintainers mailing list [email protected] http://lists.gluster.org/mailman/listinfo/maintainers
