You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "apache maillist (JIRA)" <ji...@codehaus.org> on 2008/10/04 01:39:08 UTC

[jira] Created: (CONTINUUM-1917) When "Build Fresh" is check, "Always Build" should NOT be implicit.

When "Build Fresh" is check, "Always Build" should NOT be implicit.
-------------------------------------------------------------------

                 Key: CONTINUUM-1917
                 URL: http://jira.codehaus.org/browse/CONTINUUM-1917
             Project: Continuum
          Issue Type: Improvement
          Components: SCM
    Affects Versions: 1.2
         Environment: Linux
            Reporter: apache maillist


When "Build Fresh" is check, it should always do a clean checkout rather than update, but it should ONLY build when there are changes committed, it should NOT build if no changes are committed. Thus, I do not think "Always Build" should be implicit.

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

        

[jira] Commented: (CONTINUUM-1917) When "Build Fresh" is check, "Always Build" should NOT be implicit.

Posted by "apache maillist (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149858#action_149858 ] 

apache maillist commented on CONTINUUM-1917:
--------------------------------------------

Before CONTINUUM-1838, continuum will do clean checkout and will not build regardless there are changes committed or not, after CONTINUUM-1838, continuum now will always do clean check out and builds even no changes are committed.
Here is what I would suggest:
"Fresh build" should always do clean checkout but ONLY builds when there are changes committed.

> When "Build Fresh" is check, "Always Build" should NOT be implicit.
> -------------------------------------------------------------------
>
>                 Key: CONTINUUM-1917
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1917
>             Project: Continuum
>          Issue Type: Improvement
>          Components: SCM
>    Affects Versions: 1.2
>         Environment: Linux
>            Reporter: apache maillist
>
> When "Build Fresh" is check, it should always do a clean checkout rather than update, but it should ONLY build when there are changes committed, it should NOT build if no changes are committed. Thus, I do not think "Always Build" should be implicit.

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

        

[jira] Updated: (CONTINUUM-1917) When "Build Fresh" is check, "Always Build" should NOT be implicit.

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated CONTINUUM-1917:
------------------------------------

    Fix Version/s: 1.x

I'm inclined to agree considering there are separate options.

> When "Build Fresh" is check, "Always Build" should NOT be implicit.
> -------------------------------------------------------------------
>
>                 Key: CONTINUUM-1917
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1917
>             Project: Continuum
>          Issue Type: Improvement
>          Components: SCM
>    Affects Versions: 1.2
>         Environment: Linux
>            Reporter: apache maillist
>             Fix For: 1.x
>
>
> When "Build Fresh" is check, it should always do a clean checkout rather than update, but it should ONLY build when there are changes committed, it should NOT build if no changes are committed. Thus, I do not think "Always Build" should be implicit.

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

        

[jira] Commented: (CONTINUUM-1917) When "Build Fresh" is check, "Always Build" should NOT be implicit.

Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160412#action_160412 ] 

Wendy Smoak commented on CONTINUUM-1917:
----------------------------------------

As this appears to request reverting the behavior added in CONTINUUM-1838, I suggest bringing it up on the user list to see how the community feels about it.

> When "Build Fresh" is check, "Always Build" should NOT be implicit.
> -------------------------------------------------------------------
>
>                 Key: CONTINUUM-1917
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1917
>             Project: Continuum
>          Issue Type: Improvement
>          Components: SCM
>    Affects Versions: 1.2
>         Environment: Linux
>            Reporter: apache maillist
>
> When "Build Fresh" is check, it should always do a clean checkout rather than update, but it should ONLY build when there are changes committed, it should NOT build if no changes are committed. Thus, I do not think "Always Build" should be implicit.

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