Actions
User story #2151
closed
Separate the deployment trigger in automatic and manual trigger, and based on a parameter, skip automatic deployment
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
It's the first step of tckets #2145 : being able to know if the deployment request is manual or automatic, and be able to conditionnalmy skip the automatic request
Updated by Nicolas CHARLES almost 13 years ago
- Status changed from 2 to Pending technical review
- % Done changed from 0 to 100
Applied in changeset 024623e77d507da13d49eb2fe588b1bb84e10d82.
Updated by Nicolas CHARLES almost 13 years ago
We now have the configuration propoerty rudder.autoDeployOnModification that would define if automatic changes will trigger a deployment or not
Updated by François ARMAND almost 13 years ago
- Status changed from Pending technical review to 10
The technical review is ok, even if it seems to have a lot of code duplication. See #2237
Updated by Jonathan CLARKE almost 13 years ago
- Category changed from Architecture - Code maintenance to Web - Config management
Updated by Jonathan CLARKE almost 13 years ago
- Status changed from 10 to Released
Actions