![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
build-pipeline-plugin |
|
Created:
|
06/Nov/14 10:56 PM
|
|
Description:
|
I'm trying to configure a "Build Pipeline Version" to an ANT JOB.
All my tests showed the same: the Pipeline Version is created right after the SCM step and BEFORE any other step that allow me to raise a new Environment Variable or execute a shell to read a file to get the version.
What would be a very good step-by-step option:
Run SCM
Run "EnvInject Plugin" plugin (here I can parse a file, run a script, etc, it is very useful)
Then run the Pipeline Version Creation
It is so easy to get the POM Version in a "Maven Project" with a "Maven Job", but so painful with a freestyle job.
If there's a way you have already figured out how to set the Build Pipeline Version using some info coming from files downloaded from SCM step, I'm very interested to learn.
All examples I have found were about maven jobs and POM's version ![]()
Thank you
Rafael
|
|
Project:
|
Jenkins
|
|
Labels:
|
build-pipeline-plugin
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Rafael Ximenes
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
