continuous-delivery

So much emphasis on the buttons is not needed.

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

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/

Environment

Liquibase Version: 4.6.1

Liquibase Integration & Version: 4.6.1

Liquibase Extension(s) & Version: 4.6.1

Database Vendor & Version: MySQL8.0.27

Operating System Type & Version: MacOS Monterey 12.0.1

Descript

Docker volumes are supported in GH via yaml definitions. We should tell this instead of just throwing an unsupported error.

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.

Task

When triggering an evaluation sequence, the timeframe select allows specifying a timeframe in hh : mm : ss : ms : µs - please see:

Please remove ms : µs from the date format since this is too specific.

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

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.