- Run the build,
- Run tests
- Publish build artifacts in artifactory
- Deploying the build artifacts in different environments including QA, UAT and production.
- Configure Inbound Rule on Jenkins Server on AWS EC2: One needs to add the inbound rule on Jenkins box on AWS EC2 for following IP: 104.192.143.192/28. This is required to allow requests coming from BitBucket to reach to Jenkins server on AWS EC2. This is BitBucket cloud IP outbound address (for hooks like POST) when inbound IP address for BitBucket is 104.192.143.1. The IP (104.192.143.1) can be figued out by pinging bitbucket.org. The outbound IP address can be found from this page: https://confluence.atlassian.com/bitbucket/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall-343343385.html
- Configure Webhook in BitBucket: One needs to add following URL while creating WebHook in BitBucket: http://jenkins_server_uri/bitbucket-hook/.
- Configure SCM in Jenkins Project: Next step is to configure Git as Source code management tool within Jenkins Project by clicking on Configure link on project’s dashboard. Following is a sample of input parameter:
- Repository_URL: https://<bitbucket_user>@bitbucket.org/<bitbucket_user>/<bitbucket_project_name>.git
- Credentials: Create a credential by providing bitbucket username and password
- Setup Build Triggers in Jenkins Project: Finally, one would require to setup build triggers for the Jenkins project by clicking on Configure link on project’s dashboard. Check the option “Build when a change is pushed to BitBucket”
- One-way ANOVA test: Concepts, Formula & Examples - January 8, 2023
- Linear Regression Explained with Real Life Example - January 8, 2023
- Data Governance Goals Explained with Examples - January 7, 2023
Leave a Reply