[JIRA] [copyartifact-plugin] (JENKINS-33257) "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts" with multi-configuration projects

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33257 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts" with multi-configuration projects  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java src/main/java/hudson/plugins/copyartifact/CopyArtifactPermissionProperty.java http://jenkins-ci.org/commit/copyartifact-plugin/1f34b2557f8bbf182e9cd97184685df364e8fff7 Log: Merge pull request #83 from ikedam/feature/

JENKINS-33257
_FixJavadoc 
Fix Javadoc issues introduced in 

JENKINS-33257
 
Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/9da068ef5495...1f34b2557f8b 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [copyartifact-plugin] (JENKINS-33578) Snippetizer broken for DownstreamBuildSelector with Jenkins Pipeline

2016-04-02 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-33578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Snippetizer broken for DownstreamBuildSelector with Jenkins Pipeline  
 
 
 
 
 
 
 
 
 
 


JENKINS-32526
 fixed the error, but it warns "Not Found" when you specified pipeline jobs for the upstream project. 
I found that DownstreamBuildSelector cannot pick builds related to pipeline jobs, as it depends on AbstractBuild#getUpstreamRelationshipBuild to detect relationships, which can be applicable only to `AbstractProject`. 
I'll add a change to display to warn that DownstreamBuildSelector is applicable only to AbstractProject for now. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [copyartifact-plugin] (JENKINS-33257) "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts" with multi-configuration projects

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33257 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts" with multi-configuration projects  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java src/main/java/hudson/plugins/copyartifact/CopyArtifactPermissionProperty.java http://jenkins-ci.org/commit/copyartifact-plugin/c86d948f2b4904bda17bae2ec1e11362686b7209 Log: Fix Javadoc issues introduced in 

JENKINS-33257
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [authorize-project-plugin] (JENKINS-33897) The adjunct passwordApiTokenSwitch is incorrectly referenced on the plugin

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33897 
 
 
 
  The adjunct passwordApiTokenSwitch is incorrectly referenced on the plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

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] [authorize-project-plugin] (JENKINS-33897) The adjunct passwordApiTokenSwitch is incorrectly referenced on the plugin

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33897 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The adjunct passwordApiTokenSwitch is incorrectly referenced on the plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: ikedam Path: src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/config.jelly http://jenkins-ci.org/commit/authorize-project-plugin/77c54781a48ae1dd32816b8d75e19023e6bdaab2 Log: Merge pull request #23 from fbelzunc/

JENKINS-33897
 
[FIXED JENKINS-33897] The adjunct passwordApiTokenSwitch is incorrectly referenced on the plugin 
Compare: https://github.com/jenkinsci/authorize-project-plugin/compare/a7a5ba0e5fcd...77c54781a48a 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [timestamper-plugin] (JENKINS-30143) logs for individual workflow steps do not contain timestamps

2016-04-02 Thread stevengbr...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven G Brown commented on  JENKINS-30143 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: logs for individual workflow steps do not contain timestamps  
 
 
 
 
 
 
 
 
 
 
Sorin Sbarnea, please feel welcome to add anything that is missing to the wiki. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27421) java.util.ArrayList$Itr is not Serializable

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27421 
 
 
 
  java.util.ArrayList$Itr is not Serializable  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

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] [workflow-plugin] (JENKINS-27421) java.util.ArrayList$Itr is not Serializable

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-27421 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.util.ArrayList$Itr is not Serializable  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/persistence/IteratorHack.java cps/src/test/java/org/jenkinsci/plugins/workflow/SerializationTest.java http://jenkins-ci.org/commit/workflow-plugin/a990468a828e64961eda24332673c9cb8835c629 Log: [FIXED JENKINS-27421] Producing a safe serialization replacement for ArrayList$Itr, 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27421) java.util.ArrayList$Itr is not Serializable

2016-04-02 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick started work on  JENKINS-27421 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

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] [workflow-plugin] (JENKINS-27421) java.util.ArrayList$Itr is not Serializable

2016-04-02 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated  JENKINS-27421 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27421 
 
 
 
  java.util.ArrayList$Itr is not Serializable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Reopened Open 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27421) java.util.ArrayList$Itr is not Serializable

2016-04-02 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Not in master yet, be patient JIRA link daemon… 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-27421 
 
 
 
  java.util.ArrayList$Itr is not Serializable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Resolution:
 
 Fixed 
 
 
 

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] [workflow-plugin] (JENKINS-27421) java.util.ArrayList$Itr is not Serializable

2016-04-02 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-27421 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.util.ArrayList$Itr is not Serializable  
 
 
 
 
 
 
 
 
 
 
Blocking at least the initially attempted use case from JENKINS-26481. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-33972) Item Categories should not be shipped from /categories

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33972 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Item Categories should not be shipped from /categories  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: recena Path: src/main/java/com/cloudbees/hudson/plugins/folder/FolderAddFilter.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/c3ba1ab0efab2552003752af46d659504b69c3e5 Log: 

JENKINS-33972
 View.doCategories was renamed to View.doItemCategories 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-33972) Item Categories should not be shipped from /categories

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33972 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Item Categories should not be shipped from /categories  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: http://jenkins-ci.org/commit/cloudbees-folder-plugin/ac521be9372a056a799c354e75f5ce33d516b7ff Log: Merge pull request #55 from recena/

JENKINS-33972
 


JENKINS-33972
 View.doCategories was renamed to View.doItemCategories 
Heck, merge them both, see if GitHub can handle it! 
Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/526694d36b9d...ac521be9372a 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-33972) Item Categories should not be shipped from /categories

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33972 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Item Categories should not be shipped from /categories  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/hudson/plugins/folder/FolderAddFilter.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/526694d36b9d2e0685ceac9c168204a209969b3d Log: Merge pull request #54 from jglick/itemCategories-

JENKINS-33972
 


JENKINS-33972
 View.doCategories renamed to doItemCategories 
#55 is identical, just merging the lower-numbered one. 
Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/6f2daf46be91...526694d36b9d 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-33972) Item Categories should not be shipped from /categories

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33972 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Item Categories should not be shipped from /categories  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/hudson/plugins/folder/FolderAddFilter.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/dab943292bcc6121c62701cb62307edce09c6d31 Log: 

JENKINS-33972
 View.doCategories renamed to doItemCategories. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-33971) WorkflowJob not reliably started from ReverseBuildTrigger after restart

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33971 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: WorkflowJob not reliably started from ReverseBuildTrigger after restart  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: job/src/test/java/org/jenkinsci/plugins/workflow/ReverseBuildTriggerTest.java http://jenkins-ci.org/commit/workflow-plugin/d2e726274b919aa3492d195dc75bf39711df7c2b Log: JENKINS-33971 Integration test for ReverseBuildTrigger.upstream2Trigger bug. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-33971) WorkflowJob not reliably started from ReverseBuildTrigger after restart

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33971 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: WorkflowJob not reliably started from ReverseBuildTrigger after restart  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: job/src/test/java/org/jenkinsci/plugins/workflow/ReverseBuildTriggerTest.java http://jenkins-ci.org/commit/workflow-plugin/ccac19edb8caeb4ab300fc5cce536f4410a85e45 Log: Merge pull request #374 from jglick/ReverseBuildTrigger-JENKINS-33971 
JENKINS-33971 Integration test for ReverseBuildTrigger.upstream2Trigger bug 
Compare: https://github.com/jenkinsci/workflow-plugin/compare/4b72d5eb9dee...ccac19edb8ca 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-22975) Exception parsing "implies" expression - Label.parseExpression("a->b")

2016-04-02 Thread ch...@orr.me.uk (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Orr commented on  JENKINS-22975 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Exception parsing "implies" _expression_ - Label.parseExpression("a->b")  
 
 
 
 
 
 
 
 
 
 
Related side-effect: when you enter windows -> x64 (i.e. with spaces, so that the config field does not complain), then you get the usual "Label is serviced by 3 nodes" message underneath the _expression_ field. 
However, clicking on this link leads to a URL with the canonical version of the _expression_ (i.e. with spaces stripped), so the URL looks like /label/windows->x64/ — this silently fails and shows a page with zero nodes. 
Changing the URL to have spaces in the _expression_, i.e. /label/windows%20->%20x64/ works as expected, and the three matching nodes (in this case) are shown as expected. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installed

2016-04-02 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33966 
 
 
 
  JAVA_HOME is not set when Maven is automatically installed  
 
 
 
 
 
 
 
 
 
 
Straightforward workaround present, therefore reducing priority. 
Also, could probably define JDK installations (with a defined path, doesn't need to be auto-installed), and reference those in the pipeline. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Priority:
 
 Critical 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] [core] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installed

2016-04-02 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-33966 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JAVA_HOME is not set when Maven is automatically installed  
 
 
 
 
 
 
 
 
 
 
Why not have Jenkins also install Java? 
Is Java on your PATH? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-29004) Build is running with wrong JDK Version

2016-04-02 Thread michael_gir...@choicehotels.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 michael giroux commented on  JENKINS-29004 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build is running with wrong JDK Version  
 
 
 
 
 
 
 
 
 
 
For more about toolchains see https://maven.apache.org/guides/mini/guide-using-toolchains.html 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-29004) Build is running with wrong JDK Version

2016-04-02 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-29004 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build is running with wrong JDK Version  
 
 
 
 
 
 
 
 
 
 

What about toolchains?
 
I've been told toolchains are the solution and should work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-29004) Build is running with wrong JDK Version

2016-04-02 Thread michael_gir...@choicehotels.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 michael giroux commented on  JENKINS-29004 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build is running with wrong JDK Version  
 
 
 
 
 
 
 
 
 
 
I want to be sure I understand what is being said. 
If we configure a Jenkins job as a maven project, the JDK used to run maven compiles must be at least JDK 1.7 required to run Jenkins. 
If we configure the job as a freestyle job, and execute a maven build step, the JDK used for the job may be JDK 1.6. 
What about toolchains? It seems that the whole point of maven toolchains is to allow maven-compiler-plugin to use a different JDK than the one running maven itself. Should we be able to configure the job as a maven project, building in JDK 1.7 or even 1.8, and using toolchains mechanism, specify the JDK 1.6 path for the maven-compiler-plugin? This seems like it should be the advice. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [bitbucket-plugin] (JENKINS-33989) Link to the bitbucket project on the sidebar + change links

2016-04-02 Thread jul...@rottenberg.info (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Julien R. created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33989 
 
 
 
  Link to the bitbucket project on the sidebar + change links  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 Screen Shot 2016-04-02 at 1.50.36 PM.png 
 
 
 

Components:
 

 bitbucket-plugin 
 
 
 

Created:
 

 2016/Apr/02 9:07 PM 
 
 
 

Labels:
 

 user-experience gui 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Julien R. 
 
 
 
 
 
 
 
 
 
 
Hello ! 
We've been using github for a while, part of the setup of a new job was to feed the job with 'Repository URL' and the 'GitHub project' fields. 
Out of the box once you had filled the 'GitHub project' field, you got a link on the job page (see screenshot) As an added bonus, all the links in the Changes page point to the actual diff in github, granted you left 'Repository browser' to Auto. 
The bitbucket plugin are missing those features, I can get the links for the diffs if I set 'Repository browser' with the right value (pick 

[JIRA] [workflow-plugin] (JENKINS-33719) PipelineScript from SCM does not support job parameters

2016-04-02 Thread pe...@peternijssen.nl (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Nijssen commented on  JENKINS-33719 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PipelineScript from SCM does not support job parameters  
 
 
 
 
 
 
 
 
 
 
I just want to confirm that I am also unable to use job parameters within the SCM. (Git in my 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] [git-parameter-plugin] (JENKINS-33963) Branch filter does not save the value

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33963 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Branch filter does not save the value  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Boguslaw Klimas Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition/config.jelly src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition/help-branchFilter.html src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition/help-branchfilter.html src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition/help-sortMode.html src/test/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinitionTest.java http://jenkins-ci.org/commit/git-parameter-plugin/d4585faf4584b028f0fc33b01d57652388b10d86 Log: Merge pull request #19 from jenkinsci/bugfix/

JENKINS-33963
 


JENKINS-33963
 
Compare: https://github.com/jenkinsci/git-parameter-plugin/compare/9a867652bf56...d4585faf4584 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-parameter-plugin] (JENKINS-33963) Branch filter does not save the value

2016-04-02 Thread klim...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Boguslaw Klimas resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33963 
 
 
 
  Branch filter does not save the value  
 
 
 
 
 
 
 
 
 

Change By:
 
 Boguslaw Klimas 
 
 
 

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] [git-parameter-plugin] (JENKINS-33963) Branch filter does not save the value

2016-04-02 Thread klim...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Boguslaw Klimas started work on  JENKINS-33963 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Boguslaw Klimas 
 
 
 

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] [git-parameter-plugin] (JENKINS-33963) Branch filter does not save the value

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33963 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Branch filter does not save the value  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: klimas7 Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition/config.jelly src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition/help-branchFilter.html src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition/help-branchfilter.html src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition/help-sortMode.html src/test/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinitionTest.java http://jenkins-ci.org/commit/git-parameter-plugin/e4401dccac9b255366b90dd97ad0a0975c22fb7c Log: JENKINS-33963 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [deployment-notification-plugin] (JENKINS-33988) Inject deployment env variables in the build

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33988 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Inject deployment env variables in the build  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/org/jenkinsci/plugins/deployment/DeploymentTrigger.java src/main/java/org/jenkinsci/plugins/deployment/HostRecords.java src/main/resources/org/jenkinsci/plugins/deployment/DeploymentTrigger/help.html http://jenkins-ci.org/commit/deployment-notification-plugin/63a9cd8ea6fa4bd8c3d21c65197ba65d2e1a052a Log: Inject deployment env variables in the build 
[FIXED JENKINS-33988] Inject deployment env variables in the build 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [deployment-notification-plugin] (JENKINS-33988) Inject deployment env variables in the build

2016-04-02 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33988 
 
 
 
  Inject deployment env variables in the build  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

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] [deployment-notification-plugin] (JENKINS-33988) Inject deployment env variables in the build

2016-04-02 Thread fbelz...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Félix Belzunce Arcos started work on  JENKINS-33988 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Félix Belzunce Arcos 
 
 
 

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] [deployment-notification-plugin] (JENKINS-33988) Inject deployment env variables in the build

2016-04-02 Thread fbelz...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Félix Belzunce Arcos updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33988 
 
 
 
  Inject deployment env variables in the build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Félix Belzunce Arcos 
 
 
 

URL:
 
 https://github.com/jenkinsci/deployment-notification-plugin/pull/2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [deployment-notification-plugin] (JENKINS-33988) Inject deployment env variables in the build

2016-04-02 Thread fbelz...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Félix Belzunce Arcos created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33988 
 
 
 
  Inject deployment env variables in the build  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Félix Belzunce Arcos 
 
 
 

Components:
 

 deployment-notification-plugin 
 
 
 

Created:
 

 2016/Apr/02 7:20 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Félix Belzunce Arcos 
 
 
 
 
 
 
 
 
 
 
This enhancement should allow users to have the environment variables below on their builds. In this way, they can know for example which environment and what was the path which triggered the build. 
envVars.put("DEPLOYMENT_ENV", StringUtils.join(deploymentHost, ",")); env.put("DEPLOYMENT_HOST", hostRecord.getHost()); env.put("DEPLOYMENT_PATH", hostRecord.getPath()); env.put("DEPLOYMENT_TIMESTAMP", hostRecord.getTimestampString()); 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
  

[JIRA] [clearcase-plugin] (JENKINS-32551) Pipeline script from SCM: ClearCase not available

2016-04-02 Thread george.b...@bmo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 George Bell commented on  JENKINS-32551 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline script from SCM: ClearCase not available  
 
 
 
 
 
 
 
 
 
 
Would love if the clearcase plugins could be updated for pipeline, currently get an error when saving a multibranch pipeline project with clearcase set as the scm. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [credentials-binding-plugin] (JENKINS-29581) Error when binding credentials to a job

2016-04-02 Thread niall.crow...@salesforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Niall Crowley resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fix: Installed Credentials Binding 1.7 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29581 
 
 
 
  Error when binding credentials to a job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Niall Crowley 
 
 
 

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] [credentials-binding-plugin] (JENKINS-29581) Error when binding credentials to a job

2016-04-02 Thread niall.crow...@salesforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Niall Crowley commented on  JENKINS-29581 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error when binding credentials to a job  
 
 
 
 
 
 
 
 
 
 
I was still getting this error during the week. 
Upgraded Credentials Binding Plugin 1.4 to 1.7 and the error went away. 
Jenkins 1.625.3 Credentials Plugin 1.26 Credentials Binding 1.7 
I'm going to mark this Resolved. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-31258) Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins

2016-04-02 Thread apr...@tibco.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Price commented on  JENKINS-31258 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins  
 
 
 
 
 
 
 
 
 
 
Arnaud, I documented the new Maven property and related matters (see the new paragraph headed 'Maven Surefire Test Results') on Mar 02, 2016 10:12. 
 
 
 
 
 
 
 
 
 
 
 
 

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

2016-04-02 Thread wi...@ceilfors.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wisen Tanasa updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33986 
 
 
 
  Get an Exception in Jenkins log while configuring a build job with Jira trigger  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wisen Tanasa 
 
 
 
 
 
 
 
 
 
 Get  folloiwng  following  exception while trying to setup Job for Jira trigger {code} Apr 01, 2016 8:07:55 PM WARNING hudson.model.Descriptor$NewInstanceBindInterceptor onConvertfalling back to default instantiation com.ceilfors.jenkins.plugins.jiratrigger.changelog.ChangelogMatcher {"field":"status","comparingNewValue":true,"newValue":"APPROVED FOR RELEASE","comparingOldValue":false,"oldValue":"","stapler-class":"com.ceilfors.jenkins.plugins.jiratrigger.changelog.JiraFieldChangelogMatcher","$class":"com.ceilfors.jenkins.plugins.jiratrigger.changelog.JiraFieldChangelogMatcher"}java.lang.NullPointerException at hudson.model.Descriptor$NewInstanceBindInterceptor.onConvert(Descriptor.java:663) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:543) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:647) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:404) at org.kohsuke.stapler.RequestImpl.injectSetters(RequestImpl.java:738) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:703) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:81) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:600) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:404) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:400) at hudson.model.Descriptor.newInstance(Descriptor.java:588) at hudson.model.AbstractProject.buildDescribable(AbstractProject.java:1890) at hudson.model.AbstractProject.submit(AbstractProject.java:1868) at hudson.model.Project.submit(Project.java:230) at hudson.model.Job.doConfigSubmit(Job.java:1225) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:795) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at 

[JIRA] [jira-trigger-plugin] (JENKINS-33986) Get an Exception in Jenkins log while configuring a build job with Jira trigger

2016-04-02 Thread wi...@ceilfors.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wisen Tanasa commented on  JENKINS-33986 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Get an Exception in Jenkins log while configuring a build job with Jira trigger  
 
 
 
 
 
 
 
 
 
 
Thanks for reporting this. May I know if the exception is affecting the functionality of the plugin or it's just a warning? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.