...
Navigate to the repository and click on the settings icon.
Go to "User Management" and click on "Invite."
Here click on Invite button and the redirect to Invite people to Bitbucket screen.
Enter the bitbucket@stagingpro.com
Product Role: Click There are 3 product roles, click on the drop down field and click on the relevant checkbox(es)
...
select all of them
User
Product admin
User access admin
...
There are 4 group permissions:
bitbucket-admins
bitbucket-user-access-admins
butbucket-users
org-admins
Select the group permission "bitbucket-admins-themedeploy-stagingpro"
...
To remove a user, click "Remove" in StagingPro. This action removes the user from StagingPro but not from Bitbucket.
...
...
Generate your own OAuth consumer key and secret key to build your own custom integration with Bitbucket.
1) Add OAuth Consumer
Click on Settings > workspace settings > OAuth Consumer > Add Consumer
...
2) After entering all the necessary fields on the OAuth Consumer form, click on save. You can integrate using the the following API url.
https://bitbucket.org/themedeploy-stagingpro/workspace/settings/api
Code Deployment Process
a) Workflow for direct commit
Clone the environment branch by using the command
git clone --branch $branchName https://userId:$oauthToken@bitbucket.org/ravistaging/stagingprobigi.git $branchName
After cloning branch go the folder Make some changes in the files
Open gitbash and write cd Productione160c1(“cloned folder);
git clone --branch branchname https://bigistagingprolatest:$authtoken@bitbucket.org/bigistagingpro/stagingprostaging.git branchname
After cloning branch do cd branchname
Make changes in the required file
git status to check the changes
git add --all : to add all the changes
git commit -m 'Commit Message'
git push origin branchname
Then go to code deployment screen there Go to Code Deployment screen wherein you can see the direct commit changes like this as follows:
By clicking on “Generate Preview and Approve Later” link user can launch Preview for direct commit
Click on “Approve and Deploy to initiate deployment
Workflow for Pull Request
Create Pull request in your bitbucket account under repository section
See the left menu and click on “Pull request”
Click on create pull request on the top right side then select the Environment branch for the destination branch dropdown.
you will see this screen where you can add your comment and then click on “approve” and “merge”
After clicking merge you will see this screen
...
You can add your comment but do not made modifications on top commit message like “Merged in Akanksha247e160c1472899 (pull request #12)” and simply click on “Merge” button Then you will start seeing entries like this under “Code Deployment”
Here you can see the generate Preview link click on “Generate Preview and Approve Later” link and select the correct note version from dropdown and then again click on “Launch Preview” button.
...
Q1. After giving Admin access to StagingPro Git Bitbucket repository, I see some autogenerated code branches e.g. Productione347c1, so should I keep the names as it is?
A1. Yes, that is correct. These environment branch names are autogenerated and required for code commit tracking. Please do not delete or rename these branches as it will affect the BitBucket integration.
The branches are created
i) per environment
ii) per channel and
iii) per team member
Q2. What is the purpose of developer branches?
A2. As a best practice, developers are given their own branches so they can commit their codes to their own branch at the first instance, or for more frequent code commits at the developers convenience without affecting the environment branch.
Q3. Are there any benefits to using a developer branch over a more typical git Bitbucket feature branch (e.g., feature/TICKET-description-of-the-change)?
A3. Yes indeed! The developer can commit to their branch first. Once the task is complete, they can merge the code from their branch to the environment branch. If many developers are working on a common task, they can commit codes to each of their individual branches without affecting the other developer branches. And can merge their code easily.
...
Q7. Can you explain how version control works for StagingPro with multiple development teams as part of existing CI/CD pipelines?
A7. When you successfully configure the BitBucket integration on your StagingPro tenant, your GIT Bitbucket commits will be visible on the ‘Code Deployment’ tab which displays incremental version numbers.
The code branches are created
i) per environment
ii) per channel and
iii) per repo team member.
Refer the ‘StagingPro
...
Bitbucket Branch workflow’ section of this document.
Under Settings > Status Notifications you can enable the Deployment Notifications checkbox for team notifications through
i) Email
ii) Teams and
iii) Slack for shared visibility and effective collaboration.