On 27. Sep 2017, at 16:46, Daniel Lobato Garcia > > <[email protected]> wrote: > > > > 2 is to extend http://ci.theforeman.org/view/Release%20pipeline/ > > and make it a real pipeline from 0 to release completed. At this > > moment, releases that are not the first RC1 are mostly automated by > > https://github.com/dlobatog/foreman_release and > > https://github.com/theforeman/tool_belt. > > > > My proposal is to go forward with 2. Give Jenkins permissions to do > > all of the actions needed, and whoever is the release nanny, > > ideally only has to make sure all of the steps are moving forward. > > If something breaks, figure out how to fix it for the next release.
I agree, lets do it. I think I have permissions for most things, excepting Koji, so I can help. Some thoughts inline: Github: > - Push in foreman, foreman-selinux, foreman-installer, > smart-proxy, foreman-infra, foreman-packaging Fine, any issues can easily be reverted. > Transifex - > - Allow to change the auto-update URL to point to latest -stable > branch I assume the Transifex API can handle this? > Redmine - > - Create new "Found in Release" version API should be able to handle this, or we write a trivial plugin to expose it > Jenkins - > - Modify jobs > - Run jobs Allow Jenkins to modify iteself? EEEK, Skynet :) Seriously though, what's needed here? Wouldn't the required versions be input variables to the pipeline anyway? > Koji - > - Create tags > - SSH access to update the mash scripts > - Create packages > - Tag builds Not my area... > Repository servers > - ssh in deb.theforeman.org > - ssh in yum.theforeman.org This can easily be done, we already have limited-use SSH keys for Jenkins in the deploy_web,etc jobs. Best approach is a script for what we need that can be called from Jenkins. > Announcements - > - Post to foreman-announce > - Merge access in theforeman.org > - Change IRC message > - Publish in Twitter, G+ G+ isn't so hot for us these days, I don't do much there. Which is just as well, because setting up Google OAuth stuff is a *giant* pain in the ass. The rest seems sane, but does re-open the discussion about foreman-announce - I think more than just core releases should be put there, and if we have a pipeline for it, then... good? On Wed, 2017-09-27 at 16:56 +0200, Timo Goebel wrote: > Same for plugin releases. They also are way too manual right now. +1 - if we can get a "[email protected]" author added to every gem, then we can automate this *and* prevent missing author issues... Greg -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
