-
Updated
May 16, 2022 - Go
continuous-delivery
Here are 978 public repositories matching this topic...
-
Updated
May 17, 2022 - Java
-
Updated
May 17, 2022 - Go
-
Updated
Feb 16, 2022 - Shell
-
Updated
May 17, 2022 - Go
-
Updated
May 5, 2022 - Go
-
Updated
May 16, 2022 - Java
-
Updated
May 17, 2022 - Java
Summary
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 https://concourse-ci.org/docker-compose.yml
$ echo " CONCOURSE_DEFAULT_GETIs it possible to add a check if unleash variable is indeed a json, and disable the option of saving it unless it is?
For example, created a variable for a toggle and selected type to be a json, but I've inserted a string instead of a json and was able to save and pull the value.
{'name': 'test', 'payload': {'type': 'json', 'value': 'not a json'}, 'weightType': 'variable', 'enabled': True}
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 17, 2022 - Go
In #2649, all our dependencies except this module in the Azure related end-to-end tests were updated, as it contains a breaking change.
tfinstall has been removed and needs to be replaced with https://github.com/hashicorp/hc-install. We call it exactly one time in [azure_test.go](https://github.com/
-
Updated
May 17, 2022 - Go
When there are not enough results, we tell the user that the experiment just started, so come back later. When the experiment dates are set to a future time, this language doesn't fit very well. We should adjust the language to take this future state into account when figuring out the message.
<img width="875" alt="CleanShot 2022-04-10 at 21 23 22@2x" src="https://user-images.githubusercontent
Is your feature request related to a problem? Please describe.
OpenTracing teamed up with OpenCensus to create OpenTelemetry. Tracing support is already stable.
Describe the solution you'd like
Replace OpenTracing with OpenTelemetry tracing. Alternatively, add OpenTelemetry to keep backwards compatibility.
-
Updated
Jan 5, 2022 - Shell
-
Updated
May 16, 2022 - Ruby
Is your enhancement proposal related to a problem? Please describe.
For now, there are no connectivity test for jira integration. This will cause problem if the user is integrating with the wrong credential.
Describe the solution you'd like
Add a connectivity test API for jira integration which will take the integration info as input and returns if the API call to jira can be made suc
I was thinking that we could extract the eslint config file into his own module so that we can easily reuse this across any OC related repo in the form of eslint extends.
This because we now have the @opencomponents organization and quite few repos, and i
-
Updated
Oct 30, 2020 - PHP
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 16, 2022 - Go
While testing another PR, I found that mu pipeline logs command displays information from the pipelines, but also shows this error:
$ mu pipeline logs
[... normal, expected output ...]
func1 ▶ ERROR ResourceNotFoundException: The specified log group does not exist.
status code: 400, request id: f7260741-7f69-4772-b4cc-7c6a9c22d264This error does not occur with the `-f
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
Sep 13, 2020 - Go
-
Updated
May 17, 2022 - Python
Improve this page
Add a description, image, and links to the continuous-delivery topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the continuous-delivery topic, visit your repo's landing page and select "manage topics."

So much emphasis on the buttons is not needed.