[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X, IBM AIX slave fails
Chris Graham reopened JENKINS-13614 archiving artefacts from remote MacOS X, IBM AIX slave fails I just installed 1.481 (the latest as of now) under WAS 6.1 (JDK 1.5) on AIX 5.3 (so it's the master - with no slaves). This is not a slave issue. Running a Maven build results in: JENKINS Archiving site from /hudson/hudson/jobs/GPDB/workspace/target/site to /hudson/hudson/jobs/GPDB/site Failed to load native POSIX impl; falling back on Java impl. Unsupported OS. FATAL: Unable to copy site from /hudson/hudson/jobs/GPDB/workspace/target/site to /hudson/hudson/jobs/GPDB/site java.io.IOException: readlink: not found at java.lang.UNIXProcess.fullPath(UNIXProcess.java:398) at java.lang.UNIXProcess.init(UNIXProcess.java:178) at java.lang.ProcessImpl.start(ProcessImpl.java:114) at java.lang.ProcessBuilder.start(ProcessBuilder.java:479) at java.lang.Runtime.exec(Runtime.java:607) at org.jruby.ext.posix.util.ExecIt.run(ExecIt.java:61) at org.jruby.ext.posix.util.ExecIt.runAndWait(ExecIt.java:51) at org.jruby.ext.posix.JavaLibCHelper.readlink(JavaLibCHelper.java:196) at org.jruby.ext.posix.JavaPOSIX.readlink(JavaPOSIX.java:160) at hudson.Util.resolveSymlink(Util.java:1074) at hudson.util.DirScanner$Glob.scan(DirScanner.java:115) at hudson.FilePath.writeToTar(FilePath.java:1827) at hudson.FilePath.copyRecursiveTo(FilePath.java:1754) at hudson.FilePath.copyRecursiveTo(FilePath.java:1683) at hudson.maven.reporters.MavenSiteArchiver.postExecute(MavenSiteArchiver.java:82) at hudson.maven.Maven2Builder.postExecute(Maven2Builder.java:155) at hudson.maven.MavenBuilder$Adapter.postExecute(MavenBuilder.java:310) at hudson.maven.agent.PluginManagerInterceptor$1MojoIntercepterImpl.callPost(PluginManagerInterceptor.java:170) at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:185) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:151) at hudson.maven.Maven2Builder.call(Maven2Builder.java:77) at hudson.maven.Maven2Builder.call(Maven2Builder.java:53) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:284) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:678) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:703) at java.lang.Thread.run(Thread.java:811) INFO ERROR BUILD ERROR INFO Change By: Chris Graham (14/Sep/12 6:21 AM)
[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X, IBM AIX slave fails
Nickolay Martinov commented on JENKINS-13614 archiving artefacts from remote MacOS X, IBM AIX slave fails This is not a master/slave issue. This is an issue with artifact archiving on platforms other than Windows and Linux. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15164) Using openjdk 6 to build jenkins from code failed
xibo ning created JENKINS-15164 Using openjdk 6 to build jenkins from code failed Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 14/Sep/12 7:12 AM Description: Build jenkins from jenkinsci-jenkins-jenkins-1.481-77-gf1aa7ba.zip by the command: mvn -Denforcer.skip=true -Plight-test clean install We need skip maven-enforcer-plugin, although we have openjdk 1.6.0_24 and maven 3.0.3. There are problems about generic classes or methods type inference. I got the following errors: ERROR Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5:compile (default-compile) on project jenkins-core: Compilation failure ERROR /home/tsllst/study/src/jenkinsci-jenkins-f1aa7ba/core/src/main/java/hudson/DescriptorExtensionList.java:86,35 incompatible types; no instance(s) of type variable(s) D exist so that hudson.DescriptorExtensionListT,D conforms to hudson.DescriptorExtensionListT,D ERROR found : Dhudson.DescriptorExtensionListT,D ERROR required: hudson.DescriptorExtensionListT,D ERROR - Help 1 ERROR Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project jenkins-core: Compilation failure: Compilation failure: ERROR /home/xning/study/src/jenkinsci-jenkins-53f2177/core/src/main/java/hudson/model/AbstractBuild.java:465,49 cannot find symbol ERROR symbol : method getCustomWorkspace() ERROR location: class hudson.model.Job ERROR /home/xning/study/src/jenkinsci-jenkins-53f2177/core/src/main/java/hudson/model/AbstractBuild.java:499,28 cannot find symbol ERROR symbol : method getScmCheckoutStrategy() ERROR location: class hudson.model.Job Cannot compile groovy files ERROR Failed to execute goal org.codehaus.gmaven:gmaven-plugin:1.3:compile (default) on project jenkins-core: startup failed: ERROR /home/xning/study/src/jenkinsci-jenkins-53f2177/core/src/main/groovy/jenkins/util/groovy/AbstractGroovyViewModul\ e.groovy: 7: unable to resolve class lib.JenkinsTagLib ERROR @ line 7, column 1. ERROR import lib.JenkinsTagLib Cannot process annotation ERROR Failed to execute goal com.infradna.tool:bridge-method-injector:1.4:process (default) on project jenkins-core: Failed to process @WithBridgeMethods: /home/xning/study/src/jenkinsci-jenkins-f48d05d/core/target/classes/hudson/model/User.class (No such file or directory) - Help 1 Environment: Linux desktop.pusf.org 3.4.9-2.fc16.x86_64 #1 SMP Thu Aug 23 17:51:29 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux java version 1.6.0_24 OpenJDK Runtime Environment (IcedTea6 1.11.3) (fedora-67.1.11.3.fc16-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) javac 1.6.0_24 Apache Maven 3.0.3 (rNON-CANONICAL_2011-10-11_11-56_mockbuild; 2011-10-11 19:56:36+0800) Maven home: /usr/share/maven Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.4.9-2.fc16.x86_64, arch: amd64, family: unix Project: Jenkins Labels: jenkins build Priority: Major Reporter: xibo ning This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15165) Using openjdk 6 to build jenkins from code failed
xibo ning created JENKINS-15165 Using openjdk 6 to build jenkins from code failed Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 14/Sep/12 7:15 AM Description: Build jenkins by the command: mvn -Denforcer.skip=true -Plight-test clean install We need skip maven-enforcer-plugin, although we have openjdk 1.6.0_24 and maven 3.0.3. There are problems about generic classes or methods type inference. I got the following errors: ERROR Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5:compile (default-compile) on project jenkins-core: Compilation failure ERROR /home/tsllst/study/src/jenkinsci-jenkins-f1aa7ba/core/src/main/java/hudson/DescriptorExtensionList.java:86,35 incompatible types; no instance(s) of type variable(s) D exist so that hudson.DescriptorExtensionListT,D conforms to hudson.DescriptorExtensionListT,D ERROR found : Dhudson.DescriptorExtensionListT,D ERROR required: hudson.DescriptorExtensionListT,D ERROR - Help 1 ERROR Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project jenkins-core: Compilation failure: Compilation failure: ERROR /home/xning/study/src/jenkinsci-jenkins-53f2177/core/src/main/java/hudson/model/AbstractBuild.java:465,49 cannot find symbol ERROR symbol : method getCustomWorkspace() ERROR location: class hudson.model.Job ERROR /home/xning/study/src/jenkinsci-jenkins-53f2177/core/src/main/java/hudson/model/AbstractBuild.java:499,28 cannot find symbol ERROR symbol : method getScmCheckoutStrategy() ERROR location: class hudson.model.Job Cannot compile groovy files ERROR Failed to execute goal org.codehaus.gmaven:gmaven-plugin:1.3:compile (default) on project jenkins-core: startup failed: ERROR /home/xning/study/src/jenkinsci-jenkins-53f2177/core/src/main/groovy/jenkins/util/groovy/AbstractGroovyViewModul\ e.groovy: 7: unable to resolve class lib.JenkinsTagLib ERROR @ line 7, column 1. ERROR import lib.JenkinsTagLib Cannot process annotation ERROR Failed to execute goal com.infradna.tool:bridge-method-injector:1.4:process (default) on project jenkins-core: Failed to process @WithBridgeMethods: /home/xning/study/src/jenkinsci-jenkins-f48d05d/core/target/classes/hudson/model/User.class (No such file or directory) - Help 1 Due Date: 14/Sep/12 12:00 AM Environment: Linux desktop.pusf.org 3.4.9-2.fc16.x86_64 #1 SMP Thu Aug 23 17:51:29 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux java version 1.6.0_24 OpenJDK Runtime Environment (IcedTea6 1.11.3) (fedora-67.1.11.3.fc16-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) javac 1.6.0_24 Apache Maven 3.0.3 (rNON-CANONICAL_2011-10-11_11-56_mockbuild; 2011-10-11 19:56:36+0800) Maven home: /usr/share/maven Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.4.9-2.fc16.x86_64, arch: amd64, family: unix Project: Jenkins Labels: jenkins build Priority: Major Reporter: xibo ning This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15132) Cannot use a single file name as module for retrieval in CVS Plugin version 2.5
Deepak Mahale commented on JENKINS-15132 Cannot use a single file name as module for retrieval in CVS Plugin version 2.5 Michael: Thanks for taking time, I'm checking out from the following dir structure install mvbin pkginfo file2 file3 file4 file5 file6 mvbinpro pkginfo file2 file3 file4 file5 file6 parent2 child_dir grandchild_dir Configuration which works fine has module's as follows CVS Plugin Version 1.6 Module: install/mvbin/pkginfo install/mvbinpro/pkginfo parent2/child_dir/grandchild_dir NOTE: Whitespace separated list NOTE: It used to retrieve each pkginfo file in proper directory structure CVS Plugin Version 2.5 Module 1: install/mvbin Module 2: install/mvbinpro Module 3: parent2/child_dir/grandchild_dir Configuration which doesn't work has module's as follows CVS Plugin Version 2.5 Module 1: install/mvbin/pkginfo Module 2: install/mvbinpro/pkginfo Module 3: parent2/child_dir/grandchild_dir As the mvbin and mvbinpro directories contain only a few files in my case, it doesn't make a big difference to checkout the directories, so i've used that as a workaround. But if all i need is one file from a directory containing 2,000 files, then it'll be a big loss in terms of efficiency and time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15132) Cannot use a single file name as module for retrieval in CVS Plugin version 2.5
Deepak Mahale edited a comment on JENKINS-15132 Cannot use a single file name as module for retrieval in CVS Plugin version 2.5 Michael: Thanks for prompt reply, I'm checking out from the following dir structure install mvbin pkginfo file2 file3 file4 file5 file6 mvbinpro pkginfo file2 file3 file4 file5 file6 parent2 child_dir grandchild_dir Configuration which works fine has module's as follows CVS Plugin Version 1.6 Module: install/mvbin/pkginfo install/mvbinpro/pkginfo parent2/child_dir/grandchild_dir NOTE: Whitespace separated list NOTE: It used to retrieve each pkginfo file in proper directory structure CVS Plugin Version 2.5 Module 1: install/mvbin Module 2: install/mvbinpro Module 3: parent2/child_dir/grandchild_dir Configuration which doesn't work has module's as follows CVS Plugin Version 2.5 Module 1: install/mvbin/pkginfo Module 2: install/mvbinpro/pkginfo Module 3: parent2/child_dir/grandchild_dir As the mvbin and mvbinpro directories contain only a few files in my case, it doesn't make a big difference to checkout the directories, so i've used that as a workaround. But if all i need is one file from a directory containing 2,000 files, then it'll be a big loss in terms of efficiency and time. Thanks again Regards Deepak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Markus Maki commented on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Hi, I also got the behaviour mentioned in the bug description. Since I also use global variables for the Job configurations I would appreciate, if someone could link or send a custom subversion-plugin .hpi file where Bela's Patch is applied. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14638) Update documentation links
wernight commented on JENKINS-14638 Update documentation links Thumbs up! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10123) Unable to find manually installed Maven artifacts
safe buster commented on JENKINS-10123 Unable to find manually installed Maven artifacts i have same problem and i fix it by creating symlink mklink /D c:\.m2 c:\Users\my_user_name\.m2\ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15166) Gradle plugin falis to save selected Gradle Version in Project configuration
Johannes Rost created JENKINS-15166 Gradle plugin falis to save selected Gradle Version in Project configuration Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: gradle Created: 14/Sep/12 9:21 AM Description: Hello, I have to following problem with the Gradle plugin for Jenkins: While editing the project configuration I am able to select one of the installed Gradle versions to use for "Invoke Gradle". After saving the project configuration, the value of "Gradle Version" falls back to "(Default)". Since I don't have (and don't intend to have) Gradle on the path, every build fails with the following message: [Gradle] - Launching build. [i4r-hire-build] $ cmd.exe /C gradle.bat build exit %%ERRORLEVEL%% 'gradle.bat' is not recognized as an internal or external command, operable program or batch file. Build step 'Invoke Gradle script' changed build result to FAILURE Build step 'Invoke Gradle script' marked build as failure Recording test results Finished: FAILURE I am using Gradle plugin version 1.19 and Jenkins version 1.481 Project: Jenkins Priority: Major Reporter: Johannes Rost This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15166) Gradle plugin falis to save selected Gradle Version in Project configuration
Johannes Rost commented on JENKINS-15166 Gradle plugin falis to save selected Gradle Version in Project configuration Here is my Gradle plugin configuration (hudson.plugins.gradle.Gradle.xml): ?xml version='1.0' encoding='UTF-8'? hudson.plugins.gradle.Gradle_-DescriptorImpl helpRedirect/ installations hudson.plugins.gradle.GradleInstallation nameGradle_1_2 (Gradle.org)/name home/home properties hudson.tools.InstallSourceProperty installers hudson.plugins.gradle.GradleInstaller id1.2/id /hudson.plugins.gradle.GradleInstaller /installers /hudson.tools.InstallSourceProperty /properties gradleHome/gradleHome /hudson.plugins.gradle.GradleInstallation hudson.plugins.gradle.GradleInstallation nameGradle_1_2 (Lokal)/name homeD:\jenkins\tools\Gradle\gradle_1_2/home properties/ gradleHomeD:\jenkins\tools\Gradle\gradle_1_2/gradleHome /hudson.plugins.gradle.GradleInstallation /installations /hudson.plugins.gradle.Gradle_-DescriptorImpl When editing a project configuration I can select both configurations. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11700) After master comes back on line, build fails after all build steps and post build actions. Jenkins can't find slave-null.log
Niall Pemberton commented on JENKINS-11700 After master comes back on line, build fails after all build steps and post build actions. Jenkins cant find slave-null.log How did you resolve this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15167) Parsing pom.xml failed due to '\t' character inside pom.xml
Dor B.D created JENKINS-15167 Parsing pom.xml failed due to \t character inside pom.xml Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 14/Sep/12 10:15 AM Description: Having '\t' escape code for tab inside pom.xml in case of maven project cause parsing error. As result, project can't be build, jenkins displays general parsing pom error. As solution i think: 1. More details description for this error would have help me and others. or 2. Ignoring this kind of characters inside the pom while parsing it and allow to build + displaying a warning that this character found inside the pom and should be fixed. Note: Local build without jenkins, only maven, worked fine, which means, parsing error is in jenkins. Due Date: 09/Sep/12 12:00 AM Project: Jenkins Priority: Minor Reporter: Dor B.D This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15155) Show total number of tests in test column
Fred G commented on JENKINS-15155 Show total number of tests in test column Sorry, I'm a bit confused about the use-case. If a test suite crashes I'd expect it to fail the build/test job, not carry on like nothing happened. What kind of test suite are you using? JUnit? Apart from that, I currently re-use the same Jelly-script that shows the test-result on the job page. So changing the output would require changes in Jenkins core. I'd like to avoid that, if possible. Would a tooltip showing the total number of tests on the test result column be sufficient or do you want to see the total number at a glance? Alternatively I could add another column that shows the total number of tests, but it seems a bit over the top. I'm open for other suggestions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15155) Show total number of tests in test column
Fred G assigned JENKINS-15155 to Sebastian Schuberth Show total number of tests in test column Change By: Fred G (14/Sep/12 10:58 AM) Assignee: FredG SebastianSchuberth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15155) Show total number of tests in test column
Sebastian Schuberth
commented on JENKINS-15155
Show total number of tests in test column
I'm running tests on Android, so yes, it's basically JUnit. The application under test contains native C++ code that's called via JNI. If there's an uncaught exception in native code, that will take down the Java process, too, and in fact even restart the VM. So there's actually no Java exception thrown in that case that JUnit could catch and report that test as failed. It simply terminates as if the whole test suite ran through.
I was also hoping this could be done without modifications to Jenkins core. On the other hand, I'm also missing the number of total tests on the job's project page ("Latest Test Result (3 failures / +2)"). Would it appear there, too, if you modified the Jelly script? If so, that would be a great solution solving to issues at a time.
A tooltip would be better than nothing, but as you've guessed the whole purpose of this feature is to see at a first glance whether all tests have been executed. If you're thinking about adding a separate columns for that, how about having separate columns for all of succeeded / failed / diff / total tests?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15168) Install without restart removes exec flag on jenkinsdata/plugins, thus failing plugin installations and upgrade
Adam Aquilon created JENKINS-15168 Install without restart removes exec flag on jenkinsdata/plugins, thus failing plugin installations and upgrade Issue Type: Bug Assignee: Unassigned Attachments: exec-flag-problem.txt Components: plugin Created: 14/Sep/12 11:27 AM Description: During upgrade of Jenkins, and when using the "Install without restart" button in pluginManager/available, something removes all executable flags on the "jenkinsdata/plugins" directory (and sometimes plugin subdirectories). For example from 775 to 664. This makes the plugin installation fail. The same seems to happen during upgrades, i.e. the plugins directory changes and then almost all plugin initializations fail (understandably). An example stackdump attached. Note that we have had these problems for a long time, at least since version 1.5xx. We've regularly tried upgrading to new versions but have seen these problems time and again. The only way I could make it repeatable was selecting a plugin (the Active Directory plugin in the example, but I think it could be just about any plugin) and selecting the "Install without restart". Shortly afterwards, the exec flags disappear and then the plugin installation fails. Unfortunately, the jenkins server is not accessible from the net, so no URL... Environment: Running 1.481 under Apache Tomcat/6.0.29 and JVM 1.6.0_18-b07 in SuSE Enterprise Server 11 64-bit Project: Jenkins Labels: plugin jenkins upgrade Priority: Major Reporter: Adam Aquilon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15155) Show total number of tests in test column
Fred G commented on JENKINS-15155 Show total number of tests in test column How about adding a little check after your tests, that compares the number of executed tests with the total number of tests and fails if it the numbers don't match? Yup, if I change the jelly code in core it also shows up on the job page. But... core changes would only affect newer versions of Jenkins, so users stuck on older version would not see it. Therefore changing code in the plug-in would be backwards-compatible and preferable. Maybe we can do both. I'm not sure about the right format of the string yet. How about "(3 failures/10 tests/ +2)"? Any suggestions? As horizontal space is always limited I'd always prefer one column that shows multiple values. I'll see if I can let the user configure it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15155) Show total number of tests in test column
Sebastian Schuberth commented on JENKINS-15155 Show total number of tests in test column Adding a check for the number of test on my side would only fix the problem for me, whereas fixing the issues in Jenkins helps others, too. So I prefer the latter. I usually update Jenkins regularly, so I would be OK with a core change as I would get that change soon anyway. I'm not sure how many users are stuck on an older Jenkins version but are able to update the plugin, thus I'm also not sure whether changing the code in the plugin really helps those users. Regarding the format, I'd prefer a slightly more human readable string like "3 of 10 failed (+2)". I'd also say "0 of 10 failed (±0)" instead of "no failures" if there were no failures. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15155) Show total number of tests in test column
Sebastian Schuberth assigned JENKINS-15155 to Fred G Show total number of tests in test column Change By: Sebastian Schuberth (14/Sep/12 12:32 PM) Assignee: SebastianSchuberth FredG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15169) Warning Plugin - Graph Configuration Error
Chris Engler created JENKINS-15169 Warning Plugin - Graph Configuration Error Issue Type: Bug Assignee: Ulli Hafner Components: analysis-collector, analysis-core, violations, warnings Created: 14/Sep/12 12:39 PM Description: Attempting to configure the trend graph results in http 404 page not found error. 1) Go to a job with trend grpahs displayed. 2) Click configure link (links to Jenkins Server/Job/warnings6/configure/?) 3) Click Save (links to Jenkins Server/Job/warnings6/configure/save) Versions installed Jenkins 1.481 Warnings 4.17 Static Code Analysis Plugin 1.47 Analysis Collector Plugin 1.33 Violations 0.7.11 Issues accesses Jenkins through the localhost path. Environment: windows xp Project: Jenkins Priority: Major Reporter: Chris Engler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15165) Using openjdk 6 to build jenkins from code failed
reddy k assigned JENKINS-15165 to reddy k Using openjdk 6 to build jenkins from code failed Change By: reddy k (14/Sep/12 12:47 PM) Assignee: reddyk This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15165) Using openjdk 6 to build jenkins from code failed
reddy k assigned JENKINS-15165 to Unassigned Using openjdk 6 to build jenkins from code failed Change By: reddy k (14/Sep/12 12:47 PM) Assignee: reddyk This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14762) Cobertura writes to source files (erasing contents in most cases)
Szilárd Pfeiffer commented on JENKINS-14762 Cobertura writes to source files (erasing contents in most cases) Same bug for me. Unable to this great plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14762) Cobertura writes to source files (erasing contents in most cases)
Szilárd Pfeiffer edited a comment on JENKINS-14762 Cobertura writes to source files (erasing contents in most cases) Same bug for me. Unable to use this great plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [JIRA] (JENKINS-15130) BuildTrigger ambiguous
This is an issue for me as well... All of my jobs that perform a post-build action of a parameterized build on another project are failing. Is there a known workaround until this is fixed? -- View this message in context: http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-15130-BuildTrigger-ambiguous-tp4639987p4640240.html Sent from the Jenkins issues mailing list archive at Nabble.com.
Re: [JIRA] (JENKINS-15130) BuildTrigger ambiguous
Status Code: 500 Exception: java.lang.IllegalArgumentException: BuildTrigger is ambiguous; matches both hudson.plugins.parameterizedtrigger.BuildTrigger and hudson.tasks.BuildTrigger Stacktrace: javax.servlet.ServletException: java.lang.IllegalArgumentException: BuildTrigger is ambiguous; matches both hudson.plugins.parameterizedtrigger.BuildTrigger and hudson.tasks.BuildTrigger at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at
[JIRA] (JENKINS-15132) Cannot use a single file name as module for retrieval in CVS Plugin version 2.5
Deepak Mahale edited a comment on JENKINS-15132 Cannot use a single file name as module for retrieval in CVS Plugin version 2.5 Michael: Thanks for prompt reply, I'm checking out from the following dir structure install mvbin pkginfo file2 file3 file4 file5 file6 mvbinpro pkginfo file2 file3 file4 file5 file6 parent2 child_dir grandchild_dir Configuration which works fine has module's as follows CVS Plugin Version 1.6 Module: install/mvbin/pkginfo install/mvbinpro/pkginfo parent2/child_dir/grandchild_dir NOTE: Whitespace separated list NOTE: It used to retrieve each pkginfo file in proper directory structure CVS Plugin Version 2.5 Module 1: install/mvbin Module 2: install/mvbinpro Module 3: parent2/child_dir/grandchild_dir NOTE: Here 'Module 3' checks out properly NOTE: In place of pkginfo file, i see pkginfo directories created for 'Module 1' 'Module 2' Configuration which doesn't work has module's as follows CVS Plugin Version 2.5 Module 1: install/mvbin/pkginfo Module 2: install/mvbinpro/pkginfo Module 3: parent2/child_dir/grandchild_dir As the mvbin and mvbinpro directories contain only a few files in my case, it doesn't make a big difference to checkout the directories, so i've used that as a workaround. But if all i need is one file from a directory containing 2,000 files, then it'll be a big loss in terms of efficiency and time. Thanks again Regards Deepak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15037) Option to consider only stable builds when calculating new warnings
David Pärsson commented on JENKINS-15037 Option to consider only stable builds when calculating new warnings It seems the CheckStyleResult computes the result of the build, compared to a reference build, before I'm able to set the boolean on the history in HealthAwarePublisher.perform(). I'm currently supplying the boolean flag to the BuildHistory constructor (via CheckStylePublisher and CheckStyleResult). I've created pull requests with my changes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15027) Cron expression 'H H * * *' does not work as advertised
Danny Yates commented on JENKINS-15027 Cron _expression_ H H * * * does not work as advertised Thanks. I haven't tried this yet, but it should definitely be in the documentation! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15048) Git Build Data menu items shows repo URL which kind of disturb the layout
markewaite commented on JENKINS-15048 Git Build Data menu items shows repo URL which kind of disturb the layout Yes, the fix should be in the next release of the git plugin, since the pull request was accepted and merged to the plugin source. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15170) SVN hangs after update. Performing thread dump a few times fixes.
first last created JENKINS-15170 SVN hangs after update. Performing thread dump a few times fixes. Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: after.log, before.log, prop.log Components: subversion Created: 14/Sep/12 3:39 PM Description: When Jenkins performs an SVN update it hangs indefinitely (12 hours or more) at "At revision ..." until I either to a jstack or navigate to jenkins/threadDump a few times. The thread dump right before and right after the hang is fixed are attached. It appears that it's possibly SVNKit and SVN 1.7 related? Environment: Centos 6 64bit Subversion 1.7.4 java version 1.7.0_05-icedtea OpenJDK Runtime Environment (rhel-2.2.1.el6_3-x86_64) OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode) Project: Jenkins Priority: Major Reporter: first last This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6268) Make checking for modification time of junit results be configurable and off by default
markewaite commented on JENKINS-6268 Make checking for modification time of junit results be configurable and off by default Unreliable clocks on build machines and on file systems which support build machines seem like they will create many more problems than these few that you've detected. If you have reliable clocks and are still seeing the issue, then you could consider the work around of adding a build step which updates the time stamp of the result files. The Linux command "touch" will update the time stamp of one or more files and similar commands are available for Windows and other platforms. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15171) The run button must respect the configured rights
Julien Carsique created JENKINS-15171 The run button must respect the configured rights Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: dry-run Created: 14/Sep/12 4:21 PM Description: The dry-run execution button is publicly accessible (for anonymous users) whereas anonymous users are not granted the Run right. On a public Jenkins instance, a dry-run is executed by indexing robots! Project: Jenkins Priority: Blocker Reporter: Julien Carsique This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15172) Dry run must not be counted as a build
Julien Carsique created JENKINS-15172 Dry run must not be counted as a build Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: dry-run Created: 14/Sep/12 4:27 PM Description: When a dry-run is executed: the lastSuccessfulBuild link is updated the build is considered as a "true" build and so, for instance, artifacts from the real lastSuccessfulBuild are deleted if the job is configured to keep only artifacts for one build. Those issue may be considered as a normal behavior but is it really useful? The link being updated could be kept. But it would be great if the artifacts deletion could be avoided. Project: Jenkins Priority: Minor Reporter: Julien Carsique This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14667) java.io.InvalidClassException
SCM/JIRA link daemon commented on JENKINS-14667 java.io.InvalidClassException Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/tools/JDKInstaller.java http://jenkins-ci.org/commit/jenkins/8a1b069a86a4282343047825487e43d767601f86 Log: FIXED JENKINS-14667 JDK installation failed on some slaves with InvalidClassException: hudson.tools.JDKInstaller$Platform$1; local class incompatible: … This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14667) java.io.InvalidClassException
SCM/JIRA link daemon resolved JENKINS-14667 as Fixed java.io.InvalidClassException Change By: SCM/JIRA link daemon (14/Sep/12 4:28 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14667) java.io.InvalidClassException
SCM/JIRA link daemon commented on JENKINS-14667 java.io.InvalidClassException Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/tools/JDKInstaller.java http://jenkins-ci.org/commit/jenkins/9b0e1fb6f6b94b5f2a4267fbf923b917f29ab968 Log: JENKINS-14667 Another case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15173) Valgrind plugin Valgrind Results link on project root page does not always link to the most recent build
David Ritter created JENKINS-15173 Valgrind plugin Valgrind Results link on project root page does not always link to the most recent build Issue Type: Bug Affects Versions: current Assignee: Johannes Ohlemacher Components: valgrind Created: 14/Sep/12 4:47 PM Description: We have noticed that the "Valgrind Results" link that is on the root Project page only links to the most recent unstable build. Because we set our thresholds to have any memory leak mark the build as a failure the root link never works (and we have to click down to the failed build to see the Valgrind results). Is this by design or a bug? Project: Jenkins Priority: Major Reporter: David Ritter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14667) java.io.InvalidClassException
dogfood commented on JENKINS-14667 java.io.InvalidClassException Integrated in jenkins_main_trunk #1928 FIXED JENKINS-14667 JDK installation failed on some slaves with InvalidClassException: hudson.tools.JDKInstaller$Platform$1; local class incompatible: … (Revision 8a1b069a86a4282343047825487e43d767601f86) Result = SUCCESS Jesse Glick : 8a1b069a86a4282343047825487e43d767601f86 Files : core/src/main/java/hudson/tools/JDKInstaller.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15003) Track and verify plugins mentioned in configuration XML
Jesse Glick commented on JENKINS-15003 Track and verify plugins mentioned in configuration XML Something like https://github.com/jenkinsci/cli-channel-demo/blob/master/src/main/java/org/jenkinsci/demo/cli/App.java (CLI.upgrade) could suffice for a convenient remote API, especially if the client were enhanced to automatically reconnect after a server restart. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15003) Track and verify plugins mentioned in configuration XML
Jesse Glick
updated JENKINS-15003
Track and verify plugins mentioned in configuration XML
Change By:
Jesse Glick
(14/Sep/12 5:45 PM)
Description:
Manyjobsorothermodelobjectsrequirecertainplugins.Thisshouldberepresentedintheactual{{config.xml}},e.g.{code:xml}buildersorg.jenkinsci.plugins.hello.HelloWorldBuilderplugin=hello1.5idiosyncraticConfig//org.jenkinsci.plugins.hello.HelloWorldBuilder/builders{code}(XMLnamespaceswouldinsomewaysbenaturalforthis,butXStreamprobablyismorecomfortablewithasimpleattributeontheoutermostelement“owned”byaplugin.)Needtomake{{XmlFile.write}}inserttheseattributesasitserializesconfiguration,perhapsbymakingittakesomeinterfaceimplementedby{{PluginManager}}mapping{{Class}}to{{StringshortName}}×{{Stringversion}}.{{JRubyXStreamConverter}}mightbeusedforinspiration.{{onLoad}}caneitherignoretheseattributes,orusethemashints—forexample,silentlyignoringdeserializationfailuresfromasectionownedbyapluginwhichisnotcurrentlyloaded.Webmethodslike{{doCreateItem}}and{{doConfigDotXml}},andtheircorrespondingJavamethodslike{{createProjectFromXML}}and{{updateByXml}},canbeleftalone,butacallerneedssomewayoffirstcheckingwhetherallrequiredpluginsarepresent,andattemptingtoinstallthemifnot.Sothereneedstobeawebmethodon{{Jenkins}}andacorrespondingJavamethodwhichcanbegivenanarbitraryXMLfileandwillreturn:#OK,ifallpluginsmentionedthereinarepresent.(Perhapsalsocheckversions.)#Asecurityerror,ifcallerismissing{{ADMINISTER}}permission.#Oralistofjobsgivenas{{UpdateCenterJob.id}}(introducedin{{a3e57da}})indicatingongoingprogressofinstalling(orupdating?)plugins,andperhapsevenrestartingJenkins(trackableasof{{
a3e57da
4bd0696
}})forthosepluginswhichrequireit.Mayalsowantsomehigher-levelconvenienceinterface,e.g.inCLI,tovalidateXMLandwaitforallupdatecenterjobstocomplete
(includingrestartasof{{9ae0ba0}})
.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14667) java.io.InvalidClassException
dogfood commented on JENKINS-14667 java.io.InvalidClassException Integrated in jenkins_main_trunk #1929 JENKINS-14667 Another case. (Revision 9b0e1fb6f6b94b5f2a4267fbf923b917f29ab968) Result = UNSTABLE Jesse Glick : 9b0e1fb6f6b94b5f2a4267fbf923b917f29ab968 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
[JIRA] (JENKINS-15174) Timeout option not retrieved correctly
Daniel Piorkowski created JENKINS-15174 Timeout option not retrieved correctly Issue Type: Bug Assignee: zregvart Attachments: timeout_snapshot.JPG Components: xvfb Created: 14/Sep/12 6:31 PM Description: 1. When configuring a project and looking at the advanced options for Xvfb, under Timeout in seconds, enter 5. 2. Save and then navigate back to the project configuration page. 3. Observe the Timeout in seconds is now 5000 (assuming for 5000 milliseconds). 4. Keep the timeout at 5000, save again, and navigate back to the project configuration page. 5. Observe the Timeout in seconds is now 500. This presents a problem because after initially setting the timeout to X seconds, it will be reset to X * 1000 seconds when returning and saving the configuration page. This results in Xvfb apparently hanging when it is really just waiting for the timeout to complete. Project: Jenkins Priority: Major Reporter: Daniel Piorkowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15071) Editing the describtion of Jobs throws an Error 500 message
ThiagoC commented on JENKINS-15071 Editing the describtion of Jobs throws an Error 500 message Same problem here - Caused by: java.lang.NullPointerException at org.jenkinsci.lib.envinject.EnvInjectAction.writeReplace(EnvInjectAction.java:62) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15003) Track and verify plugins mentioned in configuration XML
Jesse Glick commented on JENKINS-15003 Track and verify plugins mentioned in configuration XML To find the list of update jobs using the remote API: curl -g 'http://localhost:8080/updateCenter/api/json?prettytree=jobs[id,type,status[type],plugin[name,version]]' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15071) Editing the describtion of Jobs throws an Error 500 message
ThiagoC edited a comment on JENKINS-15071 Editing the describtion of Jobs throws an Error 500 message Same problem here: [M2Release] marking build to keep until the next release build [M2Release] removing keep build from build 75 ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.maven.MavenModuleSetBuild at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:167) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:135) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:130) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:120) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:94) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:68) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:78) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:63) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:98) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:38) at com.thoughtworks.xstream.XStream.marshal(XStream.java:840) at com.thoughtworks.xstream.XStream.marshal(XStream.java:829) at com.thoughtworks.xstream.XStream.toXML(XStream.java:804) at hudson.XmlFile.write(XmlFile.java:173) at hudson.model.Run.save(Run.java:1574) at hudson.model.Run.keepLog(Run.java:1809) at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$2.tearDown(M2ReleaseBuildWrapper.java:226) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:817) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) at hudson.model.Run.run(Run.java:1438) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: com.thoughtworks.xstream.converters.reflection.ObjectAccessException: Could not call org.jenkinsci.plugins.envinject.EnvInjectBuilder$1.writeReplace() : null at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:70) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:88) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:68) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:78) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:63) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:55) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:68) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:78) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:176) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:163) ... 22 more Caused by: java.lang.NullPointerException at org.jenkinsci.lib.envinject.EnvInjectAction.writeReplace(EnvInjectAction.java:62) at sun.reflect.GeneratedMethodAccessor451.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:66) ... 32 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15003) Track and verify plugins mentioned in configuration XML
Jesse Glick
commented on JENKINS-15003
Track and verify plugins mentioned in configuration XML
To prevalidate a job:
curl -i -d @config.xml http://localhost:8080/pluginManager/prevalidateConfig
and note the X-Jenkins-Session for later. To track its progress:
(while :; do curl -ig 'http://localhost:8080/updateCenter/api/json?prettytree=jobs[id,type,status[type],plugin[name,version]]'; sleep 1; done)
Initially all plugins will show e.g.
{
"id" : 1,
"type" : "InstallationJob",
"status" : {
"type" : "Pending"
},
"plugin" : {
"name" : "htmlpublisher",
"version" : "1.0"
}
}
but when done they will show
{
"id" : 1,
"type" : "InstallationJob",
"status" : {
"type" : "Success"
},
"plugin" : {
"name" : "htmlpublisher",
"version" : "1.0"
}
}
If you see "SuccessButRequiresRestart" then you must
curl -d '' http://localhost:8080/updateCenter/safeRestart
and then poll on
curl -I 'http://localhost:8080/'
or (more efficiently) any …/api/… such as
curl -i 'http://localhost:8080/updateCenter/api/json?tree=none'
until you get a 200 status with a new X-Jenkins-Session indicating that the server has restarted.
Now you may actually use the XML:
curl -d @/tmp/config.xml -H 'Content-Type: text/xml' 'http://localhost:8080/createItem?name=newjob'
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15003) Track and verify plugins mentioned in configuration XML
Jesse Glick commented on JENKINS-15003 Track and verify plugins mentioned in configuration XML https://github.com/jenkinsci/jenkins/pull/566 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15003) Track and verify plugins mentioned in configuration XML
Jesse Glick resolved JENKINS-15003 as Fixed Track and verify plugins mentioned in configuration XML https://github.com/jenkinsci/jenkins/commit/e1b7ac281b93b7afa33056d59da987e9542a05e4 Change By: Jesse Glick (14/Sep/12 10:10 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8149) Git submodule fetch uses (incorrect) parent refspec
Jørgen Tjernø assigned JENKINS-8149 to Jørgen Tjernø Git submodule fetch uses (incorrect) parent refspec Change By: Jørgen Tjernø (15/Sep/12 12:25 AM) Assignee: EricAnderson JørgenTjernø This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8149) Git submodule fetch uses (incorrect) parent refspec
Jørgen Tjernø started work on JENKINS-8149 Git submodule fetch uses (incorrect) parent refspec Change By: Jørgen Tjernø (15/Sep/12 12:25 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8149) Git submodule fetch uses (incorrect) parent refspec
Jørgen Tjernø commented on JENKINS-8149 Git submodule fetch uses (incorrect) parent refspec Just bit me too, I'm investigating a potential fix now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8149) Git submodule fetch uses (incorrect) parent refspec
Jørgen Tjernø commented on JENKINS-8149 Git submodule fetch uses (incorrect) parent refspec Fix (pending verification) lives at https://github.com/jenkinsci/git-plugin/pull/96 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
