User story (meta) #2281
Auto deploy pending modification when autoDeployOnModification come back to true
| Status: | New | Start date: | 2012-02-14 | |
|---|---|---|---|---|
| Priority: | 4 | Due date: | ||
| Assignee: |  Nicolas CHARLES |
% Done: | 0% |
|
| Category: | Webapp - CFEngine integration | |||
| Target version: | 2.6.1 | |||
| Needs translating: | No |
Description
If the rudder.autoDeployOnModification=false, we can accumulate modification never deployed on server.
If we then stop the server, change the property to "true", and start back the server, the pending modification are not automatically deployed.
That's not really a problem as a simple "start deployment" or any modification solve the situation, but:
- it would be nice that the deployment was done at startup, since the user requested automatic deployment (and in that case, some are still pending
- or at least, the deployment widget should display the fact that there is pending deployment, event if the server is configured to auto-deploy.
History
#1
Updated by François ARMAND 11 months ago
- Target version changed from Ideas (2.5 specific) to 48
This is not mandatory for 2.5, so it's rescheduled to 2.6.
#2
Updated by Jonathan CLARKE 10 months ago
- Target version changed from 48 to Ideas (2.5 specific)
#3
Updated by Nicolas CHARLES 4 months ago
- Target version changed from Ideas (2.5 specific) to 2.6.0~beta1
- 2 set to 0
This is not mandatory for 2.5, so it's rescheduled to 2.6.
#4
Updated by Nicolas PERRON about 1 month ago
- Target version changed from 2.6.0~beta1 to 2.6.0~rc1
#5
Updated by Matthieu CERDA 26 days ago
- Target version changed from 2.6.0~rc1 to 2.6.0
#6
Updated by Jonathan CLARKE 22 days ago
- Target version changed from 2.6.0 to 2.6.1