[JIRA] (JENKINS-56278) When running regression - find way to run same fixture with different parameters

2019-02-26 Thread sbhand...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 sunil bhanderi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56278  
 
 
  When running regression - find way to run same fixture with different parameters   
 

  
 
 
 
 

 
Change By: 
 sunil bhanderi  
 
 
Attachment: 
 fixturetest.7z  
 

  
 
 
 
 

 
 
 

 
 
 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-56279) System configuration does not affect timestamp in pipeline

2019-02-26 Thread william.daniel.las...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 William Laszlo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56279  
 
 
  System configuration does not affect timestamp in pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Devin Nusbaum  
 
 
Attachments: 
 a.png  
 
 
Components: 
 promoted-builds-plugin  
 
 
Created: 
 2019-02-26 09:04  
 
 
Environment: 
 Promoted Builds Plugin: 3.2  Jenkins 2.165  
 
 
Priority: 
  Major  
 
 
Reporter: 
 William Laszlo  
 

  
 
 
 
 

 
 Add an exact example for how "Date format" and "Time zone" should be used, not the whole documentation for two java classes. I tried a lot of values for those inputs but I didn't saw any change.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
  

[JIRA] (JENKINS-56278) When running regression - find way to run same fixture with different parameters

2019-02-26 Thread sbhand...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 sunil bhanderi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56278  
 
 
  When running regression - find way to run same fixture with different parameters   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 nunit-plugin  
 
 
Created: 
 2019-02-26 09:02  
 
 
Priority: 
  Major  
 
 
Reporter: 
 sunil bhanderi  
 

  
 
 
 
 

 
 If we use fixture attributes then is there a way to show the generated tests individually?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-54637) Create a servlet filter to prepopulate audit log attributes

2019-02-26 Thread lathagunaase...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Latha Sekar updated  JENKINS-54637  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54637  
 
 
  Create a servlet filter to prepopulate audit log attributes   
 

  
 
 
 
 

 
Change By: 
 Latha Sekar  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-55703) Add option to support exposing Build workspaces in JFR

2019-02-26 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez updated  JENKINS-55703  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55703  
 
 
  Add option to support exposing Build workspaces in JFR   
 

  
 
 
 
 

 
Change By: 
 Evaristo Gutierrez  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-55703) Add option to support exposing Build workspaces in JFR

2019-02-26 Thread egutier...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evaristo Gutierrez commented on  JENKINS-55703  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add option to support exposing Build workspaces in JFR   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/custom-war-packager/pull/71  
 

  
 
 
 
 

 
 
 

 
 
 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-39203) All stages show up as UNSTABLE when only one stage should

2019-02-26 Thread yai...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ‪yair yavneel‬‏ edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 this is necessary to enhance the pipeline status view, to be able to mark each stage status separately, to identify which of them if passed, unstable or failed. It is should not  be  Jenkins's decision to abort the pipeline or not. what if there are independent stages?what if I want to continue and just be aware about test/stage that was failed?I think the status and the abort action should be performed explicitly. for example - stage function that received 3 arguments:1 - stage status (mandatory)2 - Boolean if need to abort (optional - default to continue)3 - message to be print in the stage view window (optional)it is will be very helpful.     
 

  
 
 
 
 

 
 
 

 
 
 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-39203) All stages show up as UNSTABLE when only one stage should

2019-02-26 Thread yai...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ‪yair yavneel‬‏ commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 this is necessary to enhance the pipeline status view, to be able to mark each stage status separately, to identify which of them if passed, unstable or failed.  It is should not Jenkins's decision to abort the pipeline or not.  what if there are independent stages? what if I want to continue and just be aware about test/stage that was failed? I think the status and the abort action should be performed explicitly.  for example - stage function that received 3 arguments: 1 - stage status (mandatory) 2 - Boolean if need to abort (optional - default to continue) 3 - message to be print in the stage view window (optional) it is will be very helpful.     
 

  
 
 
 
 

 
 
 

 
 
 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.


<    1   2   3