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-1322): embargo-check internal task uses git resolver #782

Open
wants to merge 1 commit into
base: development
Choose a base branch
from

Conversation

johnbieren
Copy link
Collaborator

This commit updates the embargo-check internal pipeline to call its one task via git resolver. The pipeline itself still uses a cluster resolver, which will be changed in a separate commit.

Describe your changes

Relevant Jira

Checklist before requesting a review

  • I have marked as draft or added do not merge label if there's a dependency PR
    • If you want reviews on your draft PR, you can add reviewers or add the release-service-maintainers handle if you are unsure who to tag
  • My commit message includes Signed-off-by: My name <email>
  • I have bumped the task/pipeline version string and updated changelog in the relevant README
  • I read CONTRIBUTING.MD and commit formatting

@johnbieren
Copy link
Collaborator Author

/retest
weird failure to retrieve pipeline errors

@johnbieren
Copy link
Collaborator Author

/retest

@johnbieren
Copy link
Collaborator Author

/retest
unable to connect to cluster

mmalina
mmalina previously approved these changes Jan 24, 2025
Copy link
Contributor

@mmalina mmalina left a comment

Choose a reason for hiding this comment

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

Two small details, but otherwise it looks good.

This commit updates the embargo-check internal pipeline to call its one
task via git resolver. The pipeline itself still uses a cluster
resolver, which will be changed in a separate commit.

Signed-off-by: Johnny Bieren <[email protected]>
@openshift-ci openshift-ci bot added the lgtm label Jan 24, 2025
@konflux-ci-qe-bot
Copy link

@johnbieren: The following test has Failed, say /retest to rerun failed tests.

PipelineRun Name Status Rerun command Build Log Test Log
konflux-e2e-tests-catalog-4msmf Failed /retest View Pipeline Log View Test Logs

Inspecting Test Artifacts

To inspect your test artifacts, follow these steps:

  1. Install ORAS (see the ORAS installation guide).
  2. Download artifacts with the following commands:
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/release-service-catalog:konflux-e2e-tests-catalog-4msmf

Test results analysis

🚨 Error occurred while running the E2E tests, list of failed Spec(s):

➡️ [failed] [It] [release-pipelines-suite [HACBS-1571]test-release-e2e-push-image-to-pyxis] Post-release verification verifies a release PipelineRun is started and succeeded in managed namespace [release-pipelines, pushPyxis]

Click to view logs

Error when waiting for a release pipelinerun for release push-pyxis-rfsy-tenant/snapshot-sample-ylau-6qdln to finish
Expected success, but got an error:
    <*errors.errorString | 0xc0014947c0>: 
    Pipelinerun 'managed-j6xzh' didn't succeed
    
    {
        s: "Pipelinerun 'managed-j6xzh' didn't succeed\n",
    }

➡️ [failed] [It] [release-pipelines-suite e2e tests for rh-advisories pipeline] Rh-advisories happy path Post-release verification verifies the advs release pipelinerun is running and succeeds [release-pipelines, rh-advisories, rhAdvisories]

Click to view logs

PipelineRun managed-zbvgf failed
Expected
    : Pipelinerun 'managed-zbvgf' didn't succeed\n
to equal
    : 

➡️ [failed] [It] [release-pipelines-suite e2e tests for multi arch with rh-advisories pipeline] Multi arch test happy path Post-release verification verifies the multiarch release pipelinerun is running and succeeds [release-pipelines, multiarch-advisories, multiArchAdvisories]

Click to view logs

PipelineRun managed-fpnh2 failed
Expected
    : Pipelinerun 'managed-fpnh2' didn't succeed\n
to equal
    : 

➡️ [failed] [It] [release-pipelines-suite FBC e2e-tests] with FBC happy path Post-release verification verifies the fbc release pipelinerun is running and succeeds [release-pipelines, fbc-tests, fbcHappyPath]

Click to view logs

PipelineRun managed-wxpkc failed
Expected
    : Pipelinerun 'managed-wxpkc' didn't succeed\n
to equal
    : 

➡️ [failed] [It] [release-pipelines-suite e2e tests for rh-push-to-redhat-io pipeline] Rh-push-to-redhat-io happy path Post-release verification verifies the rhio release pipelinerun is running and succeeds [release-pipelines, rh-push-to-redhat-io, PushToRedhatIO]

Click to view logs

PipelineRun managed-vw8k7 failed
Expected
    : Pipelinerun 'managed-vw8k7' didn't succeed\n
to equal
    : 

➡️ [failed] [It] [release-pipelines-suite e2e tests for rhtap-service-push pipeline] Rhtap-service-push happy path Post-release verification verifies the rhtap release pipelinerun is running and succeeds [release-pipelines, rhtap-service-push, RhtapServicePush]

Click to view logs

PipelineRun managed-2h56v failed
Expected
    : Pipelinerun 'managed-2h56v' didn't succeed\n
to equal
    : 

➡️ [failed] [It] [release-pipelines-suite Push to external registry] Post-release verification verifies that Release PipelineRun should eventually succeed [release-pipelines, push-to-external-registry]

Click to view logs

Error when waiting for a release pipelinerun for release ex-registry-tuzy-tenant/snapshot-sample-fysb-v2rm8 to finish
Expected success, but got an error:
    <*errors.errorString | 0xc0018efb30>: 
    Pipelinerun 'managed-rxmvc' didn't succeed
    
    {
        s: "Pipelinerun 'managed-rxmvc' didn't succeed\n",
    }

@johnbieren
Copy link
Collaborator Author

/retest

@johnbieren johnbieren enabled auto-merge (squash) January 24, 2025 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants