Pradip Shah discusses using Bitbucket Pipelines to build continuous integration and delivery pipelines for WordPress and Magento applications. Bitbucket Pipelines uses Docker containers to run build steps defined in a YAML configuration file. Key benefits include reducing the cost of testing with containerization, and the ability to automate deployments through continuous delivery. The presentation provides an example Magento 2 pipeline and discusses concepts like separating concerns between Docker images and pipeline steps.

1. Build pipelines
Using Atlassian / Bitbucket
Pradip Shah
Founder, luroConnect
devops, performance, scale and security
Wordpress & Magento

2. Devops solves the wall of conflict

3. A key manifestation of the wall of conflict

4. Devops fixes this by CI/CD

5. Pipelines vs traditional CI
• Pipelines enhances traditional CI
• Steps for targets
• Reduces cost of running a CI by containerizing CI
• Pipelines should encompass CI and CD
• Continous Integration
• Builds ability to deliver at will
• Continous Delivery
• Ability to automate the delivery

7. Bitbucket Pipelines

8. Bitbucket Pipelines Promise

9. Bitbucket Pipelines
• Bitbucket Pipelines runs pipelines using Docker containers.
• Use the validator to check format
https://bitbucket-pipelines.prod.public.atl-paas.net/validator.html
Name The name of the file must be bitbucket-pipelines.yml
Location The file must be located in the root directory of the repository that you want to build.
Format The content of the file must be compliant with our bitbucket-pipelines.yml guidelines

10. YAML : Quick overview
• Key value pairs in the familiar key: value syntax
• Value can also be a associative array – set of key values either in curly
braces or one per line
• Value can be a list [item, item] OR each item starts with a hyphen
• Indentation is important
• Indentation is spaces
• # makes a comment to the end of line

11. Defining pipelines contd
• You can define the following types of pipelines in the bitbucket-
pipelines.yml file:
• default
• branches
• tags
• custom
• You can refer to branches, tags, and bookmarks in a pipeline using their
name, or by using glob patterns.
• If you want to trigger some build pipelines manually, you can add them in
the custom section.
• Every pipeline can have up to 10 steps. Each step contains a script which
defines the actions that should be performed to execute a build.

12. Keywords in a bitbucket pipeline

13. Our Demo : Magento 2 application
• In order to move code to production Magento requires
• Deploy static (less->css)
• Compile (moves files to generated, resolves conflicts, some checks)
• Optionally
• Do more checks
• Minify css / js / (static) html
• Run tests

14. steps
• Steps are executed in the order that they appear in the bitbucket-
pipelines.yml file,
• Each step runs in separate Docker container
• Use artifacts to pass built folders down to next step
Each step can be configured to:
• Use a different Docker image.
• Use specific caches
• Uses services
• Produce artifacts that subsequent steps can consume.

15. Note on separation of concerns
• There is an overlap on what can be done in a step and in docker
• Docker Image
• Closely match a environment you want the application to run in
• Pipeline
• Specific to the application
• Focus on build steps rather than image
• Might be a good idea to put the Dockerfile(s) in use in the git

16. Service : mysql
• Mysql will be a separate docker instance called a service instance
• Ofcourse you can make a single docker image with mysql but that would
break the idea of containerization
• Bitbucketpipeline maps ALL ports from the service to the main
instance
Main
Instance
Running
pipeline
Service 1 : mysql
Service 2 : redis
127.0.0.1
:5903
127.0.0.1
:6380
5
9
0
3
6
3
8
0

17. Security of passwords
• Use environment variables for things like AWS keys, clusterinfo,
docker user, etc.
• Environment variabes are at the project level
• Use keys to ssh to
• get authentication files from a remote server
• ssh to deploy built objects

18. Docker build a container and push
• Simply
• docker login –u $DOCKER_LOGIN –p $DOCKER_PASSWORD
• docker build –t luroConnect/M2:$BITBUCKET_COMMIT
• docker push luroConnect/M2:$BITBUCKET_COMMIT

19. Conclusion
• Devops aims to banish “It works
on my machine” syndrome
• Breaks barriers between
developer and operations
• Bitbucket Pipelines help speed
up the process
• Using docker it reduces the cost
of each test and improved
turnaround

20. Resources used in this presentation
• Docker Image used in the pipeline
https://hub.docker.com/r/luroconnect/bitbucket-pipeline-magento2/
• Bitbucket pipeline yaml file
https://bitbucket.org/rrap/magento2/src/master/bitbucket-
pipelines.yml
See the branch for variation

21. Where to find us
http://www.luroConnect.com/
info@luroConnect.com
@luroconnect