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

R. Tyler Croy tyler at monkeypox.org
Mon Mar 19 12:45:35 UTC 2018


(replies inline)

On Mon, 19 Mar 2018, Olblak wrote:

> Won't it means more overhead?
> Why not reusing what we currently have?
> My feeling is that we'll introduce duplication.
> Or do you plan to use something else than Artifactory.
> 
> I just want to be sure that we don't introduce new services because we
> don't want to fix what we currently have


This would be another repository in the same Artifactory instance (we have a
bunch of different repositories in that instance). The reason for not using the
same repository currently used for released plugins in Artifactory is that we
have excessive index times already on that one repository.

olblak, I'm guessing your questions with the assuming I would be deploying a
new Artifactory instance, which is not what I am suggesting. See this document
if I'm too unclear:
    https://www.jfrog.com/confluence/display/RTF/Configuring+Repositories





> On Sun, Mar 18, 2018, at 3:41 PM, Baptiste Mathus wrote:
> > +1, makes sense. Anyway, I guess though "tightly managed and garbage
> > collected" /might/ not be strictly required *right now*, this is most
> > desirable over time, so why not start now.> 
> > 2018-03-16 16:44 GMT+01:00 Oleg Nenashev <o.v.nenashev at gmail.com>:
> >> Works for me. I also see some components being polluted by snaphots.
> >> A separate repo would help>> 
> >> On Mar 16, 2018 16:41, "R. Tyler Croy" <tyler at monkeypox.org> wrote:
> >>> 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
> >>>  ------------------------------------------------------
> >>> 
> >>> _______________________________________________
> >>>  Jenkins-infra mailing list
> >>> Jenkins-infra at lists.jenkins-ci.org
> >>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
> >>> 
> >> 
> >> _______________________________________________
> >>  Jenkins-infra mailing list
> >> Jenkins-infra at lists.jenkins-ci.org
> >> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
> >> 
> > _________________________________________________
> > Jenkins-infra mailing list
> > Jenkins-infra at lists.jenkins-ci.org
> > http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
> 

> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra


- 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/20180319/020beba6/attachment.asc>


More information about the Jenkins-infra mailing list