You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2019. It is now read-only.
I basically added 2 tests, verify, and unit when I first created my ci-operator config. Later I removed the verify target from the ci-operator config, and re-ran docker run -it -v $(pwd)/ci-operator:/ci-operator:z registry.svc.ci.openshift.org/ci/ci-operator-prowgen:latest --from-dir /ci-operator/config/ --to-dir /ci-operator/jobs but the prow job file didn't get updated to remove the contents relating to the verify target.
The text was updated successfully, but these errors were encountered:
That was intentional because prowgen checks your already existing presubmit yaml file and allow you to have the extra job that doesn't exist to the ci-operator config.
I wouldn't call it "intentional", it's a side effect of the naive way how unknown jobs are handled. If we do not generate something, we just leave it as it is, even if we generated it earlier. There's room for improvement here - maybe we can annotate generated jobs?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I basically added 2 tests,
verify
, andunit
when I first created my ci-operator config. Later I removed theverify
target from the ci-operator config, and re-randocker run -it -v $(pwd)/ci-operator:/ci-operator:z registry.svc.ci.openshift.org/ci/ci-operator-prowgen:latest --from-dir /ci-operator/config/ --to-dir /ci-operator/jobs
but the prow job file didn't get updated to remove the contents relating to theverify
target.The text was updated successfully, but these errors were encountered: