Okay, then I'll step back now. I think the jobs I added are a decent starting point for subsequent tweaks. Hopefully they are useful to the project. And I disabled the old jobs, so only the new ones are running (but did not delete them).
On Fri, Aug 14, 2020, 18:40 Puja Valiyil <puja...@gmail.com> wrote: > Thanks Christopher! I think Aaron may also have been taking a look at > this with David. > > Sent from my iPhone > > > On Aug 14, 2020, at 6:19 PM, Christopher <ctubb...@apache.org> wrote: > > > > I created the following jobs based on the old ones: > > * master > > * master-with-optionals > > * fork > > * fork-with-optionals > > > > I did not create this one because the branch it was configured to > > build does not exist, and the JaCoCo post-build actions were not > > available in the new Jenkins instance. > > * incubator-rya-master-with-optionals-with-coverage > > > > I could not create the following because the GitHub Pull Request > > Builder is not installed, and pull requests probably have to be built > > in a different way. > > * incubator-rya-master-with-optionals-pull-requests > > > > So, instead, I created a parameterized build that can be triggered to > > build a pull request by specifying its PR number: > > * pr-builder > > > >> On Fri, Aug 14, 2020 at 5:19 PM Christopher <ctubb...@apache.org> > wrote: > >> > >> Hi Adina, > >> > >> I just created a test job in the Rya folder and it worked, so it did > >> not require committer privileges. > >> Therefore, I can help transfer the jobs from builds.apache.org > >> > >> There are currently 6 that I can find (I will, of course, drop > >> 'incubator' from the name): > >> incubator-rya-fork > >> incubator-rya-master > >> incubator-rya-fork-with-optionals > >> incubator-rya-master-with-optionals > >> incubator-rya-master-with-optionals-pull-requests > >> incubator-rya-master-with-optionals-with-coverage > >> > >> > >> Are all of these still needed? > >> > >> > >>> On Fri, Aug 14, 2020 at 2:16 PM Adina Crainiceanu <ad...@usna.edu> > wrote: > >>> > >>> Hi, > >>> > >>> This message is mainly for committers: > >>> We need to migrate the build jobs by tomorrow. There is a folder for > Rya on > >>> the new server. Is there anyone who has time to try to migrate the jobs > >>> (committer privileges are required)? > >>> > >>> Thanks, > >>> Adina > >>> > >>> ---------- Forwarded message --------- > >>> From: Gavin McDonald <gmcdon...@apache.org> > >>> Date: Fri, Aug 14, 2020 at 4:33 AM > >>> Subject: Who has not migrated yet? > >>> To: builds <bui...@apache.org> > >>> > >>> > >>> Hi All, > >>> > >>> Tomorrow is the deadline for migrating to ci-builds.a.o and for > builds.a.o > >>> to be turned off. > >>> > >>> So, who has not migrated yet? > >>> If not, why not? What is holding you up? > >>> > >>> If you need help, ask. > >>> > >>> If you have many jobs to migrate - please check out the script [1] > which > >>> can help you > >>> migrate all jobs in less than 5 minutes! (I know, I've tested it!) > >>> > >>> Are there plugins missing you need ? (except ghprb) > >>> What else are you waiting for? > >>> > >>> Are there outstanding tasks that Infra needs to do that might have been > >>> missed? > >>> > >>> Lets see if we can get off by end of day tomorrow > >>> > >>> [1] - > >>> > https://cwiki.apache.org/confluence/display/INFRA/Migrating+Jenkins+jobs+from+Jenkins+to+Cloudbees > >>> > >>> > >>> -- > >>> > >>> *Gavin McDonald* > >>> Systems Administrator > >>> ASF Infrastructure Team > >>> > >>> > >>> -- > >>> Dr. Adina Crainiceanu > >>> Professor > >>> Computer Science Department > >>> United States Naval Academy > >>> 410-293-6822 > >>> ad...@usna.edu > >>> http://www.usna.edu/Users/cs/adina/ >
