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 earli
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:
Thanks!
We can continue on this line!
On 08/09/2018 02:10 PM, John McDonnell wrote:
Sorry for the spam, pressed send a little to early...
The pipeline looks like:
node('H29') {
stage('Clone Sources') {
git branch: 'release90', url:
'https://github.com/apache/incubator-netbeans.g
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
wrote:
> Thanks John!
>
> Good idea! Now my question, where sh
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 McDon
Sorry for the spam, pressed send a little to early...
The pipeline looks like:
node('H29') {
stage('Clone Sources') {
git branch: 'release90', url: '
https://github.com/apache/incubator-netbeans.git'
}
stage ('Build Snap Package') {
sh 'cd nbbuild/packaging/ && snapcra
I created a Jenkins job with a Jenkins pipeline:
https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-snap-packages/
I ran it and it returned an error:
/home/jenkins/jenkins-slave/workspace/incubator-netbeans-snap-packages@tmp/durable-8c39f48a/script.sh:
line 2: snapcraft:
@Laszlo Kishalmi
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 Kishal
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 so
