Snapshots for a generic repository

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

Snapshots for a generic repository

David Ward
We currently store tarballs of our system in artifactory after each build. We do not use maven, gradle, etc., so we store them in a generic repository.

The problem that we are having is that the repository keeps growing and growing because each build is a separate artifact; however, old versions of the build are not really useful.

For maven/gradle repositories, we could configure the repository as a snapshot repository and limit versions to a small number.

Is there some way to limit the number of artifacts in a generic repository in a similar manner? For example, only allow 5 artifacts (our build tarballs) in the repository. If you put in more than five, the oldest artifact will be deleted.

Thanks.

David
Reply | Threaded
Open this post in threaded view
|

Re: Snapshots for a generic repository

dave_p
I had a similar problem with these OVA appliances (versioned releases, not snapshots) one of our teams produces nightly - ended up “fixing” it by writing a python script that uses the artifactory API to list the contents of a repository, sort them by date, and delete the oldest ones. (We retain 7, but the idea is the same.) Then added it to crontab.

Interested in knowing if there’s a better way.

Theoretically, I suppose you could use a maven repository to store tarballs. For some reason, I’ve got a maven repo with a bunch of ISOs in it. :-D

-Dave P.

On Jan 21, 2016, at 1:49 PM, David Ward <[hidden email]> wrote:

> We currently store tarballs of our system in artifactory after each build. We
> do not use maven, gradle, etc., so we store them in a generic repository.
>
> The problem that we are having is that the repository keeps growing and
> growing because each build is a separate artifact; however, old versions of
> the build are not really useful.
>
> For maven/gradle repositories, we could configure the repository as a
> snapshot repository and limit versions to a small number.
>
> Is there some way to limit the number of artifacts in a generic repository
> in a similar manner? For example, only allow 5 artifacts (our build
> tarballs) in the repository. If you put in more than five, the oldest
> artifact will be deleted.
>
> Thanks.
>
> David
>
>
>
>
> --
> View this message in context: http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Artifactory-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

RE: Snapshots for a generic repository

David Ward

D:

 

I tried using a maven repository and it doesn’t know that the tarballs are snapshots so it lets you store as many as you want. I guess we could fudge a maven environment and generate the tarballs as snapshots, but that’s silly work.

 

I know I can do the versioning with a script. But, since artifactory already has a similar approach for maven/gradle/ivy, it would seem symmetrical to have a similar policy for generic repositories. Plus, we are actually deploying our artifacts from bamboo using the default artifactory plugin so we would have to reproduce that.

 

It just seems this is something that artifactory should support.

 

Thanks.

 

David

 

From: dave_p [via Artifactory] [mailto:ml-node+[hidden email]]
Sent: Thursday, January 21, 2016 7:17 PM
To: Ward, David (Proxy) <[hidden email]>
Subject: Re: Snapshots for a generic repository

 

I had a similar problem with these OVA appliances (versioned releases, not snapshots) one of our teams produces nightly - ended up “fixing” it by writing a python script that uses the artifactory API to list the contents of a repository, sort them by date, and delete the oldest ones. (We retain 7, but the idea is the same.) Then added it to crontab.

Interested in knowing if there’s a better way.

Theoretically, I suppose you could use a maven repository to store tarballs. For some reason, I’ve got a maven repo with a bunch of ISOs in it. :-D

-Dave P.

On Jan 21, 2016, at 1:49 PM, David Ward <[hidden email]> wrote:


> We currently store tarballs of our system in artifactory after each build. We
> do not use maven, gradle, etc., so we store them in a generic repository.
>
> The problem that we are having is that the repository keeps growing and
> growing because each build is a separate artifact; however, old versions of
> the build are not really useful.
>
> For maven/gradle repositories, we could configure the repository as a
> snapshot repository and limit versions to a small number.
>
> Is there some way to limit the number of artifacts in a generic repository
> in a similar manner? For example, only allow 5 artifacts (our build
> tarballs) in the repository. If you put in more than five, the oldest
> artifact will be deleted.
>
> Thanks.
>
> David
>
>
>
>
> --
> View this message in context: http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Artifactory-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751p7580753.html

To unsubscribe from Snapshots for a generic repository, click here.
NAML

CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient. If you received this in error, please do not read, distribute, or take action in reliance upon this message. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message. Act 5.6.102a.c
Reply | Threaded
Open this post in threaded view
|

Re: Snapshots for a generic repository

HughG_TMVSE
Hi David,

I think Artifactory does support this for any repo, as long as it follows one of the repo layouts in your configuration.  You can only add non-standard layouts in the Pro version (not OSS), but you can assign any layout to a Generic repo, I think.  If your current set of files doesn't match one of the existing layouts, perhaps you could move them around with a one-off script?

https://www.jfrog.com/confluence/display/RTF/Repository+Layouts

Hope that helps,
Hugh.


From: David Ward [[hidden email]]
Sent: Friday, January 22, 2016 02:25
To: [hidden email]
Subject: Re: [Artifactory-users] Snapshots for a generic repository

D:

 

I tried using a maven repository and it doesn’t know that the tarballs are snapshots so it lets you store as many as you want. I guess we could fudge a maven environment and generate the tarballs as snapshots, but that’s silly work.

 

I know I can do the versioning with a script. But, since artifactory already has a similar approach for maven/gradle/ivy, it would seem symmetrical to have a similar policy for generic repositories. Plus, we are actually deploying our artifacts from bamboo using the default artifactory plugin so we would have to reproduce that.

 

It just seems this is something that artifactory should support.

 

Thanks.

 

David

 

From: dave_p [via Artifactory] [mailto:ml-node+[hidden email]]
Sent: Thursday, January 21, 2016 7:17 PM
To: Ward, David (Proxy) <[hidden email]>
Subject: Re: Snapshots for a generic repository

 

I had a similar problem with these OVA appliances (versioned releases, not snapshots) one of our teams produces nightly - ended up “fixing” it by writing a python script that uses the artifactory API to list the contents of a repository, sort them by date, and delete the oldest ones. (We retain 7, but the idea is the same.) Then added it to crontab.

Interested in knowing if there’s a better way.

Theoretically, I suppose you could use a maven repository to store tarballs. For some reason, I’ve got a maven repo with a bunch of ISOs in it. :-D

-Dave P.

On Jan 21, 2016, at 1:49 PM, David Ward <[hidden email]> wrote:


> We currently store tarballs of our system in artifactory after each build. We
> do not use maven, gradle, etc., so we store them in a generic repository.
>
> The problem that we are having is that the repository keeps growing and
> growing because each build is a separate artifact; however, old versions of
> the build are not really useful.
>
> For maven/gradle repositories, we could configure the repository as a
> snapshot repository and limit versions to a small number.
>
> Is there some way to limit the number of artifacts in a generic repository
> in a similar manner? For example, only allow 5 artifacts (our build
> tarballs) in the repository. If you put in more than five, the oldest
> artifact will be deleted.
>
> Thanks.
>
> David
>
>
>
>
> --
> View this message in context: http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Artifactory-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751p7580753.html

To unsubscribe from Snapshots for a generic repository, click here.
NAML

CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient. If you received this in error, please do not read, distribute, or take action in reliance upon this message. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message. Act 5.6.102a.c

View this message in context: RE: Snapshots for a generic repository
Sent from the Artifactory - Users mailing list archive at Nabble.com.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

RE: Snapshots for a generic repository

David Ward

H:

 

Thanks for the pointers.

 

I created a new layout (tarball-default) by duplicating the simple-default layout. But, it still didn’t give me any configuration like the maven layout has for Max. Unique Snapshots, etc.

 

I then created a new layout by duplicating maven-default. But, still no configuration to limit the number of snapshots, etc.

 

So, I’m pretty lost here. I just want Artifactory to give me the capabilities that it has for its other layouts – e.g., only keep the last 2 versions of an integration build – but that doesn’t seem to be possible without writing our own scripts.

 

David

 

 

From: HughG_TMVSE [via Artifactory] [mailto:ml-node+[hidden email]]
Sent: Friday, January 22, 2016 4:49 AM
To: Ward, David (Proxy) <[hidden email]>
Subject: Re: Snapshots for a generic repository

 

Hi David,

I think Artifactory does support this for any repo, as long as it follows one of the repo layouts in your configuration.  You can only add non-standard layouts in the Pro version (not OSS), but you can assign any layout to a Generic repo, I think.  If your current set of files doesn't match one of the existing layouts, perhaps you could move them around with a one-off script?

https://www.jfrog.com/confluence/display/RTF/Repository+Layouts

Hope that helps,
Hugh.


From: David Ward [[hidden email]]
Sent: Friday, January 22, 2016 02:25
To: [hidden email]
Subject: Re: [Artifactory-users] Snapshots for a generic repository

D:

 

I tried using a maven repository and it doesn’t know that the tarballs are snapshots so it lets you store as many as you want. I guess we could fudge a maven environment and generate the tarballs as snapshots, but that’s silly work.

 

I know I can do the versioning with a script. But, since artifactory already has a similar approach for maven/gradle/ivy, it would seem symmetrical to have a similar policy for generic repositories. Plus, we are actually deploying our artifacts from bamboo using the default artifactory plugin so we would have to reproduce that.

 

It just seems this is something that artifactory should support.

 

Thanks.

 

David

 

From: dave_p [via Artifactory] [mailto:ml-node+[hidden email]]
Sent: Thursday, January 21, 2016 7:17 PM
To: Ward, David (Proxy) <[hidden email]>
Subject: Re: Snapshots for a generic repository

 

I had a similar problem with these OVA appliances (versioned releases, not snapshots) one of our teams produces nightly - ended up “fixing” it by writing a python script that uses the artifactory API to list the contents of a repository, sort them by date, and delete the oldest ones. (We retain 7, but the idea is the same.) Then added it to crontab.

Interested in knowing if there’s a better way.

Theoretically, I suppose you could use a maven repository to store tarballs. For some reason, I’ve got a maven repo with a bunch of ISOs in it. :-D

-Dave P.

On Jan 21, 2016, at 1:49 PM, David Ward <[hidden email]> wrote:


> We currently store tarballs of our system in artifactory after each build. We
> do not use maven, gradle, etc., so we store them in a generic repository.
>
> The problem that we are having is that the repository keeps growing and
> growing because each build is a separate artifact; however, old versions of
> the build are not really useful.
>
> For maven/gradle repositories, we could configure the repository as a
> snapshot repository and limit versions to a small number.
>
> Is there some way to limit the number of artifacts in a generic repository
> in a similar manner? For example, only allow 5 artifacts (our build
> tarballs) in the repository. If you put in more than five, the oldest
> artifact will be deleted.
>
> Thanks.
>
> David
>
>
>
>
> --
> View this message in context: http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Artifactory-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751p7580753.html

To unsubscribe from Snapshots for a generic repository, click here.
NAML

CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient. If you received this in error, please do not read, distribute, or take action in reliance upon this message. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message. Act 5.6.102a.c


View this message in context: RE: Snapshots for a generic repository
Sent from the Artifactory - Users mailing list archive at Nabble.com.


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751p7580755.html

To unsubscribe from Snapshots for a generic repository, click here.
NAML

CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient. If you received this in error, please do not read, distribute, or take action in reliance upon this message. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
Reply | Threaded
Open this post in threaded view
|

Re: Snapshots for a generic repository

mdeboeck
We have some custom layouts configured, but I also did not succeed in cleaning up old artifacts through Artifactory. So I ended up scripting it through the AQL layout (https://github.com/JFrogDev/artifactory-scripts/tree/master/cleanup contains an example that you can use to start with).

We are publishing to Artifactory using Ivy, and the Artifactory layout has been setup to reflect the way we publish.
Maybe it is because our customized layouts don't use the fields [folderItegRev] and [fileItegRev] ?

To be honest, if the custom layouts do not help with auto-cleaning, I don't understand the added value of the custom layouts: it is perfectly possible to possible an artifact using a different layout than its repository layout, and it is also possible to search for artifacts in such repositories. So what else can they be used for ?

Marc


2016-01-22 16:43 GMT+01:00 David Ward [via Artifactory] <[hidden email]>:

H:

 

Thanks for the pointers.

 

I created a new layout (tarball-default) by duplicating the simple-default layout. But, it still didn’t give me any configuration like the maven layout has for Max. Unique Snapshots, etc.

 

I then created a new layout by duplicating maven-default. But, still no configuration to limit the number of snapshots, etc.

 

So, I’m pretty lost here. I just want Artifactory to give me the capabilities that it has for its other layouts – e.g., only keep the last 2 versions of an integration build – but that doesn’t seem to be possible without writing our own scripts.

 

David

 

 

From: HughG_TMVSE [via Artifactory] [mailto:[hidden email][hidden email]]
Sent: Friday, January 22, 2016 4:49 AM


To: Ward, David (Proxy) <[hidden email]>
Subject: Re: Snapshots for a generic repository

 

Hi David,

I think Artifactory does support this for any repo, as long as it follows one of the repo layouts in your configuration.  You can only add non-standard layouts in the Pro version (not OSS), but you can assign any layout to a Generic repo, I think.  If your current set of files doesn't match one of the existing layouts, perhaps you could move them around with a one-off script?

https://www.jfrog.com/confluence/display/RTF/Repository+Layouts

Hope that helps,
Hugh.


From: David Ward [[hidden email]]
Sent: Friday, January 22, 2016 02:25
To: [hidden email]
Subject: Re: [Artifactory-users] Snapshots for a generic repository

D:

 

I tried using a maven repository and it doesn’t know that the tarballs are snapshots so it lets you store as many as you want. I guess we could fudge a maven environment and generate the tarballs as snapshots, but that’s silly work.

 

I know I can do the versioning with a script. But, since artifactory already has a similar approach for maven/gradle/ivy, it would seem symmetrical to have a similar policy for generic repositories. Plus, we are actually deploying our artifacts from bamboo using the default artifactory plugin so we would have to reproduce that.

 

It just seems this is something that artifactory should support.

 

Thanks.

 

David

 

From: dave_p [via Artifactory] [mailto:[hidden email][hidden email]]
Sent: Thursday, January 21, 2016 7:17 PM
To: Ward, David (Proxy) <[hidden email]>
Subject: Re: Snapshots for a generic repository

 

I had a similar problem with these OVA appliances (versioned releases, not snapshots) one of our teams produces nightly - ended up “fixing” it by writing a python script that uses the artifactory API to list the contents of a repository, sort them by date, and delete the oldest ones. (We retain 7, but the idea is the same.) Then added it to crontab.

Interested in knowing if there’s a better way.

Theoretically, I suppose you could use a maven repository to store tarballs. For some reason, I’ve got a maven repo with a bunch of ISOs in it. :-D

-Dave P.

On Jan 21, 2016, at 1:49 PM, David Ward <[hidden email]> wrote:


> We currently store tarballs of our system in artifactory after each build. We
> do not use maven, gradle, etc., so we store them in a generic repository.
>
> The problem that we are having is that the repository keeps growing and
> growing because each build is a separate artifact; however, old versions of
> the build are not really useful.
>
> For maven/gradle repositories, we could configure the repository as a
> snapshot repository and limit versions to a small number.
>
> Is there some way to limit the number of artifacts in a generic repository
> in a similar manner? For example, only allow 5 artifacts (our build
> tarballs) in the repository. If you put in more than five, the oldest
> artifact will be deleted.
>
> Thanks.
>
> David
>
>
>
>
> --
> View this message in context: http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Artifactory-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751p7580753.html

To unsubscribe from Snapshots for a generic repository, click here.
NAML

CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient. If you received this in error, please do not read, distribute, or take action in reliance upon this message. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message. Act 5.6.102a.c


View this message in context: RE: Snapshots for a generic repository
Sent from the Artifactory - Users mailing list archive at Nabble.com.


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751p7580755.html

To unsubscribe from Snapshots for a generic repository, click here.
NAML

CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient. If you received this in error, please do not read, distribute, or take action in reliance upon this message. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.


If you reply to this email, your message will be added to the discussion below:
http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751p7580758.html
To start a new topic under Artifactory - Users, email [hidden email]
To unsubscribe from Artifactory, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: Snapshots for a generic repository

David Ward

M:

 

Thanks – I’ll give the scripting a try.

 

David

 

From: mdeboeck [via Artifactory] [mailto:ml-node+[hidden email]]
Sent: Monday, January 25, 2016 4:43 AM
To: Ward, David (Proxy) <[hidden email]>
Subject: Re: Snapshots for a generic repository

 

We have some custom layouts configured, but I also did not succeed in cleaning up old artifacts through Artifactory. So I ended up scripting it through the AQL layout (https://github.com/JFrogDev/artifactory-scripts/tree/master/cleanup contains an example that you can use to start with).

We are publishing to Artifactory using Ivy, and the Artifactory layout has been setup to reflect the way we publish.

Maybe it is because our customized layouts don't use the fields [folderItegRev] and [fileItegRev] ?

To be honest, if the custom layouts do not help with auto-cleaning, I don't understand the added value of the custom layouts: it is perfectly possible to possible an artifact using a different layout than its repository layout, and it is also possible to search for artifacts in such repositories. So what else can they be used for ?

Marc

 

 

2016-01-22 16:43 GMT+01:00 David Ward [via Artifactory] <[hidden email]>:

H:

 

Thanks for the pointers.

 

I created a new layout (tarball-default) by duplicating the simple-default layout. But, it still didn’t give me any configuration like the maven layout has for Max. Unique Snapshots, etc.

 

I then created a new layout by duplicating maven-default. But, still no configuration to limit the number of snapshots, etc.

 

So, I’m pretty lost here. I just want Artifactory to give me the capabilities that it has for its other layouts – e.g., only keep the last 2 versions of an integration build – but that doesn’t seem to be possible without writing our own scripts.

 

David

 

 

From: HughG_TMVSE [via Artifactory] [mailto:[hidden email][hidden email]]
Sent: Friday, January 22, 2016 4:49 AM


To: Ward, David (Proxy) <[hidden email]>
Subject: Re: Snapshots for a generic repository

 

Hi David,

I think Artifactory does support this for any repo, as long as it follows one of the repo layouts in your configuration.  You can only add non-standard layouts in the Pro version (not OSS), but you can assign any layout to a Generic repo, I think.  If your current set of files doesn't match one of the existing layouts, perhaps you could move them around with a one-off script?

https://www.jfrog.com/confluence/display/RTF/Repository+Layouts

Hope that helps,
Hugh.


From: David Ward [[hidden email]]
Sent: Friday, January 22, 2016 02:25
To: [hidden email]
Subject: Re: [Artifactory-users] Snapshots for a generic repository

D:

 

I tried using a maven repository and it doesn’t know that the tarballs are snapshots so it lets you store as many as you want. I guess we could fudge a maven environment and generate the tarballs as snapshots, but that’s silly work.

 

I know I can do the versioning with a script. But, since artifactory already has a similar approach for maven/gradle/ivy, it would seem symmetrical to have a similar policy for generic repositories. Plus, we are actually deploying our artifacts from bamboo using the default artifactory plugin so we would have to reproduce that.

 

It just seems this is something that artifactory should support.

 

Thanks.

 

David

 

From: dave_p [via Artifactory] [mailto:[hidden email][hidden email]]
Sent: Thursday, January 21, 2016 7:17 PM
To: Ward, David (Proxy) <[hidden email]>
Subject: Re: Snapshots for a generic repository

 

I had a similar problem with these OVA appliances (versioned releases, not snapshots) one of our teams produces nightly - ended up “fixing” it by writing a python script that uses the artifactory API to list the contents of a repository, sort them by date, and delete the oldest ones. (We retain 7, but the idea is the same.) Then added it to crontab.

Interested in knowing if there’s a better way.

Theoretically, I suppose you could use a maven repository to store tarballs. For some reason, I’ve got a maven repo with a bunch of ISOs in it. :-D

-Dave P.

On Jan 21, 2016, at 1:49 PM, David Ward <[hidden email]> wrote:


> We currently store tarballs of our system in artifactory after each build. We
> do not use maven, gradle, etc., so we store them in a generic repository.
>
> The problem that we are having is that the repository keeps growing and
> growing because each build is a separate artifact; however, old versions of
> the build are not really useful.
>
> For maven/gradle repositories, we could configure the repository as a
> snapshot repository and limit versions to a small number.
>
> Is there some way to limit the number of artifacts in a generic repository
> in a similar manner? For example, only allow 5 artifacts (our build
> tarballs) in the repository. If you put in more than five, the oldest
> artifact will be deleted.
>
> Thanks.
>
> David
>
>
>
>
> --
> View this message in context: http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Artifactory-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751p7580753.html

To unsubscribe from Snapshots for a generic repository, click here.
NAML

CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient. If you received this in error, please do not read, distribute, or take action in reliance upon this message. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message. Act 5.6.102a.c


View this message in context: RE: Snapshots for a generic repository
Sent from the Artifactory - Users mailing list archive at Nabble.com.


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751p7580755.html

To unsubscribe from Snapshots for a generic repository, click here.
NAML

CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient. If you received this in error, please do not read, distribute, or take action in reliance upon this message. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751p7580758.html

To start a new topic under Artifactory - Users, email [hidden email]
To unsubscribe from Artifactory, click here.
NAML

 

 


If you reply to this email, your message will be added to the discussion below:

http://forums.jfrog.org/Snapshots-for-a-generic-repository-tp7580751p7580760.html

To unsubscribe from Snapshots for a generic repository, click here.
NAML

CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient. If you received this in error, please do not read, distribute, or take action in reliance upon this message. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.