[JIRA] [build-failure-analyzer-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

[damien.corabo...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-32331 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Performance problems on scan on huge Jenkins instances  
 
 
 
 
 
 
 
 
 
 
Since the org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro#evaluate(hudson.model.AbstractBuild, hudson.model.TaskListener, java.lang.String, java.util.Map, com.google.common.collect.ListMultimap) method is synchronised (since version 1.11), we have indeed a bottleneck when several builds need to resolve the token.  
It seems to be necessary because this class has some instance variables and cannot be shared between different threads. 
So in the end, this seems more a problem with the token-macro plugin than with the BFA or the email-ext plugin. I'll go and see if there is already an issue about this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs

[nikolay.v.borise...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nikolay Borisenko commented on  JENKINS-32402 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs  
 
 
 
 
 
 
 
 
 
 
I am using "Role Strategy" plugin. The issue is not reproducible only if "Anonymous" has access to configure 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/b42f2937c1f91bfd521e00650cbee38cd565c6ba Log: JENKINS-28881 - Direct unit test for the issue discovered with folders (JENKINS-32359) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32218) buildsByBranchName is not set anymore

[a...@nederlof.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Nederlof commented on  JENKINS-32218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: buildsByBranchName is not set anymore  
 
 
 
 
 
 
 
 
 
 
Thanks Mark! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [subversion-plugin] (JENKINS-32732) Using unix server every time build fail through SVN

[ty...@monkeypox.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R. Tyler Croy moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32732 
 
 
 
  Using unix server every time build fail through SVN   
 
 
 
 
 
 
 
 
 

Change By:
 
 R. Tyler Croy 
 
 
 

Project:
 
 Infrastructure Jenkins 
 
 
 

Key:
 
 INFRA JENKINS - 554 32732 
 
 
 

Workflow:
 
 classic default workflow JNJira 
 
 
 

Component/s:
 
 subversion-plugin 
 
 
 

Component/s:
 
 svn 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

[JIRA] [subversion-plugin] (JENKINS-32732) Using unix server every time build fail through SVN

[ty...@monkeypox.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R. Tyler Croy assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32732 
 
 
 
  Using unix server every time build fail through SVN   
 
 
 
 
 
 
 
 
 

Change By:
 
 R. Tyler Croy 
 
 
 

Assignee:
 
 R. Tyler Croy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [publish-over-ssh-plugin] (JENKINS-32733) Publish over SSH plugin doesn't preserve permissions

[dg...@cray.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Gloe created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32733 
 
 
 
  Publish over SSH plugin doesn't preserve permissions  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 bap 
 
 
 

Components:
 

 publish-over-ssh-plugin 
 
 
 

Created:
 

 02/Feb/16 7:24 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 David Gloe 
 
 
 
 
 
 
 
 
 
 
The publish over SSH plugin isn't preserving executable permission for some scripts I would like to copy and run on a remote server. This is on Jenkins version 1.623. 
The remote server is on OpenSUSE 13.2, the Jenkins server is CentOS 7.1. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
  

[JIRA] [p4-plugin] (JENKINS-25145) Version Jenkins Configuration In Perforce

[p...@adobe.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jim Poje commented on  JENKINS-25145 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Version Jenkins Configuration In Perforce   
 
 
 
 
 
 
 
 
 
 
Current code for this functionality crashes for me. I do not see a mechanism to disable this feature entirely, so supplying empty values causes the crash. 
{{Jan 26, 2016 3:13:36 PM hudson.model.listeners.SaveableListener fireOnChange WARNING: null java.lang.NullPointerException at org.jenkinsci.plugins.p4.ConfigurationListener.onChange(ConfigurationListener.java:38) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at hudson.model.ComputerSet$1.save(ComputerSet.java:82) at hudson.util.PersistedList.onModified(PersistedList.java:173)}} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32735 
 
 
 
  Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency  
 
 
 
 
 
 
 
 
 

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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/ownership/folders/FolderItemListener.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipActionFactory.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderItemListener.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipActionFactory.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipProperty.java src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/index.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipDescriptionSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/index.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipDescriptionSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipProperty/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipProperty/summary.jelly src/test/java/com/synopsys/arc/jenkins/plugins/ownership/wrappers/OwnershipBuildWrapperTest.java src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipHelperTest.java src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipTest.java src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelperTest.java src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java src/test/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipActionTest.java src/test/java/org/jenkinsci/plugins/ownership/security/rolestrategy/OwnershipBasedSecurityTest.java http://jenkins-ci.org/commit/ownership-plugin/e5039a9220b6718501a5aa40c5e1d9a394c3426e Log: JENKINS-28881 - Move Folder files. Folders belong to the model 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
  

[JIRA] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipDescription.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPluginConfiguration.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/extensions/item_ownership_policy/AssignCreatorPolicy.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/ComputerOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerPropertyHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/security/rolestrategy/AbstractOwnershipRoleMacro.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/AbstractOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/config/InheritanceOptions.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipHelperLocator.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipInfo.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderItemListener.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipActionFactory.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipProperty.java src/main/java/org/jenkinsci/plugins/ownership/model/jobs/JobOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/nodes/NodeOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipHelper.java src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/ownershipSource.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/ownershipSource.properties src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/propertyConfig.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPlugin/propertyConfig.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPluginConfiguration/config.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobAction/manage-owners.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobAction/propertyConfig.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnershipAction/manage-owners.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnershipAction/propertyConfig.jelly src/main/resources/org/jenkinsci/plugins/ownership/config/InheritanceOptions/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/config/InheritanceOptions/help-blockInheritanceFromItemGroups.html src/main/resources/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource/DisabledSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource/DisabledSource/summary.properties src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/index.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/summary.jelly 

[JIRA] [cloudbees-folder-plugin] (JENKINS-32359) Folders do not always persist assigned folder properties

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

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

 
 
 
 
 
 
 
  Re: Folders do not always persist assigned folder properties  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/b42f2937c1f91bfd521e00650cbee38cd565c6ba Log: JENKINS-28881 - Direct unit test for the issue discovered with folders (JENKINS-32359) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPluginConfiguration.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/org/jenkinsci/plugins/ownership/config/InheritanceOptions.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelper.java src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPluginConfiguration/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/config/InheritanceOptions/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/config/InheritanceOptions/help-blockInheritanceFromItemGroups.html src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java src/test/java/org/jenkinsci/plugins/ownership/test/util/OwnershipPluginConfigurer.java http://jenkins-ci.org/commit/ownership-plugin/3589ce8e035701e42b8aeb926d84df59f3b68967 Log: JENKINS-28881 - Allow blocking ItemGroup inheritance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cloudbees-folder-plugin] (JENKINS-32359) Folders do not always persist assigned folder properties

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

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

 
 
 
 
 
 
 
  Re: Folders do not always persist assigned folder properties  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/a188d3e4e76465b01eeac99deae2188ca470853b Log: JENKINS-28881 - Disable the JENKINS-32359 unit test till the CloudBees Folders Plugin gets released 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/a188d3e4e76465b01eeac99deae2188ca470853b Log: JENKINS-28881 - Disable the JENKINS-32359 unit test till the CloudBees Folders Plugin gets released 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/security/jobrestrictions/OwnersListJobRestrictionTest.java http://jenkins-ci.org/commit/ownership-plugin/8d1fd0e36e7d36397708c2a657f6803ec3259bff Log: JENKINS-28881 - Tests of the JobRestrictions integration 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/security/rolestrategy/OwnershipBasedSecurityTest.java src/test/java/org/jenkinsci/plugins/ownership/security/rolestrategy/OwnershipBasedSecurityTestHelper.java http://jenkins-ci.org/commit/ownership-plugin/535baec000a54decbd214ba6a3206f28f4736e34 Log: JENKINS-28881 - Add unit tests for Ownership-based security 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps

[p...@adobe.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jim Poje commented on  JENKINS-24591 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to run perforce commands within build steps  
 
 
 
 
 
 
 
 
 
 
Exposing the P4_TICKET value is a security risk, since the ticket value is essentially a credential value with access to a perforce server. In conjunction with the exported P4_USER and P4_PORT values, anyone with the ticket value has all the access to the perforce server that is granted to the P4_USER. Passing such a ticket value, in clear text, as an environment variable poses too great a risk. 
Let me request that the P4_TICKET environment variable be entirely removed, as passing credential values in environment variables is simply a very bad practice. 
If there is severe pushback to this request, a solution that allows the P4_TICKET environment to be conditionally set – with a default setting that disables it – could be considered as a less desirable alternative. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps

[p...@adobe.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jim Poje reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Re-open to remove P4_TICKET environment variable 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-24591 
 
 
 
  Unable to run perforce commands within build steps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jim Poje 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed 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] [core] (JENKINS-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-32735 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency  
 
 
 
 
 
 
 
 
 
 
I suspect that without Git SCM, you probably aren't making many remote file system calls, or are making different types of remote file system calls. My first hunch is that the issue is somehow in your choice of virtual machine on the swarm client side, or possibly an unexpected incompatibility between your Jenkins version and the swarm client version you're using. I'm not a big user of swarm clients, but I have a few, and they run git just fine. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-client-plugin] (JENKINS-32712) Job with Git polling "succeeds" with "no changes" although the Git polling failed

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32712 
 
 
 
  Job with Git polling "succeeds" with "no changes" although the Git polling failed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Assignee:
 
 Nicolas De Loof 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction.java src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/summary.jelly http://jenkins-ci.org/commit/ownership-plugin/f5357c99c4f98e553d63d9f98b920cf833abbd76 Log: JENKINS-28881 - Display Ownership summary boxes for Folders 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipHelperLocator.java src/test/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelperTest.java http://jenkins-ci.org/commit/ownership-plugin/4afd8a3cdc3d96c3885340112a13144f74742b77 Log: JENKINS-28881 - Add OwnershipHelperLocator extension point 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/OwnershipActionFactory.java src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/ownershipSource.properties http://jenkins-ci.org/commit/ownership-plugin/6302e837890622d69b99a7534cf1b5523afd96c4 Log: JENKINS-28881 - Amend ownershipSource warning message according to comments from @olivergondza 
Also fixes minor formatting issues 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipDescription.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipHelper.java src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipHelperTest.java src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/8207da507ed68942bb98af1f648e16e671165f6a Log: JENKINS-28881 - Support inheritance of Ownership info from folders 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/test/java/com/synopsys/arc/jenkins/plugins/ownership/wrappers/OwnershipBuildWrapperTest.java src/test/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipActionTest.java http://jenkins-ci.org/commit/ownership-plugin/1e3e70fb08a59ca70359fd22379c98f13c7b5745 Log: JENKINS-28881 - Add Folder ownership tests for Run components 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/extensions/item_ownership_policy/AssignCreatorPolicy.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderItemListener.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty.java src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/206a36c085f35c2a06966af6aca6ea8f80772bc3 Log: JENKINS-28881 - Support AssignCreatorPolicy for Folders 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/ComputerOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerPropertyHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/AbstractOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipHelperLocator.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipInfo.java src/main/java/org/jenkinsci/plugins/ownership/model/jobs/JobOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/nodes/NodeOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipHelper.java src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/ownershipSource.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/ownershipSource.properties src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobAction/manage-owners.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipDescriptionSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource/DisabledSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource/DisabledSource/summary.properties src/main/resources/org/jenkinsci/plugins/ownership/model/jobs/JobOwnershipDescriptionSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/nodes/NodeOwnershipDescriptionSource/summary.jelly src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/cd1568f63f2c1480a0b57c69768ae19eb824c521 Log: JENKINS-28881 - Extend the internal implementation to allow displaying the ownership info source 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

   

[JIRA] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty.java http://jenkins-ci.org/commit/ownership-plugin/0be133350496b89778cb0434e05ababccfb4cea3 Log: JENKINS-28881 - Prevent FolderOwnershipProperty changes on the configuration submission 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/security/rolestrategy/AbstractOwnershipRoleMacro.java src/main/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipHelper.java http://jenkins-ci.org/commit/ownership-plugin/74b81be6cf8d5197abf8dc03e8bdf9984c7589a2 Log: JENKINS-28881 - Fix several issues with explicit JobOwnerProperty usage impacting the inheritance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin

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

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

 
 
 
 
 
 
 
  Re: Add support for CloudBees folder plugin  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/OwnershipActionFactory.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipActionFactory.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty.java src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/propertyConfig.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/index.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty/summary.jelly src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/1458f9358784c43f1369fa53e4c66722873f3b16 Log: JENKINS-28881 - Implementation of Ownership property injection 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [token-macro-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

[damien.corabo...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-32331 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Performance problems on scan on huge Jenkins instances  
 
 
 
 
 
 
 
 
 
 
Moving this issue to the token-macro-plugin component. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-32735 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency  
 
 
 
 
 
 
 
 
 
 
I don't think the "class not found" message is related to the git plugin, other than the fact that the git plugin is trying to make a remote call. I've assigned this to core in hopes someone on core can assist. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency

[jenkins-j...@shirley.im (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jay Shirley commented on  JENKINS-32735 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency  
 
 
 
 
 
 
 
 
 
 
Thanks Mark! 
To be clear, if I disable the Git SCM and put in a build script to fetch from Git everything is fine. This behavior only starts if the project is configured to use the Git SCM. It also doesn't seem to occur if I use the same configuration in a local Vagrant image that doesn't use Swarm… but that's not testing the same behavior, so not too relevant. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [token-macro-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

[damien.corabo...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-32331 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Performance problems on scan on huge Jenkins instances  
 
 
 
 
 
 
 
 
 
 
I've created the https://github.com/jenkinsci/token-macro-plugin/pull/21 pull request in an attempt to solve this bottleneck issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maninder Singh edited a comment on  JENKINS-28652 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary  
 
 
 
 
 
 
 
 
 
 I have upgraded Jenkins to use latest version 2.0.1 and started getting 0% coverage even thought I can see coverage.ec file have classes that have been covered. Also even though I am using "0.7.5.201505241946" in my android build.gradle  Using Jenkins 1.628 . Surprised that I dit not have a problem with build.gradle using "0.7.5.201505241946" with Jenkins Plugin 1.0.19 Can someone please help me. I have to downgrade  the  my machine to  plugin  1.0.19  for now.     Which is working totally fine. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maninder Singh edited a comment on  JENKINS-28652 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary  
 
 
 
 
 
 
 
 
 
 I have upgraded Jenkins to use latest version 2.0.1 and started getting 0% coverage even thought I can see coverage.ec file have classes that have been covered. Also even though I am using "0.7.5.201505241946" in my android build.gradle     Using Jenkins 1.628 Can someone please help me. I have to downgrade the plugin 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] [core] (JENKINS-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32735 
 
 
 
  Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 git-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)

[jurgen...@yahoo.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jurgezero assigned an issue to Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31406 
 
 
 
  Promotion Status shows an excess of whitespace (missed one)  
 
 
 
 
 
 
 
 
 

Change By:
 
 jurgezero 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)

[jurgen...@yahoo.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jurgezero assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31406 
 
 
 
  Promotion Status shows an excess of whitespace (missed one)  
 
 
 
 
 
 
 
 
 

Change By:
 
 jurgezero 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32630) Branches to build does not take into account which branch is most recent

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-32630 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Branches to build does not take into account which branch is most recent  
 
 
 
 
 
 
 
 
 
 
Yes, I'm quite willing to accept proposed improvements to the help. Changing help has very little risk of regressing functionality, and may improve the experience for users that read it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [next-build-number-plugin] (JENKINS-27958) Cannot reset the next build number

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maninder Singh closed an issue as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Cannot reproduce 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-27958 
 
 
 
  Cannot reset the next build number  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maninder Singh 
 
 
 

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] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-31406 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Promotion Status shows an excess of whitespace (missed one)  
 
 
 
 
 
 
 
 
 
 
I do not commit to fix it soon. Too many high-priority tasks in the queue, the priority of this one is "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] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev assigned an issue to Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31406 
 
 
 
  Promotion Status shows an excess of whitespace (missed one)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [next-build-number-plugin] (JENKINS-27958) Cannot reset the next build number

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maninder Singh resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27958 
 
 
 
  Cannot reset the next build number  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maninder Singh 
 
 
 

Status:
 
 Reopened 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] [versionnumber-plugin] (JENKINS-32736) Ability to support simple arithmetic with the build version number

[rami.abughaza...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rami Abughazaleh created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32736 
 
 
 
  Ability to support simple arithmetic with the build version number  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 versionnumber-plugin 
 
 
 

Created:
 

 02/Feb/16 10:28 PM 
 
 
 

Environment:
 

 Jenkins 1.646  Version Number Plug-In v1.6 
 
 
 

Labels:
 

 plugins 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Rami Abughazaleh 
 
 
 
 
 
 
 
 
 
 
Thank you for the versionnumber Jenkins plugin. 
I would like the versionnumber Jenkins plugin to support simple arithmetic to calculate the build version number. 
An example version number format string: 1.0.(1200 * $ {YEARS_SINCE_PROJECT_START} 
) + $ {BUILD_MONTH, X} 
$ {BUILD_DAY, XX} 
.$ {BUILDS_TODAY, X} 
In this way, if my project started in 2015, the last build in that year would have a version 

[JIRA] [versionnumber-plugin] (JENKINS-32736) Ability to support simple arithmetic with the build version number

[rami.abughaza...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rami Abughazaleh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32736 
 
 
 
  Ability to support simple arithmetic with the build version number  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rami Abughazaleh 
 
 
 
 
 
 
 
 
 
 Thank you for the versionnumber Jenkins plugin.I would like the versionnumber Jenkins plugin to support simple arithmetic to calculate the build version number.An example version number format string: {code:java} 1.0.(1200 * ${YEARS_SINCE_PROJECT_START}) + ${BUILD_MONTH, X}${BUILD_DAY, XX}.${BUILDS_TODAY, X} {code}   In this way, if my project started in 2015, the last build in that year would have a version number of 1.0.1231.1 for example.And then instead of having to increment the minor version number, the next build in the new year would be 1.0.1301.1 for example.It doesn't seem that the plugin currently supports this.Thank you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5150) Race condition for feature "Block build when upstream project is building"

[dtho...@osrfoundation.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dirk Thomas commented on  JENKINS-5150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Race condition for feature "Block build when upstream project is building"  
 
 
 
 
 
 
 
 
 
 
I think we have the same problem with the current LTS 1.642.1. 
Please see the detailed description of our case: https://github.com/ros-infrastructure/ros_buildfarm/pull/194 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [performance-plugin] (JENKINS-28284) Images for Test Case trends is broken and generate exception

[hellcomestot...@hotmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zhenya Frolov commented on  JENKINS-28284 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Images for Test Case trends is broken and generate exception  
 
 
 
 
 
 
 
 
 
 
Thanks for the followup, dave davejenk. Unfortunately, we had config issues when trying the 1.14 build and other issues came up, which put this on the backburner. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32731) Allow plugins to contribute to Pipeline global library

[michael.ne...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale commented on  JENKINS-32731 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow plugins to contribute to Pipeline global library  
 
 
 
 
 
 
 
 
 
 
The only real problem I can forsee is that the names of DSL files in the global lib are, well, global.  
eg:  
builg.groovy is used as  
build  { .. } 
In the script. If you install 2 plugins that each want to have a build.groovy - how is the conflict resolved? will the second one they install fail?  (I fear to suggest qualified imports as that kind of harshes the vibe, but some way to resolve this may be warranted).  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [pagerduty-plugin] (JENKINS-32738) on success, the plugin should resolve the issue

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Gray created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32738 
 
 
 
  on success, the plugin should resolve the issue  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Alexander Leibzon 
 
 
 

Components:
 

 pagerduty-plugin 
 
 
 

Created:
 

 03/Feb/16 12:50 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Alex Gray 
 
 
 
 
 
 
 
 
 
 
It would be so cool if the plugin would auto-resolve the pager duty alert when a build passes. 
I think it would be a good enhancement to add to this plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

   

[JIRA] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wenzheng Jiang created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32739 
 
 
 
  Unable to export path in matrix jobs.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Attachments:
 

 2.png 
 
 
 

Components:
 

 customtools-plugin 
 
 
 

Created:
 

 03/Feb/16 1:12 AM 
 
 
 

Environment:
 

 Jenkins 1.646  Custom Tools Plugin 0.4.4 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Wenzheng Jiang 
 
 
 
 
 
 
 
 
 
 
When using customTools plugin, I export the installation path by putting them in "Exported paths". But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs.  
 
 
 
 
 
 
 
 
 
 
 
 

 
   

[JIRA] [performance-plugin] (JENKINS-28284) Images for Test Case trends is broken and generate exception

[david.r...@businesswire.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dave davejenk commented on  JENKINS-28284 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Images for Test Case trends is broken and generate exception  
 
 
 
 
 
 
 
 
 
 
Reverting to 1.11 fixed our problem (linus jenkins 1.637). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-30353) Add perforce-plugin-style nodename hash to workspace environment variables expansion

[p_hamp...@wargaming.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul "TBBle" Hampson commented on  JENKINS-30353 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add perforce-plugin-style nodename hash to workspace environment variables expansion  
 
 
 
 
 
 
 
 
 
 
If anyone else hits this issue, we're working around it locally with the following Groovy script, run before the SCM as a 'Execute system Groovy script' step: 

 

// Work around https://issues.jenkins-ci.org/browse/JENKINS-30353
import hudson.model.*

def pa = new ParametersAction([
  new StringParameterValue("NODE_NAME_HASH", String.valueOf(Thread.currentThread().executable.getBuiltOn().hashCode()))
])

// add variable to current job
Thread.currentThread().executable.addAction(pa)
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maninder Singh reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I have upgraded Jenkins to use latest version 2.0.1 and started getting 0% coverage even thought I can see coverage.ec file have classes that have been covered. Also even though I am using "0.7.5.201505241946" in my android build.gradle  Can someone please help me. I have to downgrade the plugin for now.  
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28652 
 
 
 
  JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maninder Singh 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed 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] [hp-application-automation-tools-plugin] (JENKINS-32734) Please document that this plugin is Windows-only.

[rvinc...@prokarma.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Vincent created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32734 
 
 
 
  Please document that this plugin is Windows-only.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Ofir Shaked 
 
 
 

Components:
 

 hp-application-automation-tools-plugin 
 
 
 

Created:
 

 02/Feb/16 7:27 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Robert Vincent 
 
 
 
 
 
 
 
 
 
 
I have discovered that the hp-application-automation-tools-plugin requires Windows, as it deploys and attempts to run a Windows 32-bit executable. 
I would suggest that "win32" be added to the [Prerequisites list](https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools#HPApplicationAutomationTools-UserGuide) on the [plugin page](https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

[JIRA] [git-plugin] (JENKINS-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency

[jenkins-j...@shirley.im (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jay Shirley created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32735 
 
 
 
  Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 

Attachments:
 

 consoleText.txt 
 
 
 

Components:
 

 git-plugin 
 
 
 

Created:
 

 02/Feb/16 7:39 PM 
 
 
 

Environment:
 

 Jenkins 1.646, Git Plugin 2.4.1, Git client plugin 1.19.2; Ubuntu 14.04.1  java 1.7.0 p95, OpenJDK 7u95-2.6.4-0 64-bit build 24.95-b01, mixed mode  
 
 
 

Labels:
 

 plugin git-plugin swarm git-client 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Jay Shirley 
 
 
 
 
 
 
 
 
 
 
We are moving from a custom script to the Git SCM. Our previous script works fine, connecting to the remote agent and executing the script. The Git SCM errors out immediately, upon creating the git 

[JIRA] [core] (JENKINS-20327) “Form too large” errors submitting view configurations with many jobs

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-20327 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: “Form too large” errors submitting view configurations with many jobs  
 
 
 
 
 
 
 
 
 
 
Not a candidate for 1.642 based LTS as it was fixed in 1.639. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-20327) “Form too large” errors submitting view configurations with many jobs

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-20327 
 
 
 
  “Form too large” errors submitting view configurations with many jobs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oliver Gondža 
 
 
 

Labels:
 
 jetty  lts-candidate  performance view 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31219) A CloudProvisioningListener can prevent provisioning of all clouds instead of just the targeted cloud

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31219 
 
 
 
  A CloudProvisioningListener can prevent provisioning of all clouds instead of just the targeted cloud  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oliver Gondža 
 
 
 

Labels:
 
 lts 1.642.2 - candidate 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wenzheng Jiang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32739 
 
 
 
  Unable to export path in matrix jobs.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wenzheng Jiang 
 
 
 

Environment:
 
 Jenkins 1.646 Custom Tools Plugin 0.4.4 Matrix Project Plugin 1.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wenzheng Jiang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32739 
 
 
 
  Unable to export path in matrix jobs.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wenzheng Jiang 
 
 
 
 
 
 
 
 
 
 When using customTools plugin, I export the installation path by putting them in "Exported paths".  But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs.    My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand :export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin"# Use `flock` to ensure that we do not install/update `phpenv` simultaneously across different jobs.(if ! flock --exclusive --nonblock 9; then# Wait for the lock to be released and then continue.flock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then   # phpenv update   echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [job-dsl-plugin] (JENKINS-32742) Make environment contributors extensible

[damien.corabo...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32742 
 
 
 
  Make environment contributors extensible  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 job-dsl-plugin 
 
 
 

Created:
 

 03/Feb/16 6:10 AM 
 
 
 

Environment:
 

 1.42 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Damien Coraboeuf 
 
 
 
 
 
 
 
 
 
 
Hi, 
The environmentVariables / contributors section should be made extensible in order to facilitate the inclusion of extensions. 
This is a simple update to do and I'm preparing the pull request. 
Damien. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
   

[JIRA] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wenzheng Jiang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32739 
 
 
 
  Unable to export path in matrix jobs.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wenzheng Jiang 
 
 
 

Attachment:
 
 2.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wenzheng Jiang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32739 
 
 
 
  Unable to export path in matrix jobs.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wenzheng Jiang 
 
 
 
 
 
 
 
 
 
 When using customTools plugin, I export the installation path by putting them in "Exported paths".  But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs. My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand : ``` export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin"# Use `flock` to ensure that we do not install/update `phpenv` simultaneously across different jobs.(if ! flock --exclusive --nonblock 9; then# Wait for the lock to be released and then continue.flock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then   # phpenv update   echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)" ``` 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wenzheng Jiang commented on  JENKINS-32739 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to export path in matrix jobs.  
 
 
 
 
 
 
 
 
 
 
Updated description 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wenzheng Jiang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32739 
 
 
 
  Unable to export path in matrix jobs.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wenzheng Jiang 
 
 
 
 
 
 
 
 
 
 When using customTools plugin, I export the installation path by putting them in "Exported paths".  But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs. My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand :```export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin"# Use `flock` to ensure that we do not install/update `phpenv` simultaneously across different jobs.(if ! flock --exclusive --nonblock 9; then# Wait for the lock to be released and then continue.flock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then   # phpenv update   echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)"``` I also export the path in the installer command, but it also doesn't work. In the building process, I get 'phpenv not found' error and reason is the installation path is not in $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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wenzheng Jiang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32739 
 
 
 
  Unable to export path in matrix jobs.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wenzheng Jiang 
 
 
 
 
 
 
 
 
 
 When using customTools plugin, I export the installation path by putting them in "Exported paths".  But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs. My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand :```export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin"(if ! flock --exclusive --nonblock 9; thenflock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then    # phpenv update    echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)"```I also export the path in the installer command, but it also doesn't work. In the building process, I get 'phpenv not found' error and reason is the installation path is not in $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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wenzheng Jiang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32739 
 
 
 
  Unable to export path in matrix jobs.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wenzheng Jiang 
 
 
 
 
 
 
 
 
 
 When using customTools plugin, I export the installation path by putting them in "Exported paths".  But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs. My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand :```export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin" # Use `flock` to ensure that we do not install/update `phpenv` simultaneously across different jobs. (if ! flock --exclusive --nonblock 9; then # Wait for the lock to be released and then continue. flock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then   # phpenv update   echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)"```I also export the path in the installer command, but it also doesn't work. In the building process, I get 'phpenv not found' error and reason is the installation path is not in $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] [matrix-project-plugin] (JENKINS-9531) choose matrix build nodes based on label matches

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Reitzel commented on  JENKINS-9531 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: choose matrix build nodes based on label matches  
 
 
 
 
 
 
 
 
 
 
Thanks for linking that. I'm gonna watch it too. 
My workaround has been to setup another Jenkins with a single master and no slaves to do the chain of 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] [token-macro-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

[damien.corabo...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32331 
 
 
 
  Performance problems on scan on huge Jenkins instances  
 
 
 
 
 
 
 
 
 

Change By:
 
 Damien Coraboeuf 
 
 
 

Component/s:
 
 token-macro-plugin 
 
 
 

Component/s:
 
 build-failure-analyzer-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-application-automation-tools-plugin] (JENKINS-32734) Please document that this plugin is Windows-only.

[rvinc...@prokarma.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Vincent updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32734 
 
 
 
  Please document that this plugin is Windows-only.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robert Vincent 
 
 
 
 
 
 
 
 
 
 I have discovered that the hp-application-automation-tools-plugin requires Windows, as it deploys and attempts to run a Windows 32-bit executable.I would suggest that " win32 32-bit Windows " be added to the [Prerequisites list ]( | https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools#HPApplicationAutomationTools-UserGuide ) ]  on the [plugin page ]( | https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools ) ] . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31321) Renaming a node over another is possible and destroys both configurations

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31321 
 
 
 
  Renaming a node over another is possible and destroys both configurations  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oliver Gondža 
 
 
 

Labels:
 
 lts 1.642.2 - candidate 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] [ant-plugin] (JENKINS-13044) Ant multiple properties delimited by spaces parsed as a single property

[ed.rand...@ingenotech.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ed Randall commented on  JENKINS-13044 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ant multiple properties delimited by spaces parsed as a single property  
 
 
 
 
 
 
 
 
 
 
You can argue technical points 'til the cows come home, but bad user experience is bad user experience. Don't even fix the help text? Why not, just leave it.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ant-plugin] (JENKINS-13044) Ant multiple properties delimited by spaces parsed as a single property

[ed.rand...@ingenotech.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ed Randall edited a comment on  JENKINS-13044 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ant multiple properties delimited by spaces parsed as a single property  
 
 
 
 
 
 
 
 
 
 You can argue technical points  'til the cows come home, but bad user experience is bad user experience.Don't even fix the help text?  It  wpuld  would  have taken  somepone  someone  who knows the system ,  less time than writing a comment here - certainly less than 4 years.   Why not, just leave it.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ant-plugin] (JENKINS-13044) Ant multiple properties delimited by spaces parsed as a single property

[ed.rand...@ingenotech.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ed Randall edited a comment on  JENKINS-13044 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ant multiple properties delimited by spaces parsed as a single property  
 
 
 
 
 
 
 
 
 
 You can argue technical points  'til the cows come home, but bad user experience is bad user experience.Don't even fix the help text?   It wpuld have taken somepone who knows the system, less time than writing a comment here - certainly less than 4 years.      Why not, just leave it.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ant-plugin] (JENKINS-13044) Ant multiple properties delimited by spaces parsed as a single property

[ed.rand...@ingenotech.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ed Randall edited a comment on  JENKINS-13044 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ant multiple properties delimited by spaces parsed as a single property  
 
 
 
 
 
 
 
 
 
 You can argue technical points  'til the cows come home, but bad user experience is bad user experience.Don't even fix the help text?  It would have taken someone who knows the system less time than writing a comment here - certainly less than 4 years  since I raised this in good faith .        Just add the words "each on a new line" Why not, just leave it.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [extended-choice-parameter-plugin] (JENKINS-32722) Extended Choice-messy code when read parameter from file

[liy...@teambition.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 edision chow created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32722 
 
 
 
  Extended Choice-messy code when read parameter from file  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 edision chow 
 
 
 

Components:
 

 extended-choice-parameter-plugin 
 
 
 

Created:
 

 02/Feb/16 9:00 AM 
 
 
 

Environment:
 

 jenkins docker 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 edision chow 
 
 
 
 
 
 
 
 
 
 
We met messy code when using Extended Choice plugin. The file is utf8 and Extended Choice plugin read the chinese string into the select box. But the chinese words messy code. Could u pls tell me how to set the encoding parameter of this plugin to support chinese? 
Thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 

[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gavin Shelley commented on  JENKINS-19743 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Massive parallel builds sometimes cause errors in LogRotation  
 
 
 
 
 
 
 
 
 
 
We see this on 1.611. We too have 100s of parallel jobs running. This pollutes the logs with scary messages. Not sure if it actually affects us apart from logs, but it would be nice to see this resolved in case it is the cause of the occasional unexplained problem. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jacoco-plugin] (JENKINS-32575) Manually uploading a plugin causes 413 Request Entity Too Large error.

[roberto.pince...@n-dimension.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Pincente commented on  JENKINS-32575 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Manually uploading a plugin causes 413 Request Entity Too Large error.  
 
 
 
 
 
 
 
 
 
 
This is likely caused by the webserver and not jenkins itself... 
you may have to up the max client body size... here is an example config change for nginx if thats  
http://www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-large/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tap-plugin] (JENKINS-32729) TAP Extended Test Results page does not render properly

[meteo...@rocketmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Choon Chern Lim created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32729 
 
 
 
  TAP Extended Test Results page does not render properly  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Bruno P. Kinoshita 
 
 
 

Attachments:
 

 Screen Shot 2016-02-02 at 8.23.11 AM.png 
 
 
 

Components:
 

 tap-plugin 
 
 
 

Created:
 

 02/Feb/16 2:27 PM 
 
 
 

Environment:
 

 TAP plugin 1.24  Jenkins 1.645 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Choon Chern Lim 
 
 
 
 
 
 
 
 
 
 
When viewing the TAP Extended Test Results page, there are some unresolved HTML tags on top of the page (see attached screenshot). 
 
 
 
 
 
 
 
 
 
 
 
 

 
  

[JIRA] [jacoco-plugin] (JENKINS-32575) Manually uploading a plugin causes 413 Request Entity Too Large error.

[roberto.pince...@n-dimension.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Pincente edited a comment on  JENKINS-32575 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Manually uploading a plugin causes 413 Request Entity Too Large error.  
 
 
 
 
 
 
 
 
 
 This is likely caused by the webserver and not jenkins itself... you You  may have to up the max client body size...    here is an example config change for  nginx if thats   ngin:   http://www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-large/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jacoco-plugin] (JENKINS-32575) Manually uploading a plugin causes 413 Request Entity Too Large error.

[roberto.pince...@n-dimension.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Pincente edited a comment on  JENKINS-32575 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Manually uploading a plugin causes 413 Request Entity Too Large error.  
 
 
 
 
 
 
 
 
 
 This is likely caused by the webserver and not jenkins itself...You may have to up the max client body size... here is an example config change for  ngin  nginx :http://www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-large/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tap-plugin] (JENKINS-32730) TAP Test Results: Individual test link returns 404

[meteo...@rocketmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Choon Chern Lim created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32730 
 
 
 
  TAP Test Results: Individual test link returns 404  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Bruno P. Kinoshita 
 
 
 

Attachments:
 

 Screen Shot 2016-02-02 at 9.08.38 AM.png, Screen_Shot_2016-02-02_at_9_05_29_AM.png 
 
 
 

Components:
 

 tap-plugin 
 
 
 

Created:
 

 02/Feb/16 3:11 PM 
 
 
 

Environment:
 

 TAP Plugin 1.24  Jenkins 1.645  
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Choon Chern Lim 
 
 
 
 
 
 
 
 
 
 
When viewing the TAP Test Results page, each test link returns 404. I assume this link will show results from the test run. 
How do I configure my job to make use of these links?  
Attached is the error link I'm seeing, and my job configuration. 
 
 
 
 
 
 
 
 
 
  

[JIRA] [logaction] (JENKINS-30219) Failed to rotate log, looks to have already been deleted

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gavin Shelley commented on  JENKINS-30219 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed to rotate log, looks to have already been deleted  
 
 
 
 
 
 
 
 
 
 
Looks like a dupe of JENKINS-19743 (Not sure if I have privs or should try to mark as such...) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-traceability-plugin] (JENKINS-32723) Docker Traceability plugin not showing Environment info

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32723 
 
 
 
  Docker Traceability plugin not showing Environment info  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Soto 
 
 
 

Summary:
 
 Docker Traceability plugin  does  not  show   showing Environment info 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [customtools-plugin] (JENKINS-32724) Using injected environment variables

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-32724 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Using injected environment variables  
 
 
 
 
 
 
 
 
 
 
I'm not 100% sure about Label axis. IIRC they used to work. Regarding the EnvInject plugin, it depends on the build wrapper inclusion order. Currently it's not possible to alter the order in Jenkins core. I had a pull request for it (https://github.com/jenkinsci/jenkins/pull/1026), but I have not finished it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-24832) Failed maven builds using -T are showing up as Aborted

[l...@tikalk.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-24832 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed maven builds using -T are showing up as Aborted  
 
 
 
 
 
 
 
 
 
 
Any update on this one? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32444) Proposal: Move build logs off of Jenkins master

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32444 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Proposal: Move build logs off of Jenkins master  
 
 
 
 
 
 
 
 
 
 

I should have that choice. 
 
I don't think the proposed implementation makes sense in any official Jenkins releases, as turning off a significant part of its functionality in a hidden feature switch isn't a great approach. Having it be designed to be temporary makes it even worse… 
If you want to implement it in your fork, feel free – we may even be able to reuse parts of it. 
A new interface/super type for build wrappers to indicate their support for running on the slave, and routing through master if not all build wrappers (and whoever else may be involved) support this feature would be a better approach. With added logging which wrappers prevent direct log transfer to your storage, you could easily remove the culprits from your instance and get the same result. 
This should be both backward compatible and future proof. 
If this has been discussed in more depth in the tech track of the summit yesterday Jesse Glick please share the details. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [customtools-plugin] (JENKINS-32724) Using injected environment variables

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wenzheng Jiang created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32724 
 
 
 
  Using injected environment variables  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 customtools-plugin, envinject-plugin 
 
 
 

Created:
 

 02/Feb/16 9:21 AM 
 
 
 

Environment:
 

 Jenkins 1.646  Custom Tools Plugin 0.4.4 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Wenzheng Jiang 
 
 
 
 
 
 
 
 
 
 
I want expose some environment variables to customTool installer, and I hope these environment variables can be from EnvInject and matrix job axes. But currently, these environment variables are injected after customTools runs, so I cannot use them.  
Is it possible to let customTools run after these environment variables get injected ? Or if we cannot do it in current version, can this be implemented in future versions ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 

[JIRA] [remoting] (JENKINS-28844) The curious case of the Channel memory cycles

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

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

 
 
 
 
 
 
 
  Re: The curious case of the Channel memory cycles  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Stephen Connolly Path: pom.xml http://jenkins-ci.org/commit/jenkins/9cd1929cfc80145657ad51c2d7d98d16b9f62195 Log: Merge pull request #1766 from jenkinsci/jenkins-28844 
[FIXED JENKINS-28844] The curious case of the Channel memory cycles 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [remoting] (JENKINS-28844) The curious case of the Channel memory cycles

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

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

 
 
 
 
 
 
 
  Re: The curious case of the Channel memory cycles  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/1edb51cb919a3270b26e8782a0426381385df9b9 Log: 

JENKINS-28844
 Noting merge of #1766 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [pretested-integration-plugin] (JENKINS-32383) Java 1.6 compliance (Praqma case 14102)

[t...@praqma.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thierry Lacour closed an issue as Won't Fix 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
After internal discussion we've decided we won't go back to support 1.6 as it's long past its EOL. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32383 
 
 
 
  Java 1.6 compliance (Praqma case 14102)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thierry Lacour 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [pretested-integration-plugin] (JENKINS-32383) Java 1.6 compliance (Praqma case 14102)

[t...@praqma.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thierry Lacour reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Reopening as a task to add ample documentation and warnings about our choice of Java support. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32383 
 
 
 
  Java 1.6 compliance (Praqma case 14102)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thierry Lacour 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 

Status:
 
 Closed 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] [docker-traceability-plugin] (JENKINS-32723) Docker Traceability plugin does not show

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Soto created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32723 
 
 
 
  Docker Traceability plugin does not show   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 Screen Shot 2016-02-02 at 10.00.41.png, Screen Shot 2016-02-02 at 10.01.38.png 
 
 
 

Components:
 

 docker-traceability-plugin 
 
 
 

Created:
 

 02/Feb/16 9:12 AM 
 
 
 

Environment:
 

 Plugin Version 1.1, MACOSX 
 
 
 

Labels:
 

 bug 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Alex Soto 
 
 
 
 
 
 
 
 
 
 
Environment information is not printed in any report of a traced image. 
To reproduce it I have only created a new build image with Build and Publish Step, after that I have run a docker run of that image, and finally with docker ps -a I got the container 

[JIRA] [matrix-project-plugin] (JENKINS-26226) Matrix project overrides custom workspace configuration

[rich.norl...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Norling commented on  JENKINS-26226 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Matrix project overrides custom workspace configuration  
 
 
 
 
 
 
 
 
 
 
Have you tried setting the "Directory for sub-builds" to "."? This option should checkout all matrix spawns into the same workspace. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ant-plugin] (JENKINS-13044) Ant multiple properties delimited by spaces parsed as a single property

[ed.rand...@ingenotech.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ed Randall commented on  JENKINS-13044 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ant multiple properties delimited by spaces parsed as a single property  
 
 
 
 
 
 
 
 
 
 
Whatever the standard java prioperties file format says, this is a user interface element and should follow the principal of least surprise. The behaviour was not what the documentation described and not what the user expected. As a minimum the documentation should be fixed, ideally the box should be more than one line line high by default. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [pretested-integration-plugin] (JENKINS-32383) Java 1.6 compliance (Praqma case 14102)

[t...@praqma.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thierry Lacour updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32383 
 
 
 
  Java 1.6 compliance (Praqma case 14102)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thierry Lacour 
 
 
 

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] [pretested-integration-plugin] (JENKINS-32383) Java 1.6 compliance (Praqma case 14102)

[t...@praqma.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thierry Lacour updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32383 
 
 
 
  Java 1.6 compliance (Praqma case 14102)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thierry Lacour 
 
 
 
 
 
 
 
 
 
 Add warnings and documentation stating the minimum required version of Java for users using 1.6 or below. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [pretested-integration-plugin] (JENKINS-32360) Configuration option to mention ready branch name in commit message (our case 14095)

[t...@praqma.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thierry Lacour commented on  JENKINS-32360 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Configuration option to mention ready branch name in commit message (our case 14095)  
 
 
 
 
 
 
 
 
 
 
Discussion resulted in the feature being scrapped. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.