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

feat(RELEASE-983): add e2e tests for push-binaries-to-dev-portal #1262

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jinqi7
Copy link
Contributor

@jinqi7 jinqi7 commented Jul 15, 2024

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Issue ticket number and link

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
  • I have updated labels (if needed)

Copy link

openshift-ci bot commented Jul 15, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@jinqi7 jinqi7 force-pushed the push-binaries-to-dev-portal branch from 3a73a5d to 02e76cf Compare July 15, 2024 10:36
Copy link

openshift-ci bot commented Jul 15, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from jinqi7. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

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

@jinqi7 jinqi7 force-pushed the push-binaries-to-dev-portal branch from 02e76cf to 5841896 Compare July 15, 2024 11:38
tests/release/const.go Fixed Show fixed Hide fixed
@jinqi7 jinqi7 force-pushed the push-binaries-to-dev-portal branch 3 times, most recently from 842de49 to c370fb2 Compare July 16, 2024 03:32
tests/release/const.go Fixed Show fixed Hide fixed
@jinqi7
Copy link
Contributor Author

jinqi7 commented Jul 16, 2024

/test all

@jinqi7
Copy link
Contributor Author

jinqi7 commented Jul 22, 2024

/test redhat-appstudio-e2e

@jinqi7
Copy link
Contributor Author

jinqi7 commented Jul 29, 2024

/test redhat-appstudio-e2e

tests/release/const.go Fixed Show fixed Hide fixed
tests/release/const.go Fixed Show fixed Hide fixed
@jinqi7 jinqi7 marked this pull request as ready for review July 30, 2024 01:13
@openshift-ci openshift-ci bot requested review from johnbieren and mmalina July 30, 2024 01:14
@jinqi7 jinqi7 requested a review from a team July 30, 2024 01:14
@jinqi7 jinqi7 force-pushed the push-binaries-to-dev-portal branch from 90c109f to 2630658 Compare July 30, 2024 01:16
pkg/constants/constants.go Show resolved Hide resolved
tests/release/const.go Outdated Show resolved Hide resolved
tests/release/pipelines/push_binaries_to_dev_portal.go Outdated Show resolved Hide resolved
tests/release/pipelines/push_binaries_to_dev_portal.go Outdated Show resolved Hide resolved
Expect(err).NotTo(HaveOccurred())
})

It("verifies release CR completed and set succeeded.", func() {
Copy link
Contributor

Choose a reason for hiding this comment

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

We should probably talk about if there is another check we can do for success in addition to the release CR succeeding (like we do in many other tests)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I asked developers if more checks are needed and didn't get a suggestion. Maybe add some checks about the message in the log of the tasks?

Copy link
Contributor

Choose a reason for hiding this comment

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

If it is a slack thread, can you send it to me? It isn't always possible, but I think it is much better when we have some test specific check after the release pipelineRun to ensure what we expected to happen actually happened and we didn't just hit some exit 0 edge case early in the run

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's in this thread. Anyway, I added some check about the output from some important action in the "publish-to-cgw" task and will add similar check from "push-to-cdn" when can it run successfully.

Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, that link doesn't work for me

@jinqi7 jinqi7 force-pushed the push-binaries-to-dev-portal branch 3 times, most recently from 01a9bfd to ba45a4a Compare July 31, 2024 08:36
tests/release/const.go Dismissed Show dismissed Hide dismissed
tests/release/const.go Dismissed Show dismissed Hide dismissed
@johnbieren
Copy link
Contributor

@jinqi7 based on discussions on slack today, maybe this should be moved to draft until we figure out the push-to-cdn thing

@jinqi7 jinqi7 marked this pull request as draft August 1, 2024 05:22
@jinqi7 jinqi7 force-pushed the push-binaries-to-dev-portal branch from ba45a4a to 8e0832f Compare August 2, 2024 08:58
@jinqi7
Copy link
Contributor Author

jinqi7 commented Aug 2, 2024

/test redhat-appstudio-e2e

magefiles/magefile.go Outdated Show resolved Hide resolved
Expect(err).NotTo(HaveOccurred())
})

It("verifies release CR completed and set succeeded.", func() {
Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, that link doesn't work for me

@jinqi7 jinqi7 force-pushed the push-binaries-to-dev-portal branch from 8e0832f to 052135e Compare August 7, 2024 10:52
@jinqi7
Copy link
Contributor Author

jinqi7 commented Aug 12, 2024

/retest

@jinqi7 jinqi7 force-pushed the push-binaries-to-dev-portal branch from 052135e to 6f568a4 Compare August 12, 2024 12:37
@jinqi7
Copy link
Contributor Author

jinqi7 commented Aug 12, 2024

/retest

1 similar comment
@jinqi7
Copy link
Contributor Author

jinqi7 commented Aug 12, 2024

/retest

@konflux-ci-qe-bot
Copy link

@jinqi7: The following test finished. In case the test failed, say /retest to rerun all failed tests:

PipelineRun name Revision PipelineRun Status Command
konflux-e2e-86sv9-2d4l8 6f568a4 Failed /retest

To inspect your test artifacts, ensure you have installed ORAS on your local machine. To inspect all test artifacts, execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-86sv9-2d4l8

For instructions on how to install ORAS, please refer to the ORAS installation guide.

@konflux-ci-qe-bot
Copy link

@jinqi7: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
konflux-e2e-86sv9-2d4l8 /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-86sv9-2d4l8

For instructions on how to install ORAS, please refer to the ORAS installation guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants