Hi - Infra has created a folder in case it is needed for one of those “projects”.
https://ci-builds.apache.org/job/Pulsar/ Let me know if any more help is needed. Regards, Dave > On Aug 18, 2020, at 11:15 AM, Sijie Guo <guosi...@gmail.com> wrote: > > Okay. We can look into it to see if we can just delete them. > > > - Sijie > > On Tue, Aug 18, 2020 at 11:52 AM Dave Fisher <w...@apache.org> wrote: > >> Hi Sijie, >> >> They are still running on builds.apahce.org. >> >> Regards, >> Dave >> >>> On Aug 18, 2020, at 10:50 AM, Sijie Guo <guosi...@gmail.com> wrote: >>> >>> Hi Dave, >>> >>> I believe all the Pulsar projects have migrated to use Github Actions for >>> CI. The jobs might already not be used anymore. Other committers can >>> confirm if that is the case. >>> >>> - Sijie >>> >>> >>> On Tue, Aug 18, 2020 at 11:39 AM Dave Fisher <w...@apache.org> wrote: >>> >>>> Hi - >>>> >>>> It is critical to complete this migration THIS WEEK. >>>> >>>> I’ve submitted https://issues.apache.org/jira/browse/INFRA-20720 to >>>> request the folder. >>>> >>>> Pulsar has the following “projects” on builds.a.o. >>>> >>>> pulsar-manager-build >>>> pulsar-master >>>> pulsar-pull-request-c++-test >>>> pulsar-release-binaries >>>> pulsar-website-build >>>> pulsar_precommit_client_node >>>> pulsar_release_nightly_snapshot >>>> >>>> I can migrate the projects so that are not lost, but I have no idea >> about >>>> the integrations with GitHub and any missing Jenkins Plugins. >>>> >>>> These all need to be migrated by Friday EOD. >>>> >>>> Regards, >>>> Dave >>>> >>>> >>>>> On Aug 14, 2020, at 1:35 PM, Dave Fisher <w...@apache.org> wrote: >>>>> >>>>> Migration technique: >>>> >> https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees >>>>> >>>>> Helpful info: >>>> >> https://cwiki.apache.org/confluence/display/INFRA/Kicking+off+a+Jenkins+build+with+a+GitHub+PR >>>>> >>>>> >>>>>> On Aug 14, 2020, at 12:48 PM, Dave Fisher <w...@apache.org> wrote: >>>>>> >>>>>> Hi - >>>>>> >>>>>> There is a critical migration for Jenkins builds that the project is >>>> missing. >>>>>> >>>>>> Several PMC members ought to be subscribed to bui...@apache.org. >>>>>> >>>>>> Please act quickly. >>>>>> >>>>>> Regards, >>>>>> Dave >>>>>> >>>>>>> Begin forwarded message: >>>>>>> >>>>>>> From: Gavin McDonald <gmcdon...@apache.org> >>>>>>> Subject: [IMPORTANT] - Migration to ci-builds.a.o >>>>>>> Date: July 16, 2020 at 9:33:08 AM PDT >>>>>>> To: builds <bui...@apache.org> >>>>>>> Reply-To: bui...@apache.org >>>>>>> Reply-To: gmcdon...@apache.org >>>>>>> >>>>>>> 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 builds@a.o. 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 >>>>>> >>>>> >>>> >>>> >> >>
