I just had a crisis of faith (in artifact repos) vs. checking libs into
source control. How do I build old versions of my software if a version is
deleted?
So renaming and moving may sound like a bad idea to most... it sounds like a
bad idea to me too. And I'm sure someone is going to correct me but here's
the problem I'm thinking about.
I'm setting up an Artifactory server for the first time and after uploading
a bunch of 3rd party libs that my build depends on it occurs to me that
where I put all of them is all wrong. It's wrong because I can't change
their paths... and I probably can't change their paths ever. Which means I
can't refactor my repository to meet future requirements.... which means
they need to be perfect the first time.
You're probably thinking at this point... if you want repeatable builds you
shouldn't be moving things around anyway!
Well... what if the old url path resolutions were maintained when the
artifact was moved or deleted? Wouldn't this allow me to build old versions
of my software while still being able to refactor my repository? This would
be a better solution than uploading the same artifact twice to 2 different
paths wouldn't it? Maybe maven and ivy could support redirects? Or maybe
they do and I'm just too new to know that.
My concern is obviously that even as things are deleted that old builds will
be broken. If you could delete something or hide it instead and have that
process be differentiated from a purge process it would still allow me to
repeat old builds if redirects just worked.
Am I over-thinking all of this?
I'm using ant and ivy. Mostly because I'm an ant ninja and maven seemed like
overkill when all I want is dependency management and a versioning scheme.
--
View this message in context:
http://forums.jfrog.org/Feature-idea-Renaming-or-moving-an-artifact-tp5594853p5594853.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
