AWS CodePipeline vs Jenkins

• It is reliable and works without errors
• It integrates well with our repository and all other AWS functions as well as our end database

Read full review

• Automatic jobs: there are infinite possibilities when it comes to Jenkins. You can run code against any testing suite you can imagine or conjure up. You can deploy applications at any time anywhere, automatically with no human intervention. If a certain stage fails, it will notify the team and your sysadmin of the issue so you can resolve it as quickly as possible
• Automatic rollback: because of how Jenkins works, it can hold off publishing code and integrate locally to run QA procedures before pushing to deployment. This means that bugs are caught before your servers are updated and prevents a faulty program from affecting your downtime in the first place. Its a game changer for high availability.

Read full review

• Ease of use - things like CircleCI or other tools are a bit easier to learn.
• Ability to build from more sources.

Read full review

• Once we organized a hackathon with our GitHub Storage. Jenkins was integrated at that time. We had a 20GB plan, but it oversized to 50GB. We had to bear a large sum of money which was unpredicted by our company. Being a startup we cannot bear such mistakes.
• Jenkins cannot be easily studied and managed. We have to recruit personnel part-time for managing and servicing the server.
• Though it is open source, there is no dedicated community driven forum or support. There are 3rd party discussion and support portals. Thus, we use Gitter always for debugging and solutions.

Read full review

• CodePipeline has reduced ongoing devops costs for my clients, especially around deployment & testing.
• CodePipeline has sped up development workflow by making the deployment process automated off git pushes. Deployment takes very little coordination as the system will just trigger based on what is the latest commit in a branch.
• CodePipeline offered a lot of out-of-the-box functionality that was much simpler to setup than a dedicated CI server. It allowed the deployment process to built and put into production with much less and effort and cost compared to rolling the functionality manually.

Read full review

• Low investment: As the software is open source, there is no purchase required for on-premises installations, and there is a low barrier to entry for companies offering hosted solutions. This leads to competition on price, and therefore lower prices.
• Saves time by automating manual tasks: There are often a lot of repetitive tasks that need to be done to prepare for a release, and Jenkins enables these tasks to be run easily and frequently (for example, running tasks on every pull request)
• Near-immediate returns: Spend a day or two and easily automate most common tasks. Reports are visible so that managers and team leads can keep an eye on code quality.

Read full review