Skip to content

Commit 6b8f51e

Browse files
author
Hasan Quadri
committed
Update app package readme with additional steps to test locally
1 parent b64869b commit 6b8f51e

File tree

1 file changed

+46
-2
lines changed

1 file changed

+46
-2
lines changed

ca/app-package/README.md

Lines changed: 46 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
Appformer package for Jenkins CI
22
================================
3-
This package deploys Jenkins and the Build Service engines.
3+
This package deploys Jenkins and the Build Service engines as PODs.
44
This will create an NFS share that will be mounted inside the PODs.
55

66
The steps provided below were based on reading this [wiki link](https://cawiki.ca.com/display/intplatform/HOWTO%3A+Get+Started+With+OSE3#HOWTO:GetStartedWithOSE3-DeployaPlatformApplicationinOSE3).
@@ -9,6 +9,51 @@ In the steps, substitute the following values:
99
- `<ose3project>` - OSE3 Project where Appformer is running. _(Example: myproject)_
1010
- `<VPC>` - the VPC where the Platform instance is running on. _(Example: slogvpc4)_
1111

12+
### Testing in personal Appformer environment
13+
You'll need to get the devops team to deploy an Appformer environment for you to use in the Openshift environment.
14+
They'll deploy it to your project.
15+
16+
#### Modify app package engine descriptors for personal testing
17+
Each engine in the app package is a docker image. For Platform deployment the
18+
package expects the images to be in the platform Openshift project. However,
19+
to deploy the package in your project, you will need to modify the engine
20+
descriptors to point to your project.
21+
22+
1. Edit `engine/jenkins/descriptor.yml` to replace this line:
23+
```
24+
docker_image: "platform/buildservice-jenkins"
25+
```
26+
with the project where Appformer is running in:
27+
```
28+
docker_image: "<ose3project>/buildservice-jenkins"
29+
```
30+
2. Edit `engine/buildservice/descriptor.yml` to replace this line:
31+
```
32+
docker_image: "platform/buildservice-buildservice"
33+
```
34+
with the project where Appformer is running in:
35+
```
36+
docker_image: "<ose3project>/buildservice-buildservice"
37+
```
38+
39+
#### Push Docker engine images to VDR
40+
Following on the previous section, regarding where the images are located, the Docker
41+
images that the app package refers to needs to be made available in the local
42+
VDR.
43+
44+
1. Build the Jenkins Docker image and push the image
45+
```
46+
cd docker-workflow-plugin/demo
47+
docker build -t ose3vdr1.services.<VPC>.caplatformdev.com:5000/<ose3project>/buildservice-jenkins:1.0.0.0 -f Dockerfile_release .
48+
docker push ose3vdr1.services.<VPC>.caplatformdev.com:5000/<ose3project>/buildservice-jenkins:1.0.0.0
49+
```
50+
2. Build the Build Service Docker image (from the build-service git repo)
51+
```
52+
cd build-service
53+
docker build -t ose3vdr1.services.<VPC>.caplatformdev.com:5000/<ose3project>/buildservice-buildservice:1.0.0.0 .
54+
docker push ose3vdr1.services.<VPC>.caplatformdev.com:5000/<ose3project>/buildservice-buildservice:1.0.0.0
55+
```
56+
1257
#### Create Appformer app
1358
1. Create appformer jenkins app:
1459
```
@@ -29,7 +74,6 @@ Example:
2974
```
3075
git clone http://appformer-myproject.app.services.slogvpc4.caplatformdev.com/system/git/jenkins.git
3176
```
32-
3377
2. Place root of app package directory structure at the root of the cloned git repo and push changes:
3478
```
3579
git add -A

0 commit comments

Comments
 (0)