[JIRA] (JENKINS-10481) Expose fingerprint information from builds in REST API
drautureau commented on JENKINS-10481 Expose fingerprint information from builds in REST API I'm having the same need: this will help me to get the upstream builds involved in a release (which are locked by me) to get any related data that Jenkins can expose (could be useful to know what this release contains). @Ramon, seems that https://github.com/ramonvanalteren/pyjenkinsci is now https://github.com/ramonvanalteren/jenkinsapi ? 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-14713) Cancel permission is granted for users having build permission
drautureau created JENKINS-14713 Cancel permission is granted for users having build permission Issue Type: Bug Assignee: Unassigned Components: core Created: 07/Aug/12 4:29 PM Description: I expected that people need to have the "Cancel" permission to be able to cancel a build. That's right, unless they have the "Build" permission. I would like to be able to give "build" permission to some people without allowing them to abort a build. What do you think of it? Environment: Jenkins 1.465 Project: Jenkins Priority: Major Reporter: drautureau 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-6624) Add an option in the configuration of a job to not participate th the relationship between jobs (maven projects)
drautureau commented on JENKINS-6624 Add an option in the configuration of a job to not participate th the relationship between jobs (maven projects) Yes, you're right This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14552) Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked
drautureau commented on JENKINS-14552 Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked Miguel: I guess you are having the issue because you run cobertura:cobertura in a post action of the build. That's why you are having the message Skipping Cobertura coverage report as mojo did not run. in the log. I guess that if you add "cobertura:cobertura" in the goal of the main step you will not run into this issue anymore. Adding it I solved the issue but I consider this as a workaround for my case because grails uses the cobertura library and not the cobertura-maven-plugin. I should have said "Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked in the main step of a maven 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-14552) Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked
drautureau created JENKINS-14552 Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: cobertura Created: 24/Jul/12 12:41 PM Description: I'm building a project using grails and grails-maven-plugin. Since version 1.4 of the plugin, the cobertura report is not published because the cobertura-maven-plugin is not invoked: ... Cobertura: Loaded information on 293 classes. Cobertura: Saved information on 293 classes. Skipping Cobertura coverage report as mojo did not run. ... Looking at the sources of the plugin, it's mandatory to execute the cobertura-maven-plugin to publish reports (and that's not the way grails work!). I can't see why this test is done (as we need to provide the path of the report). Wouls it be possible to remove/adapt this check? As a workaround: I'm using version 1.3 of the plugin. thanks Environment: Jenkins cobertura plugin 1.4, 1.5 grails and grails maven plugin Project: Jenkins Priority: Major Reporter: drautureau 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-14552) Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked
drautureau
updated JENKINS-14552
Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked
Change By:
drautureau
(24/Jul/12 12:42 PM)
Description:
Imbuildingaprojectusinggrailsandgrails-maven-plugin.Sinceversion1.4oftheplugin,thecoberturareportisnotpublishedbecausethecobertura-maven-pluginisnotinvoked:{code}...Cobertura:Loadedinformationon293classes.Cobertura:Savedinformationon293classes.SkippingCoberturacoveragereportasmojodidnotrun{code}Lookingatthesourcesoftheplugin,itsmandatorytoexecutethecobertura-maven-plugintopublishreports(andthatsnotthewaygrailswork!).Icantseewhythistestisdone(asweneedtoprovidethepathofthereport).
Wouls
Would
itbepossibletoremove/adaptthischeck?Asaworkaround:Imusingversion1.3oftheplugin.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
