[JIRA] (JENKINS-15514) Backup 'userContents' folder is missing help
cowwoc created JENKINS-15514 Backup 'userContents' folder is missing help Issue Type: Bug Affects Versions: current Assignee: Thomas Fürer Components: thinBackup Created: 13/Oct/12 5:02 AM Description: If you click the question-mark for option "Backup 'userContents' folder" you will get: "ERROR: Failed to load help file: Not Found" Fix Versions: current Project: Jenkins Priority: Trivial Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15437) ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization
Grant Limberg updated JENKINS-15437 ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization Change By: Grant Limberg (13/Oct/12 4:45 AM) Component/s: gui This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15437) ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization
glimberg commented on JENKINS-15437 ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization Just to add a bit more detail to the issue I'm running up against. I'm using Project-based Matrix Authorization Strategy with the Unix user/group database security realm. I have 3 groups of users. The access configuration can be seen here: http://i.imgur.com/YiIMr.png The jenkins-user group is given access to jobs on a job-by-job basis. An example job matrix auth strategy for a project the 'jenkins-user' group has access to can be seen here: http://i.imgur.com/UW1ZK.png. Now, if I add a view (any view but the All view) to Jenkins that contains a single project that doesn't have the "Job Read" access level checked for a member of the jenkins-user group, the jenkins-user group member gets the error as described above. If all jobs in a view have the "Job Read" acces level checked for the jenkins-user group, then all is fine and the view loads as expected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15437) ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization
glimberg updated JENKINS-15437 ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization Change By: glimberg (13/Oct/12 4:20 AM) Component/s: core Component/s: view-job-filters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15437) ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization
glimberg commented on JENKINS-15437 ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization My mistake. I think I miscategorized the component for this case. The issue I'm dealing with is in the normal dashboard views. I'm not using the view-job-filters 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-15437) ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization
Jacob Robertson commented on JENKINS-15437 ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization I cannot reproduce this. Can you give me some more exact steps. Also, are you using the view-job-filters 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-15401) support TODO directive to not fail such tests
Michael Prokop commented on JENKINS-15401 support TODO directive to not fail such tests Hi Bruno, this sounds fantastic Thanks for taking care! regards, Michael This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15513) Invalid .ipa file
Gemma Barlow created JENKINS-15513 Invalid .ipa file Issue Type: Improvement Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ios-device-connector Created: 12/Oct/12 10:06 PM Description: Hi Kohuske, iOS Plugin is great - thankyou. Following your request for feedback, I'd make the following suggestions: Allowing the user to select from a drop-down list of connected devices (or 'recently connected' devices?) by name rather than having to specify a UDID specifically (can get tedious copying and pasting this from the 'Connected Devices' view) OR Allowing the user to set a default such as 'Connected iPhone' + iOS Version or 'Connected iPad' + iOS Version for installation purposes. Support for .app files in addition to .ipa would be handy Would also be a good idea to allow deletion of the .ipa / .app prior to installation via Jenkins (checkbox?). Cheers, Gemma Project: Jenkins Priority: Major Reporter: Gemma Barlow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15494) Uncaught TypeError: Cannot read property 'firstChild' of null
dogfood commented on JENKINS-15494 Uncaught TypeError: Cannot read property 'firstChild' of null Integrated in jenkins_main_trunk #2000 [FIXED JENKINS-15494] Uncaught TypeError: Cannot read property 'firstChild' of null (Revision 8dbee911c39343c3085a4f56f6e597719ba0c0ca) Result = SUCCESS Jesse Glick : 8dbee911c39343c3085a4f56f6e597719ba0c0ca Files : changelog.html war/src/main/webapp/scripts/hudson-behavior.js This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15512) HTTPBuilder for Groovy Post Build
bootstraponline
created JENKINS-15512
HTTPBuilder for Groovy Post Build
Issue Type:
New Feature
Affects Versions:
current
Assignee:
wolfs
Components:
groovy-postbuild
Created:
12/Oct/12 9:18 PM
Description:
@Grab(group='org.codehaus.groovy.modules.http-builder', module='http-builder', version='0.5.2' )
def http = new groovyx.net.http.HTTPBuilder('http://www.codehaus.org')
causes:
java.lang.NoClassDefFoundError: org/apache/ivy/core/report/ResolveReport
Is there a way to use HTTPBuilder with groovy post build?
Project:
Jenkins
Priority:
Major
Reporter:
bootstraponline
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15511) NPE from PluginManager
dogfood commented on JENKINS-15511 NPE from PluginManager Integrated in jenkins_main_trunk #1999 [FIXED JENKINS-15511] NPE from PluginManager. (Revision eb18f080bb7e1842ee8031c6a8e6c665e527badf) Result = SUCCESS Jesse Glick : eb18f080bb7e1842ee8031c6a8e6c665e527badf Files : changelog.html core/src/main/java/hudson/PluginManager.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-15499) HistoryWidget/entry.jelly throws NullPointerException
Richard Mortimer commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException There is/was a critical bug or two in 1.485 related to the lazy loading. See JENKINS-15465 and JENKINS-15439. I'm pretty sure that those are the issues that you are seeing. Kohsuke backported the fixes to the 1.486 release candidate build. You can download a pre-release build from https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_rc_branch/279/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15419) TAP published results hide JUnit published results
SCM/JIRA link daemon resolved JENKINS-15419 as Fixed TAP published results hide JUnit published results Change By: SCM/JIRA link daemon (12/Oct/12 8:12 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15419) TAP published results hide JUnit published results
Bruno P. Kinoshita started work on JENKINS-15419 TAP published results hide JUnit published results Change By: Bruno P. Kinoshita (12/Oct/12 8:12 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15419) TAP published results hide JUnit published results
SCM/JIRA link daemon commented on JENKINS-15419 TAP published results hide JUnit published results Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/TapTestResultAction.java http://jenkins-ci.org/commit/tap-plugin/5b7a8947d60718924b3327ce33ce3353456247d2 Log: [FIXED JENKINS-15419] Using a different URL and display name for the TAP Test Result action. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15419) TAP published results hide JUnit published results
Bruno P. Kinoshita commented on JENKINS-15419 TAP published results hide JUnit published results Hmm, nice catch. The plug-in was overriding the testReport URL bound. Although the JUnit report was there, you couldn't access it because you would be redirected to the TAP report. Will push the changes and it will be fixed in the next release. 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-15494) Uncaught TypeError: Cannot read property 'firstChild' of null
Jesse Glick commented on JENKINS-15494 Uncaught TypeError: Cannot read property 'firstChild' of null Wrapping an in … seems to work around the bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15494) Uncaught TypeError: Cannot read property 'firstChild' of null
SCM/JIRA link daemon resolved JENKINS-15494 as Fixed Uncaught TypeError: Cannot read property 'firstChild' of null Change By: SCM/JIRA link daemon (12/Oct/12 7:59 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-15494) Uncaught TypeError: Cannot read property 'firstChild' of null
SCM/JIRA link daemon commented on JENKINS-15494 Uncaught TypeError: Cannot read property 'firstChild' of null Code changed in jenkins User: Jesse Glick Path: changelog.html war/src/main/webapp/scripts/hudson-behavior.js http://jenkins-ci.org/commit/jenkins/8dbee911c39343c3085a4f56f6e597719ba0c0ca Log: [FIXED JENKINS-15494] Uncaught TypeError: Cannot read property 'firstChild' of null This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15494) Uncaught TypeError: Cannot read property 'firstChild' of null
Jesse Glick updated JENKINS-15494 Uncaught TypeError: Cannot read property 'firstChild' of null Seems to be a bug in Chrome; cannot reproduce in Firefox. The stylesheet link was generated by Stapler in the original HTML as part of another table; there is no reason for it to be duplicated when innerHTML is set. Bumping up priority since it can break forms with no apparent workaround other than using a different browser. Still have not pinpointed the conditions under which it occurs; a given plugin can have two describables in a pulldown, and selecting the first triggers this bug, while selecting the second does not. Change By: Jesse Glick (12/Oct/12 7:56 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Hi Alex, I'm not familiar with NOTESTS. Could you provide an example TAP Stream, please? Would it be something like: somefile.tap 1..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-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Bruno P. Kinoshita started work on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin Change By: Bruno P. Kinoshita (12/Oct/12 7:35 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15511) NPE from PluginManager
Jesse Glick assigned JENKINS-15511 to Jesse Glick NPE from PluginManager Change By: Jesse Glick (12/Oct/12 7:33 PM) Assignee: 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-15511) NPE from PluginManager
SCM/JIRA link daemon commented on JENKINS-15511 NPE from PluginManager Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/PluginManager.java http://jenkins-ci.org/commit/jenkins/eb18f080bb7e1842ee8031c6a8e6c665e527badf Log: [FIXED JENKINS-15511] NPE from PluginManager. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15511) NPE from PluginManager
SCM/JIRA link daemon resolved JENKINS-15511 as Fixed NPE from PluginManager Change By: SCM/JIRA link daemon (12/Oct/12 7:34 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15511) NPE from PluginManager
Jesse Glick created JENKINS-15511 NPE from PluginManager Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Oct/12 7:27 PM Description: When you try to install a plugin that is missing some dependencies or otherwise fails to start, SEVERE: Failed Loading plugin … or SEVERE: Failed Initializing plugin … with a detailed stack trace is shown, which is fine. But then you also get … jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Initializing plugin … java.lang.NullPointerException at hudson.PluginManager$2$1$2.run(PluginManager.java:349) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:883) 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.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) which is pretty clumsy—p.getPlugin() is null yet this is not being checked. Project: Jenkins Labels: exception plugin Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8963) Remote API to create/delete/modify promotions
Derek Brown commented on JENKINS-8963 Remote API to create/delete/modify promotions I would be using this functionality today if it existed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15401) support TODO directive to not fail such tests
Bruno P. Kinoshita started work on JENKINS-15401 support TODO directive to not fail such tests Change By: Bruno P. Kinoshita (12/Oct/12 7:22 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15401) support TODO directive to not fail such tests
Bruno P. Kinoshita commented on JENKINS-15401 support TODO directive to not fail such tests +1 thanks for reporting this issue Michael. I'll add an option so that users can decide whether a TODO directive should be interpreted as failed or not. The default behavior will be follow the TAP specification, as you mentioned in the issue description. Does that sound like a good idea for you? Cheers, B This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15497) Display link to download TAP attachment
SCM/JIRA link daemon commented on JENKINS-15497 Display link to download TAP attachment Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/TapResult.java src/main/java/org/tap4j/plugin/util/DiagnosticUtil.java src/main/resources/org/tap4j/plugin/TapResult/index.jelly src/main/resources/org/tap4j/plugin/tags/line.jelly src/main/resources/org/tap4j/plugin/tags/yaml.jelly http://jenkins-ci.org/commit/tap-plugin/3eff2031f16f744d8b7484c119982a9160fd7377 Log: [FIXED JENKINS-15497] Display link to download YAMLish 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-15497) Display link to download TAP attachment
SCM/JIRA link daemon resolved JENKINS-15497 as Fixed Display link to download TAP attachment Change By: SCM/JIRA link daemon (12/Oct/12 7:05 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15494) Uncaught TypeError: Cannot read property 'firstChild' of null
Jesse Glick
updated JENKINS-15494
Uncaught TypeError: Cannot read property 'firstChild' of null
Change By:
Jesse Glick
(12/Oct/12 7:06 PM)
Description:
Under some conditions adding a dynamic section to a configuration screen fails with the abovementioned error. In {{renderOnDemand}}, {{c.innerHTML = ""
\
+t.responseText
\
+"";}} succeeds yet immediately afterwards {{c.firstChild}} is a {{HTMLLinkElement}} rather than the expected {{HTMLTableElement}}:{code:xml}{code}The second child is indeed the expected table, so something inserted this link element at the top.Uri Scheiner says this occurred for him due to {{}} under a separated {{}}, yet it seems to occur under other circumstances as well.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15497) Display link to download TAP attachment
Bruno P. Kinoshita stopped work on JENKINS-15497 Display link to download TAP attachment Change By: Bruno P. Kinoshita (12/Oct/12 7:04 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15497) Display link to download TAP attachment
Bruno P. Kinoshita updated JENKINS-15497 Display link to download TAP attachment Change By: Bruno P. Kinoshita (12/Oct/12 6:27 PM) Attachment: 001.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15497) Display link to download TAP attachment
Bruno P. Kinoshita commented on JENKINS-15497 Display link to download TAP attachment Used this TAP Stream while testing: 1..2 ok 1 — extensions: files: sample.txt: File-Type: text/plain File-Name: sample.txt File-Size: 43 File-Content: c2FtcGxl ... ok2 Will attach an evidence of how it looks like after the 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-15497) Display link to download TAP attachment
Bruno P. Kinoshita started work on JENKINS-15497 Display link to download TAP attachment Change By: Bruno P. Kinoshita (12/Oct/12 6:26 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15502) Email-ext issues: attachments feature creating issues
Slide-O-Mix commented on JENKINS-15502 Email-ext issues: attachments feature creating issues Please attach your config.xml (stripped of secret information). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15493) Excessive memory usage with large number of request threads
Jesse Glick commented on JENKINS-15493 Excessive memory usage with large number of request threads Root fix was https://github.com/jenkinsci/jelly/compare/285312f69b...d23b0cde79 right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Hansen Loke commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException I get this error after upgrading to Jenkins 1.485 too This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15369) NPE from Jenkins.removeNode
dogfood commented on JENKINS-15369 NPE from Jenkins.removeNode Integrated in jenkins_main_trunk #1997 JENKINS-15369 NPE from Jenkins.removeNode continued. (Revision 87d9a6e413c11eda69f7c2966c3f2a5f97381585) Result = SUCCESS Jesse Glick : 87d9a6e413c11eda69f7c2966c3f2a5f97381585 Files : core/src/main/java/hudson/model/Computer.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-15202) Permanent building / consider removing latest changes
Mirek Gwiżdż commented on JENKINS-15202 Permanent building / consider removing latest changes I would like to add that I have similar issue. We are using snapshot views and from time to time I see rebuilds without reason. It says that CSPEC configured != catcs (view), but nobody actually changed cs. I'm not sure why jenkins thinks that something changed, but would it be possible to add a checkbox in plugin config to disable/enable this feature, and make it off by default? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15344) Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException
Thomas Zlika commented on JENKINS-15344 Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException I use mvn clean site This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11964) [Regression] Cannot build a single module in a Maven multi-module job with Maven 3
Rade Martinović commented on JENKINS-11964 [Regression] Cannot build a single module in a Maven multi-module job with Maven 3 Is maven 3 support planned? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15344) Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException
Ulli Hafner commented on JENKINS-15344 Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException I can't reproduce this with your example. Is there a findbugs warning in your project? When I run it I get: [INFO] [INFO] --- findbugs-maven-plugin:2.5.2:findbugs (default-cli) @ aggregator --- [INFO] Fork Value is true [INFO] Done FindBugs Analysis mojoSucceeded org.codehaus.mojo:findbugs-maven-plugin:2.5.2(default-cli) [FINDBUGS] Finding all files that match the pattern findbugsXml.xml [FINDBUGS] Parsing 1 files in /Users/hafner/Development/jenkins/jobs/JENKINS-15344/workspace/target [FINDBUGS] Successfully parsed file /Users/hafner/Development/jenkins/jobs/JENKINS-15344/workspace/target/findbugsXml.xml of module aggregator with 0 warnings. projectSucceeded net.test:aggregator:0.1-SNAPSHOT sessionEnded There is no warning found. I'm using the goals "clean package findbugs:findbugs". What did you use? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15369) NPE from Jenkins.removeNode
SCM/JIRA link daemon commented on JENKINS-15369 NPE from Jenkins.removeNode Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/Computer.java http://jenkins-ci.org/commit/jenkins/87d9a6e413c11eda69f7c2966c3f2a5f97381585 Log: JENKINS-15369 NPE from Jenkins.removeNode continued. /computer/*/doDelete should try harder to remove even a “zombie” Computer with no associated 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-15369) NPE from Jenkins.removeNode
Jesse Glick updated JENKINS-15369 NPE from Jenkins.removeNode Change By: Jesse Glick (12/Oct/12 3:20 PM) Component/s: ssh-slaves This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15476) "Block until the triggered projects finish their builds" doesn't notify upstream project when complete.
Justin Crowe updated JENKINS-15476 "Block until the triggered projects finish their builds" doesn't notify upstream project when complete. Change By: Justin Crowe (12/Oct/12 2:51 PM) Description: When using the parameterised trigger plugin Create 2 jobs.Job 1 uses the "Trigger/call builds on other projects" option to call job 2 and check the "Block until the triggered projects finish their builds" option so that job 1 will only continue if Job 2 is complete and successful.Build Job 1.Job 1 will run and call the build on Job 2 but job 1 will never receive the notification of job 2's completion. This means that job 1 never completes and just sits in the build queue.This is functionality that used to work with older versions of jenkins/the plugin so something has gone wring with recent releases as i have only just migrated from older versions.java.runtime.name Java(TM) SE Runtime Environmentjava.runtime.version 1.6.0_26-b03Jenkins Version:1.485 - a single master instance with no slavesParam Trigger version 2.16If i have left anything out please let me know.thanksUPDATE /Workaround After looking through the logs i have removed the Disk Usage Plugin which seems to be having trouble (it looks like this issue has already been logged) and this seems to have fixed this. I have assigned the issue to that component as well now.UPDATE 2After looking further, disabling the disk usage plugin only seems to fix this for jobs with a single downstream job. If a downstream job contains further downstream jobs then the results are not being received. UPDATE 3I ended up reverting to the LTS Release and this seems to have fixed the issue. So it looks like Jenkins has caused this rather than the other plugins. Component/s: disk-usage This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12908) TFS errors during get operation do not fail the build
jeffolson commented on JENKINS-12908 TFS errors during get operation do not fail the build Thanks, Erik. No, this is very infrequent, thankfully. It sounds like this probably can't be fixed, then, so you can close this issue. Thanks for investigating it! Jeff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15510) Embeddable Build Status plugin displays a Running badge for disabled jobs.
Geoff Cummings created JENKINS-15510 Embeddable Build Status plugin displays a Running badge for disabled jobs. Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: embeddable-build-status Created: 12/Oct/12 2:38 PM Description: The Embeddable Build Status plugin is displaying running.png when a project is disabled. running.png is the default option in the switch statement. default: file = "running.png"; Project: Jenkins Priority: Major Reporter: Geoff Cummings This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14657) Embeddable Build Status Plugin url issue
Geoff Cummings updated JENKINS-14657 Embeddable Build Status Plugin url issue Updating component to newly created 'embeddable-build-status' component Change By: Geoff Cummings (12/Oct/12 2:36 PM) Labels: embeddable-build-status jenkins plugin Component/s: embeddable-build-status Component/s: 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-15508) issues.jenkins-ci.org does not have a component for embeddable-build-status
Larry Shatzer, Jr. resolved JENKINS-15508 as Fixed issues.jenkins-ci.org does not have a component for embeddable-build-status Component created. Change By: Larry Shatzer, Jr. (12/Oct/12 2:29 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-15315) Slave polling hungup
Alexey Larsky edited a comment on JENKINS-15315 Slave polling hungup But network problem - is ordinary situation between two computers (master and slave(s)). And this situation mustn't influence to future builds. In other words task should restoring after network error. Thank 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-15315) Slave polling hungup
Alexey Larsky edited a comment on JENKINS-15315 Slave polling hungup But network problem - is ordinary situation between two computers (master and slave(s)). And this situation mustn't influence to future builds. In other words task should be able to restore after network error. Thank 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-15315) Slave polling hungup
Alexey Larsky commented on JENKINS-15315 Slave polling hungup But network problem - is ordinary suation between two computers (master and slave). And this situation mustn't influence to future builds. In other words task should restoring after network error. Thank 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-15035) cobertura plugin don't validate report files and later fail to parse them
Larry Shatzer, Jr. commented on JENKINS-15035 cobertura plugin don't validate report files and later fail to parse them I now get a stacktrace on remote slave running a grails build that produces a coverage.xml file. It worked till I upgraded, then when I rolled back, it works again. Here is the stacktrace: Cobertura: Loaded information on 170 classes. 08:10:16 Cobertura: Saved information on 170 classes. 08:10:16 Publishing Cobertura coverage report... 08:10:16 FATAL: Unable to find coverage results 08:10:16 hudson.util.IOException2: remote file operation failed: /home/jenkins/workspace/grailsApplication at hudson.remoting.Channel@2fcf1d75:remoteslave 08:10:16 at hudson.FilePath.act(FilePath.java:847) 08:10:16 at hudson.FilePath.act(FilePath.java:824) 08:10:16 at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:335) 08:10:16 at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) 08:10:16 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:807) 08:10:16 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:782) 08:10:16 at hudson.model.Build$BuildExecution.post2(Build.java:183) 08:10:16 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:729) 08:10:16 at hudson.model.Run.execute(Run.java:1541) 08:10:16 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 08:10:16 at hudson.model.ResourceController.execute(ResourceController.java:88) 08:10:16 at hudson.model.Executor.run(Executor.java:236) 08:10:16 Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@64916e12 08:10:16 at hudson.remoting.UserRequest.serialize(UserRequest.java:166) 08:10:16 at hudson.remoting.UserRequest.(UserRequest.java:62) 08:10:16 at hudson.remoting.Channel.call(Channel.java:663) 08:10:16 at hudson.FilePath.act(FilePath.java:840) 08:10:16 ... 11 more 08:10:16 Caused by: java.io.NotSerializableException: hudson.plugins.cobertura.CoberturaPublisher 08:10:16 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) 08:10:16 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) 08:10:16 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) 08:10:16 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) 08:10:16 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) 08:10:16 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) 08:10:16 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) 08:10:16 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) 08:10:16 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) 08:10:16 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) 08:10:16 at hudson.remoting.UserRequest._serialize(UserRequest.java:155) 08:10:16 at hudson.remoting.UserRequest.serialize(UserRequest.java:164) 08:10:16 ... 14 more 08:10:16 No coverage results were found using the pattern 'target/test-reports/cobertura/coverage.xml' relative to '/home/jenkins/workspace/grailsApplication'. Did you enter a pattern relative to the correct directory? Did you generate the XML report(s) for Cobertura? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15315) Slave polling hungup
Rob Petti commented on JENKINS-15315 Slave polling hungup It's hanging in IO, which to me suggests a network problem. I'm not sure what else I can do aside from adding some kind of timeout. :/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15464) Matrix-based security -Job cancel privilege not working
Jan Vogel reopened JENKINS-15464 Matrix-based security -Job cancel privilege not working I've experienced the same issue as the original report. Found this page when looking for a solution, so I've taken the liberty to attach the requested screenshot. Change By: Jan Vogel (12/Oct/12 1:44 PM) Resolution: Cannot Reproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15464) Matrix-based security -Job cancel privilege not working
Jan Vogel updated JENKINS-15464 Matrix-based security -Job cancel privilege not working Same issue here, I've attached the screenshot, including the hover text. I've cleared both role names. Change By: Jan Vogel (12/Oct/12 1:43 PM) Attachment: CancelBuild.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15438) Violations plugin: exception due to invalid characters in filename
Christoph Torens
commented on JENKINS-15438
Violations plugin: exception due to invalid characters in filename
i had to do the following edits to get it working
– plugins\violations\model\BuildModel.java (line 144...)
private FileModelProxy getFileNameProxy(String name) {
FileModelProxy proxy = fileModelMap.get(name);
if (proxy != null) {
return proxy;
}
File xmlFile = new File(
xmlRoot, "file/" + name + ".xml");
fileModelMap.put(name, new FileModelProxy(xmlFile));
+proxy = fileModelMap.get(name);
return proxy;
}
/**
Add a file count.
@param type the type.
@param name the filename.
@param count the number of violations.
*/
public void addFileCount(String type, String name, int[] count) {
+ // windows needs this replacement
+name = name.replace("\\", "/");
FileModelProxy proxy = getFileNameProxy(name);
getFileCounts(type).add(new FileCount(name, count, proxy));
}
–
– plugins\violations\ViolationsReport.java (lin 240...)
return new RecurDynamic(
"", name, proxy.build(build).contextPath(req.contextPath()));
+ "", name, proxy.build(build).contextPath(""));
} else {
–
sorry cant do a proper diff right now
hope that hlps others...
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10147) Add 'poll SCM' option to build step
Atef GHOULEM commented on JENKINS-10147 Add 'poll SCM' option to build step Hello, Does this bug is planned for a next 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-14139) Violations Plugin does not support CPPLINT errors on LINE 0
Christoph Torens
commented on JENKINS-14139
Violations Plugin does not support CPPLINT errors on LINE 0
for me, it is acceptable to edit: plugins/violations/generate/OutputFileModel.java (line 162...)
—
private void outputContents() throws IOException {
sourceReader = new BufferedReader(open());
+// we want an empty line 0, because googles cpplint.py gives some warnings for line 0, e.g., missing copyright
+w.println(" ");
int lineNumber = 1;
while (true) {
String line = sourceReader.readLine();
if (line == null) {
break;
}
—
this adds always an empty line 0, however
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8754) ROADMAP: Improve Start-up Time
jburrows closed JENKINS-8754 as Duplicate ROADMAP: Improve Start-up Time Looks like the issue was re-opened as another issue: See JENKINS-15465 and JENKINS-15439 Change By: jburrows (12/Oct/12 12:50 PM) Status: Reopened Closed 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-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek closed JENKINS-14103 as Fixed Grails 2.0.4 not listed in installer doropdown Confirmed working Change By: Jeroen Wesbeek (12/Oct/12 12:48 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek edited a comment on JENKINS-14103 Grails 2.0.4 not listed in installer doropdown Confirmed that I indeed see all Grails versions (currently up to 2.2.0.RC1) in the latest Jenkins (1.485 - didn't check with older installations). Could this have been fixed by integrating my pull request for the backend-crawler? ( https://github.com/jenkinsci/backend-crawler/pull/11#issuecomment-9282236 ) Anyways, thanks for fixing this annoying 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-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek edited a comment on JENKINS-14103 Grails 2.0.4 not listed in installer doropdown Confirmed that I indeed see all Grails versions (currently up to 2.2.0.RC1) in the latest Jenkins (1.485 - didn't check with older installations). Could this have been fixed by integrating my pull request for the backend-crawler? ( https://github.com/jenkinsci/backend-crawler/pull/11#issuecomment-9282236 ) Anyways, thanks for fixing the 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-15491) OOM in Jenkins after 1 day
Pailloncy Michaël commented on JENKINS-15491 OOM in Jenkins after 1 day Thanks Koshuke. I'm currently uploading the dump file (.phd) and I'll telling you where to upload 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-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek commented on JENKINS-14103 Grails 2.0.4 not listed in installer doropdown Confirmed that I indeed see all Grails versions (currently up to 2.2.0.RC1) in the latest Jenkins (1.485 - didn't check with older installations). Thanks for fixing the 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-15315) Slave polling hungup
Alexey Larsky edited a comment on JENKINS-15315 Slave polling hungup I again get hungup sitiation on slave. P4 versions - lastest 2012.2. Attaching new threaddump. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8754) ROADMAP: Improve Start-up Time
jburrows commented on JENKINS-8754 ROADMAP: Improve Start-up Time More info, after each restart of Jenkins, it clears out any and all build history again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15509) It should not be required to enter a group name
Kristoffer Peterhänsel created JENKINS-15509 It should not be required to enter a group name Issue Type: Bug Affects Versions: current Assignee: Thorsten Heit Components: crowd2 Created: 12/Oct/12 11:44 AM Description: I am not quite sure I understand why it is "cool" to be able to enter group names in Jenkins and restrict users that way. Since one of the points of Crowd is that you can set up a lot of stuff in that end and have all that centralized. Haven't seen the setup in JIRA or Confluence. But it sounds pretty strange that they do that as it just seems like a redundant step to me. But anyway. Since I'd rather set up the groups that have access in my Crowd instance. It would be nice if I didn't need to jump though the hoop of creating a group and entering it into Jenkins to get this plugin working. Also the group I grant access to Jenkins come from an Active Directory and contain spaces. So I couldn't actually enter that if I wanted. Project: Jenkins Priority: Major Reporter: Kristoffer Peterhänsel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8754) ROADMAP: Improve Start-up Time
Richard Mortimer commented on JENKINS-8754 ROADMAP: Improve Start-up Time There is/was a critical bug or two in 1.485 related to the lazy loading. See JENKINS-15465 and JENKINS-15439. I'm pretty sure that those are the issues that you are seeing. Kohsuke backported the fixes to the 1.486 release candidate build. You can download a pre-release build from https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_rc_branch/279/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15261) Mobile browsers not selectable
Ross Rowe resolved JENKINS-15261 as Fixed Mobile browsers not selectable Change By: Ross Rowe (12/Oct/12 10:53 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15261) Mobile browsers not selectable
Ross Rowe commented on JENKINS-15261 Mobile browsers not selectable Hi again, I've updated the plugin to present Browser axis for WebDriver and SeleniumRC (Sauce Labs provides two REST API calls to retrieve the supported browsers, and will use 'googlechrome' for SeleniumRC and 'chrome' for WebDriver). This change has been released in verison 1.25 of the plugin, please let me know how this version goes for you. Cheers, Ross This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8754) ROADMAP: Improve Start-up Time
jburrows reopened JENKINS-8754 ROADMAP: Improve Start-up Time Build records are not getting loaded at all, even after the Jenkins service has been up for more than 18 hours. If there is some step needed to get back the build records or get them loaded, it should have been represented in the Changelog. Please fix this issue. Log entries show: I looked at the 'jenkins.err' on the Jenkins server & saw errors similar to these: Oct 12, 2012 2:06:01 AM org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/hudson/model/View/index.jelly:44:43: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/lib/hudson/projectView.jelly:60:22: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Apps/Jenkins/war/WEB-INF/lib/jenkins-core-1.485.jar!/lib/layout/tab.jelly:46:18: Failed to write to client at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625) 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) Oct 12, 2012 2:11:01 AM hudson.model.Run execute INFO: DBS_RETAIL_R5-SNAPSHOT #102 main build action completed: SUCCESS Oct 12, 2012 2:11:01 AM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at hudson.tasks.LogRotator.perform(LogRotator.java:119) at hudson.model.Job.logRotate(Job.java:338) at hudson.model.Run.execute(Run.java:1581) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Change By: jburrows (12/Oct/12 10:49 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15492) Warnings module crashes with pep8 output
Shish Moom commented on JENKINS-15492 Warnings module crashes with pep8 output ViolationsAdapter.java:60 – parser.parse(model, temp.getParentFile(), temp.getName(), null); it's giving the parser "null" for the filename list; perhaps "empty list" would 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-15261) Mobile browsers not selectable
SCM/JIRA link daemon commented on JENKINS-15261 Mobile browsers not selectable Code changed in jenkins User: Ross Rowe Path: src/main/java/hudson/plugins/sauce_ondemand/BrowserAxis.java src/main/java/hudson/plugins/sauce_ondemand/SeleniumRCAxis.java src/main/java/hudson/plugins/sauce_ondemand/WebDriverAxis.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/044c84ce07c785eeefc131def917936789869e15 Log: JENKINS-15261 Present separate browser axis for SeleniumRC/WebDriver This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15261) Mobile browsers not selectable
SCM/JIRA link daemon commented on JENKINS-15261 Mobile browsers not selectable Code changed in jenkins User: Ross Rowe Path: src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/6b11433b56f5772550c436cde454dab70b78c4c0 Log: JENKINS-15261 Present separate browser axis for SeleniumRC/WebDriver Compare: https://github.com/jenkinsci/sauce-ondemand-plugin/compare/b52250176d96...6b11433b56f5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15449) IE 9 os is wrong
Ross Rowe assigned JENKINS-15449 to Ross Rowe IE 9 os is wrong Change By: Ross Rowe (12/Oct/12 10:33 AM) Assignee: Kohsuke Kawaguchi Ross Rowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15508) issues.jenkins-ci.org does not have a component for embeddable-build-status
Geoff Cummings created JENKINS-15508 issues.jenkins-ci.org does not have a component for embeddable-build-status Issue Type: Bug Assignee: Unassigned Components: infrastructure Created: 12/Oct/12 10:32 AM Description: I cannot create an issue for the embeddable-build-status plugin as it is not listed as a Jenkins component in JIRA. Geoff Project: Jenkins Priority: Minor Reporter: Geoff Cummings This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15315) Slave polling hungup
Alexey Larsky edited a comment on JENKINS-15315 Slave polling hungup Uploading "Thread dump [Jenkins] (2012-10-12 14-00-59).htm" Threaddump for p4 polling hungup on slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15315) Slave polling hungup
Alexey Larsky edited a comment on JENKINS-15315 Slave polling hungup Threaddump for p4 polling hungup on slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15315) Slave polling hungup
Alexey Larsky updated JENKINS-15315 Slave polling hungup Threaddump for p4 polling hungup on slaves. That intresting - now hungup polls on master too. Change By: Alexey Larsky (12/Oct/12 10:09 AM) Attachment: Thread dump [Jenkins] (2012-10-12 14-00-59).htm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15315) Slave polling hungup
Alexey Larsky commented on JENKINS-15315 Slave polling hungup I again get hungup sitiation on slave. P4 versions - last. Attaching new threaddump. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15507) Environment variables are not injected in parent matrix job
Krzysztof Malinowski created JENKINS-15507 Environment variables are not injected in parent matrix job Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 12/Oct/12 9:43 AM Description: When I choose to prepare environment for the run and provide properties content, these are not injected in matrix parent project. This behavior causes SCM checkout to fail, since variables are required in Clearcase config spec. Environment: Jenkins 1.485 on RHEL5 x86_64, envinject 1.72 Project: Jenkins Priority: Major Reporter: Krzysztof Malinowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15505) Upstream config bug: I have observed problems when triggering a testflow from another project.
Søren Mollerup resolved JENKINS-15505 as Duplicate Upstream config bug: I have observed problems when triggering a testflow from another project. Just found out this a duplicate of 14449 Change By: Søren Mollerup (12/Oct/12 9:36 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-15506) Broken Rest API: When trying to access the REST API (/api/xml?depth=1) for a build flow job, I encountered an error.
Søren Mollerup created JENKINS-15506 Broken Rest API: When trying to access the REST API (/api/xml?depth=1) for a build flow job, I encountered an error. Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 12/Oct/12 9:34 AM Description: Broken Rest API === When trying to access the REST API (/api/xml?depth=1) for a build flow job, I encountered an error. The depth=1, seems to trigger the call to the broken method. Error message: Status Code: 500 Exception: Failed to write shortDescription Stacktrace: java.io.IOException: Failed to write shortDescription at org.kohsuke.stapler.export.Property.writeTo(Property.java:119) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:179) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:176) at org.kohsuke.stapler.export.Property.writeValue(Property.java:231) at org.kohsuke.stapler.export.Property.writeValue(Property.java:181) at org.kohsuke.stapler.export.Property.writeValue(Property.java:136) at org.kohsuke.stapler.export.Property.writeTo(Property.java:113) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:179) at org.kohsuke.stapler.export.Property.writeValue(Property.java:231) at org.kohsuke.stapler.export.Property.writeValue(Property.java:181) at org.kohsuke.stapler.export.Property.writeValue(Property.java:136) at org.kohsuke.stapler.export.Property.writeTo(Property.java:113) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:179) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:176) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:176) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:176) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:176) at org.kohsuke.stapler.export.Property.writeValue(Property.java:231) at org.kohsuke.stapler.export.Property.writeValue(Property.java:181) at org.kohsuke.stapler.export.Property.writeValue(Property.java:136) at org.kohsuke.stapler.export.Property.writeTo(Property.java:113) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:179) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:176) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:176) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:176) at org.kohsuke.stapler.export.Model.writeTo(Model.java:152) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:204) at hudson.model.Api.doXml(Api.java:91) 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.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) 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$4.doDispatch(MetaClass.java:203) 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(ServletCon
[JIRA] (JENKINS-15505) Upstream config bug: I have observed problems when triggering a testflow from another project.
Søren Mollerup created JENKINS-15505 Upstream config bug: I have observed problems when triggering a testflow from another project. Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 12/Oct/12 9:33 AM Description: Upstream config bug === I have observed problems when triggering a buildflow from another project. --- Trigger Job ---> Build Flow --- The trigger cannot be specified on the build flow (minor issue), but can be specified through the trigger job. The problem is when a trigger is established. it disappears when I configure the Build flow! When I save the build flow configuration, the trigger is not present anymore. Environment: Linux Project: Jenkins Priority: Major Reporter: Søren Mollerup This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15504) NPE on running a job
Sylvain C. commented on JENKINS-15504 NPE on running a job Furthermore, the revert snapshot operation was not running before this 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-15504) NPE on running a job
Sylvain C. created JENKINS-15504 NPE on running a job Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: vsphere-cloud Created: 12/Oct/12 8:53 AM Description: On running my job, I have the following NPE : 11:40:25 Starting limited count build: 1FATAL: null 11:40:25 java.lang.NullPointerException 11:40:25 at hudson.model.Slave.createLauncher(Slave.java:311) 11:40:25 at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:544) 11:40:25 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:475) 11:40:25 at hudson.model.Run.execute(Run.java:1488) 11:40:25 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 11:40:25 at hudson.model.ResourceController.execute(ResourceController.java:88) 11:40:25 at hudson.model.Executor.run(Executor.java:236) I have the "Disconnect After Limited Builds = 1" option enabled. Environment: Jenkins 1.473, Vsphere plugin 0.10 Project: Jenkins Priority: Major Reporter: Sylvain C. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15440) Emailing users at the end of a failed build very slow for big Jenkins instance using subversion
Nicolas De Loof commented on JENKINS-15440 Emailing users at the end of a failed build very slow for big Jenkins instance using subversion SubversionMailAddressResolverImpl.findMailAddressFor is a "last chance" strategy to retrieve user email from svn, based on commonly used (but outdated) svn hosting services that offer mail service. Based on your security settings, you should have user populated with email address from company LDAP. As a workaround, just populate users with an email in jenkins user database. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14665) Quality center plugin for Hudson does not work properly
Danielle Moore commented on JENKINS-14665 Quality center plugin for Hudson does not work properly I am having this same issue. Please provide a solution or suggestion. Thank 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-15490) checkstyle plugin does not work in the latest version of Jenkins
Ulli Hafner commented on JENKINS-15490 checkstyle plugin does not work in the latest version of Jenkins Ok, thanks. I.e. you also use JDK6 to run Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15384) TFS Plugin does not seem to work (can't get latest)
redsolo commented on JENKINS-15384 TFS Plugin does not seem to work (can't get latest) Im not sure why this is happening and unfortunately i dont have a real TFS to work with. Instead I only can use the codeplex TFS instance which may work like all the other TSF versions out there. Its hard for me to fix this unless I get a good way of reproducing the issue, so if you can get any more details on when this issue happens that would be great. How reproducable is it for you? Every build, every day? Ive configure two jobs on my local jenkins instance to see if I get the "All files are up to date." issue when retrieving files from the TFS. Job pusher - triggers every 3 mins checks out a TFS project creates a local file containing the file stamp adds this to the TF workspace (tf add) commits the file (tf checkin) Job receiver - polls SCM every 10 min checks out the same TFS project fails the build if it finds the "All files are up to date." text in the console (using the text-finder plugin) Would the "Job receiver" resemble the problems you are seeing? ie, the "tf get" command would sometimes yield the "all files are up to date"? ive had this running for an hour now without any problems, but then again this very simple setup may not be applicable to the issue you are seeing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15503) Test results lost on all past builds
Sven Amann created JENKINS-15503 Test results lost on all past builds Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Screen Shot 2012-10-12 at 09.33.38.png Components: core Created: 12/Oct/12 7:44 AM Description: Test results are missing on all but the last build, i.e., the build and test result overview page still displays the number of failed tests, but the concrete tests are not listed/linked (see attachment and our build server). Environment: Jenkins on Ubuntu Lucid Lynx with build slave on Windows XP Project: Jenkins Labels: testreport testing Priority: Critical Reporter: Sven Amann This message is automatically generated by JIRA. If you 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
Stephan Grimm updated JENKINS-13790 Subversion externals fail Change By: Stephan Grimm (12/Oct/12 7:28 AM) Labels: 1.4 AssertionError jenkins subversion Environment: Windows XP SP3 , Windows 7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15305) Job-level configuration is missing
redsolo resolved JENKINS-15305 as Won't Fix Job-level configuration is missing Resolving this as it is behaving as post-build steps should do. In an earlier version of Jenkins the post-build steps would be listed as the build-coinplugin is, but that has changed now to how it looks today. I dont want the plugin to behave differently from other post-build plugins. Change By: redsolo (12/Oct/12 7:13 AM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15470) Support for instant-messaging plugin (xmpp)
redsolo commented on JENKINS-15470 Support for instant-messaging plugin (xmpp) Is this really related to the ci-game plugin? The plugin should only give points to the users that have commited something to a build, ie they are referred in a SCM change set. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12262) Error "bzr: ERROR: No WorkingTree exists for" when using shared repositories without working trees and bzr checkout option
Stewart Smith commented on JENKINS-12262 Error "bzr: ERROR: No WorkingTree exists for" when using shared repositories without working trees and bzr checkout option I'm going to close this as not relevant for the current version as I've changed a whole bunch of code around that recently. Please reopen if there's still a problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12262) Error "bzr: ERROR: No WorkingTree exists for" when using shared repositories without working trees and bzr checkout option
Stewart Smith resolved JENKINS-12262 as Fixed Error "bzr: ERROR: No WorkingTree exists for" when using shared repositories without working trees and bzr checkout option Change By: Stewart Smith (12/Oct/12 7:00 AM) Status: Open Resolved Assignee: Monty Taylor Stewart Smith 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
