An introduction to Atlassian Bitbucket Pipelines
Download as PPTX, PDF1 like1,401 views
This document provides an overview of using Bitbucket Pipelines to build, test, and deploy projects from Bitbucket repositories. It discusses how Bitbucket Pipelines uses Docker containers to run build plans, benefits like faster feedback and reusable containers. It also covers enabling Pipelines for a repository, configuring the bitbucket-pipelines.yml file, and adding tests to a sample build plan by exporting Postman tests and adding a package.json file to run the tests during the build.
An introduction to Atlassian Bitbucket Pipelines
- 1. Using Docker to improve your workflow An overview of Bitbucket Pipelines Twitter: @dkcwd
- 2. Reminder about this session The slides will be made available after the session and you are more than welcome to share them if you find them useful. We have people attending from all manner of different backgrounds with different levels of experience and you’re welcome to ask questions and share knowledge after the session. Let’s get started….
- 3. An overview of Bitbucket Pipelines
- 4. Build, test and deploy from Bitbucket Bitbucket Pipelines uses Docker containers to run build plans Benefits: - Potential for faster feedback - Sensible default containers - Can use your private containers - Easy to set environment vars
- 5. Enabling Pipelines for your repository In the Settings area, you need to enable Pipelines… Next, you need to configure your bitbucket-pipelines.yml
- 6. Configuring bitbucket-pipelines.yml Choose a template to use with your build plan…
- 7. Previewing the template Move on to the next step when you’re ready…
- 8. Previewing the template Make a change if you want to then commit to create the file…
- 9. Previewing the template An opportunity to update the message…
- 10. Previewing the template The first build begins… And fails…
- 11. An email notification is sent about the failure…
- 12. The reason for failure is clear…
- 13. Ok, so let’s add some tests….
- 14. Building on a basic example Let’s build on that basic example by adding some tests to run using Pipelines For an example I’ll reuse a simple API test collection which I previously created with Postman when experimenting with serverless-graphql I’ll export from Postman and commit: - the request collection file, including pre-request scripts and tests - an environment file which “should” mean the tests pass when they are run
- 15. Building on that basic example Additionally I’ll need to do a few more things so the tests can run I’ll create a package.json file defining newman (The CLI test runner for Postman) as a dependency so it will be installed during the build process I’ll update: - the package.json file so tests can be run using npm to call newman - the bitbucket-pipelines.yml file to run the relevant commands
- 18. Let’s deliberately break it Yay it’s broken! o/
- 19. And fix it again
- 20. Need to create your own image? Check out this link: https://answers.atlassian.com/questions/39140980/how-do-i- create-a-docker-image-for-bitbucket- pipelines?_ga=1.125432457.263526773.1473156356
- 21. Need to test with a database? Check out this link: https://confluence.atlassian.com/bitbucket/test-with-databases- 856697462.html
- 22. Need to use environment variables? Check out this link: https://confluence.atlassian.com/bitbucket/environment-variables- in-bitbucket-pipelines-794502608.html
- 23. All of those questions are in the docs! o/ Check out this link: https://confluence.atlassian.com/bitbucket/bitbucket-pipelines- 792496469.html
- 24. Off Topic: Using Docker to make tools available
- 25. Example: SugarCRM XHProf viewer The project is very useful for SugarCRM developers however some setup is required to be able to make use of it. Link: https://developer.sugarcrm.com/2016/09/05/sugar-xhprof-viewer-released-as-open-source-project/
- 26. Making it easy for a team to use The project can be set up and “containerized” with a volume made available for the files to be analyzed. Benefits: - Minimizes friction prior to using the tool - Allows a simplified workflow for sharing What tools will your team containerize? What will the benefits be?
- 27. A useful YouTube channel! o/ Check out this link: https://www.youtube.com/channel/UCnxrdFPXJMeHru_b4Q_vTPQ
- 28. Off Topic: Have you heard about BuzzConf?
- 29. An awesome technology festival! o/ Check out this link: https://buzzconf.io/go/dkcwd
- 30. Enjoy and share what you do…. I’m on Twitter: @dkcwd LinkedIn: https://au.linkedin.com/in/daveclarkprofile