[Jenkins-infra] Considering a new Maven repo for pre-release/incremental builds of plugins/core

[R. Tyler Croy]

This past week I was in San Jose chatting with Carlos Sanchez (csanchez) about
some tooling we will need to support the eventual shipping of master-branch
builds (etc) within Jenkins Essentials
(https://github.com/jenkinsci/jep/tree/master/jep/300)

Rather than attempting to make sense thousands of SNAPSHOT versions in a
repository, I suggested to Carlos that we create a new, tightly managed and
garbage collected, Maven repository specifically for this purpose in
Artifactory.

This would mean we'd have a repository *just* for these pre-release builds
(e.g. some-plugin-2.3.0-abdc3e.jar). My thinking is that the repository should
be garbage collecting/deleting artifacts after 30 days, and be completely
separate from the existing repositories to avoid negatively impacting the
quality of service for the existing Update Center procesess.

Before I write this all down into an IEP,  and do a necessary dive into
Artifactory documentation, I wanted to get some thoughts from others.


Cheers
- R. Tyler Croy

------------------------------------------------------
     Code: <https://github.com/rtyler>
  Chatter: <https://twitter.com/agentdero>
     xmpp: rtyler at jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20180316/a4d13bf9/attachment.asc>