You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@continuum.apache.org by "Trygve Laugstol (JIRA)" <ji...@codehaus.org> on 2006/01/23 09:44:06 UTC

[jira] Commented: (CONTINUUM-567) A build must be launched if we have changes since last build (for same build definition) and not only if we have detected changes when we run scm update commad

    [ http://jira.codehaus.org/browse/CONTINUUM-567?page=comments#action_56634 ] 

Trygve Laugstol commented on CONTINUUM-567:
-------------------------------------------

I don't understand this issue, isn't "scm update" the only way we know if there has been a change in the remote repository?

Or do you mean when there are two build definitions using the same working directory where doing scm up once will only trigger one of the build definitions? If so the resolution to this issue is IMO to give each build definition it's own working directory.

> A build must be launched if we have changes since last build (for same build definition) and not only if we have detected changes when we run scm update commad
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: CONTINUUM-567
>          URL: http://jira.codehaus.org/browse/CONTINUUM-567
>      Project: Continuum
>         Type: Improvement

>   Components: Core system
>     Versions: 1.0.2
>     Reporter: Emmanuel Venisse
>     Assignee: nick gonzalez
>      Fix For: 1.1-alpha-1

>
>


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