Re: Jenkins Pipeline Issue

[vishad alekh]

Hi,  The file name is correct. But still Jenkins is not able to create a new job on seeing Jenkinsfile. Rather,when I deleted the multipipeline job and created it again then I was able to get a job with the same name as the branch and things were working fine as per Jenkinsfile. But I want the case to be in such a way that whenever a code is checked in with Jenkinsfile it should create a job or update the same if already existing ‎. Kindly help. Thanks and Regards Vishad Alekh Sent from my BlackBerry 10 smartphone. From: Baptiste Mathus Sent: Wednesday 31 August 2016 2:25 AM To: jenkinsci-users@googlegroups.com Reply To: jenkinsci-users@googlegroups.com Subject: Re: Jenkins Pipeline Issue What do indexing logs say? Did you actually write Jenkinsfile or JenkinsFile as in your mail. If the latter, then it's normal, it should be Jenkinsfile. Cheers Le 23 août 2016 8:52 PM, "vishad alekh" <vishadal...@gmail.com> a écrit : Thanks for the reply Mathus. I have uploaded the JenkinsFile in the repo (GIT) . After running the job i am still not getting the desired result . No job is getting created for new branch . The job is just prunning stale remotes and getting remote branches . After that its showing success. Can someone please assist with this. Thanks and Regards Vishad Alekh On Tuesday, August 23, 2016 at 5:16:55 AM UTC+5:30, Baptiste Mathus wrote: You want to have a look at the Pipeline Multibranch Plugin. Define a Jenkinsfile in the repo with your build logic. Then each time you create a new branch it will be indexed and built if such a Jenkinsfile can be found. Cheers Le 22 août 2016 11:40 PM, "vishad alekh" <visha...@gmail.com> a écrit : Hi All, I am using jenkins version 2.11 . I want to use jenkins pipeline plugin feature. We have branches in GIT which are release specific. I want that if a new branch is created in GIT, then automatically a job should be created in jenkins which atleast can do a code checkout . Please guide me for the same. Thanks and Regards Vishad -- 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 jenkinsci-use...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4ed460a3-de32-43c3-b704-07371c165f72%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 jenkinsci-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6b2498af-c2fa-4f6c-958d-adc15b217de6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/VnqO5LUSu30/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS41khUypXiXsS27fRipMZ0OjgWFJk%2BBW326h8HGaYtcDQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160917093621.5980239.8008.24996%40gmail.com. For more options, visit https://groups.google.com/d/optout.