continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marica Tan <marica....@gmail.com>
Subject Re: Thoughts on build environment selection when releasing in distributed build setup
Date Wed, 03 Feb 2010 02:24:17 GMT
On Wed, Feb 3, 2010 at 10:04 AM, Wendy Smoak <wsmoak@gmail.com> wrote:

> On Tue, Feb 2, 2010 at 6:58 PM, Marica Tan <marica.tan@gmail.com> wrote:
> > I think the reasons why it needs to have a previous successful build are:
> >
> > 1. to make sure there is a working copy
>
> You don't need to build to have a working copy, just check out.
>
>
We could add a check to see if the working copy exists. If it doesn't then
do a checkout.


> > 2. to make sure we have a successful build before we tag. there is no
> sense
> > to release a project if the build failed because the release will fail as
> > well.
>
> There's no relationship between a successful build in the past and a
> successful release now.  A commit in between could have fixed (or
> broken) the build, giving a different result when you try to release.
>
> This feels like an arbitrary restriction that could be removed.
>
> Yes, I agree.


> --
> Wendy
>

--
Marica

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message