Skip to content
This repository was archived by the owner on Jun 14, 2019. It is now read-only.

Conversation

@droslean
Copy link
Member

@droslean droslean commented May 8, 2019

No description provided.

@droslean
Copy link
Member Author

droslean commented May 8, 2019

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label May 8, 2019
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 8, 2019
Copy link
Member

@petr-muller petr-muller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not I guess :D
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 9, 2019
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: droslean, petr-muller

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [droslean,petr-muller]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 2f7d5b5 into openshift:master May 9, 2019
@droslean droslean deleted the gcp branch May 9, 2019 12:49
@droslean
Copy link
Member Author

droslean commented May 9, 2019

why not I guess :D

@petr-muller related PR that the template was changed but we didn't trigger the rehearse:
openshift/release#3691

I triggered it manually. ci/rehearse/openshift/jenkins/openshift-3.11/e2e-gcp

@stevekuznetsov
Copy link
Contributor

Don't we have constants for these somewhere? Ew. We need to re-think what is going on with these constants. Is it better when we move all templates to Go code?

@bbguimaraes
Copy link
Contributor

I mentioned it in the original review: we didn't have these constants in ci-operator-prowgen to avoid this. The ones we use to generate jobs are in ci-operator, but even there we don't have a hard-coded list that has to be manually updated.

At this point in the execution in rehearse, we have all jobs from the master and candidate branches loaded in memory, why not derive the list from them?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants