Open harshad16 opened 3 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
/lifecycle frozen
Is your feature request related to a problem? Please describe. As some components depend upon the release of another component, it would be convenient if aicoe-ci can help with this process. With a post-trigger kind of a flow in the pipeline, which enables aicoe-ci to trigger a release in another repo when a configured repo/component is successfully released.
Describe the solution you'd like Have another task which creates the new release issue or creates a new tag in another defined repository (
B
), when the tag-release-run for the configured repo(A
) is completed successfully. This would start another tag-release pipeline for another component/repoB
, enabling it to utilize the needs based on release of component (A
)Describe alternatives you've considered use the sync-pipeline and hope it releases the components in the right manner :crossed_fingers:
Additional context https://github.com/thoth-station/thamos/pull/599#issuecomment-725255208