core
core copied to clipboard
thoth-station
Automate update of dependencies + release of image for ps-* repos.
Is your feature request related to a problem? Please describe. I want bots to take care of all stacks and repos with ps-* stacks, so that I can focus on my project and not worry about dependencies and images.
High-level Goals
- [ ] ps-* repos are completely maintained by bots.
Describe the solution you'd like Automatic release once a new update from the bot is added.
Describe alternatives you've considered Manual trigger of the release.
Additional context
Acceptance Criteria
- [ ] new image automatically released once the PR with updates from the bots is merged.
@pacospace is this a dup of #326 ?
Not a duplicate, #326 is to make sure adviser can solve all stacks in ps images. This one is to automate the release, everytime a new update came in from Kebechet, without the need for us to go and open an issue for release.
oh, got that.
Shall we start building from HEAD commit and use the commit sha as a tag on quay? to do you want bots to do regular v-releases (and have the bot open an issue for that)?
oh, got that.
Shall we start building from HEAD commit and use the commit sha as a tag on quay? to do you want bots to do regular v-releases (and have the bot open an issue for that)?
Yes so they can maintain those repos without humans ;D
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
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.
I believe this is not done yet, so /reopen /remove-lifecycle rotten
Having said that, I believe this is related to:
- https://github.com/thoth-station/kebechet/issues/847
- https://github.com/thoth-station/kebechet/issues/991
@pacospace can you help me confirm that the request in this issue would be fulfilled by these, or if there is something else?
@codificat: Reopened this issue.
In response to this:
I believe this is not done yet, so /reopen /remove-lifecycle rotten
Having said that, I believe this is related to:
- https://github.com/thoth-station/kebechet/issues/847
- https://github.com/thoth-station/kebechet/issues/991
@pacospace can you help me confirm that the request in this issue would be fulfilled by these, or if there is something else?
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.
Also related:
- https://github.com/thoth-station/core/issues/359
/sig devsecops /triage accepted
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
