[JIRA] (JENKINS-54751) Expose SCM changes as environment variables
Title: Message Title
Verbitan created an issue
Jenkins / JENKINS-54751
Expose SCM changes as environment variables
Issue Type:
New Feature
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-11-21 10:56
Priority:
Minor
Reporter:
Verbitan
Would it be possible to expose an environment variable that contained the change descriptions of all the changes in this current build. I have a Publish Assets Post-build action that I'd like to reference the change descriptions of all the changes it's building. Currently I have the following text:
Jenkins: ${JOB_NAME} automated build submission.
I'd like to do something like the following:
Jenkins: ${JOB_NAME} automated build submission.
Changes included:
${P4_CHANGE_DESCRIPTIONS}
[JIRA] [run-condition] (JENKINS-20521) Plugin installed but not visible
Verbitan resolved JENKINS-20521 as Not A Defect Plugin installed but not visible I misunderstood how this plugin should be used. After installing the Conditional Buildstep Plugin everything was ok. Apologies. Change By: Verbitan (14/Nov/13 12:45 PM) Status: Open 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] [run-condition] (JENKINS-20521) Plugin installed but not visible
Verbitan created JENKINS-20521 Plugin installed but not visible Issue Type: Bug Affects Versions: current Assignee: bap Components: run-condition Created: 11/Nov/13 5:02 PM Description: I'm running Jenkins LTS 1.509.3 and I installed the run condition plugin via the update center (version 0.10). After restarting Jenkins I can see that the plugin is installed, however it doesn't seem to be doing anything. I've opened up an existing job (matrix and non-matrix) and created a new job, none of which had a conditional build step available. I'm not sure what it is I've done wrong. I also tried manually installing version 1.0 with no luck. Environment: Solaris Project: Jenkins Priority: Major Reporter: Verbitan 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-15320) Add 'Ignore missing file' option.
Verbitan commented on JENKINS-15320 Add Ignore missing file option. I've installed that plugin before, but it never showed up as an option when configuring builds. I don't know if it's a bug with the plugin, or I'm just plain stupid. Does it work on post-build actions as well as build steps? 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-15320) Add 'Ignore missing file' option.
Verbitan created JENKINS-15320 Add Ignore missing file option. Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: cppcheck Created: 26/Sep/12 1:42 PM Description: Currently I have a matrix job which builds on both Linux and Solaris. As my cppcheck binary is only compiled for Linux, I surround the command to run cppcheck in an if Linux block. Now the plugin has an option to ignore a blank file, but it doesn't have an option to ignore a missing file. Because of this my Solaris build always fails. Project: Jenkins Priority: Minor Reporter: Verbitan 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-13954) Add an option so that the build doesn't fail if cppcheck can't find the XML file.
Nick James created JENKINS-13954: Summary: Add an option so that the build doesn't fail if cppcheck can't find the XML file. Key: JENKINS-13954 URL: https://issues.jenkins-ci.org/browse/JENKINS-13954 Project: Jenkins Issue Type: Improvement Components: cppcheck Affects Versions: current Reporter: Nick James Assignee: Gregory Boissinot Priority: Minor I've got a multi-configuration job which compiles on both Linux and Solaris. The cppcheck binary I use is compiled for Solaris and not Linux, so in the job configuration I only generate the cppcheck XML if the build is being run on Solaris. I want to publish out the cppcheck results, but this always causes the Linux build to fail as it hasn't generated the XML file. Is it possible to add a setting that ignores the file not existing? There's already something similar for when the file is blank... -- 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
