ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart" <>
Subject RE: Status Promotion Best Practice?
Date Tue, 18 Sep 2007 09:56:02 GMT

Hmm, it seems that no one has a good response to your questions.  I don't
have it neither, but here is what I think about it:

Maybe the build promotions management and dependency management are two
different things that should be handled separately.

For instance, you can have a file or a database somewhere telling which
version has passed this step of your development lifecycle.

You can see build promotions has a workflow where dependency management has
maybe nothing to do.

Of curse, build promotions and dependency management have to share
something: the version number, artefacts, and maybe some other meta-data.  

They are meeting together around the repository management, which in turn
might require a third dedicated tool.

I have to admit that I have no idea if I'm right or not...  It was just my 2


> -----Original Message-----
> From: Nascif Abousalh-Neto []
> Sent: vendredi 14 septembre 2007 19:34
> To:
> Subject: Status Promotion Best Practice?
> A question about using status during the development cycle, in a a
> scenario where different teams are responsible for the status
> "promotion".
> Let's say a development team publishes an artifact with status X,
> indicating a basic level of unit testing.
> Then a testing team retrieves this artifact (probably using
> rev="latest.X"), runs a suite of integration tests, and decides to
> "bless" the artifact with the next status value, say Y.
> How can that process be implemented? It seems the testing team would
> have to do another publish or another deliver (not sure which one),
> keeping the existing version but changing the status to Y.
> Does that makes sense? I have the feeling that this operation should be
> common enough to have a shortcut, perhaps something like <ivy:promote
> newstatus="Y" .../>
> Anybody out there doing something similar?
> Thanks,
>   Nascif

View raw message