GitLab vs Jenkins

• Safeguards implemented are customizable and allow our organization to set our level of verification before merging.
• One of the smoothest and most well-organized version control software products on the market.
• Super widespread use so our use of GitLab is understandable and usable by the customer with little "translation" as to what we are doing and what they are doing.

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

• GitLab could improve some of the confusion around how permissions work (sometimes unclear why one user can do an action, but not another)
• GitLab should provide a way to rerun a merge pipeline, without rerunning the original Merge Request pipeline
• When jobs fail, it would be awesome if every user could see the information on the runner and the versions of the software it is running on (to better debug the issue)

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

• We are moving towards Gitlab only as our SCM & CI tool. So it would be an alternative to Jenkins. Saving our licensing cost there.
• We have also stopped using Confluence & using Gitlab for our documentation purposes. Reducing cost there as well.

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