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,517 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

AppVeyor

Cloud service for building, testing and deploying Windows apps

Layer CI

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

AccessLint

Find accessibility issues in your pull requests

WhiteSource Bolt

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

Codefresh

A modern container-based CI/CD platform, easily assemble and run pipelines with high performance

Buddy

One-click delivery automation for Web Developers

CircleCI

Automatically build, test, and deploy your project in minutes

BuildPulse

Automatically detect, track, and rank flaky tests so you can regain trust in your test suite

Flaptastic

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

App Center

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

Azure Pipelines

Continuously build, test, and deploy to any platform and cloud

See more Continuous integration apps