[JIRA] [dashboard-view-plugin] (JENKINS-21578) CCE since ${jobs} includes non-Job's
Title: Message Title
Carsten Otto commented on JENKINS-21578
Re: CCE since ${jobs} includes non-Job's
Please also have a look at https://github.com/jenkinsci/dashboard-view-plugin/pull/40 which solves a very similar issue.
PS: Your login captchas are WAY too hard. Furthermore, the generated passwords use I and l which are hard/impossible to differentiate. Logging in cost me about five minutes!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-14179) offline master is used after restart
Carsten Otto commented on JENKINS-14179 offline master is used after restart No. Besides, this bug is more than a year old. I did not notice it after my initial report. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE Yes, now it works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE I uploaded the HPI file (no idea if that worked?) and created a new job based on a job that previously failed (and still does). However, the new job also fails with the same error message. Furthermore, even if the fix worked, I'd need to use the plugin for existing jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Carsten Otto edited a comment on JENKINS-14135 NPE I see that this job only works on master and fails on other nodes. Maybe the issue is that "report" is transient, but you do need serialization for the object that is passed to the node? I have no idea how plugins work, but this makes a bit of sense to me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE I see that this job only works an master and fails on other nodes. Maybe the issue is that "report" is transient, but you do need serialization for the object that is passed to the node? I have no idea how plugins work, but this makes a bit of sense to me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE Maybe a multithreading problem? I see that you recently introduced a field "report" (that triggers the NPE). Maybe it is necessary to mark this using "volatile"? The effects of the constructor might not yet be visible when invoke() runs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE Linux, Debian Stable, x86_64 java version "1.7.0_03" Java(TM) SE Runtime Environment (build 1.7.0_03-b04) Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode) Jenkins ver. 1.472 External Monitor Job Type Plugin 1.0 LDAP Plugin 1.1 pam-auth 1.0 ant 1.1 javadoc 1.0 Jenkins Subversion Plug-in 1.42 Jenkins Translation Assistance plugin 1.9 Jenkins CVS Plug-in 2.4 Jenkins SSH Slaves plugin 0.21 Maven Integration plugin 1.472 Static Analysis Utilities 1.43 Jenkins instant-messaging plugin 1.21 FindBugs Plug-in 4.42 Jenkins Email Extension Plugin 2.22 Jenkins IRC Plugin 2.18 Jenkins Parameterized Trigger plugin 2.15 Jenkins GIT plugin 1.1.20 PMD Plug-in 3.29 Jenkins SLOCCount Plug-in 1.8 Checkstyle Plug-in 3.29 Static Analysis Collector Plug-in 1.29 Jenkins Sonar Plugin 1.8 Join plugin 1.15 Copy Artifact Plugin 1.22 Fail The Build Plugin 1.0 Build Pipeline Plugin 1.3.1 Python Plugin 1.2 Jenkins Workspace Cleanup Plugin 0.8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE I configured a new job that only uses the SLOCcount plugin and has a custom working space that only contains the contents of the ZIP file. This still fails (with 1.8, not with 1.7). It even fails with a directory that just contains the report.sc (and the search pattern is changed to just "report.sc"). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE It works with 1.7. Can you tell me how I can manually test this? I have no idea how to remove files from my workspace after a build and before running the plugin. Some way to test this in my shell would be nice. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE What kind of details reg. 2 do you need? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE 1) Linux. 2) dist/report.sc 3) http://aprove.informatik.rwth-aachen.de/~cotto/workspace.zip (I deleted everything but the dist/ directory. If you need more, we need to fine tune - I cannot give you the source of our project.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9066) Aggregation of downstream project reports for static analysis reports
Carsten Otto commented on JENKINS-9066 Aggregation of downstream project reports for static analysis reports Regarding the comment from 13/Sep/11 11:37 AM: It is possible to archive the artifacts of the analysis itself (findbugs.xml generated by FindBugs) and then collect these artifacts in a job started from the upstream build. This involves, at least in my case, a python script and the "Join" plugin. Using this solution you can have different jobs for the analysis tools and a combined job for the analysis plugins (creating the graphs and such). However, I do not know how to have the tool run and the analysis of the results in one job and collecting all such results in another 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-14137) Workspace used in parallel
Carsten Otto commented on JENKINS-14137 Workspace used in parallel Second build, not second 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-14137) Workspace used in parallel
Carsten Otto resolved JENKINS-14137 as Not A Defect Workspace used in parallel I am sorry. From the output I assumed that the second build was started in parallel to the first build - which then caused the problems I saw. Instead, the first build failed due to another error (not caused by Jenkins) and the second job started shortly after that and also failed directly. In short, I don't see any reason to believe that the workspaces are used in parallel. Sorry again! Change By: Carsten Otto (21/Jun/12 5:46 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14137) Workspace used in parallel
Carsten Otto commented on JENKINS-14137 Workspace used in parallel This also happens often if two builds are run on the same node (in my case: master) without any other job in between. I think the code that takes care to create and use a second (or third, ...) workspace is to blame. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14179) offline master is used after restart
Carsten Otto created JENKINS-14179 offline master is used after restart Issue Type: Bug Assignee: Unassigned Components: other Created: 21/Jun/12 12:52 PM Description: Hi, my master node got taken offline automatically due to low free disk space. After a restart of Jenkins (it was down for a few hours) it started building jobs on master, although this node still was marked as offline. PS: Finding the right component is very very hard for non-developers. I suggest to make it easier to find the right category for non-plugin related bugs. I hope my choice of "other" is acceptable here. PPS: 1.471 is not a valid version?! This bug tracker is... weird. Best regards, Carsten Project: Jenkins Priority: Minor Reporter: Carsten Otto This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14137) Workspace used in parallel
Carsten Otto created JENKINS-14137 Workspace used in parallel Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: concurrent-build Created: 19/Jun/12 12:06 AM Description: I encountered a situation where a single workspace is used by two concurrent builds. The job is configured as follows: (checked) Execute concurrent builds if necessary (unchecked) Use custom workspace (checked) This build is parameterized I see the following builds: Failed Build #66 (Jun 19, 2012 1:38:56 AM) (on slave 1), Took 4 min 3 sec Success Build #67 (Jun 19, 2012 1:40:51 AM) (on slave 2), Took 14 min Failed Build #68 (Jun 19, 2012 1:43:00 AM) (on slave 1), Took 3 min 14 sec #66 shows: Started by upstream project "OTHERNAME" build number 18 Building remotely on slave1 in workspace /var/lib/jenkins/workspace/NAME Checkout:NAME / /var/lib/jenkins/workspace/NAME - hudson.remoting.Channel@7a85a2cf:slave1 #68 shows: Started by upstream project "YETANOTHERNAME" build number 13 Building remotely on slave1 in workspace /var/lib/jenkins/workspace/NAME Checkout:NAME / /var/lib/jenkins/workspace/NAME - hudson.remoting.Channel@7a85a2cf:slave1 The builds for this job are triggered by several upstream jobs. Each build should be able to run in parallel and the job is parameterized by a git branch (#66, #67 and #68 worked on different branches). As soon as #68 started (and cleaning its workspace, so cleaning also the workspace of #66), #66 crashed. Please tell me if you need more information! Environment: Linux x86_64, Debian stable, Java 7 Project: Jenkins Priority: Major Reporter: Carsten Otto This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Carsten Otto created JENKINS-14135 NPE Issue Type: Bug Assignee: npiguet Components: sloccount Created: 18/Jun/12 9:13 PM Description: This happens with 1.8. I get the sloccount-data (report.sc) and some other XML files (findbugs etc.). Other than that, the workspace is empty. After retrieving the files, I run the publishers. Please tell me how to work around this issue or fix the plugin. If you need more information, please ask. I'm not sure how to write bug reports in here. Best regards, Carsten ERROR: Publisher hudson.plugins.sloccount.SloccountPublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.sloccount.model.SloccountParser.parseLine(SloccountParser.java:92) at hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:59) at hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:50) at hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:40) at hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:17) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2180) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) 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.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Project: Jenkins Priority: Major Reporter: Carsten Otto This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
