[JIRA] [pretested-integration-plugin] (JENKINS-23901) Job SCM changes are not valid after running plugin (our case 11771)
Title: Message Title Lars Kruse resolved as Cannot Reproduce No activity on this case, and no ability to reproduce makes us close it - we will have to have new reports if we shall work on it. Jenkins / JENKINS-23901 Job SCM changes are not valid after running plugin (our case 11771) Change By: Lars Kruse Status: Open Resolved Resolution: Cannot Reproduce 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] [pretested-integration-plugin] (JENKINS-31128) Add Matrix Project compatibility (investigate) (our case 13748)
Title: Message Title Lars Kruse commented on JENKINS-31128 Re: Add Matrix Project compatibility (investigate) (our case 13748) As it turned out in the investigation, "proper" Matrix Project compatibility isn't a quick fix. JENKINS-31128 Investigate Matrix Job Compatibility Below is the result of investigating if SCM extensions could be used to solve our problem. TL;DR Writing SCM extensions for Pretested Integration will not solve our Matrix Project related problems. But... The problems Pretested Integration for Matrix jobs suffers are as follows: Adding the publisher to the Matrix Job causes the workspace changes in the Matrix Job's workspace to be pushed. However, no merge or verification is ever done there. The Matrix Job only pulls in the SCM changes to test connection before kicking off all its Matrix runs. As a result, the HEAD that was pulled in as a test is pushed ontop of the integration branch, which is not at all what we want. A second problem is that the merge before verification is done separately by all Matrix runs. This results in N different merges and thus N number of partially tested commits, N being the amount of Matrix runs defined. This doesn't match wanted Pretested Integration behaviour, where we want a single commit to be fully tested. A possible solution that came to mind was writing SCM extensions for the Prestested Integration plugin, allowing the merge to happen in the Matrix Job as part of the SCM phase. This seemingly solves the first problem, since a merge happens in the Matrix Job. However, this will still result in a poorly tested commit being pushed, since the second problem persists. The possible solution here is to do the merge before the Matrix Job and having the Matrix Runs pull in and verify that single commit before running the publisher (in this case it would make sense putting the publisher on the Matrix Job). After another discussion we thought about having the SCM extension push the merge changes back to the ready branch. This might offer a solution. Add Comment This message was sent by Atlassian JIRA
[JIRA] [pretested-integration-plugin] (JENKINS-25542) Git SHA is not translated to branch and checked accordingly (our case 12284)
Title: Message Title Lars Kruse closed an issue as Duplicate Jenkins / JENKINS-25542 Git SHA is not translated to branch and checked accordingly (our case 12284) Change By: Lars Kruse Status: Open Closed Resolution: Duplicate 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] [pretested-integration-plugin] (JENKINS-29377) Date formatting should be UTC in accumulated msg (Praqma case 13299)
Title: Message Title Lars Kruse closed an issue as Not A Defect We don't want to alter git's ordinal squash commit message - if you don't like it - don't squash - clean up your local history yourselv, and deliver just one commit - thats supported. Jenkins / JENKINS-29377 Date formatting should be UTC in accumulated msg (Praqma case 13299) Change By: Lars Kruse Status: Open Closed Resolution: Not A Defect 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] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)
Title: Message Title Lars Kruse resolved as Cannot Reproduce Resolving this as irrelevant, since we haven't hear anything on this topic for almost 1 1/2 year Jenkins / JENKINS-25831 Branch not found (our case 12373) Change By: Lars Kruse Status: Open Resolved Resolution: Cannot Reproduce 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] [pretested-integration-plugin] (JENKINS-27515) Stack trace if push fails - build shows successful but is not (Praqma case 12833)
Title: Message Title Lars Kruse closed an issue as Fixed This is fixed. The publisher is now a Recorder which CAN change the build status. So you will not get this type of error anymore. Jenkins / JENKINS-27515 Stack trace if push fails - build shows successful but is not (Praqma case 12833) Change By: Lars Kruse Status: Open Closed Resolution: Fixed 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] [pretested-integration-plugin] (JENKINS-32385) Check for misconfigurations (Praqma case 14105)
Title: Message Title Lars Kruse commented on JENKINS-32385 Re: Check for misconfigurations (Praqma case 14105) This issue continues on GHI: https://github.com/Praqma/pretested-integration-plugin/issues/11 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] [pretested-integration-plugin] (JENKINS-25512) If two branchheads points to same commit, wrong branch might get deleted (our case 12269)
Title: Message Title Lars Kruse commented on JENKINS-25512 Re: If two branchheads points to same commit, wrong branch might get deleted (our case 12269) This issue continues at GHI: https://github.com/Praqma/pretested-integration-plugin/issues/10 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] [pretested-integration-plugin] (JENKINS-25810) Only show postbuild step for supported job types (our case 12369)
Title: Message Title Lars Kruse commented on JENKINS-25810 Re: Only show postbuild step for supported job types (our case 12369) This issue continues one GitHub Issues: https://github.com/Praqma/pretested-integration-plugin/issues/9 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] [pretested-integration-plugin] (JENKINS-28370) Error when trying to integrate to non-existing integration branch (Praqma case 13015)
Title: Message Title Lars Kruse commented on JENKINS-28370 Re: Error when trying to integrate to non-existing integration branch (Praqma case 13015) This issue continues on GitHub Issues - come join us: https://github.com/Praqma/pretested-integration-plugin/issues/8 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] [pretested-integration-plugin] (JENKINS-25069) Plugin does not work with stash-git-hook (our case 12132)
Title: Message Title Lars Kruse closed an issue as Done Reported solved by end-user https://trello.com/c/welUuFzX/60-jenkins-25069-pretest-plugin-does-not-work-with-stash-webhooks-triggering#comment-56c324bee781644555ba562f Jenkins / JENKINS-25069 Plugin does not work with stash-git-hook (our case 12132) Change By: Lars Kruse Status: Open Closed Resolution: Done 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] [pretested-integration-plugin] (JENKINS-32362) Plugin should start with a clean workspace (our case 14096)
Title: Message Title Lars Kruse closed an issue as Done Fixed as a side effect in another issue Jenkins / JENKINS-32362 Plugin should start with a clean workspace (our case 14096) Change By: Lars Kruse Status: Open Closed Resolution: Done 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] [pretested-integration-plugin] (JENKINS-25872) Plugin doesn't use account's identity (our case 12395)
Title: Message Title Lars Kruse commented on JENKINS-25872 Re: Plugin doesn't use account's identity (our case 12395) This issue is transferred to GitHub Issues. Please follow https://github.com/Praqma/pretested-integration-plugin/issues/4 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] [pretested-integration-plugin] (JENKINS-25805) Support for maven projects type (our case 12361)
Title: Message Title Lars Kruse commented on JENKINS-25805 Re: Support for maven projects type (our case 12361) This case continues it's life on GitHub Issue in the repository where it belongs. Please comment and follow this issue on https://github.com/Praqma/pretested-integration-plugin/issues/7 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] [pretested-integration-plugin] (JENKINS-32383) Java 1.6 compliance (Praqma case 14102)
Title: Message Title Lars Kruse resolved as Not A Defect Jenkins / JENKINS-32383 Java 1.6 compliance (Praqma case 14102) Change By: Lars Kruse Status: Reopened Resolved Resolution: Not A Defect 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] [pretested-integration-plugin] (JENKINS-32360) Configuration option to mention ready branch name in commit message (our case 14095)
Title: Message Title Lars Kruse updated an issue Jenkins / JENKINS-32360 Configuration option to mention ready branch name in commit message (our case 14095) Change By: Lars Kruse This is a feature.But what's the problem it solves?As a _bla bla ha_ I want to _bla bla bla ha_ so that _bla bla bal_I'm just saying the I's not clear what the problem is: Why should the branch be mentioned in the commit message - it's not (that normal) to put a branch name in a commit message. Personally I never do it - but I rarely (as in "haven't yet") seen any other developers do it either.Let's get a description of the problem we're trying to solve, and then lets see somebody actually watch or vote for this issue, before we hit the keyboard! 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] [pretested-integration-plugin] (JENKINS-31128) Add Matrix Project compatibility (investigate) (our case 13748)
Title: Message Title Lars Kruse closed an issue as Fixed Jenkins / JENKINS-31128 Add Matrix Project compatibility (investigate) (our case 13748) Change By: Lars Kruse Status: Resolved Closed 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] [clearcase-plugin] (JENKINS-30666) Change maintainer
Title: Message Title Lars Kruse created an issue Jenkins / JENKINS-30666 Change maintainer Issue Type: Bug Assignee: Lars Kruse Components: clearcase-plugin Created: 27/Sep/15 8:30 PM Priority: Minor Reporter: Lars Kruse Vincent is looking for a new maintainer for this plugin. We will transfer maintenance to [Praqma|www.praqma.com] and support it under the Joint Open Source Roadmap Alliance [Josra|www.josra.org]. Josra is also maintaining the ClearCase UCM plugin . Add Comment
[JIRA] [logging-plugin] (JENKINS-15153) Custom logging template (our case 9584)
Title: Message Title Lars Kruse closed an issue as Not A Defect There doesn't seem to be any demand for this feature Jenkins / JENKINS-15153 Custom logging template (our case 9584) Change By: Lars Kruse Status: Open Closed Resolution: NotADefect 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] [clearcase-ucm-plugin] (JENKINS-18521) Only default Promotion levels are supported (praqma case 9642)
Title: Message Title Lars Kruse closed an issue as Fixed There doesn't seem to be any damand for this feature Jenkins / JENKINS-18521 Only default Promotion levels are supported (praqma case 9642) Change By: Lars Kruse Status: Open Closed Resolution: Fixed 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] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin
Lars Kruse updated JENKINS-23901 Job SCM changes are not valid after running plugin Change By: Lars Kruse (21/Jul/14 2:41 PM) Assignee: AlexanderUldall This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin
Lars Kruse updated JENKINS-23901 Job SCM changes are not valid after running plugin Card on JOSRA Pretested Integration roadmap board This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin
Lars Kruse commented on JENKINS-23901 Job SCM changes are not valid after running plugin Hi Morten, could you attach the log from build #119, either here or to the Trello card This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [logging] (JENKINS-18456) Jenkins Job Current Log Status ( our case 9603)
Lars Kruse commented on JENKINS-18456 Jenkins Job Current Log Status ( our case 9603) Hi Avi Sorry for the silence - it's been vacation time at the office, but I now had a chance to talk to our developers and we have dicussed you issue. Our first estimate is that we recon that we could produce a plugin that does what you are asking for in about two working days (15 hrs). If you choose to collaborate with us, and want us to implement such a plugin, it will be Open Source, released to the community, available for everyone, installable from the "manage jenkins" menu on your own Jenkins server and it will include 12 months full warranty on the implemented and agreed features. Please feel free to contact me on supp...@praqma.com if you'd like a firm (fixed price) quote on a plugin. Cheers Lars Kruse This message is automatically generated by JIRA. 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] [logging] (JENKINS-18456) Jenkins Job Current Log Status ( our case 9603)
Lars Kruse commented on JENKINS-18456 Jenkins Job Current Log Status ( our case 9603) Ok, so something like the description setter plugin https://wiki.jenkins-ci.org/display/JENKINS/Description+Setter+Plugin Except you want it to scan the console during execution (and not as a post build action), and then update the description for every match it finds. This message is automatically generated by JIRA. 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] [logging] (JENKINS-18456) Jenkins Job Current Log Status ( our case 9603)
Lars Kruse resolved JENKINS-18456 as Wont Fix Jenkins Job Current Log Status ( our case 9603) I'm resolving this issue with reference to robjohncox's answer on stackoverflow. It turns our the the big-unsplitable build is run by FinalBuilder, which basically makes it the responsibility of FinalBuilder to give you the insight you need. To use Jenkins, you should let Jenkins execute the jobs rather than FinalBuilder, then you would be able to see what your looking for in the console output - as the job executes. Change By: Lars Kruse (04/Jul/13 11:04 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. 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] [logging] (JENKINS-18456) Jenkins Job Current Log Status ( our case 9603)
Lars Kruse commented on JENKINS-18456 Jenkins Job Current Log Status ( our case 9603) Sorry for shutting you down too soon. It looks like you are trying to implement a divide-and-conquer strategy for a huge job that's controlled by FinalBuilder. The easiest way to have Jenkins break it down, is to hand the responsibility of the execution over to Jenkins. Your first suggestion, to add a prefix to each line in the console output based on the current project being compiled makes me think that in order to do that Jenkins would have to know what project is being compiled - but since your using FinalBuilder - which is then creating the output for that particular compilation, makes me think that it's really FinalBuilder that should do the pre-fix. Where does the Project name you want in the pre-fix come from? You second suggestion, to update the job description during runtime with the project being build would require a plugin, that knew the name of the project - But isn't it FinalBuilder who knows what is currently being build? The way I see it, wrapping it all up in one-big-FinalBuilder job is really what needs to be broken down. Maybe I'm missing your points. If you thing I am, then please throw some examples (screen shorts, logs, configurations) to clarify, what you are trying to achieve. This message is automatically generated by JIRA. 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] [postbuild-task] (JENKINS-12793) Why the Post Steps and Post-build Actions are not executed after the build finished
Lars Kruse commented on JENKINS-12793 Why the Post Steps and Post-build Actions are not executed after the build finished A few ideas: Are you absolutely sure that you are using the same credentials when you test it (the service account you use for Jenkins), as you do when you run in a Jenkins job? Try to run the command …set in your script it in both test and jenkins. It will list alle environmenr variables. What differs? You could also try to redirect ERROUT into STDOUT using 21 so you are sure you capture all the innformation 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 -- 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] [clearcase-ucm] (JENKINS-16487) Promotion Level being set to INITIAL - our case 8471
Lars Kruse resolved JENKINS-16487 as Not A Defect Promotion Level being set to INITIAL - our case 8471 This case does represent an issue; the only the default promotion levels are supported. But since Ronan who opened this case, clearly states that this is apparently not Ronan's concern but rather that the plugin is trying to change the promotion level ...al all This is by design: We're looking for a baseline with a certain promotion level, and when we're done with it, we'll flip the promotion level - either to the next - or to rejected - dependent on the outcome of the build step. If we didn't flip the promotion level , the build would simple build the same baseline over and over again. There is a workaround for this based on setting the promotion level to the option "ANY" in this mode the plugin will build the lates baseline - no matter what promotion level it has. I'm closing this "Not a defect" and opening a new "Only default Promotion levels are supported" instead. Change By: Lars Kruse (26/Jun/13 7:09 PM) Status: Reopened Resolved Resolution: NotADefect This message is automatically generated by JIRA. 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] [clearcase-ucm] (JENKINS-18521) Only default Promotion levels are supported
Lars Kruse created JENKINS-18521 Only default Promotion levels are supported Issue Type: Improvement Assignee: Praqma Support Components: clearcase-ucm Created: 26/Jun/13 7:06 PM Description: The plugin is supporting the default promotion levels: INITIAL BUILT TESTED RELEASED REJECTED If a project is using a custom defined list of promotion levels they are not supported. We need a sponsor for this feature - contact us at supp...@praqma.com if you want a quote on this feature. Project: Jenkins Labels: clearcase-ucm clearcase promotion Priority: Minor Reporter: Lars Kruse This message is automatically generated by JIRA. 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] [component] (JENKINS-18507) some command can't exit in the execute windows batch command (praqma case 9630)
Lars Kruse updated JENKINS-18507 some command cant exit in the execute windows batch command (praqma case 9630) Change By: Lars Kruse (26/Jun/13 7:27 PM) Component/s: windows-exe-runner This message is automatically generated by JIRA. 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] [batch-task] (JENKINS-18507) some command can't exit in the execute windows batch command (praqma case 9630)
Lars Kruse updated JENKINS-18507 some command cant exit in the execute windows batch command (praqma case 9630) Moving this case the batch-task component. Change By: Lars Kruse (26/Jun/13 7:30 PM) Assignee: PraqmaSupport Component/s: batch-task Component/s: component Component/s: windows-exe-runner This message is automatically generated by JIRA. 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] [clearcase-ucm] (JENKINS-18281) Possibility to remove the contributing activities from the change set of the build, case 9488
Lars Kruse commented on JENKINS-18281 Possibility to remove the contributing activities from the change set of the build, case 9488 Hi Marc I think you are right; using -nmerge is not really the solution to the original problem; Being that files show up more than once, due to being changed in several versions and in contributing activities (versions on different branches). The phenomena "contributing activity" is only relevant when comparing two baselines on the same stream - in other words, in the context of the plugin it's only an issue in poll-self mode. In poll-child and poll-sibling, the changesets are showing correctly as is ...right? I'm thinking of a possible solution to the original problem: Could it be that we offer an option to use a "Washed Change Set" which should mean that a) We only report versions, that are on the same stream (no contributing activities) b) If an element is included in the activity in more than one version, we only report the newest We could quite easy to do this, We could continue to use the currently generated output from the diffbl command, but then simply "wash" it before we display it - when the job runs in poll-self mode. I didn't get this idea before you mentioned it, but actually it has anopter property which I like a lot: It would report a changeset, that is less ClearCase'ish and more like what you would expect to see from VCS such as SVN, Git and Mercurial. We could simply make this feature an option (a checkbox), so old-school ClearCase nerds could continue to make sense out of the same element being represented more than once in the same change set - if they want to Let me know what you think? Lars This message is automatically generated by JIRA. 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] [clearcase-ucm] (JENKINS-18278) Change set is not correctly calculated after a rebase of the integration stream, case 9489
Lars Kruse commented on JENKINS-18278 Change set is not correctly calculated after a rebase of the integration stream, case 9489 It's actually even easier to implement in the context of the ClearCse UCM plugin, since the component ($component) and the stream ($stream) are already available from the job context we could simply do something like: cleartool lsbl -fmt "%Xn\n" -stream $stream -component $component and report the changeset by comparing the most recent baseline (the current) with the second most recent baseline (the immediately preceding one on the same stream). If the output only has one baseline, it means that the current baseline is the first baseline ever built in this context, and we simply don't report a changeset at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [clearcase-ucm] (JENKINS-18280) Provide an option to not delete view-private files at the start of each build, case 9487
Lars Kruse commented on JENKINS-18280 Provide an option to not delete view-private files at the start of each build, case 9487 Yep - no problemo, we can do that! This message is automatically generated by JIRA. 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] [matrix-reloaded] (JENKINS-16591) Matrix Reloaded plugin - our case 8520
Lars Kruse commented on JENKINS-16591 Matrix Reloaded plugin - our case 8520 This issue is caused by the design of the plugin: The Matrix Reloaded feature is an action that is attached to the executed Matrix build - at the time of the execution. Consequently the reload feature is not available on builds that was executed before the plugin was installed. This was not clear in the documentation, but it has been updated now as a note: Reload option sometimes not available The Matrix Reloaded link is only available on the builds that were executed while the Matrix Reloaded Plugin was actually installed. Sometimes you may see a Matrix Build, that doesn't offer the Reload option, even though you did install the plugin. When that happens you can simply do a regular re-run (of the entire matrix) and the Matrix Reloaded option will be available on the new result. IF this is not satisfactory to you guys, then we will have to change the behavior of the plugin, so that it upon installation scans the whole master for currently existing Matrix builds and apply the action to all of them. It does however seem to be a little overkill, so we need to see an explicit demand for this before we estimate/implement. I'm closing this issue again - It's by design This message is automatically generated by JIRA. 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] [matrix-reloaded] (JENKINS-16591) Matrix Reloaded plugin - our case 8520
Lars Kruse resolved JENKINS-16591 as Wont Fix Matrix Reloaded plugin - our case 8520 It's by design - The documentation is now updated! Change By: Lars Kruse (18/Jun/13 10:39 AM) Status: Reopened Resolved Resolution: WontFix This message is automatically generated by JIRA. 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-17372) Error looking up function 'CreateSymbolicLinkW' (our case 8908)
Lars Kruse commented on JENKINS-17372 Error looking up function CreateSymbolicLinkW (our case 8908) This bug is not related to the PRQA plugin, but to the fact that "Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available" https://issues.jenkins-ci.org/browse/JENKINS-17343 Praqma support has been in contact with Klaus who verified that Jenkins was indeed upgraded too along with the upgrade of the PRQA plugin. Rolling Jenkins back to a version 1.505 solved 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 -- 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-17015) Test issue
Lars Kruse resolved JENKINS-17015 as Wont Fix Test issue Just testing the RQM Jira component Change By: Lars Kruse (01/Mar/13 2:44 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. 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-17015) Test issue
Lars Kruse closed JENKINS-17015 as Wont Fix Test issue Change By: Lars Kruse (01/Mar/13 2:44 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-16072) Missing baselines issue with latest plugin - our case 8149
Lars Kruse resolved JENKINS-16072 as Fixed Missing baselines issue with latest plugin - our case 8149 Fixed in 1.3.2 Change By: Lars Kruse (23/Feb/13 11:30 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 -- 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-16804) Better exception handling in core, case 8644
Lars Kruse resolved JENKINS-16804 as Fixed Better exception handling in core, case 8644 Fixed in 1.3.5 Change By: Lars Kruse (23/Feb/13 11:39 AM) 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 -- 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-1682) Pre-tested commit feature
Lars Kruse commented on JENKINS-1682 Pre-tested commit feature Hmmm! I agree that the implementation of the support for pre-tested commit will have to be laid on each individual plugin. The point that I was advocating in Paris was, that there ought to be a recommended approach that the SCM plugin developers should/could use when implementing it. Our rationale is that all pre-test commits - regardless of the underlying VCS - has a generic character: Pre-build step (The pre-build step is where the SCM extension currently has it's foot print) Establish a workspace representing the tip of the branch Merge 'something' into the workspace (the 'something' can be a patch, a pull, a merge from another branch ... - this is up to the SCM plugin developer to decide) The build step If the merge succeeded the job continues to the build step - the user simply implement the test that should qualify the commit - typically something relatively simple like build and run the unit test - but the actual test is of course up to the user of the plugin to decide. The post-build step The pre-tested commit feature will have to have a foot print in the post-build step to decide if the current state of the workspace is accepted as a new commit - or not) If build is successful accept the merge as a new commit, if not then reject it an roll back the workspace (exactly what is going to happen her is up to the developer of the SCM plugin to decide) Suggested solution Currently the "generic" approach is implemented by having the SCM plugins that supports that pre-tested commit feature extend both SCM and the Notifier (to get a foot print in the post build step). We suggest that the the SCM extension simply is enhanced so that it has a wrap-up method that is called in the post-build step - those SCM plugins that want to make decisions regarding the workspace could implement and override the wrap-up method - those who doesn't could simply do nothing - and everything would stay the same. This approach would be backwards compatible and those SCM plugins that want to implement support for pre-tested commits wouldn't have to use the, not so obvious and kind of tedious, approach to have their SCM plugin extend the Notifier as well. Lars Kruse This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14240) Changlelog is missing user names
Lars Kruse commented on JENKINS-14240 Changlelog is missing user names Scheduled to be included in our next release This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14239) Sometimes CCUCM finds baselines in other masterships
Lars Kruse commented on JENKINS-14239 Sometimes CCUCM finds baselines in other masterships Scheduled to be released in next release (July) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13944) Missing hyperlink type tag in Clearcase does not fail the build
Lars Kruse commented on JENKINS-13944 Missing hyperlink type tag in Clearcase does not fail the build Scheduled to be implemented in next release: The job shall be unstable in the situation described. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13944) Missing hyperlink type tag in Clearcase does not fail the build
Lars Kruse assigned JENKINS-13944 to Christian Wolfgang Missing hyperlink type tag in Clearcase does not fail the build Change By: Lars Kruse (29/Jun/12 3:58 PM) Assignee: ChristianWolfgang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13964) Enhance the posted deliveries polling, so it can work 'as normal'
[ https://issues.jenkins-ci.org/browse/JENKINS-13964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Sorensen reassigned JENKINS-13964: --- Assignee: Leif Sorensen Enhance the posted deliveries polling, so it can work 'as normal' - Key: JENKINS-13964 URL: https://issues.jenkins-ci.org/browse/JENKINS-13964 Project: Jenkins Issue Type: Improvement Components: clearcase-ucm Reporter: Leif Sorensen Assignee: Leif Sorensen The process for posted deliveries is a bit different from normal: on top of making the baseline, the developer must issue a Deliver Baseline command. A special Posted deliver object is then created, and the mastership of the development stream is transferred to the integration stream site. The plugin will detect the posted delivery, and resume and complete (or cancel) the delivery. As a result of this, the mastership of the stream will be transferred back to the origin. Notice: The ClearCase posted delivery process does not transfer the mastership of the baseline - for that reason the promotion level of the baseline cannot be changed, but is left as INITIAL. Tags can also not be updated. The plugin should be enhanced, so it can work in exactly the same way as in a single site setup: the developer just creates baselines, and everything else happens automatically. -- 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
[JIRA] (JENKINS-13964) Enhance the posted deliveries polling, so it can work 'as normal'
[ https://issues.jenkins-ci.org/browse/JENKINS-13964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Sorensen resolved JENKINS-13964. - Resolution: Fixed Fixed in version 1.1.0 Enhance the posted deliveries polling, so it can work 'as normal' - Key: JENKINS-13964 URL: https://issues.jenkins-ci.org/browse/JENKINS-13964 Project: Jenkins Issue Type: Improvement Components: clearcase-ucm Reporter: Leif Sorensen Assignee: Leif Sorensen The process for posted deliveries is a bit different from normal: on top of making the baseline, the developer must issue a Deliver Baseline command. A special Posted deliver object is then created, and the mastership of the development stream is transferred to the integration stream site. The plugin will detect the posted delivery, and resume and complete (or cancel) the delivery. As a result of this, the mastership of the stream will be transferred back to the origin. Notice: The ClearCase posted delivery process does not transfer the mastership of the baseline - for that reason the promotion level of the baseline cannot be changed, but is left as INITIAL. Tags can also not be updated. The plugin should be enhanced, so it can work in exactly the same way as in a single site setup: the developer just creates baselines, and everything else happens automatically. -- 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
[JIRA] (JENKINS-13964) Enhance the posted deliveries polling, so it can work 'as normal'
Leif Sorensen created JENKINS-13964: --- Summary: Enhance the posted deliveries polling, so it can work 'as normal' Key: JENKINS-13964 URL: https://issues.jenkins-ci.org/browse/JENKINS-13964 Project: Jenkins Issue Type: Improvement Components: clearcase-ucm Reporter: Leif Sorensen The process for posted deliveries is a bit different from normal: on top of making the baseline, the developer must issue a Deliver Baseline command. A special Posted deliver object is then created, and the mastership of the development stream is transferred to the integration stream site. The plugin will detect the posted delivery, and resume and complete (or cancel) the delivery. As a result of this, the mastership of the stream will be transferred back to the origin. Notice: The ClearCase posted delivery process does not transfer the mastership of the baseline - for that reason the promotion level of the baseline cannot be changed, but is left as INITIAL. Tags can also not be updated. The plugin should be enhanced, so it can work in exactly the same way as in a single site setup: the developer just creates baselines, and everything else happens automatically. -- 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
[JIRA] (JENKINS-13787) Error when job is running on slave
[ https://issues.jenkins-ci.org/browse/JENKINS-13787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kruse resolved JENKINS-13787. -- Resolution: Duplicate Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-13803 Error when job is running on slave -- Key: JENKINS-13787 URL: https://issues.jenkins-ci.org/browse/JENKINS-13787 Project: Jenkins Issue Type: Bug Components: prqa Reporter: Lars Kruse Assignee: Lars Kruse Labels: Praqma If I set up the PRQA plugin on a Jenkins running on my machine (just install the official 1.441 war file and start it via java -jar jenkins.war, everything works fine. Now if I setup my machine to run as a slave and let the job be triggered by the master somewhere else (also version 1.441), I get the following error: This job will try to create a report with the following selected parameters: QAR selected project file:Sources\QAC\LibFusion\LibFusion.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources\QAC\LibFusion\LibFusion.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml Viewer dummy not available, result will not be rendered. Generating - Please wait... Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xhtml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report-Main.xhtml Finished remote reporting. Found report. Attempting to copy Compliance Report.xhtml to artifacts directory: /home/qqmthk1/.jenkins/jobs/OFRF_LibFusion_QAC/builds/2012-05-11_17-32-05/archive Attempting to copy report to following target: Compliance Report.xhtml Succesfully copied report ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception java.lang.NullPointerException at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Notifying upstream projects of job completion Finished: FAILURE -- 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
[JIRA] (JENKINS-13803) PRQA Plugin fails during the publishing phase with NULL pointer exception
[
https://issues.jenkins-ci.org/browse/JENKINS-13803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162839#comment-162839
]
Lars Kruse commented on JENKINS-13803:
--
Hi Julian
We actually got this error report from you via Jason, PRQA. I filed it as
https://issues.jenkins-ci.org/browse/JENKINS-13787 but I will close that as a
duplicate.
We tried to get this fix into 1.0.2 as well but we could not reproduce it in
our lab. Even when the master was on Linux and the slave was on windows -
started with the java web start (which essentially is a user process).
Hmmm - I'm not suspecting the 1.441 version to really be the issue.
Actually the stack trace you have given us is helpful, But I believe in this
case, we would welcome any relevant logs you can produce.
Please attach them to a mail and send them to supp...@praqma.net.
Cheers
PRQA Plugin fails during the publishing phase with NULL pointer exception
-
Key: JENKINS-13803
URL: https://issues.jenkins-ci.org/browse/JENKINS-13803
Project: Jenkins
Issue Type: Bug
Components: prqa
Environment: Master: linux
Slave: Windows 7
Jenkins 1.441
Reporter: Julian Requejo
Assignee: Lars Kruse
PRQA plugin generates reports correctly, but fails during publishing phase.
{noformat}
At revision 1572
no change for https://xx/xx since the previous build
This job will create a report with the following selected parameters:
QAR selected project file:Sources\QAC\xx\xx.prj
QAR selected product: QAC
QAR selected report type: Compliance
Beginning report generation with the following command:
qaw QAC Sources\QAC\xx\xx.prj -maseq qar %Q %P+ %L+ -po
qar::report_type=Compliance\ Report -po qar::project_name=%J -po
qar::output_path=c:\_dev\jenkins-int\workspace\xx_QAC -po
qar::viewing_program=dummy -po qar::report_format=xhtml
Viewer dummy not available, result will not be rendered.
Generating - Please wait...
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xml
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xhtml
Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report-Main.xhtml
Finished remote reporting.
Found report. Attempting to copy Compliance Report.xhtml to artifacts
directory: /home/xx/.jenkins/jobs/xx_QAC/builds/2012-05-16_17-11-12/archive
Attempting to copy report to following target: Compliance Report.xhtml
Succesfully copied report
ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted
due to exception
java.lang.NullPointerException
at
net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645)
at hudson.model.Build$RunnerImpl.post2(Build.java:162)
at
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614)
at hudson.model.Run.run(Run.java:1429)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Notifying upstream projects of job completion
Finished: FAILURE
{noformat}
I have tested this using three configurations, all with Jenkins 1.441
- Single Jenkins web app running on my local machine (Windows 7): it works
- Master-slave configuration, *both* on my local machine (Windows 7), slave
as a user process: it works
- Master-slave configuration, master on a Linux box, slave on my local
Windows 7 machine (Windows 7), slave as a user process: it does *not* work
and triggers the error above.
I could try upgrading to a newer Jenkins, but I'd strongly prefer not to
unless shown to be essential.
I'll be happy to provide further logs. Thanks
--
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
[JIRA] (JENKINS-13787) Error when job is running on slave
[ https://issues.jenkins-ci.org/browse/JENKINS-13787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kruse updated JENKINS-13787: - Description: If I set up the PRQA plugin on a Jenkins running on my machine (just install the official 1.441 war file and start it via java -jar jenkins.war, everything works fine. Now if I setup my machine to run as a slave and let the job be triggered by the master somewhere else (also version 1.441), I get the following error: This job will try to create a report with the following selected parameters: QAR selected project file:Sources\QAC\LibFusion\LibFusion.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources\QAC\xx\yy.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\xx_QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml Viewer dummy not available, result will not be rendered. Generating - Please wait... Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xml Writing c:\_dev\jenkins-int\workspace\xx_QAC\Compliance Report.xhtml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report-Main.xhtml Finished remote reporting. Found report. Attempting to copy Compliance Report.xhtml to artifacts directory: /home/qqmthk1/.jenkins/jobs/xx_QAC/builds/2012-05-11_17-32-05/archive Attempting to copy report to following target: Compliance Report.xhtml Succesfully copied report ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception java.lang.NullPointerException at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Notifying upstream projects of job completion Finished: FAILURE was: If I set up the PRQA plugin on a Jenkins running on my machine (just install the official 1.441 war file and start it via java -jar jenkins.war, everything works fine. Now if I setup my machine to run as a slave and let the job be triggered by the master somewhere else (also version 1.441), I get the following error: This job will try to create a report with the following selected parameters: QAR selected project file:Sources\QAC\LibFusion\LibFusion.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources\QAC\LibFusion\LibFusion.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml Viewer dummy not available, result will not be rendered. Generating - Please wait... Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xhtml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report-Main.xhtml Finished remote reporting. Found report. Attempting to copy Compliance Report.xhtml to artifacts directory: /home/qqmthk1/.jenkins/jobs/OFRF_LibFusion_QAC/builds/2012-05-11_17-32-05/archive Attempting to copy report to following target: Compliance Report.xhtml Succesfully copied report ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception java.lang.NullPointerException at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at
[JIRA] (JENKINS-13786) Plugin is not compliant with new Jenkins core gui lay-out
Lars Kruse created JENKINS-13786: Summary: Plugin is not compliant with new Jenkins core gui lay-out Key: JENKINS-13786 URL: https://issues.jenkins-ci.org/browse/JENKINS-13786 Project: Jenkins Issue Type: Improvement Components: prqa Reporter: Lars Kruse Assignee: Lars Kruse the newest Jenkins release doesn't seem to work at all with the PRQA plugin (the dialog doesn't show up) -- 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
[JIRA] (JENKINS-13787) Error when job is running on slave
Lars Kruse created JENKINS-13787: Summary: Error when job is running on slave Key: JENKINS-13787 URL: https://issues.jenkins-ci.org/browse/JENKINS-13787 Project: Jenkins Issue Type: Bug Components: prqa Reporter: Lars Kruse Assignee: Lars Kruse If I set up the PRQA plugin on a Jenkins running on my machine (just install the official 1.441 war file and start it via java -jar jenkins.war, everything works fine. Now if I setup my machine to run as a slave and let the job be triggered by the master somewhere else (also version 1.441), I get the following error: This job will try to create a report with the following selected parameters: QAR selected project file:Sources\QAC\LibFusion\LibFusion.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources\QAC\LibFusion\LibFusion.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml Viewer dummy not available, result will not be rendered. Generating - Please wait... Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report.xhtml Writing c:\_dev\jenkins-int\workspace\OFRF_LibFusion_QAC\Compliance Report-Main.xhtml Finished remote reporting. Found report. Attempting to copy Compliance Report.xhtml to artifacts directory: /home/qqmthk1/.jenkins/jobs/OFRF_LibFusion_QAC/builds/2012-05-11_17-32-05/archive Attempting to copy report to following target: Compliance Report.xhtml Succesfully copied report ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception java.lang.NullPointerException at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:240) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Notifying upstream projects of job completion Finished: FAILURE -- 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
[JIRA] (JENKINS-13611) Misleading error leads to slave disconnecting from master
[ https://issues.jenkins-ci.org/browse/JENKINS-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162724#comment-162724 ] Lars Kruse commented on JENKINS-13611: -- Hi Julian The problem with the new GUI in Jenkins is apparently a problem for quite a lot of the plugins in the community right now - and we will also fix this issue in due time. Right now we are very concerned with not-crashing-the-slaves when something unforeseen happens (missing licenses, missing qaw ...and we have even seen this phenomena ourselves on linux when running jenkins as a service and the QAxxx environment variables aren't loaded from the .bash_profile). IN all these occasion the plugin should fail gracefully with an informative error message of what is wrong. What actually does seem to work is (as you are also hinting in your own description) when both Jenkins master and slave is running as user processes (e.g master is started using java -jar jenkins.war and the slaves are started using the .jnlp interface) everything works fine - also the nice informative error messages. However, we do realize, that we can not allow ourselves the luxury to anticipate that all Jenkins environments out there are run like this. We have created quite a few Plugins, but we must admit, that the PRQA one is the only one, so far, where we have seen such significant differences in behavior, dependent on how the jenkins instance is started. The licence issues are being scrutinized - they do give us grey hair. But I can assure you, that we're in red-alert and we are working on these issues as we speak. We expect to have a new release ready within very short. Misleading error leads to slave disconnecting from master - Key: JENKINS-13611 URL: https://issues.jenkins-ci.org/browse/JENKINS-13611 Project: Jenkins Issue Type: Bug Components: prqa Affects Versions: current Environment: Jenkins 1.441, Windows 7, QAC-7.2F Reporter: Julian Requejo Assignee: Mads Nielsen I'm having some issues running the PQRA Plugin. The [documentation|https://wiki.jenkins-ci.org/display/JENKINS/PRQA+Plugin] is a bit strange. To start with, the screenshot shows a report type quality, even though it says that currently only compliance is available. Then it also says that a tool qaw must be installed, which I don't have anywhere in my installation files. In any case, here is the problem: the plugin seems to not find this qaw tool, and it produces an error that disconnects my slave agent from the master. Started by user X X, xx.xx...@xxx.xx Building remotely on Legoland Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build This job will try to create a report with the following selected parameters: QAR selected project file:Sources//QAC.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources//QAC.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\x\ QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:772) at hudson.FilePath.act(FilePath.java:765) at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:203) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at
[JIRA] (JENKINS-13611) Misleading error leads to slave disconnecting from master
[ https://issues.jenkins-ci.org/browse/JENKINS-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162725#comment-162725 ] Lars Kruse commented on JENKINS-13611: -- ...Oh. I forgot to respond to your offer to post us logs! We might need them later, but for now we are perfectly able to reproduce these issues on our lab environment - so for now we're OK. But I might want to get back to you later ;-) Misleading error leads to slave disconnecting from master - Key: JENKINS-13611 URL: https://issues.jenkins-ci.org/browse/JENKINS-13611 Project: Jenkins Issue Type: Bug Components: prqa Affects Versions: current Environment: Jenkins 1.441, Windows 7, QAC-7.2F Reporter: Julian Requejo Assignee: Mads Nielsen I'm having some issues running the PQRA Plugin. The [documentation|https://wiki.jenkins-ci.org/display/JENKINS/PRQA+Plugin] is a bit strange. To start with, the screenshot shows a report type quality, even though it says that currently only compliance is available. Then it also says that a tool qaw must be installed, which I don't have anywhere in my installation files. In any case, here is the problem: the plugin seems to not find this qaw tool, and it produces an error that disconnects my slave agent from the master. Started by user X X, xx.xx...@xxx.xx Building remotely on Legoland Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build This job will try to create a report with the following selected parameters: QAR selected project file:Sources//QAC.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources//QAC.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\x\ QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:772) at hudson.FilePath.act(FilePath.java:765) at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:203) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:273) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1139) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) Notifying upstream projects of job completion Finished:
[JIRA] (JENKINS-13761) PRAQ plugin disconnects slaves on Linux when tools aren't installed correctly
Lars Kruse created JENKINS-13761: Summary: PRAQ plugin disconnects slaves on Linux when tools aren't installed correctly Key: JENKINS-13761 URL: https://issues.jenkins-ci.org/browse/JENKINS-13761 Project: Jenkins Issue Type: Improvement Components: prqa Environment: Linux (Seen and reproduced on Fedora 16 - 64bit) - but probably affects all Linux version Reporter: Lars Kruse Assignee: Lars Kruse This issue is reported during beta test (on version PRQA plugin version 1.0.1), and reported by the tester like this: Quote begin We have done some tests on Linux - using the plugin causes Jenkins to crash! We don't quite understand this - there was no information in the build log files. However, we were able to run the command to analyse and generate the report as a normal build step as a shell command. We used exactly the same command as the for Windows: - Obviously we used forward slashes in the path to the project - I was wrong about qaw being called qaw.pl - it is called qaw on Linux - qar is called qar.pl on Linux - but we added a symbolic link 'qar-qar.pl' in the qar binary directory. This seems the easiest solution (and perhaps we might include this link in future versions of war) quote end -- 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
[JIRA] (JENKINS-13761) PRAQ plugin disconnects slaves on Linux when tools aren't installed correctly
[ https://issues.jenkins-ci.org/browse/JENKINS-13761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162727#comment-162727 ] Lars Kruse commented on JENKINS-13761: -- The plugin version s 1.0.x aren't compliant with windows. But on the other hand, disconnecting the slave when something goes wrong is not acceptable. This is also related to https://issues.jenkins-ci.org/browse/JENKINS-13611 PRAQ plugin disconnects slaves on Linux when tools aren't installed correctly - Key: JENKINS-13761 URL: https://issues.jenkins-ci.org/browse/JENKINS-13761 Project: Jenkins Issue Type: Improvement Components: prqa Environment: Linux (Seen and reproduced on Fedora 16 - 64bit) - but probably affects all Linux version Reporter: Lars Kruse Assignee: Lars Kruse Labels: Praqma This issue is reported during beta test (on version PRQA plugin version 1.0.1), and reported by the tester like this: Quote begin We have done some tests on Linux - using the plugin causes Jenkins to crash! We don't quite understand this - there was no information in the build log files. However, we were able to run the command to analyse and generate the report as a normal build step as a shell command. We used exactly the same command as the for Windows: - Obviously we used forward slashes in the path to the project - I was wrong about qaw being called qaw.pl - it is called qaw on Linux - qar is called qar.pl on Linux - but we added a symbolic link 'qar-qar.pl' in the qar binary directory. This seems the easiest solution (and perhaps we might include this link in future versions of war) quote end -- 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
[JIRA] (JENKINS-13611) Misleading error leads to slave disconnecting from master
[ https://issues.jenkins-ci.org/browse/JENKINS-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162695#comment-162695 ] Lars Kruse commented on JENKINS-13611: -- Sorry for the very-late reply! First of all - that fact that you haven't installed the tool must not cause Jenkins to blow up. We are sorry for the inconvenience - we are preparing a new release, it will not only behave properly when the tools aren't install, but it will also be linux compliant as well. ... The plugin is a analysis and reporting tool for integration with QAC, QAC++, and later also QAVerify. These tools are provided by Programming Research (http://www.programmingresearch.com) and do static code analysis in appliance with the MISRA rules (among others), you'll need to purchase these tools first - to get the benefit of the plugin. Misleading error leads to slave disconnecting from master - Key: JENKINS-13611 URL: https://issues.jenkins-ci.org/browse/JENKINS-13611 Project: Jenkins Issue Type: Bug Components: prqa Affects Versions: current Environment: Jenkins 1.441, Windows 7, QAC-7.2F Reporter: Julian Requejo Assignee: Mads Nielsen I'm having some issues running the PQRA Plugin. The [documentation|https://wiki.jenkins-ci.org/display/JENKINS/PRQA+Plugin] is a bit strange. To start with, the screenshot shows a report type quality, even though it says that currently only compliance is available. Then it also says that a tool qaw must be installed, which I don't have anywhere in my installation files. In any case, here is the problem: the plugin seems to not find this qaw tool, and it produces an error that disconnects my slave agent from the master. Started by user X X, xx.xx...@xxx.xx Building remotely on Legoland Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 Updating https://xxx/ At revision 1292 no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build no change for Updating https://xxx/ since the previous build This job will try to create a report with the following selected parameters: QAR selected project file:Sources//QAC.prj QAR selected product: QAC QAR selected report type: Compliance Beginning report generation with the following command: qaw QAC Sources//QAC.prj -maseq qar %Q %P+ %L+ -po qar::report_type=Compliance\ Report -po qar::project_name=%J -po qar::output_path=c:\_dev\jenkins-int\workspace\x\ QAC -po qar::viewing_program=dummy -po qar::report_format=xhtml ERROR: Publisher net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier aborted due to exception hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:772) at hudson.FilePath.act(FilePath.java:765) at net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier.perform(PRQANotifier.java:203) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:273) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1139) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249) at
[JIRA] (JENKINS-9764) Fix wrong create-project instruction
[
https://issues.jenkins-ci.org/browse/JENKINS-9764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Kruse resolved JENKINS-9764.
-
Resolution: Fixed
Fix wrong create-project instruction
Key: JENKINS-9764
URL: https://issues.jenkins-ci.org/browse/JENKINS-9764
Project: Jenkins
Issue Type: Bug
Components: clearcase-ucm
Reporter: Lars Kruse
Assignee: Christian Wolfgang
Fix For: current
When PUCM creates the read-only branch for the stream and there is no
Hudson project available the stream is created in the current project
instead, and a warning is issued:'
{{*The build project was not found. You can create the project with:
cleartool mkproject -c Your special build Project -in
rootFolder@\your_pvob yourBuildProject@\your_pvob.*}}
{{*Since there's no build project in ClearCase, pucm have made an extra
stream in your integration stream to build in*}}
Problem is that this instruction is not correct:
If you create the UCM project named Hudson from the GUI you are OK, but if
you created it using the cleartool command above you will get a UCM project
without an integration stream, so it's not enough. you have to go something
like:
{color:green}{{cleartool mkproject -c Hudson project -in RootFolder@\[YOUR
PVOB] hudson@\[YOUR PVOB]}}
{{cleartool mkstream -int -in project:hudson@\[YOUR PVOB] hudson_int@\[YOUR
PVOB]}}
{color}
--
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
[JIRA] (JENKINS-13514) Matrix Reloaded should trigger the same combination in downstream matrix job
[ https://issues.jenkins-ci.org/browse/JENKINS-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162380#comment-162380 ] Lars Kruse commented on JENKINS-13514: -- Right - I makes sense. What we'll do is that we will not require the axises and their values to be a perfect match but instead we will simply analyze which one of the reloaded combinations that makes sense in the context of the down-stream build - the ones that do will be reloaded, the rest will be ignored. If nothing makes sense - nothing will be build. The consequence of this is that a reloaded up-stream build could trigger a down-stream build, that potentially does nothing at all. This may be right in your context, but it's different from the way the plugin behaves today, and in order to make the behavior backwards compliant we intend to set a checkbox on the reloaded plugin, marking if down-stream builds should run in reloaded mode too - or not. Based on this revised design I'd like to raise the estimate with 4 hrs to a total of 20 hrs all in all - including 12 month support of this new feature. What do you think? Matrix Reloaded should trigger the same combination in downstream matrix job Key: JENKINS-13514 URL: https://issues.jenkins-ci.org/browse/JENKINS-13514 Project: Jenkins Issue Type: Improvement Components: matrix-reloaded Affects Versions: current Reporter: Dirk Haun Priority: Minor Attachments: 01-jobA.png, 02-jobB.png When rebuilding parts of a matrix job (using the matrix reloaded plugin), the build will then trigger all downstream jobs. In our case, the downstream jobs are also matrix jobs and we would like that in this case, the downstream jobs are also reloaded, i.e. only the parts that were rebuilt in the upstream job should be built there as well. To reproduce, I've used a setup that somewhat resembles what we have: - 2 matrix jobs, jobA and jobB - jobA has jobB as its downstream job - each job consists of a 3x3 matrix with the axis labelled compiler and os respectively - the compiler axis has values FORTE, GCC, MSC - the os axis has values solaris, linux, windows - the build step is just a echo hello world We're using the Parameterized Build plugin, http://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin, to trigger downstream builds but this can also be reproduced with the standard Build other projects option. The two screenshots show the matrix and which parts are supposed to be rebuild. The second screenshot shows that jobB, when triggered by rebuilding only parts of the jobA matrix, is actually building all 9 combinations, not just the 2 of the upstream job. P.S. I mentioned this problem at the Jenkins User Conference in Paris, in case you remember :) -- 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
[JIRA] (JENKINS-13574) Support for ÚCM posted deliveries
Lars Kruse created JENKINS-13574: Summary: Support for ÚCM posted deliveries Key: JENKINS-13574 URL: https://issues.jenkins-ci.org/browse/JENKINS-13574 Project: Jenkins Issue Type: New Feature Components: clearcase-ucm Environment: ClearCase UCM MultiSite Reporter: Lars Kruse In ClearCase MultiSite it's not possible to deliver directly to the parent (project integration) stream if it has different mastership the the development (current) stream. Example: A developer is working in a USA replica, but the remainder og his team - and the project integration stream - is working in the Denmark replica - so he will have to integrate (deliver) to stream that is in Denmark. For this scenario UCM supports the concept of a posted deliver - this is what happens in ClearCase: - The developer makes a posted deliver - UCM create a special posted deliver object which is attached to the stream and then the mastership of the stream i automatically changed to Denmark. - The information will have to transferred to Denmark replica using the regular shipping server export/import - In Denmark nothing happens automatically: SOMEBODY will have to go to the USA developer's development stream (which is now mastered in Denmark) and issue a deliver -resume command. - When the deliver process is either completed or cancelled, the mastership is automatically transferred back to USA again. The feature request is, that the ClearCase UCM plugin becomes capable of polling for and automatically integratin with posted deliveries (on the receiving site) as if they were just another developer managed by the poll-self mode. -- 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
[JIRA] (JENKINS-13574) Support for ÚCM posted deliveries
[ https://issues.jenkins-ci.org/browse/JENKINS-13574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kruse resolved JENKINS-13574. -- Resolution: Fixed delivered in version 1.0.7 Support for ÚCM posted deliveries - Key: JENKINS-13574 URL: https://issues.jenkins-ci.org/browse/JENKINS-13574 Project: Jenkins Issue Type: New Feature Components: clearcase-ucm Environment: ClearCase UCM MultiSite Reporter: Lars Kruse Assignee: Lars Kruse In ClearCase MultiSite it's not possible to deliver directly to the parent (project integration) stream if it has different mastership the the development (current) stream. Example: A developer is working in a USA replica, but the remainder og his team - and the project integration stream - is working in the Denmark replica - so he will have to integrate (deliver) to stream that is in Denmark. For this scenario UCM supports the concept of a posted deliver - this is what happens in ClearCase: - The developer makes a posted deliver - UCM create a special posted deliver object which is attached to the stream and then the mastership of the stream i automatically changed to Denmark. - The information will have to transferred to Denmark replica using the regular shipping server export/import - In Denmark nothing happens automatically: SOMEBODY will have to go to the USA developer's development stream (which is now mastered in Denmark) and issue a deliver -resume command. - When the deliver process is either completed or cancelled, the mastership is automatically transferred back to USA again. The feature request is, that the ClearCase UCM plugin becomes capable of polling for and automatically integratin with posted deliveries (on the receiving site) as if they were just another developer managed by the poll-self mode. -- 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
[JIRA] (JENKINS-13575) Streams with different mastership are ignored - unless Polling for Posted Deliveries is turned on
[ https://issues.jenkins-ci.org/browse/JENKINS-13575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kruse resolved JENKINS-13575. -- Resolution: Fixed fixed in version 1.0.7 Streams with different mastership are ignored - unless Polling for Posted Deliveries is turned on - Key: JENKINS-13575 URL: https://issues.jenkins-ci.org/browse/JENKINS-13575 Project: Jenkins Issue Type: Bug Components: clearcase-ucm Reporter: Lars Kruse Ooops -- 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
[JIRA] (JENKINS-13514) Matrix Reloaded should trigger the same combination in downstream matrix job
[ https://issues.jenkins-ci.org/browse/JENKINS-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161945#comment-161945 ] Lars Kruse commented on JENKINS-13514: -- I got it! I think. Please confirm that this is what you want: When Matrix reloaded Plugin is installed: IF a Matrix Build is a down-stream job of another job AND the upstream job also is a Matrix build AND the upstream job is started by the Matrix Reloaded Plugin AND the axises of the upstream build and this ave a perfect match (both axises and the values are exactly the same) THEN this build should also be a Matrix Reloaded build, rebuilding with the same settings as the upstream build did. We have set up a test bed that resembles your secretion above, this is where we plan to prove the feature done. http://code.praqma.net/ci/view/JENKINS-13514/ Matrix Reloaded should trigger the same combination in downstream matrix job Key: JENKINS-13514 URL: https://issues.jenkins-ci.org/browse/JENKINS-13514 Project: Jenkins Issue Type: Improvement Components: matrix-reloaded Affects Versions: current Reporter: Dirk Haun Priority: Minor Attachments: 01-jobA.png, 02-jobB.png When rebuilding parts of a matrix job (using the matrix reloaded plugin), the build will then trigger all downstream jobs. In our case, the downstream jobs are also matrix jobs and we would like that in this case, the downstream jobs are also reloaded, i.e. only the parts that were rebuilt in the upstream job should be built there as well. To reproduce, I've used a setup that somewhat resembles what we have: - 2 matrix jobs, jobA and jobB - jobA has jobB as its downstream job - each job consists of a 3x3 matrix with the axis labelled compiler and os respectively - the compiler axis has values FORTE, GCC, MSC - the os axis has values solaris, linux, windows - the build step is just a echo hello world We're using the Parameterized Build plugin, http://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin, to trigger downstream builds but this can also be reproduced with the standard Build other projects option. The two screenshots show the matrix and which parts are supposed to be rebuild. The second screenshot shows that jobB, when triggered by rebuilding only parts of the jobA matrix, is actually building all 9 combinations, not just the 2 of the upstream job. P.S. I mentioned this problem at the Jenkins User Conference in Paris, in case you remember :) -- 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
[JIRA] (JENKINS-13234) Option to specify the view storage location
Lars Kruse created JENKINS-13234: Summary: Option to specify the view storage location Key: JENKINS-13234 URL: https://issues.jenkins-ci.org/browse/JENKINS-13234 Project: Jenkins Issue Type: Improvement Components: clearcase-ucm Affects Versions: current Reporter: Lars Kruse Priority: Minor Snapshot views are created using switches -stgloc -auto. Some existing view storage locations may not be valid though - an option to specify which view storage location to use would be handy. -- 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
[JIRA] (JENKINS-13067) Baselines are created with -identical switch: Don't do that
Lars Kruse created JENKINS-13067: Summary: Baselines are created with -identical switch: Don't do that Key: JENKINS-13067 URL: https://issues.jenkins-ci.org/browse/JENKINS-13067 Project: Jenkins Issue Type: Improvement Components: clearcase-ucm Reporter: Lars Kruse The checkmark in make baseline creates a new baseline on the stream when running in child or sibling mode. But the baseline is created with the -identical switch (and potentially also -all?) which causes baselines to be created - even on non-modifiable components. Please loose the -identical switch (and -all if it's uses) -- 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
[JIRA] (JENKINS-13067) Baselines are created with -identical switch: Don't do that
[ https://issues.jenkins-ci.org/browse/JENKINS-13067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kruse updated JENKINS-13067: - Description: The checkmark in make baseline creates a new baseline on the stream when running in child or sibling mode. But the baseline is created with the -identical switch (and potentially also -all?) which causes baselines to be created - even on non-modifiable components. Please loose the -identical switch (and -all if it's used) was: The checkmark in make baseline creates a new baseline on the stream when running in child or sibling mode. But the baseline is created with the -identical switch (and potentially also -all?) which causes baselines to be created - even on non-modifiable components. Please loose the -identical switch (and -all if it's uses) Baselines are created with -identical switch: Don't do that --- Key: JENKINS-13067 URL: https://issues.jenkins-ci.org/browse/JENKINS-13067 Project: Jenkins Issue Type: Improvement Components: clearcase-ucm Reporter: Lars Kruse The checkmark in make baseline creates a new baseline on the stream when running in child or sibling mode. But the baseline is created with the -identical switch (and potentially also -all?) which causes baselines to be created - even on non-modifiable components. Please loose the -identical switch (and -all if it's used) -- 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
