On Thu, Aug 16, 2018 at 1:45 PM Oleg Nenashev <[email protected]> wrote: > If somebody uses official Jenkins Docker image with plugins.txt, the plugins > will fail to install when you rebuild the image after the change gets > deployed.
I am OK with that. If they really want it, they can get it from Artifactory. I am not even sure this is really true—IIUC blacklisting a plugin just means it does not appear in `update-center.actual.json`, but the `http://updates.jenkins.io/download/plugins/$name/$version/$name.hpi` link should still work, right? And that is all you should be relying on from JCasC. If some Docker build process relies on UC JSON, it is already broken because it is not actually locking down anything, and you could get a different image every time you build. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0a1QpjOmZyxUNjNdddvGTAiiDst5hJkUHPJSnROzovCw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
