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

🌱 Add dev-env-integration tests to prow #678

Merged

Conversation

peppi-lotta
Copy link
Member

Added some tests to be run from PRs in BMO, CAPM3, metal-dev-env, project-infra and, IPAM. Also changed some values to work with Prow.

@metal3-io-bot metal3-io-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 26, 2024
Copy link
Member

@tuminoid tuminoid left a comment

Choose a reason for hiding this comment

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

/approve

@metal3-io-bot metal3-io-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 28, 2024
Copy link
Member

@Sunnatillo Sunnatillo left a comment

Choose a reason for hiding this comment

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

We should also add checkout logic for PR tests like this.

    if [[ -n "${PR_ID:-}" ]]; then
        git fetch origin "pull/${PR_ID}/head:${UPDATED_BRANCH}-branch" || true
    fi

Lets discuss it with @mboukhalfa.

UPDATED_BRANCH = "${ghprbActualCommit}"
REPO_ORG = "${env.REPO_OWNER}"
REPO_NAME = "${env.REPO_NAME}"
REPO_BRANCH = "${env.PULL_BASE_REF}"
Copy link
Member

@Sunnatillo Sunnatillo Mar 28, 2024

Choose a reason for hiding this comment

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

This varibale needed to run for PR tests. Please add it here and jjb PR as well
PR_ID = "${env.PULL_NUMBER}"

@@ -12,6 +12,8 @@ CI_DIR="$(dirname "$(readlink -f "${0}")")"
export IMAGE_OS="${IMAGE_OS:-ubuntu}"
export REPO_ORG="${REPO_ORG:-metal3-io}"
export REPO_NAME="${REPO_NAME:-metal3-dev-env}"
export REPO_BRANCH="${REPO_BRANCH:-main}"
export PR_ID="${PR_ID:-0}"
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
export PR_ID="${PR_ID:-0}"
export PR_ID="${PR_ID:-}"

@@ -1334,6 +1400,39 @@ presubmits:
agent: jenkins
always_run: false
optional: true
# name: {job_prefix}-{image_os}-dev-env-integration-test-{capm3_target_branch}
Copy link
Member

Choose a reason for hiding this comment

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

same here, lets not add tests for community repo as well

@@ -1843,6 +1975,39 @@ presubmits:
agent: jenkins
always_run: false
optional: true
# name: {job_prefix}-{image_os}-dev-env-integration-test-{capm3_target_branch}
Copy link
Member

Choose a reason for hiding this comment

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

Lets not add tests for metal3-io/metal3-docs repo and

Copy link
Member Author

@peppi-lotta peppi-lotta Apr 4, 2024

Choose a reason for hiding this comment

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

I think the preview cuts the code in a poorly informative way. The test are actually under metal3-io/baremetal-operater, metal3-io/cluster-api-provider-metal3, metal3-io/meta3-dev-env, metal3-io/project-infra and metal3-io/ip-address-manager.

I checked that these are the projects where integration tests are run. Are these all correct and/or am I missing some still?

Copy link
Member

Choose a reason for hiding this comment

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

thanks

@metal3-io-bot metal3-io-bot added the needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. label Apr 3, 2024
@peppi-lotta peppi-lotta force-pushed the peppi/dev-env-integration-tests-to-prow branch from ed0e92e to 9299ed2 Compare April 8, 2024 09:06
@metal3-io-bot metal3-io-bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed needs-rebase Indicates that a PR cannot be merged because it has merge conflicts with HEAD. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Apr 8, 2024
@peppi-lotta peppi-lotta force-pushed the peppi/dev-env-integration-tests-to-prow branch from 9299ed2 to 66cd96f Compare April 8, 2024 09:20
@metal3-io-bot metal3-io-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Apr 8, 2024
@peppi-lotta peppi-lotta force-pushed the peppi/dev-env-integration-tests-to-prow branch from 66cd96f to 7b97d14 Compare April 8, 2024 09:26
@metal3-io-bot metal3-io-bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 8, 2024
Copy link
Member

@Sunnatillo Sunnatillo left a comment

Choose a reason for hiding this comment

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

/lgtm
/hold
lets wait tojjb PR merge and we can test it here

@metal3-io-bot metal3-io-bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Apr 8, 2024
Copy link
Member

@smoshiur1237 smoshiur1237 left a comment

Choose a reason for hiding this comment

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

lgtm

@metal3-io-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smoshiur1237, tuminoid

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:

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

Copy link
Member

Choose a reason for hiding this comment

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

In case we run the test on PR open on metal3-io org from nordix branch:
in line 52 when we clone the repo https://github.com/${REPO_ORG}/${REPO_NAME}.git this should clone the metal3-io repo how do we merge the nordix branch changes that we want to test

Copy link
Member

Choose a reason for hiding this comment

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

any suggestions?

Copy link
Member

Choose a reason for hiding this comment

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

refspec is added to solve the issue

@Sunnatillo
Copy link
Member

/test dev-env-integration-test-ubuntu-main

@metal3-io-bot
Copy link
Collaborator

@Sunnatillo: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test check-prow-config
  • /test markdownlint
  • /test metal3-centos-e2e-integration-test-main
  • /test metal3-ubuntu-e2e-integration-test-main
  • /test shellcheck

The following commands are available to trigger optional jobs:

  • /test metal3-centos-e2e-basic-test-main
  • /test metal3-centos-e2e-basic-test-release-1-6
  • /test metal3-centos-e2e-feature-test-main
  • /test metal3-centos-e2e-feature-test-release-1-4
  • /test metal3-centos-e2e-feature-test-release-1-5
  • /test metal3-centos-e2e-feature-test-release-1-6
  • /test metal3-centos-e2e-integration-test-release-1-4
  • /test metal3-centos-e2e-integration-test-release-1-5
  • /test metal3-centos-e2e-integration-test-release-1-6
  • /test metal3-e2e-1-26-1-27-upgrade-test-main
  • /test metal3-e2e-1-26-1-27-upgrade-test-release-1-4
  • /test metal3-e2e-1-26-1-27-upgrade-test-release-1-5
  • /test metal3-e2e-1-26-1-27-upgrade-test-release-1-6
  • /test metal3-e2e-1-27-1-28-upgrade-test-main
  • /test metal3-e2e-1-27-1-28-upgrade-test-release-1-4
  • /test metal3-e2e-1-27-1-28-upgrade-test-release-1-5
  • /test metal3-e2e-1-27-1-28-upgrade-test-release-1-6
  • /test metal3-e2e-1-28-1-29-upgrade-test-main
  • /test metal3-e2e-1-28-1-29-upgrade-test-release-1-4
  • /test metal3-e2e-1-28-1-29-upgrade-test-release-1-5
  • /test metal3-e2e-1-28-1-29-upgrade-test-release-1-6
  • /test metal3-e2e-clusterctl-upgrade-test-main
  • /test metal3-e2e-clusterctl-upgrade-test-release-0-5
  • /test metal3-e2e-clusterctl-upgrade-test-release-1-3
  • /test metal3-e2e-clusterctl-upgrade-test-release-1-4
  • /test metal3-e2e-clusterctl-upgrade-test-release-1-5
  • /test metal3-e2e-clusterctl-upgrade-test-release-1-6
  • /test metal3-keep-e2e-1-26-1-27-upgrade-test-main
  • /test metal3-keep-e2e-1-26-1-27-upgrade-test-release-1-4
  • /test metal3-keep-e2e-1-26-1-27-upgrade-test-release-1-5
  • /test metal3-keep-e2e-1-26-1-27-upgrade-test-release-1-6
  • /test metal3-keep-e2e-1-27-1-28-upgrade-test-main
  • /test metal3-keep-e2e-1-27-1-28-upgrade-test-release-1-4
  • /test metal3-keep-e2e-1-27-1-28-upgrade-test-release-1-5
  • /test metal3-keep-e2e-1-27-1-28-upgrade-test-release-1-6
  • /test metal3-keep-e2e-1-28-1-29-upgrade-test-main
  • /test metal3-keep-e2e-1-28-1-29-upgrade-test-release-1-4
  • /test metal3-keep-e2e-1-28-1-29-upgrade-test-release-1-5
  • /test metal3-keep-e2e-1-28-1-29-upgrade-test-release-1-6
  • /test metal3-keep-e2e-clusterctl-upgrade-test-main
  • /test metal3-keep-e2e-clusterctl-upgrade-test-release-0-5
  • /test metal3-keep-e2e-clusterctl-upgrade-test-release-1-3
  • /test metal3-keep-e2e-clusterctl-upgrade-test-release-1-4
  • /test metal3-keep-e2e-clusterctl-upgrade-test-release-1-5
  • /test metal3-keep-e2e-clusterctl-upgrade-test-release-1-6
  • /test metal3-ubuntu-e2e-basic-test-main
  • /test metal3-ubuntu-e2e-basic-test-release-1-6
  • /test metal3-ubuntu-e2e-feature-test-main
  • /test metal3-ubuntu-e2e-feature-test-release-1-4
  • /test metal3-ubuntu-e2e-feature-test-release-1-5
  • /test metal3-ubuntu-e2e-feature-test-release-1-6
  • /test metal3-ubuntu-e2e-integration-test-release-1-4
  • /test metal3-ubuntu-e2e-integration-test-release-1-5
  • /test metal3-ubuntu-e2e-integration-test-release-1-6

Use /test all to run the following jobs that were automatically triggered:

  • check-prow-config
  • shellcheck

In response to this:

/test dev-env-integration-test-ubuntu-main

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@peppi-lotta peppi-lotta force-pushed the peppi/dev-env-integration-tests-to-prow branch from 7b97d14 to cd95990 Compare April 18, 2024 10:58
@metal3-io-bot metal3-io-bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 18, 2024
Copy link
Member

@Sunnatillo Sunnatillo left a comment

Choose a reason for hiding this comment

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

/lgtm

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Apr 18, 2024
@Sunnatillo
Copy link
Member

/override test-ubuntu-integration-main

@metal3-io-bot
Copy link
Collaborator

@Sunnatillo: Sunnatillo unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file.

In response to this:

/override test-ubuntu-integration-main

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Sunnatillo
Copy link
Member

I will unhold this PR since it is not possible to test new test before merging this PR, and this test needed to tests new cloud.
Issues will be tackled in a followup PR if any.

@Sunnatillo
Copy link
Member

/unhold

@metal3-io-bot metal3-io-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 18, 2024
@tuminoid
Copy link
Member

/override test-ubuntu-integration-main

@metal3-io-bot
Copy link
Collaborator

@tuminoid: Overrode contexts on behalf of tuminoid: test-ubuntu-integration-main

In response to this:

/override test-ubuntu-integration-main

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@metal3-io-bot metal3-io-bot merged commit 8e6d943 into metal3-io:main Apr 18, 2024
6 checks passed
@metal3-io-bot
Copy link
Collaborator

@peppi-lotta: Updated the config configmap in namespace prow at cluster default using the following files:

  • key config.yaml using file prow/manifests/overlays/metal3/config.yaml

In response to this:

Added some tests to be run from PRs in BMO, CAPM3, metal-dev-env, project-infra and, IPAM. Also changed some values to work with Prow.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Sunnatillo Sunnatillo deleted the peppi/dev-env-integration-tests-to-prow branch April 18, 2024 11:18
@Sunnatillo
Copy link
Member

Sunnatillo commented Apr 18, 2024

part of #705

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/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants