date:20160908

[JIRA] (JENKINS-37261) cucumber-jvm reports are not showing the updated results

2016-09-08 Thread anemuda...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Uday anem closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Added my comments  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37261  
 
 
  cucumber-jvm reports are not showing the updated results   
 

  
 
 
 
 

 
Change By: 
 Uday anem  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-37261) cucumber-jvm reports are not showing the updated results

2016-09-08 Thread anemuda...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Uday anem commented on  JENKINS-37261  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: cucumber-jvm reports are not showing the updated results   
 

  
 
 
 
 

 
 Lately i noticed, some how the maven repository(cucumber.json) is not update in my "C:\Users\user\.m2" folders, so the reason cucumber-reports are unable to pick the latest cucumber.json file. Rather than maven repository i configured to "my project path/target/cucumber.json" and it stared showing the accurate results.  
 

  
 
 
 
 

 
 
 

 
 
 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-37607) Get user name from google?

2016-09-08 Thread amos.shap...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Amos Shapira commented on  JENKINS-37607  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Get user name from google?   
 

  
 
 
 
 

 
 Muaaz Saleem: 

I think you could use the user email to assign permissions, at least for matrix based security. For example "b...@company.com".
 Thanks. This seems to work as you describe.  
 

  
 
 
 
 

 
 
 

 
 
 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time

2016-09-08 Thread jda...@ipswitch.com (JIRA)

Title: Message Title

Jason Davis commented on JENKINS-36883

Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time

Thanks for taking a look! I have not tried the pin label to 'now' idea (that idea just didn't dawn on me. ), but I'll give that a try ASAP and let you know. I can understand your point of view for knowing what triggered the build, but at the same time, when the build finally fires off after a quiet period, just taking the latest available change when the build finally fires off, and tracking _that _for the changes summary, I would suggest makes sense also. Say there was no quiet period or polling. If someone pushed the build now button, Perforce would gather the latest changeset at that moment and sync to that level. Polling without a quiet period also ends up syncing to the latest available changeset at build launch. It's the addition of the quiet period that is leading to different behavior, because other changes checked in after the trigger, but before the build launches (which of course is one purpose for the quiet period - in case the Devs have an "oh crap! I forgot to check that in also" moment) are being sync'ed to changeset that triggered the build, not the latest. If - no matter how you triggered the build - the build always synced and tracked to the latest changeset, the summary would be consistent no matter how the build is launched. This would be how the community plugin worked and the P4 plugin worked up through 1.3.8. It also maintains the purpose of the quiet period, otherwise the "oh crap!" changes never make it into the build, because they are checked in after the trigger changeset. Also – and this is the big thing that threw me off – it's only the files that are in the "Exclude Changes" filter that are being sync'ed to the trigger changeset level. Normal files in the view, but not in the Exclude Changes filter, are being synced to the latest available changeset at build launch. In my environment, more changes are often checked in during the quiet period, and unfortunately, the way our builds communicate, those Exclude Changes files must be the latest available at build launch time, or hell breaks loose. Thanks and hope you enjoy the conference!

1 2 3 4 >

1 - 100 of 308 matches

Mail list logo