Hello there 👋 I have a question regarding plugin builds on the Jenkins infrastructure. Are we limited to using only official Maven repositories?
I'm working on a plugin that compiles successfully on my local machine. However, the build fails on the infrastructure because one of its dependencies (which is quite exotic) cannot be found. The Maven repository containing this dependency is actually a GitHub repository. Is using this type of dependency download forbidden? I would understand if it is, due to potential security concerns. You can see the build failure here: https://ci.jenkins.io/job/Plugins/job/open-stf-plugin/job/PR-27/6/console Could you please clarify the policy on using non-standard Maven repositories in plugin builds? If it's not allowed, could you suggest any alternatives or workarounds? Thank you for your time and assistance. Best regards, Bruno Verachten -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CACtV%3DdfvC8TcyPp_xpPqhS0ih%3DNvkH_ajV-ywD7cBDLjPR-9bQ%40mail.gmail.com.
