[JIRA] [android-lint] (JENKINS-17584) Copy source file fails with maven build
Philip Schiffer created JENKINS-17584 Copy source file fails with maven build Issue Type: Bug Affects Versions: current Assignee: Christopher Orr Components: android-lint Created: 12/Apr/13 6:55 AM Description: I have just updated to version 2.1 and enabled this plugin for my maven based build job and I get the many stacktraces, which look like this: [android-lint] Can't copy source file: source=res/layout/layout.xml, destination=b263fde3.tmp hudson.util.IOException2: Failed to copy res/layout/layout.xml to /var/lib/jenkins/jobs/ProjectJob/modules/$/builds/2013-04-12_08-38-52/workspace-files/b263fde3.tmp at hudson.FilePath.copyTo(FilePath.java:1725) at hudson.plugins.analysis.core.HealthAwareReporter.copyFilesWithAnnotationsToBuildFolder(HealthAwareReporter.java:463) at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:340) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:453) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:435) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) 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.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) 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: java.io.FileNotFoundException: res/layout/layout.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:120) at hudson.FilePath$33.invoke(FilePath.java:1751) at hudson.FilePath$33.invoke(FilePath.java:1746) at hudson.FilePath.act(FilePath.java:904) at hudson.FilePath.act(FilePath.java:877) at hudson.FilePath.copyTo(FilePath.java:1746) at hudson.FilePath.copyTo(FilePath.java:1720) ... 34 more My Project folder structure is like this: / = parent-Module /module = android-module with lint-results
[JIRA] [extended-choice-parameter] (JENKINS-17518) When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter
vimil resolved JENKINS-17518 as Fixed When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter Change By: vimil (12/Apr/13 4:26 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [postbuildscript] (JENKINS-11219) Add the option to run the script after all the sub elements of a matrix project build have finished
bradx3 commented on JENKINS-11219 Add the option to run the script after all the sub elements of a matrix project build have finished It looks like this option is just tied up in the normal "Execute script only if build succeeds" option - see https://github.com/jenkinsci/postbuildscript-plugin/pull/2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [postbuild-task] (JENKINS-12303) Post build task - 'Add another task' does not work
Ken Morse commented on JENKINS-12303 Post build task - 'Add another task' does not work I see the same behavior described in this case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17460) Error occurs viewing build history on some builds
Bruce Coveny commented on JENKINS-17460 Error occurs viewing build history on some builds This doesn't have anything to do with the name, it just has to deal with the fact that the project triggers another project. I have tried new projects with names "test 2" and "test3" without any spaces and they fail 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extended-choice-parameter] (JENKINS-17518) When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter
Michael Chmielewski commented on JENKINS-17518 When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter Probably want to close this This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [klocwork] (JENKINS-17583) WARNING: could not load directory, hudson.util.IOException2: Invalid directory name
Adam Westhusing created JENKINS-17583 WARNING: could not load directory, hudson.util.IOException2: Invalid directory name Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: klocwork Created: 11/Apr/13 7:50 PM Description: I'm receiving the following exceptions with Jenkins 1.510 and Klocwork Plugin 1.14.1. I believe this is related to a change Jenkins made on Windows related to how directories are referenced in builds. This problem does not exist when using Jenkins 1.506, but I believe it was introduced in either 1.507, 1.508 or 1.509. This is a critical issue for me because this issue happens very often, and I believe the exceptions are causing memory leaks. This ultimately causes Jenkins to run out of memory. Apr 11, 2013 3:30:43 PM hudson.model.RunMap retrieve WARNING: could not load D:\Jenkins\jobs\KlocworkProject\builds\209 hudson.util.IOException2: Invalid directory name D:\Jenkins\jobs\KlocworkProject\builds\209 at hudson.model.Run.parseTimestampFromBuildDir(Run.java:354) at hudson.model.Run.(Run.java:294) at hudson.model.AbstractBuild.(AbstractBuild.java:182) at hudson.model.Build.(Build.java:103) at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1117) at hudson.model.AbstractProject$1.create(AbstractProject.java:317) at hudson.model.AbstractProject$1.create(AbstractProject.java:315) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:368) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:1039) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:140) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:94) at hudson.model.Job.getLastSuccessfulBuild(Job.java:802) at com.thalesgroup.hudson.plugins.klocwork.util.KloProjectReviewLink.setKloHostPort(KloProjectReviewLink.java:55) at com.thalesgroup.hudson.plugins.klocwork.util.KloProjectReviewLink.(KloProjectReviewLink.java:47) at com.thalesgroup.hudson.plugins.klocwork.KloPublisher.getProjectActions(KloPublisher.java:76) at hudson.model.Project.createTransientActions(Project.java:211) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:712) at hudson.model.AbstractProject.onLoad(AbstractProject.java:311) at hudson.model.Project.onLoad(Project.java:83) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2554) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:888) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) 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: java.text.ParseException: Unparseable date: "209" at java.text.DateFormat.parse(Unknown Source) at hudson.model.Run.parseTimestampFromBuildDir(Run.java:352) ... 38 more Environment: Windows Server 2008 R2, Jenkins 1.510, Klocwork Plugin 1.14.1 Fix Versions:
[JIRA] [job-dsl-plugin] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Chris Dore
edited a comment on JENKINS-17222
Add ability to specify more than one location when using the svn method
You're right, sorry.
Using a left-shift should work:
it / locations << 'hudson.scm.SubversionSCM_-ModuleLocation' {
...
}
I tested your example with left-shifts and it worked.
See https://github.com/jenkinsci/job-dsl-plugin/wiki/configure-block (section Add-ons), for a short description of the divide and left-shift operators.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Chris Dore
edited a comment on JENKINS-17222
Add ability to specify more than one location when using the svn method
You're right, sorry.
Using a left-shift should work:
it / locations << 'hudson.scm.SubversionSCM_-ModuleLocation' {
...
}
I tested your example with left-shifts and it worked.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [greenballs] (JENKINS-17582) WARNING: could not load directory, hudson.util.IOException2: Invalid directory name
Adam Westhusing updated JENKINS-17582 WARNING: could not load directory, hudson.util.IOException2: Invalid directory name Change By: Adam Westhusing (11/Apr/13 7:44 PM) Description: I'm receiving the following exceptions with Jenkins 1.510 and GreenBalls 1.12. I believe this is related to a change Jenkins made on Windows related to how directories are referenced in builds.This problem does not exist when using Jenkins 1.506, but I believe it was introduced in either 1.507, 1.508 or 1.509. This is a critical issue for me because this issue happens very often, and I believe the exceptions are causing memory leaks. This ultimately causes Jenkins to run out of memory. Apr 4, 2013 4:11:35 PM hudson.model.RunMap retrieveWARNING: could not load D:\Jenkins\jobs\ProjectName\builds\1122hudson.util.IOException2: Invalid directory name D:\Jenkins\jobs\ProjectName\builds\1122 at hudson.model.Run.parseTimestampFromBuildDir(Run.java:354) at hudson.model.Run.(Run.java:294) at hudson.model.AbstractBuild.(AbstractBuild.java:182) at hudson.model.Build.(Build.java:103) at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41) at sun.reflect.GeneratedConstructorAccessor39.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1117) at hudson.model.AbstractProject$1.create(AbstractProject.java:317) at hudson.model.AbstractProject$1.create(AbstractProject.java:315) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:368) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:379) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:216) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:103) at hudson.model.Job.getBuildStabilityHealthReport(Job.java:1020) at hudson.model.Job.getBuildHealthReports(Job.java:980) at hudson.model.Job.getBuildHealth(Job.java:945) at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTag
[JIRA] [greenballs] (JENKINS-17582) WARNING: could not load directory, hudson.util.IOException2: Invalid directory name
Adam Westhusing created JENKINS-17582 WARNING: could not load directory, hudson.util.IOException2: Invalid directory name Issue Type: Bug Affects Versions: current Assignee: asgeirn Components: greenballs Created: 11/Apr/13 7:42 PM Description: I'm receiving the following exceptions with Jenkins 1.510 and GreenBalls 1.12. I believe this is related to a change Jenkins made on Windows related to how directories are referenced in builds. This problem does not exist when using Jenkins 1.506, but I believe it was introduced in either 1.507, 1.508 or 1.509. Apr 4, 2013 4:11:35 PM hudson.model.RunMap retrieve WARNING: could not load D:\Jenkins\jobs\ProjectName\builds\1122 hudson.util.IOException2: Invalid directory name D:\Jenkins\jobs\ProjectName\builds\1122 at hudson.model.Run.parseTimestampFromBuildDir(Run.java:354) at hudson.model.Run.(Run.java:294) at hudson.model.AbstractBuild.(AbstractBuild.java:182) at hudson.model.Build.(Build.java:103) at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41) at sun.reflect.GeneratedConstructorAccessor39.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1117) at hudson.model.AbstractProject$1.create(AbstractProject.java:317) at hudson.model.AbstractProject$1.create(AbstractProject.java:315) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:368) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:379) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:216) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:103) at hudson.model.Job.getBuildStabilityHealthReport(Job.java:1020) at hudson.model.Job.getBuildHealthReports(Job.java:980) at hudson.model.Job.getBuildHealth(Job.java:945) at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.
[JIRA] [job-dsl-plugin] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Chris Dore commented on JENKINS-17222 Add ability to specify more than one location when using the svn method Sorry, this should work: it / locations << 'hudson.scm.SubversionSCM_-ModuleLocation' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Chris Dore
edited a comment on JENKINS-17222
Add ability to specify more than one location when using the svn method
Sorry, this should work:
it / locations << 'hudson.scm.SubversionSCM_-ModuleLocation' {
...
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17581) Using the API Token beyond 496 causes intermittent 500 errors
herque created JENKINS-17581 Using the API Token beyond 496 causes intermittent 500 errors Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: active-directory Created: 11/Apr/13 7:31 PM Description: After upgrading to 509 from 496, my service accounts that use the api token stopped working all the time, giving 500 errors about 1/2 the time. I tracked it down to the AD plugin complaining that the user couldn't bind correctly (which is correct as it was passing the api token). Switching from the AD plugin to straight LDAP fixed the issue. My best guess would be that the filters that handle the plugin and the apitoken are getting fired at different times. I stopped looking at it though once moving to LDAP solved the issue. thanks! Environment: RHEL 6, tomcat 6, jenkins Project: Jenkins Priority: Minor Reporter: herque This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-9145) Last Duration shows only last successful build results.
Ben Golding commented on JENKINS-9145 Last Duration shows only last successful build results. Same issue if the last build was 'aborted' (e.g. by timeout): the duration displayed should be exactly the same as the timeout setting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17580) Add token for project Display Name
Ken Morse
created JENKINS-17580
Add token for project Display Name
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Alex Earl
Components:
email-ext
Created:
11/Apr/13 7:16 PM
Description:
The project "Display Name" is often a more human readable form of the Project Name. It would be really nice if there was a token something like ${DISPLAY_NAME} that could be used in place of ${PROJECT_NAME}.
Project:
Jenkins
Priority:
Minor
Reporter:
Ken Morse
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [release] (JENKINS-17579) Limit number of entries in "Previous release versions" section
kolos created JENKINS-17579 Limit number of entries in "Previous release versions" section Issue Type: Improvement Assignee: Peter Hayes Components: release Created: 11/Apr/13 7:02 PM Description: I was wondering if it's possible to limit the number of entries in the "Previous release versions" section when opening up a form in a release job. In our case we don't discard old builds and we're up to #2000 which means if we upgrade to the latest version of the plugin (we're stuck at version 1.10), the page takes ages to load as it adds a table for all 2000 historical releases. The build history on the left limits the list by default so something similar behaviour would be very nice. Environment: Latest Jenkins with a long history in release job. Project: Jenkins Priority: Major Reporter: kolos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17578) "target" attribute get's removed from tags in job descriptions
Marc Günther created JENKINS-17578 "target" attribute get's removed from tags in job descriptions Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Apr/13 5:55 PM Description: I have some links in my job description. These point to external sites, and so it's quite useful to have them open in a new browser window. Unfortunately, the target attribute gets removed in the final output. Is there a specific reason for this? Project: Jenkins Priority: Trivial Reporter: Marc Günther This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extended-choice-parameter] (JENKINS-17518) When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter
SCM/JIRA link daemon commented on JENKINS-17518 When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter Code changed in jenkins User: vimil Path: src/main/java/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition.java src/main/resources/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition/config.jelly src/main/resources/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition/help-multiSelectDelimiter.html http://jenkins-ci.org/commit/extended-choice-parameter-plugin/016e67f1ec4cb96db90264853392a3396b00d421 Log: Merge pull request #2 from olhado/master Added code for JENKINS-17518 Compare: https://github.com/jenkinsci/extended-choice-parameter-plugin/compare/444e5b894379...016e67f1ec4c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13426) Can't save system config
evernat resolved JENKINS-13426 as Duplicate Can't save system config Change By: evernat (11/Apr/13 5:52 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17428) Jenkins v1.508 fails to load build history from disk
Paul Dunham
resolved JENKINS-17428 as Fixed
Jenkins v1.508 fails to load build history from disk
It turns out that my Workspace Root Directory was missing the ${ITEM_FULL_NAME} in the path name. Doh!
Change By:
Paul Dunham
(11/Apr/13 5:34 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
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14827) Cannot use /usr/bin/[ as a shell script step: wrapped in "..." after save
dogfood commented on JENKINS-14827 Cannot use /usr/bin/[ as a shell script step: wrapped in "..." after save Integrated in jenkins_main_trunk #2453 JENKINS-14827 Noting. (Revision f8f9462b6c4ed1c83da9fed53e88fe0b8d034890) Result = SUCCESS Jesse Glick : f8f9462b6c4ed1c83da9fed53e88fe0b8d034890 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17575) Incorrect redirection after delete of job in folder in view
dogfood commented on JENKINS-17575 Incorrect redirection after delete of job in folder in view Integrated in jenkins_main_trunk #2453 JENKINS-17575 Baseline testing of behavior without folders. (Revision dcff6e41302093b6ba90da0aa6e9b09a5cfe2b86) [FIXED JENKINS-17575] Redirecting properly after deleting jobs in folders. (Revision 1205e9f6c492c53983a7f02926a53739b50b92fd) Result = SUCCESS Jesse Glick : dcff6e41302093b6ba90da0aa6e9b09a5cfe2b86 Files : test/src/test/java/hudson/model/AbstractProjectTest.java Jesse Glick : 1205e9f6c492c53983a7f02926a53739b50b92fd Files : changelog.html test/src/test/java/hudson/model/AbstractProjectTest.java test/src/main/java/org/jvnet/hudson/test/MockFolder.java core/src/main/java/hudson/model/AbstractProject.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [join] (JENKINS-5974) Allow aggregation job to run even if some downstream jobs Failed
Andre Leitao commented on JENKINS-5974 Allow aggregation job to run even if some downstream jobs Failed It could be done like the build other 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [join] (JENKINS-5974) Allow aggregation job to run even if some downstream jobs Failed
Andre Leitao updated JENKINS-5974 Allow aggregation job to run even if some downstream jobs Failed Change By: Andre Leitao (11/Apr/13 5:18 PM) Attachment: build_other_projects_example.gif This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cobertura] (JENKINS-15703) Cobertura ClassCastException
Ignas Mikalajunas updated JENKINS-15703 Cobertura ClassCastException I am getting the same error. This is an example xml file that causes the error for me. I have even tried removing inner tags, like having no packages, just the coverage tag, but the error stays the same. Change By: Ignas Mikalajunas (11/Apr/13 5:10 PM) Attachment: coverage.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mail] (JENKINS-16437) Extract MailAddressResolvers to dedicated plugins
SCM/JIRA link daemon commented on JENKINS-16437 Extract MailAddressResolvers to dedicated plugins Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/tasks/MailAddressResolver.java http://jenkins-ci.org/commit/mailer-plugin/d97647e6bc5fffaafffe9621c8ffbd5d13877b2b Log: Merge pull request #5 from jenkinsci/wiki_link JENKINS-16437 Link to mail address resolution wiki page Compare: https://github.com/jenkinsci/mailer-plugin/compare/78a9e893e0b0...d97647e6bc5f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-5408) Quoting Issue with JDK Installer with Windows Slave
dogfood commented on JENKINS-5408 Quoting Issue with JDK Installer with Windows Slave Integrated in jenkins_main_trunk #2452 [FIXED JENKINS-5408] Quoting Issue with JDK Installer with Windows Slave (Revision fd4ccc106f603edfa5818befca271f1400bdbf96) Result = SUCCESS Seiji Sogabe : fd4ccc106f603edfa5818befca271f1400bdbf96 Files : core/src/main/java/hudson/tools/JDKInstaller.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [memory-map] (JENKINS-17465) Missing data from bar chart (our case 8954)
Mads Nielsen resolved JENKINS-17465 as Fixed Missing data from bar chart (our case 8954) Fixed in 1.0.1 Change By: Mads Nielsen (11/Apr/13 3:46 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [memory-map] (JENKINS-17466) Graph configuration not effective until after another build (our case 8955)
Mads Nielsen resolved JENKINS-17466 as Fixed Graph configuration not effective until after another build (our case 8955) Fixed in 1.0.1 Change By: Mads Nielsen (11/Apr/13 3:46 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17575) Incorrect redirection after delete of job in folder in view
SCM/JIRA link daemon resolved JENKINS-17575 as Fixed Incorrect redirection after delete of job in folder in view Change By: SCM/JIRA link daemon (11/Apr/13 3:39 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17575) Incorrect redirection after delete of job in folder in view
SCM/JIRA link daemon commented on JENKINS-17575 Incorrect redirection after delete of job in folder in view Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/AbstractProject.java test/src/main/java/org/jvnet/hudson/test/MockFolder.java test/src/test/java/hudson/model/AbstractProjectTest.java http://jenkins-ci.org/commit/jenkins/1205e9f6c492c53983a7f02926a53739b50b92fd Log: [FIXED JENKINS-17575] Redirecting properly after deleting jobs in folders. Expanded MockFolder to be a ViewGroup so that it is possible to test views inside folders, and generally fixed it to service Stapler hierarchies properly so that WebClient-based tests can work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17577) Add trigger list of triggers that fired to the object model of the pre-send script
Bram Tassyns commented on JENKINS-17577 Add trigger list of triggers that fired to the object model of the pre-send script If you add this, please also add a way to know for which of the triggers this script is currently being executed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17575) Incorrect redirection after delete of job in folder in view
SCM/JIRA link daemon commented on JENKINS-17575 Incorrect redirection after delete of job in folder in view Code changed in jenkins User: Jesse Glick Path: test/src/test/java/hudson/model/AbstractProjectTest.java http://jenkins-ci.org/commit/jenkins/dcff6e41302093b6ba90da0aa6e9b09a5cfe2b86 Log: JENKINS-17575 Baseline testing of behavior without folders. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14827) Cannot use /usr/bin/[ as a shell script step: wrapped in "..." after save
SCM/JIRA link daemon commented on JENKINS-14827 Cannot use /usr/bin/[ as a shell script step: wrapped in "..." after save Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/f8f9462b6c4ed1c83da9fed53e88fe0b8d034890 Log: JENKINS-14827 Noting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17577) Add trigger list of triggers that fired to the object model of the pre-send script
Alex Earl created JENKINS-17577 Add trigger list of triggers that fired to the object model of the pre-send script Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 11/Apr/13 3:24 PM Description: It would be useful to have a way for the pre-send script to know what triggers fired to cause the email to be sent. This would allow someone to filter emails if one trigger is in the list of fired triggers. The idea would allow people to customize the replacement strategy through the pre-send script. Project: Jenkins Priority: Minor Reporter: Alex Earl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-5408) Quoting Issue with JDK Installer with Windows Slave
SCM/JIRA link daemon commented on JENKINS-5408 Quoting Issue with JDK Installer with Windows Slave Code changed in jenkins User: Seiji Sogabe Path: core/src/main/java/hudson/tools/JDKInstaller.java http://jenkins-ci.org/commit/jenkins/c86b6d7055a03db1add27acd4a0159ad7d024c17 Log: Merge pull request #657 from ssogabe/JENKINS-5408 [FIXED JENKINS-5408] Quoting Issue with JDK Installer with Windows Slave Compare: https://github.com/jenkinsci/jenkins/compare/d33e22d392a3...c86b6d7055a0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-5408) Quoting Issue with JDK Installer with Windows Slave
SCM/JIRA link daemon resolved JENKINS-5408 as Fixed Quoting Issue with JDK Installer with Windows Slave Change By: SCM/JIRA link daemon (11/Apr/13 3:22 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-5408) Quoting Issue with JDK Installer with Windows Slave
SCM/JIRA link daemon commented on JENKINS-5408 Quoting Issue with JDK Installer with Windows Slave Code changed in jenkins User: Seiji Sogabe Path: core/src/main/java/hudson/tools/JDKInstaller.java http://jenkins-ci.org/commit/jenkins/fd4ccc106f603edfa5818befca271f1400bdbf96 Log: [FIXED JENKINS-5408] Quoting Issue with JDK Installer with Windows Slave This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-lint] (JENKINS-16075) Lint icon not shown when selecting a particular build
Christopher Orr resolved JENKINS-16075 as Fixed Lint icon not shown when selecting a particular build Marking this as fixed. I guess the bot doesn't like resolving "reopened" issues. Change By: Christopher Orr (11/Apr/13 3:20 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Herbert Vojčík commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online @HemangL My setup is: no security connecting to slave with password-protected private key. After delete, restart and create it worked fine (I should mention that backed up data, reinstalled whole jenkins (I have it under OpenVZ machine that is created and populated by script, so no big hassle for me) and returned data back, only then I did the delete-restart-recreate). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8358) A disabled project is always DISABLED even is the project is building
Anne Stellingwerf started work on JENKINS-8358 A disabled project is always DISABLED even is the project is building Change By: Anne Stellingwerf (11/Apr/13 3:00 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-17476) parameterized-trigger List Subversion tags default value set to a current build parameter not evaluated
Walter Stone edited a comment on JENKINS-17476 parameterized-trigger List Subversion tags default value set to a current build parameter not evaluated >In what version of Jenkins is this bug occurring or you do miss a feature, want an improvement? If this issue is (likely) related to plugins, please also include >the plugins' versions. 1.501 >What environment are you using? Hint: You should attach the information from http://SERVER/systemInfo. various clients, windows redhat, ubuntu, centos, aix, solairus >How are you running Jenkins? master with slave hosts >Using the executable war like java -jar jenkins.war no >Using another container as Tomcat or Jetty. no >Have you specified additional parameters for the Java VM (Heapspace etc.)? no >Did you just install the deb or rpm? deb >With which Java VM (Oracle, IBM etc.)? sun 1.6 and oracle 1.7 >On which operating system? 32- or 64-bit? both >Include stacktraces from the log if any. n/a >Did this error start occurring after an upgrade? no, from first use >What version did you upgrade to/from? n/a >Is this your first install? yes >If this is an issue in the collaboration with another system (e.g. a SCM), please also provide the type and the version of the other system 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
HemangLavana commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online @Herbert Do you use passphrase/private key or username/password for authentication? I suspect that 0.23 has some issues with private key auth. In my setup, the jenkins server is run under a dedicated userid say "jenkins" but for certain tasks it needs to login to slave nodes with my userid. I enable this in jenkins by providing access to "jenkins" userid to my account via ssh private key method. I don't want to store my username/password in jenkins (since it is not secure). Instead the "jenkins" userid can access my account via passphase/private authentication which seems to be broken in 0.23. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-17476) parameterized-trigger List Subversion tags default value set to a current build parameter not evaluated
Walter Stone commented on JENKINS-17476 parameterized-trigger List Subversion tags default value set to a current build parameter not evaluated >In what version of Jenkins is this bug occurring or you do miss a feature, want an improvement? If this issue is (likely) related to plugins, please also include >the plugins' versions. 1.501 >What environment are you using? Hint: You should attach the information from http://SERVER/systemInfo. various clients, windows rehat, ubuntu, centos, aix, solairus >How are you running Jenkins? master with slave hosts >Using the executable war like java -jar jenkins.war no >Using another container as Tomcat or Jetty. no >Have you specified additional parameters for the Java VM (Heapspace etc.)? no >Did you just install the deb or rpm? deb >With which Java VM (Oracle, IBM etc.)? sun 1.6 and oracle 1.7 >On which operating system? 32- or 64-bit? both >Include stacktraces from the log if any. n/a >Did this error start occurring after an upgrade? no, from first use >What version did you upgrade to/from? n/a >Is this your first install? yes >If this is an issue in the collaboration with another system (e.g. a SCM), please also provide the type and the version of the other system 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita closed JENKINS-17442 as Fixed When connecting to TestLink, finding error ClassCastException Thanks for understanding! Let me know if you need anything else. Cheers, B Change By: Bruno P. Kinoshita (11/Apr/13 2:54 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [locks-and-latches] (JENKINS-13828) locks-and-latches not release job and infinitely waits for unlock.
Bernard Miegemolle edited a comment on JENKINS-13828 locks-and-latches not release job and infinitely waits for unlock. This also happens sometimes to me when I cancel a build of a job that has a lock (but not each time). For example, the following build cancellation went well. As mentionned in the logs, the lock was released, and following builds could be executed. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3:22.655s [INFO] Finished at: Wed Apr 10 18:56:34 CEST 2013 [INFO] channel stopped [locks-and-latches] Releasing all the locks [locks-and-latches] All the locks released Build was aborted Aborted by bmiegemolle Final Memory: 76M/551M [INFO] Finished: ABORTED But sometimes when I cancel a build, nothing about lock release is displayed. See following build logs for example: Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/jquery.fileupload/jquery.fileupload.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/jquery.fileupload/jquery.iframe-transport.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/handlebars/handlebars-1.0.rc.1.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/handlebars/handlebars-1.0.0.beta.6.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/select2/select2.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/jquery.storage/jquery.Storage.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/humane/humane.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/highcharts/highcharts.js Build was aborted Aborted by bmiegemolle Finished: ABORTED Following builds remained blocked just after the svn update: [locks-and-latches] Checking to see if we really have the locks [locks-and-latches] Could not get all the locks... sleeping for 1 minute [locks-and-latches] Could not get all the locks... sleeping for 1 minute [locks-and-latches] Could not get all the locks... sleeping for 1 minute [locks-and-latches] Could not get all the locks... sleeping for 1 minute Restarting Jenkins make things work again. I don't have any clue on the conditions that lead to 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Jeanjean LaGuigne resolved JENKINS-17442 as Fixed When connecting to TestLink, finding error ClassCastException Change By: Jeanjean LaGuigne (11/Apr/13 2:40 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Jeanjean LaGuigne commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Ok, thanks for your fast answers! Of course we can close 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Jesse Glick commented on JENKINS-13995 Would like the ability to disable hover-over context menus. @adamashley agreed there are problems with the UI that need fixing. For me, the arrow generally disappears when I try to click on it. I can only use it if I position my mouse within a very narrow margin, a pixel or two. @rking if HTTP service is slow, making the context menu not appear unless and until clicked should improve things a bit, since displaying the context menu is also an HTTP request that adds to server load. Formerly, a lot of context menu background requests were made and then discarded as the mouse just incidentally swept by any number of model links. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-5408) Quoting Issue with JDK Installer with Windows Slave
Diogo Guerra commented on JENKINS-5408 Quoting Issue with JDK Installer with Windows Slave I've tried @sogabe patch on 1.510 and it works. could you please accept the pull request? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-13931) sd card option requires multi-configuration axis name to be in capital letters
SCM/JIRA link daemon commented on JENKINS-13931 sd card option requires multi-configuration axis name to be in capital letters Code changed in jenkins User: Christopher Orr Path: src/main/java/hudson/plugins/android_emulator/AndroidEmulator.java src/main/java/hudson/plugins/android_emulator/EmulatorConfig.java http://jenkins-ci.org/commit/android-emulator-plugin/eca88909f30a772e37da6c9b419a6915bffd8354 Log: [FIXED JENKINS-13931] Don't alter SD card value when saving configuration, as it may contain a variable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-13931) sd card option requires multi-configuration axis name to be in capital letters
SCM/JIRA link daemon resolved JENKINS-13931 as Fixed sd card option requires multi-configuration axis name to be in capital letters Change By: SCM/JIRA link daemon (11/Apr/13 2:23 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17460) Error occurs viewing build history on some builds
Bruce Coveny updated JENKINS-17460 Error occurs viewing build history on some builds Change By: Bruce Coveny (11/Apr/13 2:04 PM) Environment: JENKINS WAR VERSION 1.509 /1.510 WINDOWS SERVER 2008 R2 ENTERPRISEAMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS)4.0 GB RAM64-BIT OPERATION SYSTEMWEBSPHERE APPLICATION SERVER 7.0.0.23 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Yup, check the compatibility matrix in the plug-in Wiki [1] Unfortunately you have to stick to a specific version of the plug-in, until you're able to update your TestLink instance. Reasons for not having compatibility between versions include: Newer version of the plug-in may use new features in TestLink. Methods changed/removed/etc in TestLink XML-RPC API (this was, by the way, what was causing this bug :=) Bugs in the PHP XML-RPC API, or in the Java API (testlink-java-api) My laziness (and lack of time) for hacking an extra abstraction layer for this Sorry for not being able to be of more help. If you're ok with it, I'll close the issue again, ok? Thanks! [1] https://wiki.jenkins-ci.org/display/JENKINS/TestLink+Plugin#TestLinkPlugin-CompatibilityMatrix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-16246) A failure of the uninstall package build step does not result in a build failure
SCM/JIRA link daemon resolved JENKINS-16246 as Fixed A failure of the uninstall package build step does not result in a build failure Change By: SCM/JIRA link daemon (11/Apr/13 1:53 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Herbert Vojčík commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online @Yoram No need to downgrade for me. Just delete all credentials, restart Jenkins and set them back, and it works with 0.23. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [embeddable-build-status] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Maciej Gąsiorowski commented on JENKINS-15769 Provide way to allow build icons without anonymous access. Publish build status on Gitlab/Trac etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-16246) A failure of the uninstall package build step does not result in a build failure
SCM/JIRA link daemon commented on JENKINS-16246 A failure of the uninstall package build step does not result in a build failure Code changed in jenkins User: Christopher Orr Path: src/main/java/hudson/plugins/android_emulator/UninstallBuilder.java src/main/java/hudson/plugins/android_emulator/builder/AbstractBuilder.java src/main/resources/hudson/plugins/android_emulator/UninstallBuilder/config.jelly src/main/webapp/help-failOnUninstallFailure.html http://jenkins-ci.org/commit/android-emulator-plugin/f3fff7c9b96356c62cdc9c3f5d3a5fd33036b48d Log: [FIXED JENKINS-16246] Build can now be failed if package uninstallation fails. Compare: https://github.com/jenkinsci/android-emulator-plugin/compare/bcb34128acd6...f3fff7c9b963 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-13932) React to failed APK install
SCM/JIRA link daemon resolved JENKINS-13932 as Fixed React to failed APK install Change By: SCM/JIRA link daemon (11/Apr/13 1:53 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-13932) React to failed APK install
SCM/JIRA link daemon commented on JENKINS-13932 React to failed APK install Code changed in jenkins User: Christopher Orr Path: src/main/java/hudson/plugins/android_emulator/InstallBuilder.java src/main/resources/hudson/plugins/android_emulator/InstallBuilder/config.jelly src/main/webapp/help-failOnInstallFailure.html http://jenkins-ci.org/commit/android-emulator-plugin/59e2ec54506437d93054f86babe99b65b7ee2960 Log: [FIXED JENKINS-13932] Build can now be failed if package installation fails. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Jeanjean LaGuigne commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Ho no, I am using TestLink 1.9.5 and 1.9.2. There are some compatibility issues? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17460) Error occurs viewing build history on some builds
Bruce Coveny edited a comment on JENKINS-17460 Error occurs viewing build history on some builds I was able to recreate doing the following. Create a build called "test", this does not have to any steps included in it. Create another build called "test (test)". In this build configuration create the build step of "Trigger/call builds on other projects" with the following properties: Projects to build: test Block until the triggered projects finish their builds: checked Fail this build step if the triggered build is worse or equal to: FAILURE Mark this build as failure if the triggered build is worse or equal to: FAILURE Mark this build as unstable if the triggered build is worse or equal to: UNSTABLE Save the configuration. Run the build on "test (test)". Once the build history shows on the left hand side, click the link for view the build history. This is when the failure occurs. You can click the menu dropdown for the build history to view the console output and that link works fine, its just the main page for the build that fails. Note this still happens in 1.510. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17460) Error occurs viewing build history on some builds
Bruce Coveny commented on JENKINS-17460 Error occurs viewing build history on some builds I was able to recreate doing the following. Create a build called "test", this does not have to any steps included in it. Create another build called "test (test)". In this build configuration create the build step of "Trigger/call builds on other projects" with the following properties: Projects to build: test Block until the triggered projects finsih their builds: checked Fail this build step if the triggered build is worse or equal to: FAILURE Mark this build as failure if the triggered build is worse or equal to: FAILURE Mark this build as unstable if the triggered build is worse or equal to: UNSTABLE Save the configuration. Run the build on "test (test)". Once the build history shows on the left hand side, click the link for view the build history. This is when the failure occurs. You can click the menu dropdown for the build history to view the console output and that link works fine, its just the main page for the build that fails. Note this still happens in 1.510. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13856) Jenkins wraps square and curly bracket string parameter values in quotation marks
Jesse Glick resolved JENKINS-13856 as Duplicate Jenkins wraps square and curly bracket string parameter values in quotation marks Was fixed in 1.506. Change By: Jesse Glick (11/Apr/13 1: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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Yoram Michaeli commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online I had the same issue and downgrade to 0.22 of the ssh-slaves plugin solved it for me as well. I needed to re-enter the credentials for all the nodes as well. Lucky me that I have only 6 nodes... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Hi @Jeanjean! Thanks for the compliments Weird. Are you using TestLink 1.9.6 with Jenkins TestLink Plug-in 3.3? Thanks 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-17576) Conditional buildstep unable to launch MultiJob
David Ishee created JENKINS-17576 Conditional buildstep unable to launch MultiJob Issue Type: Bug Assignee: domi Components: conditional-buildstep Created: 11/Apr/13 1:45 PM Description: This is related to JENKINS-16974. A conditional buildstep is not able to launch a MultiJob. Environment: Jenkins 1.480.3 conditional-buildstep v1.2.1 MultiJob plugin v1.8 Red Hat Linux Project: Jenkins Priority: Major Reporter: David Ishee This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17023) Jenkins Testlink plugin Found 0 test result is show while test is runned
Bruno P. Kinoshita commented on JENKINS-17023 Jenkins Testlink plugin Found 0 test result is show while test is runned Hi @Abdallah, There is a download link at [1]. But you can use Jenkins update site too (see [2]). HTH, B [1] http://updates.jenkins-ci.org/download/plugins/testlink/ [2] https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Usingtheinterface This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Jeanjean LaGuigne reopened JENKINS-17442 When connecting to TestLink, finding error ClassCastException Change By: Jeanjean LaGuigne (11/Apr/13 1:42 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
HemangLavana commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online It is happening to me as well. I am unable to use private key for authentication, even on a completely fresh installation of jenkins/ssh-slaves plugin. I rolled back to 0.22 version of ssh slaves plugin and I was able to get it to work but I lost all the private key passphrase stored in all the slave nodes. I have to manually re-enter all of them and I had over 40 slave nodes. I hope this issue gets fixed 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Jeanjean LaGuigne commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Hi Bruno, In a first time great job, I use your plugin for my projects, so thanks a lot! But I think the problem is not fixed with the 3.3 version. I fact i had to downgrade to the october version of your plugin to have the issue fixed . Thanks again for your 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prqa] (JENKINS-17019) Incompatible prqa plugin with older Jenkins version (our case 8751)
Mads Nielsen resolved JENKINS-17019 as Won't Fix Incompatible prqa plugin with older Jenkins version (our case 8751) We use an extension point that was added after 1.424, so we won't implement this. Change By: Mads Nielsen (11/Apr/13 1:05 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prqa] (JENKINS-17019) Incompatible prqa plugin with older Jenkins version (our case 8751)
Mads Nielsen updated JENKINS-17019 Incompatible prqa plugin with older Jenkins version (our case 8751) Change By: Mads Nielsen (11/Apr/13 1:04 PM) Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17023) Jenkins Testlink plugin Found 0 test result is show while test is runned
Abdallah Saidane commented on JENKINS-17023 Jenkins Testlink plugin Found 0 test result is show while test is runned Hi Bruno can you please where can I get this new release 3.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [locks-and-latches] (JENKINS-13828) locks-and-latches not release job and infinitely waits for unlock.
Bernard Miegemolle commented on JENKINS-13828 locks-and-latches not release job and infinitely waits for unlock. This also happens sometimes to me when I cancel a build of a job that has a lock (but not each time). For example, the following build cancellation went well. As mentionned in the logs, the lock was released, and following builds could be executed. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3:22.655s [INFO] Finished at: Wed Apr 10 18:56:34 CEST 2013 [INFO] channel stopped [locks-and-latches] Releasing all the locks [locks-and-latches] All the locks released Build was aborted Aborted by bmiegemolle Final Memory: 76M/551M [INFO] Finished: ABORTED But sometimes when I cancel a build, nothing about lock release is displayed. See following build logs for example: Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/jquery.fileupload/jquery.fileupload.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/jquery.fileupload/jquery.iframe-transport.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/handlebars/handlebars-1.0.rc.1.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/handlebars/handlebars-1.0.0.beta.6.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/select2/select2.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/jquery.storage/jquery.Storage.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/humane/humane.js Uglifying file: /srv/jenkins/platform/jobs/trunk/workspace/target/classes/web/resources-built/vendor/highcharts/highcharts.js Build was aborted Aborted by bmiegemolle Finished: ABORTED Following builds remaimed blocked just after the svn update: [locks-and-latches] Checking to see if we really have the locks [locks-and-latches] Could not get all the locks... sleeping for 1 minute [locks-and-latches] Could not get all the locks... sleeping for 1 minute [locks-and-latches] Could not get all the locks... sleeping for 1 minute [locks-and-latches] Could not get all the locks... sleeping for 1 minute Restarting Jenkins make things work again. I don't have any clue on the conditions that lead to 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
☈ king commented on JENKINS-13995 Would like the ability to disable hover-over context menus. The current widget is hard to use. I liked the way it was before, but I understand that not everyone does, so maybe we can figure out something that works for all of us? The problem is that it's not discoverable. You mouse over and get this tiny "v", which isn't obvious that if you then click on that, you'll get a menu. One option would be to make the "v" always visible, and hopefully a bit bigger. Note that, on our server, every web hit takes quite a while, so the popout menu is nice: it makes it clear that you don't have to actually go to the intermediate step to get where you want. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-14952) Downstream job build links are broken when jenkins is not hosted on the root context
Björn Pedersen commented on JENKINS-14952 Downstream job build links are broken when jenkins is not hosted on the root context see comment at https://issues.jenkins-ci.org/browse/JENKINS-14955 for the missing change. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17575) Incorrect redirection after delete of job in folder in view
Jesse Glick created JENKINS-17575 Incorrect redirection after delete of job in folder in view Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Apr/13 12:31 PM Description: If you create a top-level list view v, to which you add a folder d, and add a job j inside the folder, then delete j, you are redirected to /view/v/ rather than /view/v/job/d/ as expected. This is because in AbstractProject.doDoDelete, req.findAncestorObject(View.class) is v, whose url is view/v/. In this case we would be better served by using the super method's logic (the branch where view == null), since parent.url is view/v/job/d/ which is what we want. The use of view.url is only appropriate in case that view's view group is the same as this job's parent. Project: Jenkins Labels: folders Priority: Minor 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14955) Wrong links created on summary on a multijob execution
Björn Pedersen
commented on JENKINS-14955
Wrong links created on summary on a multijob execution
The bug still exist in 1.9, one change is still necessary:
index d347b07..b2f453f 100644
— a/src/main/resources/com/tikal/jenkins/plugins/multijob/MultiJobBuild/main.jelly
+++ b/src/main/resources/com/tikal/jenkins/plugins/multijob/MultiJobBuild/main.jelly
@@ -17,7 +17,7 @@
+
build #${builder.buildNumber}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Herbert Vojčík commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online Deleting all credentials and creating them anew solved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gradle] (JENKINS-17386) Gradle.properties ignored after 1.22 upgrade
Jochen Hinrichsen commented on JENKINS-17386 Gradle.properties ignored after 1.22 upgrade +1: same problem that $HOME/.gradle/gradle.properties is used for credentials. What's the reason for setting GRADLE_USER_HOME to job's workspace? We are making heavy use of gradle wrapper. Gradle distributions being installed per job instead of being shared nastily impacts the storage size. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Herbert Vojčík edited a comment on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online It happens to me as well (master&slave CentOS). Problem is the private key with password. I think it does not use the password to unlock the key. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Herbert Vojčík commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online It happens to me as well. Problem is the private key with password. I think it does not use the password to unlock the key. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cvs] (JENKINS-17383) CVS plugin detect changes in 'rlog' but not in 'update'
K P commented on JENKINS-17383 CVS plugin detect changes in 'rlog' but not in 'update' I confirm this issue - update not working. (by the way: CVS client and server running in same timezone. CVS server = CVSNT server) The update is seen in cvs logging, but the file is not updated. I have the "force clean copy" (-C) option is check as well. The workspace file is not updated. However, it did copy the "old" version to a ".#." file in the workspace (same directory as original file). But after that, the actual file is not updated to the latest (HEAD) version. So update is broken. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [repo] (JENKINS-17574) Branch used by manifest is incorrectly compared to generate changelogs
Yves-Marie Morgan
created JENKINS-17574
Branch used by manifest is incorrectly compared to generate changelogs
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
repo
Created:
11/Apr/13 8:59 AM
Description:
When not using the default value for manifest branch, the method getLastState in class RepoScm does not retrieve a valid last state. This leads to an empty changelog.
This is due to the string comparison :
if (lastState != null && lastState.getBranch() == manifestBranch)
It does not work unless branch is 'null'.
Something like that works better :
if (lastState != null
&& ((lastState.getBranch() == null && manifestBranch == null)
(lastState.getBranch().equals(manifestBranch {
Project:
Jenkins
Priority:
Minor
Reporter:
Yves-Marie Morgan
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17573) Installation from jenkins-ci repository fails on Ubuntu 12.04 when jenkins is already installed
Christian Tellefsen created JENKINS-17573 Installation from jenkins-ci repository fails on Ubuntu 12.04 when jenkins is already installed Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 11/Apr/13 8:50 AM Description: Error from dpkg while installing from the jenkins-ci apt repository: Unpacking jenkins (from .../archives/jenkins_1.510_all.deb) ... dpkg: error processing /var/cache/apt/archives/jenkins_1.510_all.deb (--unpack): trying to overwrite '/usr/share/jenkins/jenkins.war', which is also in package jenkins-common 1.424.6+dfsg-1ubuntu0.1 Steps to reproduce: Install jenkins from the standard Ubuntu repositories. (currently 1.424). Ubuntu splits jenkins into packages jenkins and jenkins-common. Add the jenkins-ci repository to /etc/apt/sources.list. apt-get update apt-get -u upgrade observe that jenkins will be upgraded. Note that jenkins-common is not mentioned. During upgrade, apt reports the error shown above. Suggested fix: Consider adding "conflicts: jenkins-common". Environment: Ubuntu 12.04 Fix Versions: current Project: Jenkins Labels: ubuntu installation Priority: Minor Reporter: Christian Tellefsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17573) Installation from jenkins-ci repository fails on Ubuntu 12.04 when jenkins is already installed
Christian Tellefsen commented on JENKINS-17573 Installation from jenkins-ci repository fails on Ubuntu 12.04 when jenkins is already installed Workaround: Uninstall the Ubuntu-provided jenkins installation before installing the latest snapshots from the jenkins-ci repository: apt-get remove jenkins jenkins-common This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
Artur Szostak commented on JENKINS-17566 Severe polling error when using script trigger Scripttrigger version is 0.22 EnvInject version is 0.43 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Christoph Moser edited a comment on JENKINS-17222 Add ability to specify more than one location when using the svn method Hi Chris! I tried both ... when I use the period I get following exception: FATAL: No signature of method: java.lang.String.hudson.scm.SubversionSCM_-ModuleLocation() is applicable for argument types: (script136566702984857485466$_run_closure1_closure2_closure3_closure4) values: [script136566702984857485466$_run_closure1_closure2_closure3_closure4@81a2e1] groovy.lang.MissingMethodException: No signature of method: java.lang.String.hudson.scm.SubversionSCM_-ModuleLocation() is applicable for argument types: (script136566702984857485466$_run_closure1_closure2_closure3_closure4) values: [script136566702984857485466$_run_closure1_closure2_closure3_closure4@81a2e1] at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:55) at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:46) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) ... ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Christoph Moser commented on JENKINS-17222 Add ability to specify more than one location when using the svn method Hi Chris! I tried bothe ... when i use the period I get following exception: FATAL: No signature of method: java.lang.String.hudson.scm.SubversionSCM_-ModuleLocation() is applicable for argument types: (script136566702984857485466$_run_closure1_closure2_closure3_closure4) values: [script136566702984857485466$_run_closure1_closure2_closure3_closure4@81a2e1] groovy.lang.MissingMethodException: No signature of method: java.lang.String.hudson.scm.SubversionSCM_-ModuleLocation() is applicable for argument types: (script136566702984857485466$_run_closure1_closure2_closure3_closure4) values: [script136566702984857485466$_run_closure1_closure2_closure3_closure4@81a2e1] at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:55) at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:46) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) ... ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17572) plugin fails to create tabs in some cases
Vlad Aginsky updated JENKINS-17572 plugin fails to create tabs in some cases Change By: Vlad Aginsky (11/Apr/13 7:48 AM) Environment: jenkins 1.508, chrome and IE in windows, Summary Display Plugin 1.9 Description: Hi, I observe this failure from time to time:tabs fail to be created.I tried it in chrome, IE10, still 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17572) plugin fails to create tabs in some cases
Vlad Aginsky updated JENKINS-17572 plugin fails to create tabs in some cases see 3 tables but not 3 tabs Change By: Vlad Aginsky (11/Apr/13 7:46 AM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17572) plugin fails to create tabs in some cases
Vlad Aginsky updated JENKINS-17572 plugin fails to create tabs in some cases xml frame that fails Change By: Vlad Aginsky (11/Apr/13 7:43 AM) Attachment: fullFrame (1).xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17572) plugin fails to create tabs in some cases
Vlad Aginsky assigned JENKINS-17572 to deruyter plugin fails to create tabs in some cases Change By: Vlad Aginsky (11/Apr/13 7:40 AM) Assignee: deruyter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17572) plugin fails to create tabs in some cases
Vlad Aginsky edited a comment on JENKINS-17572 plugin fails to create tabs in some cases Hi, I observe this failure from time to time: tabs fail to be created. I tried it in chrome, IE10, still 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17572) plugin fails to create tabs in some cases
Vlad Aginsky commented on JENKINS-17572 plugin fails to create tabs in some cases Hi, I observe this failure from time to 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17572) plugin fails to create tabs in some cases
Vlad Aginsky created JENKINS-17572 plugin fails to create tabs in some cases Issue Type: Bug Assignee: Unassigned Components: plugin Created: 11/Apr/13 7:35 AM Project: Jenkins Priority: Major Reporter: Vlad Aginsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
