I usually add a shell step that writes the promoted build number to a file
that can be accessed via a url.
The file will get lost if it remains in the workspace so it will be best to
add an archive step after shell step.
You should then use a url to the archived content.
On 29 April 2015 at 21:21,
Thank you, but can you please provide an example on how you would get to
that env variable from a url GET.
On Wednesday, April 29, 2015 at 2:18:31 PM UTC-5, hhvong wrote:
>
> you can use environment variable promoted_number to get last promoted
> build number
>
> On Wed, Apr 29, 2015 at 3:02 P
you can use environment variable promoted_number to get last promoted build
number
On Wed, Apr 29, 2015 at 3:02 PM, Melissa Palmer
wrote:
> Hi Zippo, did you manage to solve this? I'm needing to get the previous
> promoted build number too. Thanks Melissa
>
> On Tuesday, 28 April 2015 18:37:50 U
Hi Zippo, did you manage to solve this? I'm needing to get the previous
promoted build number too. Thanks Melissa
On Tuesday, 28 April 2015 18:37:50 UTC+2, zippo7061 wrote:
>
> I was trying the get the last successful build that was promoted
> (promotion plugin) into a specific environment out o
I was trying the get the last successful build that was promoted (promotion
plugin) into a specific environment out of Jenkins, but not sure how.
Gain, not looking for Build Number, but for the build# that was promoted.
Ran into some success using the xml/api, but this quickly ended as it
doe
