[JIRA] (JENKINS-12966) gitTool crashes Jenkins startup
domi updated JENKINS-12966 gitTool crashes Jenkins startup Change By: domi (20/Nov/12 7:19 AM) Component/s: git Component/s: core This message is automatically generated by JIRA. 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-12966) gitTool crashes Jenkins startup
domi edited a comment on JENKINS-12966 gitTool crashes Jenkins startup Please have a go with the newest version 2.5.1 and let me know if it fixes the issues for you. The plugin git-server is a required dependency 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-15276) Store Groovy Scripts into a local VCS
domi commented on JENKINS-15276 Store Groovy Scripts into a local VCS please try with 2.5.1 and let me know This message is automatically generated by JIRA. 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-12966) gitTool crashes Jenkins startup
domi assigned JENKINS-12966 to domi gitTool crashes Jenkins startup Change By: domi (20/Nov/12 7:00 AM) Assignee: Nicolas De Loof domi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12966) gitTool crashes Jenkins startup
domi commented on JENKINS-12966 gitTool crashes Jenkins startup please have a go with the newest version 2.5.1 and let me know if it fixes the issues for you. This message is automatically generated by JIRA. 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-15869) Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor
dogfood commented on JENKINS-15869 Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor Integrated in jenkins_main_trunk #2086 [FIXED JENKINS-15869] When running on Java 5, must still load DiskSpaceMonitor/TemporarySpaceMonitor, even though they will show N/A. (Revision 8ad62f77cb429a49318444fad2191d0e08857ca6) JENKINS-15869 reverting the change. (Revision 6465ba0f8386fcdef22d2f523357f3024dafd57b) [FIXED JENKINS-15869] (Revision 5eada311c640663a2dbe40c69a7257e80be9ffca) Result = SUCCESS Jesse Glick : 8ad62f77cb429a49318444fad2191d0e08857ca6 Files : changelog.html core/src/main/java/hudson/node_monitors/TemporarySpaceMonitor.java core/src/main/java/hudson/node_monitors/DiskSpaceMonitor.java core/src/main/resources/hudson/node_monitors/Messages.properties kohsuke : 6465ba0f8386fcdef22d2f523357f3024dafd57b Files : changelog.html core/src/main/java/hudson/node_monitors/DiskSpaceMonitor.java core/src/main/resources/hudson/node_monitors/Messages.properties core/src/main/java/hudson/node_monitors/TemporarySpaceMonitor.java kohsuke : 5eada311c640663a2dbe40c69a7257e80be9ffca Files : core/src/main/java/hudson/model/ComputerSet.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-15860) Mail body for two simultaneous mails get mixed
Xavier Nodet updated JENKINS-15860 Mail body for two simultaneous mails get mixed Change By: Xavier Nodet (20/Nov/12 6:39 AM) Attachment: configs_and_template.tar.gz This message is automatically generated by JIRA. 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-15732) Duplicated / multiple "Jenkins CLI" entries under "Manage Jenkins"
dogfood commented on JENKINS-15732 Duplicated / multiple "Jenkins CLI" entries under "Manage Jenkins" Integrated in jenkins_main_trunk #2085 [Bug fix for JENKINS-15732] - updated correct displayname and description for SystemInfo and SystemLog (Revision 7a4ae612ba0a4f57604e97247d08d8f349953900) Result = SUCCESS kannan : 7a4ae612ba0a4f57604e97247d08d8f349953900 Files : core/src/main/java/jenkins/management/SystemLogLink.java core/src/main/java/jenkins/management/SystemInfoLink.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-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
Akhil Mittal commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Just letting you know that even with 'Show all CVS Output' ticked on CVS plugin 2.7 no change log is displayed, however with 2.4 it displays the change log if 'Show all CVS Output' is ticked. I haven't checked 2.5 & 2.6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15860) Mail body for two simultaneous mails get mixed
Slide-O-Mix commented on JENKINS-15860 Mail body for two simultaneous mails get mixed You may want to remove the email addresses from the xml files... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15860) Mail body for two simultaneous mails get mixed
Slide-O-Mix commented on JENKINS-15860 Mail body for two simultaneous mails get mixed If the log doesn't have any useful information, don't worry about 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-15874) Add the url to the build in the status message
Phil Rumble created JENKINS-15874 Add the url to the build in the status message Issue Type: Improvement Affects Versions: current Assignee: Phil Rumble Components: lotus-connections Created: 20/Nov/12 2:42 AM Description: Please add the url to the build results in the status message. Environment: all Project: Jenkins Priority: Minor Reporter: Phil Rumble This message is automatically generated by JIRA. 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-15854) github-sqs-plugin amazon sns
Andrei Pozolotin commented on JENKINS-15854 github-sqs-plugin amazon sns Aaron: thanks for considering this. yes, you are right, I expect to use SNS -> SQS subscriptions but for audit trail purposes I also want to deliver github push to SNS -> email or http subscriptions in other words, notification chain is like this: 1. github -> SNS 2. SNS -> SQS 3. SNS -> http post 4. SNS -> email send 5. SQS -> jenkins pull am I making sense? This message is automatically generated by JIRA. 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-15871) Maven Release Plugin doesn't properly escape user's passwords during release
teilo resolved JENKINS-15871 as Duplicate Maven Release Plugin doesn't properly escape user's passwords during release JENKINS-14781 Change By: teilo (20/Nov/12 1:12 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15873) Build ICONs are "broken" for Anonymous user when given read access
Frank Merrow created JENKINS-15873 Build ICONs are "broken" for Anonymous user when given read access Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 20/Nov/12 12:42 AM Description: If Anonymous user is given read permissions to Jenkins, build ICONS will appear as broken or missing links. This issue also occurs if security is set to "Logged in user can do anything". Note that there is a full and complete description of the problem including screen shots in my jenkins-user posting which can be found here: http://jenkins.361315.n4.nabble.com/Problems-with-quot-Authorization-quot-configuration-td4645920.html#a4646198 Note that the problem seems to be partially fixed in 1.490 in that the "login" ICON now appears, but the Build Status ICONS remain broken. See jenkins-user posting for more information. Environment: Windows, LDAP, Maxtix Security Project: Jenkins Labels: jenkins Priority: Major Reporter: Frank Merrow This message is automatically generated by JIRA. 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-15854) github-sqs-plugin amazon sns
Aaron Walker commented on JENKINS-15854 github-sqs-plugin amazon sns Just to clarify what your after you want to be able to trigger a build using the github amazonsns service. The whole goal of the SQS plugin was to allow you to trigger builds where the Jenkins server sits behind the firewall SNS requires you to configure a deliver mechanism HTTP,email,SMS even SQS. Really the only transport I see working is SQS itself since HTTP support would mean opening up your Jenkins instance to the Internet which is already support by the GitHub Web Hook. I'll test support for using SNS where it's bridged to SQS and make the changes to support this mechanism. Does that solve your use 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-15319) Failure starting slave nodes
vinz r commented on JENKINS-15319 Failure starting slave nodes I also encounter the same problem. Any update on this? Thanks, Vinz This message is automatically generated by JIRA. 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-15583) "building" builds (running builds) do not show up anymore in the list of builds of a job (json API)
janick reynders
commented on JENKINS-15583
"building" builds (running builds) do not show up anymore in the list of builds of a job (json API)
I finally got some time to look around in the source code. It is caused by the changes for 1.485.
/**
* Gets the read-only view of all the builds.
*
* @return never null. The first entry is the latest build.
*/
@Exported(name="allBuilds",visibility=-2)
@WithBridgeMethods(List.class)
public RunList getBuilds() {
return RunList.fromRuns(_getRuns().values());
}
/**
* Gets the read-only view of the recent builds.
*
* @since 1.485
*/
@Exported(name="builds")
public RunList getNewBuilds() {
return getBuilds().newBuilds();
}
The getBuilds() method used to be annotated with @Exported() and the getNewBuilds() method did not exist. getBuilds().newBuilds() filters out running builds on purpose:
/**
* Reduce the size of the list by only leaving relatively new ones.
* This also removes on-going builds, as RSS cannot be used to publish information
* if it changes.
*/
public RunList newBuilds() { ... }
I don't know if this should still be considered a bug, since it looks like it is intended behaviour.
I can fix my code by asking for the (hidden) allBuilds property in the REST API.
This message is automatically generated by JIRA.
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-15249) Missing support for externals in 1.4.2 for subversion working copy version 1.7
Tom Wickert commented on JENKINS-15249 Missing support for externals in 1.4.2 for subversion working copy version 1.7 This still happens with 1.4.3. If the check-out strategy is use SVN update as much as possible, the externals do not get updated. This message is automatically generated by JIRA. 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-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
Akhil Mittal commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Yep I have raised JENKINS-15872 for that now, any update on this one. This message is automatically generated by JIRA. 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-15872) Running 'rlog' after 'cvs up -r TAG' superfluous & giving incorrect change log for the workspace
Akhil Mittal created JENKINS-15872 Running 'rlog' after 'cvs up -r TAG' superfluous & giving incorrect change log for the workspace Issue Type: Bug Assignee: Unassigned Components: cvs Created: 19/Nov/12 9:36 PM Description: Is running 'rlog' after 'cvs up -r TAG' ok? Don't think so If you are selecting 'Location' as Tag e.g. Location : Tag Tag Name : DEV cvs commands run by Jenkins will be something like cvs update -d -r DEV blah_module cvs rlog -S -d'19 Nov 2012 11:43:30 +1100<19 Nov 2012 11:47:37 +1100' blah_module What if the tag DEV on component/module has not moved but several versions are committed to cvs? In this case what's happening is your workspace is not changed & still has got the old components with 'DEV' tag revisions however change log will show the committed changes 'cos of rlog. I'll try to explain 1. Notice foo.bar 'DEV' tag is not at head cvs log srcmgr/test/someDir/foo.bar | egrep 'head:|DEV:' head: 1.15 DEV: 1.5 2. I committed a change cvs commit -m 'test' srcmgr/test/someDir/foo.bar Checking in srcmgr/test/someDir/foo.bar; /cvs/srcmgr/test/someDir/foo.bar,v <-- foo.bar new revision: 1.16; previous revision: 1.15 3. Notice that even though I have committed a change but my tag 'DEV' is not moved at all cvs log srcmgr/test/someDir/foo.bar | egrep 'head:|DEV:' head: 1.16 DEV: 1.5 4. Now my Jenkins settings is 'Location: tag', 'tag: DEV' & 'Update: ticked' Run Jenkins Building in workspace /export/home/amittal/temp cvs update -d -P -r DEV srcmgr cvs update: Updating srcmgr cvs update: Updating srcmgr/adhoc cvs update: Updating srcmgr/cm cvs update: Updating srcmgr/cm/bin cvs update: Updating srcmgr/logs cvs update: Updating srcmgr/test cvs update: Updating srcmgr/test/createSomeLongPathDirAveryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVerylongpathDirectory cvs update: Updating srcmgr/test/someDir cvs rlog -S -d19 Nov 2012 15:42:34 +1100<19 Nov 2012 15:51:08 +1100 srcmgr cvs rlog: Logging srcmgr cvs rlog: Logging srcmgr/adhoc cvs rlog: Logging srcmgr/cm cvs rlog: Logging srcmgr/cm/bin cvs rlog: Logging srcmgr/logs cvs rlog: Logging srcmgr/test cvs rlog: Logging srcmgr/test/createSomeLongPathDirAveryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVerylongpathDirectory cvs rlog: Logging srcmgr/test/someDir [temp] $ /bin/sh -xe /var/tmp/hudson5023473001197182858.sh + pwd /export/home/amittal/temp Notifying upstream projects of job completion Finished: SUCCESS 5. Jenkins displayed the committed change in the change log Changes Summary test amittal: test 1.16 srcmgr/test/someDir/foo.bar cat changelog.xml 2012-11-19 04:49:26
[JIRA] (JENKINS-15860) Mail body for two simultaneous mails get mixed
Xavier Nodet updated JENKINS-15860 Mail body for two simultaneous mails get mixed I attached the two config files, and the template used to generate the mail. I'm sorry... Could you please be more specific as to what log file you'd like? I looked at https://[myserver]/log/all, but it didn't get far enough in the past. The logs I found in .hudson were mostly related to launching the slaves, or cleaning workspace, etc. One more comment... In addition to being executed at the same time, both jobs in this issue executed on the same Linux slave. I hope this helps. Change By: Xavier Nodet (19/Nov/12 9:02 PM) Attachment: configs_and_template.tar.gz This message is automatically generated by JIRA. 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-15869) Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor
SCM/JIRA link daemon commented on JENKINS-15869 Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/ComputerSet.java http://jenkins-ci.org/commit/jenkins/5eada311c640663a2dbe40c69a7257e80be9ffca Log: [FIXED JENKINS-15869] revisiting the fix by vetting the deserialized NodeMonitors to make sure they are valid. Compare: https://github.com/jenkinsci/jenkins/compare/8ad62f77cb42...5eada311c640 This message is automatically generated by JIRA. 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-15869) Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor
SCM/JIRA link daemon commented on JENKINS-15869 Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/node_monitors/DiskSpaceMonitor.java core/src/main/java/hudson/node_monitors/TemporarySpaceMonitor.java core/src/main/resources/hudson/node_monitors/Messages.properties http://jenkins-ci.org/commit/jenkins/6465ba0f8386fcdef22d2f523357f3024dafd57b Log: JENKINS-15869 reverting the change. "When running on Java 5, must still load DiskSpaceMonitor/TemporarySpaceMonitor, even though they will show N/A." This reverts commit 8ad62f77cb429a49318444fad2191d0e08857ca6. This message is automatically generated by JIRA. 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-15871) Maven Release Plugin doesn't properly escape user's passwords during release
herque created JENKINS-15871 Maven Release Plugin doesn't properly escape user's passwords during release Issue Type: Bug Affects Versions: current Assignee: teilo Components: m2release Created: 19/Nov/12 8:27 PM Description: One of our users had '$$' as part of their password which was causing the release to fail with the below: The svn command failed. Command output: svn: Commit failed (details follow): svn: OPTIONS of 'http://myrepo/mysource': authorization failed: Could not authenticate to server: rejected Basic challenge (http://myrepo) They had no problem committing directly to svn (through tortoise and eclipse) or browsing the directory with a browser. Once their password was changed to have no '$'s in it, the release process worked normally. Environment: RHEL 6 and tomcat 7 Project: Jenkins Labels: plugin 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
[JIRA] (JENKINS-15869) Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor
Jesse Glick commented on JENKINS-15869 Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor Still not consistently reproducible, but may be necessary to run using Java 6+ before running on Java 5, presumably to populate $JENKINS_HOME/nodeMonitors.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
[JIRA] (JENKINS-15869) Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor
SCM/JIRA link daemon commented on JENKINS-15869 Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/node_monitors/DiskSpaceMonitor.java core/src/main/java/hudson/node_monitors/TemporarySpaceMonitor.java core/src/main/resources/hudson/node_monitors/Messages.properties http://jenkins-ci.org/commit/jenkins/8ad62f77cb429a49318444fad2191d0e08857ca6 Log: [FIXED JENKINS-15869] When running on Java 5, must still load DiskSpaceMonitor/TemporarySpaceMonitor, even though they will show N/A. Returning null from an @Extension method does not seem to work reliably, and is not supported by SezPoz. If desirable to hide a monitor column in $server/computer/, add a boolean isEnabled() method interpretable in Jelly. This message is automatically generated by JIRA. 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-15869) Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor
SCM/JIRA link daemon resolved JENKINS-15869 as Fixed Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor Change By: SCM/JIRA link daemon (19/Nov/12 7:12 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-15045) Support Github commit status API
Juan Muller commented on JENKINS-15045 Support Github commit status API @Nicolas, your branch looks good. I am with @david in that it would definitely help our work-flow. Will you create a pull request for this 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
[JIRA] (JENKINS-15869) Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor
Jesse Glick commented on JENKINS-15869 Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor Causes http://localhost:8080/computer/ to crash with a 500 error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15869) Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor
Jesse Glick commented on JENKINS-15869 Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor Cannot consistently reproduce. Also when building from sources rather than using a released WAR I get bogus errors such as Nov 19, 2012 1:47:33 PM hudson.ExtensionFinder$Sezpoz scout WARNING: Failed to scout hudson.scm.MailAddressResolverImpl java.lang.InstantiationException: file:…/plugins/cvs/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: hudson.scm.MailAddressResolverImpl at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:646) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:290) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.size(ExtensionList.java:157) at java.util.AbstractCollection.isEmpty(AbstractCollection.java:78) at hudson.model.queue.QueueSorter.installDefaultQueueSorter(QueueSorter.java:47) 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:592) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:875) 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(ThreadPoolExecutor.java:651) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.ClassNotFoundException: hudson.scm.MailAddressResolverImpl at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:783) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 24 more which may or may not be related. This message is automatically generated by JIRA. 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-15869) Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor
Jesse Glick commented on JENKINS-15869 Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor DiskSpaceMonitor.install and TemporarySpaceMonitor.install are returning null on Java 5, but apparently this is not preventing NodeMonitor.all() from listing them. This message is automatically generated by JIRA. 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-15870) Build trigger message in output has wrong link for downstream job
chad davis created JENKINS-15870 Build trigger message in output has wrong link for downstream job Issue Type: Bug Assignee: Praqma Support Components: logging Created: 19/Nov/12 6:32 PM Description: On the console output, when the job reports which other jobs were triggered, the link is broken. This is specifically in a case where I customized the port number Jenkins is running on. I changed it to 8081, but these links still have 8080 in them. Other than that they are fine. Project: Jenkins Priority: Minor Reporter: chad davis This message is automatically generated by JIRA. 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-15197) Add support for Maven toolchains configuration file
SCM/JIRA link daemon commented on JENKINS-15197 Add support for Maven toolchains configuration file Code changed in jenkins User: Olivier Lamy Path: src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesAction.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesRunListener.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ManagedFileUtil.java src/main/java/org/jenkinsci/plugins/configfiles/custom/CustomConfig.java src/main/java/org/jenkinsci/plugins/configfiles/groovy/GroovyScript.java src/main/java/org/jenkinsci/plugins/configfiles/maven/GlobalMavenSettingsConfig.java src/main/java/org/jenkinsci/plugins/configfiles/maven/MavenSettingsConfig.java src/main/java/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig.java src/main/java/org/jenkinsci/plugins/configfiles/xml/XmlConfig.java src/main/resources/org/jenkinsci/plugins/configfiles/Messages.properties src/main/resources/org/jenkinsci/plugins/configfiles/Messages_fr.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail.jelly src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail_fr.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/toolchains-tpl.xml http://jenkins-ci.org/commit/config-file-provider-plugin/aac2af9b779b4574b68cfe189182e4b90d091630 Log: Merge pull request #3 from jeffmaury/JENKINS-15197 JENKINS-15197 Add support for Maven toolchains config files Thanks ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14914) Errors in hudson-dev:run relating to config-file-provider
SCM/JIRA link daemon commented on JENKINS-14914 Errors in hudson-dev:run relating to config-file-provider Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/plugins/configfiles/maven/job/MvnGlobalSettingsProvider.java src/main/java/org/jenkinsci/plugins/configfiles/maven/job/MvnSettingsProvider.java src/main/resources/org/jenkinsci/plugins/configfiles/maven/job/MvnGlobalSettingsProvider/config.jelly src/main/resources/org/jenkinsci/plugins/configfiles/maven/job/MvnGlobalSettingsProvider/help.html src/main/resources/org/jenkinsci/plugins/configfiles/maven/job/MvnSettingsProvider/config.jelly src/main/resources/org/jenkinsci/plugins/configfiles/maven/job/MvnSettingsProvider/help.html http://jenkins-ci.org/commit/config-file-provider-plugin/65715a76822a2598d24d7a032853b8635fa46e46 Log: [FIXED JENKINS-14914] migrate to new EP from core and change dependency direction between maven-maven and config file provider This message is automatically generated by JIRA. 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-15197) Add support for Maven toolchains configuration file
SCM/JIRA link daemon commented on JENKINS-15197 Add support for Maven toolchains configuration file Code changed in jenkins User: Jeff MAURY Path: src/main/java/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig.java src/main/resources/org/jenkinsci/plugins/configfiles/Messages.properties src/main/resources/org/jenkinsci/plugins/configfiles/Messages_fr.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail.jelly src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail_fr.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/toolchains-tpl.xml http://jenkins-ci.org/commit/config-file-provider-plugin/8f6240a98a16cd433640e69056885219a1f424fe Log: JENKINS-15197 Add support for Maven toolchains config files This message is automatically generated by JIRA. 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-13533) Maven build fails on CleanTempFilesAction#tempFiles serialization
SCM/JIRA link daemon commented on JENKINS-13533 Maven build fails on CleanTempFilesAction#tempFiles serialization Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesAction.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesRunListener.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ConfigFileBuildWrapper.java http://jenkins-ci.org/commit/config-file-provider-plugin/535ad2ac7129f8d5141d32577b50b06ac91e35e0 Log: [FIXED JENKINS-13533] Maven build fails on CleanTempFilesAction#tempFiles serialization This message is automatically generated by JIRA. 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-15219) Invalid markup generated when template cannot be loaded for Maven settings file
SCM/JIRA link daemon commented on JENKINS-15219 Invalid markup generated when template cannot be loaded for Maven settings file Code changed in jenkins User: Jeff MAURY Path: src/main/java/org/jenkinsci/plugins/configfiles/maven/AbstractMavenSettingsProvider.java http://jenkins-ci.org/commit/config-file-provider-plugin/97df09fd7938aaecb1ea4ede01aceff113809848 Log: JENKINS-15219 Invalid markup generated when template cannot be loaded for Maven settings file This message is automatically generated by JIRA. 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-12823) Clean up temporary config files at the very end, not before post-build
SCM/JIRA link daemon commented on JENKINS-12823 Clean up temporary config files at the very end, not before post-build Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesAction.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesRunListener.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ConfigFileBuildWrapper.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ManagedFileUtil.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ManagedFilesEnvironment.java http://jenkins-ci.org/commit/config-file-provider-plugin/4236d26f52fdf42a4555a83f1e72cd62d3e0d716 Log: [FIXED JENKINS-12823] Clean up temporary config files at the very end, not before post-build This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10770) In Maven Project, copy config files runs AFTER pre-Build Steps provided by M2 Extra Steps Plugin
SCM/JIRA link daemon commented on JENKINS-10770 In Maven Project, copy config files runs AFTER pre-Build Steps provided by M2 Extra Steps Plugin Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ConfigFileBuildWrapper.java http://jenkins-ci.org/commit/config-file-provider-plugin/97d97e937a95b4b73c6ca250c1267e0900eb64a2 Log: JENKINS-10770: define ordinal for wrapper higher as the for m2extrasteps This message is automatically generated by JIRA. 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-15045) Support Github commit status API
Reto Kaiser commented on JENKINS-15045 Support Github commit status API I agree with @David on the functionality. When you create a pull request, Github will show the status for every push in it (http://i.imgur.com/PZot3.png). @Nicolas: I looked at the code - looks like a generic Notifier, so this should work for all builds right? I this planned to go into the 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-15869) Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor
Jesse Glick created JENKINS-15869 Java 5 compat: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor Issue Type: Bug Assignee: Jesse Glick Components: core Created: 19/Nov/12 6:19 PM Description: Errors are thrown starting Jenkins on Java 5: Nov 19, 2012 1:18:07 PM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running Nov 19, 2012 1:18:12 PM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.model.LoadStatistics$LoadStatisticsUpdater@1031310 failed java.lang.AssertionError: class hudson.node_monitors.DiskSpaceMonitor is missing its descriptor at jenkins.model.Jenkins.getDescriptorOrDie(Jenkins.java:1120) at hudson.node_monitors.NodeMonitor.getDescriptor(NodeMonitor.java:83) at hudson.node_monitors.NodeMonitor.getDescriptor(NodeMonitor.java:67) at hudson.util.DescribableList.get(DescribableList.java:123) at hudson.model.ComputerSet.(ComputerSet.java:392) at hudson.model.OverallLoadStatistics.computeTotalExecutors(OverallLoadStatistics.java:63) at hudson.model.LoadStatistics.updateExecutorCounts(LoadStatistics.java:188) at hudson.model.LoadStatistics$LoadStatisticsUpdater.doRun(LoadStatistics.java:226) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Nov 19, 2012 1:18:17 PM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.triggers.Trigger$2@1c5a33b failed java.lang.NoClassDefFoundError at hudson.triggers.Trigger$2.doRun(Trigger.java:298) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Nov 19, 2012 1:18:22 PM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.model.LoadStatistics$LoadStatisticsUpdater@1031310 failed java.lang.NoClassDefFoundError at hudson.model.OverallLoadStatistics.computeTotalExecutors(OverallLoadStatistics.java:63) at hudson.model.LoadStatistics.updateExecutorCounts(LoadStatistics.java:188) at hudson.model.LoadStatistics$LoadStatisticsUpdater.doRun(LoadStatistics.java:226) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Environment: tested in 1.466.x, 1.480.1 Project: Jenkins Labels: java5 Priority: Critical Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10593) Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL
Joe Hansche commented on JENKINS-10593 Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL Thanks, didn't know about that. However, it appears that is only available in the CloudBees Jenkins Enterprise package, which is not free and must be installed as a separate Jenkins installation. It's also not part of the CloudBees Free Enterprise Plugin that is available in the update center. This solution isn't as feature-rich as CloudBees's, of course But it does solve the one-off use case when an administrator just wants to restrict a single job to a smaller subset of users than the rest of the instance is configured to allow. Though I may consider revising this once more just to make sure that only an "overall administrator" can enable the option – so that non-administrator users who have access to configure the job cannot lock out the instance administrators unwittingly. This message is automatically generated by JIRA. 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-14914) Errors in hudson-dev:run relating to config-file-provider
SCM/JIRA link daemon commented on JENKINS-14914 Errors in hudson-dev:run relating to config-file-provider Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/plugins/configfiles/maven/job/MvnGlobalSettingsProvider.java src/main/java/org/jenkinsci/plugins/configfiles/maven/job/MvnSettingsProvider.java src/main/resources/org/jenkinsci/plugins/configfiles/maven/job/MvnGlobalSettingsProvider/config.jelly src/main/resources/org/jenkinsci/plugins/configfiles/maven/job/MvnGlobalSettingsProvider/help.html src/main/resources/org/jenkinsci/plugins/configfiles/maven/job/MvnSettingsProvider/config.jelly src/main/resources/org/jenkinsci/plugins/configfiles/maven/job/MvnSettingsProvider/help.html http://jenkins-ci.org/commit/config-file-provider-plugin/369811ef3a2e549bb54cc7bbfc7114b6b9d62989 Log: [FIXED JENKINS-14914] migrate to new EP from core and change dependency direction between maven-maven and config file provider This message is automatically generated by JIRA. 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-15868) Cannot archive big remote log files using "Archive the artifacts" post-build action
david catalan created JENKINS-15868 Cannot archive big remote log files using "Archive the artifacts" post-build action Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: postbuild-task Created: 19/Nov/12 4:54 PM Description: Using "Archive the artifacts" post-build action, the following kind of issues often occurs: 12:11:29 Archiving artifacts 12:11:29 ERROR: Failed to archive artifacts: testing/logs/** 12:11:29 hudson.util.IOException2: java.io.IOException: request to write '2134' bytes exceeds size in header of '852381' bytes for entry 'testing/error.log' 12:11:29 at hudson.FilePath.copyRecursiveTo(FilePath.java:1863) 12:11:29 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116) 12:11:29 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 12:11:29 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:807) 12:11:29 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:782) 12:11:29 at hudson.model.Build$BuildExecution.post2(Build.java:183) 12:11:29 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:729) 12:11:29 at hudson.model.Run.execute(Run.java:1541) 12:11:29 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) 12:11:29 at hudson.model.ResourceController.execute(ResourceController.java:88) 12:11:29 at hudson.model.Executor.run(Executor.java:236) 12:11:29 Caused by: java.util.concurrent.ExecutionException: java.io.IOException: request to write '2134' bytes exceeds size in header of '852381' bytes for entry 'testing/error.log' 12:11:29 at hudson.remoting.Channel$4.adapt(Channel.java:697) 12:11:29 at hudson.remoting.Channel$4.adapt(Channel.java:692) 12:11:29 at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) 12:11:29 at hudson.FilePath.copyRecursiveTo(FilePath.java:1861) 12:11:29 ... 10 more 12:11:29 Caused by: java.io.IOException: request to write '2134' bytes exceeds size in header of '852381' bytes for entry 'testing/error.log' 12:11:29 at hudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284) 12:11:29 at hudson.util.io.TarArchiver.visit(TarArchiver.java:115) 12:11:29 at hudson.util.DirScanner$Glob.scan(DirScanner.java:133) 12:11:29 at hudson.FilePath.writeToTar(FilePath.java:1899) 12:11:29 at hudson.FilePath.access$1000(FilePath.java:166) 12:11:29 at hudson.FilePath$36.invoke(FilePath.java:1840) 12:11:29 at hudson.FilePath$36.invoke(FilePath.java:1837) 12:11:29 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2308) 12:11:29 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 12:11:29 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 12:11:29 at hudson.remoting.Request$2.run(Request.java:326) 12:11:29 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 12:11:29 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 12:11:29 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 12:11:29 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 12:11:29 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 12:11:29 at java.lang.Thread.run(Thread.java:662) Please notice that during the same run, other log files are correctly archived. I haven't found any possible reason so far. Could such issue happen if we try to archive a file which is still being written? Is this post-build task the correct one to use to save log files? Thanks for your help, David. Due Date: 23/Nov/12 12:00 AM Project: Jenkins Priority: Major Reporter: david catalan
[JIRA] (JENKINS-4951) JUnit report doesn't distinguish between test failures and errors
Jesse Glick commented on JENKINS-4951 JUnit report doesn't distinguish between test failures and errors https://github.com/jenkinsci/jenkins/pull/623 I guess the document [1] mentioned above is quite old and now obsolete; the junit.org web site contains a lot of cruft. JUnit 4 does not treat test failures and errors distinctly. Nonetheless distinguishing VM crashes from Java-generated exceptions/errors is potentially useful. It does treat ignored tests specially; unfortunately Ant does not currently report these at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15841) tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V
Jan Mnisi
updated JENKINS-15841
tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V
Change By:
Jan Mnisi
(19/Nov/12 4:29 PM)
Description:
Hi.We get the following error running tests on Jenkins.{noformat}Xvfb starting$ Xvfb :1 -screen 0 1152x900x8 -fbdir /home/tomcat/.hudson/2012-11-16_11-25-053509576821944113109xvfbParsing POMsXvfb stoppingFATAL: tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V from class hudson.maven.MavenModuleSetBuild$RunnerImpljava.lang.IllegalAccessError: tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V from class hudson.maven.MavenModuleSetBuild$RunnerImpl at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:646) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1516) at hudson.model.Run.run(Run.java:1462) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:487) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236){noformat}Here is our set-up. Jenkins version: 1.490The Jenkins.war was renamed to Hudson.war and overwrote the Hudson.war one we had within tomcat. That allowed is to retain all the jobs we have now, including the ones that we build with maven but have no screens/windows.We also have XVFB installed on the master, which is a RHL 4 box (Nahant).And we use the latest XVFB plugin, VERSION 1.0.6 (NoV 05, 2012, required core dependencies = 1.398)The tests are Webdriver Java tests. Maven is used for building. The Pom gives no issues when we run tests locally. Below is what we have in the Pom, very few dependencies.{code}4.0.0ourGroupIdourArtifactId1jarorg.apache.maven.pluginsmaven-compiler-plugin2.5.11.71.7maven-failsafe-plugin2.12.3integration-testverifypertesttruejunitjunit4.10jarcompileorg.seleniumhq.seleniumselenium-java2.25.0org.easytestingfest-assert1.4testcom.intellijannotations9.0.4joda-timejoda-time2.1org.seleniumhq.seleniumselenium-server2.25.0jarcompile org.seleniumhq.selenium selenium-remote-driver 2.25.0 jar compile {code}
I am running Maven 3.0.4, and that's what I have in the path.
Please help.Jan
This message is automatically generated by JIRA.
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-10593) Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL
Jesse Glick commented on JENKINS-10593 Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL Just FYI, the Role-Based Access Control plugin in Jenkins Enterprise by CloudBees offers this functionality. This message is automatically generated by JIRA. 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-15867) wrong tab selected on http://jenkins-ci.org/stable-rc page
Piotr Wilkosz created JENKINS-15867 wrong tab selected on http://jenkins-ci.org/stable-rc page Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: www Created: 19/Nov/12 4:15 PM Description: This is just a really minor thing. While visiting http://jenkins-ci.org/stable-rc page, the selected tab is "Release". As http://jenkins-ci.org/stable-rc page refers to LTS Release I would expect that selected tab should be: "Long-Term Support Release". Due Date: 19/Nov/12 12:00 AM Environment: none Fix Versions: current Project: Jenkins Labels: www documentation Priority: Trivial Reporter: Piotr Wilkosz This message is automatically generated by JIRA. 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-15866) wrong version for LTE release displayed on http://jenkins-ci.org/
Piotr Wilkosz created JENKINS-15866 wrong version for LTE release displayed on http://jenkins-ci.org/ Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: www Created: 19/Nov/12 4:06 PM Description: Please visit http://jenkins-ci.org/ and then click on Long-Term Support Release tab. The displayed version is 1.466.2 that links to http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war. Today (2012-11-19) link http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war resolves to version 1.480.1. Maybe the content of the main webpage could be generated automatically based on content of http://mirrors.jenkins-ci.org/. Due Date: 19/Nov/12 12:00 AM Environment: none Fix Versions: current Project: Jenkins Labels: documentation www Priority: Trivial Reporter: Piotr Wilkosz This message is automatically generated by JIRA. 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-15367) Jenkins kicks off the wrong downstream builds for Maven
Larry Shatzer, Jr. commented on JENKINS-15367 Jenkins kicks off the wrong downstream builds for Maven This was committed after the 1.491 RC branch was created, and was not backported into the RC branch unfortunately. It will be in 1.492. This message is automatically generated by JIRA. 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-15864) multi-configuration project ignores slave setting
c089 commented on JENKINS-15864 multi-configuration project ignores slave setting After I used "mark this node as temporarilly offline" on the windows slaves, the job successfully built on the master, but as soon as one was up, it's back on the windows node... This message is automatically generated by JIRA. 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-15865) Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin
Andrew Jones updated JENKINS-15865 Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin Change By: Andrew Jones (19/Nov/12 3:18 PM) Attachment: jenkins-npe.tar.bz2 This message is automatically generated by JIRA. 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-15865) Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin
Andrew Jones created JENKINS-15865 Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven2 Created: 19/Nov/12 3:15 PM Description: Jenkins build fails with "[ERROR] FATAL ERROR" if you build a Maven 2 project that uses maven-failsafe-plugin. Steps to reproduce: 1. Create a new job in Jenkins 2. Specify Maven2/3 job 3. Choose Git in source code management 4. Specify https://github.com/ahjones/broken-failsafe-maven as the repo 5. Choose Maven 2.2.1 as the Maven version. 6. Save the build 7. Click build. Expected behaviour: The build completes Actual behaviour: The build doesn't complete. The relevant portion of the console output is: [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137) at org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56) at hudson.maven.agent.ComponentConfiguratorFilter.configureComponent(ComponentConfiguratorFilter.java:49) at hudson.maven.agent.PluginManagerInterceptor$MojoIntercepter.configureComponent(PluginManagerInterceptor.java:146) at org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1357) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:724) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:468) at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) 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:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWor
[JIRA] (JENKINS-15836) Slave's Name should be trimmed of spaces at the beginning and end of the Name on Save
sogabe updated JENKINS-15836 Slave's Name should be trimmed of spaces at the beginning and end of the Name on Save chnage component to "core". Change By: sogabe (19/Nov/12 3:09 PM) Assignee: Peter Hayes Component/s: core Component/s: dashboard-view This message is automatically generated by JIRA. 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-12847) Downstream build view updates when job chain changes
David Liu commented on JENKINS-12847 Downstream build view updates when job chain changes I have exactly the same issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15732) Duplicated / multiple "Jenkins CLI" entries under "Manage Jenkins"
sogabe resolved JENKINS-15732 as Fixed Duplicated / multiple "Jenkins CLI" entries under "Manage Jenkins" Change By: sogabe (19/Nov/12 2:55 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15732) Duplicated / multiple "Jenkins CLI" entries under "Manage Jenkins"
SCM/JIRA link daemon commented on JENKINS-15732 Duplicated / multiple "Jenkins CLI" entries under "Manage Jenkins" Code changed in jenkins User: Kannan Manickam Path: core/src/main/java/jenkins/management/SystemInfoLink.java core/src/main/java/jenkins/management/SystemLogLink.java http://jenkins-ci.org/commit/jenkins/7a4ae612ba0a4f57604e97247d08d8f349953900 Log: [Bug fix for JENKINS-15732] - updated correct displayname and description for SystemInfo and SystemLog This message is automatically generated by JIRA. 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-15732) Duplicated / multiple "Jenkins CLI" entries under "Manage Jenkins"
SCM/JIRA link daemon commented on JENKINS-15732 Duplicated / multiple "Jenkins CLI" entries under "Manage Jenkins" Code changed in jenkins User: Seiji Sogabe Path: core/src/main/java/jenkins/management/SystemInfoLink.java core/src/main/java/jenkins/management/SystemLogLink.java http://jenkins-ci.org/commit/jenkins/01479e2bbc2176706741949284cbae6816d0fe9b Log: Merge pull request #607 from arangamani/JENKINS-15732_fix [Bug fix for JENKINS-15732] - updated correct displayname and descriptio... Compare: https://github.com/jenkinsci/jenkins/compare/d32f9e511371...01479e2bbc21 This message is automatically generated by JIRA. 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-15367) Jenkins kicks off the wrong downstream builds for Maven
Arnaud Héritier commented on JENKINS-15367 Jenkins kicks off the wrong downstream builds for Maven The problem always exists in 1.491 To reproduce add these 2 projects in your jenkins : https://github.com/vietj/chromattic https://github.com/vietj/wikbook Wikbook builds will trigger chromattic builds while chromattic uses a released version of wikbook This message is automatically generated by JIRA. 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-15864) multi-configuration project ignores slave setting
rsandell assigned JENKINS-15864 to Unassigned multi-configuration project ignores slave setting Nothing to do with the multi-slave-config plugin. Change By: rsandell (19/Nov/12 2:19 PM) Assignee: rsandell This message is automatically generated by JIRA. 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-15864) multi-configuration project ignores slave setting
rsandell updated JENKINS-15864 multi-configuration project ignores slave setting Change By: rsandell (19/Nov/12 2:18 PM) Component/s: multi-slave-config This message is automatically generated by JIRA. 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-15842) Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Ray Cuadra commented on JENKINS-15842 Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1 Thank you so much, you guys rock! This message is automatically generated by JIRA. 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-15864) multi-configuration project ignores slave setting
c089 commented on JENKINS-15864 multi-configuration project ignores slave setting It even uses the same slave all the 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-15002) Parameterized trigger passes no parameters from Ivy Prioject
reeve lau commented on JENKINS-15002 Parameterized trigger passes no parameters from Ivy Prioject My setup: Ivy Plugin : version 1.21 Jenkins Parameterized Trigger plugin : version 2.16 Jenkins : version 1.489 Ivy job triggers a parameterized free-style job => the free-style job get only default param values Ivy job triggers a parameterized Ivy job => the Ivy job get only default param values Free-style job triggers a parameterized free-style job => the downstream free-style job get all param values Free-style job triggers a parameterized Ivy job => the downstream Ivy job get all param values I hope this issue could be 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-15864) multi-configuration project ignores slave setting
c089 created JENKINS-15864 multi-configuration project ignores slave setting Issue Type: Bug Affects Versions: current Assignee: rsandell Components: master-slave, multi-slave-config Created: 19/Nov/12 1:50 PM Description: After upgrading from 1.488 to 1.491 (could not test the others because of a bug with mercurial) one of our builds started to fail. It is a multi-config build with two axes, one of which is a workaround to get the "restrict where the project can be built" functionality which is not available for multi-config builds. It is a "Slaves" axis with only the Jenkins master node selected. However, the project always seems to be built on a windows node which doesn't even have mercurial installed. Project: Jenkins Priority: Major Reporter: c089 This message is automatically generated by JIRA. 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-12966) gitTool crashes Jenkins startup
wernight commented on JENKINS-12966 gitTool crashes Jenkins startup It seems that installing the new dependency "Git Server Plugin" fixes this issue along with "FileBackedHttpGitRepository" exception. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15860) Mail body for two simultaneous mails get mixed
Slide-O-Mix commented on JENKINS-15860 Mail body for two simultaneous mails get mixed Also, log output. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15860) Mail body for two simultaneous mails get mixed
Slide-O-Mix commented on JENKINS-15860 Mail body for two simultaneous mails get mixed Please upload the config.xml for each job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14583) Build number history is shared by different jobs
Bruce Adams commented on JENKINS-14583 Build number history is shared by different jobs I note that when I create a new job from an existing one the build history remains visible on the right hand side even if a new workspace is defined. Could this be the cause or at least related? This message is automatically generated by JIRA. 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-15863) OOME using fitness plugin
Nicolas De Loof created JENKINS-15863 OOME using fitness plugin Issue Type: Bug Assignee: Unassigned Components: fitnesse Created: 19/Nov/12 12:37 PM Description: Fitnesse plugin is storing large documents in memory, along with the rest of the build data. This really needs to be stored in a file and streamed/processed on the fly when needed to avoid unnecessary memory consumption and OOME. Project: Jenkins Priority: Major Reporter: Nicolas De Loof This message is automatically generated by JIRA. 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-15402) NPE in hudson.plugins.templateproject.ProxySCM.requiresWorkspaceForPolling(ProxySCM.java:124)
Rainer Burgstaller resolved JENKINS-15402 as Duplicate NPE in hudson.plugins.templateproject.ProxySCM.requiresWorkspaceForPolling(ProxySCM.java:124) caused by JENKINS-15861 Change By: Rainer Burgstaller (19/Nov/12 12:35 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
aleksas commented on JENKINS-13790 Subversion externals fail This issue also causes workspace cleanup failure when "Emulate clean checkout" is used. Seams to keep the old files intact. This message is automatically generated by JIRA. 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-15402) NPE in hudson.plugins.templateproject.ProxySCM.requiresWorkspaceForPolling(ProxySCM.java:124)
Rainer Burgstaller commented on JENKINS-15402 NPE in hudson.plugins.templateproject.ProxySCM.requiresWorkspaceForPolling(ProxySCM.java:124) In fact, this issue is caused by JENKINS-15861. This message is automatically generated by JIRA. 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-15862) perforce session ticket is not always parsed correctly
Tim Mason updated JENKINS-15862 perforce session ticket is not always parsed correctly Change By: Tim Mason (19/Nov/12 12:19 PM) Description: The perforce plugin does not always parse the session ticket from "p4 login -p" correctly, causing the job to fail.I noticed this when using the coverity plugin in combination with the perforce plugin. The coverity plugin causes some extra text to be emitted from the "p4 login -p" command, which seems to confuse the parser in the perforce plugin.Example of the extra text:timm@daxtsmtf02> cov-build --dir foo p4 login -pEnter password: 53637D707C9CB35CF2436B90972121A0[WARNING] No files were emitted. This may be due to a problem with your configurationor because no files were actually compiled by your build command.Please make sure you have configured the compilers actually used in the compilation. For more details, please look at: /home/timm/foo/build-log.txttimm@daxtsmtf02>When this happens in Jenkins, it looks like the perforce plugin is just taking the last line of output (instead of the second line) as the session ticket. Example from Jenkins console log:[workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 workspace -o MTFRA_ME_static_analysis[workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 login -p[workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 -P "/userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp/build-log.txt" workspace -o MTFRA_ME_static_analysisCaught exception communicating with perforce. Perforce password (P4PASSWD) invalid or unset.com.tek42.perforce.PerforceException: Perforce password (P4PASSWD) invalid or unset.I managed to workaround this problem by adding an option the coverity plugin which suppress the output of the extra text. But it is not ideal as the extra text is actually a warning message which might be useful at other stages in the build, and I have to suppress it for all stages.Note: there is a related ticket open against the coverity plugin (JENKINS-14834) which says the coverity plugin should not be active during the pre-build steps. If that was fixed, it would resolve this issue. But I opened this ticket for the perforce plugin as I think an improvement in the way the perforce plugin gets the session ticker ticket would be a good change to make. This message is automatically generated by JIRA. 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-15862) perforce session ticket is not always parsed correctly
Tim Mason created JENKINS-15862 perforce session ticket is not always parsed correctly Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: perforce Created: 19/Nov/12 12:15 PM Description: The perforce plugin does not always parse the session ticket from "p4 login -p" correctly, causing the job to fail. I noticed this when using the coverity plugin in combination with the perforce plugin. The coverity plugin causes some extra text to be emitted from the "p4 login -p" command, which seems to confuse the parser in the perforce plugin. Example of the extra text: timm@daxtsmtf02> cov-build --dir foo p4 login -p Enter password: 53637D707C9CB35CF2436B90972121A0 [WARNING] No files were emitted. This may be due to a problem with your configuration or because no files were actually compiled by your build command. Please make sure you have configured the compilers actually used in the compilation. For more details, please look at: /home/timm/foo/build-log.txt timm@daxtsmtf02> When this happens in Jenkins, it looks like the perforce plugin is just taking the last line of output (instead of the second line) as the session ticket. Example from Jenkins console log: [workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 workspace -o MTFRA_ME_static_analysis [workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 login -p [workspace] $ cov-build --dir /userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp p4 -P "/userspace/timm/jenkins/jenkinsHome/coverity/temp-1900101495130713288.tmp/build-log.txt" workspace -o MTFRA_ME_static_analysis Caught exception communicating with perforce. Perforce password (P4PASSWD) invalid or unset.com.tek42.perforce.PerforceException: Perforce password (P4PASSWD) invalid or unset. I managed to workaround this problem by adding an option the coverity plugin which suppress the output of the extra text. But it is not ideal as the extra text is actually warning message which might be useful at other stages in the build, and I have to suppress it for all stages. Note: there is a related ticket open against the coverity plugin (JENKINS-14834) which says the coverity plugin should not be active during the pre-build steps. If that was fixed, it would resolve this issue. But I opened this ticket for the perforce plugin as I think an improvement in the way the perforce plugin gets the session ticker would be a good change to make. Environment: RedHat EL 5.5 Project: Jenkins Priority: Major Reporter: Tim Mason This message is automatically generated by JIRA. 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-15861) SCMTrigger runs with anonymous authentication
Rainer Burgstaller created JENKINS-15861 SCMTrigger runs with anonymous authentication Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 19/Nov/12 12:13 PM Description: I have a matrix based security setup where "authenticated" can do everything and anonymous can do nothing. In addition, I am using the template-project-plugin. In such a configuration polling the SCM will fail due to Hudson.getItem() returning null. The reason for that is that the authentication of the SCMTrigger.run method is null and therefore, jenkins assumes that this user is unauthenticated (anonymous) and therefore, does not have any permissions whatsoever. ERROR: Failed to record SCM polling for java.lang.NullPointerException: project is null, at hudson.plugins.templateproject.ProxySCM.requiresWorkspaceForPolling(ProxySCM.java:179) at hudson.model.AbstractProject._poll(AbstractProject.java:1417) at hudson.model.AbstractProject.poll(AbstractProject.java:1387) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Whether this is a bug in ProxySCM (and therefore the template plugin) or whether this is a general problem is hard for me to tell. I was able to work around the problem by giving "Job/read" permission to "anonymous" but IMHO the SCMTrigger should run as SYSTEM. Project: Jenkins Priority: Major Reporter: Rainer Burgstaller This message is automatically generated by JIRA. 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-10061) http:///pluginManager/checkUpdates does not work without GUI / javascript
Reto Kaiser commented on JENKINS-10061 http:///pluginManager/checkUpdates does not work without GUI / _javascript_ Here's another workaround, if you have access to jenkin's home-directory: curl -L http://updates.jenkins-ci.org/update-center.json | sed '1d;$d' > /var/lib/jenkins/updates/default.json via https://gist.github.com/1026918 This message is automatically generated by JIRA. 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-13069) add information about job deletion to All Configuration History
Kathi Stutz resolved JENKINS-13069 as Fixed add information about job deletion to All Configuration History Feature included in version 2.0 (Nov 19, 2012) Change By: Kathi Stutz (19/Nov/12 11:45 AM) Status: Open Resolved Fix Version/s: current 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-15860) Mail body for two simultaneous mails get mixed
Xavier Nodet created JENKINS-15860 Mail body for two simultaneous mails get mixed Issue Type: Bug Assignee: Slide-O-Mix Components: email-ext Created: 19/Nov/12 11:31 AM Description: When email-ext has to send two emails, from two different jobs failing at the same time, the same body appears in the two emails. The subjects are correct. This morning, two unrelated jobs started and failed at exactly the same moment: the build date/time is the same, down to the second. They both lasted a quarter of a second. Both triggered a 'Failure' mail. The two subjects in the mails were different, as expected. But the mails had the same body. The body was correct for one job (i.e. it's not two bodies mixed, it's two copies of the same body that is fine for one of the jobs). A lock missing when generating the mails? Environment: Jenkins 1.456, email-ext 2.24.1 Project: Jenkins Priority: Critical Reporter: Xavier Nodet This message is automatically generated by JIRA. 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-15820) JClouds plugin deadlock
onemanbucket commented on JENKINS-15820 JClouds plugin deadlock The deadlock seems to occur when running both EC2-plugin and jclouds plugin (on separate clouds). This message is automatically generated by JIRA. 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-15859) Multiple patterns for job authorizations
Dridi Boukelmoune created JENKINS-15859 Multiple patterns for job authorizations Issue Type: Improvement Affects Versions: current Assignee: Daniel Petisme Components: role-strategy Created: 19/Nov/12 10:50 AM Description: Sometimes we need to define several unrelated projects to a team, each project having several jobs. One solution is to duplicate the groups which we want to avoid, and the other is to have a single group with a slightly more complex regexp. Another solution could be multiple patterns: ^build_my_first_project_.* ^test_my_first_project_.* ^build_the_second_one_.* ^test_the_second_one_.* Instead of: ^(build|test)_(my_first_project_|the_second_one_).* Not everyone in the team is comfortable with (even simple) regular expressions, so we could trade a bit of duplication for readability. I stole the idea from this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Build+Blocker+Plugin#BuildBlockerPlugin-Howtouse Environment: jenkins 1.466.1 role-strategy 1.1.2 Project: Jenkins Labels: role multiple pattern Priority: Major Reporter: Dridi Boukelmoune This message is automatically generated by JIRA. 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-9616) Revert configuration to an older version
Kathi Stutz commented on JENKINS-9616 Revert configuration to an older version Release was done today, finally. Version 2.0 This message is automatically generated by JIRA. 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-14866) Extra requirement of having output files break TestNG integration and create complex implementation
Christopher Orr edited a comment on JENKINS-14866 Extra requirement of having output files break TestNG integration and create complex implementation In fact, looking at the example you posted in your comment, it seems that the ATTACHMENT part isn't on its own line – it's at the end of the line starting with "1746". Try inserting a newline before the ATTACHMENT part. This message is automatically generated by JIRA. 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-14866) Extra requirement of having output files break TestNG integration and create complex implementation
Christopher Orr commented on JENKINS-14866 Extra requirement of having output files break TestNG integration and create complex implementation In fact, looking at the example you posted in your commend, it seems that the ATTACHMENT part isn't on its own line – it's at the end of the line starting with "1746". Try inserting a newline before the ATTACHMENT part. This message is automatically generated by JIRA. 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-15858) Jenkinks UI blocking on some calls
Arnaud Héritier commented on JENKINS-15858 Jenkinks UI blocking on some calls Same thing on my side : https://gist.github.com/4109900 (1.491) This message is automatically generated by JIRA. 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-15858) Jenkinks UI blocking on some calls
olamy updated JENKINS-15858 Jenkinks UI blocking on some calls Change By: olamy (19/Nov/12 10:01 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15858) Jenkinks UI blocking on some calls
Arnaud Héritier edited a comment on JENKINS-15858 Jenkinks UI blocking on some calls Same thing on my side : https://gist.github.com/4109911 (1.491) This message is automatically generated by JIRA. 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-15858) Jenkinks UI blocking on some calls
Vincent Massol created JENKINS-15858 Jenkinks UI blocking on some calls Issue Type: Bug Assignee: Peter Hayes Components: core, dashboard-view Created: 19/Nov/12 9:59 AM Description: I've noticed issues with jenkins being blocked for several minutes in recent versions (even before 1.490, it started probably like 10 versions in the past). Here's thread dump showing such deadlocks: https://gist.github.com/4109900 Note that my home page is using the dashboard and several threads are blocked on: at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:638) - waiting to lock <0x5e3afde0> (a hudson.model.RunMap) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:621) at jenkins.model.lazy.AbstractLazyLoadRunMap.getById(AbstractLazyLoadRunMap.java:498) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:472) at hudson.model.AbstractProject.getNearestOldBuild(AbstractProject.java:1025) at hudson.maven.MavenModuleSetBuild.getModuleLastBuilds(MavenModuleSetBuild.java:434) at hudson.maven.MavenModuleSetBuild.getResult(MavenModuleSetBuild.java:189) at hudson.model.Run.getIconColor(Run.java:640) at hudson.plugins.view.dashboard.stats.StatBuilds.getBuildStat(StatBuilds.java:50) Project: Jenkins Priority: Major Reporter: Vincent Massol This message is automatically generated by JIRA. 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-15858) Jenkinks UI blocking on some calls
Vincent Massol updated JENKINS-15858 Jenkinks UI blocking on some calls Change By: Vincent Massol (19/Nov/12 10:00 AM) Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14866) Extra requirement of having output files break TestNG integration and create complex implementation
Christopher Orr commented on JENKINS-14866 Extra requirement of having output files break TestNG integration and create complex implementation The "redirectTestOutputToFile" option is a Maven feature; nothing to do with Jenkins? The attachments syntax definitely does work. However the parser is currently pretty strict, and requires that each ATTACHMENT line has no extra whitespace at the start or end, and there must be a newline after each attachment. Could that be where you're having problems? If so, this should be improved once pull request #1 gets merged. Otherwise, can you provide a minimal XML file where you see a failure to show attachments? This message is automatically generated by JIRA. 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-15857) Parse Exception with Java7 and Emma 2.2.0
Flavio Donzé commented on JENKINS-15857 Parse Exception with Java7 and Emma 2.2.0 Link to forum post: http://www.eclipse.org/forums/index.php?t=rview&goto=986116 Link to issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=368042 This message is automatically generated by JIRA. 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-15857) Parse Exception with Java7 and Emma 2.2.0
Flavio Donzé created JENKINS-15857 Parse Exception with Java7 and Emma 2.2.0 Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: coverage_report.zip Components: emma Created: 19/Nov/12 8:42 AM Description: We are using Jenkins and Buckminster to build our product, about half a year ago we updated to java7 since then emma did not work anymore. Because the buckminster emma extension was outdated, used emma (1.4.x). After I reported in the forum, buckminster updated emma to version 2.2.0. I now get the following exception even though the xml looks fine (to me). Maybe this is caused by the update to java7 or emma 2.2.0. Attached is the coverage report. Emma: looking for coverage reports in the provided path: output/coverage_report.xml Emma: found 1 report files: C:\Data\Jenkins\workspace\workspace\scodi.server.integration\output\coverage_report.xml Emma: stored 1 report files in the build folder: C:\Data\Jenkins\workspace\jobs\scodi.server.integration\builds\2012-11-19_09-05-45\emma ERROR: Publisher hudson.plugins.emma.EmmaPublisher aborted due to exception hudson.util.IOException2: Failed to parse C:\Data\Jenkins\workspace\workspace\scodi.server.integration\output\coverage_report.xml at hudson.plugins.emma.EmmaBuildAction.load(EmmaBuildAction.java:243) at hudson.plugins.emma.EmmaPublisher.perform(EmmaPublisher.java:150) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1541) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: org.xmlpull.v1.XmlPullParserException: expected START_TAG or END_TAG not END_DOCUMENT (position: END_DOCUMENT seen .. @1:5408806) at org.xmlpull.mxp1.MXParser.nextTag(MXParser.java:1083) at hudson.plugins.emma.EmmaBuildAction.loadRatios(EmmaBuildAction.java:269) at hudson.plugins.emma.EmmaBuildAction.load(EmmaBuildAction.java:241) ... 10 more Environment: Java7,buckminster4.2,Jenkins1.491 Project: Jenkins Priority: Major Reporter: Flavio Donzé This message is automatically generated by JIRA. 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-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
Michael Clarke commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Sorry, but that last comment isn't relevant to this issue. If you're having a problem with additional items appearing in your changelist then open another issue for it so I can make sure your case gets reviewed properly. This message is automatically generated by JIRA. 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-14545) Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname
hiteswar kumar commented on JENKINS-14545 Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname Can you please consider this fix in coming release of this plugin. and can you please share next release schedule and bug fixes included? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
