[JIRA] (JENKINS-36474) Copy Artifacts - Cloudbees folder issue

2016-07-24 Thread petrikvanderve...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Petrik van der Velde commented on  JENKINS-36474  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Copy Artifacts - Cloudbees folder issue   
 

  
 
 
 
 

 
 Can you be more specific to what the permissions issues where? I'm running into this at the moment and following the documentation online is not getting me anywhere  
 

  
 
 
 
 

 
 
 

 
 
 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-36295) Component for steps

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay started work on  JENKINS-36295  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-35727) Unable to bundle react component libraries

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35727  
 
 
  Unable to bundle react component libraries   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Critical Major  
 

  
 
 
 
 

 
 
 

 
 
 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-36590) Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job

2016-07-24 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Liu commented on  JENKINS-36590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job   
 

  
 
 
 
 

 
 Does this fix also apply tomultibranch-multiconfiguration job?  
 

  
 
 
 
 

 
 
 

 
 
 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-36590) Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job

2016-07-24 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Liu edited a comment on  JENKINS-36590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job   
 

  
 
 
 
 

 
 Does this fix also apply  to  tomultibranch-multiconfiguration job?  
 

  
 
 
 
 

 
 
 

 
 
 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-36904) Running/queued indicator in favourite card "pulse" is not filled

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Cliff Meyers  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36904  
 
 
  Running/queued indicator in favourite card "pulse" is not filled
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Cliff Meyers  
 

  
 
 
 
 

 
 
 

 
 
 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-35864) Step section in log sticks to result header when scrolling

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35864  
 
 
  Step section in log sticks to result header when scrolling   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m12  
 

  
 
 
 
 

 
 
 

 
 
 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-35864) Step section in log sticks to result header when scrolling

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35864  
 
 
  Step section in log sticks to result header when scrolling   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m13  
 

  
 
 
 
 

 
 
 

 
 
 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-36781) Display of SCM identifiers should be consistent

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36781  
 
 
  Display of SCM identifiers should be consistent   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 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-36781) Display of SCM identifiers should be consistent

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36781  
 
 
  Display of SCM identifiers should be consistent   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 

  
 
 
 
 

 
 *In Scope** Ensure that all commits have a 7 digit hash* Remove the {{#}} from the beginning of commits*Original report* h3. Procedure# Browse the blueocean interface# Main view has commits like 1234567# Build view has commits like #12345678h3. ExpectedCommit identifiers are consistent throughout the user interface.h3. ActualDifferent screens in blueocean use differently formatted identifiers for Git commits (or more generally SCM identifiers I would assume). Notably 1234567 vs #12345678 for the same commit. Git tends to use 7 digit for the short format. !screenshot-1.png|thumbnail!  !screenshot-2.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-36895) favorite star layout issues if running at page zoom < 100%

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Cliff Meyers  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36895  
 
 
  favorite star layout issues if running at page zoom < 100%   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Cliff Meyers  
 

  
 
 
 
 

 
 
 

 
 
 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-35890) Developer can click the commit ID on the Changes tab of the Run result screen to view the full commit details

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35890  
 
 
  Developer can click the commit ID on the Changes tab of the Run result screen to view the full commit details   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m7, 1.0-m10 , 1.0-m13  
 

  
 
 
 
 

 
 
 

 
 
 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-36513) BlueRun stop() does not use TreeResponse

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36513  
 
 
  BlueRun stop() does not use TreeResponse   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m13  
 

  
 
 
 
 

 
 
 

 
 
 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-36425) Move non-multibranch run button into header

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36425  
 
 
  Move non-multibranch run button into header   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m13  
 

  
 
 
 
 

 
 
 

 
 
 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-36851) Favourite stars should be hidden for the anonymous user

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36851  
 
 
  Favourite stars should be hidden for the anonymous user   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m13  
 

  
 
 
 
 

 
 
 

 
 
 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-35768) Developer can filter the activity list to a specific branch

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35768  
 
 
  Developer can filter the activity list to a specific branch   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m13  
 

  
 
 
 
 

 
 
 

 
 
 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-35810) Developer sees the Branches tab organised by relevance

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35810  
 
 
  Developer sees the Branches tab organised by relevance   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m13  
 

  
 
 
 
 

 
 
 

 
 
 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-36781) Display of SCM identifiers should be consistent

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36781  
 
 
  Display of SCM identifiers should be consistent   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m12  
 

  
 
 
 
 

 
 
 

 
 
 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-36782) SCM identifiers too small

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Ben Walding good catch. Updated these styles in the JDL.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36782  
 
 
  SCM identifiers too small   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open Resolved  
 
 
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-36590) Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job

2016-07-24 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-36590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job   
 

  
 
 
 
 

 
 Just added JENKINS-36590 to 1.5 release notes. 1.5 will be released soon (<4 weeks I believe, maybe in 1 week)  
 

  
 
 
 
 

 
 
 

 
 
 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-36782) SCM identifiers too small

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36782  
 
 
  SCM identifiers too small   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m12  
 

  
 
 
 
 

 
 
 

 
 
 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-36590) Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job

2016-07-24 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36590  
 
 
  Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open Resolved  
 
 
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-36782) SCM identifiers too small

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to James Dumay  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36782  
 
 
  SCM identifiers too small   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 James Dumay  
 

  
 
 
 
 

 
 
 

 
 
 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-36590) Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job

2016-07-24 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-36590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job   
 

  
 
 
 
 

 
 Attached Screenshot from 2016-07-25 16-25-58.png, with the parameter rendered for a job in a folder. You can see the hierarchy in the bread crumb. The parameter is being rendered with the same code provided by the reporter (thanks heaps for doing that, helped a lot to have a simple working example of how to reproduce with detailed explanation).  
 

  
 
 
 
 

 
 
 

 
 
 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-36590) Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job

2016-07-24 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36590  
 
 
  Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Attachment: 
 Screenshot from 2016-07-25 16-25-58.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-36852) Dashboard should use JWT to find the authenticated user

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Cliff Meyers  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36852  
 
 
  Dashboard should use JWT to find the authenticated user   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Cliff Meyers  
 

  
 
 
 
 

 
 
 

 
 
 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-36895) favorite star layout issues if running at page zoom < 100%

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36895  
 
 
  favorite star layout issues if running at page zoom < 100%   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m12  
 

  
 
 
 
 

 
 
 

 
 
 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-36852) Dashboard should use JWT to find the authenticated user

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36852  
 
 
  Dashboard should use JWT to find the authenticated user   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m13  
 

  
 
 
 
 

 
 
 

 
 
 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-36904) Running/queued indicator in favourite card "pulse" is not filled

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36904  
 
 
  Running/queued indicator in favourite card "pulse" is not filled
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Jenkins Blue Ocean 2016-07-25 14-26-10.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Jul/25 4:29 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 Cliff Meyers as we discussed the indicator here is not solidly filled like the others. Feel free to pick up JENKINS-36858 if that feels like it will allow some reuse of mixins.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 
 

[JIRA] (JENKINS-36590) Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job

2016-07-24 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita stopped work on  JENKINS-36590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 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-36855) BlueOcean Not Honoring Parameters For Pipeline Projects

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Thanks for reporting. We are tracking this in JENKINS-36059.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36855  
 
 
  BlueOcean Not Honoring Parameters For Pipeline Projects   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-36884) Add Rollbar support

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36884  
 
 
  Add Rollbar support   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0-m12  
 

  
 
 
 
 

 
 
 

 
 
 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-36895) favorite star layout issues if running at page zoom < 100%

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36895  
 
 
  favorite star layout issues if running at page zoom < 100%   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 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-36884) Add Rollbar support

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Vivek Pandey  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36884  
 
 
  Add Rollbar support   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Vivek Pandey  
 

  
 
 
 
 

 
 
 

 
 
 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-36903) Development footer is missing on blueocean.io

2016-07-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36903  
 
 
  Development footer is missing on blueocean.io   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Vivek Pandey  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Jul/25 3:58 AM  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 Vivek Pandey I think you broke this when you did the cleanup in JENKINS-36481  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin

2016-07-24 Thread pskumar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Suresh Kumar commented on  JENKINS-29652  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin   
 

  
 
 
 
 

 
 I have the same issue and figured out a way implementing same requirement using promotionsbuild-plugin. In this case configure Promotion as Trigger JobD when downstream projects JobB & JobC completed in JobA   
 

  
 
 
 
 

 
 
 

 
 
 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-36590) Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job

2016-07-24 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita started work on  JENKINS-36590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-36590) Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job

2016-07-24 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita commented on  JENKINS-36590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active-Choice jenkinsProject variable is not available under Folder or Multibranch-Multiconfiguration job   
 

  
 
 
 
 

 
 Issue reproduced locally. Debugger attached, let's see what's going on.  
 

  
 
 
 
 

 
 
 

 
 
 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-36902) Refactor destructured objects to not be destructured.

2016-07-24 Thread i...@ivan.net.nz (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Meredith created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36902  
 
 
  Refactor destructured objects to not be destructured.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Jul/25 1:44 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ivan Meredith  
 

  
 
 
 
 

 
 Example below make it hard to read code. In general destructing nested data should probably be avoided.  

 

 const {
context: {
router,
location,
pipeline: {
_class: pipelineClass,
fullName,
organization,
},
},
props: {
result: {
durationInMillis,
estimatedDurationInMillis,
pipeline,
id,
result,
state,
startTime,
endTime,
commitId,
},
changeset,
},
} = this;
 

  
 

  
 
 
 
 

 
 
 

 
   

[JIRA] (JENKINS-29287) Merge build fails when ref contains remote's name

2016-07-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-29287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Merge build fails when ref contains remote's name   
 

  
 
 
 
 

 
 [~andreineculau] I don't understand your latest comment clearly enough to use it to duplicate the problem you're seeing.  Can you provide a set of step by step instructions that will show the problem you're describing?You said:{quote}The sender uses origin/master (a value accepted by the git plugin in the "SCM" block) and cannot be changed{quote}Does that mean upstream job definition is passing a parameter to a downstream job, and you can't separate the parameters into separate values for repository name and branch name?  Or, is there some other meaning in what you said? Which location accepts "origin/master" in the SCM block that cannot be changed?  The branch name (where it could be changed to "master", as far as I know), or the refspec, or something else?  
 

  
 
 
 
 

 
 
 

 
 
 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-29287) Merge build fails when ref contains remote's name

2016-07-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-29287  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Merge build fails when ref contains remote's name   
 

  
 
 
 
 

 
 Andrei Neculau I don't understand your latest comment clearly enough to use it to duplicate the problem you're seeing. Can you provide a set of step by step instructions that will show the problem you're describing? You said: 

The sender uses origin/master (a value accepted by the git plugin in the "SCM" block) and cannot be changed
 Does that mean upstream job definition is passing a parameter to a downstream job, and you can't separate the parameters into separate values for repository name and branch name? Or, is there some other meaning in what you said?  
 

  
 
 
 
 

 
 
 

 
 
 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-21845) Command "git rev-parse /develop^{commit}" returned status code 128

2016-07-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Mark Waite  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-21845  
 
 
  Command "git rev-parse /develop^{commit}" returned status code 128   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Nicolas De Loof Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 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-21845) Command "git rev-parse /develop^{commit}" returned status code 128

2016-07-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-21845  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Command "git rev-parse /develop^{commit}" returned status code 128   
 

  
 
 
 
 

 
 rlagoue a key change from 2.5.0 to 2.5.1 is that the original clone now honors the refspec (see JENKINS-31393) specified behind the "Advanced" button of the git plugin "Repositories" section. Could you check the refspec listed in that section of your job definition to confirm that it includes the develop branch? An alternate way to check if that is the problem affecting you is to test drive the pre-release build from pull request 425. That pull request switches back to the 2.5.0 (and before) default of always pulling all references with the initial clone, even if the refspec will then cause later operations to ignore those references.  
 

  
 
 
 
 

 
 
 

 
 
 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-21845) Command "git rev-parse /develop^{commit}" returned status code 128

2016-07-24 Thread lagoue.njin...@bao-sarl.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 rlagoue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-21845  
 
 
  Command "git rev-parse /develop^{commit}" returned status code 128   
 

  
 
 
 
 

 
Change By: 
 rlagoue  
 
 
Comment: 
 HelloI started facing this issue after an upgrade from 2.5.0 to 2.5.1. Downgrading to 2.5.0 solved the issue. The problem is still present in 2.5.2 I just tested it.  
 

  
 
 
 
 

 
 
 

 
 
 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-21845) Command "git rev-parse /develop^{commit}" returned status code 128

2016-07-24 Thread lagoue.njin...@bao-sarl.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 rlagoue reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Hello I started facing this issue after an upgrade from 2.5.0 to 2.5.1. Downgrading to 2.5.0 solved the issue. The problem is still present in 2.5.2 I just tested it.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-21845  
 
 
  Command "git rev-parse /develop^{commit}" returned status code 128   
 

  
 
 
 
 

 
Change By: 
 rlagoue  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-21845) Command "git rev-parse /develop^{commit}" returned status code 128

2016-07-24 Thread lagoue.njin...@bao-sarl.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 rlagoue commented on  JENKINS-21845  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Command "git rev-parse /develop^{commit}" returned status code 128   
 

  
 
 
 
 

 
 Hello I started facing this issue after an upgrade from 2.5.0 to 2.5.1. Downgrading to 2.5.0 solved the issue. The problem is still present in 2.5.2 I just tested it.  
 

  
 
 
 
 

 
 
 

 
 
 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-34488) Failing 'assert' hangs the pipeline

2016-07-24 Thread alex.fran...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Francis edited a comment on  JENKINS-34488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failing 'assert' hangs the pipeline   
 

  
 
 
 
 

 
 Worth noting a workaround: just add a message to the assertion, e.g.{code: groovy java }assert false : 'oh no!'{code}  
 

  
 
 
 
 

 
 
 

 
 
 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-34488) Failing 'assert' hangs the pipeline

2016-07-24 Thread alex.fran...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Francis commented on  JENKINS-34488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failing 'assert' hangs the pipeline   
 

  
 
 
 
 

 
 Worth noting a workaround: just add a message to the assertion, e.g. 

 

Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml


assert false : 'oh no!'
 

  
 

  
 
 
 
 

 
 
 

 
 
 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-34924) p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace

2016-07-24 Thread b...@cbord.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Langton commented on  JENKINS-34924  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace   
 

  
 
 
 
 

 
 I was able to work around this issue in 1.4.3, by using the new "Poll on Master using Last Build" option. Thanks! Ben Langton  
 

  
 
 
 
 

 
 
 

 
 
 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-33986) Get an Exception in Jenkins log while configuring a build job with Jira trigger

2016-07-24 Thread jaydenlee2...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jayden Lee commented on  JENKINS-33986  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Get an Exception in Jenkins log while configuring a build job with Jira trigger   
 

  
 
 
 
 

 
 I got this exception too.  repro step: 1. In the jenkins job configuration, select "Changelog trigger", set Jira Field Matcher". then change the jira status, the jenkins job can be triggered. 2. input the JQL filter and save the configuration, the jenkins log report the NullPointerException, and the job CANNOT be triggered anymore. please please try to fix this ASAP cause I really need this in my work. Thanks a lot.  
 

  
 
 
 
 

 
 
 

 
 
 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-36824) Can not deploy EAR to Websphere using deployer plugin.

2016-07-24 Thread sijo.josa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 sijo josan commented on  JENKINS-36824  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can not deploy EAR to Websphere using deployer plugin.   
 

  
 
 
 
 

 
 Thanks Greg!  
 

  
 
 
 
 

 
 
 

 
 
 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-36824) Can not deploy EAR to Websphere using deployer plugin.

2016-07-24 Thread sijo.josa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 sijo josan closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36824  
 
 
  Can not deploy EAR to Websphere using deployer plugin.   
 

  
 
 
 
 

 
Change By: 
 sijo josan  
 
 
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-36811) Cannot update JIRA custom field through jira-ext plugin

2016-07-24 Thread orensc...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oren Schor edited a comment on  JENKINS-36811  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot update JIRA custom field through jira-ext plugin   
 

  
 
 
 
 

 
 [~dalvizu] There are 2 fields I'm trying to update:1. Label field (which can contain more than one value)2. User Picker (single user) field which can contain only 1 value. Are Is  the update of these 2 fields supported?  
 

  
 
 
 
 

 
 
 

 
 
 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-36811) Cannot update JIRA custom field through jira-ext plugin

2016-07-24 Thread orensc...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oren Schor commented on  JENKINS-36811  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot update JIRA custom field through jira-ext plugin   
 

  
 
 
 
 

 
 Dan Alvizu There are 2 fields I'm trying to update: 1. Label field (which can contain more than one value) 2. User Picker (single user) field which can contain only 1 value. Are the update of these 2 fields supported?  
 

  
 
 
 
 

 
 
 

 
 
 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-36846) request to have a contribution guildeline to build email-ext-plugin from source

2016-07-24 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum commented on  JENKINS-36846  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: request to have a contribution guildeline to build email-ext-plugin from source   
 

  
 
 
 
 

 
 Just got it to build on the build server work now?  
 

  
 
 
 
 

 
 
 

 
 
 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-28266) JMeter sampler error count isn't checked against error thresholds

2016-07-24 Thread hitesh.h.pa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hitesh Patel commented on  JENKINS-28266  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JMeter sampler error count isn't checked against error thresholds   
 

  
 
 
 
 

 
 Using Mac and latest changes from master for performance plugin. > mvn compile -DskipTests > mvn hpi:run Looks like the issue is resolved with the latest changes from master, this is the console result when parsing should_fail.jtl. 

 
Building in workspace /Users/hitesh/github/performance-plugin/work/jobs/HiteshTemp/workspace
Performance: Percentage of errors greater or equal than 0% sets the build as unstable
Performance: Percentage of errors greater or equal than 0% sets the build as failure



Performance: Recording JMeter reports 'should_fail.jtl'
Performance: Parsing JMeter report file '/Users/hitesh/github/performance-plugin/./work/jobs/HiteshTemp/builds/2016-07-24_00-42-53/performance-reports/JMeter/should_fail.jtl'.
should_fail.jtl has an average of: 15
Performance: File should_fail.jtl reported 100.0% of errors [FAILURE]. Build status is: FAILURE



Build step 'Publish Performance test result report' changed build result to FAILURE
Finished: FAILURE
 

  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-36901) Can I archive with xcode, but with Jenkins fail, error with bridging-header

2016-07-24 Thread continuous.integrat...@appschmiede.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 conti integ created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36901  
 
 
  Can I archive with xcode, but with Jenkins fail, error with bridging-header   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 xcode-plugin  
 
 
Created: 
 2016/Jul/24 7:51 AM  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 conti integ  
 

  
 
 
 
 

 
 Hi, I'm working on workspace, with main project and pods. On of pods vfrReader. Main project is in swift so I use bridging header to include vfrReader in my project. The problem is I can make an Archive product via Xcode, but when I run jenkins build on the same target, scheme, and ..  I face with this error:  

 

Header.h:21:9: error: 'vfrReader/ReaderViewController.h' file not found
#import 
^
:0: error: failed to import bridging header 
 

 There is no problem in xcode, xcode easilly can find the header files. Any idea? where should I investigate the problem?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
 

[JIRA] (JENKINS-36733) Performance Plugin upload failures

2016-07-24 Thread hitesh.h.pa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hitesh Patel resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36733  
 
 
  Performance Plugin upload failures   
 

  
 
 
 
 

 
Change By: 
 Hitesh Patel  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 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-27220) Error Column in Performance Trend report is showing as 100% though HTTP Response code is 200.

2016-07-24 Thread hitesh.h.pa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hitesh Patel commented on  JENKINS-27220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error Column in Performance Trend report is showing as 100% though HTTP Response code is 200.   
 

  
 
 
 
 

 
 This issue appears to be the same as JENKINS-30963. Pull request has been submitted.  
 

  
 
 
 
 

 
 
 

 
 
 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-36249) Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen

2016-07-24 Thread thomas.sau...@newtec.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Sauter edited a comment on  JENKINS-36249  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen   
 

  
 
 
 
 

 
 I had the same issue after upgrading Jenkins from version 1.6xx to 2.7.1.The err.log also showed me the same lines. {quote} Jun 27, 2016 12:34:56 PM hudson.PluginManager$1$3$2$1 reactOnCycle {quote} SEVERE: found cycle in plugin dependencies: (root=Plugin:git, deactivating all involved) Plugin:git -> Plugin:workflow-scm-step -> Plugin:gitJun 27, 2016 12:35:11 PM hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtExceptionSEVERE: A thread (pool-6-thread-6/32) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.java.lang.NoClassDefFoundError: org/jenkinsci/plugins/github_branch_source/GitHubSCMSource{quote}After i updated manually the *workflow-scm-step* plugin, Jenkins was going on.I think it is related to his issue JENKINS-35247.  
 

  
 
 
 
 

 
 
 

 
 
 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-36249) Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen

2016-07-24 Thread thomas.sau...@newtec.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas commented on  JENKINS-36249  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Stuck at "Please wait while Jenkins is getting ready to work..." Screen   
 

  
 
 
 
 

 
 I had the same issue after upgrading Jenkins from version 1.6xx to 2.7.1. The err.log also showed me the same lines. Jun 27, 2016 12:34:56 PM hudson.PluginManager$1$3$2$1 reactOnCycle 

SEVERE: found cycle in plugin dependencies: (root=Plugin:git, deactivating all involved) Plugin:git -> Plugin:workflow-scm-step -> Plugin:git 
Jun 27, 2016 12:35:11 PM hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException SEVERE: A thread (pool-6-thread-6/32) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NoClassDefFoundError: org/jenkinsci/plugins/github_branch_source/GitHubSCMSource
 After i updated manually the workflow-scm-step plugin, Jenkins was going on. I think it is related to his issue JENKINS-35247.  
 

  
 
 
 
 

 
 
 

 
 
 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-30963) JMeter's Percentage of errors is always 100%

2016-07-24 Thread hitesh.h.pa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hitesh Patel commented on  JENKINS-30963  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JMeter's Percentage of errors is always 100%   
 

  
 
 
 
 

 
 Submitted fix https://github.com/jenkinsci/performance-plugin/pull/69. Marco Piras With this fix, sample test.jtl will work with "JMeter Performance Report" and not show 100% errors for all uri's.  
 

  
 
 
 
 

 
 
 

 
 
 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-30963) JMeter's Percentage of errors is always 100%

2016-07-24 Thread hitesh.h.pa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hitesh Patel assigned an issue to Hitesh Patel  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-30963  
 
 
  JMeter's Percentage of errors is always 100%   
 

  
 
 
 
 

 
Change By: 
 Hitesh Patel  
 
 
Assignee: 
 vergnes Hitesh Patel  
 

  
 
 
 
 

 
 
 

 
 
 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-36846) request to have a contribution guildeline to build email-ext-plugin from source

2016-07-24 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum commented on  JENKINS-36846  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: request to have a contribution guildeline to build email-ext-plugin from source   
 

  
 
 
 
 

 
 Whats the maven command you are running?  
 

  
 
 
 
 

 
 
 

 
 
 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-36846) request to have a contribution guildeline to build email-ext-plugin from source

2016-07-24 Thread writeback2po...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 pooja shah commented on  JENKINS-36846  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: request to have a contribution guildeline to build email-ext-plugin from source   
 

  
 
 
 
 

 
 thanks David, latest pull have solved few but still it fails on "findbugs", any work-around I can try? on a hunch i'm thinking of commenting these lines of code, though not aware of the impact at the moment.  ? ``` Downloaded: http://repo.jenkins-ci.org/public/org/apache/maven/maven-model/2.0.6/maven-model-2.0.6.jar (0 B at 0.0 KB/sec) [INFO] Fork Value is true [java] Warnings generated: 7 [INFO] Done FindBugs Analysis [INFO]  [INFO] <<< findbugs-maven-plugin:3.0.3:check (findbugs) < :findbugs @ email-ext <<< [INFO]  [INFO] — findbugs-maven-plugin:3.0.3:check (findbugs) @ email-ext — [INFO] BugInstance size is 7 [INFO] Error size is 0 [INFO] Total bugs: 7 [INFO] Possible null pointer dereference in hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisherContext) due to return value of called method [hudson.plugins.emailext.ExtendedEmailPublisher, hudson.plugins.emailext.ExtendedEmailPublisher] Dereferenced at ExtendedEmailPublisher.java:[line 595]Known null at ExtendedEmailPublisher.java:[line 595] NP_NULL_ON_SOME_PATH_FROM_RETURN_VALUE [INFO] Exception is caught when Exception is not thrown in hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisherContext) [hudson.plugins.emailext.ExtendedEmailPublisher] At ExtendedEmailPublisher.java:[line 462] REC_CATCH_EXCEPTION [INFO] Exception is caught when Exception is not thrown in hudson.plugins.emailext.plugins.EmailTriggerDescriptor._createDefault() [hudson.plugins.emailext.plugins.EmailTriggerDescriptor] At EmailTriggerDescriptor.java:[line 47] REC_CATCH_EXCEPTION [INFO] Found reliance on default encoding in hudson.plugins.emailext.plugins.content.AbstractEvalContent.getManagedFile(String): String.getBytes() [hudson.plugins.emailext.plugins.content.AbstractEvalContent] At AbstractEvalContent.java:[line 148] DM_DEFAULT_ENCODING [INFO] Possible null pointer dereference in hudson.plugins.emailext.plugins.recipients.CulpritsRecipientProvider.addRecipients(ExtendedEmailPublisherContext, EnvVars, Set, Set, Set) due to return value of called method [hudson.plugins.emailext.plugins.recipients.CulpritsRecipientProvider, hudson.plugins.emailext.plugins.recipients.CulpritsRecipientProvider] Dereferenced at CulpritsRecipientProvider.java:[line 57]Known null at CulpritsRecipientProvider.java:[line 57] NP_NULL_ON_SOME_PATH_FROM_RETURN_VALUE [INFO] Possible null pointer dereference in hudson.plugins.emailext.plugins.recipients.CulpritsRecipientProvider.addRecipients(ExtendedEmailPublisherContext, EnvVars, Set, Set, Set) due to return value of called method [hudson.plugins.emailext.plugins.recipients.CulpritsRecipientProvider, hudson.plugins.emailext.plugins.recipients.CulpritsRecipientProvider] Dereferenced at CulpritsRecipientProvider.java:[line 62]Known null at CulpritsRecipientProvider.java:[line 62] NP_NULL_ON_SOME_PATH_FROM_RETURN_VALUE [INFO] Possible null pointer dereference in hudson.plugins.emailext.plugins.recipients.FirstFailingBuildSuspectsRecipientProvider.addRecipients(ExtendedEmailPublisherContext, EnvVars, Set, Set, Set) due to return value of called method [hudson.plugins.emailext.plugins.recipients.FirstFailingBuildSuspectsRecipientProvider, hudson.plugins.emailext.plugins.recipients.FirstFailingBuildSuspectsRecipientProvider] Dereferenced at FirstFailingBuildSuspectsRecipientProvider.java:[line 87]Known null at FirstFailingBuildSuspectsRecipientProvider.java:[line 87] NP_NULL_ON_SOME_PATH_FROM_RETURN_VALUE [INFO]  To see bug detail using the Findbugs GUI, use the following command