Promotion Plugin

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Promotion Plugin

Lerenc, Vedran
Hi,

I installed the Promotion plugin, but it doesn't seem to work for me. I
configured it on a job that has another job as successor. I added this
job to "When the following downstream projects build successfully" and
triggered the build. Nothing happened after I triggered the build of my
job or after the successor was built (both of course successfully).
Promotion status says "No build promoted so far".

Have I missunderstood the function of this plugin or is it a bug?

Thank you in advance,
Regards,

Vedran

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Promotion Plugin

Kohsuke Kawaguchi
Administrator
Lerenc, Vedran wrote:

> Hi,
>
> I installed the Promotion plugin, but it doesn't seem to work for me. I
> configured it on a job that has another job as successor. I added this
> job to "When the following downstream projects build successfully" and
> triggered the build. Nothing happened after I triggered the build of my
> job or after the successor was built (both of course successfully).
> Promotion status says "No build promoted so far".
>
> Have I missunderstood the function of this plugin or is it a bug?
Have you enabled fingerprinting to link those two jobs? If not, Hudson
should have reported a warning at the end of the successor build to that
extent.

>
> Thank you in advance,
> Regards,
>
> Vedran
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Re: Promotion Plugin

Lerenc, Vedran
Hi Kohsuke,

Yes, you are right and I have missed that. Interestingly I get the
warning twice:

WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
criteria, but no fingerprint is recorded.
WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
criteria, but no fingerprint is recorded.

However, after I activated fingerprints, I still get the warnings:

WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
criteria, but no fingerprint is recorded.
WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
criteria, but no fingerprint is recorded.

That's strange, since I now see on the left side the Fingerprints link
and when I click it it looks good to me.

I don't even know if this plugin would help me.

My use case: I have a complex project graph and some kind of master job,
let's call it BUILD_ALL. This BUILD_ALL job lists as downstream projects
all distinct root projects of my project graph. When I trigger it, it
fires of the root projects which in the end will fire all other projects
in my graph.

My problem: The BUILD_ALL job returns immediately, because it isn't
doing anything. It just lists the root projects of my project graph as
downstream projects, i.e. it always succeeds. But I would wish that it
shows SUCCESS only if all other jobs succeeeded and FAILURE otherwise.

Is that somehow possible to achieve?

Thank you in advance,
Regards,

Vedran



-----Original Message-----
From: Kohsuke Kawaguchi [mailto:[hidden email]]
Sent: Dienstag, 15. Juli 2008 19:36
To: [hidden email]
Subject: Re: Promotion Plugin

Lerenc, Vedran wrote:
> Hi,
>
> I installed the Promotion plugin, but it doesn't seem to work for me.
I
> configured it on a job that has another job as successor. I added this
> job to "When the following downstream projects build successfully" and
> triggered the build. Nothing happened after I triggered the build of
my
> job or after the successor was built (both of course successfully).
> Promotion status says "No build promoted so far".
>
> Have I missunderstood the function of this plugin or is it a bug?

Have you enabled fingerprinting to link those two jobs? If not, Hudson
should have reported a warning at the end of the successor build to that

extent.

>
> Thank you in advance,
> Regards,
>
> Vedran
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Promotion Plugin

Kohsuke Kawaguchi
Administrator
Lerenc, Vedran wrote:
> Hi Kohsuke,
>
> Yes, you are right and I have missed that.

I wonder if it's better to mark the build as a failure to get an attention?

 > Interestingly I get the
> warning twice:
>
> WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
> criteria, but no fingerprint is recorded.
> WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
> criteria, but no fingerprint is recorded.

I fixed the bug in the repository so that Hudson won't issue the same
warning twice.


> However, after I activated fingerprints, I still get the warnings:
>
> WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
> criteria, but no fingerprint is recorded.
> WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
> criteria, but no fingerprint is recorded.
>
> That's strange, since I now see on the left side the Fingerprints link
> and when I click it it looks good to me.

Fingerprinting needs to be enabled on both your upstream and the
downstream. See http://hudson.gotdns.com/wiki/display/HUDSON/Fingerprint 
for how it works.

I improved the error message a bit in the repository.


> I don't even know if this plugin would help me.
>
> My use case: I have a complex project graph and some kind of master job,
> let's call it BUILD_ALL. This BUILD_ALL job lists as downstream projects
> all distinct root projects of my project graph. When I trigger it, it
> fires of the root projects which in the end will fire all other projects
> in my graph.
>
> My problem: The BUILD_ALL job returns immediately, because it isn't
> doing anything. It just lists the root projects of my project graph as
> downstream projects, i.e. it always succeeds. But I would wish that it
> shows SUCCESS only if all other jobs succeeeded and FAILURE otherwise.
>
> Is that somehow possible to achieve?
Promoted builds plugin won't let you mark the "BUILD ALL" as a failure,
but you can effectively achieve what you want with this plugin.


> Thank you in advance,
> Regards,
>
> Vedran
>
>
>
> -----Original Message-----
> From: Kohsuke Kawaguchi [mailto:[hidden email]]
> Sent: Dienstag, 15. Juli 2008 19:36
> To: [hidden email]
> Subject: Re: Promotion Plugin
>
> Lerenc, Vedran wrote:
>> Hi,
>>
>> I installed the Promotion plugin, but it doesn't seem to work for me.
> I
>> configured it on a job that has another job as successor. I added this
>> job to "When the following downstream projects build successfully" and
>> triggered the build. Nothing happened after I triggered the build of
> my
>> job or after the successor was built (both of course successfully).
>> Promotion status says "No build promoted so far".
>>
>> Have I missunderstood the function of this plugin or is it a bug?
>
> Have you enabled fingerprinting to link those two jobs? If not, Hudson
> should have reported a warning at the end of the successor build to that
>
> extent.
>
>>
>> Thank you in advance,
>> Regards,
>>
>> Vedran
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Re: Promotion Plugin

Lerenc, Vedran
Hi Kohsuke,

Thank you for the help! Yes, the plugin can help me and works now (when
I open the BUILD_ALL job, I see whether or not the latest build is
tagged with a star). However, it can't render my BUILD_ALL job as a
failure. This would have been very nice, tough. Is that somehow
possible? Alternatively, it would also help if the star is displayed in
the joblist of the main Hudson view, so that one can see immediately,
but a real Failure would be much better. Already now developers are
confused by the colors and the sun/cloud icons. Out of curiosity, why is
the ok build icon blue and not green?

In regards to your question: Warning or Error. Both is ok for me now.
From your perspective: I would choose whatever will reduce your support
effort, i.e. let the build fail. If promotioin is used, but not
configured correctly, it's ok to fail. Thereby people check at least the
console output and will understand what needs to be done (Or do you have
a paradigm for misconfiguration? Warning or Error?).

Thank you again,
Regards,

Vedran

-----Original Message-----
From: Kohsuke Kawaguchi [mailto:[hidden email]]
Sent: Donnerstag, 17. Juli 2008 07:13
To: [hidden email]
Subject: Re: Promotion Plugin

Lerenc, Vedran wrote:
> Hi Kohsuke,
>
> Yes, you are right and I have missed that.

I wonder if it's better to mark the build as a failure to get an
attention?

 > Interestingly I get the
> warning twice:
>
> WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
> criteria, but no fingerprint is recorded.
> WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
> criteria, but no fingerprint is recorded.

I fixed the bug in the repository so that Hudson won't issue the same
warning twice.


> However, after I activated fingerprints, I still get the warnings:
>
> WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
> criteria, but no fingerprint is recorded.
> WARNING: SUBMIT_(-)_BUILD_ALL appears to use this job as a promotion
> criteria, but no fingerprint is recorded.
>
> That's strange, since I now see on the left side the Fingerprints link
> and when I click it it looks good to me.

Fingerprinting needs to be enabled on both your upstream and the
downstream. See http://hudson.gotdns.com/wiki/display/HUDSON/Fingerprint

for how it works.

I improved the error message a bit in the repository.


> I don't even know if this plugin would help me.
>
> My use case: I have a complex project graph and some kind of master
job,
> let's call it BUILD_ALL. This BUILD_ALL job lists as downstream
projects
> all distinct root projects of my project graph. When I trigger it, it
> fires of the root projects which in the end will fire all other
projects
> in my graph.
>
> My problem: The BUILD_ALL job returns immediately, because it isn't
> doing anything. It just lists the root projects of my project graph as
> downstream projects, i.e. it always succeeds. But I would wish that it
> shows SUCCESS only if all other jobs succeeeded and FAILURE otherwise.
>
> Is that somehow possible to achieve?

Promoted builds plugin won't let you mark the "BUILD ALL" as a failure,
but you can effectively achieve what you want with this plugin.


> Thank you in advance,
> Regards,
>
> Vedran
>
>
>
> -----Original Message-----
> From: Kohsuke Kawaguchi [mailto:[hidden email]]
> Sent: Dienstag, 15. Juli 2008 19:36
> To: [hidden email]
> Subject: Re: Promotion Plugin
>
> Lerenc, Vedran wrote:
>> Hi,
>>
>> I installed the Promotion plugin, but it doesn't seem to work for me.
> I
>> configured it on a job that has another job as successor. I added
this
>> job to "When the following downstream projects build successfully"
and
>> triggered the build. Nothing happened after I triggered the build of
> my
>> job or after the successor was built (both of course successfully).
>> Promotion status says "No build promoted so far".
>>
>> Have I missunderstood the function of this plugin or is it a bug?
>
> Have you enabled fingerprinting to link those two jobs? If not, Hudson

> should have reported a warning at the end of the successor build to
that

>
> extent.
>
>>
>> Thank you in advance,
>> Regards,
>>
>> Vedran
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Promotion Plugin

Michael Donohue-2
> -----Original Message-----
> From: Lerenc, Vedran [mailto:[hidden email]]
> Sent: Thursday, July 17, 2008 12:41 AM
> To: [hidden email]
> Subject: RE: Re: Promotion Plugin

> Already now developers are
> confused by the colors and the sun/cloud icons. Out of curiosity, why
is
> the ok build icon blue and not green?

The green vs blue issue is covered in enhancement request 369.  It's
apparently somewhat contentious.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Promotion Plugin

stephenconnolly
the balls say whether the build worked or not. blue is nothing  
stopping the build. yellow is tests failed. red is build failed.

the weather is an assesment of the project health. for example if the  
build has failed a lot recently you get storm clouds. if the build has  
low test coverage you get storm clouds

Sent from my iPod

On 20 Jul 2008, at 03:05, "Donohue, Michael" <[hidden email]>  
wrote:

>> -----Original Message-----
>> From: Lerenc, Vedran [mailto:[hidden email]]
>> Sent: Thursday, July 17, 2008 12:41 AM
>> To: [hidden email]
>> Subject: RE: Re: Promotion Plugin
>
>> Already now developers are
>> confused by the colors and the sun/cloud icons. Out of curiosity, why
> is
>> the ok build icon blue and not green?
>
> The green vs blue issue is covered in enhancement request 369.  It's
> apparently somewhat contentious.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Promotion Plugin

Adam Purkiss
I know the team I work with are not fussed about colour and the weather icon is fun and yet helpful at the same time.




> From: [hidden email]

> To: [hidden email]
> Date: Sun, 20 Jul 2008 08:28:33 +0100
> Subject: Re: Promotion Plugin
>
> the balls say whether the build worked or not. blue is nothing
> stopping the build. yellow is tests failed. red is build failed.
>
> the weather is an assesment of the project health. for example if the
> build has failed a lot recently you get storm clouds. if the build has
> low test coverage you get storm clouds
>
> Sent from my iPod
>
> On 20 Jul 2008, at 03:05, "Donohue, Michael" <[hidden email]>
> wrote:
>
> >> -----Original Message-----
> >> From: Lerenc, Vedran [mailto:[hidden email]]
> >> Sent: Thursday, July 17, 2008 12:41 AM
> >> To: [hidden email]
> >> Subject: RE: Re: Promotion Plugin
> >
> >> Already now developers are
> >> confused by the colors and the sun/cloud icons. Out of curiosity, why
> > is
> >> the ok build icon blue and not green?
> >
> > The green vs blue issue is covered in enhancement request 369. It's
> > apparently somewhat contentious.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


Reply | Threaded
Open this post in threaded view
|

Re: Promotion Plugin

stephenconnolly
the other thing is that the weather is relative. for one sprint you could set stormy to 65000 checkstyles and sunny to 64000, that way even though the number is big people can see meaningful progress towards the target

Sent from my iPod

On 20 Jul 2008, at 08:32, Adam Purkiss <[hidden email]> wrote:

I know the team I work with are not fussed about colour and the weather icon is fun and yet helpful at the same time.




> From: [hidden email]
> To: [hidden email]
> Date: Sun, 20 Jul 2008 08:28:33 +0100
> Subject: Re: Promotion Plugin
>
> the balls say whether the build worked or not. blue is nothing
> stopping the build. yellow is tests failed. red is build failed.
>
> the weather is an assesment of the project health. for example if the
> build has failed a lot recently you get storm clouds. if the build has
> low test coverage you get storm clouds
>
> Sent from my iPod
>
> On 20 Jul 2008, at 03:05, "Donohue, Michael" <[hidden email]>
> wrote:
>
> >> -----Original Message-----
> >> From: Lerenc, Vedran [[hidden email]]
> >> Sent: Thursday, July 17, 2008 12:41 AM
> >> To: [hidden email]
> >> Subject: RE: Re: Promotion Plugin
> >
> >> Already now developers are
> >> confused by the colors and the sun/cloud icons. Out of curiosity, why
> > is
> >> the ok build icon blue and not green?
> >
> > The green vs blue issue is covered in enhancement request 369. It's
> > apparently somewhat contentious.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


Reply | Threaded
Open this post in threaded view
|

RE: RE: Promotion Plugin

Lerenc, Vedran
In reply to this post by Adam Purkiss
Please, I never meant to irritate someone with the feedback -  a feedback I got by some dozen developers.
 
They just didn't understand it on the first time. That's all. Some found the legend, as I did when I first looked into it, some didn't and needed some help.
 
No problem. It's not bad, but not intuitive either. You need to read what the weather icons mean, which is ok. I like it as they show me a trend over the last builds, which is certainly good to get a feeling for the build stability.
 
All fine. :-)
 
 


From: Adam Purkiss [mailto:[hidden email]]
Sent: Sonntag, 20. Juli 2008 09:33
To: [hidden email]
Subject: RE: Promotion Plugin

I know the team I work with are not fussed about colour and the weather icon is fun and yet helpful at the same time.




> From: [hidden email]

> To: [hidden email]
> Date: Sun, 20 Jul 2008 08:28:33 +0100
> Subject: Re: Promotion Plugin
>
> the balls say whether the build worked or not. blue is nothing
> stopping the build. yellow is tests failed. red is build failed.
>
> the weather is an assesment of the project health. for example if the
> build has failed a lot recently you get storm clouds. if the build has
> low test coverage you get storm clouds
>
> Sent from my iPod
>
> On 20 Jul 2008, at 03:05, "Donohue, Michael" <[hidden email]>
> wrote:
>
> >> -----Original Message-----
> >> From: Lerenc, Vedran [mailto:[hidden email]]
> >> Sent: Thursday, July 17, 2008 12:41 AM
> >> To: [hidden email]
> >> Subject: RE: Re: Promotion Plugin
> >
> >> Already now developers are
> >> confused by the colors and the sun/cloud icons. Out of curiosity, why
> > is
> >> the ok build icon blue and not green?
> >
> > The green vs blue issue is covered in enhancement request 369. It's
> > apparently somewhat contentious.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


Reply | Threaded
Open this post in threaded view
|

RE: Promotion Plugin

Adam Purkiss
not irritated at all :) Its all good. Just because one set of people think one thing does not mean all do, its always helpful to get feedback incase something can be done to improve things :)




Date: Wed, 23 Jul 2008 10:57:23 +0200
From: [hidden email]
To: [hidden email]
Subject: RE: RE: Promotion Plugin

Please, I never meant to irritate someone with the feedback -  a feedback I got by some dozen developers.
 
They just didn't understand it on the first time. That's all. Some found the legend, as I did when I first looked into it, some didn't and needed some help.
 
No problem. It's not bad, but not intuitive either. You need to read what the weather icons mean, which is ok. I like it as they show me a trend over the last builds, which is certainly good to get a feeling for the build stability.
 
All fine. :-)
 
 


From: Adam Purkiss [mailto:[hidden email]]
Sent: Sonntag, 20. Juli 2008 09:33
To: [hidden email]
Subject: RE: Promotion Plugin

I know the team I work with are not fussed about colour and the weather icon is fun and yet helpful at the same time.




> From: [hidden email]

> To: [hidden email]
> Date: Sun, 20 Jul 2008 08:28:33 +0100
> Subject: Re: Promotion Plugin
>
> the balls say whether the build worked or not. blue is nothing
> stopping the build. yellow is tests failed. red is build failed.
>
> the weather is an assesment of the project health. for example if the
> build has failed a lot recently you get storm clouds. if the build has
> low test coverage you get storm clouds
>
> Sent from my iPod
>
> On 20 Jul 2008, at 03:05, "Donohue, Michael" <[hidden email]>
> wrote:
>
> >> -----Original Message-----
> >> From: Lerenc, Vedran [mailto:[hidden email]]
> >> Sent: Thursday, July 17, 2008 12:41 AM
> >> To: [hidden email]
> >> Subject: RE: Re: Promotion Plugin
> >
> >> Already now developers are
> >> confused by the colors and the sun/cloud icons. Out of curiosity, why
> > is
> >> the ok build icon blue and not green?
> >
> > The green vs blue issue is covered in enhancement request 369. It's
> > apparently somewhat contentious.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>