Geoff, I am facing a issue which was working before in Nov, 1.2.4 ALPHA release of this plugin.
I have logged that as defect ID 116. Thanks Pawan On Tuesday, June 26, 2012 11:05:55 PM UTC-4, Geoff Bullen wrote: > > Have you tried the latest version of the build pipeline plugin. It > allows you to retry successful builds > > *Geoff Bullen * > Centrum Systems > Level 8, 5 Elizabeth Street > Sydney > > *0408 659 395 (m) > 02 9235 0516 (t)** * > http://www.centrumsystems.com.au > > > > On 6 June 2012 02:43, Singh <pawan.gandhi...@gmail.com> wrote: > >> I am using build pipeline. The issue that I am facing to keep track >> which build number is deployed into web contains at a given time. I >> tried to using Promotion Status which goes out of sync, so for time >> being I am using fingerprinting page to see latest build. >> >> Here are my settings >> >> I have started with two jobs in pipeline >> 1. Basic ci build which polls svn and generates war >> a. A promotion in ci build which promotes a particular build from its >> downstream deployment job success.. something like “promote-to-dev”. >> >> 2. Deploy build (manually trigger required in pipeline) >> >> But problem comes, when i want to redeploy a specific build, no retry >> button successful deployment job in pipeline. Alternatively, i run >> deploy job by passing parameter as build number (using Build Selector >> for copy artifact parameter type). It redeploy provided build number >> artifact from ci job but doesn’t promote that build number again. So >> this way my Promotion Status goes out of sync. >> >> Any idea will be helpful. >> >> >> Thanks >> Pawan >> > >
