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,019 public repositories matching this topic...
-
Updated
Apr 5, 2020 - Java
-
Updated
Jan 27, 2020 - JavaScript
This is a dup of #1620. However #1620 was closed by the stale bot and I can't reopen it. The issue still has merit so I (re-)submit the issue.
For our purposes, we'd just like the file names easily parsable and since the terminal's ls -l sorts by filename by default, make sure the filenames start with the year, month, day, hour etc.
Currently, lib/testsuite/screenshots.js:18 has:
st
The first few Google results for OpenShift alert documentation point to https://docs.openshift.com/online/dev_guide/notifications.html , which is now a dead link.
Please help Google point results to the right link, such as by redirecting from this URL to a valid one.
In order to make the UI/UX consistent across all pages of GoCD, GoCD is rebuilding the Pipeline Config Edit Page (changing into a Single Page App).
As part of this page rewrite, following changes needs to be done on the plugins:
Breaking Changes
Task Plugins View:
GoCD Task Plugins implements Get Task View extension call, which
What challenge are you facing?
The help text for fly order-pipelines:
Usage:
fly [OPTIONS] order-pipelines [order-pipelines-OPTIONS]
Application Options:
-t, --target= Concourse target name
-v, --version Print the version of Fly and exit
--verbose Print API requests and responses
--print-table-headers Print table heade
There's a list of deprecation warnings installing Strider. A sample as follows:
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated mailcomposer@0.2.12: This project is unmaintained
npm WARN deprecated browserslist@1.4.0: Browserslist 2 could fail on re
I cannot find any reference, in the documentation, about how the history of past builds is handled. Is it stored in memory? On files? On the database?
I'm running buildbot in docker (one container for the master, one for the worker, as in the "simple" scenario). Whenever I have to modify the master.cfg I have to
- stop the master container
- remove the master container
- start again the mas
Summary
ShouldInstallBinary function is currently checking presence of binary on the $PATH variable and returning false if not present there (while it's present on JX/bin).
Expected behavior
It should be checking at JX/bin for the binary, if not present should return false.
Colours are replaced by black and white with travis formatter
xcpretty -c Travis output
xcpretty -f `xcpretty-travis-formatter` Travis output

at getModulePat
-
Updated
Nov 5, 2018
-
Updated
Mar 28, 2020 - Go
On the basis of Review Russian documentation #1963
- Main
- README
- Documentation Overview
- Configuration / Introduction
- Configuration / Dockerfile image
- Configuration / Stapel Image / Naming
- Configuration / Stapel Image / Base Image
- Configuration / Stapel Image / Docker directive
- Confi
... or even decide to not deprecate it after all.
This came up on the mailing list.
It seems that this config option is well established, works as expected and is used in many scenarios (especially corporate when using internal pypi repos with different stages or devpi). So we might want to
Describe the bug
I just signed up and went to the public templates section.
There is only one template shown (see screenshot).
To Reproduce
Steps to reproduce the behavior:
- Go to 'https://cloud.lastbackend.com/templates#public'
- See error
Expected behavior
I was expecting a lot more, e.g. Wordpress, MongoDB, Bootstrap, PostgreSQL, Etherpad, Apache, CouchDB, SearX, wall
-
Updated
Dec 31, 2019 - PHP
-
Updated
Apr 5, 2020 - JavaScript
-
Updated
Oct 8, 2019 - PHP
-
Updated
Apr 1, 2020 - Shell
-
Updated
Apr 3, 2020 - Go
What happened:
screwdriver-chart doesn't work in kubernetes 1.16+.
It contains deployments whose apiVersions are extensions/v1beta1, but this apiVersion for deployment are deprecated and removed in kubernetes 1.16. And the dependencies also has same problem.
https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/
**What you
- Wikipedia
- Wikipedia
Continuous integration apps
Travis CI
Test and deploy with confidence
Cirrus CI
Enjoy unlimited concurrency for fast and secure development cycle
Check Run Reporter
The reporting tool you wish your CI service had built
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
BuildPulse
Automatically track flaky builds. Measure improvement over time. Install in less than a minute. Works with your current CI
Percy
Automated visual review platform
GuardRails
GuardRails provides continuous security feedback for modern development teams
Semaphore
Test and deploy at the push of a button
Buddy
One-click delivery automation for Web Developers
Codefresh
A modern container-based CI/CD platform, easily assemble and run pipelines with high performance
CloudBees CodeShip
Continuous Integration and Delivery. Fast. Customizable. Easy
Google Cloud Build
Build, test, & deploy in a fast, consistent, and secure manner
App Center
Continuously build, test, release, and monitor apps for every platform
Cloud 66 Skycap
Skycap is a container native CI/CD tool

the SSE feed should cache repository permissions to reduce database lookups. There are no documented issues of this being a problem, but this sort of performance improvements seems like low hanging fruit.