One set of bot: commands will still work. Those associated with Jenkins, in general, should still work. So: bot:retest bot:ibm:retest bot:lanl:retest
Those bot: commands are processed as part of the Jenkins setup and are not reliant on the IU webhook. Note: The IBM CI is not currently setup to watch the release branches now that they have moved. I'll try to fix that tomorrow when I'm back in the office. On Tue, Sep 20, 2016 at 8:20 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com > wrote: > All the branches from ompi-release have now been merged back into the ompi > repo. > > (amusingly, we all got a gitdub email for the creation of each old release > branch) > > The ompi-release repo is now effectively closed. It will not be deleted, > however, so that old links won't go stale, and old conversations won't be > lost. We'll shortly "git rm -rf *" in each of the branches in the > ompi-release repo and leave a short README explaining that that branch has > now moved to the ompi repo -- just to further accentuate that that repo is > now closed / stale. > > There were a handful of PRs still open on the ompi-release repo: some were > failing CI tests, some hadn't received reviews, etc. Authors need to open > new PRs on the ompi repo to get them into release branches. I left them > open so that they would be easy to find; authors: please close them when > you open a new corresponding PR on the ompi repo. > > The ompi-all-the-branches sandbox repo has been deleted. > > As discussed in an email earlier today, the use of the "bot:" commands are > no longer necessary. You can just directly set labels, set milestones, and > assign people to pull requests on the ompi repo (even on release > branches). Yay! > > Also, the new github "review" functionality is *required* on all PRs on > release branches (but not on master). We have required reviews on release > branches for a long time; Github now enforces this requirement for us. > > The wiki pages about making PRs (and the bot and ...) are now out of > date. If someone could go update them to reflect this new arrangement, I > would greatly appreciate it (I have already spent far too much time on all > the infrastructure work lately) -- thank you! > > Long live the ompi repo! > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: http://www.cisco.com/web/ > about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel > -- Josh Hursey IBM Spectrum MPI Developer
_______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
