[JIRA] (JENKINS-40626) Allow script definition in job for Multibranch pipelines

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 By design, we require there to be a Jenkinsfile for multibranch. Sorry.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40626  
 
 
  Allow script definition in job for Multibranch pipelines   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit

[JIRA] (JENKINS-40626) Allow script definition in job for Multibranch pipelines

[jenk...@xgouchet.fr (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Xavier Gouchet created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40626  
 
 
  Allow script definition in job for Multibranch pipelines   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2016/Dec/22 10:40 AM  
 
 
Environment: 
 Jenkins v2.33 / Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux     
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Xavier Gouchet  
 

  
 
 
 
 

 
 For now, creating a Multibranch pipeline requires a `Jenkinsfile` to be present at the root of the repository. A few limitations come from this :  
 
The file MUST be named `Jenkinsfile`, meaning you can only have one script for your multibranch. What if we want to have different multibranch jobs each with a different script ? 
There must be a file present, so a multibranch job can't run against past branches that should not be commited to or have read only permissions 
 A nice improvement would be to allow defining a Pipeline script (like in standard Pipeline jobs), and add a regexp to filter which branches (and/or tags) are concerned with the current job