Hi, AMQ5 is using Jenkins via a Jenkinsfile in the repo, so, it should update smoothly (I will check on ci-builds anyway).
Regards JB > Le 9 mars 2021 à 23:33, Clebert Suconic <[email protected]> a écrit : > > I see the website is the pelican system. > > I'm not sure how the AMQ5 is configured on Jenkins... that's the only thing > I'm lost now. > > > > On Tue, Mar 9, 2021 at 4:31 PM Clebert Suconic <[email protected]> > wrote: > >> That's right.. I will do it for all the Branches... >> >> >> At this point now I'm looking to what I would need to change on ci-builds >> >> >> I'm looking on ci-builds for things we would need to change.. >> >> however I don't understand how ActiveMQ5 is configured here: >> >> https://ci-builds.apache.org/job/ActiveMQ/job/ActiveMQ/ >> >> >> I could find the simple configuration on artemis, but AMQ5 is using >> some fancy configuration that I don't know where it's taking it from. >> >> @Jb or anyone can you give me some pointers here? I'm really curious >> now.. (I know you could say you would change it. .but at this point >> I'm trying to understand what is going on :) ) >> >> >> Also: where is the build for the website? I can't find it on >> ci-builds.apache.org >> >> On Tue, Mar 9, 2021 at 3:10 AM Jean-Baptiste Onofre <[email protected]> >> wrote: >>> >>> That’s my guess as well ;) >>> >>>> Le 9 mars 2021 à 08:57, michael.andre.pearce < >> [email protected]> a écrit : >>>> >>>> I assume the plan is to cover all repos, not just artemis.Sent from my >> Galaxy >>>> -------- Original message --------From: Clebert Suconic < >> [email protected]> Date: 06/03/2021 14:33 (GMT+00:00) To: >> [email protected] Subject: Re: [DISCUSS] Renaming master as main We >> will have to create the main branch on gitbox and Infra will make theswitch >> on GitHub.On Sat, Mar 6, 2021 at 12:15 AM Jean-Baptiste Onofre < >> [email protected]>wrote:> Correct, we should focus on gitbox (that’s why >> better to ask to infra).>> Regards> JB>> > Le 5 mars 2021 à 23:16, Justin >> Bertram <[email protected]> a écrit :> >> > Aren't the Apache GitHub >> repos just mirrors of the official versions on> > Apache's infrastructure? >> I know when we merge PRs we push to> > https://gitbox.apache.org/. If the >> GitHub repo is just a mirror> wouldn't we> > have to rename the branch on >> Apache first? I'm not real clear on all the> > details of how the >> integration works so maybe that's wrong.> >> >> > Justin> >> > On Fri, Mar >> 5, 2021 at 4:06 PM Matt Pavlovich <[email protected]>> wrote:> >> >> >> GitHub solved the PR move if the rename is done via their UI:> >>> >> >> https://github.com/github/renaming <https://github.com/github/renaming>> >>>>>>> -Matt> >>> >>> On Mar 5, 2021, at 2:54 PM, Clebert Suconic < >> [email protected]> >> >> wrote:> >>>> >>> Good point.> >>>> >>> >> I’m not sure what to do with pending PRs> >>>> >>> In artemis you could use >> the scripts and they would work.> >>>> >>> On Fri, Mar 5, 2021 at 2:54 PM >> Matt Pavlovich <[email protected]>> >> wrote:> >>>> >>>> +1 no problem. >> Please to cover the CI jobs, so we don’t lose those.> >>>> Thanks!> >>>>> >>>>>>> On Mar 5, 2021, at 11:24 AM, Clebert Suconic <> >> >> [email protected]>> >>>> wrote:> >>>>>> >>>>> I would like to >> propose to rename all of our git branches as main on> >>>>> all of our >> branches. This would be a very first easy step to take on> >>>>> renaming >> offensive language from our codebases.> >>>>>> >>>>> We could allow some >> time before we do that, say 7 days after we> decide> >>>>> to take the >> move.> >>>>>> >>>>> Anyone sees a problem with that?> >>>>>> >>>>> if >> anyone has internal forks depending on master (say if you have a> >>>>> >> downstream branch of ActiveMQ), you will likely have to update your> >>>>> >> internal git repos and scripts.> >>>>>> >>>>> We could keep the master for >> some time without being updated, until> we> >>>>> remove it later.> >>>>> >>>>>> --> >>> Clebert Suconic> >>> >>>> --Clebert Suconic >>> >> >> >> -- >> Clebert Suconic >>
