build from main
Closed this issue · 5 comments
Is your feature request related to a problem? Please describe.
For a project in early development, it would be very handy to build container images on each push to master. Having a high frequency of tags being created and deployed after each PR is merged seems to be an un-productive overload
Describe the solution you'd like
- trigger a build-deploy on push to main branch
- cancel any existing build-deploy of an older commit
Describe alternatives you've considered
Build/Deploy from PR, with a subsequent tag-release after PR merged @durandom and rational why this is not that good?
Additional context
simply fully building on each push to main might overload the cluster...
/assign @Gregory-Pereira
/assign @harshad16
/priority critical-urgent
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
Development on this feature was halted almost immediately as the Thoth-Station project was moved to hiatus. This issue will be closed, and may be re-opened when development resumes.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@sesheta: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.