Need advice about which tool to choose?Ask the StackShare community!
Jenkins vs Perforce: What are the differences?
- Integration with version control system: One key difference between Jenkins and Perforce is their integration with version control systems. Jenkins primarily focuses on continuous integration and can integrate with various version control systems, allowing developers to automate build and testing processes. Perforce, on the other hand, is a version control system that focuses on managing software development and versioning files. While Perforce can integrate with some CI/CD tools, it does not provide the same level of automation and flexibility as Jenkins.
- Scope of functionality: Jenkins is a versatile automation server that offers a wide range of functionality beyond just CI/CD. It supports plugin integration, allowing users to extend its capabilities to meet their specific needs. Perforce, on the other hand, is primarily focused on version control and collaboration, providing features like branch management, file versioning, and merge tracking. While Perforce offers some CI/CD capabilities, it may not provide the same level of functionality as Jenkins in terms of automation and customization.
- Ease of use: Jenkins is known for its user-friendly interface and easy setup process. It provides a web-based dashboard that allows users to configure and manage their automation processes with ease. Perforce, on the other hand, may have a steeper learning curve for new users, as it is primarily designed for developers and version control management. The setup and configuration process in Perforce may require more technical expertise compared to Jenkins.
- Scalability: Jenkins is highly scalable and can support large-scale deployments with a distributed architecture. It can handle a high volume of builds and tests concurrently, making it suitable for enterprises with complex software development needs. Perforce, on the other hand, may have some limitations in terms of scalability, especially when it comes to managing a large number of branches and file versions. While it can handle moderate-sized projects efficiently, it may require additional resources to handle larger scale deployments.
- Community support and ecosystem: Jenkins has a vast and active community of developers, offering a wide range of plugins and integrations. It has a well-documented ecosystem, with numerous online resources, forums, and communities that provide support and assistance to users. Perforce, on the other hand, may have a smaller community compared to Jenkins, which might limit the availability of plugins and community-driven solutions. While Perforce does have its own developer community and support resources, it may not be as extensive as the Jenkins community.
- Pricing and licensing: Jenkins is an open-source tool, free to use and modify, making it cost-effective for organizations of any size. It provides the flexibility to customize and adapt the tool according to specific requirements without any licensing fees. Perforce, on the other hand, is a commercial product that requires a license for usage. It offers different licensing options based on the number of users and scale of deployment, which may involve additional costs for organizations.
In summary, Jenkins and Perforce differ in terms of their integration with version control systems, scope of functionality, ease of use, scalability, community support, and licensing. Jenkins provides a versatile automation server with extensive integration options and community support, while Perforce focuses on version control management with some CI/CD capabilities but may have limitations in terms of scalability and community resources. Jenkins is also open-source, making it cost-effective for organizations, while Perforce is a commercial product with licensing costs.
We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.
If your source code is on GitHub, also take a look at Github actions. https://github.com/features/actions
I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.
Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.
I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !
I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.
From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"
We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.
As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !
I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.
I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.
One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.
Feel free to checkout an example: Cloudbuild Example
I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.
You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.
I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.
If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).
Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.
CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.
And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.
Pros of Jenkins
- Hosted internally523
- Free open source469
- Great to build, deploy or launch anything async318
- Tons of integrations243
- Rich set of plugins with good documentation211
- Has support for build pipelines111
- Easy setup68
- It is open-source66
- Workflow plugin53
- Configuration as code13
- Very powerful tool12
- Many Plugins11
- Continuous Integration10
- Great flexibility10
- Git and Maven integration is better9
- 100% free and open source8
- Github integration7
- Slack Integration (plugin)7
- Easy customisation6
- Self-hosted GitLab Integration (plugin)6
- Docker support5
- Pipeline API5
- Fast builds4
- Platform idnependency4
- Hosted Externally4
- Excellent docker integration4
- It`w worked3
- Customizable3
- Can be run as a Docker container3
- It's Everywhere3
- JOBDSL3
- AWS Integration3
- Easily extendable with seamless integration2
- PHP Support2
- Build PR Branch Only2
- NodeJS Support2
- Ruby/Rails Support2
- Universal controller2
- Loose Coupling2
Pros of Perforce
- Powerful3
- Great for Enterprise level use3
- Robust2
- Scalable1
Sign up to add or upvote prosMake informed product decisions
Cons of Jenkins
- Workarounds needed for basic requirements13
- Groovy with cumbersome syntax10
- Plugins compatibility issues8
- Lack of support7
- Limited abilities with declarative pipelines7
- No YAML syntax5
- Too tied to plugins versions4
Cons of Perforce
Sign up to add or upvote consMake informed product decisions
What is Jenkins?
What is Perforce?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Perforce?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Jenkins?
What tools integrate with Perforce?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+7
+4
+7
+4
+17
+22
+42
+37