New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Try to support installation of specific versions of plugins #104
Comments
would this support installing from http? we use some internally developed plugins that are not hosted in the update center (they wouldn't be useful to anybody) our current bash/groovy configuration grabs the .hpi files and installs them directly |
@steven-foster the goal here is to improve plugins and dependency management, so cherry-picking binaries from outside update center without metadata is out of scope imho. |
@ndeloof @steven-foster |
Note that this will make this issue impossible to resolve, as update sites only advertise the latest release (compatible with the core version, more or less). (Unless you start consuming |
Thanks for the Juseppe pointer, didn't come across this when looking at self-hosting plugins |
@daniel-beck plugin management need indeed to be updated in many places. |
@steven-foster in case you don't get your plugin installation use-case to work, please make another issue for future work of maybe supporting your situation with self-made non-public plugins. But it is out of scope on this issues. |
Related to the above (hosting your own update sites), lets make sure this can still work in air-gapped environments! |
@ndeloof I added 'Size' to help with planning and prediction |
We could rely on |
the sole option I have in mind is to assume update centers all use the |
@ewelinawilkosz I've been working on my own version of it here : https://github.com/ndeloof/configuration-as-code-plugin/tree/plugins |
see #175 |
@ndeloof if I remember right current installation is not the final one, and we need to monitor jenkins-infra/update-center2#197 |
yes indeed, I think we can close this one and create a follow-up once we have an alternative to offer |
@ndeloof Since the dependant issues seem solved, are there plans to continue this work? |
No, this feature was removed as of v1.8 |
For now we only support latest - let's try recommendation by @ndeloof in this comment #43 (comment)
The text was updated successfully, but these errors were encountered: