I updated the job I linked earlier based on what's the latest on the legacy jenkins. It ran successfully https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
I didn't replicate every config setting - main gap is the spotbugs post-build, which seems to be missing from the new jenkins plugins. That's just maven master though. Not sure about the rest. Can we do more of a "matrix" config in the new system vs cloning all the time? Patrick On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt <[email protected]> wrote: > > On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <[email protected]> wrote: > >> >> >> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <[email protected]> >> wrote: >> >>> FYI >>> >> >> Fun. I do notice it says "Hadoop and related projects have their own >> migration path to follow" - any insight on that? We are or are not lumped >> in? I would assume we are? >> >> This (eventual migration) came up a while back on the Hadoop PMC and I >> volunteered to try for us (ZK). I was never able to get it to work, I >> provided feedback to infra but they never got back, as such we have a >> project here that's not working with some basic dependencies missing: >> https://ci-hadoop.apache.org/job/zookeeper-master-maven/ >> >> That said, we can try again. Can we verify where ZK is supposed to land? >> Perhaps we can try to delete and recreate the POC job I created at that >> link to see if we can get it working? >> >> > I see another email thread on the list saying that we are part of said > "related projects". We are expected to move to > http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are already > being removed/migrated from the "H#" pool. > > Also this: > > There are over 400 plugins on the current builds.apache.org - most of which > we don't need any more, or are replaced with different plugins on the new > system. I expect there may be some plugins we still need to install to get > you going again, which is why it is vitally important that you start > testing and migrating your jobs over *now*. You should all have auth. > > Any questions, feel free to email the [email protected] list if > you are one of the projects listed below. The rest of you, not listed, a > similar email to this one will be posted for you shortly on [email protected]. > > > full details > https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E > > Patrick > > > >> Patrick >> >> >>> >>> ---------- Forwarded message --------- >>> Da: Gavin McDonald <[email protected]> >>> Date: Gio 16 Lug 2020, 18:33 >>> Subject: [IMPORTANT] - Migration to ci-builds.a.o >>> To: builds <[email protected]> >>> >>> >>> Hi All, >>> >>> This NOTICE is for everyone on builds.apache.org. We are migrating to a >>> new >>> Cloudbees based Client Master called https://ci-builds.apache.org. The >>> migrations of all jobs needs to be done before the switch off date of >>> 15th >>> August 2020, so you have a maximum of 4 weeks. >>> >>> There is no tool or automated way of migrating your jobs, the >>> differences in the platforms, the plugins and the setup makes it >>> impossible >>> to do in a safe way. So, you all need to start creating new jobs on >>> ci-infra.a.o and then , when you are happy, turn off your old builds on >>> builds.a.o. >>> >>> There are currently 4 agents over there ready to take jobs, plus a >>> floating >>> agent which is shared amongst many masters (more to come). I will migrate >>> away 2 more agents from builds.a.o to ci-builds.a.o every few days, and >>> will keep an eye of load across both and adjust accordingly. >>> >>> If needed, create a ticket on INFRA jira for any issues that crop up, or >>> email here on [email protected]. there may be one or two plugins we need to >>> install/tweak etc. >>> >>> We will be not using 'Views' at the top level, but rather we will take >>> advantage of 'Folders Plus' - each project will get its own Folder and >>> have >>> authorisation access to create/edit jobs etc within that folder. I will >>> create these folders as you ask for them to start with. This setup allows >>> for credentials isolation amongst other benefits, including but not >>> limited >>> to exclusive agents (Controlled Agents) for your own use , should you >>> have >>> any project targeted donations of agents. >>> >>> As with other aspects of the ASF, projects can choose to just enable all >>> committers access to their folder, just ask. >>> >>> We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will >>> not >>> be setting up any forwarding rules or anything like that. >>> >>> So, please, get started *now *on this so you can be sure we are all >>> completed before the final cutoff date of 15th August 2020. >>> >>> Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA >>> tickets. >>> >>> Hadoop and related projects have their own migration path to follow, same >>> cut off date, Cassandra, Beam, CouchDB have already migrated and are >>> doing >>> very well in their new homes. >>> >>> Lets get going ... >>> >>> -- >>> >>> *Gavin McDonald* >>> Systems Administrator >>> ASF Infrastructure Team >>> >>
