Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.
N/A
Mattermost
Score 8.9 out of 10
Enterprise companies (1,001+ employees)
Mattermost from the company of the same name in Palo Alto is a messaging, collaboration and communication platform providing high security and compliance for the businesses that need it.
First of all, we don't lose messages; we can see or search messages from any point in the past. Second, it offers to manage the whole product ourselves from hosting to serving users of our organisation. We feel that we have full control over data, managing users, …
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
I used Mattermost on a full remote company and it perfectly suited our collaboration and communication culture. The company dealt with privileged and personal information of a huge data base of users, so it was a significant advantage for our need to comply with industry regulations.
Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
Mattermost has been an excellent tool for our business, allowing for a very cost-effective means of communicating, collaborating, and sharing project and business documentation and resources. The free community edition allows for simple installation on existing cloud server resources which results in significantly lower recurring costs compared to the competition
Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
Since it helps track all the things at one place and the bots can be made which helps to automate many tasks. We use it in our security incident tracking in which there are pre defined tasks like adding people, creating groups, launching bots. All these things make the work easier and oraganized
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
We have not had to contact support for Mattermost ever. All that we have needed has been available in the documentation or website. One of our DevOps team members set it up in a couple of hours. The whole team was using Mattermost that same day. No support needed.
It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
I feel slack is a bit more difficult to use overall than Mattermost. Mattermost makes the tasks of communicating across departments and team members easier, as well as giving the ability to share information via hyper links, attachments, and other forms of communication among every body here. Also, easier user interface
