...
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 on the drop down field and click on the relevant checkbox(es)
There will be 3 group permissions:
bitbucket-admins
bitbucket-user-access-admins
butbucket-users
Select the group permission "bitbucket-admins-themedeploy-stagingpro"
...
Add stagingpro as a user, assign it "Admin" permission at the repository level
...
Click on Invite users button to send the invitation
For additional users:
Assign developer permissions.
Follow similar steps, but assign different permissions.
...
Step 5: Verify Repository
...
To remove a user, click "Remove" in StagingPro. This action removes the user from StagingPro but not from Bitbucket.
...
Create OAUTH Token
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/bigisagingprothemedeploy-stagingpro/workspace/settings/api
Code Deployment Process
a) Workflow for direct commit
...
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 you can see the direct commit changes like this
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.
...
Staging Pro StagingPro Deployment workflow
The following illustration shows the suggested ideal process as part of the Git development workflow with Pull request, that can be implemented as part of your StagingPro setup.
...
The status will show as ‘Rejected|Code Not approved’
...
A few
...
Bitbucket FAQS
Q1. After giving Admin access to StagingPro Git 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.
...