Re: claim plugin not working

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: claim plugin not working

Tom Huybrechts
Maybe the claim plugin is running before the text finder does.
Unfortunately we don't really have support for expressing runtime
dependencies between plugins.
We can define some 'priority' number in the source code, but this may
well cause problems elsewhere...


2009/7/8 anthonyjeffery <[hidden email]>:

>
> After some more experimenting I have found that the claim plugin links
> consistently appear correctly for failed builds only when I disable the text
> finder plugin.
>
> I was using the text finder plugin to set the overall result to failure if
> one of the
> platform variants I am building failed to build. I have the following string
> set in the
> regular expression field which catches two different make error strings.
> "make(\[\d*\])?: \*\*\*|[Ee]rror:"
> I still need to use the text finder plugin because Hudson does not always
> mark the build run
> as a failure if for instance one of platforms 1 thru 5 fail and platform 6
> is a successful build.
>
> When the text finder plugin is turned on and an SCM change trigger starts
> the job,
> the Claim link does not appear for failed builds :-(
>
> Is this a bug in the claim plugin? Is there something I can do on my end to
> fix the problem?
>
> Thanks,
> Anthony
>
>
> On Mon, Jun 29, 2009 at 4:11 PM, anthonyjeffery
> <[hidden email]>wrote:
>
>>
>> Some engineers were very excited to hear about the Claim plugin for
>> Hudson.
>> We tried enabling it today and we are running into some flakiness after
>> installing the plugin & restarting Hudson.
>>
>> We do not see the "claim" link on every broken build page. My
>> understanding
>> is that if the overall result is FAILURE, we should see a claim link on
>> the
>> build page when the build is done.
>> We did see it for one build which failed but it was manually executed.
>> Subsequent builds (triggered by SCM) which also failed do not have the
>> claim
>> page.
>>
>> I created a new job called 'test_claim' and I dont see the claim issue
>> occuring at all there. It works like a charm on my new empty job.
>>
>> I dont see any claim errors in our hudson.log. Does anyone have an idea
>> how
>> I can further troubleshoot and resolve this? Has anyone else experienced
>> this problem?
>>
>> --
>> View this message in context:
>> http://www.nabble.com/claim-plugin-not-working-tp24260801p24260801.html
>> Sent from the Hudson users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
>
>
>
> --
> View this message in context: http://www.nabble.com/claim-plugin-not-working-tp24260801p24399955.html
> Sent from the Hudson users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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: claim plugin not working

anthonyjeffery
This sounds like a good reason for the problem.
Unfortunately I have no way of finding out since the the console output for text finder & claim doesnt say what its doing as it does with "Archiving artifacts" and "Recording fingerprints".

How can I make the claim plugin run after the textfinder plugin?



TomHuybrechts wrote
Maybe the claim plugin is running before the text finder does.
Unfortunately we don't really have support for expressing runtime
dependencies between plugins.
We can define some 'priority' number in the source code, but this may
well cause problems elsewhere...


2009/7/8 anthonyjeffery <anthonyj@broadcom.com>:
>
> After some more experimenting I have found that the claim plugin links
> consistently appear correctly for failed builds only when I disable the text
> finder plugin.
>
> I was using the text finder plugin to set the overall result to failure if
> one of the
> platform variants I am building failed to build. I have the following string
> set in the
> regular expression field which catches two different make error strings.
> "make(\[\d*\])?: \*\*\*|[Ee]rror:"
> I still need to use the text finder plugin because Hudson does not always
> mark the build run
> as a failure if for instance one of platforms 1 thru 5 fail and platform 6
> is a successful build.
>
> When the text finder plugin is turned on and an SCM change trigger starts
> the job,
> the Claim link does not appear for failed builds :-(
>
> Is this a bug in the claim plugin? Is there something I can do on my end to
> fix the problem?
>
> Thanks,
> Anthony
>
>
> On Mon, Jun 29, 2009 at 4:11 PM, anthonyjeffery
> <anthonyj@broadcom.com>wrote:
>
>>
>> Some engineers were very excited to hear about the Claim plugin for
>> Hudson.
>> We tried enabling it today and we are running into some flakiness after
>> installing the plugin & restarting Hudson.
>>
>> We do not see the "claim" link on every broken build page. My
>> understanding
>> is that if the overall result is FAILURE, we should see a claim link on
>> the
>> build page when the build is done.
>> We did see it for one build which failed but it was manually executed.
>> Subsequent builds (triggered by SCM) which also failed do not have the
>> claim
>> page.
>>
>> I created a new job called 'test_claim' and I dont see the claim issue
>> occuring at all there. It works like a charm on my new empty job.
>>
>> I dont see any claim errors in our hudson.log. Does anyone have an idea
>> how
>> I can further troubleshoot and resolve this? Has anyone else experienced
>> this problem?
>>
>> --
>> View this message in context:
>> http://www.nabble.com/claim-plugin-not-working-tp24260801p24260801.html
>> Sent from the Hudson users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
>> For additional commands, e-mail: users-help@hudson.dev.java.net
>>
>>
>
>
>
>
>
> --
> View this message in context: http://www.nabble.com/claim-plugin-not-working-tp24260801p24399955.html
> Sent from the Hudson users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
> For additional commands, e-mail: users-help@hudson.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
For additional commands, e-mail: users-help@hudson.dev.java.net