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
Pendo Feedback
Score 7.0 out of 10
N/A
Pendo Feedback (formerly Receptive, acquired 2019) is a SaaS product management platform that allows users to collect product feedback and feature requests from customers as well as internal teams, and collaborate on the product roadmap.
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.
Receptive is very effective for multiple internal teams/department of a single product who need to scale their product feedback management effectively. We've been leveraging it for one of our products and it was so successful, that we implemented it with a second product. The main issue we ran into situationally with that was managing 2+ modules (products) in Receptive; it was a bit more difficult to present Receptive to two different customer bases/users (we couldn't change the appearance) and slightly confusing to do within the app (lots of filtering needed). I have heard that support of multiple modules is something that Receptive will likely be working on in the near future, so that's good news.
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.
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.
There is a large development community - but it is shifting as people move towards other tools. A lot of companies still use Jenkins and will build propriety tools, which doesn't help any of the open-source community. Jenkins has a lot of help and support online, but other, more modern, alternatives will have better support for newer tech.
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.
We had UserVoice prior to Receptive but it was just too clunky and extensive for our needs. It was less about automation and still very manual work to process feedback. It also didn't provide collaboration levels that we needed for our internal teams to work together. ProdPad was a very clean tool but also didn't enable us to automate the process like Receptive does.
