[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: make force-tag gone

On Tue, 2008-09-09 at 08:12 -0800, Jeff Spaleta wrote:
> On Tue, Sep 9, 2008 at 8:03 AM, Denis Leroy <denis poolshark org> wrote:
> > There's no logic here. You're not forcing people to tag after every CVS
> > check-in, as far as I know. If a release 'n' fails to build (for example,
> > because you forgot to check-in a patch), it makes zero sense to bump to n+1,
> > because release 'n' never *existed* in the first place, since it was never
> > built. That has zero impact over auditing. Spec file auditing is done
> > through CVS.
> I believe he misspoke.  You are of course free to make 300 small
> separate specfile changes between each build attempt.
> There is a desire to move to a point where we can be reasonably sure
> that a cvs tag corresponds to a specific build.  Since we have no way
> of making only tags corresponding to successfully built packages
> immutable, all tags must be immutable.
> Find me a way to mark only the subset of cvs tags which correspond to
> a successful koji build as immutable.

If this is the aim, then koji should be the one to tag the CVS after a
build is successful.
It doesn't make sense to tag an unsuccessful build,a nd it is an
unnecessary burden on developers.

Automation is better, let koji do it.


Simo Sorce * Red Hat, Inc * New York

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]