[JIRA] (JENKINS-38108) "Resume build" on Jenkins Multijob doesn't resume the build from failed step, it starts it over from first step within a phase.

2016-10-13 Thread ebrahim.mosh...@cognitoiq.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ebrahim Moshaya commented on  JENKINS-38108  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Resume build" on Jenkins Multijob doesn't resume the build from failed step, it starts it over from first step within a phase.   
 

  
 
 
 
 

 
 I have the same issue...I really wish there's away to retry the builds from the tree view.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38108) "Resume build" on Jenkins Multijob doesn't resume the build from failed step, it starts it over from first step within a phase.

2016-09-09 Thread amatuszc...@egnyte.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alan Matuszczak created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38108  
 
 
  "Resume build" on Jenkins Multijob doesn't resume the build from failed step, it starts it over from first step within a phase.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 multijob-plugin  
 
 
Created: 
 2016/Sep/09 3:53 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Alan Matuszczak  
 

  
 
 
 
 

 
 Overview: our multijob has a phase called 'Developer Quality Gates' which runs 2 jobs in the following order: 1. Integration tests 2. Acceptance tests Let's say there's a particular run of the multijob (#149) which failed because the Acceptance tests job finished with UNSTABLE status. Build #151 is a resumed build of #149 - instead of #151 starting with acceptance tests (step at which #149 failed), it started over with first step running integration tests. Build #151 log shows: 

 

14:42:24 Started by upstream project "acme_Multijob" build number 151
14:42:24 originally caused by:
14:42:24  Started by an SCM change
14:42:24  Started by an SCM change
14:42:24  Started by an SCM change
14:42:24  Started by user redacted
14:42:24  Started by upstream project "acme_Multijob" build number 149
14:42:24  originally caused by:
14:42:24   Started by an SCM change
14:42:24   Started by an SCM change