-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add a task to update installed plugins #56
Comments
The existing calls will update a plug in, if the state is given as "latest"
or a version pin would cause it to update. However, they would then blindly
restart the master without any sort of warning. Improving the intelligence
of that will be the real crux of this issue.
…On Tue, Mar 7, 2017 at 3:24 PM, robled ***@***.***> wrote:
Since updating plugins requires a Jenkins restart, this task would need to
be created in a way to inform the user that a restart would occur, and
implement the necessary safety measures/warnings for a production Jenkins
master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#56>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQsrnSrmFAB0ezG2tOD-eevt_y4Ikizks5rjcsKgaJpZM4MWC0T>
.
|
I wonder if updating plugins without a restart for any extended period of time has any downsides. If not, then I'd suggest a var that can be set to enable the restart (disabled by default) to protect against outages. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since updating plugins requires a Jenkins restart, this task would need to be created in a way to inform the user that a restart would occur, and implement the necessary safety measures/warnings for a production Jenkins master.
The text was updated successfully, but these errors were encountered: