Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: buckminster-plugin
-
Labels:None
-
Similar Issues:
Description
When using the "Install automatically", an install is performed from the repositories as it stands right there and then. Subsequent updates to the repository will not be picked up automatically. I think that's fine. I would however like a way to force an update. It could be as simple as just removing whatever is there first and then reinstall from scratch using the same config.
I do understand the need of that, but it raises a few issues depending on how and when this is triggered:
First Option:
This is a setting in the 'Manage Hudson' page as part of the Buckminster Installation configuration (a checkbox 'update automatically' or so). In this case the tool gets deleted and re-installed every time a build runs. This sounds a bit heavy to me but could be considered
Second Option:
this setting is part of a build job (update before execution)
That however is problematic. The managment of tool installations are a job of an admin whereas the job configuration is the responsibility of the job owner. The job should probably not be allowed to delete/alter the configuration given by the hudson admin (since the effects are global).
None of these I really like to be honest. It would be better to have the ability to actually update (or at least check for updates) instead of deleting and installing again. Is there a way (planned at least) to update buckminster, or is there a way for the director application to perform an update?
If not, would it be possible to check for updates to see if it makes sense to erase the existing installation and provision a new one?
That would match best with the workflows in hudson, since that way the first option could be used (make it part of the hudson configuration if the tool should be updated) while avoiding excessive network traffic.
The other installers (that download things) work in a similar way. When the tool is requested they check if it is already present. If so, they check if the download archive has been updated since the tool was installed. If so, they download the newer version and replace the old tool.