Version Control?

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Version Control?

Jordo
Hello

First 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%2Ftomcat

Thanks!
Reply | Threaded
Open this post in threaded view
|

Re: Version Control?

dave_p
I am not super-sure yet, but I think it has something to do with this setting. (See circled/attached PNG.)

It seems to add a timestamp to the build/version number, so they're uniquely named.

Dave P.

-----Original Message-----
From: Jordo [mailto:[hidden email]]
Sent: Thursday, February 06, 2014 8:59 AM
To: [hidden email]
Subject: [Artifactory-users] Version Control?

Hello

First 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%2Ftomcat

Thanks!



--
View this message in context: http://forums.jfrog.org/Version-Control-tp7579595.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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Capture.PNG (13K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Version Control?

Jordo
I think all my repos are set up that way..

You know what i just noticed, if you do build and overwrite an artifact, you can't tell from the artifact properties screen. It just says when it was created but not when it was modified / over written.
Reply | Threaded
Open this post in threaded view
|

Re: Version Control?

pscheir
This post was updated on .
In reply to this post by Jordo
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-overwritten

Best, Peter


Jordo wrote
Hello

First 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%2Ftomcat

Thanks!
Reply | Threaded
Open this post in threaded view
|

Re: Version Control?

Jordo
I do tick the build number up each time.  We are using jenkins to build and it all happens automatically.

So what you are suggesting is to leverage folder hierarchy to manage different versions of the the same artifact?  This makes it more difficult to parameterize deployment later down the pipeline, .eg.

get_artifact(Name,rev)

A refractor would be necessary...

get_artifact(path+"/"+rev+name)

You get it..
Reply | Threaded
Open this post in threaded view
|

Re: Version Control?

pscheir
Ah, I see.

Well, we use the folder hierarchy since we do not use the Build Server Integration of Artifactory: http://www.jfrog.com/confluence/display/RTF/Build+Integration

Since you are using Jenkins you can also use the Jenkins Artifactory Plugin: https://wiki.jenkins-ci.org/display/JENKINS/Artifactory+Plugin

And this REST call:

https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-RetrieveBuildArtifactsArchive

Best, Peter

Jordo wrote
I do tick the build number up each time.  We are using jenkins to build and it all happens automatically.

So what you are suggesting is to leverage folder hierarchy to manage different versions of the the same artifact?  This makes it more difficult to parameterize deployment later down the pipeline, .eg.

get_artifact(Name,rev)

A refractor would be necessary...

get_artifact(path+"/"+rev+name)

You get it..
Reply | Threaded
Open this post in threaded view
|

Re: Version Control?

Jordo
That was helpful!

Thank you!
Reply | Threaded
Open this post in threaded view
|

Re: Version Control?

Jordo
Hey folks, I figured it out.

My artifactory server ran out of space, which I found odd as I believed I was just overwriting the same Artifacts.  Turns out, every single build result was being stored, exactly in the manner I was asking about.

If you go to any artifact, and click the 'Builds' tab, you will see all the builds that produced that artifact. If you click on a build, you can say 'go to build'.  That will bring you to a window that shows you all the artifacts said build created.  From here, you can click on any of them and click 'Download'.  I tested this with my the first build of a test project and found a very old version of that artifact.

Thus... versioning.. exactly as I was seeking.

Thanks everyone for your help.
Jordan