Pipeline created for testing the CD in D4Science

continuous-deployment jenkins-pipeline

Go to file

Roberto Cirillo 7f786fbbe7 add check on release components		2023-06-14 14:59:34 +02:00
images	Delete 'images/FlowChartgCubeDeployer.png'	2022-10-13 17:35:13 +02:00
.gitignore	add gitignore	2022-04-29 16:13:39 +02:00
.project	fix println sintax	2022-09-09 11:48:07 +02:00
Jenkinsfile	add check on release components	2023-06-14 14:59:34 +02:00
LICENSE.md	add LICENSE; fix deploy exitcode	2022-05-10 11:57:09 +02:00
README.md	add Environment variable section to README.md	2022-10-17 10:36:27 +02:00

README.md

Pipeline-gCubeDeployer

Jenkins Pipeline script to manage one or more gCube components deployment

Requirements

Jenkins ver. 2.164.2 or newer
Pipeline plugin
Pipeline: Maven
Pipeline: Basic Steps
Email Extension (to send emails with attachments)
Jenkins agent(s) configured with Ansible ver. 2.9.27 or newer
One or more Jenkins agents labeled as 'ansible'

Expected usage

ContinuousDeployment(CD): configured as post step build on jenkinsjob
Scheduled by system: In this case all the pending deployments (CD) will be managed by a temporized trigger
Manually from Jenkins GUI

Expected environment variables

The variables below must be specified as environment variables on the agent where the deployments will be executed:

IS_SCHEDULED (True | False): if true all the deployment requests will be performed periodically as specified by cron
ENVIRONMENT: ( DEV | PREPROD | PROD) Indicates the target environment where will be deployed all the artifacts
DEPLOY_CATEGORY: (Related to release build) one or more Component group on yaml file where search the components to deploy
CD: (Continuous Deployment: True | False) if True the remote deploy will be performed

References

Wiki doc

Flow Chart

License

This project is licensed under the EUPL V.1.1 License.