If "Fresh Build" is used, "Always build" should be implicit but it doesn't

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1
  • Fix Version/s: 1.2.1
  • Component/s: None
  • Labels:
    None
  • Environment:
    Windows 2003, Continuum 1.1 under Tomcat 6 using mvane 2.0.9
  • Complexity:
    Intermediate

Issue Links

is related to

Improvement - An improvement or enhancement to an existing feature or task. CONTINUUM-1917 When "Build Fresh" is check, "Always Build" should NOT be implicit.

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Emmanuel Venisse added a comment -

Done in r.699174

Show
Emmanuel Venisse added a comment - Done in r.699174
Hide
Permalink
apache maillist added a comment -

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.

Show
apache maillist added a comment - 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.

People

  • Assignee:
    Emmanuel Venisse
    Reporter:
    Raffaele Gambelli
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: