-
Updated
Mar 10, 2022 - Go
continuous-delivery
Here are 960 public repositories matching this topic...
-
Updated
Mar 10, 2022 - Java
-
Updated
Mar 10, 2022 - Go
-
Updated
Feb 16, 2022 - Shell
-
Updated
Mar 10, 2022 - Go
-
Updated
Feb 25, 2022 - Go
-
Updated
Mar 10, 2022 - Java
-
Updated
Mar 10, 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_GET
Is 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}
We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome
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.
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
Mar 10, 2022 - Go
-
Updated
Feb 7, 2022 - TypeScript
-
Updated
Mar 5, 2022 - Go
I noticed that when CML produces the reports (as per in cml-send-comment --update --pr report.md
) such reports are shown in the PR conversation as belonging to a certain user rather than GitHub actions reports. Is this intended behaviour or is there a setting/flag where we can choose which user to assign to the comments reports?
I haven't figured out how such user is chosen, I suspect it is t
Describe the bug
https://fluxcd.io/docs/use-cases/aws-codecommit/
Flux Create Source:
Failed to retrieve list of SSH authentication methods
► applying secret with repository credentials
► applying GitRepository source
◎ waiting for GitRepository source reconciliation
✗ unable to clone: Failed to retrieve list of SSH auth
-
Updated
Mar 10, 2022 - TypeScript
When we show data for a metric, we currently don't include the current day's worth of data. For users just getting set up, they may only have events from today, and want to test out if the query is working, and by excluding events from 'today', they can't see results.
TODO:
- In
packages/back-end/src/services/experiments.ts
on line329
, instead of using the current date as the value
-
Updated
Feb 26, 2022 - Go
-
Updated
Oct 8, 2020
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
Aug 7, 2021 - Go
-
Updated
Jan 5, 2022 - Shell
-
Updated
Mar 4, 2022 - Ruby
-
Updated
Aug 1, 2021 - Java
Use case
As a user, I would like to see the service name and the timestamp also on the details page of a sequence execution.
Details
- The service name, e.g.
of carts
is inserted between the sequence name and status. ->delivery of carts succeeded
- The start time
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
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."
Summary
The Argo CD core mode should allow the user to set a permanent path to a K8s client configuration file, instead of either using
~/.kube/config
per default or having to specify--kubeconfig
for each command.Motivation
Some K8s distributions by default install a Kubernetes client CLI (
kubectl
) which uses a custom path for its configuration. For example, K3s uses `/etc/ran