[JIRA] [xunit] (JENKINS-17193) Missing Delete button
justinas Urbanavicius commented on JENKINS-17193 Missing Delete button Did you add more then one build action, xUnit being the last one ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [bugzilla] (JENKINS-21176) trebon
read one created JENKINS-21176 trebon Issue Type: Improvement Assignee: mdonohue Components: bugzilla Created: 30/Dec/13 8:22 AM Project: Jenkins Priority: Major Reporter: read one This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [xunit] (JENKINS-21094) NullPointerException at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:178)
Vlad Aginsky commented on JENKINS-21094 NullPointerException at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:178) Same for me: ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception 10:43:17 java.lang.NullPointerException 10:43:17 at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:80) 10:43:17 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 10:43:17 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) 10:43:17 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) 10:43:17 at hudson.model.Build$BuildExecution.post2(Build.java:183) 10:43:17 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) 10:43:17 at hudson.model.Run.execute(Run.java:1703) 10:43:17 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 10:43:17 at hudson.model.ResourceController.execute(ResourceController.java:88) 10:43:17 at hudson.model.Executor.run(Executor.java:231) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [maven] (JENKINS-20209) Maven plugin sends email notification to null address
kutzi commented on JENKINS-20209 Maven plugin sends email notification to null address Dmitry, it's available already. Just update the Maven plugin to 2.1. There's nothing special about LTS in that respect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [maven] (JENKINS-20209) Maven plugin sends email notification to null address
Dmitry Baburkin commented on JENKINS-20209 Maven plugin sends email notification to null address Kutzi, for some reason, Jenkins doesn't show that I can upgrade from 2.0 to 2.1. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-8423) Slave priority
Chris Hobbs commented on JENKINS-8423 Slave priority This needs to happen. I have a small linux server hosting my Jenkins which takes some time building and slows down everything else on the server while doing so and I also have my Desktop which is much beefier. I would like to have the jobs run on my PC when it's online but on the linux server when my PC is off... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [maven] (JENKINS-20506) Subprojects not displayed for Maven Projectes
Dominik Bartholdi updated JENKINS-20506 Subprojects not displayed for Maven Projectes Change By: Dominik Bartholdi (30/Dec/13 10:25 AM) Component/s: maven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [maven] (JENKINS-20506) Subprojects not displayed for Maven Projectes
Dominik Bartholdi commented on JENKINS-20506 Subprojects not displayed for Maven Projectes placed new PR to fix issue in maven-plugin https://github.com/jenkinsci/maven-plugin/pull/16 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-8423) Slave priority
Dell Green commented on JENKINS-8423 Slave priority Sadly I still haven't found the time to look into writing this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21173) Anonymous Users Can Configure Priorities
Magnus Sandberg assigned JENKINS-21173 to Magnus Sandberg Anonymous Users Can Configure Priorities Change By: Magnus Sandberg (30/Dec/13 11:35 AM) Assignee: bklarson Magnus Sandberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-18971) Triggering a build with a parameterized node label to run on the same node doesn't work in most cases because it will take an addition executor on the node.
Dominik Bartholdi commented on JENKINS-18971 Triggering a build with a parameterized node label to run on the same node doesn't work in most cases because it will take an addition executor on the node. I'm not sure how to solve this... The job does not actually take an additional executor, but the way you have organized your jobs means that your first job triggers a second. This will always use two executors. If your "prerequisite job" always has to run before the "main job", then maybe you should change the order? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
Getting error while deploy to weblogic
Hello All,When we are trying to migrate WAR file to web logic 12c server we
are getting below error.Started by user anonymousBuilding in workspace
C:\Users\1568\.jenkins\workspace\Deploy - Weblogic
Project[WeblogicDeploymentPlugin] - Pay attention of Jdk version {selected
version is 1.7.0_45} compatibility with Weblogic Deployer API (see Oracle
documentation).[WeblogicDeploymentPlugin] - The JDK C:\Program
Files\Java\jdk1.7.0_45 will be used.[WeblogicDeploymentPlugin] -
ArtifactSelector used :
org.jenkinsci.plugins.deploy.weblogic.FreeStyleJobArtifactSelectorImpl@16887b3[WeblogicDeploymentPlugin]
- Retrieving artifacts recorded [filtered resources on
jci.war]...[WeblogicDeploymentPlugin] - the following file UserBean.class
doesn't match jci.war[WeblogicDeploymentPlugin] - the following file
main.xhtml doesn't match jci.war[WeblogicDeploymentPlugin] - the following
file Test.html doesn't match jci.war[WeblogicDeploymentPlugin] - the
following file beans.xml doesn't match jci.war[WeblogicDeploymentPlugin] -
the following file UserBean.class doesn't match
jci.war[WeblogicDeploymentPlugin] - the following file web.xml doesn't match
jci.war[WeblogicDeploymentPlugin] - the following file recorded jci.war is
eligible.[WeblogicDeploymentPlugin] - the following file pom.properties
doesn't match jci.war[WeblogicDeploymentPlugin] - Deploying the artifact on
the following target : (name=Weblogic) (host=192.168.200.176)
(port=7001)[WeblogicDeploymentPlugin] - UNDEPLOYING ARTIFACT...$ "C:\Program
Files\Java\jdk1.7.0_45\bin/java" -Xms256M -Xmx256M -cp
C:\Users\1568\.jenkins\plugins\weblogic-deployer-plugin\weblogic.jar
weblogic.Deployer -debug -remote -verbose -noexit -name JCI -targets
AdminServer -adminurl t3://192.168.200.176:7001 -user wissen -password
Cr8@01dec -undeploy[WeblogicDeploymentPlugin] - ARTIFACT UNDEPLOYED
SUCCESSFULLY.[WeblogicDeploymentPlugin] - DEPLOYING ARTIFACT...$ "C:\Program
Files\Java\jdk1.7.0_45\bin/java" -Xms256M -Xmx256M -cp
C:\Users\1568\.jenkins\plugins\weblogic-deployer-plugin\weblogic.jar
weblogic.Deployer -debug -stage -remote -verbose -upload -name JCI -source
"C:\Users\1568\.jenkins\workspace\Deploy - Weblogic
Project2\branches\jci\target\jci.war" -targets AdminServer -adminurl
t3://192.168.200.176:7001 -user wissen -password Cr8@01dec
-deployjava.lang.RuntimeException: task completed abnormally (exit code = 1)
at
org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.deploy(DeploymentTaskServiceImpl.java:255)
at
org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:184)
at
org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:236)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)
at
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757)
at hudson.model.Build$BuildExecution.post2(Build.java:183) at
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
at hudson.model.Run.execute(Run.java:1703) at
hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at
hudson.model.ResourceController.execute(ResourceController.java:88) at
hudson.model.Executor.run(Executor.java:231)ERROR:
[WeblogicDeploymentPlugin] - Failed to deploy.[INFO]
[INFO]
DEPLOYMENT SUCCESS[INFO]
Finished:
SUCCESSannd also when we click on Weblogic deployments, we are seeing below
error. ARTIFACT UNDEPLOYMENT
Error: Could not find or
load main class weblogic.Deployer
ARTIFACT DEPLOYMENT Error:
Could not find or load main class weblogic.DeployerCan some one help me on
this to resove the issue.Thanks,Nagesh S
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/Getting-error-while-deploy-to-weblogic-tp4685694.html
Sent from the Jenkins issues mailing list archive at Nabble.com.
--
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/groups/opt_out.
[JIRA] [envinject] (JENKINS-21177) EnvInject Plugin - Does not override environment variables at job level
Prithula Mukherjee
created JENKINS-21177
EnvInject Plugin - Does not override environment variables at job level
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
envinject
Created:
30/Dec/13 1:09 PM
Description:
The EnvInject plugin still does not override the global environment variable in within a jenkins job. I am using version 1.89.
I have set couple of global variables in the jenkins. In one of the jenkins job, I am trying to override the values of those variables based on a condition. But it is not working.
Below snippet is for reference:EnvInject - Loading node environment variables.
EnvInject - Preparing an environment for the build.
EnvInject - Keeping Jenkins build variables.
EnvInject - Executing and processing the following script content: This piece is executed in the Prepare an environment for the run section.
if [ ${EmergencyFix}= true ]
then
export RelPractice=${OldRelease}.x; export SprintCycle=""
fi
echo ${RelPractice}
hudson $ /bin/sh -xe /tmp/hudson3221881724786897823.sh
+ '' true = true ''
+ export RelPractice=1.4.x
+ RelPractice=1.4.x
+ export SprintCycle=
+ SprintCycle=
+ echo 1.4.x
1.4.x
EnvInject - Script executed successfully.
EnvInject - Injecting contributions.
Building on master in workspace /var/lib/hudson/jobs/TestJob_Practice/workspace
EnvInject - Executing scripts and injecting environment variables after the SCM step.
EnvInject - Executing and processing the following script content: - This piece is executed in the Build environment section.
echo ${RelPractice}
workspace $ /bin/sh -xe /tmp/hudson1726775335392935354.sh
+ echo 1.5
1.5 - it is showing the old value.
EnvInject - Script executed successfully.
Finished: SUCCESS
Due Date:
31/Dec/13 12:00 AM
Project:
Jenkins
Priority:
Critical
Reporter:
Prithula Mukherjee
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [core] (JENKINS-21178) Matrix jobs fails randomly during building the changelog
Anne Stellingwerf created JENKINS-21178 Matrix jobs fails randomly during building the changelog Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Dec/13 1:35 PM Description: Sometimes several of the matrix jobs fail: The first few sub runs go fine, and then all of a sudden, the next sub run fails with the following stack trace: Started by upstream project "pct-trunk-wip-frt-w-x64" build number 495 originally caused by: Started by upstream project "pct-junit-linkchecker-w" build number 527 originally caused by: Started by upstream project "security-install-crd97" build number 1087 originally caused by: Started by timer Building remotely on srv-nl-crd97 in workspace e:\pct-trunk-wip-workspace Updating http://srv-ind-scrat.vanenburg.com:8080/repos/tools/trunk/silent-installer/stable/dev at revision '2013-12-27T05:44:14.546 +0100' At revision 12697 hudson.util.IOException2: revision check failed on http://srv-ind-scrat.vanenburg.com:8080/repos/tools/trunk/silent-installer/stable/dev at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:178) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:113) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:649) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:810) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:657) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1604) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: org.tmatesoft.svn.core.SVNException: svn: E195012: Unable to find repository location for 'http://srv-ind-scrat.vanenburg.com:8080/repos/tools/trunk/silent-installer/stable/dev@UNDEFINED' in revision '12,697' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:187) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:291) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:166) ... 11 more Caused by: svn: E195012: Unable to find repository location for 'http://srv-ind-scrat.vanenburg.com:8080/repos/tools/trunk/silent-installer/stable/dev@UNDEFINED' in revision '12,697' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:189) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:141) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184) ... 20 more Retrying after 10 seconds Updating http://srv-ind-scrat.vanenburg.com:8080/repos/tools/trunk/silent-installer/stable/dev at revision '2013-12-27T05:44:14.546 +0100' At revision 12697 hudson.util.IOException2: revision check failed on http://srv-ind-scrat.vanenburg.com:8080/repos/tools/trunk/silent-installer/stable/dev at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:178) at hudson.scm.SubversionChangeLogBuil
[JIRA] [git] (JENKINS-20231) Wipe out repository & force clone option is broken since GIT plugin version 2.0
Hallvard Nygård commented on JENKINS-20231 Wipe out repository & force clone option is broken since GIT plugin version 2.0 Also experiencing the same issue when wiping or like this time - started using concurrent builds (with new workspaces). Started by build flow Project - Orchestrator#132 Building in workspace D:\Jenkins\jobs\Project - Flow - Build and publish\workspace@3 Cloning the remote Git repository Cloning repository ssh://...@...:29418/Project.git git --version git version 1.8.4.msysgit.0 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Since we are using a Flow build (plugin) we forward different Gerrit Trigger variables that is needed to checkout the correct code. Build parameters: GIT_COMMIT_PARAM: 5eec51b0eeaa79eb5d9d7f8067a96f049a941fef GIT_COMMIT_REFSPEC: refs/changes/66/66/2 This is the same variables that Gerrit Trigger normally is configured with. Configuration - Source Code Management: Repo URL: ssh://...@...:29418/Project.git Credentials: Our credentials - SSH key based Name: Refspec: $GIT_COMMIT_REFSPEC Branch Specifier: $GIT_COMMIT_PARAM Repository Browser: (Auto) No "Gerrit Trigger" as "Strategy" (normal setup when using the Gerrit Trigger) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [junit] (JENKINS-20701) Matrix Project with Combination Filter does not publish JUnit Reports
Dominik Bartholdi commented on JENKINS-20701 Matrix Project with Combination Filter does not publish JUnit Reports can please provide the config.xml of your build? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-11600) Implement Entry.getDate and Entry.getRevision for email-ext support
Walter Couto commented on JENKINS-11600 Implement Entry.getDate and Entry.getRevision for email-ext support I can't tell the version as it is not reported in the emails, but it stopped working for us on October 30th, 2013. So recently. We keep up to date with the latest Jenkins and plugins. Our P4 server version hasn't changed between those dates. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-19222) Update to 1.527 breaks ${NODE_NAME} as node parameter on master
Dominik Bartholdi
commented on JENKINS-19222
Update to 1.527 breaks ${NODE_NAME} as node parameter on master
I think this is related to JENKINS-19307 which is fixed with core version 1.532.1
my tests where OK with '1.532.1' - can you please try too?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-18256) Sort node names
Dominik Bartholdi resolved JENKINS-18256 as Fixed Sort node names sorting is now alphabetically, with 'master' and 'ALL' always on top Change By: Dominik Bartholdi (30/Dec/13 3:06 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-17660) Trigger via script does not support LABEL
Dominik Bartholdi
resolved JENKINS-17660 as Not A Defect
Trigger via script does not support LABEL
you should use 'label' instead of 'value' as the key.
curl --silent --show-error --data 'json={"parameter":[{"name":"NODE_LABEL","label":"LABEL"}]}&Submit=Build' http://jenkins:/job/JOBNAME/build
Change By:
Dominik Bartholdi
(30/Dec/13 3:39 PM)
Status:
Open
Resolved
Resolution:
Not A Defect
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [core] (JENKINS-15576) LoadStatistics queue length and Cloud provisioning not working in conjunction with Node and Label parameter plugin
Dominik Bartholdi assigned JENKINS-15576 to Jesse Glick LoadStatistics queue length and Cloud provisioning not working in conjunction with Node and Label parameter plugin Jesse, I'm quite sure you have a better understanding of the LoadStatistics - do you think the proposed solution would help? Change By: Dominik Bartholdi (30/Dec/13 3:55 PM) Assignee: Laurence Hey Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-13966) Parameter Factories on Trigger parameterized build
Dominik Bartholdi commented on JENKINS-13966 Parameter Factories on Trigger parameterized build unfortunate, the parameterized-trigger-plugin does not (yet) use the factories in the post-build actions... ...PR's welcome This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [update-center] (JENKINS-16556) Plugin deploy after update
jburrows commented on JENKINS-16556 Plugin deploy after update Same issues still exist in v 1.544: Maven Project Plugin Failure - java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1304) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1103) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Unable to delete C:\Apps\Jenkins\plugins\maven-plugin\WEB-INF\lib\aether-api-0.9.0.M3.jar at hudson.Util.deleteFile(Util.java:254) at hudson.Util.deleteRecursive(Util.java:301) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:422) at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:128) at hudson.PluginManager.dynamicLoad(PluginManager.java:412) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1300) ... 6 more java.vm.name Java HotSpot(TM) 64-Bit Server VM java.version 1.6.0_26 os.name Windows Server 2008 R2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-16574) IllegalArgumentException when Rebuilding a project with nodelabel
Dominik Bartholdi commented on JENKINS-16574 IllegalArgumentException when Rebuilding a project with nodelabel Which version of the plugins are you using, the error message given in the stack - leads me to a quite old version of the nodelabelparameter-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-11600) Implement Entry.getDate and Entry.getRevision for email-ext support
Rob Petti commented on JENKINS-11600 Implement Entry.getDate and Entry.getRevision for email-ext support I'd recommend rolling back to see if it fixes your issue. As I've said, this doesn't appear to be an issue with the Perforce Plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
Brenden Conte commented on JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. Confirmed this issue is not resolved. Please reopen. Windows Server 2008 Jenkins ver. 1.532.1 Maven Interaction Plugin 2.0 ERROR: Failed to parse POMs java.io.FileNotFoundException: E:\Jenkins\builds\Project\com.domain:proj\2013-12-30_12-33-08\log (The filename, directory name, or volume label syntax is incorrect) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
Brenden Conte edited a comment on JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. Confirmed this issue is not resolved. Windows Server 2008 Jenkins ver. 1.532.1 Maven Interaction Plugin 2.0 ERROR: Failed to parse POMs java.io.FileNotFoundException: E:\Jenkins\builds\Project\com.domain:proj\2013-12-30_12-33-08\log (The filename, directory name, or volume label syntax is incorrect) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21166) Environment variables are NOT passed further build steps when using "Block until the triggered projects finish their builds"
Dilip M updated JENKINS-21166 Environment variables are NOT passed further build steps when using "Block until the triggered projects finish their builds" Change By: Dilip M (30/Dec/13 7:31 PM) Description: In section +Usage as a Build step+ in https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin its mentioned that, When using the +Trigger/Call builds on another project+ item. If the trigger is configured with the +Block until the triggered projects finish their builds+ enabled, the following Environment variables are made available for further build steps Env variables for future build steps * LAST_TRIGGERED_JOB_NAME="Last project started"* TRIGGERED_BUILD_NUMBER_="Last build number triggered"version 2.17 onwards* TRIGGERED_JOB_NAMES="Comma separated list of all triggered projects"* TRIGGERED_BUILD_NUMBERS_="Comma separated list of build numbers triggered"* TRIGGERED_BUILD_RESULT_="Last triggered build result of project"* TRIGGERED_BUILD_RESULT_RUN="Result of triggered build for build number"* TRIGGERED_BUILD_RUN_COUNT_project name>="Number of builds triggered for the project" I tried configuring one upstream and downstream job. But I don’t see these ENV variables being passed to downstream jobs? PS: I am checking for these ENV variables in Build step of downstream job like 'env|grep TRIGGERED' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-18971) Triggering a build with a parameterized node label to run on the same node doesn't work in most cases because it will take an addition executor on the node.
Russell Weber commented on JENKINS-18971 Triggering a build with a parameterized node label to run on the same node doesn't work in most cases because it will take an addition executor on the node. I worked around this by using the rest api and python on a proxy virtual machine to run and control the jobs; I needed something to monitor the machine as it rebooted anyway. If all else fails... use the api which is much more flexible than the web front end. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [htmlpublisher] (JENKINS-15301) HTML Publisher failure: Failed to extract directory from slave
John Armenia commented on JENKINS-15301 HTML Publisher failure: Failed to extract directory from slave Problem still exists in 1.544 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
Brenden Conte edited a comment on JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. Confirmed this issue is not resolved. Windows Server 2008 Jenkins ver. 1.532.1 Maven Interaction Plugin 2.0 ERROR: Failed to parse POMs java.io.FileNotFoundException: E:\Jenkins\builds\Project\com.domain:proj\2013-12-30_12-33-08\log (The filename, directory name, or volume label syntax is incorrect) Edit: Also verified with Jenkins ver. 1.544 Maven Interaction Plugin 2.1 Also note this is "out of the box" configuration. No custom paths have been specified. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
Brenden Conte edited a comment on JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. Edit: Non-issue; turns out ITEM_FULLNAME was being used in the system-wide configuration. Changed to ITEM_FULL_NAME and it now works properly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [xunit] (JENKINS-16131) Conversion error with boost test and long Error information
Gregory Boissinot resolved JENKINS-16131 as Fixed Conversion error with boost test and long Error information Change By: Gregory Boissinot (30/Dec/13 10:07 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
Gregory Boissinot commented on JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing Please check with the latest version, it should be OK for now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [xunit] (JENKINS-21094) NullPointerException at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:178)
Gregory Boissinot resolved JENKINS-21094 as Fixed NullPointerException at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:178) Fixed with last version Change By: Gregory Boissinot (30/Dec/13 10:23 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [infrastructure] (JENKINS-21056) Ability to separate build build history of parameterized projects
Michael Rose edited a comment on JENKINS-21056 Ability to separate build build history of parameterized projects Adding job creator plugins to components section to get some other points of view. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [infrastructure] (JENKINS-21056) Ability to separate build build history of parameterized projects
Michael Rose updated JENKINS-21056 Ability to separate build build history of parameterized projects Adding job creator plugins to components to get some other points of view. Change By: Michael Rose (30/Dec/13 11:44 PM) Description: I'm not sure what component this would fall under so I just chose infrastructure. There are several plugins to generate jobs in Jenkins. The reason being users want to be able to quickly create jobs that follow a standard set of steps. I have taken a different approach. I have made completely parametrized "helper" jobs that my build flow jobs calls. This limits the number of places that configuration changes need to be made.The problem I have found with this approach is that if you have multiple projects calling the same "helper" job, the build history for the "helper" job becomes less useful (e.g. you can't quickly discern trend data).It would be nice if there was a way to separate builds into different buckets. A couple of approaches that came to mind were:A new job type "Link to existing job"- This would be similar to copy existing job except the config file(s) would be a link(s). The configuration screen would probably need to display a warning showing the projects that would be affected if changes were made.Parameter based "bucketing"- The user can choose the "bucket" they want the build to appear in.Enhance reporters- Allow build reporting tools (e.g. the build history list on each project page, the build history list on each node page) filter results based on the build parameters.Thoughts? Component/s: job-dsl-plugin Component/s: jobcopy-builder Component/s: jobgenerator This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [sitemonitor] (JENKINS-13358) Timeout not working
Mark Edington commented on JENKINS-13358 Timeout not working This issue appears to be addressed by Pull Request #7. I built and tested this fix and it solved the issue where the connection is successful, but the server fails to return a response in a reasonable amount of time. For reference, here is how the mis-behaving server I'm dealing with looks like via curl: curl output curl -v -I -m 10 'http://10.21.0.216:8983/solr/wanderful1/select?q=id:1&rows=0&wt=json' About to connect() to 10.21.0.216 port 8983 (#0) Trying 10.21.0.216... Adding handle: conn: 0x7fb9b3004400 Adding handle: send: 0 Adding handle: recv: 0 Curl_addHandleToPipeline: length: 1 - Conn 0 (0x7fb9b3004400) send_pipe: 1, recv_pipe: 0 Connected to 10.21.0.216 (10.21.0.216) port 8983 (#0) > HEAD /solr/wanderful1/select?q=id:1&rows=0&wt=json HTTP/1.1 > User-Agent: curl/7.30.0 > Host: 10.21.0.216:8983 > Accept: / > Operation timed out after 10138 milliseconds with 0 out of -1 bytes received Closing connection 0 curl: (28) Operation timed out after 10138 milliseconds with 0 out of -1 bytes received This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [sitemonitor] (JENKINS-13358) Timeout not working
Mark Edington edited a comment on JENKINS-13358 Timeout not working This issue appears to be addressed by Pull Request #7. I built and tested this fix and it solved the issue where the connection is successful, but the server fails to return a response in a reasonable amount of time. For reference, here is how the mis-behaving server I'm dealing with looks like via curl: curl output curl -v -I -m 10 'http://10.21.0.216:8983/solr/wanderful1/select?q=id:1&rows=0&wt=json' * About to connect() to 10.21.0.216 port 8983 (#0) * Trying 10.21.0.216... * Adding handle: conn: 0x7fb9b3004400 * Adding handle: send: 0 * Adding handle: recv: 0 * Curl_addHandleToPipeline: length: 1 * - Conn 0 (0x7fb9b3004400) send_pipe: 1, recv_pipe: 0 * Connected to 10.21.0.216 (10.21.0.216) port 8983 (#0) > HEAD /solr/wanderful1/select?q=id:1&rows=0&wt=json HTTP/1.1 > User-Agent: curl/7.30.0 > Host: 10.21.0.216:8983 > Accept: */* > * Operation timed out after 10138 milliseconds with 0 out of -1 bytes received * Closing connection 0 curl: (28) Operation timed out after 10138 milliseconds with 0 out of -1 bytes received This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Mark Waite commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials I was able to confirm Hallvard's report that when running Jenkins as a service, it is unable to checkout if the Git URL uses ssh:// (like ssh://wheezy64/var/lib/git/mwaite/bin.git ). I am still able to checkout if the Git URL uses ssh protocol without the ssh:(like g...@github.com:MarkEWaite/jenkins-demo.git ). I am still able to checkout if Jenkins is not running as a service, even when it uses an ssh:// URL. It requires both that it is running as a service and that it is using ssh: protocol. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-17660) Trigger via script does not support LABEL
Dominik Bartholdi commented on JENKINS-17660 Trigger via script does not support LABEL In addition, I altered the code to also support 'value'... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
