Hi Piotr, no, you would simply add a Jenkinsfile to the develop branch similar to the one we use in PLC4X: https://github.com/apache/plc4x/blob/develop/Jenkinsfile
The plugin will automatically scan all branches of the given repo for existence of a Jenkinsfile and for every one where it finds one it will setup a build using the information in the Jenkinsfile. So if you push a new branch, it will setup a new Jenkins build for that and as soon as a branch is deleted, so will the corresponding job. The only thing I would be careful about, is to setup the Jenkinsfile to do a "mvn deploy" only for the "develop" branch (Like we do it in PLC4X) ... otherwise it will become a mess. Chris Am 23.07.20, 10:45 schrieb "Piotr Zarzycki" <[email protected]>: Hi Chris, Thanks for suggestion - Are you talking about custom branch where we have to create 3 branches together with same name. We are doing this very rarely - in fact non of us did that since at lest 2 years. What would be an advantage of having such setup for develop ? Thanks, Piotr czw., 23 lip 2020 o 10:32 Christofer Dutz <[email protected]> napisał(a): > Hi all, > > I would instead suggest to create a "Jenkinsfile" which Jenkins can pick > up with the multibranch pipeline plugin. > > This way all you gotta do is setup a new "multibranch pipeline project", > tell it about the git repo url and it will setup the jobs automatically and > also auto-build for any branch created. So it would be setting up of 3 of > these files which would in general all be similar and to configure 3 jobs > in Jenkins. > > If you need help with that, I could be of assistance. > > Chris > > > > Am 22.07.20, 19:34 schrieb "Yishay Weiss" <[email protected]>: > > So should we be doing this [1]? > > [1] > https://wiki.jenkins.io/display/JENKINS/Administering+Jenkins#AdministeringJenkins-Moving%2Fcopying%2Frenamingjobs > > From: Piotr Zarzycki<mailto:[email protected]> > Sent: Tuesday, July 21, 2020 8:23 PM > To: Apache Royale Development<mailto:[email protected]> > Subject: Re: You folks monitoring builds@? > > That's only a first step - I'm not sure whether I find time for the > next > one ;) > > wt., 21 lip 2020 o 19:18 Carlos Rovira <[email protected]> > napisał(a): > > > Thanks for taking over guys :) > > > > El mar., 21 jul. 2020 a las 13:35, Andrew Wetmore (< > [email protected]>) > > escribió: > > > > > Good that Christopher pointed this out and that you have taken the > first > > > steps. > > > > > > a > > > > > > On Tue, Jul 21, 2020 at 7:08 AM Piotr Zarzycki < > > [email protected]> > > > wrote: > > > > > > > Relevant link to archive on builds: > > > > > > > > > > > > > > https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E > > > > > > > > Jira where I'm asking for creating folder/space for Royale: > > > > https://issues.apache.org/jira/browse/INFRA-20571 > > > > > > > > Thanks, > > > > Piotr > > > > > > > > niedz., 19 lip 2020 o 18:54 Christofer Dutz < > [email protected] > > > > > > > napisał(a): > > > > > > > > > I think they are switching to a commercial Jenkins > distribution from > > > > > CloudBees. > > > > > > > > > > I think in general managing such a huge CI server like the > Apache one > > > > with > > > > > the Open-Source version is a challenge. > > > > > The commercial distributions usually have some bells and > whistles > > that > > > > > allow managing the CI for large corporates which Apache might > benefit > > > > from. > > > > > > > > > > But I'm just guessing, so this might not be true. > > > > > > > > > > Chris > > > > > > > > > > Am 19.07.20, 15:06 schrieb "Piotr Zarzycki" < > > > [email protected] > > > > >: > > > > > > > > > > Hi Chris, > > > > > > > > > > Why they are changing that? Do you know the reason? > > > > > > > > > > Do you know Is there any way to just copy settings without > manual > > > > > steps? > > > > > > > > > > Thanks, > > > > > Piotr > > > > > > > > > > > > > > > On Sun, Jul 19, 2020, 2:06 PM Christofer Dutz < > > > > > [email protected]> > > > > > wrote: > > > > > > > > > > > Hi all, > > > > > > > > > > > > if you haven’t been following [email protected]<mailto: > > > > > [email protected]>. > > > > > > > > > > > > It seems that builds.apache.org will be soon replaced by > > > > > > ci-builds.apache.org and all jobs have to be re-setup > on the > > new > > > > CI > > > > > > system. > > > > > > So I think you should probably start setting up as I > think the > > > old > > > > > CI will > > > > > > be turned off somewhere around August 15th. > > > > > > > > > > > > Chris > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Piotr Zarzycki > > > > > > > > Patreon: *https://www.patreon.com/piotrzarzycki > > > > <https://www.patreon.com/piotrzarzycki>* > > > > > > > > > > > > > -- > > > Andrew Wetmore > > > > > > http://cottage14.blogspot.com/ > > > > > > > > > -- > > Carlos Rovira > > http://about.me/carlosrovira > > > > > -- > > Piotr Zarzycki > > Patreon: *https://www.patreon.com/piotrzarzycki > <https://www.patreon.com/piotrzarzycki>* > > > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
