If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 09/May/11 11:21 PM
Updated: 12/Sep/11 04:50 PM
|
|
Component/s: |
None
|
Affects Version/s: |
3.1.38
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
I would like to be able send notifications when a build is recommended and would like an audit trail of who recommended the build. While I realize this could be implemented with promotions, that would result in excessive disk space usage since that would mean promoting all the artifacts.
We currently promote our builds into multiple environments. For instance, after a build is recommended, it is promoted to the QA environment. From there it can be promoted to UAT and then Production. These promotions trigger deployment activities in their configurations.
At each step, a build must be recommended before it can be promoted. This would mean 8 configurations to manage instead of four and the promotion chain would be harder to read on the dashboard. A much simpler implementation would to be to allow notification and auditing on the recommendations.
An even better thing would to be to allow you to define multiple "recommendations" the way you define promotions or notifications. This would allow different groups to make their recommendations. You could have a Dev recommendation and a QA recommendation, for instance.
|
Description
|
I would like to be able send notifications when a build is recommended and would like an audit trail of who recommended the build. While I realize this could be implemented with promotions, that would result in excessive disk space usage since that would mean promoting all the artifacts.
We currently promote our builds into multiple environments. For instance, after a build is recommended, it is promoted to the QA environment. From there it can be promoted to UAT and then Production. These promotions trigger deployment activities in their configurations.
At each step, a build must be recommended before it can be promoted. This would mean 8 configurations to manage instead of four and the promotion chain would be harder to read on the dashboard. A much simpler implementation would to be to allow notification and auditing on the recommendations.
An even better thing would to be to allow you to define multiple "recommendations" the way you define promotions or notifications. This would allow different groups to make their recommendations. You could have a Dev recommendation and a QA recommendation, for instance. |
Show » |
No changes have yet been made on this issue.
|
|