[JIRA] (JENKINS-16435) implements an easier way to set verbose mode
Antoine Musso created JENKINS-16435 implements an easier way to set verbose mode Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 22/Jan/13 7:56 AM Description: When using the git plugin, the console output might be mind-boggling because it does not gives enough details. The plugin has support for more verbosity in the console log by starting Jenkins with the java parameter -Dhudson.plugins.git.GitSCM.verbose="true" The relevant code in GitSCM.java : public static boolean VERBOSE = Boolean.getBoolean(GitSCM.class.getName() + ".verbose"); This has already saved me a lot of time once I have discovered this switch. Would it be possible to add an option to enable this globally and another option to enable verbosity on a per job basis? I guess the default will be non verbose. Project: Jenkins Priority: Major Reporter: Antoine Musso 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
[JIRA] (JENKINS-13654) Showing attributes in testng results
Nalin Makar updated JENKINS-13654 Showing attributes in testng results Change By: Nalin Makar (22/Jan/13 7:53 AM) Assignee: nalin_makar Nalin Makar 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
[JIRA] (JENKINS-10100) Replace build-in test graphs with the TestNG ones
Nalin Makar updated JENKINS-10100 Replace build-in test graphs with the TestNG ones Change By: Nalin Makar (22/Jan/13 7:53 AM) Assignee: nalin_makar Nalin Makar 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
[JIRA] (JENKINS-10462) Display TestNG Method parameters at the top level
Nalin Makar updated JENKINS-10462 Display TestNG Method parameters at the top level Change By: Nalin Makar (22/Jan/13 7:53 AM) Assignee: nalin_makar Nalin Makar 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
[JIRA] (JENKINS-9838) Support health reporting based on test results
Nalin Makar updated JENKINS-9838 Support health reporting based on test results Change By: Nalin Makar (22/Jan/13 7:53 AM) Assignee: nalin_makar Nalin Makar 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
[JIRA] (JENKINS-15985) Common TestNG report on Matrix configuration project
Nalin Makar updated JENKINS-15985 Common TestNG report on Matrix configuration project Change By: Nalin Makar (22/Jan/13 7:53 AM) Assignee: nalin_makar Nalin Makar 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
[JIRA] (JENKINS-11899) Print all URLs as HTML anchors
Nalin Makar updated JENKINS-11899 Print all URLs as HTML anchors Change By: Nalin Makar (22/Jan/13 7:53 AM) Assignee: nalin_makar Nalin Makar 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
[JIRA] (JENKINS-12909) Add option to not HTML-sanitize stack traces
Nalin Makar updated JENKINS-12909 Add option to not HTML-sanitize stack traces Change By: Nalin Makar (22/Jan/13 7:53 AM) Assignee: nalin_makar Nalin Makar 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
[JIRA] (JENKINS-10100) Replace build-in test graphs with the TestNG ones
Nalin Makar commented on JENKINS-10100 Replace build-in test graphs with the TestNG ones kutzi, way back, via email conversation you mentioned you'll check with olamy and others to see whats the best way of handling this. Did you or others have an idea to point me in the right direction before I start looking into this? Junit and TestNG publishers attach separate ProjectActions to the job and currently I don't know if a clean way of replacing Junit's ProjectAction with the one from TestNG for Maven builds. 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
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Jurgen Van Bouchaute commented on JENKINS-15156 Builds Disappear from Build History after Completion Same problem on 1.498 version (Linux) - very annoying bug. 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
[JIRA] (JENKINS-12275) TestNG plugin should contribute to DashBoardView
Nalin Makar commented on JENKINS-12275 TestNG plugin should contribute to DashBoardView I have made changes to have TestNG's build action extend from AbstractTestResultAction, but looks like for replacing Dashboard View plugin also expects TestNG plugin to contribute a hudson.tasks.test.TestResultProjectAction. Instead, TestNG plugin contributes it's own TestNGProjectAction. It looks like either: 1. I'll have to jump through hoops again to have TestNGProjectAction extend from TestResultProjectAction or completely replace it, or, 2. Have Dashboard View plugin updated to also look for TestNGProjectAction 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
[JIRA] (JENKINS-8754) ROADMAP: Improve Start-up Time
Nickolay Martinov commented on JENKINS-8754 ROADMAP: Improve Start-up Time Looks like this feature breaks a lot. See https://issues.jenkins-ci.org/browse/JENKINS-15156 Would be nice to have a patch that reverts the change. 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
[JIRA] (JENKINS-15860) Mail body for two simultaneous mails get mixed
Slide-O-Mix commented on JENKINS-15860 Mail body for two simultaneous mails get mixed I tried reproducing it that way and did not see the same thing. I couldn't reproduce it. 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
[JIRA] (JENKINS-16374) BuildStepMonitor.STEP makes concurrent builds wait, could be changed to BuildStepMonitor.NONE
Nalin Makar resolved JENKINS-16374 as Fixed BuildStepMonitor.STEP makes concurrent builds wait, could be changed to BuildStepMonitor.NONE Fixed in revision v1.0. I think it should just work. If the reports look weird, please go give your feedback. Change By: Nalin Makar (22/Jan/13 12:32 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
[JIRA] (JENKINS-16374) BuildStepMonitor.STEP makes concurrent builds wait, could be changed to BuildStepMonitor.NONE
SCM/JIRA link daemon commented on JENKINS-16374 BuildStepMonitor.STEP makes concurrent builds wait, could be changed to BuildStepMonitor.NONE Code changed in jenkins User: Nalin Makar Path: README src/main/java/hudson/plugins/testng/Publisher.java src/main/java/hudson/plugins/testng/TestNGProjectAction.java src/main/java/hudson/plugins/testng/results/MethodResult.java src/main/java/hudson/plugins/testng/util/TestResultHistoryUtil.java http://jenkins-ci.org/commit/testng-plugin-plugin/033f48c3feaf460c7ab89c7d7824160b1fc13a45 Log: Fixed: JENKINS-16374 - BuildStepMonitor.STEP makes concurrent builds wait, could be changed to BuildStepMonitor.NONE Compare: https://github.com/jenkinsci/testng-plugin-plugin/compare/43e72a907aec...033f48c3feaf 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
[JIRA] (JENKINS-16434) thinBackup plugin puts Jenkins into shutdown mode and does not come out of it
smadden created JENKINS-16434 thinBackup plugin puts Jenkins into shutdown mode and does not come out of it Issue Type: Bug Affects Versions: current Assignee: Thomas Fürer Attachments: jenkins.err.log Components: thinBackup Created: 21/Jan/13 11:27 PM Description: We have a Jenkins project that uses the build step "Trigger builds on other projects" and is set to "Block until the triggered projects finish their builds". This project has a lot of those dependencies and runs for several hours total (3 to 5). Sometimes the thinBackup kicks right in in the middle and puts Jenkins into Shutdown mode. In this case the main project is still active because it is blocked by the other triggered projects. And because Jenkins is in shutdown mode, it won't start building those; they stay in the queue. And the thinBackup client doesn't run either. Maybe because the Main Project is still active? (just an assumption). At this stage we have a deadlock. Nothing is going to build anymore, the backup is not happening and Jenkins won't come out of Shutdown mode. If I cancel the shutdown mode, one of the queued up projects starts to build, but shortly after that the shutdown mode will be re-enabled by the thinBackup plugin. You can see that in the log. The only way to get out of this state is to repeatedly cancel the shutdown until all queued projects finished building. Then the thinBackup plugin backs things up and takes Jenkins out of shutdown mode. Could someone please take a look? I have the Jenkins error log attached. Thanks, Sandra Environment: Windows Server 2003 Project: Jenkins Priority: Major Reporter: smadden 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
[JIRA] (JENKINS-16386) Please add a button for viewing the console of the latest / current build
Nigel Smith commented on JENKINS-16386 Please add a button for viewing the console of the latest / current build Thanks for doing this so quickly Fred! Much Appreciated! 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
[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered
Duane Bronson commented on JENKINS-16273 Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered @Jesse - thank you for taking a closer look at this. I have resorted to running without security in hopes that a better solution will be found for the "Logged-in users can do anything" authorization policy. How can I track SECURITY-54? Is the SECURITY project restricted from the general public? https://issues.jenkins-ci.org/secure/BrowseProjects.jspa shows the project, but it looks like it contains no issues. 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
[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered
Jesse Glick resolved JENKINS-16273 as Fixed Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered Considering fixed. The outstanding issue of slave installers is trickier and has broader implications, filed separately as SECURITY-54. Change By: Jesse Glick (21/Jan/13 10:18 PM) Status: Reopened 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
[JIRA] (JENKINS-16433) Jabber Plugin does not send any notification
Laurentius Purba created JENKINS-16433 Jabber Plugin does not send any notification Issue Type: Bug Assignee: kutzi Components: jabber Created: 21/Jan/13 10:04 PM Description: After upgrading to latest release 1.499, my jabber + instant message plugins does not work any more. Installed plugins: Jenkins instant-messaging plugin 1.25 Jenkins Jabber notifier plugin 1.25 Error message: Jan 21, 2013 4:55:54 PM hudson.plugins.im.IMConnectionProvider$ConnectorRunnable run INFO: Trying to reconnect Jan 21, 2013 4:55:54 PM hudson.plugins.jabber.im.transport.JabberIMConnection createConnection INFO: Trying to connect to XMPP on chat.MYDOMAIN.com:5222/chat.MYDOMAIN.com with SASL Jan 21, 2013 4:55:55 PM hudson.plugins.jabber.im.transport.JabberIMConnection setupSubscriptionMode INFO: Accepting all subscription requests Jan 21, 2013 4:55:55 PM hudson.plugins.jabber.im.transport.JabberIMConnection connect INFO: Connected to XMPP on chat.MYDOMAIN.com:5222/chat.MYDOMAIN.com using TLS stream:error (conflict) at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:260) at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:43) at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:70) Environment: OS: FreeBSD 7.2 Jenkins 1.499 java version "1.6.0_07" Diablo Java(TM) SE Runtime Environment (build 1.6.0_07-b02) Diablo Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode) Project: Jenkins Labels: jabber instant-messaging Priority: Minor Reporter: Laurentius Purba 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
[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered
dogfood commented on JENKINS-16273 Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered Integrated in jenkins_main_trunk #2206 JENKINS-16273 Improved instructions for passing -jnlpCredentials. (Revision a1e709ddf0ca48b25ad07ee13a2fbdb0a6d97c0e) Result = SUCCESS Jesse Glick : a1e709ddf0ca48b25ad07ee13a2fbdb0a6d97c0e Files : core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly 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
[JIRA] (JENKINS-15011) Jacoco Plugin 1.0.3 - no threshold config and displays broken graphic link
Shane McEneaney commented on JENKINS-15011 Jacoco Plugin 1.0.3 - no threshold config and displays broken graphic link Hi Ogi, This looks like the same problem I have. Has this been fixed yet? Thanks, Shane 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
[JIRA] (JENKINS-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.
Shane McEneaney updated JENKINS-15366 Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods. Version of Jacoco Change By: Shane McEneaney (21/Jan/13 9:15 PM) Attachment: jacoco3.PNG 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
[JIRA] (JENKINS-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.
Shane McEneaney updated JENKINS-15366 Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods. Why no health reporting thresholds? Change By: Shane McEneaney (21/Jan/13 9:13 PM) Attachment: jacoco2.PNG 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
[JIRA] (JENKINS-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.
Shane McEneaney commented on JENKINS-15366 Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods. Hi Ogi, Why is there no health reporting thresholds as seen in http://www.lordofthejars.com/2012/08/jacoco-jenkins-plugin.html? I have attached a screen shot of my project configuration. Thanks, Shane 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
[JIRA] (JENKINS-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.
Shane McEneaney updated JENKINS-15366 Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods. Why is the JaCoCo Coverage Report blank? Change By: Shane McEneaney (21/Jan/13 9:09 PM) Attachment: jacoco.PNG 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
[JIRA] (JENKINS-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.
Shane McEneaney reopened JENKINS-15366 Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods. Hi Ogi, I have decided to try the Jenkins Jacoco plugin again. We had moved to Sonar. I am still seeing the same problem. I presume it's a bug. Please see latest attachment. Why is the JaCoCo Coverage Report blank? Thanks, Shane Change By: Shane McEneaney (21/Jan/13 9:07 PM) Resolution: Fixed Status: Resolved Reopened 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
[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered
Jesse Glick updated JENKINS-16273 Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered Fixed the display of the slave overview page. Leaving open since the slave installers do not write out -jnlpCredentials yet. Change By: Jesse Glick (21/Jan/13 8:24 PM) Summary: Slaves forbidden to request JNLP anonymously but no clear way to pass API token -jnlpCredentials not offered 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
[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but no clear way to pass API token
SCM/JIRA link daemon commented on JENKINS-16273 Slaves forbidden to request JNLP anonymously but no clear way to pass API token Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly http://jenkins-ci.org/commit/jenkins/a1e709ddf0ca48b25ad07ee13a2fbdb0a6d97c0e Log: JENKINS-16273 Improved instructions for passing -jnlpCredentials. First, display instructions when the user has CONNECT, not necessarily ADMINISTER. Second, when anonymous users cannot CONNECT, show how to use -jnlpCredentials (and do not bother showing javaws, since it does not work in this case). 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
[JIRA] (JENKINS-16426) Backup fails while copying a file from the jobs folder
SCM/JIRA link daemon commented on JENKINS-16426 Backup fails while copying a file from the jobs folder Code changed in jenkins User: tofuatjava Path: pom.xml src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java http://jenkins-ci.org/commit/thin-backup-plugin/cfe9e2dc71f92e2bc291798fd2ea16dfcb7515f0 Log: JENKINS-16426: back up only directorys in the job directory 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
[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but no clear way to pass API token
Jesse Glick commented on JENKINS-16273 Slaves forbidden to request JNLP anonymously but no clear way to pass API token Another annoyance: JNLPLauncher/main.jelly only displays these things when , i.e. you have ADMINISTER, when only CONNECT (on that Computer) should be 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
[JIRA] (JENKINS-16426) Backup fails while copying a file from the jobs folder
Thomas Fürer commented on JENKINS-16426 Backup fails while copying a file from the jobs folder Why do you have a xml file in the jobs directory. normally there are only folders in there. can you please tell me which plugins you use and which of it will store files in the jobs directory, or why this file is placed in this folder? 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
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Nathan Neulinger edited a comment on JENKINS-15156 Builds Disappear from Build History after Completion Same here with 1.499, reload from disk consistently clears it, but hardly an option for automated build chains. Our setup is client/server with 5 slaves. 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
[JIRA] (JENKINS-16376) BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?
Slide-O-Mix commented on JENKINS-16376 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE? The default mailer uses BuildStepMonitor.NONE. 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
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Nathan Neulinger commented on JENKINS-15156 Builds Disappear from Build History after Completion Same here with 1.499, reload from disk consistently clears it, but hardly an option for automated build chains. 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
[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but no clear way to pass API token
Jesse Glick commented on JENKINS-16273 Slaves forbidden to request JNLP anonymously but no clear way to pass API token The javaws command unfortunately does not seem to handle passwords or API tokens; so while curl is fine with http://user:pass@host:8080/computer/stuff/slave-agent.jnlp the same passed to javaws just gives a 403. Same for java -jar slave.jar -jnlpUrl … it seems; need to pass -jnlpCredentials to set up a headless slave, which the slave page under Connect slave to Jenkins one of these ways fails to mention. Then there is the problem that the installer fails to define -jnlpCredentials in your new jenkins-slave.xml; and JENKINS-9679 can make this not work unless you clear some obscure caches first. Seems URL.openConnection fails to parse out the username and password, or is just waiting for a BASIC auth challenge which never comes, due to Jenkins security policy? 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
[JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
Jesse Glick commented on JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option …or rather, launching the JNLP link seems to load from cache, and you have to manually delete e.g. C:\Documents and Settings\My Name\Local Settings\Application Data\Sun\Java\Deployment\cache and reload the JNLP to see the new 2.21 JAR. So it seems Jenkins is somehow not expiring old copies of the JAR properly, which ought to be 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
[JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
Jesse Glick reopened JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option The issue was fixed in slave.jar 2.21, served from /jnlpJars/slave.jar, but the jenkins-slave.exe service wrapper continues to bundle 2.20. Change By: Jesse Glick (21/Jan/13 5:45 PM) Resolution: Fixed Status: Resolved Reopened 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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
kutzi commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed For that you can e.g. use the xunit plugin as mentioned in JENKINS-10234. Generally, don't use any build steps which require blocking behaviour. Yes, very unfortunately it's not visible for end users which build steps do and which don't. 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
[JIRA] (JENKINS-7518) CLONE -Crumb breaks ajax request behind proxies. -- Still broken behind nginx proxies
Derek E commented on JENKINS-7518 CLONE -Crumb breaks ajax request behind proxies. -- Still broken behind nginx proxies I agree with the comment about switching to a more compatible header like "x-jenkins-crumb". There is some concern that disabling the nginx 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
[JIRA] (JENKINS-7518) CLONE -Crumb breaks ajax request behind proxies. -- Still broken behind nginx proxies
Derek E edited a comment on JENKINS-7518 CLONE -Crumb breaks ajax request behind proxies. -- Still broken behind nginx proxies I agree with the comment about switching to a more compatible header like "x-jenkins-crumb". 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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
Sergey Smirnov commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed I mean all result of concurent job. For example. I have Jenkins job that execute E2E tests on different QA servers. I started 10 jobs. One job running 5 hours. But others takes 1 hour. Then I can't see results of finished job and have to wait 4 hours to see it. We must have instrument to prevent 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
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Richard Mortimer
commented on JENKINS-15156
Builds Disappear from Build History after Completion
I'm wondering if this is due to the failure to re-load of an individual build history in AbstractLazyLoadRunMap.java.
Specifically the search(int, Direction) method does a binary search looking for a specific build. When it finds a match it may have to load() the build record from disk. If this fails then it "silently" removes the build that it tried to load and carries on.
R r = load(idOnDisk.get(pivot), null);
if (r==null) {
// this ID isn't valid. get rid of that and retry pivot
hi--;
if (!clonedIdOnDisk) {// if we are making an edit, we need to own a copy
idOnDisk = new SortedList(idOnDisk);
clonedIdOnDisk = true;
}
idOnDisk.remove(pivot);
continue;
}
Assuming that the failure to load is a (unknown) transient error then that would cause the build to disappear but it would be re-loaded when jenkins is restarted and the on-disk records scanned again.
I haven't seen this failure mode so I'm not able to test directly. If someone is able/willing to take a debug build of the latest jenkins I'll try to find time to add some additional debug logging to see if we can prove/disprove this theory.
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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
kutzi commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Sergey, do you mean 'artifact archiving' or 'JUnit result archiving'. In the former case, you would be probably right, but I've seen no comment here that artifact archiving is blocking, too. In the case of JUnit: yes it MUST block to calculate the diff (regressions et.al.) to the previous test results. So it is a feature. 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
[JIRA] (JENKINS-16319) Failure to delete old config files during rekeying on Windows
dogfood commented on JENKINS-16319 Failure to delete old config files during rekeying on Windows Integrated in jenkins_main_trunk #2205 [FIXED JENKINS-16319] Stream ordering problem prevented SecretRewriter from working on Windows. (Revision 8b8231108fb5930bab5c7e2f20685c9a9d237749) Result = SUCCESS Jesse Glick : 8b8231108fb5930bab5c7e2f20685c9a9d237749 Files : changelog.html core/src/main/java/hudson/util/SecretRewriter.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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
Sergey Smirnov commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed It is not a feature. All concurent builds execute in separated workspace and must archive its artifacts independently. No need to wait others builds if current have finished. 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
[JIRA] (JENKINS-16432) CVS-Plugin: global credential store only works if port is set in CVSROOT string
Julian Taylor created JENKINS-16432 CVS-Plugin: global credential store only works if port is set in CVSROOT string Issue Type: Bug Assignee: Unassigned Components: cvs Created: 21/Jan/13 4:44 PM Description: with the cvs plugin version 2.7 the global credential storage does not match cvsroot strings without a port. e.g. this is not matched: :pserver:username@host:/path whereas the equivalent with the default port works (if set in both the job and the global config): :pserver:username@host:2401/path Project: Jenkins Priority: Minor Reporter: Julian Taylor 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
[JIRA] (JENKINS-16427) Job build freezes during access to svn repository
kutzi commented on JENKINS-16427 Job build freezes during access to svn repository Could be related to http://issues.tmatesoft.com/issue/SVNKIT-312 Can you try the workarounds described here? http://issues.tmatesoft.com/issue/SVNKIT-312#comment=60-4367 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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
kutzi commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed There are several cause described here. Some are JUnit archiving, which is specifically handled in JENKINS-10234. Some seem to be related to email notification. I dare to say that in almost all cases this is a feature and not a bug as the logic for email notification and JUnit result archiving needs to wait until the previous builds are finished. 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
[JIRA] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
kutzi commented on JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds IMO this is definitely a feature and not a bug. If you don't like this behaviour, then use e.g. the xunit plugin which doesn't seem to behave in this way. 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
[JIRA] (JENKINS-12497) scm poll not saved when creating a new job
evernat commented on JENKINS-12497 scm poll not saved when creating a new job Is it reproduced with a recent Jenkins version? 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
[JIRA] (JENKINS-12493) Jenkins distinguishes username between typed in and copied in
evernat commented on JENKINS-12493 Jenkins distinguishes username between typed in and copied in I do not reproduce the problem. Do you reproduce it with a recent Jenkins version? If yes, are there special characters in the username or is it just "user". And how do you have configured security? 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
[JIRA] (JENKINS-16319) Failure to delete old config files during rekeying on Windows
SCM/JIRA link daemon resolved JENKINS-16319 as Fixed Failure to delete old config files during rekeying on Windows Change By: SCM/JIRA link daemon (21/Jan/13 4:06 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12489) Need a good Calendar module for www.jenkins-ci.org
evernat commented on JENKINS-12489 Need a good Calendar module for www.jenkins-ci.org There is http://jenkins-ci.org/calendar, which was almost never used but is still available. And there is http://jenkins-ci.org/content/event-calendar, which is used. Perhaps it is ok now? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16319) Failure to delete old config files during rekeying on Windows
SCM/JIRA link daemon commented on JENKINS-16319 Failure to delete old config files during rekeying on Windows Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/util/SecretRewriter.java http://jenkins-ci.org/commit/jenkins/8b8231108fb5930bab5c7e2f20685c9a9d237749 Log: [FIXED JENKINS-16319] Stream ordering problem prevented SecretRewriter from working on Windows. 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
[JIRA] (JENKINS-16431) the projects not order by my order of input
Coffee Night updated JENKINS-16431 the projects not order by my order of input Change By: Coffee Night (21/Jan/13 3:47 PM) Component/s: core 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
[JIRA] (JENKINS-16165) Configure screen stuck in "LOADING" state
Jesse Glick updated JENKINS-16165 Configure screen stuck in "LOADING" state Probably looking at multiple unrelated bugs here. Change By: Jesse Glick (21/Jan/13 3:46 PM) Component/s: email-ext Component/s: core 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
[JIRA] (JENKINS-16431) the projects not order by my order of input
Coffee Night created JENKINS-16431 the projects not order by my order of input Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 21/Jan/13 3:37 PM Description: such as I have a project as A then I set when A finish build, parameterized trigger start C and B project but in fact it always first build B not C. seems like Alphabetical not my input order. I want to C before B because their build will take about 30min and sometimes I want C first sometimes I want B first, so I won't change the name C to B.(in fact I have about 30+ projects, so it's impossible to set block after someone) Sorry for my poor English. Project: Jenkins Priority: Major Reporter: Coffee Night 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
[JIRA] (JENKINS-16233) EnvInject plugin using a cached value for ${WORKSPACE}
Dave Hunt
reopened JENKINS-16233
EnvInject plugin using a cached value for ${WORKSPACE}
Were you able to replicate the issue? We have upgraded to 1.80 and still see the issue. I've taken a look at the changes and not sure that 'we set a global workspace at job level' is accurate for what we are doing. We are setting an environment variable to the value including ${WORKSPACE} and instead of getting the job workspace it is the value of a previous job's workspace...
Change By:
Dave Hunt
(21/Jan/13 3:36 PM)
Resolution:
Fixed
Status:
Resolved
Reopened
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
[JIRA] (JENKINS-16165) Configure screen stuck in "LOADING" state
Laurentius Purba commented on JENKINS-16165 Configure screen stuck in "LOADING" state I got the same error with "LOADING" div; I resolved the issue by downgrading Email-ext plugin from 2.25 to 2.14.1. I have my jenkins installed on FreeBSD 7.2, with latest jenkin 1.499. I opened the configuration from Firefox 18.0 and Chrome 23.0.1271.91 in Xubuntu. 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
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Joel Johnson commented on JENKINS-15156 Builds Disappear from Build History after Completion @Nickolay Martinov: It's been happening to us ever since we upgraded to the Lazy Loading patch (1.485). 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
[JIRA] (JENKINS-16430) Cannot connect a slave without Connect right
wernight created JENKINS-16430 Cannot connect a slave without Connect right Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ldap Created: 21/Jan/13 2:55 PM Description: Since latest LDAP and Jenkins 1.480.2 in order for slave to connect with LDAP plugin I had to give the following rights: Anonymous: Overall Read, and Slave Connect. Without those, the JNLP gives a 403 (or 404) error. This wasn't the case before. Project: Jenkins Priority: Major Reporter: wernight 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
[JIRA] (JENKINS-16165) Configure screen stuck in "LOADING" state
Jesse Glick updated JENKINS-16165 Configure screen stuck in "LOADING" state Change By: Jesse Glick (21/Jan/13 2:46 PM) Component/s: clearcase 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
[JIRA] (JENKINS-16138) mercurial SCM always clones (instead of pulling) when using https
Jesse Glick commented on JENKINS-16138 mercurial SCM always clones (instead of pulling) when using https A warning would be better than nothing, but I think there is an actual fix; just have not gotten to it yet. 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
[JIRA] (JENKINS-11010) image icons for downstream-buildview point to port 8080, even if jenkins is configured to run on another port
evernat resolved JENKINS-11010 as Fixed image icons for downstream-buildview point to port 8080, even if jenkins is configured to run on another port Change By: evernat (21/Jan/13 2:42 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11010) image icons for downstream-buildview point to port 8080, even if jenkins is configured to run on another port
w brown commented on JENKINS-11010 image icons for downstream-buildview point to port 8080, even if jenkins is configured to run on another port It seems to be fixed now. Thank you. 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
[JIRA] (JENKINS-16372) Password parameter is malformed
Mateusz Balbus reopened JENKINS-16372 Password parameter is malformed I created Windows batch script in Jenkins: echo %password% > out.txt and my out.txt looks like: aUZfmW1sIV8Cf1ylDYbisNAlvHM5BIFcWQh6DOBXpt4= Change By: Mateusz Balbus (21/Jan/13 2:26 PM) Resolution: Not A Defect Status: Resolved Reopened 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
[JIRA] (JENKINS-16013) [jenkins-multijob-plugin] "Use custom workspace" is not working with the MultiJob Plugin
Gil Shinar closed JENKINS-16013 as Fixed [jenkins-multijob-plugin] "Use custom workspace" is not working with the MultiJob Plugin Closed Change By: Gil Shinar (21/Jan/13 1:56 PM) Status: Resolved Closed 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
[JIRA] (JENKINS-16013) [jenkins-multijob-plugin] "Use custom workspace" is not working with the MultiJob Plugin
Gil Shinar resolved JENKINS-16013 as Fixed [jenkins-multijob-plugin] "Use custom workspace" is not working with the MultiJob Plugin deleted custome workspace's get/set property functions because parent project is taking care of that. Change By: Gil Shinar (21/Jan/13 1:54 PM) Status: Open Resolved Fix Version/s: current 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
[JIRA] (JENKINS-16078) JNLP slave hangs on start in ~1 of 10 build starts
Serge Tsygankov edited a comment on JENKINS-16078 JNLP slave hangs on start in ~1 of 10 build starts Hi Still reproducing this issue sometimes. Even more rare than 1/10 Maybe there is way to turn on additional debug info into log? To see on which step exactly hanging happens. The problem is it happens really rare. And I guess it depends a lot from the time conditions. 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
[JIRA] (JENKINS-16078) JNLP slave hangs on start in ~1 of 10 build starts
Serge Tsygankov commented on JENKINS-16078 JNLP slave hangs on start in ~1 of 10 build starts Hi Still reproducing this issue sometimes. Even more rare than 1/10 Maybe there is way to turn on addition debug info into log? To see on which step exactly hanging happens. The problem is it happens really rare. And I guess it depends a lot from the time conditions. 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
[JIRA] (JENKINS-16013) [jenkins-multijob-plugin] "Use custom workspace" is not working with the MultiJob Plugin
itai Or assigned JENKINS-16013 to Gil Shinar [jenkins-multijob-plugin] "Use custom workspace" is not working with the MultiJob Plugin Change By: itai Or (21/Jan/13 1:41 PM) Assignee: Gil Shinar 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
[JIRA] (JENKINS-16429) OutOfMemoryError Exception due to thread leakage
Bernhard Berbuir created JENKINS-16429 OutOfMemoryError Exception due to thread leakage Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: active-directory Created: 21/Jan/13 1:14 PM Description: I get the following stack trace once a day: Exception: FATAL: unable to create new native thread java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:640) at hudson.Proc$LocalProc.(Proc.java:264) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:763) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:79) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1467) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1428) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:792) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1516) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) The URL http:/jenkinsserver/threadDump shows that there are hundreds of ComThreads: ComThread for RequestHandlerThread301 "ComThread for RequestHandlerThread301" Id=50942 Group=main RUNNABLE (in native) at com4j.Win32Lock.suspend0(Native Method) at com4j.Win32Lock.suspend(Win32Lock.java:37) at com4j.ComThread.run0(ComThread.java:146) at com4j.ComThread.run(ComThread.java:134) The Monitoring plugin (https://wiki.jenkins-ci.org/display/JENKINS/Monitoring) shows that about 40 threads are added every hour. I tried to kill the ComThreads with the plugin but this did not work. As far as I understand the threads belong to the Active Directory plugin but I do not understand why they are created / never finish. I have activated logging for the Active Directory plugin by enabling the following loggers (all with log level all): hudson.plugins.active_directory org.acegisecurity com4j The log contains a lot of entries like this: Jan 16, 2013 12:20:27 PM org.acegisecurity.context.HttpSessionContextIntegrationFilter doFilter FINE: SecurityContextHolder now cleared, as request processing completed Jan 16, 2013 12:20:27 PM org.acegisecurity.providers.anonymous.AnonymousProcessingFilter doFilter FINE: Populated SecurityContextHolder with anonymous token: 'org.acegisecurity.providers.anonymous.AnonymousAuthenticationToken@7ceb964f: Username: anonymous; Password: [PROTECTED]; Authenticated: true; Details: org.acegisecurity.ui.WebAuthenticationDetails@1de6: RemoteIpAddress: ##.##.##.##; SessionId: null; Granted Authorities: ' Jan 16, 2013 12:20:27 PM org.acegisecurity.context.HttpSessionContextIntegrationFilter storeSecurityContextInSession FINE: The HttpSession is currently null, and the HttpSessionContextIntegrationFilter is prohibited from creating an HttpSession (because the allowSessionCreation property is false) - SecurityContext thus not stored for next request Jan 16, 2013 12:20:27 PM org.acegisecurity.ui.basicauth.BasicProcessingFilter doFilter FINE: Authorization header: null Jan 16, 2013 12:20:27 PM org.acegisecurity.ui.ExceptionTranslationFilter doFilter FINE: Chain processed normally Jan 16, 2013 12:20:
[JIRA] (JENKINS-16376) BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?
Inbar Rose commented on JENKINS-16376 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE? i have a similar problem, as this: https://issues.jenkins-ci.org/browse/JENKINS-10234 and as this. if this is not going to be changed - is there an email plugin that does not have triggers depending on the BuildStepMonitor.BUILD. and is able to send mails concurrently? 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
[JIRA] (JENKINS-16428) no 'delete' button on some post-built actions sometimes
Inbar Rose updated JENKINS-16428 no 'delete' button on some post-built actions sometimes Change By: Inbar Rose (21/Jan/13 12:36 PM) Description: Jenkins ver. 1.495Sometimes the 'delete' button does not appear for some items in the 'Post-build Actions'Specifically the 'Editable Email Notification' and 'E-mail Notification'The strange thing is that it does appear for some items.See attached image. Issue can be fixed by saving configuration and then opening configuration again until 'delete' button is visible again. 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
[JIRA] (JENKINS-16428) no 'delete' button on some post-built actions sometimes
Inbar Rose created JENKINS-16428 no 'delete' button on some post-built actions sometimes Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: New Bitmap Image.bmp Components: postbuild-task Created: 21/Jan/13 12:33 PM Description: Jenkins ver. 1.495 Sometimes the 'delete' button does not appear for some items in the 'Post-build Actions' Specifically the 'Editable Email Notification' and 'E-mail Notification' The strange thing is that it does appear for some items. See attached image. Project: Jenkins Labels: jenkins Priority: Major Reporter: Inbar Rose 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
[JIRA] (JENKINS-15534) Maven disk usage is incorrect
SCM/JIRA link daemon commented on JENKINS-15534 Maven disk usage is incorrect Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/disk_usage/DiskUsageThread.java http://jenkins-ci.org/commit/disk-usage-plugin/4c30e5bdc92a27a7889b687575e947904e1c132f Log: JENKINS-15534 compute maven modules disk usage 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
[JIRA] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Inbar Rose updated JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds Change By: Inbar Rose (21/Jan/13 11:53 AM) Priority: Major Blocker 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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
Inbar Rose commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed same problem here. total blocker. task A starts, then task B starts. task B reaches the 'Recording test results' stage and hangs until task A finishes. after testing with simple timed builds with many plugins/options enabled/disabled concluded that junit is the problem. - found another issue like this here: https://issues.jenkins-ci.org/browse/JENKINS-10234 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
[JIRA] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Inbar Rose commented on JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds same problem here. total blocker. task A starts, then task B starts. task B reaches the 'Recording test results' stage and hangs until task A finishes. after testing with simple timed builds with many plugins/options enabled/disabled concluded that junit is the 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
[JIRA] (JENKINS-16416) EXCEPTION_ACCESS_VIOLATION uninstalling Active Directory plugin with GUI
Takeji Naigeon edited a comment on JENKINS-16416 EXCEPTION_ACCESS_VIOLATION uninstalling Active Directory plugin with GUI We have similar errors here, 4 times in ~2 weeks. Not while uninstalling, but in normal usage (looks like while timestamper plugin is doing its job). I don't know if it is linked, but first crashed happened a few hours after we upgraded from former LTS release to 1.480.1 and then 1.480.2. Attaching hs_err_pid188.log 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
[JIRA] (JENKINS-16416) EXCEPTION_ACCESS_VIOLATION uninstalling Active Directory plugin with GUI
Takeji Naigeon updated JENKINS-16416 EXCEPTION_ACCESS_VIOLATION uninstalling Active Directory plugin with GUI We have similar errors here, 4 times in ~2 weeks. Not while uninstalling, but in normal usage (looks like while timestamper plugin is doing its job). I don't know if it is linked, but first crashed happened a few hours after we upgraded from former LTS release to 1.480.1 and then 1.480.2. Change By: Takeji Naigeon (21/Jan/13 11:34 AM) Attachment: hs_err_pid188.log 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
[JIRA] (JENKINS-16404) email-ext regression trigger not firing when it should
Slide-O-Mix commented on JENKINS-16404 email-ext regression trigger not firing when it should I'm trying to figure out the history behind the getNumFailures method, it was implemented before I started working on 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
[JIRA] (JENKINS-16424) Add Parameter to use the Name of Recipient
Slide-O-Mix resolved JENKINS-16424 as Won't Fix Add Parameter to use the Name of Recipient If you have more than one recipient, this will not work. Change By: Slide-O-Mix (21/Jan/13 11:26 AM) Status: Open Resolved Resolution: Won't 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
[JIRA] (JENKINS-16423) Add option for CC and BCC
Slide-O-Mix commented on JENKINS-16423 Add option for CC and BCC Will add something in 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
[JIRA] (JENKINS-9586) Sometimes after Jenkins restart platform labels are not available
Krzysztof Malinowski commented on JENKINS-9586 Sometimes after Jenkins restart platform labels are not available It is. I just encountered it again yesterday starting up Jenkins 1.499. 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
[JIRA] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
aleksas assigned JENKINS-15587 to Kohsuke Kawaguchi Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" Change By: aleksas (21/Jan/13 11:04 AM) Assignee: Kohsuke Kawaguchi 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
[JIRA] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
aleksas
commented on JENKINS-15587
Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
The issue is with the File.getCanonicalFile() function. It doesn't resolve the original directory name from NTFS symlink.
To see the code look here: function parseTimestampFromBuildDir in https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Run.java .
To test the problem one can compile (jdk1.7) and run code below (change "./294" to appropriate symlink path)
To create directory symlink on windows Vista/7/2008 run command: mklink /D symlinkname targetdirpath (e.g. mklink /D win "C:\Windows")
MainClass.java code:
import java.io.File;
import java.nio.file.Path;
import java.nio.file.Files;
import java.io.IOException;
public class MainClass {
public static void main(String [] args) {
File file = new File("./294");
try {
if(file.isDirectory()) System.out.print("Dir ");
else System.out.print("File ");
if(Files.isSymbolicLink(file.toPath())) System.out.print("Symlink ");
System.out.println(file.getAbsolutePath());
System.out.println(file.getCanonicalFile().getName());
System.out.println(file.getCanonicalFile().getAbsolutePath());
} catch (IOException e) {
e.printStackTrace();
}
}
}
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
[JIRA] (JENKINS-16427) Job build freezes during access to svn repository
Anton Tupikov created JENKINS-16427 Job build freezes during access to svn repository Issue Type: Bug Affects Versions: current Assignee: Simon Wiest Attachments: Jenkins.ThreadDump.txt Components: svncompat14 Created: 21/Jan/13 10:49 AM Description: Environment: Jenkins version 1.499 Jenkins Subversion Plug-in 1.44 many other plugins. Description: Time to time (30% percent of the total builds number) builds stuck. Notes: Problem always at the stage of working with svn repository (f.e. check update). Access to the svn repository from this host is available. Tasks can not be stopped (till Jenkins full restart) After Jenkins restart the task is performed job logs looks like: example 1: Started by user A Building in workspace /home/A/.jenkins/api_functional *loader icon* example 2: Started by user B Building in workspace /home/A/.jenkins/page_response_status_code Reverting /home/A/.jenkins/page_response_status_code/. Updating svn://path/qa to revision '2013-01-21T14:23:55.881 +0400' *loader icon* threadDump has been attached Additional information: Current SCM Polling Activities There are more SCM polling activities scheduled than handled, so the threads are not keeping up with the demands. Check if your polling is hanging, and/or increase the number of threads if necessary. The following polling activities are currently in progress: Project ↓ Running for API functional 46 min Page response status code 1 hr 16 min Project: Jenkins Priority: Major Reporter: Anton Tupikov 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
[JIRA] (JENKINS-16425) /tmp/android-jenkins was filled with files of format emulator-YNLSnL
Christopher Orr closed JENKINS-16425 as Not A Defect /tmp/android-jenkins was filled with files of format emulator-YNLSnL The Android emulator creates those files, not the Jenkins plugin. You can either delete these files via cron, or use the ANDROID_TMP variable to point the emulator to write files to another partition, rather than to /tmp/android-$USER. Change By: Christopher Orr (21/Jan/13 10:15 AM) Status: Open Closed 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
[JIRA] (JENKINS-16424) Add Parameter to use the Name of Recipient
Slide-O-Mix commented on JENKINS-16424 Add Parameter to use the Name of Recipient What if there are 20 recipients or 40? I don't think I will implement this for thus reason. 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
[JIRA] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
aleksas commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" Same here 1.492 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
[JIRA] (JENKINS-16423) Add option for CC and BCC
Christoph Läubrich commented on JENKINS-16423 Add option for CC and BCC A thank you, is this documented somewhere? Might be good to add it to the Jenkins Help for "Project Recipient List" 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
[JIRA] (JENKINS-16424) Add Parameter to use the Name of Recipient
Christoph Läubrich commented on JENKINS-16424 Add Parameter to use the Name of Recipient It would be nice to have something like: "Hi , ..." in the mail body to make the mail apear more personal. 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
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Henri Gomez edited a comment on JENKINS-15156 Builds Disappear from Build History after Completion Same problem here, with 1.498 (powered by Tomcat 7.0.35) under openSUSE Linux. I noticed this problem appears for jobs built on agents. 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
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Henri Gomez commented on JENKINS-15156 Builds Disappear from Build History after Completion Same problem here, with 1.498, under openSUSE Linux. I noticed this problem appears for jobs built on agents. 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
[JIRA] (JENKINS-16018) Not all builds show in the build history dashboard on job
Henri Gomez commented on JENKINS-16018 Not all builds show in the build history dashboard on job Same problem here with 1.498. 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
[JIRA] (JENKINS-14893) scm sync configuration causes memory leak
Steven Aerts commented on JENKINS-14893 scm sync configuration causes memory leak The only dump I have is more than a gigabyte. I am not able to upload a file this big. Are you looking for something specific? By the way, as a workaround, I removed the j:set-statements of the fail, msg and success variables in the footer.jelly file, which seems to work. Best regards, Steven 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
[JIRA] (JENKINS-16426) Backup fails while copying a file from the jobs folder
Christian Apel created JENKINS-16426 Backup fails while copying a file from the jobs folder Issue Type: Bug Affects Versions: current Assignee: Thomas Fürer Components: thinBackup Created: 21/Jan/13 8:51 AM Description: It looks like the backup plugin tries to copy a directory instead of a file and stops the backup at this point. Also the configured compression to zip files wasn't working, probably due to the exception. Jan 21, 2013 5:00:34 AM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobsDirectory INFO: Found 31 jobs to back up. Jan 21, 2013 5:00:34 AM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobsDirectory INFO: Found 347 jobs to back up. Jan 21, 2013 5:00:36 AM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobsDirectory INFO: Found 36 jobs to back up. Jan 21, 2013 5:00:38 AM org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork backupNow SEVERE: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path 'D:\backup\jenkins'. java.io.IOException: Source 'd:\jenkins\jobs\settings-XYZ.xml' exists but is not a directory at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:869) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:814) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobConfigFor(HudsonBackup.java:240) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJob(HudsonBackup.java:201) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobsDirectory(HudsonBackup.java:190) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobs(HudsonBackup.java:169) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backup(HudsonBackup.java:136) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.backupNow(ThinBackupPeriodicWork.java:87) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.execute(ThinBackupPeriodicWork.java:68) at org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:54) at java.lang.Thread.run(Thread.java:722) I haven't recognized this issue immediately, because a full backup and 6 incremental backups were partially stored in the backup folder. It would be helpful to show an error on the thinBackup Jenkins page, if a backup failed due to any issue. Environment: Windows Server 2008 R2 64bit, Tomcat 7 Project: Jenkins Priority: Major Reporter: Christian Apel 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
[JIRA] (JENKINS-16425) /tmp/android-jenkins was filled with files of format emulator-YNLSnL
Matti Linnanvuori created JENKINS-16425 /tmp/android-jenkins was filled with files of format emulator-YNLSnL Issue Type: Bug Affects Versions: current Assignee: Christopher Orr Components: android-emulator Created: 21/Jan/13 8:24 AM Description: Directory /tmp/android-jenkins was filled with files of format emulator-YNLSnL, which eventually filled up the partition. Environment: Debian GNU/Linux wheezy/sid Xen Linux 3.2.0-3-amd64 #1 SMP Thu Jun 28 09:07:26 UTC 2012 x86_64 Project: Jenkins Priority: Major Reporter: Matti Linnanvuori 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
