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
{{ message }}
This repository was archived by the owner on Mar 21, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/add-to-repository.adoc
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,17 +23,17 @@ pipeline:
23
23
- name: build
24
24
taskRef:
25
25
kind: Task
26
-
name: ods-build-go-v0-11-1
26
+
name: ods-build-go-v0-12-0
27
27
workspaces:
28
28
- name: source
29
29
workspace: shared-workspace
30
30
----
31
31
32
-
`ods-build-go-v0-11-1` runs tests and produces a Go binary. If you use another technology, e.g. a Java project using Gradle, exchange the task with `ods-build-gradle-v0-11-1`. See the link:tasks/[tasks reference] for available tasks.
32
+
`ods-build-go-v0-12-0` runs tests and produces a Go binary. If you use another technology, e.g. a Java project using Gradle, exchange the task with `ods-build-gradle-v0-12-0`. See the link:tasks/[tasks reference] for available tasks.
33
33
34
34
=== (Optionally) Create `Dockerfile`
35
35
36
-
If you want to create a container image with the produced Go binary, you can add the `ods-package-image-v0-11-1` task to the `tasks` list, like this:
36
+
If you want to create a container image with the produced Go binary, you can add the `ods-package-image-v0-12-0` task to the `tasks` list, like this:
37
37
38
38
.ods.yaml
39
39
[source,yaml]
@@ -43,14 +43,14 @@ pipeline:
43
43
- name: build
44
44
taskRef:
45
45
kind: Task
46
-
name: ods-build-go-v0-11-1
46
+
name: ods-build-go-v0-12-0
47
47
workspaces:
48
48
- name: source
49
49
workspace: shared-workspace
50
50
- name: package
51
51
taskRef:
52
52
kind: Task
53
-
name: ods-package-image-v0-11-1
53
+
name: ods-package-image-v0-12-0
54
54
runAfter:
55
55
- build
56
56
workspaces:
@@ -72,13 +72,13 @@ EXPOSE 8080
72
72
CMD ["./app"]
73
73
----
74
74
75
-
NOTE: `ods-build-go-v0-11-1` produces a binary called `app` and places it at `docker/app` so that it can be referenced in the `Dockerfile` and copied into the image by the `ods-package-image-v0-11-1` task.
75
+
NOTE: `ods-build-go-v0-12-0` produces a binary called `app` and places it at `docker/app` so that it can be referenced in the `Dockerfile` and copied into the image by the `ods-package-image-v0-12-0` task.
76
76
77
77
NOTE: Pay attention to the `runAfter` configuration in the task list: it ensures that the tasks run sequentially and can use the outputs from the previous task(s).
78
78
79
79
=== (Optionally) Create Helm Chart
80
80
81
-
If you want to deploy the created image, you can add the `ods-deploy-helm-v0-11-1` task to the `tasks` list and configure which Kubernetes namespaces to deploy into, like this:
81
+
If you want to deploy the created image, you can add the `ods-deploy-helm-v0-12-0` task to the `tasks` list and configure which Kubernetes namespaces to deploy into, like this:
Copy file name to clipboardExpand all lines: docs/convert-quickstarter-component.adoc
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,14 +93,14 @@ pipelines:
93
93
- name: build
94
94
taskRef:
95
95
kind: Task
96
-
name: ods-build-go-v0-11-1
96
+
name: ods-build-go-v0-12-0
97
97
workspaces:
98
98
- name: source
99
99
workspace: shared-workspace
100
100
- name: package
101
101
taskRef:
102
102
kind: Task
103
-
name: ods-package-image-v0-11-1
103
+
name: ods-package-image-v0-12-0
104
104
runAfter:
105
105
- build
106
106
workspaces:
@@ -109,21 +109,21 @@ pipelines:
109
109
- name: deploy
110
110
taskRef:
111
111
kind: Task
112
-
name: ods-deploy-helm-v0-11-1
112
+
name: ods-deploy-helm-v0-12-0
113
113
runAfter:
114
114
- package
115
115
workspaces:
116
116
- name: source
117
117
workspace: shared-workspace
118
118
----
119
119
120
-
What has been done in Jenkins in `stageCheckFormat`, `stageLint`, `stageUnitTest`, `stageBuild` and `odsComponentStageScanWithSonar` is now done by the `ods-build-go-v0-11-1` task. If you have modified how the application is tested and built, or added further steps, you will need to create your own Tekton tasks reflecting those changes. See the link:authoring-tasks.adoc[authoring tasks] guide.
120
+
What has been done in Jenkins in `stageCheckFormat`, `stageLint`, `stageUnitTest`, `stageBuild` and `odsComponentStageScanWithSonar` is now done by the `ods-build-go-v0-12-0` task. If you have modified how the application is tested and built, or added further steps, you will need to create your own Tekton tasks reflecting those changes. See the link:authoring-tasks.adoc[authoring tasks] guide.
121
121
122
-
Building the container image is now done in `ods-package-image-v0-11-1` instead of in `odsComponentStageBuildOpenShiftImage`. The task continues to use the existing `docker/Dockerfile` file, which does not need to change much if at all. Consult the task reference in question for more information. In the case of Go, the link:tasks/ods-build-go.adoc[`ods-build-go` task reference] states that the resulting Go binary is named `app` and placed into the `docker` directory. Make sure that your `docker/Dockerfile` copies `app`, not e.g. `app_linux_amd64` (as is the default for an ODS 4.x based Go quickstarter).
122
+
Building the container image is now done in `ods-package-image-v0-12-0` instead of in `odsComponentStageBuildOpenShiftImage`. The task continues to use the existing `docker/Dockerfile` file, which does not need to change much if at all. Consult the task reference in question for more information. In the case of Go, the link:tasks/ods-build-go.adoc[`ods-build-go` task reference] states that the resulting Go binary is named `app` and placed into the `docker` directory. Make sure that your `docker/Dockerfile` copies `app`, not e.g. `app_linux_amd64` (as is the default for an ODS 4.x based Go quickstarter).
123
123
124
124
== Create Helm Chart
125
125
126
-
Finally, the application is deployed in `ods-deploy-helm-v0-11-1` as opposed to `odsComponentStageRolloutOpenShiftDeployment`.
126
+
Finally, the application is deployed in `ods-deploy-helm-v0-12-0` as opposed to `odsComponentStageRolloutOpenShiftDeployment`.
127
127
Let's look at this deployment piece in detail. The new Tekton task makes use of Helm to define and deploy the Kubernetes resources to use. Your existing repository might not define Kubernetes resources at all (this is the default), or they might be expressed as OpenShift templates (in a folder named `openshift`) and applied with link:https://github.com/opendevstack/tailor[Tailor]. ODS pipeline only supports Helm at the moment, and requires the Kubernetes resources (the Helm "chart") to be under version control. It is recommended to start with the link:https://github.com/opendevstack/ods-pipeline/tree/sample-helm-chart[sample chart provided in this repository]. If the existing component controlled resources via Tailor, please see the link:https://github.com/opendevstack/tailor/wiki/Migrating-from-Tailor-to-Helm#ods-quickstarter-migration[ODS Quickstarter Migration Guide] of Tailor as well.
@@ -145,4 +145,4 @@ TIP: The credentials stored in the K8s secrets will not be updated. If you need
145
145
146
146
==== Finishing the update
147
147
148
-
Once the resources in your namespace are updated, you likely have to update the `ods.yaml` files in your repository to point to the new tasks, e.g. changing `ods-build-go-v0-10-1` to `ods-build-go-v0-11-1`. Whether or not you have to update the `ods.yaml` file depends whether the task suffix (controlled by the value `taskSuffix`) has changed due to the update.
148
+
Once the resources in your namespace are updated, you likely have to update the `ods.yaml` files in your repository to point to the new tasks, e.g. changing `ods-build-go-v0-11-1` to `ods-build-go-v0-12-0`. Whether or not you have to update the `ods.yaml` file depends whether the task suffix (controlled by the value `taskSuffix`) has changed due to the update.
0 commit comments