[JIRA] (JENKINS-52683) Allow flexible source definition in WorkflowBranchProjectFactories

[stephen.alan.conno...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52683  
 
 
  Allow flexible source definition in WorkflowBranchProjectFactories   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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 https://groups.google.com/d/optout.

[JIRA] (JENKINS-52683) Allow flexible source definition in WorkflowBranchProjectFactories

[stevengfos...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven Foster created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52683  
 
 
  Allow flexible source definition in WorkflowBranchProjectFactories   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Stephen Connolly  
 
 
Components: 
 branch-api-plugin, workflow-multibranch-plugin  
 
 
Created: 
 2018-07-20 22:51  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Steven Foster  
 

  
 
 
 
 

 
 I'd like to write an extension which allows a different script path to be set for Tag type heads. My use case is that my Branch type builds build, test and store artifacts ready for release/deploy. Only tag builds perform whatever is needed to release that artifact. Releasing can mean different things for different projects. For smaller projects, it's ok to have the entire pipeline run again with an additional release stage covered by a when directive checking for a tag. With a large project this is an unfortunate inefficiency. I would like to define a separate Jenkinsfile which just handles releasing the artifact previously built in the branch build.   I figure this can be possible by defining a new BranchProjectFactory, and using the createDefinition method to pick one Jenkinsfile for branch/pr and one for tags. The method would need to expose information about the head being built though. Perhaps passing through the Branch object would be helpful?