The Wayback Machine - https://web.archive.org/web/20210730125741/https://github.com/topics/continuous-delivery
Skip to content
#

continuous-delivery

Here are 873 public repositories matching this topic...

jdomag
jdomag commented Jul 28, 2021

Summary

Add additional parameter to command argocd app rollback [APP] that will perform rollback to previous release. As for now we need to find out previous revision ID from the history and then issue the rollback command.

Motivation

In our CICD we deploy the app with argocd app sync and then run the tests of the application. When the tests fail for any reason, in the next step o

jx
msvticket
msvticket commented Nov 2, 2018

Summary

When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.

This means that when new versions of the application are created the unchanged dependencies can't be reused.

It would be a great enhancement if the application code where p

unleash
ivarconr
ivarconr commented Jun 22, 2021

Hi all 👋

We already released the addon-framework where we want to provide out-of the box integrations with third party tools. It would be super helpful if someone familiar with New Relic could assist on building the New Relic integration. The idea is to inform New Relic about changes via [New Relic Custom events](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-apis/introduct

flux2
keptn
christian-kreuzberger-dtx
christian-kreuzberger-dtx commented Jun 22, 2021

With Keptn 0.8.4, when executing keptn auth without parameters, the following deprecation warning is shown:

$ keptn auth
W0622 09:12:38.907621  114793 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

This is caused by the function GetKeptnEndpointFromIngress which is implemented in kubernetes-utils:
http

timbaileyjones
timbaileyjones commented Aug 12, 2019

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-7c6a9c22d264

This error does not occur with the `-f

Improve this page

Add a description, image, and links to the continuous-delivery topic page so that developers can more easily learn about it.

Curate this topic

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."

Learn more