Jenkins Reviews

This tool made the development flow fluid. Standout features are the continuous integration and a variety of support offered for creating packages for a number of technologies like, Java, C#, C++, etc and across multiple platforms that makes releases easier for faster roll out of business functionalities . It also has hundreds of plugins that can help you setup continuous integration and continuous delivery tool chain in quick time. You can easily scale out Jenkins across multiple machines, and support simultaneous large number of builds, tests and deployments across multiple platforms.

Jenkins is as our R&D build and deploy pipeline.
It allows us to:
1) Run end to end and unit tests every time we push new code.
2) Compile and bundle our code.
3) Deploy images and containers it to our Azure servers (Kubernetes).
4) Give us a nice dashboard to view that status of the tests, builds, and deployment.

Jenkins is the tool we use for building our code, running our test cases and also for few of the inhouse datacenter deployments.

Apart from the regular CICD, we also use it for many of our other automation tasks, for example automating regular operational tasks like disk cleanup, log rotation etc.

Jenkins is used for automating the build process of testing, deployment, and release. It makes continuous deployment faster and an automated process. It is used across the organization.

Jenkins is currently used to build and deploy our Amazon infrastructure. We practice the principles of infrastructure as code, meaning our infrastructure config and setup is checked into a revision control system and built via Chef and other scripts. Jenkins manages building that automatically or on demand and ensures that everything that is checked in is working properly.

We primarily use Jenkins as part of our build infrastructure for compile and build, typically executing mavens builds but also ant scripts for more complex tasks and workflows

Jenkins is an extremely powerful continuous integration/continuous delivery tool. It can be used to automate a very diverse set of operations - including, but also well beyond, application deployments. This is thanks to amazing flexibility and the impressive number of available plugins.

In the traditional sense, Jenkins easily addresses the following problems:

• Build and release automation
• Test automation with result report generation
• Test coverage reports
• Version control polling
• Status notifications
• Conditional, concurrent and branched pipelines
• Master-slave architecture
• Credentials storage
  
• Really, any custom scheduled or event-driven (primarily via version control events) workloads - of course don't go crazy with that, you don't want to schedule data science jobs on Jenkins for example. Key word is "operations".
  

Thanks to its large community and amount of available plugins, you can easily:

• Integrate with Slack to push notifications, also true for many other chat services
• Integrate with GitHub, GitLab, Bitbucket via hooks (as opposed to polling)
• Create and restore backups
• Integrate with external authentication providers (e.g. OAuth)
• Define your pipelines as code

Jenkins is one of the best open source Continuous Integration and Continuous Deployment tools. It is used in most of the projects in our company where we need a CI/CD pipeline. In the aspect of test automation, it is most helpful for the continuous executions whenever there is a new build.

Jenkins is used across our entire organization. For our dev shop, it mains our build cycle by completing builds of code and handling deployment of code. In addition, we even utilize it to roll out database schema changes. If this wasn't enough, we also utilize Jenkins to generate content based off of markup. Jenkins has allowed us to meet the needs of our dev department of continuous integration while allowing customers to put out content in a timely manner.

My organization has deployed Jenkins as the main continuous integration tool for their projects which is responsible for automating all the unit tests, integration tests, end-to-end tests and also the process of releasing the final products as configured.

Jenkins is a continuous integration tool on which my team relies heavily. My whole company uses Jenkins. It starts our build process, and goes all the way to start the code pipeline, from then our release goes from qa env, to e2e, and to production. Each job on Jenkins starts automatically when we push a new code to master.

Currently Jenkins is being used across the IT team in our organization. It simply does the hard job of automating all the repetitive tasks, includes details in projects, inside builds, follows workflows, accesses operating systems, and alerts when it's done, or, based on decisions during tasks, what to do. This reduced a lot of work for our dev teams, but also now is helping the infrastructure team and other departments. The knowledge of Jenkins utilization replicates really fast inside our organization as at least one people inside every team learned about or knows how to use it to build a simple job to automate a task, workflow or a deploy. Jenkins also allows us to monitor what's being done, helping managers and the team have an overview of how a pipeline is running. Another problem that Jenkins solved is centralizing automation. As it's controlled by a web console, it's easy to check what is being done, access logs of old jobs, view the entire console output and know exactly who and when a job was last executed. Also, you may set permissions by project, by job, or what you or your organization needs.

It is being used by mostly the technology department. It allows us to run jobs between engineers and non-engineers. It increases productivity by automating processes.

In our EAI department, we are using Jenkins to automate building and packaging TIBCO BW project.
Once the testing step is OK, the package is installed firstly in test environment.
Jenkins process is triggred each time a code is commited on SVN.
Jenkins can also serve as a versioning system because each time a build is made, its version is stored in Jenkins

I used Jenkins to manage both development and release builds of software at my two previous roles (IBM and Red Hat.) In both cases, each department had its own instances, so that plugins could be customized and managed on a per-team, per-product basis. It enables teams to manage a fleet of build servers (slaves in Jenkins parlance) that can build source code and run tests in an automated fashion, across platforms - this enables cross-platform software to be tested against various versions of Windows and Linux, for example. It can also be used for simple automation tasks, though other tools like Ansible are better suited for those tasks.

We have been using Jenkins across the company. The infrastructure provided by Jenkins allows us to automate our build process. The ability to work with numerous plugins makes it super easy to change various parts of the manual process to be fully automated. This reduces the level of effort engineers need to put in.

Jenkins is used as a default tool for continuous integration across the enterprise. We have multiple instances for different applications. The slaves are auto scaled depending on the demand for builds. Jenkins builds, deploys and tests our deliverables providing instant feedback when changes are implemented. We use a numerous number of plugins to support our choice of technologies

Jenkins is used as a development only tool as a manual as well as continuous integration tool with hooks into Artifactory. We have 15 build machines supporting Windows, Mac OSX and Linus Operating Systems.

We are mainly using jenkins to automate many parts of out software development life cycle like:
- Build artifacts after commits
- Run integration tests
- Deploy artifacts

Jenkins is being used by the whole organization.

Jenkins is being used as the orchestration layer for our Continuous Delivery Pipelines. The DSL is used to set up Pipeline-As-Code.

Jenkins is really useful at the time of regression testing. At the time of deployment it’s very handy to use, just have to trigger the build corresponding to the environment and to get your job deployed. Also, we have automatic build triggers in Jenkins, which get activated when there is any code change.This reduces the manual effort of triggering a build.

We have been using Jenkins in different areas of organization such as in Development, Test Automation and in cases for building docker images.

We use it across all the dev org. Maintenance is pretty straight forward and there are so many plugins to choose from. We have about 20-25 build machines that are continuously running jobs. It has so many hooks for svn.

We use Jenkins to build and deploy AEM (java/maven) applications. We usually stand up one instance per project so that teams do not interfere with each other. At the end of the project we destroy those instances. It is used primarily for CI to dev and qa environments, and final build package delivery. It integrates with our package management system Artifactory.

We have been able to leverage existing free plugins, and not needed to write any custom or convoluted scripts.

Jenkins is been use as our main CI/CD software, we have a micro-service architecture that is been build, tested, deployed through all our environments qa, staging, production and all of them at scale. We also build on jenkins our mobile applications with the same flow we build test and deploy our applications to the stores reducing human error on configurations and spotting issues before we even know about it. That allow us to reach an estate of trust with our clients.
About Jenkins we are using the new BlueOcean interface, what it is really amazing; and using Pipelines as our definition language.