Jenkins › Jenkins issues

[JIRA] (JENKINS-14705) Jenkins' built-in Variables should be useable in Integrity Plugin's Configuration Fields

Classic

List

Threaded

3 messages Options

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-14705) Jenkins' built-in Variables should be useable in Integrity Plugin's Configuration Fields

Issue Type:	Improvement
Affects Versions:	current
Assignee:	Cletus D'Souza
Components:	integrity-plugin
Created:	07/Aug/12 11:44 AM
Description:	Would be great to be able to use Jenkins' environment and built-in variables in the configuration fields of the integrity plugin. E.g., my job names are equal to the project names in MKS and I just want to copy existing jobs in Jenkins to create new jobs for other projects just by changing the job name. Therefore I would like to use something like this in the "Integrity Project" configuration field: #p=d:/mks/archives/src/${JOB_NAME}.pj
Environment:	All
Project:	Jenkins
Priority:	Major
Reporter:	Karsten Günther

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 noreply@jenkins-ci.org

[JIRA] (JENKINS-14705) Jenkins' built-in Variables should be useable in Integrity Plugin's Configuration Fields

This could become tricky as the Change Log feature could become unusable between builds

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-14705) Jenkins' built-in Variables should be useable in Integrity Plugin's Configuration Fields

In reply to this post by JIRA noreply@jenkins-ci.org

Maybe my description was a little bit misleading, I do not want to change the JOB_NAME after the job was created. Nevertheless I think it is a good idea to use Jenkins' built-in variables in configuration fields wherever it is possible. My major work rule: DRY (Don't Repeat Yourself)