-
Updated
May 22, 2022 - Python
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,742 public repositories matching this topic...
-
Updated
May 19, 2022 - Go
-
Updated
May 23, 2022 - Java
-
Updated
Jan 27, 2020 - JavaScript
-
Updated
May 23, 2022 - Go
-
Updated
May 21, 2022 - Java
-
Updated
May 22, 2022 - Java
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: https://goreportcard.com/report/github.com/jenkins
-
Updated
May 20, 2022 - Go
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
-
Updated
May 20, 2022 - Go
-
Updated
May 22, 2022 - TypeScript
-
Updated
May 19, 2022 - TypeScript
Since drf_yasg2 is not being maintained anymore, we are left with two options:
- Move back to drf_yasg, we can do that, but it does not support Openapi 3.0, so really we are left with one option to use https://github.com/tfranzel/drf-spectacular
-
Updated
May 20, 2022 - Elixir
-
Updated
Oct 30, 2020 - PHP
-
Updated
May 17, 2022 - CMake
https://github.com/google/starlark-go/blob/master/doc/spec.md
It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.
Like in #137 we should provide build context information.
-
Updated
May 21, 2022 - Rust
-
Updated
May 16, 2022 - Go
-
Updated
May 16, 2022 - Shell
-
Updated
Apr 10, 2022 - Java
What happened:
Press the create pipeline button in the screwdriver header and the modal will be expanded.

<img width="615" alt="スクリーンショット 2021-10-05 9 21 05" src="https://user-images.githubusercontent.com/17828065/135941963-0309606d-6c26-44e8-84c5-2c0e3
-
Updated
May 21, 2022
-
Updated
Apr 29, 2022 - TypeScript
Kudu plugin
-
Updated
Mar 9, 2022 - Python
-
Updated
May 16, 2022 - Groovy
-
Updated
May 16, 2022 - Java
- Wikipedia
- Wikipedia
Continuous integration apps
WhiteSource Bolt
Detect open source vulnerabilities in real time with suggested fixes for quick remediation
Travis CI
Test and deploy with confidence
GuardRails
GuardRails provides continuous security feedback for modern development teams
Cloud 66 Skycap
Skycap is a container native CI/CD tool
Buddy
One-click delivery automation for Web Developers
Percy
Automated visual review platform
App Center
Continuously build, test, release, and monitor apps for every platform
AppVeyor
Cloud service for building, testing and deploying Windows apps
Google Cloud Build
Build, test, & deploy in a fast, consistent, and secure manner
Semaphore
Test and deploy at the push of a button
Testspace.com
Test Management software for DevOps, including CI Results Dashboard, Manual Test Case Management, and Exploratory testing
Localazy
Manage your i18n and localization needs from one place with Localazy ®
Hound
Automated code reviews
Azure Pipelines
Continuously build, test, and deploy to any platform and cloud
CircleCI
Automatically build, test, and deploy your project in minutes
Summary
If there is a global
default-get-timeoutset on the web node, it is not possible to override that timeout for the implicitgetstep that is used to pull theimage_resourceconfigured on a task.Steps to reproduce
Start up Concourse with
default-get-timeoutset very low