[JIRA] [clover] (JENKINS-22433) Provide instructions on how to include the Clover Html report in a job
Ronan Mulvaney created JENKINS-22433 Provide instructions on how to include the Clover Html report in a job Issue Type: Improvement Affects Versions: current Assignee: stephenconnolly Components: clover Created: 31/Mar/14 2:58 PM Description: Hi, Our job uses build scripts which generate the Clover XML and HTML report for use in the manual configuration of the Clover plugin. Whilst I can see how to use XML report, I am struggling to determine how we upload the html report so that it has visibility from the Coverage Report links i.e. /clover/ Is this something offered by your plugin or should be upload this some other way? Thanks. Environment: IE/Windows Project: Jenkins Priority: Minor Reporter: Ronan Mulvaney 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] (JENKINS-16487) Promotion Level being set to INITIAL
Ronan Mulvaney commented on JENKINS-16487 Promotion Level being set to INITIAL Hi Jens, We use the following levels: REJECTED INITIAL SMOKETESTED CIBUILD CIBUILD_FAILED CIBUILD_PASSED BUILT PEERSIGNOFF TESTED RELEASED However our issue here we have configured the job to avoid setting anything on the VOB therefore would like to ensure that the job isn't trying to change the promotion level like it is doing now, not that we want these added for usage. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16487) Promotion Level being set to INITIAL
Ronan Mulvaney commented on JENKINS-16487 Promotion Level being set to INITIAL Just wondering if there is any update on this as we have had to shutdown Jenkins builds until we can get this resolved. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16487) Promotion Level being set to INITIAL
Ronan Mulvaney reopened JENKINS-16487 Promotion Level being set to INITIAL Hi Jens, We are changing this, the problem seems to be that the plugin is changing it back upon processing the baseline via a poll scm. This is only happening since the latest release if that helps. Here is a more complete view on VOB log: These steps are our internal build process - --01-25T11:05 make attribute "PromotionLevel" on baseline "LP_MAIN_20130125_110252" "Added attribute "PromotionLevel" with value "CIBUILD_PASSED"." --01-25T11:05 remove attribute "master_process_started" from baseline "LP_MAIN_20130125_110252" Then Jenkins picks up the baseline - --01-25T11:11 make hyperlink "UseBaseline" on baseline "LP_MAIN_20130125_110252" "Attached hyperlink "UseBaseline@10960@\LP-PVOB"." --01-25T11:21 make attribute "PromotionLevel" on baseline "LP_MAIN_20130125_110252" "Added attribute "PromotionLevel" with value "INITIAL"." As such Jenkins is changing a PromotionLevel that our internal build process is relying upon. Thanks. Change By: Ronan Mulvaney (25/Jan/13 3:52 PM) Resolution: Not A Defect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16487) Promotion Level being set to INITIAL
Ronan Mulvaney created JENKINS-16487 Promotion Level being set to INITIAL Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: clearcase-ucm Created: 25/Jan/13 1:42 PM Description: With a Job which polls the SCM repository we are finding that after polling and working with a new baseline that the plugin is setting the following on our repository: --01-25T11:21 username make attribute "PromotionLevel" on baseline "LP_MAIN_20130125_110252" "Added attribute "PromotionLevel" with value "INITIAL"." We have the following set on the Job: Promotion Level - Any Load Modules - All Polling - Poll Self Create Baseline - unchecked Recommend Baseline - unchecked Make Tag - unchecked Set description - unchecked I have marked this as blocker as this invalidates our whole SCM process which Jenkins is just a small part of and we cannot have Jenkins interact like this here i.e. it should not set anything on the repository. Environment: Windows 2008 64Bit RC2 Project: Jenkins Priority: Blocker Reporter: Ronan Mulvaney 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-16072) Missing baselines issue with latest plugin
Ronan Mulvaney commented on JENKINS-16072 Missing baselines issue with latest plugin Anything I can do to move this forward as this has systemically hit all our farms now and the only workaround is to provide a baseline parameter to a build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16072) Missing baselines issue with latest plugin
Ronan Mulvaney commented on JENKINS-16072 Missing baselines issue with latest plugin If I don't pass the baseline in and just try to use the latest on the stream I get: [CCUCM] ClearCase UCM Plugin version 1.3.0 [CCUCM] Allow for slave polling: true [CCUCM] Poll for posted deliveries: false [CCUCM] Forcing deliver: false [CCUCM] Polling streams: self [CCUCM] Getting baselines for : [CCUCM] * Stream: n2o_ref_int@\N2O-PVOB [CCUCM] * Component: N2O-VOB@\N2O-PVOB [CCUCM] * Promotion level: null [CCUCM] No Baselines found [CCUCM] Pre build steps done [CCUCM] Finished processing; the baseline is null, this could pose as a problem! As the Promotion level: null appeared here I have tried setting and unsetting this from "any" but this doesn't seem to effect this error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16072) Missing baselines issue with latest plugin
Ronan Mulvaney commented on JENKINS-16072 Missing baselines issue with latest plugin Have tried downgrading to the previous plugin on the new System that I set up and everything works as expected so this does seem an issue with the 1.3.0 plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16072) Missing baselines issue with latest plugin
Ronan Mulvaney created JENKINS-16072 Missing baselines issue with latest plugin Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: clearcase-ucm Created: 07/Dec/12 3:49 PM Description: Since upgrading to the 1.3.0 release of the plugin any new node that we add as slaves have the following effect on the build. [CCUCM] ClearCase UCM Plugin version 1.3.0 [CCUCM] Allow for slave polling: true [CCUCM] Poll for posted deliveries: false [CCUCM] Forcing deliver: true [CCUCM] No Baselines found [CCUCM] Pre build steps done [CCUCM] Finished processing; the baseline is null, this could pose as a problem! Other nodes that have been migrated through the version 1.2.0 of the plugin behave normally for the same build. Additionally a fresh install of Jenkins with the latest plugins causes the same issue as a new node. During the upgrade from 1.2.0 to 1.3.0 I did note/remember that there was managed data that was no longer relevant around the baseline topic however this was not noticable from the UI i.e. I did not spot anything missing so ignored. We are using the standard settings that the documentation mentions to apply i.e. At the System Level for the plugin I have: Allow polling on slaves - unchecked Poll for Posted Deliveries - unchecked Job Level: Promotion level - ANY Load modules - All Polling - Poll Self Create baseline - unchecked Recommend baseline - unchecked Make tag - unchecked Set description - unchecked Force deliver - unchecked Plus the required: Stream Component Build Project appropriate for our repository. Environment: Windows 2008 Server Project: Jenkins Priority: Major Reporter: Ronan Mulvaney 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
