ci
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,699 public repositories matching this topic...
The second example in section 1.1 says:
expect(result.approved).to.be.false;
It should be:
expect(result.approved).to.be.true;
(I'm guessing you made it false so you could simulate the error output in the next picture.)
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
Documentation:
https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on
Yaml that duplicates error:
name: Test
on:
push:
branches:
- master
jobs:
build:
runs-on: [self-hosted, windows]
name: Test
steps:
- name: Ensure Docker is running
run: |
docker ps -a
Error received:
Thank you for creating the issue!
- [ x ] Yes, I'm using a binary release within 2 latest major releases. Only such installations are supported.
- [ x ] Yes, I've searched similar issues on GitHub and didn't find any.
- [ x ] Yes, I've included all information below (version, config, etc).
This isn't a bug, just a wishlist item.
Internally golangci-lint checks for a FAIL_ON_WARNINGS e
I've just discovered while grepping through the code that webhook also supports YAML. That's great! :) Could we please have a proper documentation for this? Currently nothing in the documentation points to any kind of yaml support.
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
- Newman Version: 5.0.0
- OS details : Ubuntu 18.04.1 x64
- Newman as a library
- this bug always been there: RunSummary -> run -> timings doesnt has completed
- Expected behaviour: RunSummary -> run -> timings has completed
- Command / script used to run Newman: newman run
- Sample collection, and auxiliary files : any collection with error
- Screenshots : http://
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
I cannot figure out how to use properly danger on circleci 2.0 with workflows
Support I have a linear workflow where I bundle my app / install libraries (build job) and then run the tests in parallel. (I'm taking Ruby/Rspec as an example).
How can I execute Danger to report test failures on all containers ?
Currently if a job fails on circleCI, the dependent jobs are not ran (ie if I
If this is something currently supported, let me know and I can make it more clear in the docs.
The "run" options in a scheme have several options that are unable to be set via XcodeGen. Namely those in the "Options" and "Diagnostics" tabs:

Installing collected packages: pip
Found existing installation: pip 10.0.1
Uninstalling pip-10.0.1:
Successfully uninstalled
reviewdog/reviewdog#405 introduced the -tee option, but there is no mention of the feature in the readme. This would be helpful info for us who are trying to implement/debug this tool
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
Scan with variables
Hi :),
It's possible to scan with variables json or .tf file name ?
Like
{
"region": "eu-central-1",
"environment_id": "demo",
"tags": {
"EnvironmentId": "integration",
"ApplicationName": "demo",
"EnvironmentType": "development",
"Project": "pepito"
},
"rds_instances": [
{
"sg_name": "test-sg",
"kms_key_label": "kms",
"rds_label": "rds",
Is your feature request related to a problem? Please describe.
I'm trying to get two containers to communicate with each other.
I can start up each container and connect to it from the command line using localhost and the bound IP but I'm not clear how to get two containers to talk to each other.
I think this would be the equivalent of "docker network connect" https://stackoverflow.com/qu
-
Updated
Apr 29, 2020 - CMake
The commads push and test include the build step.
The documentation misses to state that. Otherwise it would be a bug and push (as well as test) should not build
-
Updated
May 29, 2020 - Go
-
Updated
May 6, 2020 - Python
-
Updated
Apr 16, 2020 - Rust
-
Updated
May 26, 2020 - Groovy
Show timestamps in the steps console output, e.g.
[13:03:00] starting test...
[13:03:00] test 1 success
[13:03:02] test 2 sucesss
[13:08:16] test 3 timeout
This can help in debugging to give users an idea how long individual steps in the log took.
taskcat test run
To Reproduce
Steps to reproduce the behavior:
- curl -O https://bootstrap.pypa.io/get-pip.py
- python3 get-pip.py --user
- pip install --upgrade pip
- pip3 install taskcat --user
- taskcat --version
- taskcat test run
error: ValidationError Additional properties are not allowed ('parameters' was unexpected)
github url of docs,
-
Updated
May 30, 2020 - Dockerfile
- Wikipedia
- Wikipedia


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.