On Wed, Oct 13, 2010 at 2:55 PM, Les Mikesell <lesmikesell_at_gmail.com> wrote:
> I'd like to find a generic scheme (and one that can be plugged into hudson
> if possible) to store build results with a versioning scheme that doesn't
> force you to keep them forever because most are obsolete after a few new
> builds but that has a close-coupling to the svn version or at least the tag
> name of the matching source. But this seems like it should be a common
> scenario and not something everyone re-invents differently.
You want a Generic scheme? It's one of the reasons I use Maven for a
release repository even for projects that are far from Mavenish.
Maven is a standard mechanism for handling a release repository, and
Maven integrates with Hudson and Subversion. If you move your release
repository or even change the software behind your release repository,
the configuration points that have to be changed are minimal.
I haven't been involved with a C/C++ project for a while, but I can
see using a Maven release repository for that. You can use "get" and
"curl" commands to fetch stuff from a Maven repository, so developers
don't need to install Maven or Java on their systems. Just setup their
Makefiles to figure out the correct URL which is not that difficult to
do.
And if your developers want to upload files into your Maven
repository, they can do that via the HTML interface both Artifactory
and Nexus have.
You probably do want to install Maven on your Hudson build machine.
This will allow Hudson to automatically upload releases to your Maven
server. Since Hudson already runs under Java, you already have Java
installed there anyway.
There may be other release repositories software out there, but in the
two odd decades I've been doing releases, I've never seen one except
for the home grown hacks that each site seems to implement.
--
David Weintraub
qazwart_at_gmail.com
Received on 2010-10-13 22:07:28 CEST