continuous-delivery

The (still undocumented) feature is great for our purpose, but can you add the same functionality to the post-update hook (in the same manner, of course)?

I have added a script to the post-update to check the database-version. If they not match, the script returns exit 1. It would be great if the post-update hook could log a error- or warning-message, so the slack-notification gets a message (l

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}

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

Is your feature request related to a problem? Please describe.

In KubeVela v1.4, we have authentication and authorization based on Kubernetes Impersonation and RBAC mechanism. The impersonation will be triggered when application wants to get/create/update/delete resources in clusters, wh

We need to add a new arg (string array) to flux create source git and flux create source bucket that populates the ignore spec filed, each arg would add a new line to the ignore value e.g.:

flux create source git podinfo \
--url=https://github.com/stefanprodan/podinfo \
--branch=master \
--ignore-path=".git/" \
--ignore-path=".github/" \
--export

The above command will

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

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

Currently when you sort the list of features (or experiments) it only kept for that session and not saved. We would like to persist this sort state to local storage.

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.

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

User Story

As a user, I'd like to know on which day a sequence/task was executed.

Technical Details

In the sequence screen, stages have below them the timestamp of when a sequence was executed for that stage. Similarly, next to the task a timestamp is shown. The format is always HH:MM.

In the best-case, it's usually clear that the sequence was executed within the same day (but you wou

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.