Gerrit Code Review vs Travis CI: What are the differences?

## Key Differences between Gerrit Code Review and Travis CI

Gerrit Code Review is a code review tool used primarily for reviewing source code changes before they are merged into the main codebase, ensuring better code quality, whereas Travis CI is a continuous integration tool used for testing and building software projects, ensuring code stability and quality.

1. **Integration**: Gerrit Code Review integrates directly with Git repositories, allowing developers to submit, review, and merge code changes within the same platform, while Travis CI integrates with version control systems like GitHub or Bitbucket to automatically build and test code changes.

2. **Code Review Process**: In Gerrit, code reviews are performed by peers who provide feedback on the proposed changes, leading to more comprehensive and detailed reviews, whereas Travis CI focuses on automating the testing process and providing feedback on the build status based on predefined criteria.

3. **User Interface**: Gerrit Code Review offers a web-based interface for code reviews, with features like inline commenting and detailed change history, providing a more interactive and collaborative review process, while Travis CI provides a dashboard view of build statuses and logs, focusing more on the automation aspect of testing.

4. **Workflow Management**: Gerrit Code Review allows for custom workflows with multiple code review stages and permissions settings, offering flexibility in managing the code review process for different projects, whereas Travis CI follows a predefined build pipeline workflow, making it easier to set up and use for continuous integration tasks.

5. **Notification System**: Gerrit Code Review notifies users about code changes, reviews, and approvals through email notifications, keeping users informed about the progress of code reviews and merge requests, while Travis CI notifies users about build statuses and failures through email or chat notifications, helping teams to address issues promptly.

6. **Deployment Options**: Gerrit Code Review is primarily used for reviewing code changes and does not focus on deployment tasks, whereas Travis CI can be configured to automate deployment tasks along with testing and building, providing a more integrated continuous integration and deployment solution.

In Summary, Gerrit Code Review and Travis CI differ in their focus on code review vs. continuous integration, integration methods, code review processes, user interfaces, workflow management, notification systems, and deployment options.