[JIRA] [cucumber-reports-plugin] (JENKINS-30347) newest version 0.3.1 is not ok on jenkins 1.588

[peter.goe...@sap.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Goebel closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
with version 1.639 I don't have this issue anymore 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30347 
 
 
 
  newest version 0.3.1 is not ok on jenkins 1.588  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Goebel 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [nuget-plugin] (JENKINS-34420) Allow triggering on new prerelease versions

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34420 
 
 
 
  Allow triggering on new prerelease versions  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [nuget-plugin] (JENKINS-34420) Allow triggering on new prerelease versions

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34420 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow triggering on new prerelease versions  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Arnaud TAMAILLON Path: src/main/java/org/jenkinsci/plugins/nuget/Utils/NuGetCommandBase.java src/main/java/org/jenkinsci/plugins/nuget/Utils/NugetGetLatestPackageVersionCommand.java src/main/java/org/jenkinsci/plugins/nuget/Utils/NugetPackageCheckerVisitor.java src/main/java/org/jenkinsci/plugins/nuget/Utils/NugetPackagesCheckerCallable.java src/main/java/org/jenkinsci/plugins/nuget/Utils/NugetUpdater.java src/main/java/org/jenkinsci/plugins/nuget/triggers/NugetTrigger.java src/main/resources/org/jenkinsci/plugins/nuget/triggers/NugetTrigger/config.jelly src/main/resources/org/jenkinsci/plugins/nuget/triggers/NugetTrigger/config.properties src/main/resources/org/jenkinsci/plugins/nuget/triggers/NugetTrigger/config_fr.properties http://jenkins-ci.org/commit/nuget-plugin/91478ba1d5eb69489ad6902f8e4abd7cf1d13ec8 Log: Allow triggering on new prerelease versions (#3) 
[FIXED JENKINS-34420] Allow triggering on new prerelease versions 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [nuget-plugin] (JENKINS-25277) NuGet Plugin Job Root NullPointerException

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-25277 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NuGet Plugin Job Root NullPointerException  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Arnaud TAMAILLON Path: src/main/java/org/jenkinsci/plugins/nuget/triggers/NugetTrigger.java http://jenkins-ci.org/commit/nuget-plugin/482f73ce0aac30e2ce4fd17b7fcf3af233cb0eab Log: Merge pull request #4 from Greybird/

JENKINS-25277
 
NuGet Plugin Job Root NullPointerException 
Compare: https://github.com/jenkinsci/nuget-plugin/compare/b4ea5980b017...482f73ce0aac 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [nuget-plugin] (JENKINS-25277) NuGet Plugin Job Root NullPointerException

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25277 
 
 
 
  NuGet Plugin Job Root NullPointerException  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [nuget-plugin] (JENKINS-25277) NuGet Plugin Job Root NullPointerException

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-25277 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NuGet Plugin Job Root NullPointerException  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Arnaud Path: src/main/java/org/jenkinsci/plugins/nuget/triggers/NugetTrigger.java http://jenkins-ci.org/commit/nuget-plugin/9df818d71ce6023b79eb6d2dea93b0aab1235cda Log: [FIXED JENKINS-25277] NuGet Plugin Job Root NullPointerException 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [git-plugin] (JENKINS-34409) Document accessing environment variables in Git Publisher

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34409 
 
 
 
  Document accessing environment variables in Git Publisher  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [extensible-choice-parameter-plugin] (JENKINS-27374) Integrate with Script-Security plugin

[de...@ikedam.jp (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam assigned an issue to ikedam 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27374 
 
 
 
  Integrate with Script-Security plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 ikedam 
 
 
 

Assignee:
 
 ikedam 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [extensible-choice-parameter-plugin] (JENKINS-27374) Integrate with Script-Security plugin

[de...@ikedam.jp (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-27374 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Integrate with Script-Security plugin  
 
 
 
 
 
 
 
 
 
 
https://github.com/jenkinsci/extensible-choice-parameter-plugin/pull/22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [extensible-choice-parameter-plugin] (JENKINS-27374) Integrate with Script-Security plugin

[de...@ikedam.jp (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam started work on  JENKINS-27374 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 ikedam 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [collapsing-console-sections-plugin] (JENKINS-34387) Errors when plugin is unconfigured

[sam.mxra...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Gleske commented on  JENKINS-34387 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Errors when plugin is unconfigured  
 
 
 
 
 
 
 
 
 
 
You were correct to change it. I was merely replying to your oddity of pointing out "perhaps" in my original language. As always, it's hard to be 100% sure (sometimes more obvious than others) and the best way for you to be sure is to try it as well to verify my assessment. 
I feel this bug report is complete with enough details for the maintainer to address. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-branch-source-plugin] (JENKINS-34120) Do not suppress unmergeable PRs

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-34120 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Do not suppress unmergeable PRs  
 
 
 
 
 
 
 
 
 
 
I've pushed a PR 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [nuget-plugin] (JENKINS-34422) Allow using archived artifact as source for publication

[arnaud....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud TAMAILLON updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34422 
 
 
 
  Allow using archived artifact as source for publication  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arnaud TAMAILLON 
 
 
 

Issue Type:
 
 Improvement New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [nuget-plugin] (JENKINS-34422) Allow using archived artifact as source for publication

[arnaud....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud TAMAILLON created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34422 
 
 
 
  Allow using archived artifact as source for publication  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 nuget-plugin 
 
 
 

Created:
 

 2016/Apr/24 8:35 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Arnaud TAMAILLON 
 
 
 
 
 
 
 
 
 
 
Link with features provided by https://wiki.jenkins-ci.org/display/JENKINS/ArtifactDeployer+Plugin Could be usefull when used in conjonction with promotion plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
  

[JIRA] [nuget-plugin] (JENKINS-34421) Allow specifying the location of Nuget.config to use

[arnaud....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud TAMAILLON created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34421 
 
 
 
  Allow specifying the location of Nuget.config to use  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 nuget-plugin 
 
 
 

Created:
 

 2016/Apr/24 8:33 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Arnaud TAMAILLON 
 
 
 
 
 
 
 
 
 
 
Igor Berger It would be great to be able to specify the location of NuGet.config. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian 

[JIRA] [nuget-plugin] (JENKINS-34420) Allow triggering on new prerelease versions

[arnaud....@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arnaud TAMAILLON created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34420 
 
 
 
  Allow triggering on new prerelease versions  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 nuget-plugin 
 
 
 

Created:
 

 2016/Apr/24 8:33 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Arnaud TAMAILLON 
 
 
 
 
 
 
 
 
 
 
claus dannhauer: It would be great to be able to specify if Prereleases should be checked too,l when "nuget list" is called. 
Is this still in development? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
   

[JIRA] [collapsing-console-sections-plugin] (JENKINS-34387) Errors when plugin is unconfigured

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34387 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Errors when plugin is unconfigured  
 
 
 
 
 
 
 
 
 
 
Sam Gleske Based on what you wrote about the issue occurring on LTS, I rewrote this issue to be not about Jenkins 2. Please correct me (and this issue) if that was wrong. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-branch-source-plugin] (JENKINS-34120) Do not suppress unmergeable PRs

[rec...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-34120 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Do not suppress unmergeable PRs  
 
 
 
 
 
 
 
 
 
 
By the way, I don't think this is a bug but a design decision that may be changed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-29895) layout of Build Executor table is not clearly readable

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29895 
 
 
 
  layout of Build Executor table is not clearly readable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [exclusion-plugin] (JENKINS-34419) Exclusion Plugin fails on Matrix configuration after upgrade

[manosn...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34419 
 
 
 
  Exclusion Plugin fails on Matrix configuration after upgrade  
 
 
 
 
 
 
 
 
 

Change By:
 
 Noam Manos 
 
 
 

Summary:
 
 Exclusion Plugin  fails  on Matrix configuration  after upgrade 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-10613) The build name setter does not work for multi-configuration jobs

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin commented on  JENKINS-10613 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The build name setter does not work for multi-configuration jobs  
 
 
 
 
 
 
 
 
 
 
Jeremy Rampon It would be great if you provide an xml configuration of your jobs 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-23639) EnvInject squelches changes to $BUILD_DISPLAY_NAME made by build name setter plugin

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
fixed in version 1.6.5 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-23639 
 
 
 
  EnvInject squelches changes to $BUILD_DISPLAY_NAME made by build name setter plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 Gregory Boissinot Lev Mishin 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-10613) The build name setter does not work for multi-configuration jobs

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin assigned an issue to Lev Mishin 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-10613 
 
 
 
  The build name setter does not work for multi-configuration jobs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi Lev Mishin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-32753) build name should be updated even if previous buld step fails

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32753 
 
 
 
  build name should be updated even if previous buld step fails  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Issue Type:
 
 Bug Improvement 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-32753) build name should be updated even if previous buld step fails

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin commented on  JENKINS-32753 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: build name should be updated even if previous buld step fails  
 
 
 
 
 
 
 
 
 
 
Vincent Bricard-Vieu In general it is by design that if one step failed all the next steps. This plugin also can set build name at the begining and at the end of the build (not as a build step), this feature works even if build is failed. Please check out described way. If it isn't OK for then please provide more detailed use-case. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-32753) build name should be updated even if previous buld step fails

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32753 
 
 
 
  build name should be updated even if previous buld step fails  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Priority:
 
 Major Minor 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-33527) Intermittent exception thrown when using plugin

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin commented on  JENKINS-33527 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent exception thrown when using plugin  
 
 
 
 
 
 
 
 
 
 
please provide more detailed description of the bug and check if it still persists with the most recent version 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-32753) build name should be updated even if previous buld step fails

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32753 
 
 
 
  build name should be updated even if previous buld step fails  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Priority:
 
 Critical Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-31681) Build Name Setter plugin doesn't depend on Token Macro properly

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31681 
 
 
 
  Build Name Setter plugin doesn't depend on Token Macro properly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-24277) BUILD_USER_ID not available for build-name-setter plugin.

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-24277 
 
 
 
  BUILD_USER_ID not available for build-name-setter plugin.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Priority:
 
 Major Minor 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-24015) Job overview becomes unreadable with long(er) names in build history

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-24015 
 
 
 
  Job overview becomes unreadable with long(er) names in build history  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-13347) Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-13347 
 
 
 
  Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-9159) use a parameter value or an environment value for setting the build name build-name-setter-plugin

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-9159 
 
 
 
  use a parameter value or an environment value for setting the build name build-name-setter-plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Resolved Closed 
 
 
 

Assignee:
 
 Lev Mishin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-21270) Add licenses to jenkins core and plugins

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-21270 
 
 
 
  Add licenses to jenkins core and plugins  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-34221) GitHub repository is missing a tag for the 1.6.0 release

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34221 
 
 
 
  GitHub repository is missing a tag for the 1.6.0 release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-22079) Enable build parameters to be used in build name

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-22079 
 
 
 
  Enable build parameters to be used in build name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [accurev-plugin] (JENKINS-24710) Accurev changelog displays "Action=Dispatch" transactions

[skylar.sut...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Skylar Sutton commented on  JENKINS-24710 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Accurev changelog displays "Action="" transactions  
 
 
 
 
 
 
 
 
 
 
I attempted to create my own patch but the state of the public source for the accurev-plugin is shamefully sub-par. The source was several versions behind the official release, would not compile as published, and after making modifications required to get it to compile... the Jenkins plugin environment refused to acknowledge it / allow me to debug it.  
After multiple requests for help from project contributors (including Scott) went unanswered, I gave up on this effort.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [accurev-plugin] (JENKINS-21381) Create token for "SCM Issue Number" in change log format

[skylar.sut...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Skylar Sutton reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Reopening to move to SCM plugin based on the above.  
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-21381 
 
 
 
  Create token for "SCM Issue Number" in change log format  
 
 
 
 
 
 
 
 
 

Change By:
 
 Skylar Sutton 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [accurev-plugin] (JENKINS-21381) Create token for "SCM Issue Number" in change log format

[skylar.sut...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Skylar Sutton assigned an issue to Scott Tatum 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
SCM in question is accurev, see above.  
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-21381 
 
 
 
  Create token for "SCM Issue Number" in change log format  
 
 
 
 
 
 
 
 
 

Change By:
 
 Skylar Sutton 
 
 
 

Component/s:
 
 accurev-plugin 
 
 
 

Component/s:
 
 email-ext-plugin 
 
 
 

Assignee:
 
 Alex Earl Scott Tatum 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [exclusion-plugin] (JENKINS-34419) Exclusion Plugin on Matrix configuration

[manosn...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34419 
 
 
 
  Exclusion Plugin on Matrix configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Noam Manos 
 
 
 
 
 
 
 
 
 
 I've upgraded Jenkins to version 2.0 (!) and to Excusion Plugin 0.12.But now Exclusion plugins blocks my Matrix Multi job configurations.The definition inside the job is: SEMAPHORE_MATRIX_$\{NODE_NAME}   *+ On Plugin version 0.12, it fails to load Matrix configurations due to: +* Apr 24, 2016 2:40:10 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading job Automation_Matrix_Newjava.lang.NullPointerException at org.jvnet.hudson.plugins.exclusion.IdAllocator.getDescriptor(IdAllocator.java:172) at hudson.model.Descriptor.toMap(Descriptor.java:986) at hudson.util.DescribableList.toMap(DescribableList.java:151) at hudson.matrix.MatrixProject.getBuildWrappers(MatrixProject.java:812) at hudson.matrix.MatrixConfiguration.getBuildWrappers(MatrixConfiguration.java:358) at hudson.model.Project.createTransientActions(Project.java:257) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:755) at hudson.matrix.MatrixConfiguration.updateTransientActions(MatrixConfiguration.java:141) at hudson.model.AbstractProject.onLoad(AbstractProject.java:339) at hudson.model.Project.onLoad(Project.java:98) at hudson.matrix.MatrixConfiguration.onLoad(MatrixConfiguration.java:97) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:573) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:580) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:580) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:617) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:508) at hudson.model.Items.load(Items.java:327) at jenkins.model.Jenkins$18.run(Jenkins.java:2812) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:1009) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) *+ On version 0.11, it fails to load Matrix configurations due to: +* Apr 24, 2016 3:35:30 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading job Automation_Matrix_Newjava.lang.IndexOutOfBoundsException: Index: 0, Size: 1 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.remove(ArrayList.java:492) at org.jvnet.hudson.plugins.exclusion.IdAllocator.getDescriptor(IdAllocator.java:173) at hudson.model.Descriptor.toMap(Descriptor.java:986) at hudson.util.DescribableList.toMap(DescribableList.java:151) at hudson.matrix.MatrixProject.getBuildWrappers(MatrixProject.java:812) at hudson.matrix.MatrixConfiguration.getBuildWrappers(MatrixConfiguration.java:358) at hudson.model.Project.createTransientActions(Project.java:257) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:755) at 

[JIRA] [exclusion-plugin] (JENKINS-34419) Exclusion Plugin on Matrix configuration

[manosn...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34419 
 
 
 
  Exclusion Plugin on Matrix configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Noam Manos 
 
 
 
 
 
 
 
 
 
 I've upgraded Jenkins to version 2.0  (  ! ) and to Excusion Plugin 0.12.   But now Exclusion plugins blocks my Matrix Multi job configurations. The definition inside the job is: SEMAPHORE_MATRIX_${NODE_NAME}   On Plugin version 0.12, it fails to load Matrix configurations due to:Apr 24, 2016 2:40:10 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading job Automation_Matrix_Newjava.lang.NullPointerException at org.jvnet.hudson.plugins.exclusion.IdAllocator.getDescriptor(IdAllocator.java:172) at hudson.model.Descriptor.toMap(Descriptor.java:986) at hudson.util.DescribableList.toMap(DescribableList.java:151) at hudson.matrix.MatrixProject.getBuildWrappers(MatrixProject.java:812) at hudson.matrix.MatrixConfiguration.getBuildWrappers(MatrixConfiguration.java:358) at hudson.model.Project.createTransientActions(Project.java:257) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:755) at hudson.matrix.MatrixConfiguration.updateTransientActions(MatrixConfiguration.java:141) at hudson.model.AbstractProject.onLoad(AbstractProject.java:339) at hudson.model.Project.onLoad(Project.java:98) at hudson.matrix.MatrixConfiguration.onLoad(MatrixConfiguration.java:97) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:573) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:580) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:580) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:617) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:508) at hudson.model.Items.load(Items.java:327) at jenkins.model.Jenkins$18.run(Jenkins.java:2812) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:1009) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)On version 0.11, it fails to load Matrix configurations due to:Apr 24, 2016 3:35:30 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading job Automation_Matrix_Newjava.lang.IndexOutOfBoundsException: Index: 0, Size: 1 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.remove(ArrayList.java:492) at org.jvnet.hudson.plugins.exclusion.IdAllocator.getDescriptor(IdAllocator.java:173) at hudson.model.Descriptor.toMap(Descriptor.java:986) at hudson.util.DescribableList.toMap(DescribableList.java:151) at hudson.matrix.MatrixProject.getBuildWrappers(MatrixProject.java:812) at hudson.matrix.MatrixConfiguration.getBuildWrappers(MatrixConfiguration.java:358) at hudson.model.Project.createTransientActions(Project.java:257) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:755) at 

[JIRA] [exclusion-plugin] (JENKINS-34419) Exclusion Plugin on Matrix configuration

[manosn...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34419 
 
 
 
  Exclusion Plugin on Matrix configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Noam Manos 
 
 
 
 
 
 
 
 
 
 I've upgraded Jenkins to version 2.0 (!) and to Excusion Plugin 0.12.But now Exclusion plugins blocks my Matrix Multi job configurations.The definition inside the job is: SEMAPHORE_MATRIX_$ \ {NODE_NAME}  On Plugin version 0.12, it fails to load Matrix configurations due to:Apr 24, 2016 2:40:10 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading job Automation_Matrix_Newjava.lang.NullPointerException at org.jvnet.hudson.plugins.exclusion.IdAllocator.getDescriptor(IdAllocator.java:172) at hudson.model.Descriptor.toMap(Descriptor.java:986) at hudson.util.DescribableList.toMap(DescribableList.java:151) at hudson.matrix.MatrixProject.getBuildWrappers(MatrixProject.java:812) at hudson.matrix.MatrixConfiguration.getBuildWrappers(MatrixConfiguration.java:358) at hudson.model.Project.createTransientActions(Project.java:257) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:755) at hudson.matrix.MatrixConfiguration.updateTransientActions(MatrixConfiguration.java:141) at hudson.model.AbstractProject.onLoad(AbstractProject.java:339) at hudson.model.Project.onLoad(Project.java:98) at hudson.matrix.MatrixConfiguration.onLoad(MatrixConfiguration.java:97) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:573) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:580) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:580) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:617) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:508) at hudson.model.Items.load(Items.java:327) at jenkins.model.Jenkins$18.run(Jenkins.java:2812) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:1009) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)On version 0.11, it fails to load Matrix configurations due to:Apr 24, 2016 3:35:30 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading job Automation_Matrix_Newjava.lang.IndexOutOfBoundsException: Index: 0, Size: 1 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.remove(ArrayList.java:492) at org.jvnet.hudson.plugins.exclusion.IdAllocator.getDescriptor(IdAllocator.java:173) at hudson.model.Descriptor.toMap(Descriptor.java:986) at hudson.util.DescribableList.toMap(DescribableList.java:151) at hudson.matrix.MatrixProject.getBuildWrappers(MatrixProject.java:812) at hudson.matrix.MatrixConfiguration.getBuildWrappers(MatrixConfiguration.java:358) at hudson.model.Project.createTransientActions(Project.java:257) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:755) at 

[JIRA] [exclusion-plugin] (JENKINS-34419) Exclusion Plugin on Matrix configuration

[manosn...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34419 
 
 
 
  Exclusion Plugin on Matrix configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Noam Manos 
 
 
 
 
 
 
 
 
 
 I  had 've upgraded Jenkins  to  downgrade back to  version  2.  0  !But now Exclusion plugins blocks my Matrix Multi job configurations . 11, since on On Plugin version  0.12 , it fails to load  Matrix configurations  cannot load  due to:Apr 24, 2016 2:40:10 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading job Automation_Matrix_Newjava.lang.NullPointerException at org.jvnet.hudson.plugins.exclusion.IdAllocator.getDescriptor(IdAllocator.java:172) at hudson.model.Descriptor.toMap(Descriptor.java:986) at hudson.util.DescribableList.toMap(DescribableList.java:151) at hudson.matrix.MatrixProject.getBuildWrappers(MatrixProject.java:812) at hudson.matrix.MatrixConfiguration.getBuildWrappers(MatrixConfiguration.java:358) at hudson.model.Project.createTransientActions(Project.java:257) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:755) at hudson.matrix.MatrixConfiguration.updateTransientActions(MatrixConfiguration.java:141) at hudson.model.AbstractProject.onLoad(AbstractProject.java:339) at hudson.model.Project.onLoad(Project.java:98) at hudson.matrix.MatrixConfiguration.onLoad(MatrixConfiguration.java:97) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:573) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:580) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:580) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:617) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:508) at hudson.model.Items.load(Items.java:327) at jenkins.model.Jenkins$18.run(Jenkins.java:2812) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:1009) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) On version 0.11, it fails to load Matrix configurations due to:Apr 24, 2016 3:35:30 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading job Automation_Matrix_Newjava.lang.IndexOutOfBoundsException: Index: 0, Size: 1 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.remove(ArrayList.java:492) at org.jvnet.hudson.plugins.exclusion.IdAllocator.getDescriptor(IdAllocator.java:173) at hudson.model.Descriptor.toMap(Descriptor.java:986) at hudson.util.DescribableList.toMap(DescribableList.java:151) at hudson.matrix.MatrixProject.getBuildWrappers(MatrixProject.java:812) at hudson.matrix.MatrixConfiguration.getBuildWrappers(MatrixConfiguration.java:358) at hudson.model.Project.createTransientActions(Project.java:257) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:755) at hudson.matrix.MatrixConfiguration.updateTransientActions(MatrixConfiguration.java:141) at hudson.model.AbstractProject.onLoad(AbstractProject.java:339) at 

[JIRA] [exclusion-plugin] (JENKINS-34419) Exclusion Plugin on Matrix configuration

[manosn...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34419 
 
 
 
  Exclusion Plugin on Matrix configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Noam Manos 
 
 
 

Summary:
 
 Exclusion Plugin  0.12 failure  on Matrix configuration 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-34415) Broken backward compatibility

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in version 1.6.5 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34415 
 
 
 
  Broken backward compatibility  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-33687) BUILD_DISPLAY_NAME environment variable not updated

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in version 1.6.5 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33687 
 
 
 
  BUILD_DISPLAY_NAME environment variable not updated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-34195) NPE after upgrade to build-name-setter 1.6.0

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34195 
 
 
 
  NPE after upgrade to build-name-setter 1.6.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-34229) NPE

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34229 
 
 
 
  NPE  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [exclusion-plugin] (JENKINS-34419) Exclusion Plugin 0.12 failure on Matrix configuration

[manosn...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34419 
 
 
 
  Exclusion Plugin 0.12 failure on Matrix configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Noam Manos 
 
 
 

Priority:
 
 Minor Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [exclusion-plugin] (JENKINS-34419) Exclusion Plugin 0.12 failure on Matrix configuration

[manosn...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34419 
 
 
 
  Exclusion Plugin 0.12 failure on Matrix configuration  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 exclusion-plugin 
 
 
 

Created:
 

 2016/Apr/24 12:15 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Noam Manos 
 
 
 
 
 
 
 
 
 
 
I had to downgrade back to version 0.11, since on 0.12 Matrix configurations cannot load due to: 
Apr 24, 2016 2:40:10 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job Automation_Matrix_New java.lang.NullPointerException at org.jvnet.hudson.plugins.exclusion.IdAllocator.getDescriptor(IdAllocator.java:172) at hudson.model.Descriptor.toMap(Descriptor.java:986) at hudson.util.DescribableList.toMap(DescribableList.java:151) at hudson.matrix.MatrixProject.getBuildWrappers(MatrixProject.java:812) at hudson.matrix.MatrixConfiguration.getBuildWrappers(MatrixConfiguration.java:358) at hudson.model.Project.createTransientActions(Project.java:257) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:755) at hudson.matrix.MatrixConfiguration.updateTransientActions(MatrixConfiguration.java:141) at hudson.model.AbstractProject.onLoad(AbstractProject.java:339) at hudson.model.Project.onLoad(Project.java:98) at hudson.matrix.MatrixConfiguration.onLoad(MatrixConfiguration.java:97) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:573) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:580) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:580) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:617) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:508) at 

[JIRA] [exclusion-plugin] (JENKINS-32367) Exclusion list doesn't get updated when resources are removed

[manosn...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32367 
 
 
 
  Exclusion list doesn't get updated when resources are removed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Noam Manos 
 
 
 

Priority:
 
 Blocker Minor 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [exclusion-plugin] (JENKINS-32367) Exclusion list doesn't get updated when resources are removed

[manosn...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noam Manos updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32367 
 
 
 
  Exclusion list doesn't get updated when resources are removed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Noam Manos 
 
 
 

Priority:
 
 Minor Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [hp-quality-center-plugin] (JENKINS-34418) Implement User Defined Fields for Test Labs

[michaelfa...@me.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fazio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34418 
 
 
 
  Implement User Defined Fields for Test Labs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Michael Fazio 
 
 
 

Components:
 

 hp-quality-center-plugin 
 
 
 

Created:
 

 2016/Apr/24 9:44 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Michael Fazio 
 
 
 
 
 
 
 
 
 
 
User defined fields should be implemented for test labs. At the moment they only exist for test plans. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA 

[JIRA] [hp-quality-center-plugin] (JENKINS-34417) Skipped Unit Tests Not Mapped to QC Run Type

[michaelfa...@me.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Fazio created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34417 
 
 
 
  Skipped Unit Tests Not Mapped to QC Run Type  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Michael Fazio 
 
 
 

Components:
 

 hp-quality-center-plugin 
 
 
 

Created:
 

 2016/Apr/24 9:37 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Michael Fazio 
 
 
 
 
 
 
 
 
 
 
Skipped JUnit tests are reported as "failed" runs in QC run result. These should be mapped to either "Not Run" or "N/A". 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA 

[JIRA] [build-name-setter-plugin] (JENKINS-24277) BUILD_USER_ID not available for build-name-setter plugin.

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin started work on  JENKINS-24277 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-24277) BUILD_USER_ID not available for build-name-setter plugin.

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-24277 
 
 
 
  BUILD_USER_ID not available for build-name-setter plugin.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-24277) BUILD_USER_ID not available for build-name-setter plugin.

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin commented on  JENKINS-24277 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: BUILD_USER_ID not available for build-name-setter plugin.  
 
 
 
 
 
 
 
 
 
 
Damien Nozay please check if the bug still persists and let me know.  Also please provide more detailed description (reproduce steps including setting BUILD_USER_ID) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [buildgraph-view-plugin] (JENKINS-26111) jenkins1.588+buildgraph-view1.1.1 display empty

[pskumar...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Suresh Kumar closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26111 
 
 
 
  jenkins1.588+buildgraph-view1.1.1 display empty  
 
 
 
 
 
 
 
 
 

Change By:
 
 Suresh Kumar 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [buildgraph-view-plugin] (JENKINS-26111) jenkins1.588+buildgraph-view1.1.1 display empty

[pskumar...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Suresh Kumar assigned an issue to Julien Pivotto 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26111 
 
 
 
  jenkins1.588+buildgraph-view1.1.1 display empty  
 
 
 
 
 
 
 
 
 

Change By:
 
 Suresh Kumar 
 
 
 

Assignee:
 
 Julien Pivotto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-31681) Build Name Setter plugin doesn't depend on Token Macro properly

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31681 
 
 
 
  Build Name Setter plugin doesn't depend on Token Macro properly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [buildgraph-view-plugin] (JENKINS-26111) jenkins1.588+buildgraph-view1.1.1 display empty

[pskumar...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Suresh Kumar commented on  JENKINS-26111 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: jenkins1.588+buildgraph-view1.1.1 display empty  
 
 
 
 
 
 
 
 
 
 
Confliction with Prototype.js has been removed Do not conflict with prototype.js - 813017caf02dcbfd7874908e94cc3b9951b42b90 Merged this to main line and released in 1.2 version 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [buildgraph-view-plugin] (JENKINS-29416) Improve arrows in wrapping graph

[pskumar...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Suresh Kumar closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29416 
 
 
 
  Improve arrows in wrapping graph   
 
 
 
 
 
 
 
 
 

Change By:
 
 Suresh Kumar 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [buildgraph-view-plugin] (JENKINS-29416) Improve arrows in wrapping graph

[pskumar...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Suresh Kumar commented on  JENKINS-29416 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Improve arrows in wrapping graph   
 
 
 
 
 
 
 
 
 
 
Instead of wrapping build graph allowing graph to grow horizontally, Below is the commit against to the issue. Preventing wrapping of build graph - 8cc7b2491d606059e7d8d8425144edb0fe5814a9 Merged this to main line and released in 1.2 version 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [buildgraph-view-plugin] (JENKINS-29416) Improve arrows in wrapping graph

[pskumar...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Suresh Kumar assigned an issue to Clay Anderson 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29416 
 
 
 
  Improve arrows in wrapping graph   
 
 
 
 
 
 
 
 
 

Change By:
 
 Suresh Kumar 
 
 
 

Assignee:
 
 Clay Anderson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [buildgraph-view-plugin] (JENKINS-29779) Build dependency graph

[pskumar...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Suresh Kumar closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29779 
 
 
 
  Build dependency graph  
 
 
 
 
 
 
 
 
 

Change By:
 
 Suresh Kumar 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [buildgraph-view-plugin] (JENKINS-29779) Build dependency graph

[pskumar...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Suresh Kumar assigned an issue to Julien Pivotto 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29779 
 
 
 
  Build dependency graph  
 
 
 
 
 
 
 
 
 

Change By:
 
 Suresh Kumar 
 
 
 

Assignee:
 
 Julien Pivotto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [buildgraph-view-plugin] (JENKINS-29779) Build dependency graph

[pskumar...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Suresh Kumar commented on  JENKINS-29779 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build dependency graph  
 
 
 
 
 
 
 
 
 
 
Confliction with Prototype.js has been removed Do not conflict with prototype.js - 813017caf02dcbfd7874908e94cc3b9951b42b90 Merged this to main line and released in 1.2 version 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [workflow-plugin] (JENKINS-34416) workflow-cps-global-lib: global variables are not global singletons

[vehov...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Vehovsky updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34416 
 
 
 
  workflow-cps-global-lib: global variables are not global singletons  
 
 
 
 
 
 
 
 
 

Change By:
 
 Martin Vehovsky 
 
 
 
 
 
 
 
 
 
 Documentation says "Internally, scripts in the vars directory are instantiated as a singleton on-demand, when used first."Here is a very basic example to demonstrate it's not the case:{code:java}// vars/acme.groovydef setFoo(v) {this.foo = v;}def getFoo() {return this.foo;}{code}{code:java}//  src/  com/foo/Zot.groovypackage com.foodef printAcmeFoo() {try {echo acme.foo} catch (e){echo "acme.foo is undefined"}}{code}And here is a pipeline:{code:java}import com.foo.Zotnode{acme.foo = "5"echo acme.foo;Zot z = new Zot()z.printAcmeFoo()}{code}Actually it shows 2 issues:1/ scripts in the vars directory are not singletons2/ when accessing undefined field pipeline will hang indefinitely 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [workflow-plugin] (JENKINS-34416) workflow-cps-global-lib: global variables are not global singletons

[vehov...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Vehovsky updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34416 
 
 
 
  workflow-cps-global-lib: global variables are not global singletons  
 
 
 
 
 
 
 
 
 

Change By:
 
 Martin Vehovsky 
 
 
 
 
 
 
 
 
 
 Documentation says "Internally, scripts in the vars directory are instantiated as a singleton on-demand, when used first."Here is a very basic example to demonstrate it's not the case:{code:java}// vars/acme.groovydef setFoo(v) {this.foo = v;}def getFoo() {return this.foo;}{code}  { { code:java}  // com/foo/Zot.groovy  }}  {{ package com.foodef printAcmeFoo() {try {echo acme.foo} catch (e){echo "acme.foo is undefined"}} {code } } And here is a pipeline:{ { code:java} import com.foo.Zotnode{acme.foo = "5"echo acme.foo;Zot z = new Zot()z.printAcmeFoo()} {code } } Actually it shows 2 issues:1/ scripts in the vars directory are not singletons2/ when accessing undefined field pipeline will hang indefinitely 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [workflow-plugin] (JENKINS-34416) workflow-cps-global-lib: global variables are not global singletons

[vehov...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Vehovsky updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34416 
 
 
 
  workflow-cps-global-lib: global variables are not global singletons  
 
 
 
 
 
 
 
 
 

Change By:
 
 Martin Vehovsky 
 
 
 
 
 
 
 
 
 
 Documentation says "Internally, scripts in the vars directory are instantiated as a singleton on-demand, when used first."Here is a very basic example to demonstrate it's not the case:  { { code:java}  // vars/acme.groovy  }}  {{ def setFoo(v) {this.foo = v;}def getFoo() {return this.foo;} {code } } {{ // com/foo/Zot.groovy }}{{package com.foodef printAcmeFoo() {try {echo acme.foo} catch (e){echo "acme.foo is undefined"And here is a pipeline:{{import com.foo.Zotnode{acme.foo = "5"echo acme.foo;Zot z = new Zot()z.printAcmeFoo()}}}Actually it shows 2 issues:1/ scripts in the vars directory are not singletons2/ when accessing undefined field pipeline will hang indefinitely  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [workflow-plugin] (JENKINS-34416) workflow-cps-global-lib: global variables are not global singletons

[vehov...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Vehovsky created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34416 
 
 
 
  workflow-cps-global-lib: global variables are not global singletons  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/Apr/24 7:51 AM 
 
 
 

Environment:
 

 Tested on Jenkins docker images 1.642.4 / 2.0-beta-2 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Martin Vehovsky 
 
 
 
 
 
 
 
 
 
 
Documentation says "Internally, scripts in the vars directory are instantiated as a singleton on-demand, when used first." 
Here is a very basic example to demonstrate it's not the case: 
{{ // vars/acme.groovy }} {{ def setFoo(v)  { this.foo = v; } 
def getFoo()  { return this.foo; } 
}} 
{{ // com/foo/Zot.groovy }} {{ package com.foo 
def printAcmeFoo() { try  { echo acme.foo } 
 catch (e) { echo "acme.foo is undefined" } 
} }} 
And here is a pipeline: {{ import com.foo.Zot 
node { acme.foo = "5" echo acme.foo; Zot z = new Zot() z.printAcmeFoo() } 
}} 
 

[JIRA] [build-name-setter-plugin] (JENKINS-34415) Broken backward compatibility

[scm_issue_l...@java.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-34415 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Broken backward compatibility  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Leo Path: src/main/java/org/jenkinsci/plugins/buildnamesetter/BuildNameSetter.java http://jenkins-ci.org/commit/build-name-setter-plugin/bffcad21e26988e1142e9fa5ecb9d17008b0ee1b Log: Merge pull request #13 from jenkinsci/fix-backwards-compatibility 
Fix for bug JENKINS-34415 Broken backward compatibility 
Compare: https://github.com/jenkinsci/build-name-setter-plugin/compare/d449908f72f7...bffcad21e269 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-name-setter-plugin] (JENKINS-33167) Build Name Setter Plugin doesn't update the build name during the build

[leomich...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lev Mishin resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33167 
 
 
 
  Build Name Setter Plugin doesn't update the build name during the build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lev Mishin 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.