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,132 public repositories matching this topic...
-
Updated
Jun 26, 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
Installation method "Method
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
Finish Guides setup
FutureStudios via @marcuspoehls has given us permission to move/adapt their Strider blog post series into our website. This has been started here: https://github.com/Strider-CD/strider/tree/master/docs but still needs more work:
- Add all sections to nav (see README
For context: here's an excerpt from the buildbot source that is responsible for querying a secret from the hashicorp vault:
ret = json.get('data', {}).get('data', {}).get('value')
When reading vault documentation, the version data section is not emphasized leading to believe this is a typical key value store i.o.w. one has to land on the specific section covering the kv secrets e
Summary
I’m trying to use a Chart Repository by external Nexus, but I’d a problem in pipeline when I’m using the command:
jx step helm release
When this command do the upload chart file, my $CHART_REPOSITORY is changing and including the /api/charts
+ jx step helm release --verbose
DEBUG: Using helmBinary helm with feature flag: template-mode
DEBUG: Initialising Helm 'i
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
On the basis of Review Russian documentation #1963
- Main
- Releases
- README
- Documentation Overview
- Configuration / Introduction
- Configuration / Dockerfile image
- Configuration / Stapel Image / Naming
- Configuration / Stapel Image / Base Image
- Configuration / Stapel Image / Docker direct
Per the tox documentation is mentions that the parallel_show_output setting is a global [tox] setting however this doesn't seem to be the case, i.e., if one's tox.ini file is of the form:
[tox]
parallel_show_output = true
then running tox --parallel auto does not show any output.
According to t
-
Updated
Jun 6, 2020 - Go
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
Jun 19, 2020 - CMake
-
Updated
May 31, 2020 - JavaScript
-
Updated
Dec 31, 2019 - PHP
-
Updated
Apr 1, 2020 - Shell
-
Updated
Oct 8, 2019 - PHP
-
Updated
Jun 24, 2020 - Go
- 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
Cirrus CI
Enjoy unlimited concurrency for fast and secure development cycle
Semaphore
Test and deploy at the push of a button
Travis CI
Test and deploy with confidence
BuildPulse
Stop losing time to flaky tests
Cloud 66 for Rails
Build, deploy, and maintain your Rails apps on any cloud or server
AppVeyor
Cloud service for building, testing and deploying Windows apps
Azure Pipelines
Continuously build, test, and deploy to any platform and cloud
WhiteSource Bolt
Detect open source vulnerabilities in real time with suggested fixes for quick remediation
CloudBees CodeShip
Continuous Integration and Delivery. Fast. Customizable. Easy
AccessLint
Find accessibility issues in your pull requests
CircleCI
Automatically build, test, and deploy your project in minutes
Percy
Automated visual review platform
App Center
Continuously build, test, release, and monitor apps for every platform
Check Run Reporter
Your CI service tells you that tests failed; Check Run Reporter tells you *which* tests failed

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.