-
Notifications
You must be signed in to change notification settings - Fork 6
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
[FEATURE] using the cached values is configurable #17
Comments
Hi there, and thank you for the feature request! Regarless, I'll be a bit busy in the next couple of weeks, so unsure when I have time to work on this. If you yourself or anyone passing by wants to start earlier you are welcome to do so (just post here that u are working on it). |
Thanks for your quick reply. I'm not familiar with java code and jenkins plugins development. so I just modified the code and built it locally. But I can take a try when I have time. |
Hey, Noevi. Feel free to give it a try if you can. |
Small update: /edit: If you still want to try, pls feel free to! I for sure don't want to block you exploring Jenkins/Java 😉 |
It isn't an urgent requirement. Thanks very much. |
So, caching is live with the 1.2.x release. I hope it works as you had envisioned it and per default it will force web requests. |
Is your feature request related to a problem? Please describe.
Actually, I need the latest rest api response in every build job. Not a cached value.
I think it's better to provide an option.
Describe the solution you'd like
A checkbox in configure page.
Describe alternatives you've considered
If the checkbox is checked, use the cached values, or retrieve values every time.
Additional context
None
The text was updated successfully, but these errors were encountered: