[JIRA] (JENKINS-49698) Show/Enable "Run" button in Jenkins Blue Ocean multibranch pipeline activity tab

[peter.nieder...@datenbetrieb.de (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Niederlag commented on  JENKINS-49698  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Show/Enable "Run" button in Jenkins Blue Ocean multibranch pipeline activity tab   
 

  
 
 
 
 

 
 would be nice to have something like this in order to unify the user experience across different job types  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188634.151930713.9228.1572955682189%40Atlassian.JIRA.

[JIRA] (JENKINS-49698) Show/Enable "Run" button in Jenkins Blue Ocean multibranch pipeline activity tab

[avl...@cloudbasesolutions.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrian Vladu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49698  
 
 
  Show/Enable "Run" button in Jenkins Blue Ocean multibranch pipeline activity tab   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-02-22 13:45  
 
 
Environment: 
 Jenkins ver. 2.73.3, Jenkins Blue Ocean 1.4.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Adrian Vladu  
 

  
 
 
 
 

 
 In the normal jobs (freestyle) or the pipeline jobs (non-multibranch), there is the "Run" button in the Jenkins Blue Ocean Pipeline. In the multi-branch pipelines, the "Run" button is missing, and you need to go to the branches tab and press the small "|>" button, which is harder to know what it means. I know that the question would be: to what branch that "Run" button to point at? I suggest having it pointed to the master branch by default and have a pipeline configuration option to change that default behavior. Or reuse the favorite plugin and point to the first favorite. 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment