You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21-21Lines changed: 21 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,18 +9,18 @@ This repo includes Jenkins, Gitlab and Github Actions tests of the scripts
9
9
The tasks appear in the `rhtap` directory and are updated manually. Once updated they can be tested locally in the shell or pushed to the appropriate CI system and tested in that CI.
10
10
11
11
This includes:
12
-
1. A Jenkins shared library to be tested in Jenkins as well as Developer Hub as part of RHTAP.
12
+
1. A Jenkins shared library to be tested in Jenkins as well as Developer Hub as part of RHTAP.
13
13
2. A gitlab CI file which can be pushed to gitlab in a fork of this repo to test it
14
-
3. A github actions workflow which can be run manually in this repo or pushed to a test repo to validate. When github actions are created for some of the tasks, this will require publishing to github individual to test.
14
+
3. A github actions workflow which can be run manually in this repo or pushed to a test repo to validate. When github actions are created for some of the tasks, this will require publishing to github individual to test.
15
15
16
-
## Development Mode
16
+
## Development Mode
17
17
18
18
In development mode, the pipeline scripts can be tested using local shell scripts.
19
19
20
-
`bash build-pipeline.sh` to run a build which will create the Image, SBOM and other artifacts from your local shell.
20
+
`bash build-pipeline.sh` to run a build which will create the Image, SBOM and other artifacts from your local shell.
21
21
`bash promote-pipeline` to run a promotion script which will run the promotion flow, upload SBOM (some systems) and validate Enterprise Contract.
22
22
23
-
The local execution requires binaries to be installed in your cluster on your path. The shell scripts will print error message if any binaries are missing.
23
+
The local execution requires binaries to be installed in your cluster on your path. The shell scripts will print error message if any binaries are missing.
24
24
25
25
## RHTAP-integrated mode
26
26
@@ -56,25 +56,25 @@ Once you have a cluster ready:
56
56
Note: once you've set up your `.env` for the first time, most of the variables will be re-usable
57
57
for future deployments.
58
58
59
-
## Releasing to Templates and Jenkins Library
59
+
## Releasing to Templates and Jenkins Library
60
60
61
-
### Jenkins
61
+
### Jenkins
62
62
63
-
In order to run in RHTAP via software templates, you need to release to a fork of templates https://github.com/redhat-appstudio/tssc-sample-templates and install these into RHTAP. When validated in a fork, send a pull request to the release templates repo.
63
+
In order to run in RHTAP via software templates, you need to release to a fork of templates https://github.com/redhat-appstudio/tssc-sample-templates and install these into RHTAP. When validated in a fork, send a pull request to the release templates repo.
64
64
65
65
In order to run the Jenkinsfile you must push to the Jenkins library https://github.com/redhat-appstudio/tssc-sample-jenkins
66
-
If you want to use a fork you must update your jenkinsfile to reference your fork repository in the jenkins file.
66
+
If you want to use a fork you must update your jenkinsfile to reference your fork repository in the jenkins file.
To update forks, in preparation for sending pull requests to the official library locations, you can run ` bash hack/copy-to-tssc-templates` to update your local forked repos and then manually check and push to your branch.
74
+
To update forks, in preparation for sending pull requests to the official library locations, you can run ` bash hack/copy-to-tssc-templates` to update your local forked repos and then manually check and push to your branch.
75
75
76
76
77
-
### TODO - update to include gitlab and gihub
77
+
### TODO - update to include gitlab and gihub
78
78
79
79
80
80
## Creating a cosign signing secret
@@ -105,7 +105,7 @@ Note that the MY_IMAGES_TO_VERIFY is a workaround so that the image being verifi
105
105
Binaries
106
106
The agent machines running jenkins (or if on master, that machine will need to have binaries configured for the jenkins user running the pipelines)
107
107
108
-
These will be checked prior to allowing execution to proceed. If any binaries are missing, there will be an error message printed. Install the required binary and re-run the shell mode or the jenkins agent.
108
+
These will be checked prior to allowing execution to proceed. If any binaries are missing, there will be an error message printed. Install the required binary and re-run the shell mode or the jenkins agent.
109
109
110
110
```
111
111
ENV vars:
@@ -146,7 +146,7 @@ variables for you, which `jenkins-set-secrets` will then deploy to your Jenkins
146
146
To set the secrets, run `hack/jenkins-set-secrets`
147
147
To validate secrets are set run `hack/jenkins-get-secrets`
148
148
149
-
You can also check the credentials view in your Jenkins instance.
149
+
You can also check the credentials view in your Jenkins instance.
150
150
151
151
![alt text](creds.png"Title")
152
152
@@ -170,18 +170,18 @@ The script will perform the following
170
170
171
171
1. Reset the build and gitops repositories for each of the CI systems to a base source and application sample, these repos are typically called `tssc-dev-source-{ci-name}` and `tssc-dev-gitops-{ci-name} `. Note github Actions may have a different name due to history. The ci-test.sh script will print the names of the repos used as well as any manual steps on creating repos (gitlab)
172
172
2. Copy the CI pipelines and env setup for the ci tests into the build and gitops repos. The script can be run with RHTAP connected or not installed. If running without an RHTAP (usefull for testing build, sbom, ec) the scripts will detect that there is no cluster and will disable ACS, REKOR and TRUSTIFICATION. If you have a running cluster, this can also be accomplished with `oc logout ` for simpler testing.'
173
-
3. Kick off a build on each CI if manually required.
173
+
3. Kick off a build on each CI if manually required.
174
174
4. To get automated pull requests, run `bash hack/wait-for-gitops-update.sh` in a separate window before running the ci-test.sh. It will watch the three gitops repos for updates from build and automatically send a PR to update stage from dev. This can be used to validate a full build/promotion cycle before releasing into the tssc-sample-templates.
175
-
5. You can also run `hack/rhtap-promote --repo repo-url` to trigger a PR for an individual repo.
175
+
5. You can also run `hack/rhtap-promote --repo repo-url` to trigger a PR for an individual repo.
0 commit comments