On successful promotion, build metadata file (build.xml) will gets updated
with following status.
<statuses>
<hudson.plugins.promoted__builds.Status>
<name>Promotion</name>
<badges>
<hudson.plugins.promoted__builds.conditions.GroovyCondition_-Badge>
<displayLabel>Custom Groovy script condition</displayLabel>
<variables class="empty-map"/>
</hudson.plugins.promoted__builds.conditions.GroovyCondition_-Badge>
<hudson.plugins.promoted__builds.conditions.SelfPromotionBadge/>
</badges>
<timestamp>
<time>1479318413549</time>
<timezone>Asia/Calcutta</timezone>
</timestamp>
<promotion>16</promotion>
<promotionAttempts>
<int>15</int>
<int>16</int>
</promotionAttempts>
</hudson.plugins.promoted__builds.Status>
</statuses>
If i remove this section from xml and restart the jenkin promotion status
will be unmarked. But i am exploring a programmatic option to do this meta
data change without restarting the jenkins! Any suggestions/clue ?
On Wednesday, 16 November 2016 21:14:11 UTC+5:30, avinash....@gmail.com
wrote:
>
> I am using Promoted Build plugin to mark the stable build.
>
>
> I have a scenario where i need to unmark the build from promotion. Any
> suggestion to achieve this ?
>
>
> The idea is having am multiple builds with the promotion flag will make
> the deploy team confuse. So as soon as we get a new stable build, i want to
> unmark the build from promotion.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/0d3c97a7-8798-4aa7-ba08-f8ad8fd32ade%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
