ci-operator
ci-operator copied to clipboard
openshift
Pod teardown may take longer than 5 mins (default ci-operator timeout). This commit would ensure the same timeout is applied to the teardown container - and then applied to the...
As we move templates into the ci-operator, we need a way to stage the changes for sets of jobs and move gradually. When a user provides --template on the command...
This came in with ad5a4e335b (#288), but the lack of `oc adm release new` logs is making it hard to debug [broken ImageStream retrieval][1]. I don't understand the bulk of...
Because while two seconds may be sufficient teardown time for unit tests and such, it's too short for e2e teardown (where cluster logs should be collected, cluster resources need to...
Not ready to merge, but will be straightforward. Once we do this, we would change prowgen to use the same form as upgrade, then regen all the jobs.
Ou test jobs are depending on multiple targets to be completed. In example: ``` name: pull-ci-openshift-openshift-azure-master-e2e-upgrade-v1.2 rerun_command: /test e2e-upgrade-v1.2 spec: containers: - args: - --artifact-dir=$(ARTIFACTS) - --give-pr-author-access-to-namespace=true - --target=[images] -...
We have use cases where we want to build images with container image tags corresponding to git tags. Something similar as `openshift-ansible` used to do where we have `release-vx` branch,...
If a build fails with: ``` status: message: 'Pod The node was low on resource: [DiskPressure]. ' phase: Failed reason: Evicted startTime: 2019-02-19T02:02:50Z ``` the build can be restarted by...
Today the ci-operator namespace caching is reusing the same installer image on multiple test re-runs. If it happens that the e2e coverage on the installer does not catch a bug...
I want to have `build_root`.`project_image` based on an imagestream in api.ci but I am not able to replace `FROM` in that Dockerfile. More concretely I want to extend the root...
