[
http://jira.codehaus.org/browse/CONTINUUM-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated CONTINUUM-686:
-----------------------------------
Fix Version/s: (was: 1.2)
1.3
> Provide each build definition for a given project with its own checked-out
> workspace.
> -------------------------------------------------------------------------------------
>
> Key: CONTINUUM-686
> URL: http://jira.codehaus.org/browse/CONTINUUM-686
> Project: Continuum
> Issue Type: New Feature
> Components: Core system
> Affects Versions: 1.0.3
> Reporter: Christian Gruber
> Fix For: 1.3
>
>
> Each build definition should not work off of the same workspace as another
> build definition. Otherwise, the notion of overlapping schedules is
> meaningless.
> This particularly affects configurations where several build definitions are
> defined for varying situations, such as a seperate one for continuous (five
> minute loop), one for a daily integration build, one to push the site
> nightly, and a "never" scheduled build (scheduled for 2061 or something) that
> can be used for full manually triggered builds, but will never build on its
> own. These four build defs have different purposes, and change in the source
> of one should imply change in the source of another. However, if they share
> a workspace, then change in the shared workspace would be masked by the
> five-minute-loop schedule, which would (presumably) succeed, thus impeding
> any other builds.
> Also, the changes between the build at 5:30 and the build at 12:00am would be
> large, but if there were fifteen other builds in between because of
> continuous build schedules, then the "changes" listing in the build process
> will be masked by all those other changes. Having separate workspaces
> provides a clean solution to many of the above issues, and allows problems to
> be examined in isolation.
--
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
