Skip to content
#

Continuous integration

Automatically build and test your code as you push it upstream, preventing bugs from being deployed to production. A complementary practice to CI is that before submitting work, each programmer must do a complete build and run (and pass) all unit tests. Integration tests are usually run automatically on a CI server when it detects a new commit.

Here are 2,440 public repositories matching this topic...

jx
msvticket
msvticket commented Nov 2, 2018

Summary

When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.

This means that when new versions of the application are created the unchanged dependencies can't be reused.

It would be a great enhancement if the application code where p

cake
Wikipedia
Wikipedia

Continuous integration apps

Flaptastic

Manage flaky unit tests. Click a checkbox to instantly disable any test on all branches. Works with your current test suite

AccessLint

Find accessibility issues in your pull requests

AppVeyor

Cloud service for building, testing and deploying Windows apps

Check Run Reporter

See your test and style results without leaving GitHub. Works with any CI service. Supports JUnit, Checkstyle, and more

App Center

Continuously build, test, release, and monitor apps for every platform

Layer CI

A staging server replacement and CI/CD tool for full-stack apps

WhiteSource Bolt

Detect open source vulnerabilities in real time with suggested fixes for quick remediation

Buddy

One-click delivery automation for Web Developers

Percy

Automated visual review platform

Cirrus CI

Enjoy unlimited concurrency for fast and secure development cycle

abaplint

ABAP quality assurance and static analysis

Semaphore

Test and deploy at the push of a button

See more Continuous integration apps