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

Make rehearsals of hidden jobs have skip_report: true #346

Merged

Conversation

petr-muller
Copy link
Member

Rehearsals of hidden jobs are also hidden jobs, but they are "special"
by being hidden jobs on a repository that should not have hidden
jobs (openshift/release). This causes problems because the config makes
jobs on openshift/release to have URLs in GH to the public Deck/Spyglass
instance, but that instance does not have access to the underlying private
storage so it cannot show the rehearsal's logs and artifacts.

(see the ci/rehearse/openshift-priv/ci-experiment-origin/master/e2e-cmd
rehearsal on openshift/release#6536 for an example)

Additionally, whoever triggers a rehearsal of a hidden job is unlikely to
have access to the Deck instance that shows hidden jobs, so they would not
be able to access the logs even if the URL were correct.

Therefore, we make such jobs skip reporting to GH to avoid confusion

Note: "hidden" means the Deck concept of hidden jobs


Additionally, I discovered the current tests panic when they fail because diff.Object*Diff (deprecated anyway) do not handle unexported fields, so I ported the tests to cmp.Diff. Also, spotted some dead code in those tests and removed it.

/cc @openshift/openshift-team-developer-productivity-platform

The latter is deprecaded, and also unable to make a diff of the current
form of the `Presubmit` struct, which contains unexported fields. This
caused failing tests to end with a panic instead of producing a readable
diff.
Rehearsals of hidden jobs are also hidden jobs, but they are "special"
by being hidden jobs on a repository that should not have hidden
jobs (openshift/release). This causes problems because the config makes
jobs on `openshift/release` to have URLs in GH to the public Deck/Spyglass
instance, but that instance does not have access to the underlying private
storage so it cannot show the rehearsal's logs and artifacts.

Additionally, whoever triggers a rehearsal of a hidden job is unlikely to
have access to the Deck instance that shows hidden jobs, so they would not
be able to access the logs even if the URL were correct.

Therefore, we make such jobs skip reporting to GH to avoid confusion

Note: "hidden" means the Deck concept of hidden jobs
@openshift-ci-robot openshift-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 3, 2020
@petr-muller
Copy link
Member Author

/cc @openshift/openshift-team-developer-productivity-test-platform

@openshift-ci-robot openshift-ci-robot requested a review from a team January 7, 2020 22:59
@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 8, 2020
@openshift-ci-robot
Copy link
Contributor

[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

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 806103f into openshift:master Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants