You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will be the list of improvements to implement before we can make this feature mandatory for every chart owner and make an announcement company-wide.
Improvements
Implement auto-trigger at chart-bump.
When a new PR is merged on the chart upstream repository, this must trigger a new auto chart-bump at the charts repository.
This must be done with @pjbgf approval, the strategy that will be implemented must not generate security risks.
This must be documented in the Wiki before the announcement.
After the company-wide statement the Chart owners will be responsible for implementing their part of the integration in their upstream repositories respectively.
When a new chart-bump occurs, the last release.yaml entry for that chart must be removed before a new one is added.
The feature currently is hard-coded only for dev-v2.10 branch, expand the functionality for the newer lines that might come (e.g., dev-v2.11; dev-v2.12....)
The text was updated successfully, but these errors were encountered:
The auto-chart-bump is executed manually using the charts-build-scripts.
This will be the list of improvements to implement before we can make this feature mandatory for every chart owner and make an announcement company-wide.
Improvements
When a new PR is merged on the chart upstream repository, this must trigger a new auto chart-bump at the charts repository.
This must be done with @pjbgf approval, the strategy that will be implemented must not generate security risks.
This must be documented in the Wiki before the announcement.
After the company-wide statement the Chart owners will be responsible for implementing their part of the integration in their upstream repositories respectively.
When a new chart-bump occurs, the last
release.yaml
entry for that chart must be removed before a new one is added.The feature currently is hard-coded only for
dev-v2.10
branch, expand the functionality for the newer lines that might come (e.g.,dev-v2.11
;dev-v2.12
....)The text was updated successfully, but these errors were encountered: