[JIRA] (JENKINS-9688) Build runs on master without executor and get stuck
Jose Sa commented on JENKINS-9688 Build runs on master without executor and get stuck After several similar situations in the past weeks like this one where concurrent jobs using the same lock I think the problem may be mostly between chair and keyboard, but also due to lack of informative messages. Lets assume 3 jobs A, B and C using the same lock, the following timeline occurs: A is already running (so it has the lock) and we start B and C. B and C show in queue stating they are being blocked by A A finishes B and C already waited the 'delay' so they are ready to run, so they do run at the same time B gets the lock so it states it in the log is activelly running C on the other hand didn't get the lock, but is running anyway and showing no output that it is actively waiting for the lock Users panic when they see a job running for 2 days without any output in the log and cancel the C C get's inconsistent state and starts showing "null" instead of real dates Jenkins needs to be restarted to get rid of C because there is no way to kill it Also we observed that if we don't Cancel C eventually it starts executing normally when B finishes and showing it has acquired the lock in the log file. Bottom line the problem is lack of informative messages from the plugin to provide the proper feedback to users so they don't panic. Workaround: Revoke users permissions to Cancel builds that are using locks. 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-9688) Build runs on master without executor and get stuck
Jose Sa updated JENKINS-9688 Build runs on master without executor and get stuck Change By: Jose Sa (23/Sep/12 10:51 AM) Component/s: locks-and-latches 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-9688) Build runs on master without executor and get stuck
Jose Sa assigned JENKINS-9688 to stephenconnolly Build runs on master without executor and get stuck Change By: Jose Sa (23/Sep/12 10:53 AM) Assignee: stephenconnolly 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-13420) Unable to serialize hudson.plugins.android_emulator.SdkInstaller
Christopher Orr resolved JENKINS-13420 as Fixed Unable to serialize hudson.plugins.android_emulator.SdkInstaller Fixed in https://jenkins-ci.org/commit/android-emulator-plugin/a531f90 Change By: Christopher Orr (23/Sep/12 12:35 PM) Status: InProgress 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-15097) Expecting integer when it can be a float or even a string
Christopher Orr closed JENKINS-15097 as Fixed Expecting integer when it can be a float or even a string Version 2.4 of the plugin was released this week, which includes this fix. Change By: Christopher Orr (23/Sep/12 12:36 PM) Status: Open Closed 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-15008) NPE
Slide-O-Mix commented on JENKINS-15008 NPE I have the exact same setup and don't have this issue. Can you upload an example config.xml for a job (scrubbed of any personal/company info) so I can see if there is anything amiss? 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] (TEST-15) Finishing with a Null Pointer Exception after a successful build.
Avishay Halpren commented on TEST-15 Finishing with a Null Pointer Exception after a successful build. עכט. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9211) Rebuild Plugin does not work for Subversion List Parameter
Rino Kadijk updated JENKINS-9211 Rebuild Plugin does not work for Subversion List Parameter Improved patch to be more in line with the existing param copying. Change By: Rino Kadijk (23/Sep/12 1:09 PM) Attachment: JENKINS-9211_20120923.patch 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-9211) Rebuild Plugin does not work for Subversion List Parameter
Rino Kadijk updated JENKINS-9211 Rebuild Plugin does not work for Subversion List Parameter Change By: Rino Kadijk (23/Sep/12 1:12 PM) Attachment: rebuild.hpi 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-14748) Rebuild plugin throws JellyTagException after upgrade to 477
Rino Kadijk updated JENKINS-14748 Rebuild plugin throws JellyTagException after upgrade to 477 I attached a snapshot build with a ListSubversionTagsParameterValue.jelly included. Could you please test if this resolves the issue? Change By: Rino Kadijk (23/Sep/12 1:36 PM) Attachment: rebuild.hpi 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-9767) MavenTestDataPublisher is unusable in this state
Ryszard Perkowski commented on JENKINS-9767 MavenTestDataPublisher is unusable in this state I just created a pull request https://github.com/jenkinsci/jenkins/pull/574 with Sebastien's changes. Hope they'll get pulled in. I'm also affected by this bug in JUnit Excepted Diff Plugin (https://github.com/usultis/junit-expected-diff-plugin). With provided patch it works ok. 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-15146) EnvJect unsets empty string properties returned in maps
SCM/JIRA link daemon commented on JENKINS-15146 EnvJect unsets empty string properties returned in maps Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectEnvVars.java src/test/java/org/jenkinsci/plugins/envinject/EnvInjectEnvVarsEmpty.java http://jenkins-ci.org/commit/envinject-plugin/718586449693a86314242223b14813c374b8bbdc Log: Fix JENKINS-15146 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-15146) EnvJect unsets empty string properties returned in maps
Gregory Boissinot commented on JENKINS-15146 EnvJect unsets empty string properties returned in maps Sorry for the inconvenience. Empty environment variables are acceptable for now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15146) EnvJect unsets empty string properties returned in maps
Gregory Boissinot resolved JENKINS-15146 as Fixed EnvJect unsets empty string properties returned in maps Change By: Gregory Boissinot (23/Sep/12 2:57 PM) Status: InProgress 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-15009) Plugin should include descriptive information, not only the ID's
Bruno P. Kinoshita updated JENKINS-15009 Plugin should include descriptive information, not only the IDs Change By: Bruno P. Kinoshita (23/Sep/12 4:04 PM) Summary: Pluginshould show includedescriptiveinformation, notonlythe environment ID andBuildIDbutalsothedescription s Description: e.g.:Build,EnvironmentOnlytheIDisretrievednow.Itwouldbehelpfultohavethedescription,username,usere-mail,etc. 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-15095) Testopia fields witn no value should give an empty environment variable and not value null
Bruno P. Kinoshita updated JENKINS-15095 Testopia fields witn no value should give an empty environment variable and not value null Change By: Bruno P. Kinoshita (23/Sep/12 4:10 PM) Fix Version/s: current Affects Version/s: current 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-15095) Testopia fields witn no value should give an empty environment variable and not value null
Bruno P. Kinoshita updated JENKINS-15095 Testopia fields witn no value should give an empty environment variable and not value null Change By: Bruno P. Kinoshita (23/Sep/12 4:11 PM) Fix Version/s: current Affects Version/s: current 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-15008) NPE
Kanstantsin Shautsou commented on JENKINS-15008 NPE This construction work ok in other jobs, but in this i not found reason of NPE. 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
iPhone App To Help You Learn Spanish Faster By Using Flashcards With Pictures
http://goo.gl/CRhLz - Spanish Flashcards with Pictures is an iPhone app that will help you learn Spanish faster by using flashcards with pictures (learn over 300 most commonly used words in the English / Spanish language from A to Z), thanks.
[JIRA] (JENKINS-8149) Git submodule fetch uses (incorrect) parent refspec
SCM/JIRA link daemon commented on JENKINS-8149 Git submodule fetch uses (incorrect) parent refspec Code changed in jenkins User: Jørgen P. Tjernø Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/6c2e0bdc7b33760f67a481a0cf9935ebc245e3b9 Log: JENKINS-8149 Fix submodule refspec. This switches from using the parent repository's refspec to using the commit specified in the index. We will now use the correct refspec when fetching submodules. 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-8149) Git submodule fetch uses (incorrect) parent refspec
SCM/JIRA link daemon commented on JENKINS-8149 Git submodule fetch uses (incorrect) parent refspec Code changed in jenkins User: Jørgen P. Tjernø Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/8642f269754b90b6b5e01249d0292f3f90ad1458 Log: Merge pull request #96 from jorgenpt/fix-refspec-in-submodule-fetch JENKINS-8149 Fix submodule refspec. Compare: https://github.com/jenkinsci/git-plugin/compare/cb3b1c0e0b0e...8642f269754b 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-15029) Update of MSBuild plugin to 1.15 causes Parameterized trigger plugin to fail.
Gregory Boissinot commented on JENKINS-15029 Update of MSBuild plugin to 1.15 causes Parameterized trigger plugin to fail. @Michael I don't really understand. Could I set to 'Resolved' the issue? 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-11285) Ability to run postbuild script on a given node
Gregory Boissinot commented on JENKINS-11285 Ability to run postbuild script on a given node @John By default, post-build scripts are executed on the build node. Do you want I add a check-box 'Run on master' in order to provide the ability to run post-build script on master. 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
AUTO: Martin Schoepf is out of the office (returning 10.08.2012)
I am out of the office until 10.08.2012. Note: This is an automated response to your message [JIRA] (JENKINS-11285) Ability to run postbuild script on a given node sent on 9/24/2012 1:26:49. This is the only notification you will receive while this person is away.
[JIRA] (JENKINS-15008) NPE
Slide-O-Mix commented on JENKINS-15008 NPE Can you isolate on which token is causing the issue? I don't think its the item in the recipient list. It could be the FILE or ENV tokens. 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-15258) The TAP Plugin does not work with the CI Game Plugin
chotchki resolved JENKINS-15258 as Not A Defect The TAP Plugin does not work with the CI Game Plugin I did some more digging and it seems to be working okay after all. This issue can be closed. Change By: chotchki (24/Sep/12 4:00 AM) Status: Open Resolved Assignee: redsolo chotchki Fix Version/s: current Resolution: NotADefect 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
