[JIRA] [customize-build-now-plugin] (JENKINS-27214) The revised text should also appear on the start button when executing a parameterized job
Kim Nyhjem created JENKINS-27214 The revised text should also appear on the start button when executing a parameterized job Issue Type: Improvement Assignee: Udaypal Aarkoti Components: customize-build-now-plugin Created: 03/Mar/15 7:15 AM Description: The revised text should also appear on the start button when executing a parameterized job. It does not make sense to have the label triggering the build set to "Deploy now" when you still need to press "Build now" after entering run parameters Project: Jenkins Labels: plugin jenkins build label Priority: Major Reporter: Kim Nyhjem 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/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-26387) Since version 1.9, you can’t run only a test (always check “Is target a suite”)
Antoine Aumjaud started work on JENKINS-26387 Since version 1.9, you can’t run only a test (always check “Is target a suite”) Change By: Antoine Aumjaud (03/Mar/15 6:33 AM) Status: Open In Progress 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/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
Ximon Eighteen edited a comment on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException "Request has expired" Hi martinfr62, I have verified that I have not left any files uncommitted, and that the pull request latest commit ID and commit message match what I have locally. I am now using that pull request on several Jenkins instances in AWS and they are all now working. The pull request introduced a "Use old signing mechanism for authenticating request" tick box in the Amazon EC2 Cloud configuration, above the secret key and access key, did you tick that box? Without ticking that box I get authentication errors. It was implied by the original AWS staff member who responded to the forum request about the v4 vs query text signer algorithm issue that the default (v4) signer algorithm should work in most cases and thus I have not made the box ticked by default. However, thinking about it, the previous behaviour of the EC2 plugin was to use the old signer algorithm, so perhaps the old behaviour should be the default? There is currently no description or help for the tick box, I should add that. 'Test Connection' and 'Check AMI' both work for me when the box is ticked. My Jenkins instances are in the EU (Ireland) AWS region. If you could give me the error message and stack trace that would be very appreciated, and please verify that you have tested both with and without ticking the tick box. 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/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-26387) Since version 1.9, you can’t run only a test (always check “Is target a suite”)
Antoine Aumjaud resolved JENKINS-26387 as Fixed Since version 1.9, you can’t run only a test (always check “Is target a suite”) Change By: Antoine Aumjaud (03/Mar/15 6:34 AM) 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/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
Ximon Eighteen edited a comment on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException "Request has expired" Hi martinfr62, I have verified that I have not left any files uncommitted, and that the pull request latest commit ID and commit message match what I have locally. I am now using that pull request on several Jenkins instances in AWS and they are all now working. The pull request introduced a "Use old signing mechanism for authenticating request" tick box in the Amazon EC2 Cloud configuration, above the secret key and access key, did you tick that box? Without ticking that box I get authentication errors, but it was implied by the original AWS staff member who responded to the forum request about the v4 vs query text signer algorithm issue that the default (v4) signer algorithm should work in most cases and thus I have not made the box ticked by default. There is currently no description or help for the tick box, I should add that. 'Test Connection' and 'Check AMI' both work for me when the box is ticked. My Jenkins instances are in the EU (Ireland) AWS region. If you could give me the error message and stack trace that would be very appreciated, and please verify that you have tested both with and without ticking the tick box. 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/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
Ximon Eighteen commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException "Request has expired" Hi martinfr62, I have verified that I have not left any files uncommitted, and that the pull request latest commit ID and commit message match what I have locally. I am now using that pull request on several Jenkins instances in AWS and they are all now working. The pull request introduced a "Use old signing mechanism for authenticating request" tick box in the Amazon EC2 Cloud configuration, above the secret key and access key, did you tick that box? Without ticking that box I get authentication errors, but it was implied by the original AWS staff member who responded to the forum request about the v4 vs query text signer algorithm issue that the default (v4) signer algorithm should work in most cases and thus I have not made the box ticked by default. 'Test Connection' and 'Check AMI' both work for me when the box is ticked. My Jenkins instances are in the EU (Ireland) AWS region. If you could give me the error message and stack trace that would be very appreciated, and please verify that you have tested both with and without ticking the tick box. 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/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-26387) Since version 1.9, you can’t run only a test (always check “Is target a suite”)
SCM/JIRA link daemon commented on JENKINS-26387 Since version 1.9, you can’t run only a test (always check “Is target a suite”) Code changed in jenkins User: Antoine Aumjaud Path: .gitignore src/main/java/hudson/plugins/fitnesse/FitnesseResults.java src/main/java/hudson/plugins/fitnesse/NativePageCounts.java src/test/java/hudson/plugins/fitnesse/NativePageCountsParserTest.java src/test/java/hudson/plugins/fitnesse/NativePageCountsTest.java http://jenkins-ci.org/commit/fitnesse-plugin/cf0644c8fc4dbd377f398d01e2d1db785c052ad6 Log: Merge pull request #22 from antoine-aumjaud/features/FITNESSE-PLUGIN-FixGetDetailOnTestPage Fix JENKINS-26387: can't run a test page only Compare: https://github.com/jenkinsci/fitnesse-plugin/compare/19b742134f0d...cf0644c8fc4d 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/d/optout.
[JIRA] [perforce-plugin] (JENKINS-26839) perforce plugin: exception in parseDateWithTimezone
Oleg Nenashev resolved JENKINS-26839 as Fixed perforce plugin: exception in parseDateWithTimezone 1.3.34 has been released Change By: Oleg Nenashev (03/Mar/15 5:48 AM) 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/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke commented on JENKINS-26776 Jenkins vSphere cloud plugin does not terminate sessions @jswager1 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/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke assigned JENKINS-26776 to Jason Swager Jenkins vSphere cloud plugin does not terminate sessions Change By: Parag Doke (03/Mar/15 5:04 AM) Assignee: Jason Swager 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/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke commented on JENKINS-26776 Jenkins vSphere cloud plugin does not terminate sessions Testing tagging ... @jswager 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/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-26776) Jenkins vSphere cloud plugin does not terminate sessions
Parag Doke commented on JENKINS-26776 Jenkins vSphere cloud plugin does not terminate sessions Jason Swager merged pull request https://github.com/jenkinsci/vsphere-cloud-plugin/pull/26. Don't know the next step. Probably to wait until the next version is out and close this issue after noting the version number? 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/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke updated JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node Change By: Parag Doke (03/Mar/15 4:57 AM) Environment: vsphere-cloud plugin version 2.3build-flow plugin version 0.17Jenkins build 1.599[Java version / OS does not matter] 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/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke created JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 03/Mar/15 4:56 AM Description: Steps 1) Deploy a Jenkins instance from the appropriate war, and get those 2 plugins installed. 2) Configure a test vcenter, a vsphere cloud slave instance (in my case the configuration was: boot on demand, connect via ssh launcher, shut down when idle after 10 min of idle time). 3) Tie a job to the slave and kick it off. I observe that the build simply sits in queue and never kicks off. Environment: vsphere-cloud plugin version 2.3 build-flow plugin version 0.17 Jenkins build 1.599 [Java / OS does not matter] Project: Jenkins Priority: Blocker Reporter: Parag Doke 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
dogfood commented on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Integrated in jenkins_main_trunk #3995 [FIXED JENKINS-26739] Suppress monotonicity assertion for MatrixRun. (Revision 5ada903554a493fcfbc8e23c5c8d02bc50c17845) Result = SUCCESS jesse glick : 5ada903554a493fcfbc8e23c5c8d02bc50c17845 Files : core/src/main/java/hudson/model/RunMap.java 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
Jesse Glick commented on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Should be in 1.601. 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
SCM/JIRA link daemon commented on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/RunMap.java http://jenkins-ci.org/commit/jenkins/6ee6fc3b2f7a9bceca1b04c4af5e6f1b024e2ab4 Log: JENKINS-26739 Backporting #1592 to rc. (cherry picked from commit cf2b02dc58c140aafc4e20115a8bc936d05815be) Conflicts: changelog.html 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
SCM/JIRA link daemon resolved JENKINS-26739 as Fixed ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Change By: SCM/JIRA link daemon (03/Mar/15 1:18 AM) 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
SCM/JIRA link daemon commented on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/RunMap.java http://jenkins-ci.org/commit/jenkins/cf2b02dc58c140aafc4e20115a8bc936d05815be Log: JENKINS-26739 Merging #1592. Compare: https://github.com/jenkinsci/jenkins/compare/87ab95e7fc30...cf2b02dc58c1 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
SCM/JIRA link daemon commented on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/RunMap.java http://jenkins-ci.org/commit/jenkins/5ada903554a493fcfbc8e23c5c8d02bc50c17845 Log: [FIXED JENKINS-26739] Suppress monotonicity assertion for MatrixRun. 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/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-27212) Ability to set github status group
Bill Hwang created JENKINS-27212 Ability to set github status group Issue Type: Improvement Assignee: Honza Brázdil Components: ghprb-plugin Created: 03/Mar/15 1:14 AM Description: Currently the commit status is report to 'default' group. It will be nice if that is settable. See https://github.com/elasticsearch/logstash/pull/2738#issuecomment-76850496 for example. Even if it isn't configuration, 'Build Status' is better than 'default' Project: Jenkins Priority: Minor Reporter: Bill Hwang 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/d/optout.
[JIRA] [git-plugin] (JENKINS-27211) Please add ability to use the git 'clean' options AFTER job execution
Nathan Neulinger
created JENKINS-27211
Please add ability to use the git 'clean' options AFTER job execution
Issue Type:
Improvement
Assignee:
Nicolas De Loof
Components:
git-plugin
Created:
03/Mar/15 1:10 AM
Description:
I would love to be able to have my jobs automatically return the workspace to a clean state after execution - but otherwise leave the cloned repo present at the end of a job automatically. I could do this myself in a post step, but seems like it would be nice to be able to just define this in the SCM section and have it done automatically.
Even better would be ability to say "Clean after job, if: {stable|unstable|failed}" - to allow leaving the workspace around for examination if the job fails, but otherwise clean when done.
Project:
Jenkins
Priority:
Minor
Reporter:
Nathan Neulinger
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/d/optout.
[JIRA] [core] (JENKINS-27188) BUILDID and BUILD_TAG from previous project
dogfood commented on JENKINS-27188 BUILDID and BUILD_TAG from previous project Integrated in jenkins_main_trunk #3994 JENKINS-27188 Picking a better test location for #1590. (Revision e559f39697dad8ee44320b092fc7b32c35ac1eb9) JENKINS-27188 Noting merge of #1590. (Revision 7d6cd1bd5b4675dbbcf1df08eb4760fdaea8dffc) Result = SUCCESS jesse glick : e559f39697dad8ee44320b092fc7b32c35ac1eb9 Files : test/src/test/java/hudson/model/NodeTest.java test/src/test/java/jenkins/tasks/SimpleBuildWrapperTest.java jesse glick : 7d6cd1bd5b4675dbbcf1df08eb4760fdaea8dffc Files : changelog.html 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/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-27119) path attribute in manifest.yml is not evaluated relative to the manifest.yml file
William Gautier commented on JENKINS-27119 path attribute in manifest.yml is not evaluated relative to the manifest.yml file Confirmed, will be fixed in v1.3 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26100) SCM steps should return revision state
Bastian Echterhoelter commented on JENKINS-26100 SCM steps should return revision state Just to mention another workaround on this topic. You can also pipe the current revision into a file and archive that file to be reused later on in the workflow instead of the complete source code. 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/d/optout.
[JIRA] [core] (JENKINS-27178) Execute shell is terminated randomly
Jesse Glick resolved JENKINS-27178 as Fixed Execute shell is terminated randomly Merged, and backported to rc for 1.601. Change By: Jesse Glick (03/Mar/15 12:00 AM) 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/d/optout.
[JIRA] [core] (JENKINS-27178) Execute shell is terminated randomly
SCM/JIRA link daemon commented on JENKINS-27178 Execute shell is terminated randomly Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/Computer.java test/src/test/java/hudson/model/NodeTest.java http://jenkins-ci.org/commit/jenkins/ef4d1553bf12f5ba8d584491f1c118c8797a3846 Log: JENKINS-27178 Amended merge of #1590. (cherry picked from commit 87ab95e7fc30af0d20a2bfe6a977fa2da7d15dba) 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/d/optout.
[JIRA] [core] (JENKINS-27188) BUILDID and BUILD_TAG from previous project
SCM/JIRA link daemon commented on JENKINS-27188 BUILDID and BUILD_TAG from previous project Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/7d6cd1bd5b4675dbbcf1df08eb4760fdaea8dffc Log: JENKINS-27188 Noting merge of #1590. 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/d/optout.
[JIRA] [core] (JENKINS-27188) BUILDID and BUILD_TAG from previous project
SCM/JIRA link daemon commented on JENKINS-27188 BUILDID and BUILD_TAG from previous project Code changed in jenkins User: Jesse Glick Path: test/src/test/java/hudson/model/NodeTest.java test/src/test/java/jenkins/tasks/SimpleBuildWrapperTest.java http://jenkins-ci.org/commit/jenkins/e559f39697dad8ee44320b092fc7b32c35ac1eb9 Log: JENKINS-27188 Picking a better test location for #1590. 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/d/optout.
[JIRA] [core] (JENKINS-27178) Execute shell is terminated randomly
Jesse Glick assigned JENKINS-27178 to Johno Crawford Execute shell is terminated randomly Change By: Jesse Glick (02/Mar/15 11:42 PM) Assignee: Nicolas De Loof Johno Crawford 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/d/optout.
[JIRA] [core] (JENKINS-27188) BUILDID and BUILD_TAG from previous project
Jesse Glick resolved JENKINS-27188 as Duplicate BUILDID and BUILD_TAG from previous project Change By: Jesse Glick (02/Mar/15 11:40 PM) Status: Open Resolved Resolution: Duplicate 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/d/optout.
[JIRA] [core] (JENKINS-27199) Invoke Ant fails in 1.600
Jesse Glick resolved JENKINS-27199 as Duplicate Invoke Ant fails in 1.600 Change By: Jesse Glick (02/Mar/15 11:35 PM) Status: Open Resolved Resolution: Duplicate 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
SCM/JIRA link daemon commented on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Code changed in jenkins User: Jesse Glick Path: src/test/java/hudson/matrix/MatrixProjectTest.java http://jenkins-ci.org/commit/matrix-project-plugin/5f011e8f2718937295584cdf1101941631d6e7ec Log: JENKINS-26739 Suppress testConcurrentBuild until we can pick up a fix. 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27210) Ability to add a descriptive text to a shell script execution that gets displayed in the Running Steps perspective
Bastian Echterhoelter created JENKINS-27210 Ability to add a descriptive text to a shell script execution that gets displayed in the Running Steps perspective Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 02/Mar/15 11:16 PM Description: When working with a workflow that has many shell scripts it is very hard to see in the "Runnning Steps" perspective what each of them does to identify the one that one is looking for. It would be great to be able to drive the display of Shell Scripts in this perspective by either providing a text or possibly displaying the shell command executed. Project: Jenkins Priority: Minor Reporter: Bastian Echterhoelter 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/d/optout.
[JIRA] [core] (JENKINS-27199) Invoke Ant fails in 1.600
Chris Sullens commented on JENKINS-27199 Invoke Ant fails in 1.600 the dropbox war fixed my problem...the jobs are successful again. thanks for the help! 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/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
martinfr62 edited a comment on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException "Request has expired" Tried pulling 131 and patching current master - it fails to connect to aws. Pulled current master - built and depoyed - connects okay (but has normal bug in it) Pulled 131 and split the patch in two - first half (ie prior 131) works - can connect to aws Apply second patch as a straight merge - and it builds - but cannot connect Next tried pull master, apply first half - and then apply my patch alone - this works. Looks like something in the second patch causes aws to fail. Let me know if you need a stack trace or anything if you cannot reproduce - but happens every time for me. Try executing 'Test Connection' from jenkins config page for ec2 - fails immediately for both profile and real keys. 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/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
martinfr62 commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException "Request has expired" Tried pulling 131 and patching current master - it fails to connect to aws. Pulled current master - built and depoyed - connects okay (but has normal bug in it) Pulled 131 and split the patch in two - first half (ie prior 131) works - can connect to aws Apply second patch as a straight merge - and it builds - but cannot connect Next tried pull master, apply firt half - and then apply my patch alone - this works. Looks like something in the second patch causes aws to fail. Let me know if you need a stack trace or anything if you cannot reproduce - but happens every time for me. Try executing 'Test Connection' from jenkins config page for ec2 - fails immediately for both profile and real keys. 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/d/optout.
[JIRA] [core] (JENKINS-26582) ISE from RunMap.put after reloading config
Jesse Glick commented on JENKINS-26582 ISE from RunMap.put after reloading config I am guessing the reload operation caused the problem. Do you happen to know how to reproduce? 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
Jesse Glick updated JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Change By: Jesse Glick (02/Mar/15 11:00 PM) Summary: Executors are dying since 1 ISE from AbstractLazyLoadRunMap . 597 - related to the directory layout change? proposeNewNumber for concurrent matrix builds Labels: regression 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/d/optout.
[JIRA] [core] (JENKINS-26582) ISE from RunMap.put after reloading config
Jesse Glick updated JENKINS-26582 ISE from RunMap.put after reloading config Change By: Jesse Glick (02/Mar/15 11:01 PM) Summary: Unexpected Executor Death - build already existed - 1 ISE from RunMap . 597 put after reloading config Description: Jan 23, 2015 11:43:52 PM hudson.model.Executor runSEVERE: Unexpected executor deathjava.lang.IllegalStateException: /MY_DIR/jenkins/home/jobs/MY_JOB/builds/29 already existed; will not overwite with MY_JOB #29 at hudson.model.RunMap.put(RunMap.java:187) at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178) at hudson.model.AbstractProject.newBuild(AbstractProject.java:1001) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1200) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) at hudson.model.Executor.run(Executor.java:213)I tried to manually start a job via the run button. I see the Dead(!) indicator in the executor status sidebar. I was able to restart the thread and then manually start the job again. This time it started with #30 and appears to be running OK.Looking at JENKINS_HOME dir in linux, I see that there is a build directory for #29 and the job ran and failed (unrelated). Looking at the Jenkins webpage for the job, the build skips from 28 to (the now running) 30. #29 has no listing.I know some items related to the major enhancement are not closed yet, like JENKINS-23152, so please close this if the behavior I'm seeing is expected until the next release. If this is unexpected - hopefully this report is informative - this issue happened 4x in a row for each job I had put in the build queue. Labels: regression Assignee: 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/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-26616) Multi-config project concurrent build race
Jesse Glick resolved JENKINS-26616 as Duplicate Multi-config project concurrent build race Change By: Jesse Glick (02/Mar/15 10:57 PM) Status: Open Resolved Assignee: rsandell Jesse Glick Resolution: Duplicate 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/d/optout.
[JIRA] [core] (JENKINS-27199) Invoke Ant fails in 1.600
Daniel Beck commented on JENKINS-27199 Invoke Ant fails in 1.600 In the comments to JENKINS-27178 I link to a jenkins war on my Dropbox. I also link to a Github branch with a fix so you could build it yourself. 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/d/optout.
[JIRA] [cmakebuilder-plugin] (JENKINS-27203) Broken env variable replacing
A. Klitzing commented on JENKINS-27203 Broken env variable replacing https://github.com/jenkinsci/cmakebuilder-plugin/pull/2 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/d/optout.
[JIRA] [google-login-plugin] (JENKINS-26279) google login plugin just shows a alert message on top asking username password
Thien Nguyen commented on JENKINS-26279 google login plugin just shows a alert message on top asking username password Hello, I am also having this issue but I'm not using a proxy at all. I am currently testing in a Vagrant VM. Below is the curl output. I am using Jenkins 1.600, OpenJDK 7u75, and Ubuntu Linux 14.04. Thanks for the plugin and any thoughts you could provide to debug the issue if it's on my end. vagrant@default-ubuntu-1404:/var/lib/jenkins$ curl http://localhost:8080/jenkins -v * Hostname was NOT found in DNS cache * Trying ::1... * Connected to localhost (::1) port 8080 (#0) > GET /jenkins HTTP/1.1 > User-Agent: curl/7.35.0 > Host: localhost:8080 > Accept: */* > < HTTP/1.1 302 Found < Location: http://localhost:8080/jenkins/ < Content-Length: 0 * Server Jetty(winstone-2.8) is not blacklisted < Server: Jetty(winstone-2.8) < * Connection #0 to host localhost left intact System Properties awt.toolkit sun.awt.X11.XToolkit executable-war /usr/share/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-7-openjdk-amd64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.7.0_75-b13 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_75 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.75-b04 jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib jnidispatch.path /tmp/jna--1712433994/jna4332158744456668839.tmp lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate lib.svnkit.ssh2.persistent false line.separator mail.smtp.sendpartial true mail.smtp.starttls.enable true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.13.0-24-generic path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rhino.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jfr.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/classes sun.boot.library.path /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpListenAddress=0.0.0.0 --httpPort=8080 --ajp13Port=-1 --prefix=/jenkins sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone America/New_York Plugins are all updated to latest. active-directory ant antisamy-markup-formatter bitbucket build-user-vars-plugin config-file-provider copyartifact credentials cvs email-ext external-monitor-job git git-client google-login javadoc jenkins-cloudformation-plugin junit ldap mailer managed-scripts mapdb-api matrix-auth matrix-project maven-plugin mercurial multiple-scms pam-auth parameterized-trigger postbuild-task promoted-builds s3 sbt scala-junit-name-decoder scm-api script-security skip-certificate-check ssh-credentials ssh-slaves subversion text-finder token-macro translation windows-slaves
[JIRA] [core] (JENKINS-27188) BUILDID and BUILD_TAG from previous project
Jesse Glick assigned JENKINS-27188 to Nicolas De Loof BUILDID and BUILD_TAG from previous project Change By: Jesse Glick (02/Mar/15 10:02 PM) Assignee: Nicolas De Loof 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/d/optout.
[JIRA] [core] (JENKINS-27188) BUILDID and BUILD_TAG from previous project
Jesse Glick updated JENKINS-27188 BUILDID and BUILD_TAG from previous project Change By: Jesse Glick (02/Mar/15 10:03 PM) Labels: regression 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/d/optout.
[JIRA] [core] (JENKINS-27178) Execute shell is terminated randomly
Jesse Glick updated JENKINS-27178 Execute shell is terminated randomly Change By: Jesse Glick (02/Mar/15 10:03 PM) Labels: regression 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/d/optout.
[JIRA] [google-login-plugin] (JENKINS-27117) google login plugin not working
recampbell commented on JENKINS-27117 google login plugin not working oeuftete, I suppose a workaround is to create an api key and secret in the target Google apps domain. Is that an option? I agree it isn't ideal. My guess (from looking at the code) is that there is an error that is being swallowed by the oauth library I'm using (ironically, one from Google). So I need to tease out the error code and return or log that somewhere. 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/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-27146) Deploying an applicatin w/ "no-route" fails because route deletion fails
William Gautier commented on JENKINS-27146 Deploying an applicatin w/ "no-route" fails because route deletion fails No problem! 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/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-27146) Deploying an applicatin w/ "no-route" fails because route deletion fails
Andreas Buchen commented on JENKINS-27146 Deploying an applicatin w/ "no-route" fails because route deletion fails Sorry for not answering earlier. I got a quite busy schedule and won't come around to this before Thursday. If you have time, I'd appreciate if you fix 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/d/optout.
[JIRA] [claim-plugin] (JENKINS-27206) Enable claim support from workflow
Nigel Harniman updated JENKINS-27206 Enable claim support from workflow Change By: Nigel Harniman (02/Mar/15 9:32 PM) Labels: workflow 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/d/optout.
[JIRA] [google-login-plugin] (JENKINS-27117) google login plugin not working
oeuftete edited a comment on JENKINS-27117 google login plugin not working Seeing an identical problem. Things were working fine, but I'm trying to migrate our URL to a different domain than the Google Apps domain doing the authenticating, and that's when the problem started. Looks like the OP has a similar configuration. Edit: My Jenkins version is 1.580.3. 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/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27209) Enable reporting of compiler warnings in workflow steps
Nigel Harniman created JENKINS-27209 Enable reporting of compiler warnings in workflow steps Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-plugin Created: 02/Mar/15 9:26 PM Description: Enable generation of trend report data on compiler warnings from workflow build steps. Handle multiple compiles in a workflow. Project: Jenkins Priority: Major Reporter: Nigel Harniman 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/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27209) Enable reporting of compiler warnings in workflow steps
Nigel Harniman updated JENKINS-27209 Enable reporting of compiler warnings in workflow steps Change By: Nigel Harniman (02/Mar/15 9:26 PM) Labels: workflow 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/d/optout.
[JIRA] [log-parser-plugin] (JENKINS-27208) Add workflow compatibility to log-parser
Nigel Harniman created JENKINS-27208 Add workflow compatibility to log-parser Issue Type: New Feature Assignee: rgoren Components: log-parser-plugin Created: 02/Mar/15 9:19 PM Description: highlighting lines of interest in workflow logs (errors, warnings, information) dividing the log into sections based on stages and parallel executions displaying a summary of number of errors , warnings and information lines within the workflow log and its sections. linking the summary of errors and warnings into the context of the full workflow log, making it easy to find a line of interest in the log showing a summary of errors and warnings on the build page Project: Jenkins Labels: workflow Priority: Minor Reporter: Nigel Harniman 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/d/optout.
[JIRA] [timestamper-plugin] (JENKINS-27207) Add timestamps to workflow console output
Nigel Harniman created JENKINS-27207 Add timestamps to workflow console output Issue Type: New Feature Assignee: stevengbrown Components: timestamper-plugin Created: 02/Mar/15 9:12 PM Description: Add timestamps to workflow job output Project: Jenkins Labels: workflow Priority: Major Reporter: Nigel Harniman 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
Jesse Glick started work on JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock Change By: Jesse Glick (02/Mar/15 9:06 PM) Status: Open In Progress 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27180) Upgrade to version 1.600 broke GIT plugin
Mark Waite edited a comment on JENKINS-27180 Upgrade to version 1.600 broke GIT plugin I have the same problem on my Jenkins 1.580.3 installation at the office. The fix appears to be reasonably straightforward. It is unclear to me what changed that caused this to become visible now when it was previously not visible. 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27180) Upgrade to version 1.600 broke GIT plugin
Mark Waite edited a comment on JENKINS-27180 Upgrade to version 1.600 broke GIT plugin I have the same problem on my Jenkins 1.580.3 installation at the office. The fix appears to be [reasonably straightforward](https://github.com/MarkEWaite/git-plugin/commit/ec64289ec2933a5ff61c9c9dc2e86ea7c276e582). It is unclear to me what changed that caused this to become visible now when it was previously not visible. 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/d/optout.
[JIRA] [claim-plugin] (JENKINS-27206) Enable claim support from workflow
Nigel Harniman created JENKINS-27206 Enable claim support from workflow Issue Type: New Feature Assignee: Christian Bremer Components: claim-plugin Created: 02/Mar/15 9:02 PM Description: It should be possible to claim failed workflow builds. Project: Jenkins Priority: Major Reporter: Nigel Harniman 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/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-27205) Jenkins raised java.net.SocketTimeoutException: Read timed out when start FitNesse on remote VM
Heng Wang created JENKINS-27205 Jenkins raised java.net.SocketTimeoutException: Read timed out when start FitNesse on remote VM Issue Type: Bug Assignee: Unassigned Components: fitnesse-plugin Created: 02/Mar/15 8:59 PM Description: I'm having a slave node to run the FitNesse test cases using the FitNesse plugin. However when the executing time of test suite is long (over 20 minutes), Jenkins will raise the Java read timed out Exception during the executing time, and the jenkins job is failed. This seems to be a known issue in the FitNesse plugin, and it has been raised for a long time. Hope this bug could be resolved ASAP. Issue raised before: https://issues.jenkins-ci.org/browse/JENKINS-18501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel Environment: Jenkins ver. 1.480.3 on SUSE 11 Project: Jenkins Labels: jenkins plugin fitnesse java exception readtimeout Priority: Critical Reporter: Heng Wang 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/d/optout.
[JIRA] [core] (JENKINS-27188) BUILDID and BUILD_TAG from previous project
John McClane
commented on JENKINS-27188
BUILDID and BUILD_TAG from previous project
We are using the Build Flow plugin and the build numbers are not being passed correctly after upgrading to 1.600.
build_job1 = build("Build 1")
build_job2 = build("Build 2")
deploy_job = build("Deploy", DEPLOY_BUILD_NUMBER: build_job2.build.number)
When the "Deploy" job runs in this instance, the DEPLOY_BUILD_NUMBER environment variable is the one from build_job1 instead of build_job2. I realize this thread is not about the Build Flow Plugin but I'm guessing the root cause is the same.
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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26513) Deserialization error of ExecutorStepExecution
SCM/JIRA link daemon commented on JENKINS-26513 Deserialization error of ExecutorStepExecution Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/8fe11e081785d6b2a901edcd9792942aa909064b Log: Merge pull request #62 from jglick/ExecutorStepExecution-deser-JENKINS-26513 JENKINS-26513 Deserialization error in ExecutorStepExecution Compare: https://github.com/jenkinsci/workflow-plugin/compare/e850c8c6c97c...8fe11e081785 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
SCM/JIRA link daemon commented on JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java http://jenkins-ci.org/commit/workflow-plugin/f94559d5f48c794c836ee2d80e93a13fbb6c6ed6 Log: JENKINS-25890 causing problems for this test. 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26513) Deserialization error of ExecutorStepExecution
SCM/JIRA link daemon resolved JENKINS-26513 as Fixed Deserialization error of ExecutorStepExecution Change By: SCM/JIRA link daemon (02/Mar/15 8:57 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26513) Deserialization error of ExecutorStepExecution
SCM/JIRA link daemon commented on JENKINS-26513 Deserialization error of ExecutorStepExecution Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/aac402a592ed8c1e2b6cc4f04a0055c910954a21 Log: [FIXED JENKINS-26513] Deserialization error in ExecutorStepExecution. 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/d/optout.
[JIRA] [core] (JENKINS-27199) Invoke Ant fails in 1.600
Chris Sullens commented on JENKINS-27199 Invoke Ant fails in 1.600 I'd be happy to test...my server is ubuntu, if you could point me to a download I'll give it a shot 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/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-18501) Fitnesse Plugin - java.net.SocketTimeoutException: Read timed out
Heng Wang stopped work on JENKINS-18501 Fitnesse Plugin - java.net.SocketTimeoutException: Read timed out Change By: Heng Wang (02/Mar/15 8:42 PM) Status: In Progress Open 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/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-18501) Fitnesse Plugin - java.net.SocketTimeoutException: Read timed out
Heng Wang started work on JENKINS-18501 Fitnesse Plugin - java.net.SocketTimeoutException: Read timed out Change By: Heng Wang (02/Mar/15 8:42 PM) Status: Open In Progress 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26123) Non-blocking build trigger step
SCM/JIRA link daemon resolved JENKINS-26123 as Fixed Non-blocking build trigger step Change By: SCM/JIRA link daemon (02/Mar/15 8:40 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26123) Non-blocking build trigger step
SCM/JIRA link daemon commented on JENKINS-26123 Non-blocking build trigger step Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/config.jelly http://jenkins-ci.org/commit/workflow-plugin/cb8b5cc327a0d23f9b9fadfe1e7422d910c6b126 Log: [FIXED JENKINS-26123] BuildTriggerStep.wait 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26123) Non-blocking build trigger step
SCM/JIRA link daemon commented on JENKINS-26123 Non-blocking build trigger step Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/config.jelly http://jenkins-ci.org/commit/workflow-plugin/e850c8c6c97cf4a93cd7286c62ee2699c7d1626f Log: Merge pull request #63 from jglick/BuildTriggerStep.wait-JENKINS-26123 JENKINS-26123 Non-blocking build trigger step Compare: https://github.com/jenkinsci/workflow-plugin/compare/1feac3ecba68...e850c8c6c97c 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27180) Upgrade to version 1.600 broke GIT plugin
Mark Waite commented on JENKINS-27180 Upgrade to version 1.600 broke GIT plugin I have the same problem on my Jenkins 1.580.3 installation at the office. The fix appears to be reasonably straightforward. It is unclear to me what changed that caused this to become visible now when it was previously not visible. 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/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-27146) Deploying an applicatin w/ "no-route" fails because route deletion fails
William Gautier commented on JENKINS-27146 Deploying an applicatin w/ "no-route" fails because route deletion fails Would you prefer to update your pull request or should I fix this problem? 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/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-25884) configure name of manifest.yml
William Gautier started work on JENKINS-25884 configure name of manifest.yml Change By: William Gautier (02/Mar/15 8:32 PM) Status: Open In Progress 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/d/optout.
[JIRA] [mstest-plugin] (JENKINS-21899) tests that return a status of Error are not being reported as such
Ivo Bellin Salarin resolved JENKINS-21899 as Duplicate tests that return a status of Error are not being reported as such Robert Kozlowski said this is a duplicate of the https://issues.jenkins-ci.org/browse/JENKINS-18265 issue. Change By: Ivo Bellin Salarin (02/Mar/15 8:27 PM) Status: Open Resolved Assignee: acmarques Ivo Bellin Salarin Resolution: Duplicate 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/d/optout.
[JIRA] [git-plugin] (JENKINS-27191) Support bare clone
Mark Waite commented on JENKINS-27191 Support bare clone Good suggestion. Jesse Glick implemented something similar in the Mercurial plugin. The Mercurial plugin copies to a central location on the Jenkins server, then uses the Jenkins slave communication system to transfer the repository to slaves as needed. 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/d/optout.
[JIRA] [core] (JENKINS-27199) Invoke Ant fails in 1.600
Daniel Beck commented on JENKINS-27199 Invoke Ant fails in 1.600 Would be interesting if any of you could test the build (or build from my branch) that fixes JENKINS-27178 to see whether this is related. I cannot see any other related changes in the source code. At least Chris Sullens also has env-inject installed. 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/d/optout.
[JIRA] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
SCM/JIRA link daemon commented on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly http://jenkins-ci.org/commit/jenkins/56795ba1f30ea9f060c9bb1e302fcff9827dd947 Log: [FIXED JENKINS-22311] Show queue item parameters in tool tip (cherry picked from commit 44e6b5d76211bc40e1a608ae3aa93c083befaeba) 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/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
SCM/JIRA link daemon commented on JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/JDK.java http://jenkins-ci.org/commit/jenkins/bf6859f059bc809a8b1bae6ef184af56a37f79e0 Log: [FIXED JENKINS-25601] Amend JAVA_HOME check to work with JDK 9 (cherry picked from commit 1186e7b4047a70162a1a3be399fc449ae3b0e1f5) 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/d/optout.
[JIRA] [core] (JENKINS-27199) Invoke Ant fails in 1.600
Chris Sullens commented on JENKINS-27199 Invoke Ant fails in 1.600 Same sort of error on all of my linux jobs (my 1 windows job is ok). No changes to the project, just started failing after 1.600 update. For example: 14:47:00 Started by timer 14:47:00 [EnvInject] - Loading node environment variables. 14:47:00 Building on master in workspace /var/lib/jenkins/jobs/Remove Empty Folders - SEALSBUNTU - sabnzbd/workspace 14:47:00 $ hg --config auth.jenkins.prefix=* --config --config --config "auth.jenkins.schemes=http https" clone --rev default --noupdate http://sealsbuntu:5000/Jenkins-Repo "/var/lib/jenkins/jobs/Remove Empty Folders - SEALSBUNTU - sabnzbd/workspace" 14:47:00 ERROR: Failed to clone http://sealsbuntu:5000/Jenkins-Repo 14:47:00 java.io.IOException: Cannot run program "hg": error=7, Argument list too long 14:47:00 at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047) 14:47:00 at hudson.Proc$LocalProc.(Proc.java:244) 14:47:00 at hudson.Proc$LocalProc.(Proc.java:216) 14:47:00 at hudson.Launcher$LocalLauncher.launch(Launcher.java:803) 14:47:00 at hudson.Launcher$ProcStarter.start(Launcher.java:381) 14:47:00 at hudson.Launcher$ProcStarter.join(Launcher.java:388) 14:47:00 at hudson.plugins.mercurial.MercurialSCM.clone(MercurialSCM.java:779) 14:47:00 at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:547) 14:47:00 at hudson.scm.SCM.checkout(SCM.java:484) 14:47:00 at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) 14:47:00 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) 14:47:00 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 14:47:00 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) 14:47:00 at hudson.model.Run.execute(Run.java:1717) 14:47:00 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 14:47:00 at hudson.model.ResourceController.execute(ResourceController.java:89) 14:47:00 at hudson.model.Executor.run(Executor.java:240) 14:47:00 Caused by: java.io.IOException: error=7, Argument list too long 14:47:00 at java.lang.UNIXProcess.forkAndExec(Native Method) 14:47:00 at java.lang.UNIXProcess.(UNIXProcess.java:186) 14:47:00 at java.lang.ProcessImpl.start(ProcessImpl.java:130) 14:47:00 at java.lang.ProcessBuilder.start(ProcessBuilder.java:1028) 14:47:00 ... 16 more 14:47:00 ERROR: Failed to clone http://sealsbuntu:5000/Jenkins-Repo 14:47:00 [BFA] Scanning build for known causes... 14:47:00 14:47:00 [BFA] Done. 0s 14:47:00 Collecting metadata... 14:47:00 Metadata collection done. 14:47:00 Started calculate disk usage of build 14:47:00 Finished Calculation of disk usage of build in 0 seconds 14:47:00 Started calculate disk usage of workspace 14:47:00 Finished Calculation of disk usage of workspace in 0 seconds 14:47:00 Finished: FAILURE 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/d/optout.
[JIRA] [core] (JENKINS-25897) Infinite loop with crontab "H H(19-24) * * *"
SCM/JIRA link daemon commented on JENKINS-25897 Infinite loop with crontab "H H(19-24) * * *" Code changed in jenkins User: Daniel Beck Path: core/src/test/java/hudson/scheduler/CronTabTest.java http://jenkins-ci.org/commit/jenkins/b7ccd6bb14becb51a5df9ebf043d28323abd538a Log: JENKINS-25897 Add tests (cherry picked from commit b090751c16242402ad2187292e40f0f7bd5bbe10) 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/d/optout.
[JIRA] [core] (JENKINS-25897) Infinite loop with crontab "H H(19-24) * * *"
SCM/JIRA link daemon commented on JENKINS-25897 Infinite loop with crontab "H H(19-24) * * *" Code changed in jenkins User: Daniel Beck Path: core/src/main/grammar/crontab.g core/src/main/java/hudson/scheduler/BaseParser.java http://jenkins-ci.org/commit/jenkins/6e67cb9e28707c19ded5c5c5c301ffe179ed5d64 Log: [FIXED JENKINS-25897] Add range check for H(X-Y) syntax (cherry picked from commit 9a8329ebfe6b713acd8c6e42de095e44cd126f2c) 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/d/optout.
[JIRA] [core] (JENKINS-10944) MatrixProject can run on a heavyweight executor, leading to deadlocks
SCM/JIRA link daemon commented on JENKINS-10944 MatrixProject can run on a heavyweight executor, leading to deadlocks Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/LoadBalancer.java core/src/main/java/hudson/model/Queue.java core/src/main/java/jenkins/model/Jenkins.java test/src/test/java/hudson/model/QueueTest.java http://jenkins-ci.org/commit/jenkins/ff26bb8a18c62a4cd008cfff935166e38ee94f6a Log: JENKINS-10944 Merge branch 'master' into FlyweightTask-JENKINS-10944 (cherry picked from commit 1a80973ab875d12c3eda61ebb25850795d9cb6d6) 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/d/optout.
[JIRA] [core] (JENKINS-26365) Animated ball in job's build history widget won't open Console Output
SCM/JIRA link daemon commented on JENKINS-26365 Animated ball in job's build history widget won't open Console Output Code changed in jenkins User: tfennelly Path: war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/4c4fb74043fa264a29d83d63d77cbb96de83d840 Log: [FIXED JENKINS-26365] Animated ball in job's build history widget won't open Console Output (cherry picked from commit 1dd60ec7780870f9c11686659178e52d251c15fc) Conflicts: changelog.html Compare: https://github.com/jenkinsci/jenkins/compare/dd2083aa4734...4c4fb74043fa 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/d/optout.
[JIRA] [core] (JENKINS-27178) Execute shell is terminated randomly
Johno Crawford commented on JENKINS-27178 Execute shell is terminated randomly Pull request here https://github.com/jenkinsci/jenkins/pull/1590 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/d/optout.
[JIRA] [core] (JENKINS-27199) Invoke Ant fails in 1.600
Kanstantsin Shautsou
updated JENKINS-27199
Invoke Ant fails in 1.600
Change By:
Kanstantsin Shautsou
(02/Mar/15 7:50 PM)
Description:
After updating from 1.599 to 1.600 no ant build works anymore with the following stack, Let me know if any additional information is required. Reverting to 1.599 resolves the issue.
{code}
[Common_Restore] $ cmd.exe /C '"ant.bat -file build.xml -Djenkins.managed=true -DjarOutputDir=C:\jenkins\workspace\12_Common_Restore/workspace -DarchiveDir=C:\jenkins\workspace\12_Common_Restore/archive -DPROJECTS_SRC=C:\jenkins\workspace\12_Common_Restore -DPROJECTS_LIB=C:\jenkins\workspace\Common_Libs\lib && exit %%ERRORLEVEL%%"'The filename or extension is too longFATAL: command execution failed.Maybe you need to configure the job to choose one of your Ant installations?java.io.IOException: Cannot run program "cmd.exe" (in directory "C:\jenkins\workspace\12_Common_Restore\build\Common_Restore"): CreateProcess error=206, The filename or extension is too long at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:803) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1136) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ..remote call to WINDOWS-AQGP48S-87.244(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:916) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$ProcStarter.join(Launcher.java:388) at hudson.tasks.Ant.perform(Ant.java:217) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1717) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)Caused by: java.io.IOException: CreateProcess error=206, The filename or extension is too long at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:803) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1136) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source)Build step 'Invoke Ant' marked build as failure
{code}
[JIRA] [crowd2-plugin] (JENKINS-27070) Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration"
kutsal commented on JENKINS-27070 Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration" This is happening with us as well; Jenkins 1.600; about 1 per second, and the JVM running Jenkins ends up at 100% CPU which makes Jenkins unusable. Mar 02, 2015 1:51:18 PM org.apache.commons.httpclient.MultiThreadedHttpConnectionManager freeConnection SEVERE: Host connection pool not found, hostConfig=HostConfiguration[host=https://crowd.xxx.com] Mar 02, 2015 1:51:19 PM org.apache.commons.httpclient.MultiThreadedHttpConnectionManager freeConnection SEVERE: Host connection pool not found, hostConfig=HostConfiguration[host=https://crowd.xxx.com] 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/d/optout.
[JIRA] [core] (JENKINS-27204) "hudson.util.ProcessTree.enabled" keeps changing to "false" in Windows nodes
Diogo Campos commented on JENKINS-27204 "hudson.util.ProcessTree.enabled" keeps changing to "false" in Windows nodes Whenever we start the slave, we configure that flag. Maybe the slave lost connection and reconnected automatically (using slave.jar mechanism, nothing on our part), would that be something that could cause 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/d/optout.
[JIRA] [core] (JENKINS-27204) "hudson.util.ProcessTree.enabled" keeps changing to "false" in Windows nodes
Daniel Beck commented on JENKINS-27204 "hudson.util.ProcessTree.enabled" keeps changing to "false" in Windows nodes Are you sure the slave isn't just restarting? Recent Windows Slaves should be configured to restart their own process when they lose the connection. 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/d/optout.
[JIRA] [core] (JENKINS-27204) "hudson.util.ProcessTree.enabled" keeps changing to "false" in Windows nodes
Diogo Campos created JENKINS-27204 "hudson.util.ProcessTree.enabled" keeps changing to "false" in Windows nodes Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Mar/15 6:00 PM Description: In order to get my Windows nodes to correctly kill all processes and subprocess when a build is aborted I had to make sure that all processes have a BUILD_ID environment variable, and that all nodes have hudson.util.ProcessTree.enabled=true. The problem is that every once in a while, nodes that I had previously configured with hudson.util.ProcessTree.enabled=true will revert to false. I'm configuring that option via Script Console in node page whenever it changes to false, and I was not able to find anything in Jenkins logs, nor the node command line (started by running java -jar slave.jar). This problem does not occur in Unix nodes. Environment: Jenkins ver. 1.599 Project: Jenkins Priority: Minor Reporter: Diogo Campos 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/d/optout.
[JIRA] [compress-artifacts-plugin] (JENKINS-27042) java.util.zip.ZipException thrown when reading artifacts from archive larger than 4G
Oliver Gondža resolved JENKINS-27042 as Fixed java.util.zip.ZipException thrown when reading artifacts from archive larger than 4G Fixed in 1.4 Change By: Oliver Gondža (02/Mar/15 5:42 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/d/optout.
[JIRA] [configurationslicing-plugin] (JENKINS-21225) Configuration Slicing for Editable Email Notification not working anymore with latest versions
Ninian commented on JENKINS-21225 Configuration Slicing for Editable Email Notification not working anymore with latest versions Should be fixed by https://github.com/jenkinsci/configurationslicing-plugin/pull/15 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/d/optout.
[JIRA] [core] (JENKINS-27188) BUILDID and BUILD_TAG from previous project
Adrian Kirchner
commented on JENKINS-27188
BUILDID and BUILD_TAG from previous project
Same here. We're using vars like ${env.BUILD_NUMBER} in ANT Buildscripts to tag builds in vcs. Since we upgraded to 1.600 these vars are filled with the information from the last build in the whole Jenkins instance (job independent).
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/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-10706) MERCURIAL_BRANCH environment variable
A. Klitzing commented on JENKINS-10706 MERCURIAL_BRANCH environment variable https://github.com/jenkinsci/mercurial-plugin/pull/62 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/d/optout.
[JIRA] [cmakebuilder-plugin] (JENKINS-27203) Broken env variable replacing
A. Klitzing assigned JENKINS-27203 to volkai Broken env variable replacing Change By: A. Klitzing (02/Mar/15 5:17 PM) Assignee: volkai 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/d/optout.
[JIRA] [cmakebuilder-plugin] (JENKINS-27203) Broken env variable replacing
A. Klitzing created JENKINS-27203 Broken env variable replacing Issue Type: Bug Assignee: Unassigned Components: cmakebuilder-plugin Created: 02/Mar/15 5:16 PM Description: If I use environment variables in "Other CMake Arguments" it will replace the variables in an incorrect order. It needs to replace long names before short names. Example: The following variables exists: MERCURIAL_REVISION = 0c775e18b569d4c5b505bd5fb73b854d700247d8 MERCURIAL_REVISION_BRANCH = default MERCURIAL_REVISION_NUMBER = 5543 MERCURIAL_REVISION_SHORT = 0c775e18 If I use _BRANCH, _NUMBER or _SHORT it will replace half of the variable with the content of MERCURIAL_REVISION: "0c775e18b569d4c5b505bd5fb73b854d700247d8_NUMBER" instead of "5543" Project: Jenkins Priority: Major Reporter: A. Klitzing 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/d/optout.
[JIRA] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
pmv commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name FYI for any others searching Jira - in my testing the issue Antoine identifies 3 comments above and Jean created the pull request for is no longer an issue in version 2.3.5 of the 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/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-27201) Failed to transfer Could not find artifact
Daniel Beck resolved JENKINS-27201 as Not A Defect Failed to transfer Could not find artifact This is an issue tracker, not a support website. And for a bug report, this contains not nearly enough information. Change By: Daniel Beck (02/Mar/15 5:05 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/d/optout.
[JIRA] [git-plugin] (JENKINS-27166) CLONE - Git SCM-polling doesn't work when using a parametrized branch-name
pmv commented on JENKINS-27166 CLONE - Git SCM-polling doesn't work when using a parametrized branch-name I'm not sure which change did it, but this seems to be resolved in 2.3.5. 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/d/optout.
