-
Notifications
You must be signed in to change notification settings - Fork 21
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
Update instructions for on-boarding new workloads #158
base: master
Are you sure you want to change the base?
Conversation
eb7515a
to
6e9db4a
Compare
This commit: - Adds documentation around onboarding new workloads as well testing the pull requests before submitting them. - Adds Job Config History plugin to help with grabbing the xml file of the job to be converted to the jenkins job builder or yaml template.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
hulk | 6 | scale-ci | 2.9.13 | | ||
loki | 4 | scale-ci | 2.9.16 | | ||
black panther | 4 | scale-ci | 2.9.16 | | ||
black widow | 4 | scale-ci | 2.9.16 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chaitanyaenr I added a new agent today for jetpack - https://jenkins.scalelab.redhat.com/computer/antman/
### Test setup/Migrating scale-ci jobs to any Jenkins | ||
The following instructions will help you setup a jenkins test environment super quick so as to play around and test the changes locally before pushing them to production. | ||
### Testing changes before creating a PR, grabbing the Jenkins job builder template to add a new job and migrating scale-ci jobs to any Jenkins | ||
The following instructions will help you setup a jenkins test environment super quick so as to play around and test the changes locally before creating a PR to update the master: | ||
``` | ||
$ podman run -d --name scale-ci-jenkins --net=host quay.io/openshift-scale/scale-ci-jenkins:latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This image needs ansible at the least.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, add a note saying that if you have node-labels the job won't run without changing the config as there won't be any slaves with those labels.
@@ -99,30 +129,37 @@ $ git clone https://github.com/openshift-scale/scale-ci-pipeline.git | |||
$ cd scale-ci-pipeline | |||
$ # Set the variables in the scale-ci-watcher-env.sh and source it | |||
$ source scale-ci-watcher-env.sh | |||
$ # Set the jenkins user name, url and passwd in the scale-ci-watcher config file | |||
$ # Set the jenkins user name, url, passwd, github repo and branch with the changes in the scale-ci-watcher config file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth mentioning that the provided container image does not need username/password.
@@ -99,30 +129,37 @@ $ git clone https://github.com/openshift-scale/scale-ci-pipeline.git | |||
$ cd scale-ci-pipeline | |||
$ # Set the variables in the scale-ci-watcher-env.sh and source it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Specify that the path related variables need to refer to the local path of you code under development.
This commit:
the pull requests before submitting them.
of the job to be converted to the jenkins job builder or yaml template.