Jenkins vs. Travis CI vs. Go.CD

Jenkins is our continuous integration system for packaging builds and running unit tests after each check in.

CI

Jenkins project files with Maven artifacts

Testing of Java APIs.

Opstax uses Jenkins as the backbone of our continuous integration pipeline.

Continuous deployment and build monitoring

All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.

Continuous integration and deployment automation

Our CI server—Borg—uses Jenkins to keep everything running smoothly.

Continuous integration and deployment.

Delivery/Deploy system.

To launch update development environment and perform CasperJS tests.

Is for continuous integration and monitoring of the app - the app is deployed for test through Jenkins - dashboard for monitoring of status on GitHub, App health etc.

Continuous integration that run all test and build scripts, we separate it into few build stages for multiple sub-modules.

빌드 자동화 툴로 jenkins 를 사용하고 있습니다.

Jenkins is used for running tests before and after merge, for deploying changes and for running periodic tasks, similarly to cron.

Builds project.

More customisable continuous integration, very useful for Swift compiling and PR management.

Used for optimizing our dev workflow.

Continuous integration for non-Docker builds

Continuous Integration and deploys.

It can do anything, ANYTHING!

Continuous integration with built-in testing so every release is safe and any errors are picked up immediately.

서버 빌드 및 배포

Best Open Source CI Software. We use it for Web, Mobile and BackEnd

持续集成必备

Automating build, running specs, blocking pull request, deploy on the Kubernetes, Jenkins does this all with ease.

Build, test-runner, ContinuousDelivery To Dev

CI/CD, Jenkins 2.0

• Groovy (Jenkinsfile.groovy: Pipeline as code)
• build slave (aws ec2)
• checkpoint stage
  • build
  • e2e
  • deploy to dev
  • deploy to sys
  • e2e test
  • deploy to uat
• shell scripts
  • ci.sh
  • e2e.sh
  • deploy.sh
  • publish.sh
  • publish-docs.sh

Used for continuous integration; e.g. running unit tests before deployment and of open GitHub Pull Requests.

We use Jenkins to schedule our Browser and API Based regression and acceptance tests on a regular bases. We use additionally to Jenkins GitlabCI for unit and component testing.

Continuous Integration server.

used at several companies for continuous integration and build environment.

Experience with overall Jenkins configuration, setting up agents and (multi-branch) continuous deployment pipelines through Jenkinsfiles.

Currently serves as the location that our QA team builds various automated testing jobs.

At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.

Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.

지속적인 통합을 통한 빌드와 테스팅 자동화를 위해 사용해보았습니다.

CI

Runs on a private server.

Continuous integration and build management.

Industry standard, easy to setup and reliable

Continuous Integration.

持续集成

We automate our release cycle and use it to trigger our tests once a new code was pushed

• Nodejs , Spring Project에서 자동 빌드할수 있도록 구성해봄

Continuous Testing

Continuous integration & deployment

CI/CD

Continuous Integration

• CI
• Deployments
• Reports generation
• Services life-cycle (start/stop)

To make sure that I don't push bugs to production.

CI via travis

Testing of Ruby APIs, Chef cookbooks, and builds of iOS apps.

Travis CI builds and tests every commit. It's also used to deploy Buildtime Trend as a Service to Heroku and the Buildtime Trend Python library to the PyPi repository.

Automated build testing on every commit

Continuous integration

build server and deploy to heroku

To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel

Travis provides more than one Ruby version setting. So i can test my push directly in different Ruby versions.

For GitHub integration, very easy to use and useful to get a confirmation that a build runs on a clean machine

While we usually run tests before commits, Travis goes further and tests with different Python versions and different database backends. It works great, and, best of all, it is free for open source projects.

Making sure things compile, will be adding deploy artifacts someday.

CI for our Github public repos

CI via github

As an automated build and internal release system for mobile apps

I do all of My CI/CD in Travis

Travis builds, tests and ultimately deploys our websites and APIs.

Continuous integration for some of my iOS projects and open source frameworks

Travis CI is our pillar for automated deployment, pull request testing, auto-merging (for non-mission-critical projects), and build testing per commit / release.

It is highly configurable, super cheap, and extremely robust (supports every language and configuration we've thrown at it).

Travis runs test-scripts on our repositories.

CI and testing server of my open source projects.

Build all the apps! Test all the things! Ship it when it's green!

travis, slack을 연동하여 PR마다 체크하였습니다

Deployment

We use Travis CI to test and automatically deploy our static website on our server.

Build, Test, Deploy

We use Travis CI to test our open source libraries.

To test the lambda function scripts.

Travis CI is critical for Linux and macOS CI tests for the Powershell module. Travis runs the same tests we run in AppVeyor in parallel.

We use Travis CI to run our tests on each build and to build binaries used for deployments.

Build the lfzyx.org website source code

Part of the automated build process, running any tests before deployment.

For automated testing and coverage reports