Cicd documentation layout
Download 6.25 Mb.
|
| Parameters are accessible and executes after requires script approval from an Administrator.
It creates parameterized build property in Jenkins job configuration. By the above stage Jenkins job Configuration path looks like this: The below Environment block contains global environment variables which works inside of the stage and outside as a null. Variables for the parametrized execution The below stage script executes Azure region. Here using and executing IF condition to check branch name and update version in that branch. Build code using maven by Clone updates from the version control system, in our case here “GitHub”. Test the code analysis by using login credentials of SonarQube with maven test command Deploy created and build artifact(Jar, war) in artifactory repository using Nexus Build, tag and push docker image to container registry Deploy image on Dev environment in Aks by using Helm charts which are configured with Dev environment server details. In the same way write script for map and configure Test and Prod environment details in in Jenkinsfile as next stages. Below is the Post build action stage, which sends e-mail notification when build fails. By below script we can get Slack notifications of Build status(success, failed, aborted, stopped) It maps to the SlackNotifier.groovy file which contains slack script. Slacknotifier.groovy file contains below script Note: The first word on the shebang line has to be a binary executable. If it happens that your "groovy" program is a shell script, you have to use the #!/usr/bin/env groovy form Download 6.25 Mb. Share with your friends:
|