philsttr commented on pull request #15: URL: https://github.com/apache/maven-deploy-plugin/pull/15#issuecomment-750633631
We have one shared artifactory instance to which all artifacts are published. All CI servers use the same `settings.xml` file, which causes artifacts to publish to the same repositories on the shared artifactory instance. The [example settings.xml](https://github.com/apache/maven-deploy-plugin/files/5731992/settings.xml.txt) file shows that artifacts are published to one of three repositories on the shared artifactory instance (either `maven-releases`, `maven-snapshots`, or `maven-combined`) We prefer to centrally manage the distribution settings on our CI servers via `settings.xml` files rather than poms. We do this mainly because we have few CI servers (less than 5), and many poms (thousands). If/when we need to change these settings, it's a trivial task to update the CI servers. By comparison, to update all the poms would be a monumental task of distributed effort across many dev teams and release cycles. It's just not a scalable solution. Note that this isn't just a theoretical exercise. We have had to update these settings several times over the past few years due to changes to our artifactory infrastructure. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
