Re: Moving to Attic
That’s the move, IMO. That said, there are a fair amount of legacy deployments still kicking around. For reference, every time a security patch is released somebody pings our docker repo within a few days. So folks are using it and watching for releases. Providing the community with some examples of how to migrate to other options (say Reposilite) would be responsible. I’ve been meaning to do that myself for a few months and just haven’t found the time. On Sun, Nov 19, 2023 at 6:26 PM Olivier Lamy wrote: > Hi, > I can only see a little (almost none) activity with the project now. > So, it's time to call for an Attic move. > > Please let me know me what do you think about this? > Is there any volunteers who would like to help? > Please note there is still possibility to continue the project out of > Apache (some github forks) but this cannot be called anymore Apache > Archva. > > Cheers, > Olivier >
Re: Interested in a Docker Image & Kubernetes Chart?
Martin, Sounds good! I've got to pickup another project, but as soon as I have some time I'll pickup the Archiva source and take a look at where the docker image would fit. To be honest, I probably should have just done that to begin with. There are a few minor things I've been wanting to change/fix in there for years, I've just been avoiding the effort of getting familiar with the project source :-). If I just bite the bullet get familiar with the source, I can send over a few different pull requests. Best, Terence On Sat, Oct 20, 2018 at 12:13 AM Martin wrote: > Hi Terence, > > thank you for help. > As you already know, resources are very limited in this project. So, I > have to focus on the things that are manageable. > Code contribution is very appreciated, so if you have any changes you like > to get into the project, feel free to create pull > requests. If you like, you can even add the complete docker/kubernetes > part as pull request. > If you have any questions, don't hesitate to ask. > > Regards > > Martin > > > Am Samstag, 20. Oktober 2018, 01:30:41 CEST schrieb Terence Kent: > > Hey Martin, > > > > Feel free to add a link to our image and chart on the Archiva webpage. > > Also, I threw together a v2-snapshot > > <https://github.com/xetus-oss/docker-archiva/tree/v2-snapshot> > branch/tag > > of the image that is built using the most recent 2.2.4 snapshot. All of > our > > image tests pass using the current 2.2.4-SNAPSHOT build, as you would > > expect. > > > > Looking ahead, whenever you dust off this project to finish out 2.2.4 or > > jump to version 3, I'd really like to see a docker image brought into the > > project directly. Maintaining the image code separately from the project > > isn't the greatest idea and since you already have a docker image for > > testing, I'm sure it's something you've considered. If we're available > the > > next time there's some focus on this project, we'll see if we can help > out > > with that part. We've learned several lessons about running Archiva in a > > container over the past few years and we'd love to make some small > changes > > in the source project to make life easier :-). > > > > Oh, and it'd sure be nice to have an official Kubernetes helm chart once > > there is an offical docker image. I'm confident that a lot more people > > would use Archiva if was available there. > > > > Best, > > Terence > > > > On Fri, Oct 19, 2018 at 12:31 PM Martin wrote: > > > > > Hi Terence, > > > > > > thank you for the information. Great work and great to hear, that you > > > decided to keep archiva, despite the > > > slow development. > > > I would like to add the link to our archiva web page if you don't mind. > > > We are using docker images for our integration tests on the jenkins > > > server, but without kubernetes, maybe I > > > can find some configuration on your project that may be useful for > these. > > > > > > Our current snapshot version for the stable 2.2 release branch > > > (2.2.4-SNAPSHOT) contains some fixes and > > > there are not very much changes compared to the 2.2.3 version, so I > would > > > consider it as stable. > > > If you like, you can use a current snapshot version in your docker > image > > > or provide an option for using it. > > > The zip files can be found at: > > > > > > > https://archiva-repository.apache.org/archiva/repository/snapshots/org/apache/archiva/archiva-jetty/2.2.4-SNAPSHOT/ > > > But it's still a snapshot version so, if there is development going > on, it > > > may be broken every now and then, so it may be not a > > > good idea, if the file is downloaded dynamically during container > > > start/build. > > > > > > Regards > > > > > > Martin > > > > > > Am Freitag, 19. Oktober 2018, 02:08:52 CEST schrieb Terence Kent: > > > > Hello, > > > > > > > > In early 2015, we made our Archiva docker image public. It's had a > small > > > > following on github/dockerhub and we field questions on it from time > to > > > > time. As best we can tell, it's the de-facto docker image for > Archiva. > > > > > > > > We recently moved to Kubernetes and were faced with the decision of > > > > dropping the archiva image and moving to another repository manager, > or > > > > re-upping and modernizing the image. We chose to re-up and modernize > the > > > > image and we now have a "vers
Re: Interested in a Docker Image & Kubernetes Chart?
Hey Martin, Feel free to add a link to our image and chart on the Archiva webpage. Also, I threw together a v2-snapshot <https://github.com/xetus-oss/docker-archiva/tree/v2-snapshot> branch/tag of the image that is built using the most recent 2.2.4 snapshot. All of our image tests pass using the current 2.2.4-SNAPSHOT build, as you would expect. Looking ahead, whenever you dust off this project to finish out 2.2.4 or jump to version 3, I'd really like to see a docker image brought into the project directly. Maintaining the image code separately from the project isn't the greatest idea and since you already have a docker image for testing, I'm sure it's something you've considered. If we're available the next time there's some focus on this project, we'll see if we can help out with that part. We've learned several lessons about running Archiva in a container over the past few years and we'd love to make some small changes in the source project to make life easier :-). Oh, and it'd sure be nice to have an official Kubernetes helm chart once there is an offical docker image. I'm confident that a lot more people would use Archiva if was available there. Best, Terence On Fri, Oct 19, 2018 at 12:31 PM Martin wrote: > Hi Terence, > > thank you for the information. Great work and great to hear, that you > decided to keep archiva, despite the > slow development. > I would like to add the link to our archiva web page if you don't mind. > We are using docker images for our integration tests on the jenkins > server, but without kubernetes, maybe I > can find some configuration on your project that may be useful for these. > > Our current snapshot version for the stable 2.2 release branch > (2.2.4-SNAPSHOT) contains some fixes and > there are not very much changes compared to the 2.2.3 version, so I would > consider it as stable. > If you like, you can use a current snapshot version in your docker image > or provide an option for using it. > The zip files can be found at: > > https://archiva-repository.apache.org/archiva/repository/snapshots/org/apache/archiva/archiva-jetty/2.2.4-SNAPSHOT/ > But it's still a snapshot version so, if there is development going on, it > may be broken every now and then, so it may be not a > good idea, if the file is downloaded dynamically during container > start/build. > > Regards > > Martin > > Am Freitag, 19. Oktober 2018, 02:08:52 CEST schrieb Terence Kent: > > Hello, > > > > In early 2015, we made our Archiva docker image public. It's had a small > > following on github/dockerhub and we field questions on it from time to > > time. As best we can tell, it's the de-facto docker image for Archiva. > > > > We recently moved to Kubernetes and were faced with the decision of > > dropping the archiva image and moving to another repository manager, or > > re-upping and modernizing the image. We chose to re-up and modernize the > > image and we now have a "version 2" image with an companion helm chart to > > make it easy to run in Kubernetes. > > > > I wanted to reach out to see if you had any interest in making our image > > your official one and pulling it the Archiva source. I think it's > > reasonable to assume new Archiva deployments are likely to be > > containerized, and Kubernetes is the most popular container orchestration > > platform. If our small image and chart can save you time, we'd be quite > > happy hand it over. > > > > Here's the project links for reference: > > > > - https://github.com/xetus-oss/docker-archiva > > - https://github.com/xetus-oss/helm-charts/tree/master/xetusoss-archiva > > > > Let me know, > > Terence > > > > >
Re: deleting old snapshots
Stefaan, Matthew, I hate "works for me responses", so apologies in advance. However, we are seeing artifacts automatically removed according to our repository retention settings in our deployment and I wanted to share possibly-relevant information. We've been using Archiva version 2.2.3 in a docker container for over a year now and haven't had any retention-related problems. Here are the parts of our configuration that may be relevant. 1. We have dedicated "snapshots" and "releases" repositories. Only snapshots are allowed in the "snapshots" repository, and only "releases" in the releases repository. 2. In each repository we have retention policies, and each repository is configured to be scanned. 3. The "repository-purge" consumer is enabled. Also, FWIW, I'm pretty sure the code that applies the retention policy is in the "repository-purge" consumer, and the out-most class for the feature is found here: https://github.com/apache/archiva/blob/9351c66bc89c65357ba72bb84982951919cbc0c4/archiva-modules/archiva-base/archiva-consumers/archiva-core-consumers/src/main/java/org/apache/archiva/consumers/core/repository/RepositoryPurgeConsumer.java Best, Terence On Fri, Oct 19, 2018 at 7:59 AM Matthew Broadhead wrote: > > https://github.com/apache/archiva/blob/9351c66bc89c65357ba72bb84982951919cbc0c4/archiva-modules/archiva-scheduler/archiva-scheduler-repository/src/main/java/org/apache/archiva/scheduler/repository/ArchivaRepositoryScanningTaskExecutor.java#L181 > > seems that it hasn't been implemented? > > On 19/10/2018 15:39, Matthew Broadhead wrote: > > yes i have activated the "repository-purge" consumer under Repository > > scanning -> Consumers. maybe i also need to activate the > > "validate-checksums" consumer as that is the only one not enabled > > > > in my snapshot repository i have the following values: > > Cron Expression 0 0,30 * * * ? > > Days Older 30 > > Retention Count 2 > > Delete Released Snapshots is checked > > > > i was going to upgrade to 2.2.3 but if yours is not working either > > then there is not much point > > > > i wonder if there is any way to trigger it from the command line? > > > > On 19/10/2018 13:52, Stefaan Dutry wrote: > >> According to my understanding it should be through the > >> repository-purge consumer. (This is located under Administration > > >> repository scanning > Consumers) > >> > >> Then on the repository configuration itself there are settings like > >> "Delete Released Snapshots" and "retention count" and "days older" > >> > >> Unfortunately the automatic purge isn't happening on our systems either. > >> (our version is 2.2.3) > >> > >> see: > >> http://archiva.apache.org/docs/2.2.0/adminguide/repositories.html > >> * delete released snapshots > >> * repository purge by days older > >> * repository purge by retention count > >> http://archiva.apache.org/docs/2.2.0/adminguide/consumers.html > >> * repository-purge > >> > >> But this is what's specified in the link you provided > >> > >> Regards, > >> Stefaan Dutry > >> Op vr 19 okt. 2018 om 13:37 schreef Jay Vyas : > >>> Hey Matt: some of us are definetly here. Archiva saved me when I > >>> couldn’t pay for nexus so, I’d definetly say there are a few others > >>> in that boat. Ufortubately nobody has responded yet. Next step if > >>> necessary would be filing a JIrA issue on the Apache organization > >>> for archiva if nobody is able to help on the thread. > >>> > On Oct 19, 2018, at 4:51 AM, Matthew Broadhead > wrote: > > sorry to chase but is anyone still monitoring this list? are we > supposed to move to sonatype nexus oss? i thought apache created > maven? > > > On 08/10/2018 20:00, Matthew Broadhead wrote: > > i am using 2.2.0 and i have looked through all the settings but i > > don't understand how to automatically delete old snapshots. > > > > i followed this > > > https://stackoverflow.com/questions/12315461/how-to-configure-maven-or-apache-archiva-that-it-keeps-only-n-builds-of-an-snaps > > but it didn't work > > > >
Interested in a Docker Image & Kubernetes Chart?
Hello, In early 2015, we made our Archiva docker image public. It's had a small following on github/dockerhub and we field questions on it from time to time. As best we can tell, it's the de-facto docker image for Archiva. We recently moved to Kubernetes and were faced with the decision of dropping the archiva image and moving to another repository manager, or re-upping and modernizing the image. We chose to re-up and modernize the image and we now have a "version 2" image with an companion helm chart to make it easy to run in Kubernetes. I wanted to reach out to see if you had any interest in making our image your official one and pulling it the Archiva source. I think it's reasonable to assume new Archiva deployments are likely to be containerized, and Kubernetes is the most popular container orchestration platform. If our small image and chart can save you time, we'd be quite happy hand it over. Here's the project links for reference: - https://github.com/xetus-oss/docker-archiva - https://github.com/xetus-oss/helm-charts/tree/master/xetusoss-archiva Let me know, Terence
