-
Updated
Mar 5, 2021 - Go
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,396 public repositories matching this topic...
-
Updated
Mar 9, 2021 - Java
-
Updated
Jan 27, 2020 - JavaScript
-
Updated
Mar 9, 2021 - Go
-
Updated
Mar 9, 2021 - Java
JanitorConfigurator should have an option to delete logs for specific builders (or tags). Users might want to delete logs for only specific builders, or might want to keep logs for specific builders for longer duration.
http://docs.buildbot.net/latest/manual/cfg-configurators.html#janitorconfigurator currently doesn't seems to contain any such option.
-
Updated
Jan 14, 2021 - JavaScript
We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome
Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.
This is blocked until #114 is merged which comes with first initial integration.
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
-
Updated
Jan 19, 2021 - JavaScript
-
Updated
Mar 9, 2021 - Java
-
Updated
Mar 9, 2021 - Go
The MSBuildSettings extension UseToolVersion expects a valid value from the MSBuildToolVersion enumeration.
public static MSBuildSettings UseToolVersion(this MSBuildSettings settings, MSBuil-
Updated
Mar 7, 2021
-
Updated
Jun 11, 2020 - PHP
-
Updated
Mar 9, 2021 - Go
-
Updated
Mar 8, 2021 - Python
-
Updated
Mar 9, 2021 - Ruby
-
Updated
Mar 9, 2021 - Go
-
Updated
Oct 8, 2020
-
Updated
Mar 4, 2021 - CMake
-
Updated
Dec 18, 2020 - Go
-
Updated
Mar 8, 2021 - TypeScript
-
Updated
Mar 8, 2021 - JavaScript
-
Updated
Mar 9, 2021 - C#
-
Updated
Mar 7, 2021 - Java
-
Updated
Jan 13, 2021 - Shell
-
Updated
Feb 18, 2021 - PHP
- Wikipedia
- Wikipedia
Continuous integration apps
App Center
Continuously build, test, release, and monitor apps for every platform
Cloud 66 Skycap
Skycap is a container native CI/CD tool
AccessLint
Find accessibility issues in your pull requests
Cloud 66 for Rails
Build, deploy, and maintain your Rails apps on any cloud or server
Azure Pipelines
Continuously build, test, and deploy to any platform and cloud
Percy
Automated visual review platform
Check Run Reporter
See your test and style results without leaving GitHub. Supporting JUnit, Checkstyle, and more
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
Semaphore
Test and deploy at the push of a button
AppVeyor
Cloud service for building, testing and deploying Windows apps
Travis CI
Test and deploy with confidence
Buddy
One-click delivery automation for Web Developers
Codefresh
A modern container-based CI/CD platform, easily assemble and run pipelines with high performance
Hound
Automated code reviews
Summary
#6369 tracks the user who created the build (either manual trigger or rerun) and also tweaked the
api/v1/userendpoint to contain a newdisplay_user_idfield. The new field should be used to show the user in the top bar, since it reflects the same value that Concourse tracks as the build creator.We should be able to replace [this function](https://github.com/concourse/concour