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, zippo7061 <[email protected]> wrote:

> 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 PM, Melissa Palmer <[email protected]>
>> 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 UTC+2, zippo7061 wrote:
>>>>
>>>> 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 doesn't seem i have a way of extracting the most recent in the build.
>>>>
>>>>
>>>>
>>>> http://JENKINS/job/APPLICATION/promotion/process/QA_ENVIRONMENT/api/xml?depth=1&xpath=/*/build[2]/target/number
>>>> was promising, but can't set the most recent buld number.  The xml format
>>>> seems to change and would have to not do xpath read all and then sort by
>>>> date somehow.  Not good to do.
>>>>
>>>> The end result is to put the # on a wiki page that has tons of other
>>>> information, so linking/iframes not really a good thing, would like to just
>>>> get the result from a GET and display it on a page.
>>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/d3b614ee-6454-4fab-bbeb-df3f8d07d712%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/d3b614ee-6454-4fab-bbeb-df3f8d07d712%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/43f206e0-6269-4fdb-8ca6-8b76f96ef438%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/43f206e0-6269-4fdb-8ca6-8b76f96ef438%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CACPng9Z6O86Sp3oqca8B%3DnQ2ssFatHjixznncvpSUGqe28aLQw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to