GitLab vs. GoCD vs. Jive

GitLab is good if you work a lot with code and do complex repository actions. It gives you a very good overview of what were the states of your branches and the files in them at different stages in time. It's also way easier and more efficient to write pipelines for CI\CD. It's easier to read and it's easier to write them. It takes fewer clicks to achieve the same things with GitLab than it does for competitor products.

Incentivized

Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.

Incentivized

It's definitely worth considering Jive for the type of application we've developed i.e. a central shared repository for all employees to host and discuss information. I can't say I have ever used a superior tool, but they may exist. I'm just not sure I would want to use it exclusively for file hosting, though. It does integrate with various other tools, so perhaps it would be fine if used in conjunction with another tool for that purpose.

Incentivized

• GitLab excels in managing code versions, allowing easy tracking of changes, branch management, and merging contributions.
• It helps maintain code stability and reliability, saving time and effort in the development or research workflow.
• Powerful code review features, enabling collaboration and feedback among team members.
• Robust project management features, including issue tracking, kanban boards, and milestones.

Incentivized

• Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
• The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
• Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.

Incentivized

• Individual design
• Presence of Russian language (localization can be independently established)
• You can configure several information tapes with different themes. One for work, the second for communication
• A newly-arrived network user immediately receives a prepared block for beginners. After completing several game tasks, the user will receive the basics of using Jive.
• There is a template for each scenario. There is even a template for planning R&D, and there are more than twenty of them.
• Integrates with MS Office, Google Drive, Google Docs
• There are all platforms (even Winphone and blackberry)
• You can create forum threads

Incentivized

• CI variables management is sometimes hard to use, for example, with File type variables. The scope of each variable is also hard to guess.
• Access Token: there are too many types (Personal, Project, global..), and it is hard to identify the scope and where it comes from once created.
• Runners: auto-scaled runners are for the moment hard to put in place, and monitoring is not easy.

Incentivized

• UI can be improved
• Location for settings can be re-arranged
• API for setting up pipeline

Incentivized

• Search functionality is very weak
• The information architecture and taxonomy doesnt allow for easy discoverability of content
• It's hard to navigate the and find spaces/groups that I already know about
• The main profile/interface does not allow easy access to key tasks or common tasks.

I really feel the platform has matured quite faster than others, and it is always at the top of its game compared to the different vendors like GitHub, Azure pipelines, CircleCI, Travis, Jenkins. Since it provides, agents, CI/CD, repository hosting, Secrets management, user management, and Single Sign on; among other features

Incentivized

There are always external factors that can impact this decision but currently, the Jive platform is maintaining its lead in the market place in this area. If the innovation in this space by Jive continues, then this number will remain high. Integration with other systems and adaptability to changes in the market or in client needs will also make this decision hard to predict more then 6 months into the future

I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!

Incentivized

It was harder to use that expected. The admin needs to be code savvy to truly customize the system. And users need to trained on the system and the setup. Trainings and monitoring need to continue to enforce use.

I've never had experienced outages from GItlab itself, but regarding the code I have deployed to Gitlab, the history helps a lot to trace the cause of the issue or performing a rollback to go back to a working version

Incentivized

Uptime was OK. But there was one day that the system crashed for a whole day. Our company was unable to operate. And all the plugins to word/excel froze causing those systems to freeze.

Jive posted a statement to the media saying all customers were up, but we were not.

GItlab reponsiveness is amazing, has never left me IDLE. I've never had issues even with complex projects. I have not experienced any issues when integrating it with agents for example or SSO

Incentivized

The product worked as designed. It just didn't work for our needs.

At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft

Incentivized

They did an OK job when I needed them. Except for the one day the system went down. Jive pointed the finger at the hosting company, and the hosting company pointed the finger at Jive. No reliable information came to us.

Jive online training is there. It is OK/average. I feel some other companies are doing better. It is not a piece that is required to have a successfully implementation, but it could be useful to improve it

If I did this over, I would hire out the implementation. They know the best practices and could have guided us to make an easier to use setup.

Gitlab seems more cutting-edge than GitHub; however, its AI tools are not yet as mature as those of CoPilot. It feels like the next-generation product, so as we selected a tool for our startup, we decided to invest in the disruptor in the space. While there are fewer out-of-the-box templates for Gitlab, we have never discovered a lack of feature parity.

Incentivized

GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.

Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.

Incentivized

We had a Google phone number set up before and Jive was a lot better option than that. It is more consistent and can be configured much easier and with more advanced settings. Additionally, based on the pricing as well as working with the rep on our account, it was a perfect option for us

Incentivized

I think is very well designed, and like any VCS it works as intended

Incentivized

• GitLab cut down our spent on container, package and infrastructure registry
• Best thing is we can now have everything in single platform which cost effective too
• Quality of support is really good and they do have emergency support team as well which is great

Incentivized

• ROI has been good since it's open source
• Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
• More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date

Incentivized

• reduce email traffic
• reduce amount of files/documents scattered & lost across shared drives
• increased discovery, awareness and interaction of historically more separated individuals & team functions across the organisation
• from an IT perspective, we've benefited from improved IT operations (e.g. troubleshooting info shared and easily searched/found with all team members - such that even junior team members can solve technical problems outside of business hours, lessening the burden for standby/call-in for more senior team members)

Incentivized