I figured out what happened. Being a Java programmer too used to Camel case I named the file JenkinsFile. So as configured on commit to the branch head, it created a a job, but when Jenkins went loooking for aJenkinsfile, it couldn;t find one. So it disabled the job and eventually removed it.
I reverted the commit and renamed it as Jenkinsfile and it worked. :-)
I had this using the Bitbucket Branch Source plugin... switching to the Bitbucket Server Integration plugin fixed it... you can simply replace the Branch source in your existing multi-branch pipeline job.You do not lose your existing job history which is nice. This is with Jenkins 2.232, Bitbucket Branch Source 2.9.0, Bitbucket Server Integration 1.1.0.
Regards
Paul
I created a feature branch on Bitbucket and pushed JenkinsFile amongst other files to the head. As defined by the administrators, I automatically get a Jenkins job for that branch. I do see a new job with feature branch name but there is a strikethrough line through the name of the job on the Jenkins dashboard. I am wondering what conditions cause it.
I am sure it is disabled as the round icon on the left of the job is gray. I see the jobs for other branches to be active
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/66865c43-8c25-4cea-ac9f-70ed12608269n%40googlegroups.com.
Locked
