[JIRA] (JENKINS-10771) hudson.util.IOException2: remote file operation failed
Alex Vesely commented on JENKINS-10771 hudson.util.IOException2: remote file operation failed Same problem. Cannot checkout the repo or create a script file due to the "Remote file operation failed" error. Using Jenkins 1.480.1 (LTS). Disconnecting and reconnecting the slave usually helps. But this is a MAJOR headache as it introduces instability that is seemingly absolutely random. I'd say this is a CRITICAL bug, not just Major. This message is automatically generated by JIRA. 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-10771) hudson.util.IOException2: remote file operation failed
Alex Vesely edited a comment on JENKINS-10771 hudson.util.IOException2: remote file operation failed Same problem. Cannot checkout the repo or create a script file due to the "Remote file operation failed" error. Using Jenkins 1.480.1 (LTS). Disconnecting and reconnecting the slave usually helps. But this is a MAJOR headache as it introduces instability that is seemingly absolutely random. I'd say this is a CRITICAL 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-10771) hudson.util.IOException2: remote file operation failed
Alex Vesely edited a comment on JENKINS-10771 hudson.util.IOException2: remote file operation failed Same problem. Cannot checkout the repo or create a script file due to the "Remote file operation failed" error. Using Jenkins 1.480.1 (LTS). Disconnecting and reconnecting the slave usually helps. But this is a MAJOR headache as it introduces instability that seems absolutely random. I'd say this is a CRITICAL 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-10771) hudson.util.IOException2: remote file operation failed
Alex Vesely updated JENKINS-10771 hudson.util.IOException2: remote file operation failed Change By: Alex Vesely (11/Dec/12 8:31 AM) 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-11149) JNLP slave fails to connect if Anonymous has not permission READ
Rainer Weinhold commented on JENKINS-11149 JNLP slave fails to connect if Anonymous has not permission READ This issue is still in the LTS 1.480.1 Version. Had to enable global read, because otherwise the "Jenkins controls this as windows service" doesn't work. Guess this also uses JNLP to start it. ( This can only be a temporarily workaround, there is a reason why anonymous doesn't have this right! ) Since some versions Jenkins supports "api tokens", wouldn't that be a way to go? This message is automatically generated by JIRA. 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-16091) Aborted builds are repeated within subsequent builds
Christian Apel created JENKINS-16091 Aborted builds are repeated within subsequent builds Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Components: core, release Created: 11/Dec/12 8:57 AM Description: If a user is starting a build (e.g. a maven release build with command line parameters including SVN credentials) and this build is aborted by the server, we have identified an issue with the subsequent build. Builds which are aborted by the server are repeated within the following build (even if a different user has started a different build type). We had the issue that another user wanted to start a SNAPSHOT build by clicking on the "Build Now" link, but a "Maven release build" was started instead. This release build was triggered by the current user, but contained the command line parameters of the previously aborted release build. If a build is aborted by the server, it must be ensured that subsequent builds are not started with optional or user defined parameters. Project: Jenkins Priority: Critical Reporter: Christian Apel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11149) JNLP slave fails to connect if Anonymous has not permission READ
Rainer Weinhold commented on JENKINS-11149 JNLP slave fails to connect if Anonymous has not permission READ @Waldek M : Yes, you cannot see something useful. But you also don't get the login dialog (per default). So users are not aware that they have to login to seen anything useful. So from the user perception, the ui seems to "work" but they can't see any projects. This message is automatically generated by JIRA. 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-2556) Use svn switch where applicable
Alexander Wenzel commented on JENKINS-2556 Use svn switch where applicable Having jenkins use 'svn switch' instead of a full checkout when changing the branch of the project would be heavily appreciated. This would save a lot of time, if you have a lot of files in the repository. +1 for a fix for this 4 years old 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-16085) Mail Commander Plugin not working.
Deepal Neema started work on JENKINS-16085 Mail Commander Plugin not working. Change By: Deepal Neema (11/Dec/12 10:07 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16092) Loading project page and running coverage report fails when SourceForge is unavailable
Chris Kramer created JENKINS-16092 Loading project page and running coverage report fails when SourceForge is unavailable Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: cobertura Created: 11/Dec/12 10:07 AM Description: This is a very old problem; it looks like the Cobertura plugin tries to download the coverage.dtd from SourceForge.net on every run AND on every request of the Project's homepage. This is probably part of the coverage.xml parser used in the plugin. In previous versions of Cobertura, the stacktrace for the build looks like this: [INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo:cobertura-maven-plugin:2.5.1:cobertura': Server returned HTTP response code: 503 for URL: http://cobertura.sourceforge.net/xml/coverage-04.dtd Lately we get this error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo:cobertura-maven-plugin:2.5.2:cobertura': Connection reset [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo:cobertura-maven-plugin:2.5.2:cobertura': Connection reset at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:698) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:151) at hudson.maven.Maven2Builder.call(Maven2Builder.java:77) at hudson.maven.Maven2Builder.call(Maven2Builder.java:53) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.maven.plugin.PluginManagerException: Connection reset at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:196) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 28 more Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream
[JIRA] (JENKINS-16085) Mail Commander Plugin not working.
Deepal Neema resolved JENKINS-16085 as Fixed Mail Commander Plugin not working. This problem was resolved... I worked on this and found that port on the server where jenkins installed was not open. After opening the port 110 and 25 this problem was resolved. So, thanks to my network team. Change By: Deepal Neema (11/Dec/12 10:09 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16092) Loading project page and running coverage report fails when SourceForge is unavailable
Chris Kramer
updated JENKINS-16092
Loading project page and running coverage report fails when SourceForge is unavailable
Change By:
Chris Kramer
(11/Dec/12 10:09 AM)
Description:
This is a very old problem; it looks like the Cobertura plugin tries to download the coverage.dtd from SourceForge.net on every run AND on every request of the Project's homepage.
So most of our application jobs fail when:- SourceForge goes offline for maintenance- Or blocks us for hammering the dtd file
This is probably part of the coverage.xml parser used in the plugin.In previous versions of Cobertura, the stacktrace for the build looks like this:{code}[INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo:cobertura-maven-plugin:2.5.1:cobertura': Server returned HTTP response code: 503 for URL: http://cobertura.sourceforge.net/xml/coverage-04.dtd{code}Lately we get this error:{code}[INFO] [ERROR] BUILD ERROR[INFO] [INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo:cobertura-maven-plugin:2.5.2:cobertura': Connection reset[INFO] [INFO] Traceorg.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo:cobertura-maven-plugin:2.5.2:cobertura': Connection reset at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:698) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:151) at hudson.maven.Maven2Builder.call(Maven2Builder.java:77) at hudson.maven.Maven2Builder.call(Maven2Builder.java:53) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)Caused by: org.apache.maven.plugin.PluginManagerException: Connection reset at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:196) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 28 moreCaused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read1(BufferedInputStream.java:258) at java.io.BufferedInputStream.read(BufferedInputS
[JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
Rainer Weinhold commented on JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option Still exists in 1.480.1, Workaround from Tiago Pais works. This message is automatically generated by JIRA. 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-16092) Loading project page and running coverage report fails when SourceForge is unavailable
Chris Kramer
updated JENKINS-16092
Loading project page and running coverage report fails when SourceForge is unavailable
Change By:
Chris Kramer
(11/Dec/12 10:19 AM)
Description:
Cobertura Jenkins plugin: 1.5Cobertura Maven Plugin: 2.5.1Jenkins: 1.492
This is a very old problem; it looks like the Cobertura plugin tries to download the coverage.dtd from SourceForge.net on every run AND on every request of the Project's homepage.So most of our application jobs fail when:- SourceForge goes offline for maintenance- Or blocks us for hammering the dtd fileThis is probably part of the coverage.xml parser used in the plugin.In previous versions of Cobertura, the stacktrace for the build looks like this:{code}[INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo:cobertura-maven-plugin:2.5.1:cobertura': Server returned HTTP response code: 503 for URL: http://cobertura.sourceforge.net/xml/coverage-04.dtd{code}Lately we get this error:{code}[INFO] [ERROR] BUILD ERROR[INFO] [INFO] Internal error in the plugin manager executing goal 'org.codehaus.mojo:cobertura-maven-plugin:2.5.2:cobertura': Connection reset[INFO] [INFO] Traceorg.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo:cobertura-maven-plugin:2.5.2:cobertura': Connection reset at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:698) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:151) at hudson.maven.Maven2Builder.call(Maven2Builder.java:77) at hudson.maven.Maven2Builder.call(Maven2Builder.java:53) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)Caused by: org.apache.maven.plugin.PluginManagerException: Connection reset at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:196) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 28 moreCaused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read1(BufferedI
[JIRA] (JENKINS-16083) HTML Publisher v1.1 regression
Isidro Merayo Castellano commented on JENKINS-16083 HTML Publisher v1.1 regression Thanks!!! Nice 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-16092) Loading project page and running coverage report fails when SourceForge is unavailable
sslavic commented on JENKINS-16092 Loading project page and running coverage report fails when SourceForge is unavailable Maybe this discussion will help: https://community.jboss.org/message/69356#69356 This message is automatically generated by JIRA. 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-16093) Mail Commander: what are the Commands to build a war using subject in mail.
Deepal Neema created JENKINS-16093 Mail Commander: what are the Commands to build a war using subject in mail. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: mailcommander Created: 11/Dec/12 10:45 AM Description: I send the mail with the subject : build JOB_NAME The mail was triggered and build starts but at the end i received the following logs. What's that mean please help. "BUILD SUCCESSFUL Total time: 39 seconds No such job 'payhubvt' java -jar jenkins-cli.jar build args... Starts a build, and optionally waits for a completion. Aside from general scripting use, this command can be used to invoke another job from within a build of one job. With the -s option, this command changes the exit code based on the outcome of the build (exit code 0 indicates a success.) With the -c option, a build will only run if there has been an SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -r VAL : Number of times to retry reading of the output log if it does not exists on first attempt. Defaults to 0. Use with -v. -s : Wait until the completion/abortion of the command -v : Prints out the console output of the build. Use with -s -w : Wait until the start of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the password Build step 'Mail Commander' marked build as failure Finished: FAILURE" Suggest me on thisASAP. Fix Versions: current Project: Jenkins Labels: jenkins Priority: Critical Reporter: Deepal Neema This message is automatically generated by JIRA. 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-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
SCM/JIRA link daemon commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Code changed in jenkins User: Nicolas De Loof Path: core/src/main/java/hudson/tasks/CommandInterpreter.java http://jenkins-ci.org/commit/jenkins/8e74242d8b961a78d5d498b55e1f3797f92bb8a1 Log: JENKINS-12235 root cause is hidden by by script deletion failure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15957) All build executors permanently "Dead!"
Bruce Adams commented on JENKINS-15957 All build executors permanently "Dead!" I've given up and downgraded (reluctantly) to the latest long term support release (1.480.1) I suspect this problem was introduced around 1.488 This message is automatically generated by JIRA. 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-16094) Better Job filtering capabilities - make use of JobViewsFilterPlugin
Myron n/a created JENKINS-16094 Better Job filtering capabilities - make use of JobViewsFilterPlugin Issue Type: Improvement Affects Versions: current Assignee: Julien RENAUT Components: xfpanel Created: 11/Dec/12 11:05 AM Description: Have installed the https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters plugin which works fine for all the other views. Maybe you could try to integrate this too, to help in better filtering the jobs (status, type, regex, disabled, failed, ...) Another idea: is it possible to have Views with parameters? EG: i have 150 jobs... and in one panel usually only fit ~16 jobs nicely If i create a view for all jobs and want to display the second 16 jobs (without creating a hard view) like &size=16&page=2 (so this will be independent of my often changing views ) Project: Jenkins Priority: Minor Reporter: Myron n/a This message is automatically generated by JIRA. 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-2556) Use svn switch where applicable
kutzi commented on JENKINS-2556 Use svn switch where applicable Could someone (preferably the one submitting the patch) check if the patch can still be applied without conflicts and convert it to a Github pull request? Then I'll have a look at it - when time allows. This message is automatically generated by JIRA. 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-2556) Use svn switch where applicable
kutzi assigned JENKINS-2556 to kutzi Use svn switch where applicable Change By: kutzi (11/Dec/12 11:32 AM) 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-14100) Keep Android SDK updated automatically
Peter Kovacs commented on JENKINS-14100 Keep Android SDK updated automatically Right now, the plugin downloads sdk version 16, but the newest is 21. There is no way to update it (automatically or parameterized from jenkins build) and because of this android-17 can not be installed: 'SDK Platform Android 4.2, API 17, revision 1'; it depends on 'Android SDK Tools, revision 21' which was not installed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
dogfood commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Integrated in jenkins_main_trunk #2141 JENKINS-12235 root cause is hidden by by script deletion failure (Revision 8e74242d8b961a78d5d498b55e1f3797f92bb8a1) Result = SUCCESS Nicolas De Loof : 8e74242d8b961a78d5d498b55e1f3797f92bb8a1 Files : core/src/main/java/hudson/tasks/CommandInterpreter.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-15213) email-ext 2.22+ allows any user with configure permission for a single job to circumvent Jenkins security
Slide-O-Mix commented on JENKINS-15213 email-ext 2.22+ allows any user with configure permission for a single job to circumvent Jenkins security Groovy Postbuild's security is easily bypassed, I can add imports at the top of the post-build script and access the Jenkins/Hudson instance all I want, even with the security enabled. I need to research this more, something along the lines of a sandbox if something like that exists. This message is automatically generated by JIRA. 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-16083) HTML Publisher v1.1 regression
Kerstin Klein commented on JENKINS-16083 HTML Publisher v1.1 regression with version 1.2 of this plugin it works for me again. Thank you for the quick 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-16095) Heap memory leak (possibly jclouds plugin related)
onemanbucket created JENKINS-16095 Heap memory leak (possibly jclouds plugin related) Issue Type: Bug Assignee: abayer Attachments: screenshot-leak.png, screenshot-leak2.png, screenshot-leak3.png Components: core, jclouds Created: 11/Dec/12 2:03 PM Description: We're running into a memory leak that might be related to the jclouds plugin. Running with a heap of 5.5gb, old gen becomes full after a couple of days with moderate to heavy load. We have a setup with jenkins & jclouds provisioning test instances on a private nova-compute cloud. When I look at the heap dump it seems that there's a guava cache that occupies 70% of the heap. Any idea how to proceed debugging this? Project: Jenkins Priority: Major Reporter: onemanbucket This message is automatically generated by JIRA. 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
John Ament created JENKINS-16096 Support for inclusions, exclusions Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco Created: 11/Dec/12 2:07 PM Description: Add support for inclusions, exclusions with JaCoCo In my build setup, I'm using Arquillian + JaCoCo for code coverage. When looking at the results in Jenkins it shows many more packages than I actually cover. I think it would be good to have an inclusion/exclusion section for what to show. Environment: Windows 7 client machine. Project: Jenkins Priority: Major Reporter: John Ament This message is automatically generated by JIRA. 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-16095) Heap memory leak (possibly jclouds plugin related)
onemanbucket updated JENKINS-16095 Heap memory leak (possibly jclouds plugin related) Change By: onemanbucket (11/Dec/12 2:17 PM) Description: We're running into a memory leak that might be related to the jclouds plugin. Running with a heap of 5.5gb, old gen becomes full after a couple of days with moderate to heavy load.We have a setup with jenkins & jclouds provisioning test instances on a private nova-compute cloud. When I look at the heap dump it seems that there's a guava cache that occupies 70% of the heap. Any idea how to proceed debugging this? This is jeknins 1.492, jclouds plugin 2.3.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15213) email-ext 2.22+ allows any user with configure permission for a single job to circumvent Jenkins security
Slide-O-Mix started work on JENKINS-15213 email-ext 2.22+ allows any user with configure permission for a single job to circumvent Jenkins security Change By: Slide-O-Mix (11/Dec/12 2:21 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15213) email-ext 2.22+ allows any user with configure permission for a single job to circumvent Jenkins security
Slide-O-Mix commented on JENKINS-15213 email-ext 2.22+ allows any user with configure permission for a single job to circumvent Jenkins security I've decided to use the groovy sandbox to disallow interaction with the Jenkins instance when security is enabled for the pre-send 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-11149) JNLP slave fails to connect if Anonymous has not permission READ
Matthias Vach commented on JENKINS-11149 JNLP slave fails to connect if Anonymous has not permission READ Correct, we enforce the login by not offering read permissions to anonymous. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
Cyrille Boulanger commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Bitten by this issue also This message is automatically generated by JIRA. 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-12972) Add option to run 'git bisect' to find which commit added new bugs
txemi M commented on JENKINS-12972 Add option to run 'git bisect' to find which commit added new bugs I would love this feature. Now I am running bisect manually. It would be great that jenkins could tell which commit broke compilation or unit 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-12972) Add option to run 'git bisect' to find which commit added new bugs
txemi M edited a comment on JENKINS-12972 Add option to run 'git bisect' to find which commit added new bugs I would love this feature. Now I am running bisect manually. It would be great that jenkins could tell which single commit broke compilation or unit 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-16095) Heap memory leak (possibly jclouds plugin related)
abayer commented on JENKINS-16095 Heap memory leak (possibly jclouds plugin related) Lemme see what other jclouds people think. This message is automatically generated by JIRA. 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-15213) email-ext 2.22+ allows any user with configure permission for a single job to circumvent Jenkins security
Slide-O-Mix resolved JENKINS-15213 as Fixed email-ext 2.22+ allows any user with configure permission for a single job to circumvent Jenkins security Added a sandbox around the pre-send script execution that when security is enabled the user will not be able to access the Jenkins/Hudson instance. This is different than the implementation used in the groovy postbuild plugin which can easily be subverted. Change By: Slide-O-Mix (11/Dec/12 4:18 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Cameron Horn commented on JENKINS-15156 Builds Disappear from Build History after Completion Notice this in particular with newly created jobs, where all build history will vanish after a build or two. This message is automatically generated by JIRA. 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
Jaime Gago
commented on JENKINS-14193
EnvInject doesn't pass variables defined in prebuild step if maven project is used
Any progress on this? I can reproduce on 1.493. Unfortunately none of the alternatives work in my case as I need the variable value to be created dynamically after an SCM checkout but before the build as I'm using the value to specify profiles to the maven build (mvn clean install -P$PROFILES). FWIW the value of $PROFILES is computed via this command mvn help:all-profiles|grep "Profile Id"|awk '{print $3}'|sort|uniq|tr "n" ","
This message is automatically generated by JIRA.
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-16097) Copy To Slave plugin fails when copying from Windows slave to Linux master
Jeff Rodgers created JENKINS-16097 Copy To Slave plugin fails when copying from Windows slave to Linux master Issue Type: Bug Assignee: Daniel Petisme Components: copy-to-slave Created: 11/Dec/12 5:02 PM Description: The workspace does not seem to render properly for the master when using the copy-to-master option. It appears in Windows path format on the Linux side. An exception occured while creating VERDE_build: java.io.IOException: Failed to mkdirs: workspace\VERDE_build [copy-to-slave] Copying 'win4/trunk/src/win32/FinishWin7Install/*.exe', excluding nothing, from 'file:/c:/Users/Vbridges/Development/workspace/VERDE_build/' on 'hudson.plugins.virtualbox.VirtualBoxSlave@eba543f' to 'file:/workspace%5CVERDE_build' on the master. ERROR: Publisher com.michelin.cio.hudson.plugins.copytoslave.CopyToMasterNotifier aborted due to exception hudson.util.IOException2: Failed to extract c:\Users\Vbridges\Development\workspace\VERDE_build/win4/trunk/src/win32/FinishWin7Install/*.exe at hudson.FilePath.readFromTar(FilePath.java:1936) at hudson.FilePath.copyRecursiveTo(FilePath.java:1848) at com.michelin.cio.hudson.plugins.copytoslave.CopyToMasterNotifier.perform(CopyToMasterNotifier.java:93) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1562) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.io.FileNotFoundException: workspace\VERDE_build/win4/trunk/src/win32/FinishWin7Install/FinishWin7Install.exe (No such file or directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:209) at java.io.FileOutputStream.(FileOutputStream.java:160) at hudson.util.IOUtils.copy(IOUtils.java:35) at hudson.FilePath.readFromTar(FilePath.java:1926) ... 10 more The workaround is to hard-code the Linux workspace path using the Override Destination Folder option. Environment: Jenkins on Centos 6.3 with Windows 7 and Ubuntu 10.04 slaves hosted on the same machine through VirtualBox. Project: Jenkins Priority: Critical Reporter: Jeff Rodgers This message is automatically generated by JIRA. 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-16090) Cannot access published results page via links in prior builds
mcrooney commented on JENKINS-16090 Cannot access published results page via links in prior builds HTML Publisher 1.2 is out which may address the 1.1 issue and this one, could you give that a try and report back? This message is automatically generated by JIRA. 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-16095) Heap memory leak (possibly jclouds plugin related)
onemanbucket updated JENKINS-16095 Heap memory leak (possibly jclouds plugin related) Change By: onemanbucket (11/Dec/12 5:13 PM) Attachment: screenshot-leak-4.png Attachment: screenshot-leak-5.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16095) Heap memory leak (possibly jclouds plugin related)
onemanbucket commented on JENKINS-16095 Heap memory leak (possibly jclouds plugin related) Ok cool. There's a lot of reflect.Method objects (1.2gb shallow heap) that are cached by jclouds if that could help investigate this further. Attaching 2 more screenshots. This message is automatically generated by JIRA. 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-16098) Nested View Plugin shows FAIL build staus whenever Build Pipeline Plugin is used as a Nested View
Fernando Rubbo created JENKINS-16098 Nested View Plugin shows FAIL build staus whenever Build Pipeline Plugin is used as a Nested View Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: nested-viewANDbuild-pipeline.png Components: build-pipeline, nested-view Created: 11/Dec/12 5:35 PM Description: Always shows fail whenever we use a build pipeline as a nested view. Even if there is no issues in the build pipeline. Moreover, it is impossible to add a nested view if the first one is a build pipeline. Project: Jenkins Priority: Major Reporter: Fernando Rubbo This message is automatically generated by JIRA. 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-16099) Not able to enter correct SVN credentials
domi
created JENKINS-16099
Not able to enter correct SVN credentials
Issue Type:
Bug
Assignee:
Unassigned
Components:
subversion
Created:
11/Dec/12 6:27 PM
Description:
Since version 1.18 we are not able to upgrade the Subversion plugin anymore, the reason why we always failed to introduce the new version is because the plugin did not let us configure the correct credentials anymore.
The credentials used where always the once hard coded in the svnkit fork of Jenkins (https://github.com/jenkinsci/svnkit/blob/master/svnkit/src/main/java/org/tmatesoft/svn/core/internal/io/dav/http/HTTPConnection.java):
... new SVNPasswordAuthentication("qaOWQ8w3-byHudson","OGQCrcJ9-byHudson",false);
The usage of this is enforced by a call to authManager.setAuthenticationForced(true) in hudson.scm.SubversionSCM.postCredential(...).
This code is only called to test for valid credentials from within the UI.
If setAuthenticationForced is set to false, everything works fine.
Environment:
Master: Solaris
Subversion: 1.6
Project:
Jenkins
Priority:
Blocker
Reporter:
domi
This message is automatically generated by JIRA.
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-15965) Currently building links point to wrong downstream projects when concurent builds are active
Asmund olsen
commented on JENKINS-15965
Currently building links point to wrong downstream projects when concurent builds are active
I do not know any Jenkins(user only) but I have an feeling some of the issue is located in MultiJobBuilder.java. I believe the build number gathered with project.getLastBuild() could be incorrect if sub build is allowed to execute parallel. Is it possible to query project(sub build) about upstream build number to make sure the correct sub build number is used?
[...]
public boolean perform(AbstractBuild build, Launcher launcher,
BuildListener listener) throws InterruptedException, IOException {
[...]
addSubBuild(thisBuild, thisProject,
(AbstractBuild) project.getLastBuild());
projectList.remove(project);
futuresList.remove(future);
break;
} catch (ExecutionException e) {
failed = true;
}
} else if (project.isBuilding()) {
addSubBuild(thisBuild, thisProject,
(AbstractBuild) project.getLastBuild());
}
[...]
I may very well wrong!
This message is automatically generated by JIRA.
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-15965) Currently building links point to wrong downstream projects when concurent builds are active
Devin Linnington commented on JENKINS-15965 Currently building links point to wrong downstream projects when concurent builds are active You are probably correct. The console output contains the correct links to the right build number, so the stuff generating the console output must be using a different method than project.getLastBuild(). Otherwise I would imagine the console would be having the same 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-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Keith Collison updated JENKINS-15948 Analyzer Icons aren't displayed if Jenkins isn't installed at root context. Change By: Keith Collison (11/Dec/12 7:16 PM) Attachment: jenkins-failbadge.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Keith Collison reopened JENKINS-15948 Analyzer Icons aren't displayed if Jenkins isn't installed at root context. Upon updating the plugin to the most recent version, the image URLs appear to have the web context twice. I have jenkins installed on a context named "jenkins". Below is what I'm seeing as the path to the icon: [base url]/jenkins/jenkins/plugin/build-failure-analyzer/images/16x16/information.png Change By: Keith Collison (11/Dec/12 7:15 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang
Martin Scherer commented on JENKINS-7114 aborting download of workspace files makes slave agent hang I can confirm this behaviour. My Log has grown to 12Gb due to the continuous thrown (and not properly handled) exception. Thanks in advance for fixing this soon! This message is automatically generated by JIRA. 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-7114) aborting download of workspace files makes slave agent hang
Martin Scherer updated JENKINS-7114 aborting download of workspace files makes slave agent hang Change By: Martin Scherer (11/Dec/12 7:47 PM) Attachment: stack.txt This message is automatically generated by JIRA. 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-15976) Provided maven settings.xml in maven builder is lost
SCM/JIRA link daemon commented on JENKINS-15976 Provided maven settings.xml in maven builder is lost Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/resources/org/jenkinsci/plugins/configfiles/maven/job/MvnGlobalSettingsProvider/config.jelly src/main/resources/org/jenkinsci/plugins/configfiles/maven/job/MvnSettingsProvider/config.jelly src/test/java/org/jenkinsci/plugins/configfiles/maven/job/MvnSettingsProviderTest.java http://jenkins-ci.org/commit/config-file-provider-plugin/40c66e9aeb51afd33999145437feb4c1c755bacb Log: [FIXED JENKINS-15976] "it" refers to the object that owns the page, such as FreeStyleProject. So a small object like SettingsProvider that contributes to those big guys should refer to itself as 'instance', not via 'it'. Also added a regression test case. Compare: https://github.com/jenkinsci/config-file-provider-plugin/compare/05f431815f32...40c66e9aeb51 This message is automatically generated by JIRA. 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-15976) Provided maven settings.xml in maven builder is lost
SCM/JIRA link daemon resolved JENKINS-15976 as Fixed Provided maven settings.xml in maven builder is lost Change By: SCM/JIRA link daemon (11/Dec/12 7:55 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-15965) Currently building links point to wrong downstream projects when concurent builds are active
Asmund olsen commented on JENKINS-15965 Currently building links point to wrong downstream projects when concurent builds are active Having done some searching on the issue of downstream upstream build numbers it looks like it could be difficult only using numbers. One(execution) build can be triggered by multiple upstream builds. My suggestion is to hack in a build parameter ID that is generated unique for sub build. And then somehow match against this build parameter. But as I have already stated I do not know MultiJob and Jenkins internals at all. This message is automatically generated by JIRA. 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-15533) Jobs disappearing with Jenkins 1.485 and 1.486
taksan commented on JENKINS-15533 Jobs disappearing with Jenkins 1.485 and 1.486 I am experiencing something similar, jenkins fails to load several jobs, but my stackstrace is differente: SEVERE: Failed Loading job AProject com.thoughtworks.xstream.mapper.CannotResolveClassException: fingerprint : fingerprint 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) I noticed that some of the modules have a builds.xml file with tags I don't know whether this is pthe 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-16097) Copy To Slave plugin fails when copying from Windows slave to Linux master
Jeff Rodgers commented on JENKINS-16097 Copy To Slave plugin fails when copying from Windows slave to Linux master A similar problem also occurs using "Copy files into the job's workspace before building" option in the downstream job. This is rather interesting since the master and the downstream jobs are both Linux. An exception occured while creating VERDE_build: java.io.IOException: Failed to mkdirs: workspace\VERDE_build [copy-to-slave] Copying '**/FinishWin7Install.exe', excluding nothing, from 'file:/workspace%5CVERDE_build' on the master to 'file:/var/jenkins/workspace/VERDE_build/' on 'vbuilder'. This message is automatically generated by JIRA. 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-15320) Add 'Ignore missing file' option.
Gregory Boissinot resolved JENKINS-15320 as Not A Defect Add 'Ignore missing file' option. Taking in consideration missing files is not the responsibility of the Cppcheck plugin. Run-Condition plugin is one way to solve your issue. Change By: Gregory Boissinot (11/Dec/12 8:35 PM) Status: In Progress Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16100) Use of variable names with . fail to resolve.
Mike Eggleton
created JENKINS-16100
Use of variable names with . fail to resolve.
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
envinject
Created:
11/Dec/12 8:55 PM
Description:
If a property file is passed in that contains a variable name that contains a . and then is referenced it does not resolve.
For example
Use the property file field to bring in a file that contains the following:
my.variable.name=1
Then in the next section have the following:
$SOME_VARIABLE=$my.variable.name
$SOME_VARIABLE will then resolve to $my.variable.name instead of resolving to 1.
Also tried was: $SOME_VARIABLE=${my.variable.name}
Environment:
Windows
Project:
Jenkins
Priority:
Major
Reporter:
Mike Eggleton
This message is automatically generated by JIRA.
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-9142) "Add Build Step" button broken in job configure page
Yves Schumann commented on JENKINS-9142 "Add Build Step" button broken in job configure page We run into this issue with Jenkins 1.493 so we are unable to add build steps at the moment! Tested with Chrome 23, FF 16.01 and IE 8. Any ideas? This message is automatically generated by JIRA. 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-16097) Copy To Slave plugin fails when copying from Windows slave to Linux master
Jeff Rodgers updated JENKINS-16097 Copy To Slave plugin fails when copying from Windows slave to Linux master Change By: Jeff Rodgers (11/Dec/12 11:03 PM) Environment: Jenkins (1.492) on Centos 6.3 with Windows 7 and Ubuntu 10.04 slaves hosted on the same machine through VirtualBox. This message is automatically generated by JIRA. 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-16101) Add support for TFS SCM plug-in
John Mills created JENKINS-16101 Add support for TFS SCM plug-in Issue Type: Improvement Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 11/Dec/12 11:06 PM Description: Please add support for using the TFS SCM plug-in with SCM Sync Configuration plugin. We have a large need to check in Jenkins configuration changes (jobs, core, and plug-in changes). We are currently using TFS 2010. Thanks! Project: Jenkins Priority: Major Reporter: John Mills This message is automatically generated by JIRA. 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
eguess74 commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Hi everyone. I need this bug/feature so much that I'm willing to pay 100.00 bucks for it. This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/95/parsing-ivy-descriptors-step-fails-on-a-slave-when-custom-ivy-settings-file-is-used). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay up! If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors! This message is automatically generated by JIRA. 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-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type
eguess74 commented on JENKINS-15774 Add ability to specify custom ivy settings file in global configuration for ivy job type Hi everyone. I need this bug/feature so much that I'm willing to pay 50.00 bucks for it. This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/96/add-ability-to-specify-custom-ivy-settings-file-in-global-configuration-for-ivy-job-type). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay up! If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors! This message is automatically generated by JIRA. 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-16101) Add support for TFS SCM plug-in
Frédéric Camblor commented on JENKINS-16101 Add support for TFS SCM plug-in I won't work on it since I don't have the need (and knowledge) to. But I would be happy to have a contribution for this need (Git and Mercurial support has been contributed by others than me ) This message is automatically generated by JIRA. 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-16101) Add support for TFS SCM plug-in
Frédéric Camblor updated JENKINS-16101 Add support for TFS SCM plug-in Change By: Frédéric Camblor (12/Dec/12 12:53 AM) Priority: Major Minor This message is automatically generated by JIRA. 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-13770) StarTeam Plugin SCM Polling failing on Slave machines
Hugo Ares commented on JENKINS-13770 StarTeam Plugin SCM Polling failing on Slave machines fixed in commit https://github.com/hugares/starteam-plugin/commit/284cd2d3513b6cee735896ad12d48bc4287c977c This message is automatically generated by JIRA. 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-13054) Starteam plugin error when executing checkout by label.
Hugo Ares commented on JENKINS-13054 Starteam plugin error when executing checkout by label. fixed in commit https://github.com/hugares/starteam-plugin/commit/0c82938f723d0597d4536f32de2dfd705b4deb8b This message is automatically generated by JIRA. 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-13848) Option to add full build console log as an attachment
SCM/JIRA link daemon commented on JENKINS-13848 Option to add full build console log as an attachment Code changed in jenkins User: slide Path: src/main/java/hudson/plugins/emailext/AttachmentUtils.java src/main/java/hudson/plugins/emailext/EmailType.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.jelly src/main/resources/hudson/plugins/emailext/tags/mailtype.jelly src/main/resources/hudson/plugins/emailext/tags/mailtype.properties src/main/webapp/help/projectConfig/attachBuildLog.html http://jenkins-ci.org/commit/email-ext-plugin/4c8c49515e780d5abe2a39208d407ba49110d73e Log: Fix JENKINS-13848 and JENKINS-13672 This message is automatically generated by JIRA. 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-13672) Allow email attachments at TRIGGER LEVEL
SCM/JIRA link daemon commented on JENKINS-13672 Allow email attachments at TRIGGER LEVEL Code changed in jenkins User: slide Path: src/main/java/hudson/plugins/emailext/AttachmentUtils.java src/main/java/hudson/plugins/emailext/EmailType.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.jelly src/main/resources/hudson/plugins/emailext/tags/mailtype.jelly src/main/resources/hudson/plugins/emailext/tags/mailtype.properties src/main/webapp/help/projectConfig/attachBuildLog.html http://jenkins-ci.org/commit/email-ext-plugin/4c8c49515e780d5abe2a39208d407ba49110d73e Log: Fix JENKINS-13848 and JENKINS-13672 This message is automatically generated by JIRA. 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-5949) Trim JUnit stack traces & logs to reasonable length before mailing
SCM/JIRA link daemon commented on JENKINS-5949 Trim JUnit stack traces & logs to reasonable length before mailing Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/content/FailedTestsContent.java src/test/java/hudson/plugins/emailext/plugins/content/FailedTestsContentTest.java http://jenkins-ci.org/commit/email-ext-plugin/4a441eba86eebb5c96ca4dacfb2b3e53e8f12ec2 Log: Merge branch 'JENKINS-5949' This message is automatically generated by JIRA. 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-15213) email-ext 2.22+ allows any user with configure permission for a single job to circumvent Jenkins security
SCM/JIRA link daemon commented on JENKINS-15213 email-ext 2.22+ allows any user with configure permission for a single job to circumvent Jenkins security Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.jelly src/main/webapp/help/globalConfig/security.html http://jenkins-ci.org/commit/email-ext-plugin/062f768561cb0e9b64331b8a43a2820d52971751 Log: Fix JENKINS-15213 Allow administrator to enable security for pre-send scripts. This is a breaking change for current pre-send scripts. This message is automatically generated by JIRA. 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-16102) Cannot change my JIRA - Jenkins account password.
John Mills created JENKINS-16102 Cannot change my JIRA - Jenkins account password. Issue Type: Bug Assignee: Unassigned Components: jira Created: 12/Dec/12 3:37 AM Description: I just opened an account on JIRA - Jenkins and there is no way that I can find to change my password Project: Jenkins Priority: Major Reporter: John Mills This message is automatically generated by JIRA. 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-8226) Add reviewers in gerrit when a build is successful
Andreas Borglin commented on JENKINS-8226 Add reviewers in gerrit when a build is successful We merged in the changes and gave it a go. It works well, but one issue. We have set up the Deny rule for Email Reviewers for Jenkins in order to reduce the Gerrit spamming a bit. When this is turned on and Jenkins adds the reviewers, they are not notified (makes sense). Is there any way though to let those emails come through but stop the Build notifications being sent to all the reviewers? Any way to configure that via the plugin? 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-15860) Mail body for two simultaneous mails get mixed
Slide-O-Mix commented on JENKINS-15860 Mail body for two simultaneous mails get mixed If you are willing to, I can attach a snapshot of the RC of the next release. I did make a couple modifications that theoretically could "fix" this, though I am not willing to say for certain. This message is automatically generated by JIRA. 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-16103) If Anonymous has overall read access, anyone can connect as a slave over JNLP
Andrew Collette created JENKINS-16103 If Anonymous has overall read access, anyone can connect as a slave over JNLP Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Dec/12 4:59 AM Description: Using Matrix-based security with one admin (full rights) user and Anonymous Jenkins' own user database Build slaves configured to launch over JNLP Jenkins version 1.493 If the user Anonymous has "overall read" permissions, then anyone can access the JNLP file from /computer//slave-agent.jnlp, and connect to the server as a slave via e.g. java -jar slave.jar -jnlpURL http:///computer//slave-agent.jnlp. The URL is trivial to guess, especially since build slave names are displayed on the front page when anonymous read is enabled. Environment: Linux 32-bit (Fedora-derived Amazon EC2 image), with Jenkins installed via yum. Project: Jenkins Priority: Major Reporter: Andrew Collette This message is automatically generated by JIRA. 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-15972) No display available in post build actions
Yves Langisch
reopened JENKINS-15972
No display available in post build actions
Saving an existing job with Xvfb enabled leads to this exception:
Status Code: 500
Exception: java.lang.IllegalArgumentException: Failed to instantiate class org.jenkinsci.plugins.xvfb.XvfbBuildWrapper from {"additionalOptions":"","debug":false,"displayName":"","displayNameOffset":"","installationName":"Xvfb","screen":"","shutdownWithBuild":false,"timeout":""}
Stacktrace:
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class org.jenkinsci.plugins.xvfb.XvfbBuildWrapper from {"additionalOptions":"","debug":false,"displayName":"","displayNameOffset":"","installationName":"Xvfb","screen":"","shutdownWithBuild":false,"timeout":""}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilte
[JIRA] (JENKINS-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Tomas Westling commented on JENKINS-15948 Analyzer Icons aren't displayed if Jenkins isn't installed at root context. We got a bugfix for this in the latest version of the source code, it's not released yet though. You could build the latest from source and try it out or wait for the next release, I will close this once we've done the 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-15079) Should be able to copy an AMI, or a whole cloud, for quick setup
Craig Ringer commented on JENKINS-15079 Should be able to copy an AMI, or a whole cloud, for quick setup The Jenkins CloudFormation plugin might be useful for this This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15389) Fingerprinting private key for discovery is flawed
Craig Ringer commented on JENKINS-15389 Fingerprinting private key for discovery is flawed This appears to be fixed in more recent releases. This message is automatically generated by JIRA. 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-9292) Provide an option for deleting extra volumes produced by terminated ec2 instances
Craig Ringer commented on JENKINS-9292 Provide an option for deleting extra volumes produced by terminated ec2 instances Also note that this only occurrs if your AMIs are created from an instance that has delete on terminate turned off. If you turn delete on terminate on before creating AMIs this won't be a problem. That's a bit of a pain when you don't control the AMIs, though. I'm currently working around this by having Jenkins stop the instances rather than terminate them. This is also saving lots of setup time. This message is automatically generated by JIRA. 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-16104) Build Failure Analyzer
Oliver Bolte created JENKINS-16104 Build Failure Analyzer Issue Type: Bug Affects Versions: current Assignee: Tomas Westling Components: build-failure-analyzer, timestamper Created: 12/Dec/12 7:33 AM Description: With release 1.3.0: 02:14:18 Notifying upstream projects of job completion 02:14:18 Finished: FAILURE [8mha:dB+LCABb85aBtbiIQSOjNKU4P0+vIKc0PTOvWK8kMze1uCQxtyC1SC8ExvbLL0llgABGJgZGLwaB3MycnMzi4My85FTXgvzkjIoiBimoScn5ecX5Oal6zhAaVS9DRQGQtm7flp8HAPhU/CWB[0mStarted by timer [8mha:dB+LCABb85aBtbiIQSOjNKU4P0+vIKc0PTOvWK8kMze1uCQxtyC1SC8ExvbLL0llgABGJgZGLwaB3MycnMzi4My85FTXgvzkjIoiBimoScn5ecX5Oal6zhAaVS9DRQGQtm7fNu0QAM/h4j+B[0mBuilding on master [8mha:dB+LCABb85aBtbiIQSOjNKU4P0+vIKc0PTOvWK8kMze1uCQxtyC1SC8ExvbLL0llgABGJgZGLwaB3MycnMzi4My85FTXgvzkjIoiBimoScn5ecX5Oal6zhAaVS9DRQGQtm7fNu0QAM/h4j+B[0mNo emails were triggered. Project: Jenkins Priority: Major Reporter: Oliver Bolte This message is automatically generated by JIRA. 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-16104) Build Failure Analyzer: Ugly output from plugin
Oliver Bolte updated JENKINS-16104 Build Failure Analyzer: Ugly output from plugin Change By: Oliver Bolte (12/Dec/12 7:36 AM) Summary: Build Failure Analyzer : Ugly output from plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
