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,784 public repositories matching this topic...

amwill04 commented Jun 17, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When running batch-write-item and request-items is missing the primary key and/or the sort key for a given table it returns 500 meaning that any sdk will try again before exhausting retries and hiding the true ValidationException error.

Expected Behavior

Return `ValidationExce

good first issue area: integration/aws-cli type: feature aws:dynamodb
kberzinch commented Dec 30, 2021


If there is a global default-get-timeout set on the web node, it is not possible to override that timeout for the implicit get step that is used to pull the image_resource configured on a task.

Steps to reproduce

Start up Concourse with default-get-timeout set very low

$ wget

michelvocks commented Jan 30, 2019

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module:

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.

enhancement help wanted good first issue blocked
ankitm123 commented Jan 5, 2022

Not sure what the error is, but lint passes in the CI and locally even if exported structs dont have comments.
Most probably, it's an issue with the golangci yaml config we use.

Also we use revive instead of golint (which is deprecated), may be some setting in revive needs to be enabled?

If we check the goreport card, we can see the issues:

help wanted good first issue area/quality
augustoproiete commented Nov 21, 2020

Currently when calling the MSBuild alias with an MSBuildSettings, we need to set the target using the WithTarget extension method.

MSBuild("./my-app.sln", new MSBuildSettings
    Configuration = "Release",
    ToolVersion = MSBuildToolVersion.VS2019,
}.WithTarget("Build")); // <<<###

It would be nice if we could use a property, with a string, which would make it more na


Continuous integration apps


Automated visual review platform

App Center

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


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

Cirrus CI

Enjoy unlimited concurrency for fast and secure development cycle


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

Check Run Reporter

See your test and style results without leaving GitHub. Works with any CI service. Supports JUnit, Checkstyle, and more

Mend Bolt

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


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


Find accessibility issues in your pull requests


ABAP quality assurance and static analysis


Automated code reviews

See more Continuous integration apps