Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Force a new buildid on staging changes #7116

Open
coolo opened this issue Mar 5, 2019 · 0 comments
Open

Feature request: Force a new buildid on staging changes #7116

coolo opened this issue Mar 5, 2019 · 0 comments
Labels
Backend Things regarding the OBS backend Feature status-api Things related to the status feature

Comments

@coolo
Copy link
Member

coolo commented Mar 5, 2019

We have one hole in the staging workflow: if unselecting packages that were unresolvable, the scheduler checks the new state and finds that nothing changed (outside of the build status) and doesn't trigger a new buildid in the repository and no event either.

This means we have no way to re-trigger a check job. So we need some way from the outside to force a new buildid on changes we do (the staging workflow could do this itself, but we need this for all projects following the status api).

@coolo coolo added Feature Backend Things regarding the OBS backend labels Mar 5, 2019
@hennevogel hennevogel added the status-api Things related to the status feature label Mar 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend Things regarding the OBS backend Feature status-api Things related to the status feature
Projects
None yet
Development

No branches or pull requests

2 participants