Duplicate builds after update to ver. 1.363

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

Duplicate builds after update to ver. 1.363

tiainpa
Hi,

Yesterday I updated our Hudson from ver. 1.361 to 1.363, and I've seen occasional duplicate builds since.

For example, some upstream job triggers same downstream job twice. Similarly, remotely triggering a job via curl sometimes triggers the same job twice.

Anybody else seeing this behavior? Also, any help regarding this matter greatly appreciated!

Thanks!
-Pasi
Reply | Threaded
Open this post in threaded view
|

Re: Duplicate builds after update to ver. 1.363

Aggamemnon
This post has NOT been accepted by the mailing list yet.
I have seen a similar problem and had to downgrade to 1.362.  Does anyone have any idea when this issue will be fixed, as it means that 1.363 is unusable?
Reply | Threaded
Open this post in threaded view
|

Re: Duplicate builds after update to ver. 1.363

tiainpa
I created the following Jira ticket for this:
HUDSON-6819

-Pasi
Reply | Threaded
Open this post in threaded view
|

Re: Duplicate builds after update to ver. 1.363

jcarsique
Hi,

I've add a comment.

Do you have a workaround for stopping duplicated jobs ?
They never finish, we cannot stop them neither view job or current
build; whereas other jobs work fine.

Thanks,

Le 22/06/10 15:02, tiainpa a écrit :
> I created the following Jira ticket for this:
> http://issues.hudson-ci.org/browse/HUDSON-6819 HUDSON-6819
>
> -Pasi
>  

--
Julien Carsique, Nuxeo (Paris, France) — [hidden email]
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform



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

Reply | Threaded
Open this post in threaded view
|

Re: Duplicate builds after update to ver. 1.363

Timothy Bingaman
In reply to this post by tiainpa
We're seeing this as well after upgrading to 1.363.

Looks like there was a change to the BuildDependency logic allowing multiple triggers between the same two jobs (and I'm even seeing self-referencing triggers now with builds that trigger themselves endlessly).  Perhaps it was something else, but I'm thinking this change is what's causing this (r31934 to Hudson core).

No easy workarounds that I can see except to shut Hudson down and go back to the previous version.

-Timo

On 22 June 2010 18:45, tiainpa <[hidden email]> wrote:

Hi,

Yesterday I updated our Hudson from ver. 1.361 to 1.363, and I've seen
occasional duplicate builds since.

For example, some upstream job triggers same downstream job twice.
Similarly, remotely triggering a job via curl sometimes triggers the same
job twice.

Anybody else seeing this behavior? Also, any help regarding this matter
greatly appreciated!

Thanks!
-Pasi
--
View this message in context: http://hudson.361315.n4.nabble.com/Duplicate-builds-after-update-to-ver-1-363-tp2263673p2263673.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]




--
Timothy Bingaman
Software Engineer, Open Cloud Limited
Level 4, 54-56 Cambridge Tce, Wellington, New Zealand
http://www.opencloud.com
t:  +64 4 977 4782
m:  +64 21 027 33614
linkedIn:  http://www.linkedin.com/in/timobingaman
Reply | Threaded
Open this post in threaded view
|

Re: Duplicate builds after update to ver. 1.363

Andrew Bayer
I got my duplicates of downstream builds to stop by reconfiguring the projects upstream and downstream builds, but I'm not sure whether that'll help with the curl use case. I inadvertently created a duplicate bug of this, so I've marked it as a dupe, assigned the original bug to Kohsuke, and bumped up the priority to Blocker.

A. 

On Tue, Jun 22, 2010 at 2:29 PM, Timothy Bingaman <[hidden email]> wrote:
We're seeing this as well after upgrading to 1.363.

Looks like there was a change to the BuildDependency logic allowing multiple triggers between the same two jobs (and I'm even seeing self-referencing triggers now with builds that trigger themselves endlessly).  Perhaps it was something else, but I'm thinking this change is what's causing this (r31934 to Hudson core).

No easy workarounds that I can see except to shut Hudson down and go back to the previous version.

-Timo

On 22 June 2010 18:45, tiainpa <[hidden email]> wrote:

Hi,

Yesterday I updated our Hudson from ver. 1.361 to 1.363, and I've seen
occasional duplicate builds since.

For example, some upstream job triggers same downstream job twice.
Similarly, remotely triggering a job via curl sometimes triggers the same
job twice.

Anybody else seeing this behavior? Also, any help regarding this matter
greatly appreciated!

Thanks!
-Pasi
--
View this message in context: http://hudson.361315.n4.nabble.com/Duplicate-builds-after-update-to-ver-1-363-tp2263673p2263673.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]




--
Timothy Bingaman
Software Engineer, Open Cloud Limited
Level 4, 54-56 Cambridge Tce, Wellington, New Zealand
http://www.opencloud.com
t:  +64 4 977 4782
m:  +64 21 027 33614
linkedIn:  http://www.linkedin.com/in/timobingaman

Reply | Threaded
Open this post in threaded view
|

Re: Duplicate builds after update to ver. 1.363

tiainpa
Luckily we didn't have any problems aborting the duplicate jobs for some reason, but we really had to downgrade to version 1.362 to prevent this behavior.

Andrew's advice would've been good if we only used downstream triggering, but I'm pretty sure that the advice won't work on curl triggered jobs. Thanks anyway, maybe it helps some others using 1.363 already!

-Pasi