[JIRA] (JENKINS-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-23 Thread maciej.szewczys...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maciej Szewczyszyn edited a comment on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 I've created a simple flag which allows you to ignore the checkpoints  (and thus ,  blocking),  you can find the change in my fork:https://github.com/MaciejSzewczyszyn/cucumber-testresult-plugin/commit/4577c13283ba36ec2adb22b97ffb4d9d5b4fd95c !jenkins.png|thumbnail!Seems to work okay so far.  
 

  
 
 
 
 

 
 
 

 
 
 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-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-23 Thread maciej.szewczys...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maciej Szewczyszyn edited a comment on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 I've created a simple flag which allows you to ignore the checkpoints (and thus, blocking) , you . You  can find the change in my fork:https://github.com/MaciejSzewczyszyn/cucumber-testresult-plugin/commit/4577c13283ba36ec2adb22b97ffb4d9d5b4fd95c !jenkins.png|thumbnail!Seems to work okay so far.  
 

  
 
 
 
 

 
 
 

 
 
 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-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-14 Thread maciej.szewczys...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maciej Szewczyszyn commented on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 I've created a simple flag which allows you to ignore the checkpoints, you can find the change in my fork: https://github.com/MaciejSzewczyszyn/cucumber-testresult-plugin/commit/4577c13283ba36ec2adb22b97ffb4d9d5b4fd95c   Seems to work okay so far.  
 

  
 
 
 
 

 
 
 

 
 
 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-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-14 Thread maciej.szewczys...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maciej Szewczyszyn updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38516  
 
 
  "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
Change By: 
 Maciej Szewczyszyn  
 
 
Attachment: 
 jenkins.png  
 

  
 
 
 
 

 
 
 

 
 
 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-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-09 Thread mid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 noob alot commented on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 Forgive my ignorance w Jenkins: What if the updating part was done in a separate thread so the build itself can complete?  
 

  
 
 
 
 

 
 
 

 
 
 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-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-09 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord commented on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 See this comment The display of results and failing count etc needs to be updated.  
 

  
 
 
 
 

 
 
 

 
 
 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-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-09 Thread mid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 noob alot edited a comment on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 I'm also affected by this issue.The plugin uses Checkpoints, which wait for the status of previous build . :  Looking at the code, I don't really see why this was done. https://github.com/jenkinsci/cucumber-testresult-plugin/blob/master/src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java#L167 This code was originally added here: https://github.com/jenkinsci/cucumber-testresult-plugin/commit/c4c0274ec9cb6d14a8155d5152823d4c271561ad#diff-49f27251bb42a6e90637f8082b4c7321And was modified support pipeline builds:https://github.com/jenkinsci/cucumber-testresult-plugin/pull/8https://github.com/jenkinsci/cucumber-testresult-plugin/pull/8/files#diff-49f27251bb42a6e90637f8082b4c7321R160 It seems the status/data of the previous build isn't used. I suggest removing the checkpoints.  
 

  
 
 
 
 

 
 
 

 
 
 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-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-11-09 Thread mid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 noob alot commented on  JENKINS-38516  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
 I'm also affected by this issue. The plugin uses Checkpoints, which wait for the status of previous build. Looking at the code, I don't really see why this was done. https://github.com/jenkinsci/cucumber-testresult-plugin/blob/master/src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java#L167 It seems the status/data of the previous build isn't used.  I suggest removing the checkpoints.  
 

  
 
 
 
 

 
 
 

 
 
 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-38516) "Parsing cucumber.json" blocked by parallel job executions

2016-09-26 Thread james.vau...@elasticpath.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Vaudry created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38516  
 
 
  "Parsing cucumber.json" blocked by parallel job executions   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 James Nord  
 
 
Components: 
 cucumber-testresult-plugin  
 
 
Created: 
 2016/Sep/26 6:21 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Vaudry  
 

  
 
 
 
 

 
 Steps to reproduce: 1. Create a new freestyle job 
 
Add a string parameter: WORK_FOLDER 
Select "Execute concurrent builds if necessary" 
Under "Advanced Project Options", select "Use custom workspace", and input $ {WORK_FOLDER} 
Build action: Invoke Maven 3 "mvn clean verify..." 
Post-build action: "Publish cucumber test result" 
 2. Execute the job twice (simultaneously) with different parameters: 
 
WORK_FOLDER=foo 
WORK_FOLDER=bar 
 Expected behavior: 
 
The two jobs run in parallel and complete independently, using their separate workspaces 
 Actual behavior: One job will wait for the other job to complete. The jobs are dependent on each other in their post-build step.  One job will hang at the step until the second job finishes: