That said, we need to push a new build of 2.1.X out the door. On Mon, Jul 20, 2020 at 4:53 PM Emmanuel Lécharny <[email protected]> wrote:
> > On 20/07/2020 22:45, Jonathan Valliere wrote: > > Okay. Emmanuel is our go-to person for managing the CI but he has been > > unavailable recently so I should take a look at this so I can be useful. > > > I'm mostly absent, but I follow what's going on. If there is a task I > can complete quickly, then I can divert an hour or two from my tight > schedule if needed :-) > > > Yes, I guess we need to migrate those CI builds, which is not > necessarily a complex task. > > > > > > On Mon, Jul 20, 2020 at 2:55 PM Roy Lenferink <[email protected]> > wrote: > > > >> This affects all CI builds running on builds.a.o. See [1] for the > >> announcement on builds@ > >> > >> [1] > >> > https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E > >> > >> The cutoff date is August 15th, that's why I started with the site job > >> already. > >> > >> In the meantime infra created the MINA folder on the new instance so > jobs > >> can be created already. > >> > >> On 2020/07/20 17:30:57, Jonathan Valliere <[email protected]> wrote: > >>> Is this just for the MINA site or also for our CI builds? > >>> > >>> On Mon, Jul 20, 2020 at 1:16 PM Roy Lenferink <[email protected]> > >> wrote: > >>>> Hi all, > >>>> > >>>> The builds.a.o environment is on the move to a new ci-builds.a.o > >>>> environment. Some time ago I > >>>> created a mina-site job to generate the MINA site. The configuration > >> was > >>>> still part of the Jenkins job. > >>>> > >>>> I just created [1] to put this into version control. I also created > >> [2] to > >>>> get a MINA folder created on the > >>>> new Jenkins environment. On this new Jenkins environment access > control > >>>> changed a bit and > >>>> access is granted per folder now. So any MINA committer is able to > >>>> setup/manage the jobs for the MINA > >>>> project. > >>>> > >>>> In [1] I created the pipeline as a multi-branch pipeline which deploys > >>>> when changes are merged to the > >>>> 'master' branch (default branch). Unfortunately one cannot take a > quick > >>>> peak at another project its > >>>> job configuration anymore and since I am not a MINA committer I am not > >>>> able to setup the job either so > >>>> if I need to support someone let me know. > >>>> > >>>> Roy > >>>> > >>>> [1] https://github.com/apache/mina-site/pull/4 > >>>> [2] https://issues.apache.org/jira/browse/INFRA-20562 > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: [email protected] > >>>> For additional commands, e-mail: [email protected] > >>>> > >>>> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
