[JIRA] (JENKINS-54027) ID analysis is already used by another action
Title: Message Title
Jan Linnenkohl commented on JENKINS-54027
Re: ID analysis is already used by another action
It works, when it disable aggregating results: recordIssues aggregatingResults: false, tools: [msBuild(id: "${profile}_DI")]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-54027) ID analysis is already used by another action
Title: Message Title
Jan Linnenkohl reopened an issue
I just got the following error: java.lang.IllegalStateException: ID analysis is already used by another action: io.jenkins.plugins.analysis.core.model.ResultAction for Static Analysis I working in a three parallel stages. Two of them will work on the same machine (all windows at the moment). The error happens on the machine, where two parallel steps are happening.
recordIssues aggregatingResults: true, tools: [msBuild(id: "${profile}_DI")]
We are using Jenkins 2.150.2, Warnings Next Generation 2.1.2 & Analysis Model api 2.0.2.
Jenkins / JENKINS-54027
ID analysis is already used by another action
Change By:
Jan Linnenkohl
Resolution:
Fixed
Status:
Resolved Reopened
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] [subversion] (JENKINS-15249) Missing support for externals in 1.4.2 for subversion working copy version 1.7
Jan Linnenkohl resolved JENKINS-15249 as Fixed Missing support for externals in 1.4.2 for subversion working copy version 1.7 This has been fixed in JENKINS-13790 and works for 1.45+ version. Change By: Jan Linnenkohl (11/Jul/13 12:17 PM) 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 -- 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] [subversion] (JENKINS-15249) Missing support for externals in 1.4.2 for subversion working copy version 1.7
Jan Linnenkohl closed JENKINS-15249 as Fixed Missing support for externals in 1.4.2 for subversion working copy version 1.7 Ticket closed. Change By: Jan Linnenkohl (11/Jul/13 12:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13790) Subversion externals fail
Jan Linnenkohl commented on JENKINS-13790 Subversion externals fail Hi Nick, the problem is, that the "patched" svnkit is already in use, but the "patches" for subversion 1.7 are still missing. May be you could write to the mailing list, because here seems none of the plugin developers to listen. This message is automatically generated by JIRA. 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
Jan Linnenkohl commented on JENKINS-13790 Subversion externals fail I just have the checked the sources and found out, that only the wc16 is supported for the externals. There is a missing support for wc17. So in an old project, where still the working copy was in format 16, I was able to update. Using a fresh checkout it generates version 17 and the externals fail. So there is a need to update the patched svnkit to support the new working copy format. This message is automatically generated by JIRA. 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
Jan Linnenkohl commented on JENKINS-13790 Subversion externals fail I went now back to use subversion 1.6 working copy format (main settings) and it works fine. Be sure that you delete the existing working copies rerun the builds. Otherwise it keep using the 1.7 working copy. This message is automatically generated by JIRA. 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
Jan Linnenkohl created JENKINS-15249 Missing support for externals in 1.4.2 for subversion working copy version 1.7 Issue Type: Bug Assignee: Unassigned Components: subversion Created: 20/Sep/12 11:34 AM Description: The modified svnkit didn't support the "externals" for WC17. The WC16 works (subversion 1.6). Without knowing the externals, an update of an library doesn't result in an rebuild of the projects. Project: Jenkins Priority: Blocker Reporter: Jan Linnenkohl This message is automatically generated by JIRA. 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
Jan Linnenkohl updated JENKINS-13790 Subversion externals fail We are also working with a lot of externals in our projects. And they still not working in 1.4.2 / 1.446.1 (configured to use workspace 1.7). How can we help, to find a resolution for this problem? Change By: Jan Linnenkohl (31/Jul/12 3:35 PM) 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-13790) Subversion externals fail
Jan Linnenkohl updated JENKINS-13790 Subversion externals fail Change By: Jan Linnenkohl (31/Jul/12 4:02 PM) Fix 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-12194) warnings dashboard view portlet, ability to filter by category or type
[ https://issues.jenkins-ci.org/browse/JENKINS-12194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160050#comment-160050 ] Jan Linnenkohl commented on JENKINS-12194: -- This would be very helpful for us. Because we have a lot of different types and we always make our statistics by hand. Just a small filter field with a Type selection would be very nice. warnings dashboard view portlet, ability to filter by category or type -- Key: JENKINS-12194 URL: https://issues.jenkins-ci.org/browse/JENKINS-12194 Project: Jenkins Issue Type: Improvement Components: dashboard-view, warnings Affects Versions: current Reporter: Greg Moncreaff Assignee: Peter Hayes with parsers, either built in or hand crafted jelly script, you can throw a lot of different data into the warnings buckets. it would be nice to be able to select from either category or type to indicate which portions of those data you want on a dashboard view. CONOPS: lots of little quick jobs that each have multiple checkers with associated parsers contributing to warnings, so developers get a soup to nuts validation of their commit best practice review wants to see sorting/trending of each of those warnings separately to look for hot spots, etc. in this case its not realistic to split the jobs into tool name filterable pieces (too many jobs, and warnings don't roll up if jobs are connected in a stream) its also not realistic (no matter how desirable) that those individual checkers will get their own plugins and columns in analysis-code in any reasonable amount of time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
