Need advice about which tool to choose?Ask the StackShare community!
AWS CodePipeline vs Bitbucket: What are the differences?
AWS CodePipeline: Continuous delivery service for fast and reliable application updates. CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define; Bitbucket: One place to plan projects, collaborate on code, test and deploy, all with free private repositories. Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
AWS CodePipeline and Bitbucket are primarily classified as "Continuous Deployment" and "Code Collaboration & Version Control" tools respectively.
Some of the features offered by AWS CodePipeline are:
- Workflow Modeling
- AWS Integrations
- Pre-Built Plugins
On the other hand, Bitbucket provides the following key features:
- Unlimited private repositories, charged per user
- Best-in-class Jira integration
- Built-in CI/CD
"Simple to set up" is the top reason why over 3 developers like AWS CodePipeline, while over 896 developers mention "Free private repos" as the leading cause for choosing Bitbucket.
According to the StackShare community, Bitbucket has a broader approval, being mentioned in 1735 company stacks & 1449 developers stacks; compared to AWS CodePipeline, which is listed in 30 company stacks and 15 developer stacks.
Do you review your Pull/Merge Request before assigning Reviewers?
If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:
- Pick the correct target branch
- Make Drafts explicit
- Name things properly
- Ask help for tools
- Remove the noise
- Fetch necessary data
- Understand Mergeability
- Pass the message
- Add screenshots
- Be found in the future
- Comment inline in your changes
Read the blog post for more detailed explanation for each item :D
What else do you review before asking for code review?
One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but git rebase -i is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.
It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.