Hi, best approach from my point of view is to increment the build number with
each build. In addition I would disable overwriting of artifacts for the
automatic deployment via the build machine:
http://stackoverflow.com/questions/6461152/how-can-i-prevent-previously-deployed-artifacts-from-being-overwrittenBest,
Peter
Jordo wrote
> HelloFirst post here. I searched and couldn't find anything on this
> topic.We are use to using something like subversion to hold our artifacts.
> We simply build to a workspace and check in when finished. The nice thing
> is, checking in an already existing artifact (same name, etc) allows us to
> go back to artifacts past if needed pretty easily. This has proven useful
> at times. In artifactory, I have been overwriting the same artifacts on
> every build. Is there a way to go back in time to an artifact from a
> previous build? Or would I need to implement versioning via file/folder
> structure to handle this?
> i.e.http://repo.jfrog.org/artifactory/webapp/browserepo.html?pathId=distributions%3Aorg%2Fapache%2FtomcatThanks!
--
View this message in context:
http://forums.jfrog.org/Version-Control-tp7579595p7579603.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
