[JIRA] Created: (HUDSON-5687) Parameterized trigger from multi-configuration project does not trigger

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

[JIRA] Created: (HUDSON-5687) Parameterized trigger from multi-configuration project does not trigger

Hudson issues mailing list
Parameterized trigger from multi-configuration project does not trigger
-----------------------------------------------------------------------

                 Key: HUDSON-5687
                 URL: http://issues.hudson-ci.org/browse/HUDSON-5687
             Project: Hudson
          Issue Type: Bug
          Components: parameterized-trigger
    Affects Versions: current
         Environment: Ubuntu Linux 8.10, Sun JDK 1.6.0_14
            Reporter: sti
            Assignee: huybrechts
         Attachments: Picture 2.png

We have a multi-configuration job that builds a bunch of builds with various configurations. After the job completes, we use parameterized trigger plugin to launch a test with the respective configurations. Screenshot of the multi-configuration project is shows in attachment "Picture 2.png"

The properties file contains 2 lines like this:
BUILDTOTEST=8015
CONFIGURATION=FOOBAR

We upgraded this plugin from version 2.0 to 2.3 and discovered the downstream test job was no longer being triggered. No exceptions in the logs. No explanation in build consoles.

Downgrade back to 2.0 makes the downstream job triggering again.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-5687) Parameterized trigger from multi-configuration project does not trigger

Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136619#action_136619 ]

kphonik commented on HUDSON-5687:
---------------------------------

Any thoughts on this? We need to build another project once all our config axes have completed...

> Parameterized trigger from multi-configuration project does not trigger
> -----------------------------------------------------------------------
>
>                 Key: HUDSON-5687
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5687
>             Project: Hudson
>          Issue Type: Bug
>          Components: parameterized-trigger
>    Affects Versions: current
>         Environment: Ubuntu Linux 8.10, Sun JDK 1.6.0_14
>            Reporter: sti
>            Assignee: huybrechts
>         Attachments: Picture 2.png
>
>
> We have a multi-configuration job that builds a bunch of builds with various configurations. After the job completes, we use parameterized trigger plugin to launch a test with the respective configurations. Screenshot of the multi-configuration project is shows in attachment "Picture 2.png"
> The properties file contains 2 lines like this:
> BUILDTOTEST=8015
> CONFIGURATION=FOOBAR
> We upgraded this plugin from version 2.0 to 2.3 and discovered the downstream test job was no longer being triggered. No exceptions in the logs. No explanation in build consoles.
> Downgrade back to 2.0 makes the downstream job triggering again.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (HUDSON-5687) Parameterized trigger from multi-configuration project does not trigger

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

swiest updated HUDSON-5687:
---------------------------

    Attachment: patch_BuildTrigger.txt

The current implementation of {{hudson.plugins.parameterizedtrigger.BuildTrigger}} does not take into account the special nature of MatrixBuilds. The attached patch (patch-BuildTrigger.txt) will add MatrixBuild support like {{hudson.tasks.BuildTrigger}} does.

Anybody out there who could to review the patch?

> Parameterized trigger from multi-configuration project does not trigger
> -----------------------------------------------------------------------
>
>                 Key: HUDSON-5687
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5687
>             Project: Hudson
>          Issue Type: Bug
>          Components: parameterized-trigger
>    Affects Versions: current
>         Environment: Ubuntu Linux 8.10, Sun JDK 1.6.0_14
>            Reporter: sti
>            Assignee: huybrechts
>         Attachments: patch_BuildTrigger.txt, Picture 2.png
>
>
> We have a multi-configuration job that builds a bunch of builds with various configurations. After the job completes, we use parameterized trigger plugin to launch a test with the respective configurations. Screenshot of the multi-configuration project is shows in attachment "Picture 2.png"
> The properties file contains 2 lines like this:
> BUILDTOTEST=8015
> CONFIGURATION=FOOBAR
> We upgraded this plugin from version 2.0 to 2.3 and discovered the downstream test job was no longer being triggered. No exceptions in the logs. No explanation in build consoles.
> Downgrade back to 2.0 makes the downstream job triggering again.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-5687) Parameterized trigger from multi-configuration project does not trigger

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139792#action_139792 ]

samodelkin commented on HUDSON-5687:
------------------------------------

The patch looks good to me (I've made similar patch independently, before I found that the issue already exists in hudson issue tracker) and fixes the problem for me.

Can this patch be committed, please?

> Parameterized trigger from multi-configuration project does not trigger
> -----------------------------------------------------------------------
>
>                 Key: HUDSON-5687
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5687
>             Project: Hudson
>          Issue Type: Bug
>          Components: parameterized-trigger
>    Affects Versions: current
>         Environment: Ubuntu Linux 8.10, Sun JDK 1.6.0_14
>            Reporter: sti
>            Assignee: huybrechts
>         Attachments: patch_BuildTrigger.txt, Picture 2.png
>
>
> We have a multi-configuration job that builds a bunch of builds with various configurations. After the job completes, we use parameterized trigger plugin to launch a test with the respective configurations. Screenshot of the multi-configuration project is shows in attachment "Picture 2.png"
> The properties file contains 2 lines like this:
> BUILDTOTEST=8015
> CONFIGURATION=FOOBAR
> We upgraded this plugin from version 2.0 to 2.3 and discovered the downstream test job was no longer being triggered. No exceptions in the logs. No explanation in build consoles.
> Downgrade back to 2.0 makes the downstream job triggering again.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

Reply | Threaded
Open this post in threaded view
|

[JIRA] Assigned: (HUDSON-5687) Parameterized trigger from multi-configuration project does not trigger

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mindless reassigned HUDSON-5687:
--------------------------------

    Assignee: mindless  (was: huybrechts)

> Parameterized trigger from multi-configuration project does not trigger
> -----------------------------------------------------------------------
>
>                 Key: HUDSON-5687
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5687
>             Project: Hudson
>          Issue Type: Bug
>          Components: parameterized-trigger
>    Affects Versions: current
>         Environment: Ubuntu Linux 8.10, Sun JDK 1.6.0_14
>            Reporter: sti
>            Assignee: mindless
>         Attachments: patch_BuildTrigger.txt, Picture 2.png
>
>
> We have a multi-configuration job that builds a bunch of builds with various configurations. After the job completes, we use parameterized trigger plugin to launch a test with the respective configurations. Screenshot of the multi-configuration project is shows in attachment "Picture 2.png"
> The properties file contains 2 lines like this:
> BUILDTOTEST=8015
> CONFIGURATION=FOOBAR
> We upgraded this plugin from version 2.0 to 2.3 and discovered the downstream test job was no longer being triggered. No exceptions in the logs. No explanation in build consoles.
> Downgrade back to 2.0 makes the downstream job triggering again.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-5687) Parameterized trigger from multi-configuration project does not trigger

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139806#action_139806 ]

scm_issue_link commented on HUDSON-5687:
----------------------------------------

Code changed in hudson
User: : mindless
Path:
 trunk/hudson/plugins/parameterized-trigger/src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java
http://hudson-ci.org/commit/32432
Log:
[parameterized-trigger] [FIXED HUDSON-5687] add patch from swiest to add
support for matrix projects.


> Parameterized trigger from multi-configuration project does not trigger
> -----------------------------------------------------------------------
>
>                 Key: HUDSON-5687
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5687
>             Project: Hudson
>          Issue Type: Bug
>          Components: parameterized-trigger
>    Affects Versions: current
>         Environment: Ubuntu Linux 8.10, Sun JDK 1.6.0_14
>            Reporter: sti
>            Assignee: mindless
>         Attachments: patch_BuildTrigger.txt, Picture 2.png
>
>
> We have a multi-configuration job that builds a bunch of builds with various configurations. After the job completes, we use parameterized trigger plugin to launch a test with the respective configurations. Screenshot of the multi-configuration project is shows in attachment "Picture 2.png"
> The properties file contains 2 lines like this:
> BUILDTOTEST=8015
> CONFIGURATION=FOOBAR
> We upgraded this plugin from version 2.0 to 2.3 and discovered the downstream test job was no longer being triggered. No exceptions in the logs. No explanation in build consoles.
> Downgrade back to 2.0 makes the downstream job triggering again.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

Reply | Threaded
Open this post in threaded view
|

[JIRA] Resolved: (HUDSON-5687) Parameterized trigger from multi-configuration project does not trigger

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

scm_issue_link resolved HUDSON-5687.
------------------------------------

    Resolution: Fixed

> Parameterized trigger from multi-configuration project does not trigger
> -----------------------------------------------------------------------
>
>                 Key: HUDSON-5687
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5687
>             Project: Hudson
>          Issue Type: Bug
>          Components: parameterized-trigger
>    Affects Versions: current
>         Environment: Ubuntu Linux 8.10, Sun JDK 1.6.0_14
>            Reporter: sti
>            Assignee: mindless
>         Attachments: patch_BuildTrigger.txt, Picture 2.png
>
>
> We have a multi-configuration job that builds a bunch of builds with various configurations. After the job completes, we use parameterized trigger plugin to launch a test with the respective configurations. Screenshot of the multi-configuration project is shows in attachment "Picture 2.png"
> The properties file contains 2 lines like this:
> BUILDTOTEST=8015
> CONFIGURATION=FOOBAR
> We upgraded this plugin from version 2.0 to 2.3 and discovered the downstream test job was no longer being triggered. No exceptions in the logs. No explanation in build consoles.
> Downgrade back to 2.0 makes the downstream job triggering again.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-5687) Parameterized trigger from multi-configuration project does not trigger

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140480#action_140480 ]

Darkfang commented on HUDSON-5687:
----------------------------------

I've tried building the last version from SVN and load it into hudson 1.361
The bug is still present. By looking at the proposed patch and the applied ones it seems a part of the patch has been left out:
-public class BuildTrigger extends Notifier implements DependecyDeclarer {
+public class BuildTrigger extends Notifier implements DependecyDeclarer, MatrixAggregatable {

I'm no expert in Java and never had a look at Hudson code but with the applied patch not working, I'd say this bit is important !

> Parameterized trigger from multi-configuration project does not trigger
> -----------------------------------------------------------------------
>
>                 Key: HUDSON-5687
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5687
>             Project: Hudson
>          Issue Type: Bug
>          Components: parameterized-trigger
>    Affects Versions: current
>         Environment: Ubuntu Linux 8.10, Sun JDK 1.6.0_14
>            Reporter: sti
>            Assignee: mindless
>         Attachments: patch_BuildTrigger.txt, Picture 2.png
>
>
> We have a multi-configuration job that builds a bunch of builds with various configurations. After the job completes, we use parameterized trigger plugin to launch a test with the respective configurations. Screenshot of the multi-configuration project is shows in attachment "Picture 2.png"
> The properties file contains 2 lines like this:
> BUILDTOTEST=8015
> CONFIGURATION=FOOBAR
> We upgraded this plugin from version 2.0 to 2.3 and discovered the downstream test job was no longer being triggered. No exceptions in the logs. No explanation in build consoles.
> Downgrade back to 2.0 makes the downstream job triggering again.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-5687) Parameterized trigger from multi-configuration project does not trigger

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140483#action_140483 ]

Darkfang commented on HUDSON-5687:
----------------------------------

Note: I've applied the line missing from the patch in SVN repo, recompiled and reloaded it into hudson and it now works perfectly !

> Parameterized trigger from multi-configuration project does not trigger
> -----------------------------------------------------------------------
>
>                 Key: HUDSON-5687
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5687
>             Project: Hudson
>          Issue Type: Bug
>          Components: parameterized-trigger
>    Affects Versions: current
>         Environment: Ubuntu Linux 8.10, Sun JDK 1.6.0_14
>            Reporter: sti
>            Assignee: mindless
>         Attachments: patch_BuildTrigger.txt, Picture 2.png
>
>
> We have a multi-configuration job that builds a bunch of builds with various configurations. After the job completes, we use parameterized trigger plugin to launch a test with the respective configurations. Screenshot of the multi-configuration project is shows in attachment "Picture 2.png"
> The properties file contains 2 lines like this:
> BUILDTOTEST=8015
> CONFIGURATION=FOOBAR
> We upgraded this plugin from version 2.0 to 2.3 and discovered the downstream test job was no longer being triggered. No exceptions in the logs. No explanation in build consoles.
> Downgrade back to 2.0 makes the downstream job triggering again.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-5687) Parameterized trigger from multi-configuration project does not trigger

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140489#action_140489 ]

scm_issue_link commented on HUDSON-5687:
----------------------------------------

Code changed in hudson
User: : mindless
Path:
 trunk/hudson/plugins/parameterized-trigger/src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java
http://hudson-ci.org/commit/33246
Log:
[HUDSON-5687] oops, missed a line in applying patch (thx Darkfang)


> Parameterized trigger from multi-configuration project does not trigger
> -----------------------------------------------------------------------
>
>                 Key: HUDSON-5687
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5687
>             Project: Hudson
>          Issue Type: Bug
>          Components: parameterized-trigger
>    Affects Versions: current
>         Environment: Ubuntu Linux 8.10, Sun JDK 1.6.0_14
>            Reporter: sti
>            Assignee: mindless
>         Attachments: patch_BuildTrigger.txt, Picture 2.png
>
>
> We have a multi-configuration job that builds a bunch of builds with various configurations. After the job completes, we use parameterized trigger plugin to launch a test with the respective configurations. Screenshot of the multi-configuration project is shows in attachment "Picture 2.png"
> The properties file contains 2 lines like this:
> BUILDTOTEST=8015
> CONFIGURATION=FOOBAR
> We upgraded this plugin from version 2.0 to 2.3 and discovered the downstream test job was no longer being triggered. No exceptions in the logs. No explanation in build consoles.
> Downgrade back to 2.0 makes the downstream job triggering again.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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