[JIRA] Created: (HUDSON-7085) Ivy Projects using multi-module, non-aggregated, incremental build sometimes build their modules in the wrong order

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

[JIRA] Created: (HUDSON-7085) Ivy Projects using multi-module, non-aggregated, incremental build sometimes build their modules in the wrong order

Hudson issues mailing list
Ivy Projects using multi-module, non-aggregated, incremental build sometimes build their modules in the wrong order
-------------------------------------------------------------------------------------------------------------------

                 Key: HUDSON-7085
                 URL: http://issues.hudson-ci.org/browse/HUDSON-7085
             Project: Hudson
          Issue Type: Bug
          Components: ivy
            Reporter: tbingaman
            Assignee: tbingaman


When a multi-module Ivy Project is configured to build modules as separate jobs and to only do an incremental build then when svn changes span multiple dependent modules then they will not wait for each other.

--
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-7085) Ivy Projects using multi-module, non-aggregated, incremental build sometimes build their modules in the wrong order

Hudson issues mailing list

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

tbingaman commented on HUDSON-7085:
-----------------------------------

Fixed in r33282 (forgot to enter JIRA issue in commit)

> Ivy Projects using multi-module, non-aggregated, incremental build sometimes build their modules in the wrong order
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-7085
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-7085
>             Project: Hudson
>          Issue Type: Bug
>          Components: ivy
>            Reporter: tbingaman
>            Assignee: tbingaman
>
> When a multi-module Ivy Project is configured to build modules as separate jobs and to only do an incremental build then when svn changes span multiple dependent modules then they will not wait for each other.

--
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-7085) Ivy Projects using multi-module, non-aggregated, incremental build sometimes build their modules in the wrong order

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

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

tbingaman resolved HUDSON-7085.
-------------------------------

    Resolution: Fixed

A new CauseOfBlockage has been added so that modules within an Ivy Project configured to do non-aggregated, incremental builds will wait for each other and therefore build in the correct order.

> Ivy Projects using multi-module, non-aggregated, incremental build sometimes build their modules in the wrong order
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-7085
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-7085
>             Project: Hudson
>          Issue Type: Bug
>          Components: ivy
>            Reporter: tbingaman
>            Assignee: tbingaman
>
> When a multi-module Ivy Project is configured to build modules as separate jobs and to only do an incremental build then when svn changes span multiple dependent modules then they will not wait for each other.

--
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]