[JIRA] (JENKINS-9616) Revert configuration to an older version
Mirko Friedenhagen closed JENKINS-9616 as Fixed Revert configuration to an older version Change By: Mirko Friedenhagen (18/Jan/13 7:59 AM) 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-16319) Failure to delete old config files during rekeying on Windows
Damien Finck commented on JENKINS-16319 Failure to delete old config files during rekeying on Windows Hello, I have try to create a new proper instance of Jenkins (1.496) on a Windows Server 2008r2 with no plugins. I have juste configure the proxy in Jenkins, and so I have do the update to 1.499. When I have start the re-key, I have : Re-keying log Started re-keying Fri Jan 18 09:00:02 CET 2013 Scanning C:\Users\Administrateur\.jenkins\hudson.model.UpdateCenter.xml ERROR: Failed to rewrite C:\Users\Administrateur\.jenkins\proxy.xml java.io.IOException: Unable to delete C:\Users\Administrateur\.jenkins\proxy.xml at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.util.SecretRewriter.rewrite(SecretRewriter.java:121) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:170) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:143) at jenkins.security.RekeySecretAdminMonitor$RekeyThread.run(RekeySecretAdminMonitor.java:182) Completed re-keying 0 files on Fri Jan 18 09:00:02 CET 2013 This message is automatically generated by JIRA. 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-15466) Fatal Error No Class Definition found for Kernel32
Marcus Jacobsson commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 We've started to receive this error after updating to jdk-7u9-windows-x64. The problem is that the nunit constantly fails on when trying to clean. We are currently running a patched version of 1.480.1 Recording NUnit tests results 16:57:17 - ERROR: Publisher hudson.plugins.nunit.NUnitPublisher aborted due to exception 16:57:17 - hudson.util.IOException2: remote file operation failed: *\temporary-junit-reports at hudson.remoting.Channel@271d097d:WSAB101036 16:57:17 - at hudson.FilePath.act(FilePath.java:838) 16:57:17 - at hudson.FilePath.act(FilePath.java:824) 16:57:17 - at hudson.FilePath.deleteRecursive(FilePath.java:908) 16:57:17 - at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:115) 16:57:17 - at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) 16:57:17 - at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) 16:57:17 - at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) 16:57:17 - at hudson.model.Build$BuildExecution.post2(Build.java:183) 16:57:17 - at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) 16:57:17 - at hudson.model.Run.execute(Run.java:1527) 16:57:17 - at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 16:57:17 - at hudson.model.ResourceController.execute(ResourceController.java:88) 16:57:17 - at hudson.model.Executor.run(Executor.java:236) 16:57:17 - Caused by: java.io.IOException: Remote call on * failed 16:57:17 - at hudson.remoting.Channel.call(Channel.java:673) 16:57:17 - at hudson.FilePath.act(FilePath.java:831) 16:57:17 - ... 12 more 16:57:17 - Caused by: java.lang.NoClassDefFoundError: Could not initialize class hudson.util.jna.Kernel32 16:57:17 - at hudson.util.jna.Kernel32Utils.isJunctionOrSymlink(Kernel32Utils.java:62) 16:57:17 - at hudson.Util.isSymlink(Util.java:314) 16:57:17 - at hudson.Util.deleteRecursive(Util.java:279) 16:57:17 - at hudson.FilePath$11.invoke(FilePath.java:910) 16:57:17 - at hudson.FilePath$11.invoke(FilePath.java:908) 16:57:17 - at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2236) 16:57:17 - at hudson.remoting.UserRequest.perform(UserRequest.java:118) 16:57:17 - at hudson.remoting.UserRequest.perform(UserRequest.java:48) 16:57:17 - at hudson.remoting.Request$2.run(Request.java:326) 16:57:17 - at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 16:57:17 - at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 16:57:17 - at java.util.concurrent.FutureTask.run(Unknown Source) 16:57:17 - at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 16:57:17 - at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 16:57:17 - at hudson.remoting.Engine$1$1.run(Engine.java:60) 16:57:17 - at java.lang.Thread.run(Unknown Source) This message is automatically generated by JIRA. 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-16408) Initial state of the new dashboard view not user friendly
Kohsuke Kawaguchi created JENKINS-16408 Initial state of the new dashboard view not user friendly Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view Created: 18/Jan/13 8:54 AM Description: For those users who came from other views expect that it is suffice to select several jobs to start using the dashboard view plugin. But if no portlet is configured, the view just shows an empty page. This is not very user friendly. Either the new view should contain some initial portlets to get the user going, or otherwise show the welcome message to encourage users to add portlet when none is defined. (Based on the actual user feedback at a training.) Project: Jenkins Priority: Major Reporter: 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-16409) Add a Script trigger
Sebastian Schuberth created JENKINS-16409 Add a Script trigger Issue Type: New Feature Assignee: Slide-O-Mix Components: email-ext Created: 18/Jan/13 8:55 AM Description: Please add a "Script" trigger that displays a text field where a shell script can be entered, and sending of email is triggered only if the script's exit code is 0. This way one could e.g. trigger sending an email if some log output contains a certain keyword. Project: Jenkins Priority: Major Reporter: Sebastian Schuberth This message is automatically generated by JIRA. 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-16410) VirtualBox plugin tries to unlock non-locked machine, fails to start it.
Peter Soetens
created JENKINS-16410
VirtualBox plugin tries to unlock non-locked machine, fails to start it.
Issue Type:
Bug
Affects Versions:
current
Assignee:
godin
Components:
virtualbox
Created:
18/Jan/13 9:29 AM
Description:
Since recently, the plugin failed to start any of my VBox machines.
I'm not sure if this is a bug in the vboxwebsrv application or if the virtualbox plugin is sending the wrong commands, but this is the output on Jenkins slave log:
VirtualBox Launching node server-1210-amd64
VirtualBox Powering up VirtualBoxMachine{host=VirtualBoxHost{url='', username='virtual'},name='server-1210-amd64'}...
VirtualBox Lost connection to http://vader:18083, reconnecting
VirtualBox Trying to connect to http://vader:18083, user virtual
VirtualBox Creating connection to VirtualBox version 4.2.6
VirtualBox Connected to VirtualBox version 4.2.6 on host http://vader:18083
VirtualBox starting node server-1210-amd64 from state Saved
FATAL: VirtualBox node server-1210-amd64 error: The virtual machine 'server-1210-amd64' has terminated unexpectedly during startup with exit code 0
FATAL: Unable to launch
And this is what we see on vboxwebsrv -v :
Oracle VM VirtualBox web service Version 4.2.6
(C) 2007-2012 Oracle Corporation
All rights reserved.
VirtualBox web service 4.2.6 r82870 linux.amd64 (Dec 19 2012 15:09:30) release log
00:00:00.015733 main Log opened 2013-01-18T09:09:31.20007Z
00:00:00.015740 main OS Product: Linux
00:00:00.015742 main OS Release: 3.2.0-35-generic
00:00:00.015743 main OS Version: #55-Ubuntu SMP Wed Dec 5 17:42:16 UTC 2012
00:00:00.015775 main DMI Product Name: System Product Name
00:00:00.015785 main DMI Product Version: System Version
00:00:00.015795 main Host RAM: 24104MB total, 2972MB available
00:00:00.015799 main Executable: /usr/lib/virtualbox/vboxwebsrv
00:00:00.015800 main Process ID: 560
00:00:00.015801 main Package type: LINUX_64BITS_UBUNTU_12_04
00:00:00.022241 main Pumping COM event queue
00:00:00.022271 main Pumping COM event queue
00:00:00.022356 Watchdog Watchdog thread started
00:00:00.022383 Watchdog Watchdog: sleeping 5 seconds
00:00:00.025370 SQPmpSocket connection successful: host = default (localhost), port = 18083, master socket = 8
00:00:05.022484 Watchdog Watchdog: checking 0 sessions
00:00:05.022555 Watchdog Watchdog: sleeping 5 seconds
00:00:10.022617 Watchdog Watchdog: checking 0 sessions
00:00:10.022691 Watchdog Watchdog: sleeping 5 seconds
00:00:12.330449 SQPmpRequest 1 on socket 10 queued for processing (1 items on Q)
00:00:12.330538 SQW01New SOAP thread started
00:00:12.330570 SQW01Processing connection from IP=127.0.0.1 socket=10 (0 out of 1 threads idle)
00:00:12.356091 SQW01 entering _vbox_IVirtualBox_USCOREgetVersion
00:00:12.356110 SQW01 findRefFromId(): looking up objref 35869155d6a20050-0004
00:00:12.356121 SQW01 findRefFromId: cannot find session for objref 35869155d6a20050-0004
00:00:12.356165 SQW01 leaving _vbox_IVirtualBox_USCOREgetVersion, rc: 0xEF32 (-4302)
00:00:12.358599 SQPmpRequest 2 on socket 11 queued for processing (1 items on Q)
00:00:12.358649 SQW01Processing connection from IP=127.0.0.1 socket=11 (0 out of 1 threads idle)
00:00:12.359034 SQW01 entering _vbox_IWebsessionManager_USCORElogon
00:00:12.359638 main Pumping COM event queue
00:00:12.361551 main Pumping COM event queue
00:00:12.361919 main Pumping COM event queue
00:00:12.361992 SQW01external authentication library is 'null'
00:00:12.362225 SQW01 * ManagedObjectRef: MOR created for ISession*=0x7FD3100216C0 (IUnknown*=0x7FD3100216C0; COM refcount now 3/4), new ID is 1; now 1 objects total
00:00:12.362241 SQW01 * authenticate: created session object with comptr 0x7FD3100216C0, MOR = 0a39b81ff238d417-0001
00:00:12.362632 main Pumping COM event queue
00:00:12.362651 SQW01 * ManagedObjectRef: MOR created for IVirtualBox*=0x1785190
[JIRA] (JENKINS-14595) I should be able to source a flow definition from SCM
Kohsuke Kawaguchi commented on JENKINS-14595 I should be able to source a flow definition from SCM While I agree with what Nicolas is saying, in the mean time, it's very easy to let the user specify the file in the workspace that defines the workflow, and execute that instead of loading up the script from the text area. This message is automatically generated by JIRA. 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-16411) Downstream-buildview fails to display downstrem build information when Block until the triggered projects finish their builds is set by Parameterized Trigger plugin
Sergey Samylin created JENKINS-16411 Downstream-buildview fails to display downstrem build information when Block until the triggered projects finish their builds is set by Parameterized Trigger plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Downstream build view.jpg, parent_config.jpg Components: downstream-buildview Created: 18/Jan/13 10:13 AM Description: I have a parent job which has one (or more) downstream jobs triggered with the "Parameterized Trigger plugin". When I set "Block until the triggered projects finish their builds" for downstream projects in the parent project configuration and then look at the downstream view for the parent job run, there is "build number # (NOT_BUILT)" displayed. When "Block until the triggered projects finish their builds" is not set then build information is displayed. Environment: Jenkins (version 1.499) Parameterized Trigger plugin (version 2.16) Downstream build view (version 1.8) Project: Jenkins Priority: Major Reporter: Sergey Samylin This message is automatically generated by JIRA. 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-12330) Occasionally,collecting findbugs analysis files will take very long time, event two more hours.
Ulli Hafner commented on JENKINS-12330 Occasionally,collecting findbugs analysis files will take very long time, event two more hours. @michael: please attach a thread dump. How many warnings do you have? This message is automatically generated by JIRA. 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-11535) Jenkins job triggering automatically even though there is no change in the repository claiming the repository is corrupted.
Kimmo Koskinen commented on JENKINS-11535 Jenkins job triggering automatically even though there is no change in the repository claiming the repository is corrupted. I ran into the same problem too. The output of "git rev-parse" just happens to contain a newline. So I happened to look at the manual page of rev-parse and saw this option: --sq Usually the output is made one line per flag and parameter. This option makes output a single line, properly quoted for consumption by shell. Useful when you expect your parameter to contain whitespaces and newlines (e.g. when using pickaxe -S with git diff-*). In contrast to the --sq-quote option, the command input is still interpreted as usual. Here is an example when run on a windows box: git rev-parse --sq 64b62d8698dddafb06362a92d3fcaf7a36b91835 '64b62d8698dddafb06362a92d3fcaf7a36b91835' Maybe this could help resolve the ambiguity of what belongs to the result and what not (some github pull requests mention getting rid of error output mixed together with the actual output). This message is automatically generated by JIRA. 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-16096) Support for inclusions, exclusions
Thomas Zlika commented on JENKINS-16096 Support for inclusions, exclusions It would be nice if the jacoco-maven-plugin "excludes" parameter was taken into account by Jenkins. This message is automatically generated by JIRA. 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-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Thomas Zlika commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Yes, the problem is still present with the latest 1.0.9 version. I have some packages excluded from code coverage using the "excludes" parameter of the jacoco-maven-plugin. The HTML page generated by this plugin are correct (the excludes packages are not taken into account). However, the Jenkins plugin take them into account and display a code coverage of 0%. The configuration for the Jenkins plugin is the standard one: Path to exec files: **/target/jacoco.exec Path to class dir: **/target/classes Path to source dir: **/src/main/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-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Markus Meisterernst assigned JENKINS-14193 to Markus Meisterernst EnvInject doesnt pass variables defined in prebuild step if maven project is used Change By: Markus Meisterernst (18/Jan/13 10:49 AM) Assignee: GregoryBoissinot MarkusMeisterernst This message is automatically generated by JIRA. 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-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Markus Meisterernst assigned JENKINS-14193 to Gregory Boissinot EnvInject doesnt pass variables defined in prebuild step if maven project is used sorry I messed with Jira Change By: Markus Meisterernst (18/Jan/13 10:50 AM) Assignee: MarkusMeisterernst GregoryBoissinot This message is automatically generated by JIRA. 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-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Markus Meisterernst edited a comment on JENKINS-14193 EnvInject doesnt pass variables defined in prebuild step if maven project is used sorry I messed with Jira (incidentally clicked the AssignToMe Button). argh. Reassigned it to its own, sorry for that. This message is automatically generated by JIRA. 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-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Markus Meisterernst edited a comment on JENKINS-14193 EnvInject doesnt pass variables defined in prebuild step if maven project is used sorry I messed with Jira (incidentally clicked the AssignToMe Button). argh. Reassigned it to its owner, sorry for that. This message is automatically generated by JIRA. 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-16384) Blocking on downstream projects
Alex Vesely commented on JENKINS-16384 Blocking on downstream projects Yes, I forgot to mention that "Block when downstream is building" is of course enabled in A. Posting publishers for all 5 jobs: job_A: publishers hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_B/projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers hudson.plugins.emailext.plugins.trigger.FailureTrigger email recipientList/recipientList subject$PROJECT_DEFAULT_SUBJECT/subject body$PROJECT_DEFAULT_CONTENT/body sendToDeveloperstrue/sendToDevelopers sendToRequesterfalse/sendToRequester includeCulpritsfalse/includeCulprits sendToRecipientListtrue/sendToRecipientList /email /hudson.plugins.emailext.plugins.trigger.FailureTrigger /configuredTriggers contentTypedefault/contentType defaultSubject$DEFAULT_SUBJECT/defaultSubject defaultContent$DEFAULT_CONTENT/defaultContent attachmentsPattern/attachmentsPattern presendScript/presendScript /hudson.plugins.emailext.ExtendedEmailPublisher /publishers job_B: publishers hudson.plugins.logparser.LogParserPublisher unstableOnWarningfalse/unstableOnWarning failBuildOnErrortrue/failBuildOnError parsingRulesPathmake.error/parsingRulesPath /hudson.plugins.logparser.LogParserPublisher hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_C, job_D/projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger join.JoinTrigger joinProjects/joinProjects joinPublishers hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.PredefinedBuildParameters propertiesA_CUSTOM_PARAMETER=HELLO/properties /hudson.plugins.parameterizedtrigger.PredefinedBuildParameters hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_E, /projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger /joinPublishers evenIfDownstreamUnstablefalse/evenIfDownstreamUnstable /join.JoinTrigger hudson.notify.UpDownStreamNumberSychronizedNotify times10/times itimes10/itimes /hudson.notify.UpDownStreamNumberSychronizedNotify hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers/ contentTypedefault/contentType defaultSubject$DEFAULT_SUBJECT/defaultSubject defaultContent$DEFAULT_CONTENT/defaultContent attachmentsPattern/attachmentsPattern presendScript/presendScript matrixTriggerModeONLY_PARENT/matrixTriggerMode /hudson.plugins.emailext.ExtendedEmailPublisher /publishers job_C: publishers hudson.tasks.ArtifactArchiver artifacts*/test//.log/artifacts latestOnlyfalse/latestOnly /hudson.tasks.ArtifactArchiver hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers hudson.plugins.emailext.plugins.trigger.FailureTrigger email recipientList/recipientList
[JIRA] (JENKINS-16384) Blocking on downstream projects
Alex Vesely edited a comment on JENKINS-16384 Blocking on downstream projects Yes, I forgot to mention that "Block when downstream is building" is of course enabled in A. Posting publishers for all 5 jobs: job_A: publishers hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_B/projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers hudson.plugins.emailext.plugins.trigger.FailureTrigger email recipientList/recipientList subject$PROJECT_DEFAULT_SUBJECT/subject body$PROJECT_DEFAULT_CONTENT/body sendToDeveloperstrue/sendToDevelopers sendToRequesterfalse/sendToRequester includeCulpritsfalse/includeCulprits sendToRecipientListtrue/sendToRecipientList /email /hudson.plugins.emailext.plugins.trigger.FailureTrigger /configuredTriggers contentTypedefault/contentType defaultSubject$DEFAULT_SUBJECT/defaultSubject defaultContent$DEFAULT_CONTENT/defaultContent attachmentsPattern/attachmentsPattern presendScript/presendScript /hudson.plugins.emailext.ExtendedEmailPublisher /publishers job_B: publishers hudson.plugins.logparser.LogParserPublisher unstableOnWarningfalse/unstableOnWarning failBuildOnErrortrue/failBuildOnError parsingRulesPathmake.error/parsingRulesPath /hudson.plugins.logparser.LogParserPublisher hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_C, job_D/projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger join.JoinTrigger joinProjects/joinProjects joinPublishers hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.PredefinedBuildParameters propertiesA_CUSTOM_PARAMETER=HELLO/properties /hudson.plugins.parameterizedtrigger.PredefinedBuildParameters hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_E, /projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger /joinPublishers evenIfDownstreamUnstablefalse/evenIfDownstreamUnstable /join.JoinTrigger hudson.notify.UpDownStreamNumberSychronizedNotify times10/times itimes10/itimes /hudson.notify.UpDownStreamNumberSychronizedNotify hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers/ contentTypedefault/contentType defaultSubject$DEFAULT_SUBJECT/defaultSubject defaultContent$DEFAULT_CONTENT/defaultContent attachmentsPattern/attachmentsPattern presendScript/presendScript matrixTriggerModeONLY_PARENT/matrixTriggerMode /hudson.plugins.emailext.ExtendedEmailPublisher /publishers job_C: publishers hudson.tasks.ArtifactArchiver artifacts**/test/**/*.log/artifacts latestOnlyfalse/latestOnly /hudson.tasks.ArtifactArchiver hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers hudson.plugins.emailext.plugins.trigger.FailureTrigger email
[JIRA] (JENKINS-16384) Blocking on downstream projects
Alex Vesely edited a comment on JENKINS-16384 Blocking on downstream projects Yes, I forgot to mention that "Block when downstream is building" is of course enabled in A. Posting publishers for all 5 jobs: job_A: publishers hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_B/projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers hudson.plugins.emailext.plugins.trigger.FailureTrigger email recipientList/recipientList subject$PROJECT_DEFAULT_SUBJECT/subject body$PROJECT_DEFAULT_CONTENT/body sendToDeveloperstrue/sendToDevelopers sendToRequesterfalse/sendToRequester includeCulpritsfalse/includeCulprits sendToRecipientListtrue/sendToRecipientList /email /hudson.plugins.emailext.plugins.trigger.FailureTrigger /configuredTriggers contentTypedefault/contentType defaultSubject$DEFAULT_SUBJECT/defaultSubject defaultContent$DEFAULT_CONTENT/defaultContent attachmentsPattern/attachmentsPattern presendScript/presendScript /hudson.plugins.emailext.ExtendedEmailPublisher /publishers job_B: publishers hudson.plugins.logparser.LogParserPublisher unstableOnWarningfalse/unstableOnWarning failBuildOnErrortrue/failBuildOnError parsingRulesPathmake.error/parsingRulesPath /hudson.plugins.logparser.LogParserPublisher hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_C, job_D/projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger join.JoinTrigger joinProjects/joinProjects joinPublishers hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.PredefinedBuildParameters propertiesA_CUSTOM_PARAMETER=HELLO/properties /hudson.plugins.parameterizedtrigger.PredefinedBuildParameters hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_E, /projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger /joinPublishers evenIfDownstreamUnstablefalse/evenIfDownstreamUnstable /join.JoinTrigger hudson.notify.UpDownStreamNumberSychronizedNotify times10/times itimes10/itimes /hudson.notify.UpDownStreamNumberSychronizedNotify hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers/ contentTypedefault/contentType defaultSubject$DEFAULT_SUBJECT/defaultSubject defaultContent$DEFAULT_CONTENT/defaultContent attachmentsPattern/attachmentsPattern presendScript/presendScript matrixTriggerModeONLY_PARENT/matrixTriggerMode /hudson.plugins.emailext.ExtendedEmailPublisher /publishers job_C: publishers hudson.tasks.ArtifactArchiver artifacts**/test/**/*.log/artifacts latestOnlyfalse/latestOnly /hudson.tasks.ArtifactArchiver hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers hudson.plugins.emailext.plugins.trigger.FailureTrigger email recipientList/recipientList
[JIRA] (JENKINS-16384) Blocking on downstream projects
Alex Vesely edited a comment on JENKINS-16384 Blocking on downstream projects Yes, I forgot to mention that "Block when downstream is building" is of course enabled in A. Posting publishers for all 5 jobs: job_A: publishers hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_B/projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers hudson.plugins.emailext.plugins.trigger.FailureTrigger email recipientList/recipientList subject$PROJECT_DEFAULT_SUBJECT/subject body$PROJECT_DEFAULT_CONTENT/body sendToDeveloperstrue/sendToDevelopers sendToRequesterfalse/sendToRequester includeCulpritsfalse/includeCulprits sendToRecipientListtrue/sendToRecipientList /email /hudson.plugins.emailext.plugins.trigger.FailureTrigger /configuredTriggers contentTypedefault/contentType defaultSubject$DEFAULT_SUBJECT/defaultSubject defaultContent$DEFAULT_CONTENT/defaultContent attachmentsPattern/attachmentsPattern presendScript/presendScript /hudson.plugins.emailext.ExtendedEmailPublisher /publishers job_B: publishers hudson.plugins.logparser.LogParserPublisher unstableOnWarningfalse/unstableOnWarning failBuildOnErrortrue/failBuildOnError parsingRulesPathmake.error/parsingRulesPath /hudson.plugins.logparser.LogParserPublisher hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_C, job_D/projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger join.JoinTrigger joinProjects/joinProjects joinPublishers hudson.plugins.parameterizedtrigger.BuildTrigger configs hudson.plugins.parameterizedtrigger.BuildTriggerConfig configs hudson.plugins.parameterizedtrigger.PredefinedBuildParameters propertiesA_CUSTOM_PARAMETER=HELLO/properties /hudson.plugins.parameterizedtrigger.PredefinedBuildParameters hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ /configs projectsjob_E, /projects conditionSUCCESS/condition triggerWithNoParametersfalse/triggerWithNoParameters /hudson.plugins.parameterizedtrigger.BuildTriggerConfig /configs /hudson.plugins.parameterizedtrigger.BuildTrigger /joinPublishers evenIfDownstreamUnstablefalse/evenIfDownstreamUnstable /join.JoinTrigger hudson.notify.UpDownStreamNumberSychronizedNotify times10/times itimes10/itimes /hudson.notify.UpDownStreamNumberSychronizedNotify hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers/ contentTypedefault/contentType defaultSubject$DEFAULT_SUBJECT/defaultSubject defaultContent$DEFAULT_CONTENT/defaultContent attachmentsPattern/attachmentsPattern presendScript/presendScript matrixTriggerModeONLY_PARENT/matrixTriggerMode /hudson.plugins.emailext.ExtendedEmailPublisher /publishers job_C: publishers hudson.tasks.ArtifactArchiver artifacts**/test/**/*.log/artifacts latestOnlyfalse/latestOnly /hudson.tasks.ArtifactArchiver hudson.plugins.emailext.ExtendedEmailPublisher recipientList$DEFAULT_RECIPIENTS/recipientList configuredTriggers hudson.plugins.emailext.plugins.trigger.FailureTrigger email recipientList/recipientList
[JIRA] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
Matti Linnanvuori commented on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) I have this issue intermittently even after linking emulator to emulator-arm. The emulator processes keep piling up because the plugin does not kill them after unsuccessfully trying to connect to them. Building remotely on madmax2 in workspace /var/lib/jenkins/projects/avt/tests Starting xvnc tests $ vncserver :11 -localhost -nolisten tcp New 'X' desktop is madmax2.ecolane.com:11 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/madmax2.ecolane.com:11.log android Using Android SDK: /opt/adt-bundle-linux-x86_64/sdk android Waiting 1 seconds before starting emulator... $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb start-server android Starting Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/tools/emulator -no-boot-anim -ports 56341,34347 -avd Android2.2GoogleAPIs -no-snapshot-load -no-snapshot-save daemon not running. starting it now on port 50229 * daemon started successfully * android Emulator did not appear to start; giving up $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb disconnect localhost:34347 android Stopping Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb kill-server Taking screenshot. tests $ import -window root -display :11 screenshot.jpg Terminating xvnc. $ vncserver -kill :11 Killing Xtightvnc process ID 18436 This message is automatically generated by JIRA. 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-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
Matti Linnanvuori edited a comment on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) I have this issue intermittently even after linking emulator to emulator-arm. The emulator processes keep piling up because the plugin does not kill them after unsuccessfully trying to connect to them. I have tried to fix the issue by building a private version of the plugin with setting the ignore variable to true even for UNIX but it did not help. Building remotely on madmax2 in workspace /var/lib/jenkins/projects/avt/tests Starting xvnc tests $ vncserver :11 -localhost -nolisten tcp New 'X' desktop is madmax2.ecolane.com:11 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/madmax2.ecolane.com:11.log android Using Android SDK: /opt/adt-bundle-linux-x86_64/sdk android Waiting 1 seconds before starting emulator... $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb start-server android Starting Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/tools/emulator -no-boot-anim -ports 56341,34347 -avd Android2.2GoogleAPIs -no-snapshot-load -no-snapshot-save daemon not running. starting it now on port 50229 * daemon started successfully * android Emulator did not appear to start; giving up $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb disconnect localhost:34347 android Stopping Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb kill-server Taking screenshot. tests $ import -window root -display :11 screenshot.jpg Terminating xvnc. $ vncserver -kill :11 Killing Xtightvnc process ID 18436 This message is automatically generated by JIRA. 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-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
Matti Linnanvuori edited a comment on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) I have this issue intermittently even after linking emulator to emulator-arm. The emulator processes keep piling up because the plugin does not kill them after unsuccessfully trying to connect to them. I have tried to fix the issue by building a private version of the plugin with setting the ignore variable to true even for UNIX but it did not help. My environment is Xen Linux 3.2.0-3-amd64 #1 SMP 86_64 Debian GNU/Linux wheezy/sid. Building remotely on madmax2 in workspace /var/lib/jenkins/projects/avt/tests Starting xvnc tests $ vncserver :11 -localhost -nolisten tcp New 'X' desktop is madmax2.ecolane.com:11 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/madmax2.ecolane.com:11.log android Using Android SDK: /opt/adt-bundle-linux-x86_64/sdk android Waiting 1 seconds before starting emulator... $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb start-server android Starting Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/tools/emulator -no-boot-anim -ports 56341,34347 -avd Android2.2GoogleAPIs -no-snapshot-load -no-snapshot-save daemon not running. starting it now on port 50229 * daemon started successfully * android Emulator did not appear to start; giving up $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb disconnect localhost:34347 android Stopping Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb kill-server Taking screenshot. tests $ import -window root -display :11 screenshot.jpg Terminating xvnc. $ vncserver -kill :11 Killing Xtightvnc process ID 18436 This message is automatically generated by JIRA. 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
cforce commented on JENKINS-16319 Failure to delete old config files during rekeying on Windows Here to on windows serever 2008 with jenkins running on tomcat as windows service with own user in winndows tomcat runs from. This user has write/read bright on the complete partition jenkins_home is saved. Till today this alls worked without problems. Please provide 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
[JIRA] (JENKINS-16319) Failure to delete old config files during rekeying on Windows
cforce updated JENKINS-16319 Failure to delete old config files during rekeying on Windows Change By: cforce (18/Jan/13 12:41 PM) Priority: Major Critical This message is automatically generated by JIRA. 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-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
Matti Linnanvuori edited a comment on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) I have this issue intermittently even after linking emulator to emulator-arm. The emulator processes keep piling up because the plugin does not kill them after unsuccessfully trying to connect to them. I have tried to fix the issue by building a private version of the plugin with setting the ignore variable to true even for UNIX but it did not help. My environment is Xen Linux 3.2.0-3-amd64 #1 SMP 86_64 Debian GNU/Linux wheezy/sid. One problem I have had is that the emulator does not always get the display started by the xvnc plugin right because you cannot specify the display that the xvnc plugin starts. Building remotely on madmax2 in workspace /var/lib/jenkins/projects/avt/tests Starting xvnc tests $ vncserver :11 -localhost -nolisten tcp New 'X' desktop is madmax2.ecolane.com:11 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/madmax2.ecolane.com:11.log android Using Android SDK: /opt/adt-bundle-linux-x86_64/sdk android Waiting 1 seconds before starting emulator... $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb start-server android Starting Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/tools/emulator -no-boot-anim -ports 56341,34347 -avd Android2.2GoogleAPIs -no-snapshot-load -no-snapshot-save daemon not running. starting it now on port 50229 * daemon started successfully * android Emulator did not appear to start; giving up $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb disconnect localhost:34347 android Stopping Android emulator $ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb kill-server Taking screenshot. tests $ import -window root -display :11 screenshot.jpg Terminating xvnc. $ vncserver -kill :11 Killing Xtightvnc process ID 18436 This message is automatically generated by JIRA. 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-16412) Remove sticky date tags not working when local name not set and only one module is used
Sascha Vogt created JENKINS-16412 Remove sticky date tags not working when local name not set and only one module is used Issue Type: Bug Assignee: Unassigned Components: cvs Created: 18/Jan/13 12:59 PM Description: If I got it correctly, the removal of the sticky date tags happens in AbstractCvs.postCheckout, where the path workspace.child(module.getCheckoutName()) is used. Now, if only one module is checked out and the local name is not set, the project is actually checked out in the root directory of the workspace, while module.getCheckoutName() will return the CVS module name. Failing to cleanup the sticky date tags causes the M2 release plugin to fail Project: Jenkins Priority: Major Reporter: Sascha Vogt This message is automatically generated by JIRA. 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-16375) show job difference does not work, url escaped twice
Kathi Stutz resolved JENKINS-16375 as Fixed show job difference does not work, url escaped twice Version 2.1 was released today. It contains a great new feature (build badges!) as well as new URL parameters. Change By: Kathi Stutz (18/Jan/13 1:05 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-11535) Jenkins job triggering automatically even though there is no change in the repository claiming the repository is corrupted.
Murali Srinivasan commented on JENKINS-11535 Jenkins job triggering automatically even though there is no change in the repository claiming the repository is corrupted. This is not happening anymore, I'm not sure how it got resolved. Probably the later version might have solved this 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-16412) Remove sticky date tags not working when local name not set and only one module is used
Sascha Vogt commented on JENKINS-16412 Remove sticky date tags not working when local name not set and only one module is used Pull request at https://github.com/jenkinsci/cvs-plugin/pull/17 This message is automatically generated by JIRA. 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-16407) Android Emulator plugin does not compile with Java 7
Christopher Orr commented on JENKINS-16407 Android Emulator plugin does not compile with Java 7 Yeah, I might increase the Jenkins requirement, which would fix this. According to JENKINS-8942, this may have been fixed in Jenkins ~1.420. That sounds about right, as I've previously compiled this plugin on JDK 7 by changing the version in pom.xml to 1.424 (an LTS release). This message is automatically generated by JIRA. 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-16399) SCM documentation is incorrect
Walter Kacynski closed JENKINS-16399 as Fixed SCM documentation is incorrect Change By: Walter Kacynski (18/Jan/13 1:38 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-12547) ec2-plugin doesn't allow for multiple EC2 clouds to be configured
Eric Smalling commented on JENKINS-12547 ec2-plugin doesnt allow for multiple EC2 clouds to be configured Seeing some problems with my change, will investigate more... This message is automatically generated by JIRA. 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-11535) Jenkins job triggering automatically even though there is no change in the repository claiming the repository is corrupted.
Kimmo Koskinen commented on JENKINS-11535 Jenkins job triggering automatically even though there is no change in the repository claiming the repository is corrupted. Hmm, odd, since I'm seeing this with git version 1.8.0.msysgit.0, Jenkins 1.499, Git plugin 1.1.26. What is more odd is that if I redirect the output to a file, I don't see extra newline. And seems that other commands, like "git status" have extra newline when run from cmd.exe, hmm... This message is automatically generated by JIRA. 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-16412) Remove sticky date tags not working when local name not set and only one module is used
SCM/JIRA link daemon resolved JENKINS-16412 as Fixed Remove sticky date tags not working when local name not set and only one module is used Change By: SCM/JIRA link daemon (18/Jan/13 2:00 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-16412) Remove sticky date tags not working when local name not set and only one module is used
SCM/JIRA link daemon commented on JENKINS-16412 Remove sticky date tags not working when local name not set and only one module is used Code changed in jenkins User: Sascha Vogt Path: src/main/java/hudson/scm/AbstractCvs.java http://jenkins-ci.org/commit/cvs-plugin/eca20caaa7be08297b177a0cb24afef97e289b3a Log: FIXED JENKINS-16412 Don't use the module name for cleanup if flatten is true This message is automatically generated by JIRA. 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-16412) Remove sticky date tags not working when local name not set and only one module is used
SCM/JIRA link daemon commented on JENKINS-16412 Remove sticky date tags not working when local name not set and only one module is used Code changed in jenkins User: mc1arke Path: src/main/java/hudson/scm/AbstractCvs.java http://jenkins-ci.org/commit/cvs-plugin/e1d22aa5de3bed53233276431e85453e3cc65ce0 Log: Merge pull request #17 from svogt/master JENKINS-16412 Don't use local name on workspace cleanup if flatten is true Compare: https://github.com/jenkinsci/cvs-plugin/compare/7366c494f973...e1d22aa5de3b This message is automatically generated by JIRA. 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-16412) Remove sticky date tags not working when local name not set and only one module is used
SCM/JIRA link daemon commented on JENKINS-16412 Remove sticky date tags not working when local name not set and only one module is used Code changed in jenkins User: Sascha Vogt Path: src/main/java/hudson/scm/AbstractCvs.java http://jenkins-ci.org/commit/cvs-plugin/1201f8be1a4f564727bc3d9049c6769b2af2fb27 Log: FIXED JENKINS-16412 Don't use the module name for cleanup if flatten is true This message is automatically generated by JIRA. 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-16413) Compatibility config-file-provider and release plugins
Dominique Arnou created JENKINS-16413 Compatibility config-file-provider and release plugins Issue Type: Bug Affects Versions: current Assignee: domi Components: config-file-provider, release Created: 18/Jan/13 2:02 PM Description: The differents maven settings provided by the plugin "config-file-provider" are not available with release plugin Project: Jenkins Priority: Major Reporter: Dominique Arnou This message is automatically generated by JIRA. 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-16413) Compatibility config-file-provider and release plugins
Dominique Arnou commented on JENKINS-16413 Compatibility config-file-provider and release plugins Without my global settings file provided as input, the release plugin seeking my own artifacts in the repository instead of mine This message is automatically generated by JIRA. 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-16349) People view aborts and returns nothing
alexlombardi commented on JENKINS-16349 People view aborts and returns nothing Not using Gravatar plugin. Adding another Thread Dump doc. This message is automatically generated by JIRA. 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-16349) People view aborts and returns nothing
alexlombardi updated JENKINS-16349 People view aborts and returns nothing Another thread Dump as requested. Change By: alexlombardi (18/Jan/13 2:15 PM) Attachment: ThreadDump1-18-2013.doc This message is automatically generated by JIRA. 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-15680) I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml'
Sascha Vogt commented on JENKINS-15680 I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml Actually I think this was related to https://issues.jenkins-ci.org/browse/JENKINS-16412 Maybe this one can be closed as well? This message is automatically generated by JIRA. 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-16042) NullPointer when collecting successful results
damian dixon commented on JENKINS-16042 NullPointer when collecting successful results For those needing a quick fix a snapshot is here (works for me): https://buildhive.cloudbees.com/job/jenkinsci/job/tikal-multijob-plugin/org.jenkins-ci.plugins$jenkins-multijob-plugin/ Upload the hpi you downloaded into your jenkins and uninstall the current plugin. Restart. You will need to check back to the jenkins website regularly to see if a new version has been released. When that occurs remove the snapshot and install the new 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-16234) Plugin does not currently work for Clearcase Base
Steve Davidson commented on JENKINS-16234 Plugin does not currently work for Clearcase Base We need to get rid of that "stgloc auto". As of the last pull, this is still an issue. Job Output; Started by user Stephen Davidson Building remotely on DevBuild in workspace /export/home/jenkins.dev/workspace/DemoWestBuild_JanRVL DevJenkins_DevBuild_DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool lsview -cview -s INFO computeChangeLogBeforeCheckout = false INFO computeChangeLogAfterCheckout = true DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool lsview DevJenkins_DevBuild_DemoWestBuild_JanRVL cleartool: Error: No matching entries found for view tag "DevJenkins_DevBuild_DemoWestBuild_JanRVL". FATAL: Base ClearCase failed. exit code=1 DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool mkview -snapshot -tag DevJenkins_DevBuild_DemoWestBuild_JanRVL -stgloc -auto DevJenkins_DevBuild_DemoWestBuild_JanRVL cleartool: Error: No available Server Storage Location entries. FATAL: Base ClearCase failed. exit code=1 java.io.IOException: cleartool did not return the expected exit code. Command line="mkview -snapshot -tag DevJenkins_DevBuild_DemoWestBuild_JanRVL b-stgloc -auto/b DevJenkins_DevBuild_DemoWestBuild_JanRVL", actual exit code=1 at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:121) at hudson.plugins.clearcase.ClearToolExec.mkview(ClearToolExec.java:657) at hudson.plugins.clearcase.action.SnapshotCheckoutAction.cleanAndCreateViewIfNeeded(SnapshotCheckoutAction.java:163) at hudson.plugins.clearcase.action.BaseSnapshotCheckoutAction.checkout(BaseSnapshotCheckoutAction.java:53) at hudson.plugins.clearcase.AbstractClearCaseScm.checkout(AbstractClearCaseScm.java:667) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Sending e-mails to: stephen.david...@one.verizon.com Finished: FAILURE The appropriate command line here is something along the lines of: mkview -tag DevJenkins_DevBuild_DemoWestBuild_JanRVL -snapshot DevJenkins_DevBuild_DemoWestBuild_JanRVL Btw, this is approximately equivalent to the IBM documented command line of; mkview -tag dev -snapshot ~bert/my_views Suggestions as to how to get the plugin to generate this command line please? -Steve This message is automatically generated by JIRA. 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-16234) Plugin does not currently work for Clearcase Base
Steve Davidson updated JENKINS-16234 Plugin does not currently work for Clearcase Base Change By: Steve Davidson (18/Jan/13 2:48 PM) Priority: Major Critical This message is automatically generated by JIRA. 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-16414) com.thoughtworks.xstream.mapper.CannotResolveClassException: log : log
Arvid E.P created JENKINS-16414 com.thoughtworks.xstream.mapper.CannotResolveClassException: log : log Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: clone-workspace-scm Created: 18/Jan/13 3:05 PM Description: Building remotely on emu01 in workspace /home/jenkins/workspace/test-emulator-mw Restoring workspace from build #13 of project imager-emulator FATAL: log : log com.thoughtworks.xstream.mapper.CannotResolveClassException: log : log at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:68) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:71) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:86) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:96) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:249) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:43) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:56) at com.thoughtworks.xstream.core.util.HierarchicalStreams.readClassType(HierarchicalStreams.java:29) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:136) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:33) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:926) at hudson.util.XStream2.unmarshal(XStream2.java:103) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:912) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:856) at hudson.plugins.repo.ChangeLog.parse(ChangeLog.java:76) at hudson.plugins.repo.ChangeLog.parse(ChangeLog.java:56) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:925) at hudson.model.AbstractBuild.access$600(AbstractBuild.java:100) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:687) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236)
[JIRA] (JENKINS-16389) Emailing users at the end of a failed build very slow for big Jenkins instance using CVS
kutzi assigned JENKINS-16389 to Unassigned Emailing users at the end of a failed build very slow for big Jenkins instance using CVS Change By: kutzi (18/Jan/13 3:40 PM) Assignee: kutzi This message is automatically generated by JIRA. 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-16349) People view aborts and returns nothing
alexlombardi edited a comment on JENKINS-16349 People view aborts and returns nothing Not using Gravatar plugin but have Subversion. Adding another Thread Dump doc. This message is automatically generated by JIRA. 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
Martin dAnjou commented on JENKINS-15156 Builds Disappear from Build History after Completion We're using 1.492. Suddenly, builds #1 to #9 disappeared. After a day or two we decided to launch a build using a different user account. Now the builds do show up, but only starting at #10. I agree with making this bug a 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-16234) Plugin does not currently work for Clearcase Base
Vincent Latombe commented on JENKINS-16234 Plugin does not currently work for Clearcase Base Hello Steve, The new version introduces 'Default' as a new view storage strategy for jobs (under the advanced section in the job configurationclearcase section). Try with that. This message is automatically generated by JIRA. 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-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Mirko Friedenhagen commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Same here, I exclude the generated HelpMojo: in build https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L134 and reporting https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L166 Maven only needs the exclusion for the report mojo, though. This message is automatically generated by JIRA. 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-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Mirko Friedenhagen edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Same here, I exclude the generated HelpMojo: in build https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L134 and reporting https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L166 Maven only needs the exclusion for the report mojo, though. jacoco's version is: 0.6.1.201212231917. This message is automatically generated by JIRA. 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-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Mirko Friedenhagen edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Same here, I exclude the generated HelpMojo: in build https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L134 and reporting https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L166 Maven only needs the exclusion for the report mojo, though. jacoco's version is: 0.6.1.201212231917. Maybe the Jenkins-Plugin should just drop all .class files where no .java files are found? This message is automatically generated by JIRA. 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-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Mirko Friedenhagen edited a comment on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Same here, I exclude the generated HelpMojo: in build https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L134 and reporting https://github.com/1and1/bill-of-materials-maven-plugin/blob/a7c20afe67620df3c3be0458ddd23a596398af33/pom.xml#L166 Maven only needs the exclusion for the report mojo, though. jacoco's version is: 0.6.1.201212231917. Maybe the Jenkins-Plugin should just drop all .class files where no .java files are found? This message is automatically generated by JIRA. 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-15237) Dependent Maven Jobs ignore version-number
Andrei Pozolotin commented on JENKINS-15237 Dependent Maven Jobs ignore version-number I am curious is this really fixed by #15367 ? This message is automatically generated by JIRA. 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-15237) Dependent Maven Jobs ignore version-number
Andrei Pozolotin edited a comment on JENKINS-15237 Dependent Maven Jobs ignore version-number I am curious is this really fixed by #JENINS-15367 ? This message is automatically generated by JIRA. 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-15237) Dependent Maven Jobs ignore version-number
Andrei Pozolotin edited a comment on JENKINS-15237 Dependent Maven Jobs ignore version-number I am curious is this really fixed by #JENKINS-15367 ? This message is automatically generated by JIRA. 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-3761) When login j_acegi_security_check return a 404 error
Ingo Wiese commented on JENKINS-3761 When login j_acegi_security_check return a 404 error Maybe this helps. I was able to login when accessing jenkins directly (port 8080) and wasn't when I tried to login through an apache proxy. The error was caused by a proxy pass rule "/jenkins http://localhost:9080/jenkins/" which led to the incomming (jenkins) request "/jenkins//j_acegi_security_check" (double //). So the login page was rejected with 404 (while all other pages where served). Changing the rule to "/jenkins http://localhost:9080/jenkins" solved 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-16415) Unable to add project roles using Role stratedy plugin
Uma shankar created JENKINS-16415 Unable to add project roles using Role stratedy plugin Issue Type: Bug Affects Versions: current Assignee: Daniel Petisme Components: role-strategy Created: 18/Jan/13 6:01 PM Description: I am unable to add Project roles when i use Role strategy plugin. After clicking on Add button, it does not respond. Global roles addition works fin. Jenkins verson tested with: 1.456, LTS 1.480.1 Due Date: 18/Jan/13 12:00 AM Environment: Linux Fix Versions: current Project: Jenkins Priority: Major Reporter: Uma shankar This message is automatically generated by JIRA. 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-16402) HTML in Set Build Description no longer honored
alexlombardi updated JENKINS-16402 HTML in Set Build Description no longer honored Change By: alexlombardi (18/Jan/13 6:39 PM) Description: HTML hyperlink thatwasaddedaspartofthebuildprocesstothebuilddescription,toallowuserstoclickandlinkto extrnal external information/toolwithinformationspecifictoeachsuccessfulbuild,isnolongerhonored,despiteneitherachangetotheproduceddescriptionoutputorthedescriptionsetterplugin. Suspectsomeformatingisclippingtheankertagentry. This message is automatically generated by JIRA. 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-15466) Fatal Error No Class Definition found for Kernel32
Jesse Glick commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 @hanabi 1.483 introduces direct support for Java 7, bypassing JNA for these calls. This message is automatically generated by JIRA. 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-16349) People view aborts and returns nothing
Jesse Glick resolved JENKINS-16349 as Duplicate People view aborts and returns nothing Change By: Jesse Glick (18/Jan/13 6:46 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
[JIRA] (JENKINS-16128) Broken Jenkins Configuration page when Github SQS plugin is installed
Andrei Pozolotin commented on JENKINS-16128 Broken Jenkins Configuration page when Github SQS plugin is installed we should try to bribe Aaron via FreedomSponsors.org This message is automatically generated by JIRA. 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 Are you using a Maven job, or a Free Style Job? This message is automatically generated by JIRA. 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-16409) Add a Script trigger
Slide-O-Mix commented on JENKINS-16409 Add a Script trigger You could do this now using the pre-send Groovy script This message is automatically generated by JIRA. 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
Walter Kacynski created JENKINS-16416 EXCEPTION_ACCESS_VIOLATION uninstalling Active Directory plugin with GUI Issue Type: Bug Assignee: vjuranek Attachments: hs_err_pid7064.log Components: active-directory, groovy, plugin, update-center Created: 18/Jan/13 7:08 PM Description: I was attempting to uninstall the Active Directory plugin via the GUI and Java terminated with # A fatal error has been detected by the Java Runtime Environment: # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x01a25701, pid=7064, tid=5672 # JRE version: 6.0_29-b11 Java VM: Java HotSpot(TM) Client VM (20.4-b02 mixed mode, sharing windows-x86 ) Problematic frame: J org.kohsuke.stapler.jelly.groovy.GroovyFacet$1.dispatch(Lorg/kohsuke/stapler/RequestImpl;Lorg/kohsuke/stapler/ResponseImpl;Ljava/lang/Object;)Z # If you would like to submit a bug report, please visit: http://java.sun.com/webapps/bugreport/crash.jsp # --- T H R E A D --- Current thread (0x05254000): JavaThread "Handling POST /pluginManager/plugin/active-directory/uninstall : RequestHandlerThread331" daemon _thread_in_Java, id=5672, stack(0x0757,0x075c) Project: Jenkins Priority: Major Reporter: Walter Kacynski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
Jenkins error running the scripts from JDK 1.7
I'm getting this error when i try to run my automation script in jenkins. When I run in IntelliJ or Eclipse, it's running fine since i have installed JDK 1.7. However when i run in Jenkins with the same script, it's giving the error below. [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] \Program Files (x86)\Jenkins\jobs\QA Smoke Test\workspace\src\main\java\Util\DriverManager2.java:[21,15] error: strings in switch are not supported in -source 1.5 mojoFailed org.apache.maven.plugins:maven-compiler-plugin:2.3.2(default-compile)[ERROR] \Program Files (x86)\Jenkins\jobs\QA Smoke Test\workspace\src\main\java\Util\DriverManager.java:[64,20] error: strings in switch are not supported in -source 1.5 Can anyone guide me how to get over this issue? Thanks -- *- If you haven't suffered, you haven't lived your life.* ** Thanks, Sirus
[JIRA] (JENKINS-16234) Plugin does not currently work for Clearcase Base
Steve Davidson commented on JENKINS-16234 Plugin does not currently work for Clearcase Base Ok, checkouts are working! Custom build.xml locations are now broken This is only for the system that Build 53 of this plugin the other Jenkins test prod systems we have are not having this issue (in fact, I am using settings and a job from one of them for this testing). In this case, the build.xml file is in the directory "build_files", and the "Build File" setting in the "Invoke Ant" has been modified to reflect this. And is using the same settings as is working on other targets. Console output is as follows; Started by user Stephen Davidson Building remotely on DevBuild in workspace /export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL DevJenkins_DevBuild_DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool lsview -cview -s DevJenkins_DevBuild_DemoWestBuild_JanRVL DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool lsview DevJenkins_DevBuild_DemoWestBuild_JanRVL DevJenkins_DevBuild_DemoWestBuild_JanRVL /net/eamrsd3/export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL/DevJenkins_DevBuild_DemoWestBuild_JanRVL/.view.stg INFO computeChangeLogBeforeCheckout = true INFO computeChangeLogAfterCheckout = false DevJenkins_DevBuild_DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool pwv -root /export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL/DevJenkins_DevBuild_DemoWestBuild_JanRVL DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool lsview DevJenkins_DevBuild_DemoWestBuild_JanRVL DevJenkins_DevBuild_DemoWestBuild_JanRVL /net/eamrsd3/export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL/DevJenkins_DevBuild_DemoWestBuild_JanRVL/.view.stg DevJenkins_DevBuild_DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool lshistory -all -since 18-jan-13.18:44:13utc+ -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \n%c\n' -branch brtype:APB_MR09_JAN_RVL -nco vob/apb "20130118.124429" "" "/export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL/DevJenkins_DevBuild_DemoWestBuild_JanRVL/vob/apb/build_files/build.xml" "/main/APB_MR09_JAN_RVL/3" "create version" "checkin" Added deploy for built application files. Added aggregate target for deploying to a running WL instance. Added target to stop/start Admin Server. DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool lsview DevJenkins_DevBuild_DemoWestBuild_JanRVL DevJenkins_DevBuild_DemoWestBuild_JanRVL /net/eamrsd3/export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL/DevJenkins_DevBuild_DemoWestBuild_JanRVL/.view.stg DevJenkins_DevBuild_DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool lsview -cview -s DevJenkins_DevBuild_DemoWestBuild_JanRVL Removing view because 'Use Update' isn't checked. DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool rmview -force DevJenkins_DevBuild_DemoWestBuild_JanRVL DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool mkview -snapshot -tag DevJenkins_DevBuild_DemoWestBuild_JanRVL DevJenkins_DevBuild_DemoWestBuild_JanRVL Created view. Host-local path: eamrsd3:/export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL/DevJenkins_DevBuild_DemoWestBuild_JanRVL/.view.stg Global path: /net/eamrsd3/export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL/DevJenkins_DevBuild_DemoWestBuild_JanRVL/.view.stg It has the following rights: User : ... : rwx Group: staff: r-x Other: : r-x Created snapshot view directory "DevJenkins_DevBuild_DemoWestBuild_JanRVL". Running cleartool setcs, this operation may take a while DevJenkins_DevBuild_DemoWestBuild_JanRVL $ /usr/atria/bin/cleartool setcs /export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL/configspec3421279836326354639.txt INFO updt file name: '/export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL/DevJenkins_DevBuild_DemoWestBuild_JanRVL/update.2013-01-18T12:56:08-06:00.updt' build_files $ ant -file build.xml -DAPB_BUILD_HOME=/export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL/DevJenkins_DevBuild_DemoWestBuild_JanRVL/vob/apb all FATAL: command execution failed.Maybe you need to configure the job to choose one of your Ant installations? java.io.IOException: Cannot run program "ant" (in directory "/export/home/jenkins.steve/workspace/DemoWestBuild_JanRVL/DevJenkins_DevBuild_DemoWestBuild_JanRVL/vob/apb/build_files"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at
[JIRA] (JENKINS-16234) Plugin does not currently work for Clearcase Base
Steve Davidson commented on JENKINS-16234 Plugin does not currently work for Clearcase Base Forgot to mention, I cleaned the above output of some internal data (if you see a field with an odd value). I forgot to mention that you needed to take note of the "-f build.xml" in the command line, even though error=2??? Oh dear, that's the "Ant Not Found" scenario. Doing some digging. This message is automatically generated by JIRA. 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-16234) Plugin does not currently work for Clearcase Base
Steve Davidson commented on JENKINS-16234 Plugin does not currently work for Clearcase Base Misconfigured Slave Controller in test master. Confirmed that this patch fixes issue THANKS! I will rebase and document 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-16234) Plugin does not currently work for Clearcase Base
Steve Davidson commented on JENKINS-16234 Plugin does not currently work for Clearcase Base Forgot to add, I should have documentation uploaded with a Pull request by Monday AM. This message is automatically generated by JIRA. 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-16406) Environment variables
Gregory Boissinot started work on JENKINS-16406 Environment variables Change By: Gregory Boissinot (18/Jan/13 7:56 PM) Status: Open InProgress This message is automatically generated by JIRA. 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-16406) Environment variables
Gregory Boissinot commented on JENKINS-16406 Environment variables Please could you describe the complete problem? Thanks This message is automatically generated by JIRA. 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-9258) Remember me on this computer, still getting asked to log in after a few hours
Jon Hyman commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours We upgraded from Jenkins 1.494 to 1.498 and all of the sudden, Remember Me stopped working. The server is running on a small EC2 instance with Amazon's standard AMI. After a few days, I downgraded us back to 1.494 and Remember Me started working 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-9258) Remember me on this computer, still getting asked to log in after a few hours
Stephane Odul commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours John, the issue with 1.494 is different and tracked in JENKINS-16278. This message is automatically generated by JIRA. 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-16402) HTML in Set Build Description no longer honored
alexlombardi updated JENKINS-16402 HTML in Set Build Description no longer honored Change By: alexlombardi (18/Jan/13 9:12 PM) Description: HTMLhyperlinkthatwasaddedaspartofthebuildprocesstothebuilddescription,toallowuserstoclickandlinktoexternalinformation/toolwithinformationspecifictoeachsuccessfulbuild,isnolongerhonored,despiteneitherachangetotheproduceddescriptionoutputorthedescriptionsetterplugin.Suspectsomeformatingisclippingtheankertagentry. AfterdoingsomeresearchIencounteredaproblemwithhowthehtmlwasparsedandstoredinthebuildxmlfile.Anexamplehtmlankertagebeingstorediswrittenasfollows:ahref="">However,whatgetsstoredintheXMLlookslikethis:lt;ahref="">WhenIlookathttp://en.wikipedia.org/wiki/Character_encodings_in_HTMLIseethattheapos;tagisdiscouraged(doesntwork),andthatwhatshouldbeusedis#39;or#x0027;.Whateverencodinggetsusedtoparseandstoremyoriginalhtmlankertagintothebuild.xmlneedstobefixed,orwhateverisreadingitbackwhendisplayinghastobereverted. This message is automatically generated by JIRA. 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-16402) HTML in Set Build Description no longer honored
alexlombardi updated JENKINS-16402 HTML in Set Build Description no longer honored Change By: alexlombardi (18/Jan/13 9:14 PM) Description: HTMLhyperlinkthatwasaddedaspartofthebuildprocesstothebuilddescription,toallowuserstoclickandlinktoexternalinformation/toolwithinformationspecifictoeachsuccessfulbuild,isnolongerhonored,despiteneitherachangetotheproduceddescriptionoutputorthedescriptionsetterplugin.Suspectsomeformatingisclippingtheankertagentry.AfterdoingsomeresearchIencounteredaproblemwithhowthehtmlwasparsedandstoredinthebuildxmlfile.Anexamplehtmlankertagebeingstorediswrittenasfollows:ahref="">However,whatgetsstoredintheXMLlookslikethis:lt;ahref="">WhenIlookathttp://en.wikipedia.org/wiki/Character_encodings_in_HTMLIseethattheapos ; tagisdiscouraged(doesntwork),andthatwhatshouldbeusedis#39 ; or#x0027 ; .Whateverencodinggetsusedtoparseandstoremyoriginalhtmlankertagintothebuild.xmlneedstobefixed,orwhateverisreadingitbackwhendisplayinghastobereverted. This message is automatically generated by JIRA. 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
lcgerke gerke commented on JENKINS-16404 email-ext regression trigger not firing when it should Sorry, should have said: maven job. Thanks! This message is automatically generated by JIRA. 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-16417) Extensibility for Run.whyKeepLog
Jesse Glick created JENKINS-16417 Extensibility for Run.whyKeepLog Issue Type: New Feature Assignee: Unassigned Components: core Created: 18/Jan/13 9:47 PM Description: Currently Run.keepLog(boolean) asks for Run.UPDATE permission to toggle whether or not to keep a given build. It may make sense to distinguish between passing true, which is a relatively harmless act that anyone testing a build might need, and false, which will eventually lead to the build being deleted and which administrators might therefore want to restrict. Perhaps passing false should require DELETE instead of (or in addition to) UPDATE. Then an administrator can be assured that important builds, e.g. corresponding to product releases, will not be deleted casually. To implement this without changing the semantics of the current “keep” badge that some users may rely on or find more convenient, it would be useful to add an extension point to Run.getWhyKeepLog allowing plugins to inject other reasons to keep a build. Then a plugin could offer a keep badge following the semantics described above, without affecting the logic of the standard badge. Other possibilities could be implemented as well, such as a marker which can be removed only by submitting an annotated request going into an administrative queue; or an automated keep for a build whose artifact is known to have been deployed to a Maven release repository (according to hash lookup). The existing overrides—for downstream projects, matrix builds, and Maven module sets—could probably be factored out into extensions too. Project: Jenkins Labels: security extension Priority: Major Reporter: 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-14398) Hard to find IP address of jclouds created slave
John Dyer commented on JENKINS-14398 Hard to find IP address of jclouds created slave Anyone? This message is automatically generated by JIRA. 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-14040) After the build I want to trigger two e-mails
Brian ONeill commented on JENKINS-14040 After the build I want to trigger two e-mails I'd also like to see this happen. Currently I need a way to send 2 e-mails for the Unstable and Failure triggers. This message is automatically generated by JIRA. 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 Ok, I'll see what I can do. I don't currently have any Maven stuff to test with. This message is automatically generated by JIRA. 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
Here is the code for Regression Trigger. I'll have to try and setup something with Maven to test out your issue.
public boolean trigger(AbstractBuild?, ? build) {
if (build.getPreviousBuild() == null)
return build.getResult() == Result.FAILURE;
if (build.getTestResultAction() == null) return false;
if (build.getPreviousBuild().getTestResultAction() == null)
return build.getTestResultAction().getFailCount() 0;
return getNumFailures(build)
getNumFailures(build.getPreviousBuild());
}
This message is automatically generated by JIRA.
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-11771) java.lang.RuntimeException: Failed to instantiate class hudson.triggers.TimerTrigger when adding a space to invalid cron syntax after being warned about invalid input
evernat commented on JENKINS-11771 java.lang.RuntimeException: Failed to instantiate class hudson.triggers.TimerTrigger when adding a space to invalid cron syntax after being warned about invalid input reproduced with Jenkins 1.496 This message is automatically generated by JIRA. 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-9704) jenkins-ci.org is wonky when accessed via HTTPS
evernat commented on JENKINS-9704 jenkins-ci.org is wonky when accessed via HTTPS the captcha in signup seems ok now: https://jenkins-ci.org/account/signup This message is automatically generated by JIRA. 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-11657) Unable to deploy to remote server due to war file not being hosted
evernat commented on JENKINS-11657 Unable to deploy to remote server due to war file not being hosted Is it still necessary to support this with JBoss 4.2.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
[JIRA] (JENKINS-11657) Unable to deploy to remote server due to war file not being hosted
Erik Nelson commented on JENKINS-11657 Unable to deploy to remote server due to war file not being hosted Sorry, I haven't even tried again with this since. I just looked at the log again and it looks like it was probably my fault, since the address it's trying is http://server:18080. Probably meant to reference a variable in my script and quoted it instead. I'll close the 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-11657) Unable to deploy to remote server due to war file not being hosted
Erik Nelson closed JENKINS-11657 as Not A Defect Unable to deploy to remote server due to war file not being hosted User error Change By: Erik Nelson (19/Jan/13 12:23 AM) Status: Open Closed 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
[JIRA] (JENKINS-11401) NullpointerException when sending 'build failed' mail
evernat commented on JENKINS-11401 NullpointerException when sending build failed mail 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-16110) testng suite support
Chris Cooper commented on JENKINS-16110 testng suite support Can you update the documentation to specify that TestNG 6.3.1 is not supported? The documentation on your page says it parses the results generated from org.testng.reporters.XMLReporter but this class does not exist after version 6.3.1 (see search.maven.org). Otherwise I am clueless about what you are asking me to do. I am just using a standard maven configuration for running the tests using testng 6.7. This message is automatically generated by JIRA. 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-16110) testng suite support
Chris Cooper edited a comment on JENKINS-16110 testng suite support Can you update the documentation to specify that TestNG 6.3.1 is not supported? The documentation on your page says it parses the results generated from org.testng.reporters.XMLReporter but this class does not exist after version 6.3.1 (see search.maven.org). Otherwise I am clueless about what you are asking me to do. I am just using a standard maven configuration for running the tests using testng 6.7. Edit: disregard...didn't scroll down far enough I'm still unsure why the XMLReporter isn't enabled by default when you just run standard maven 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
[JIRA] (JENKINS-16110) testng suite support
Nalin Makar commented on JENKINS-16110 testng suite support See https://github.com/cbeust/testng/blob/master/src/main/java/org/testng/reporters/XMLReporter.java and http://search.maven.org/remotecontent?filepath=org/testng/testng/6.8/testng-6.8.jar contains the class. This message is automatically generated by JIRA. 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-9494) Configure System hangs with LOADING gray div covering top half of settings
frank stockmans commented on JENKINS-9494 Configure System hangs with LOADING gray div covering top half of settings I was able to replicate this with Jenkins 1.499. The issue was the clearcase plugin, which broke the setup when upgrading from version 1.3.13 to 1.3.6. For me it was not browser related, since I could replicate on chrome/firefox/safari. Only when I dowgraded this plugin again, it was resolved. This message is automatically generated by JIRA. 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
frank stockmans commented on JENKINS-16165 Configure screen stuck in LOADING state I had the same issue, I could trace it back to an upgrade of the clearcase plugin from 1.3.13 to 1.3.6 on jenkins 1.499. All other plugins are up to date as of today. This message is automatically generated by JIRA. 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
frank stockmans edited a comment on JENKINS-16165 Configure screen stuck in LOADING state I had the same issue, I could trace it back to an upgrade of the clearcase plugin from 1.3.13 to 1.3.6 on jenkins 1.499. All other plugins are up to date as of today. Also I was able to reproduce the error on firefox, chrome and safari with the above setup. This message is automatically generated by JIRA. 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-16418) Cannot start Windows Server 2012 slave.
albert cheng created JENKINS-16418 Cannot start Windows Server 2012 slave. Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 19/Jan/13 1:24 AM Description: When I try to start the Jenkin slave, we encounter the following error. Connecting to 10.0.0.4 ERROR: Access is denied. See http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM for more information about how to resolve this. org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x0005 at org.jinterop.winreg.smb.JIWinRegStub.winreg_CreateKey(JIWinRegStub.java:297) at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:480) at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:427) at org.jvnet.hudson.wmi.WMI.connect(WMI.java:59) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:218) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:204) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.jinterop.dcom.common.JIRuntimeException: Message not found for errorCode: 0x0005 at org.jinterop.winreg.IJIWinReg$createKey.read(IJIWinReg.java:459) at ndr.NdrObject.decode(NdrObject.java:19) at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:138) at rpc.Stub.call(Stub.java:112) at org.jinterop.winreg.smb.JIWinRegStub.winreg_CreateKey(JIWinRegStub.java:291) ... 10 more ream.init(TransactNamedPipeOutputStream.java:32) at jcifs.smb.SmbNamedPipe.getNamedPipeOutputStream(SmbNamedPipe.java:187) at rpc.ncacn_np.RpcTransport.attach(RpcTransport.java:91) at rpc.Stub.attach(Stub.java:104) at rpc.Stub.call(Stub.java:109) at org.jinterop.winreg.smb.JIWinRegStub.winreg_OpenHKCR(JIWinRegStub.java:119) ... 10 more Due Date: 21/Jan/13 12:00 AM Environment: Windows Server 2012 Project: Jenkins Priority: Major Reporter: albert cheng This message is automatically generated by JIRA. 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-15964) All configuration screens are stuck LOADING
frank stockmans commented on JENKINS-15964 All configuration screens are stuck LOADING I resolved my issue by downgrading the clearcase plugin from 1.3.6 on jenkins 1.499. I recommend removing all your plugins and going with a old stable combination. I basically shut down jenkins and keep the .hpi files around for the reboot. Then upgrade them one by one to see which one is causing the error. This message is automatically generated by JIRA. 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-12051) Latest jenkins running on tomcat prevents me from configuring
Laurentius Purba commented on JENKINS-12051 Latest jenkins running on tomcat prevents me from configuring Get the same issue with latest jenkin 1.499 on Freebsd 7.2. Fails on Chrome and Firefox in Ubuntu. This message is automatically generated by JIRA. 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-16234) Plugin does not currently work for Clearcase Base
Vincent Latombe resolved JENKINS-16234 as Fixed Plugin does not currently work for Clearcase Base Fixed in 1.3.13 Change By: Vincent Latombe (19/Jan/13 7:17 AM) 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
