Mitch in you post earlier you described the polluting of the tag
directory over time with numerous CI commits. This had been a concern
to me, however our project was not old enough for this to become a
seriouss problem.
It was a requirement of the build system to tag successful builds for
easier build reproducibility. However this is an elegant solution that
does away with the need for what could become a very large tag directory.
Thank you Shawn, I need to look into this and see if it is doable on our
build system.
Shawn Castrianni wrote:
My raw checked in ivy.xml files contain this:
<info organisation="Company" module="dsgeol">
<repository name="Subversion"
url="svn://svnserv.lgc.com/repos/dsgeol${env.SVN_BRANCH_TAG}${env.SVN_REPO_REVISION}"/>
<description>This module contains the Geology
Application.</description>
</info>
Then my CI tool sets the SVN_BRANCH_TAG and SVN_REPO_REVISION environment
variables so that it gets resolved to something like:
<info organisation="Company" module="dsgeol">
<repository name="Subversion"
url="svn://svnserv.lgc.com/repos/dsgeol/branches/[EMAIL PROTECTED]"/>
<description>This module contains the Geology
Application.</description>
</info>
That tells me everything I need to know to later checkout the exact source that
built this version of the module
---
Shawn Castrianni
-----Original Message-----
From: Mitch Gitman [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 7:11 PM
To: [email protected]
Subject: Re: buildnumber Ant task & automated updates of ivy.xml
Shawn, I think you just offered much the same solution that I was trying to
describe, just far more verbosely. Good to see people coalescing on the same
wavelength.
One small difference. While I had talked about creating a separate
properties file just to hold the Subversion version number, you decided put
that version right in the ivy.xml. The question is, where? I'm not aware of
a natural place in the ivy-module schema to put that extra piece of
information.
On Thu, Nov 20, 2008 at 8:46 AM, Shawn Castrianni <
[EMAIL PROTECTED]> wrote:
If the source comes from CVS, we tag it. If the source comes from SVN, I
use the CI system to set an ANT property based on what subversion revision
was checked out which gets resolved and stored into the ivy.xml file for
publishing. Then any published build will contain the ivy.xml file which
contains the revision number from subversion from which it was built. Once
nice feature of subversion.
---
Shawn Castrianni
-----Original Message-----
From: Niklas Matthies [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 7:27 AM
To: [email protected]
Subject: Re: buildnumber Ant task & automated updates of ivy.xml
I'm curious: Given a build number, how do you later find the
corresponding sources in SVN? Does the CI system tag the sources
with the auto-incremented build number?
-- Niklas Matthies
----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and
privileged information for the sole use of the intended recipient. Any review,
use, distribution, or disclosure by others is strictly prohibited. If you are
not the intended recipient (or authorized to receive information for the
intended recipient), please contact the sender by reply e-mail and delete all
copies of this message.
