When we define 'pull-requests': develop: - - - extra code Here in this case pull request run based on source branch and not a destination. From the above code, when you create PR from develop to master ( which is very common in industries) at that time your pipeline will run. But when someone raised PR from feat/notification_update to develop. At that time Pipeline will not work. Pipelines 'pull-request' is based on source branch & not a destination based.
using this pull-request: and branches under it I am sure that a pull request will be created each time I commit new code? in case no so how to be sure that each time I push new code a pull request will be created or updated
I'm going to guess you mean you've got an existing PR up, and you want to make sure it creates a new build/runs your pipeline every time you commit code to the branch in that PR? If so, you should be able to just commit & push up your changes -> Go to pipelines in bitbucket -> and there should be a new build taking place.
CD depends on where you're deploying to. For example if you're throwing it on firebase, you'd just add your commands to deploy to firebase in one of the steps in the yaml file and include it in the appropriate step.
When we define
'pull-requests':
develop:
- - - extra code
Here in this case pull request run based on source branch and not a destination.
From the above code, when you create PR from develop to master ( which is very common in industries) at that time your pipeline will run.
But when someone raised PR from feat/notification_update to develop.
At that time Pipeline will not work.
Pipelines 'pull-request' is based on source branch & not a destination based.
Exactly
Thanks! Very helpful guide for a beginner in these topics
Glad it was helpful!
using this pull-request: and branches under it I am sure that a pull request will be created each time I commit new code? in case no so how to be sure that each time I push new code a pull request will be created or updated
I'm going to guess you mean you've got an existing PR up, and you want to make sure it creates a new build/runs your pipeline every time you commit code to the branch in that PR? If so, you should be able to just commit & push up your changes -> Go to pipelines in bitbucket -> and there should be a new build taking place.
Thanks, this was super helpful, I've been wondering how CI/CD pipelines worked.
Good to hear!
So clear.... amazing!!!!!!
Glad you think so!
how can we setup aws aurora mysql through this bitbucket pipeline?
If your using JavaScript you can just put a script in your package json and run that script in your pipe
This is only for CI. What about CD?
CD depends on where you're deploying to. For example if you're throwing it on firebase, you'd just add your commands to deploy to firebase in one of the steps in the yaml file and include it in the appropriate step.
Nice!