-
Notifications
You must be signed in to change notification settings - Fork 7
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
[zuul] Use the stf-crc-jobs project template #122
Conversation
This change depends on a change with an invalid configuration. |
Instead of updating the .zuul.yaml file everytime infrawatch/service-telemetry-operator adds a new job, the project-template can be updated in STO, which will propogate the change to the project and avoid leaving gaps in testing. Depends-On: infrawatch/service-telemetry-operator#514
3939d73
to
13afa4d
Compare
This change depends on a change with an invalid configuration. |
This is expected until https://review.rdoproject.org/r/c/config/+/50707 is merged and the project templates can be used |
recheck |
Looks like the two expected jobs are running! |
This change depends on a change that failed to merge. Change infrawatch/service-telemetry-operator#514 is needed. |
recheck |
The coveralls job that is failing seems to be a false failure. The file that is flagged as having lower coverage is https://github.com/infrawatch/sg-core/blob/master/plugins/handler/events/pkg/lib/source.go, which has not been modified recently. The test_source.go file was also not modified recently. |
Yea that happens sometimes. I keep looking periodically for a threshold since it's a bit fuzzy, but nothing shows up. You can pretty much just ignore it failing since it's a very small value. |
The failures are not related to this change |
Instead of updating the .zuul.yaml file everytime
infrawatch/service-telemetry-operator adds a new job, the project-template can be updated in STO, which will propogate the change to the project and avoid leaving gaps in testing.
Depends-On: infrawatch/service-telemetry-operator#514