R11/release11-tools-mocked-services
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated README.md and Jenkinsfile.

Browse Source
This commit is contained in:
Artur Kolecki
2023-01-12 14:42:12 +01:00
parent 0d4974b0ea
commit 13995a0269
3 changed files with 2 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
README.md
View File

@@ -1,8 +1,6 @@
# R11-MockedServices
Mockup service for middleware testing.
[comment]: <> ([![Build Status]&#40;https://travis-ci.com/Szakalakamaka/Klaus.svg?token=Tt3QbF7q4wiFNnCGkuew&branch=master&#41;]&#40;https://travis-ci.com/Szakalakamaka/Klaus&#41;)
Available scripts:
### Running the application on a local machine
@@ -47,47 +45,4 @@ Display elements from the list.
Display list length.
###### SMEMBERS key
Display elements from hashSet.
Logs can be found in lists with names logstash_yyyy-mm-dd.
### Deployment and building with docker and jenkins
For creating docker context (feature available from docker version 19.03) run the command
#### docker context create
as shown by examples below.
```
docker context create DEV \
--description "context for DEV environment" \
--docker "host=ssh://jenkins@s5000xvn:22"
```
```
docker context create PROD \
--description "connection to PROD environment" \
--docker "host=ssh://jenkins@server361209.nazwa.pl:22"
```
```
docker context create PROD \
--description "context for PROD environment" \
--docker "host=ssh://jenkins@server361209:22"
```
However it is highly adviseable to deploy service via Jenkins tool at jenkins.zipper.release11.com, where contexts have been already configured.
#### docker-compose up -d --build
Builds and launches Redis service and the application. Performs unit testing on the code and run the applicationon on localhost.
#### docker-compose --context DEV up --build -d
The same as above, but the application will be deployed on the server defined via docker context as DEV.
#### docker-compose --context PROD up --build -d
The same as above, but the application will be deployed on the server defined via docker context as PROD.
The application can be started on a local machine without environment support.
Once a docker image repository will be availabe, the proper deployment order should be under control by docker-compose script
which should check if the applications are present and if not deploy stable images of Spring Cloud applications from
docker image repo.
Logs can be found in lists with names logstash_yyyy-mm-dd.