4. Deploying For Different Environment
● Do same thing over and over for
○ Development
○ Staging
○ Production
Because the normal flow for Development is moving from
Development → Staging → Production
6. Why use Bitbucket pipeline
● Sufficient coverage gives you confidence to deploy.
Reduce human error and keep the team lean working on
critical tasks.
● Pipelines can be aligned with the branch structure,
making it easier to work with branching workflows like
feature branching or git-flow.
● Stop jumping between multiple applications. Manage your
entire development workflow within Bitbucket, from code
to deployment.
7. Demo with an Angular application and Shared Server
Source code: https://bitbucket.org/theo4u/aug-wecode
Pushing to
● Develop branch should push to our development server
● Master branch should push to our staging server
● Tagging master branch should push to our production server
Using: Git-FTP
8. Demo with an Angular application and Paas (Heroku)
https://confluence.atlassian.com/bitbucket/deploy-to-heroku-872013667.html
9. Demo with an Angular application and VPS
Using: SSHPASS
10. bitbucket-pipelines.yml
You can read more on bitbucket pipeline configuration here
https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-
792298910.html
Online validator for your
https://bitbucket-pipelines.prod.public.atl-paas.net/validator.html
Because of time we are moving straight to what we do normally and how we can automate the process
Show example uploading to ftp client after building your application with angular