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

CI integration for windows-machine-config-operator #7317

Merged
merged 5 commits into from
Feb 28, 2020

Conversation

aravindhp
Copy link
Contributor

@aravindhp aravindhp commented Feb 25, 2020

  • Ran "make new-repo" with the following configuration:
Welcome to the repository configuration initializer.
In order to generate a new set of configurations, some information will be necessary.

Let's start with general information about the repository...
Enter the organization for the repository: openshift
Enter the repository to initialize: windows-machine-config-operator
Enter the development branch for the repository: [default: master]

Now, let's determine how the repository builds output artifacts...
Does the repository build and promote container images?  [default: no] yes
Does the repository promote images as part of the OpenShift release?  [default: no]
Do any images build on top of the OpenShift base image?  [default: no]
Do any images build on top of the CentOS base image?  [default: no]

Now, let's configure how the repository is compiled...
What version of Go does the repository build with? [default: 1.13]
[OPTIONAL] Enter the Go import path for the repository if it uses a vanity URL (e.g. "k8s.io/my-repo"):
[OPTIONAL] What commands are used to build binaries in the repository? (e.g. "go install ./cmd/...") make build
[OPTIONAL] What commands are used to build test binaries? (e.g. "go install -race ./cmd/..." or "go test -c ./test/...")

Now, let's configure test jobs for the repository...

First, we will configure simple test scripts. Test scripts
execute unit or integration style tests by running a command
from your repository inside of a test container. For example,
a unit test may be executed by running "make test-unit" after
checking out the code under test.

Are there any test scripts to configure?  [default: no] yes
What is the name of this test (e.g. "unit")?  lint
Does this test require built binaries?  [default: no]
What commands in the repository run the test (e.g. "make test-unit")?  make lint
Are there any more test scripts to configure?  [default: no] yes
What is the name of this test (e.g. "unit")?  build
Does this test require built binaries?  [default: no]
What commands in the repository run the test (e.g. "make test-unit")?  make build
Are there any more test scripts to configure?  [default: no]

Next, we will configure end-to-end tests. An end-to-end test
executes a command from your repository against an ephemeral
OpenShift cluster. The test script will have "cluster:admin"
credentials with which it can execute no other tests will
share the cluster.

Are there any end-to-end test scripts to configure?  [default: no] yes
What is the name of this test (e.g. "e2e-operator")?  e2e-operator
Which specific cloud provider does the test require, if any?  [default: aws] aws
What commands in the repository run the test (e.g. "make test-e2e")?  make run-ci-e2e-test
Are there any more end-to-end test scripts to configure?  [default: no]
  • Add the images config option pointing to the Dockerfile in the WMCO repo
    and execute, "make jobs".
  • Add ovn CLUSTER_VARIANT to the presubmit job
  • Remove the e2e-operator from the config.
  • Remove prow-gen-controlled:true as prow-gen does not support specifying CLUSTER_VARIANT.
  • Manually add the OWNERS file
  • Add unit test to config and ran "make jobs" to generate the job.

@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 25, 2020
@aravindhp aravindhp force-pushed the wmco branch 2 times, most recently from 0584009 to 4a91a4d Compare February 27, 2020 19:48
@aravindhp
Copy link
Contributor Author

/test pj-rehearse

@aravindhp
Copy link
Contributor Author

/test pj-rehearse

1 similar comment
@aravindhp
Copy link
Contributor Author

/test pj-rehearse

@aravindhp
Copy link
Contributor Author

/retest

1 similar comment
@aravindhp
Copy link
Contributor Author

/retest

@aravindhp
Copy link
Contributor Author

/test pj-rehearse

Ran "make new-repo" with the following configuration:
```
Welcome to the repository configuration initializer.
In order to generate a new set of configurations, some information will be necessary.

Let's start with general information about the repository...
Enter the organization for the repository: openshift
Enter the repository to initialize: windows-machine-config-operator
Enter the development branch for the repository: [default: master]

Now, let's determine how the repository builds output artifacts...
Does the repository build and promote container images?  [default: no] yes
Does the repository promote images as part of the OpenShift release?  [default: no]
Do any images build on top of the OpenShift base image?  [default: no]
Do any images build on top of the CentOS base image?  [default: no]

Now, let's configure how the repository is compiled...
What version of Go does the repository build with? [default: 1.13]
[OPTIONAL] Enter the Go import path for the repository if it uses a vanity URL (e.g. "k8s.io/my-repo"):
[OPTIONAL] What commands are used to build binaries in the repository? (e.g. "go install ./cmd/...") make build
[OPTIONAL] What commands are used to build test binaries? (e.g. "go install -race ./cmd/..." or "go test -c ./test/...")

Now, let's configure test jobs for the repository...

First, we will configure simple test scripts. Test scripts
execute unit or integration style tests by running a command
from your repository inside of a test container. For example,
a unit test may be executed by running "make test-unit" after
checking out the code under test.

Are there any test scripts to configure?  [default: no] yes
What is the name of this test (e.g. "unit")?  lint
Does this test require built binaries?  [default: no]
What commands in the repository run the test (e.g. "make test-unit")?  make lint
Are there any more test scripts to configure?  [default: no] yes
What is the name of this test (e.g. "unit")?  build
Does this test require built binaries?  [default: no]
What commands in the repository run the test (e.g. "make test-unit")?  make build
Are there any more test scripts to configure?  [default: no]

Next, we will configure end-to-end tests. An end-to-end test
executes a command from your repository against an ephemeral
OpenShift cluster. The test script will have "cluster:admin"
credentials with which it can execute no other tests will
share the cluster.

Are there any end-to-end test scripts to configure?  [default: no] yes
What is the name of this test (e.g. "e2e-operator")?  e2e-operator
Which specific cloud provider does the test require, if any?  [default: aws] aws
What commands in the repository run the test (e.g. "make test-e2e")?  make run-ci-e2e-test
Are there any more end-to-end test scripts to configure?  [default: no]
```
Add the images config option pointing to the Dockerfile in the WMCO repo
and execute, "make jobs".
- Remove the e2e-operator from the config.
- Remove prow-gen-controlled:true as prow-gen does not support
  specifying CLUSTER_VARIANT.
Ran "make jobs" to generate the job.
@aravindhp
Copy link
Contributor Author

/retest

@openshift-bot
Copy link
Contributor

/bugzilla refresh

The requirements for Bugzilla bugs have changed, recalculating validity.

@openshift-ci-robot
Copy link
Contributor

@openshift-bot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

/bugzilla refresh

The requirements for Bugzilla bugs have changed, recalculating validity.

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.

@openshift-bot
Copy link
Contributor

/test all

The requirements for Bugzilla bugs have changed, recalculating validity.

@aravindhp
Copy link
Contributor Author

/retest

@aravindhp aravindhp changed the title [WIP] CI integration for windows-machine-config-operator CI integration for windows-machine-config-operator Feb 28, 2020
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 28, 2020
@aravindhp
Copy link
Contributor Author

/assign @sdodson @openshift/openshift-team-developer-productivity-test-platform

Copy link
Contributor

@sebsoto sebsoto left a comment

Choose a reason for hiding this comment

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

/lgtm

@@ -101,6 +100,8 @@ presubmits:
env:
- name: CLUSTER_TYPE
value: aws
- name: CLUSTER_VARIANT
Copy link
Contributor

Choose a reason for hiding this comment

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

Its annoying that this needs to be done manually still

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 28, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aravindhp, sebsoto, stevekuznetsov

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 28, 2020
@openshift-merge-robot openshift-merge-robot merged commit 32a4c73 into openshift:master Feb 28, 2020
@openshift-ci-robot
Copy link
Contributor

@aravindhp: Updated the following 7 configmaps:

  • ci-operator-master-configs configmap in namespace ci-stg at cluster default using the following files:
    • key openshift-windows-machine-config-operator-master.yaml using file ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-master.yaml
  • plugins configmap in namespace ci at cluster default using the following files:
    • key plugins.yaml using file core-services/prow/02_config/_plugins.yaml
  • config configmap in namespace ci at cluster default using the following files:
    • key config.yaml using file core-services/prow/02_config/_config.yaml
  • config configmap in namespace release-controller-test at cluster default using the following files:
    • key config.yaml using file core-services/prow/02_config/_config.yaml
  • job-config-master configmap in namespace ci at cluster default using the following files:
    • key openshift-windows-machine-config-operator-master-postsubmits.yaml using file ci-operator/jobs/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-master-postsubmits.yaml
    • key openshift-windows-machine-config-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-master-presubmits.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
    • key openshift-windows-machine-config-operator-master.yaml using file ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-master.yaml
  • ci-operator-master-configs configmap in namespace ci at cluster default using the following files:
    • key openshift-windows-machine-config-operator-master.yaml using file ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-master.yaml

In response to this:

  • Ran "make new-repo" with the following configuration:
Welcome to the repository configuration initializer.
In order to generate a new set of configurations, some information will be necessary.

Let's start with general information about the repository...
Enter the organization for the repository: openshift
Enter the repository to initialize: windows-machine-config-operator
Enter the development branch for the repository: [default: master]

Now, let's determine how the repository builds output artifacts...
Does the repository build and promote container images?  [default: no] yes
Does the repository promote images as part of the OpenShift release?  [default: no]
Do any images build on top of the OpenShift base image?  [default: no]
Do any images build on top of the CentOS base image?  [default: no]

Now, let's configure how the repository is compiled...
What version of Go does the repository build with? [default: 1.13]
[OPTIONAL] Enter the Go import path for the repository if it uses a vanity URL (e.g. "k8s.io/my-repo"):
[OPTIONAL] What commands are used to build binaries in the repository? (e.g. "go install ./cmd/...") make build
[OPTIONAL] What commands are used to build test binaries? (e.g. "go install -race ./cmd/..." or "go test -c ./test/...")

Now, let's configure test jobs for the repository...

First, we will configure simple test scripts. Test scripts
execute unit or integration style tests by running a command
from your repository inside of a test container. For example,
a unit test may be executed by running "make test-unit" after
checking out the code under test.

Are there any test scripts to configure?  [default: no] yes
What is the name of this test (e.g. "unit")?  lint
Does this test require built binaries?  [default: no]
What commands in the repository run the test (e.g. "make test-unit")?  make lint
Are there any more test scripts to configure?  [default: no] yes
What is the name of this test (e.g. "unit")?  build
Does this test require built binaries?  [default: no]
What commands in the repository run the test (e.g. "make test-unit")?  make build
Are there any more test scripts to configure?  [default: no]

Next, we will configure end-to-end tests. An end-to-end test
executes a command from your repository against an ephemeral
OpenShift cluster. The test script will have "cluster:admin"
credentials with which it can execute no other tests will
share the cluster.

Are there any end-to-end test scripts to configure?  [default: no] yes
What is the name of this test (e.g. "e2e-operator")?  e2e-operator
Which specific cloud provider does the test require, if any?  [default: aws] aws
What commands in the repository run the test (e.g. "make test-e2e")?  make run-ci-e2e-test
Are there any more end-to-end test scripts to configure?  [default: no]
  • Add the images config option pointing to the Dockerfile in the WMCO repo
    and execute, "make jobs".
  • Add ovn CLUSTER_VARIANT to the presubmit job
  • Remove the e2e-operator from the config.
  • Remove prow-gen-controlled:true as prow-gen does not support specifying CLUSTER_VARIANT.
  • Manually add the OWNERS file
  • Add unit test to config and ran "make jobs" to generate the job.

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.

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