Hi, No problem Laszlo, glad I could help. So Jenkinsfiles can be stored in the same repo, let's say in nbbuild directory for example (maybe under a CI or Jenkins folder), and with multi-branch pipeline job in Jenkins, Jenkins will automatically create jobs for each branch.
I've taken a look earlier at our Jenkins jobs, and I can see we have 5 Jenkins jobs, which I believe could be merged into 1 pipeline script, as some of the jobs repeat steps, and I think if we had 1 pipeline we could save on the resources we actually use in some places. As a starting point, I was planning on looking into creating an experimental pipeline next week and documenting the 2 approaches. Later on, we can add steps to the pipeline in relation to the release process, and this is where could kick off a snap package build once a release is performed. I haven't looked at your setup yet, but what is required per release (I guess there's a variable for the name of the build, 9.0, or dev etc?) Regards John On Fri, 10 Aug 2018 at 22:33, Laszlo Kishalmi <laszlo.kisha...@gmail.com> wrote: > Thanks John! > > Finally it worked. We can produce a snap image on Apache infrastructure. > > BTW what should be the strategy with these Jenkins files. Separate repo? > In the future I'd like to track two branches with this: master and the > actual release. > > > On 08/09/2018 03:21 PM, John McDonnell wrote: > > Right now it doesn't look like its set up correctly, as it cannot find > 'snapcraft', > see: > > https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-snap-packages/1/console > > > On Thu, 9 Aug 2018 at 23:16, Laszlo Kishalmi <laszlo.kisha...@gmail.com> > wrote: > >> Thanks John! >> >> Good idea! Now my question, where shall I put my Jenkinsfile? >> NetBeans repository? Which branch: master or release90, or some unique >> one, or in a separate repo? >> Right now I just need to know if snapcraft set up correctly for NetBeans >> on node H29 >> >> On 08/09/2018 01:05 AM, John McDonnell wrote: >> >> @Laszlo Kishalmi <laszlo.kisha...@gmail.com> >> >> If write a Jenkinsfile and commit it, then the Jenkins Job properties are >> yours to adjust at any time, and the jenkins job will update accordingly. >> We just need to create a pipeline job and point it to the Jenkinsfile. >> >> >> Regards >> >> John >> >> >> >> On Tue, 7 Aug 2018 at 22:48, Laszlo Kishalmi <laszlo.kisha...@gmail.com> >> wrote: >> >>> Just made the Subject more descriptive. >>> >>> >>> On 08/07/2018 01:22 PM, Laszlo Kishalmi wrote: >>> > >>> > Hi there! >>> > >>> > I need a bit of Jenkins help. We are preparing the Apache >>> > infrastructure to be able to build a Snap package out of our code. >>> > (https://issues.apache.org/jira/browse/INFRA-16728) >>> > >>> > I would need somebody who can configure a simple job for test purposes >>> > on Apache Jenkins Grid. >>> > >>> > The job details: >>> > >>> > 1. Please tie it to node: H29 >>> > 2. Clone the netbeans git repository >>> > 3. Use the release90 branch >>> > 4. There shall be a shell build step: >>> > cd nbbuild/packaging/ && snapcraft >>> > >>> > That's all. >>> > >>> > >>> > Thanks! >>> > >>> >>> >> >
