Skip to content
#

continuous-deployment

Here are 595 public repositories matching this topic...

GaneshSPatil
GaneshSPatil commented Mar 2, 2020

In order to make the UI/UX consistent across all pages of GoCD, GoCD is rebuilding the Pipeline Config Edit Page (changing into a Single Page App).

As part of this page rewrite, following changes needs to be done on the plugins:

Breaking Changes

Task Plugins View:

GoCD Task Plugins implements Get Task View extension call, which

flux
ChillarAnand
ChillarAnand commented Apr 1, 2020

When deploying hasura example - mono repo with k8s, git push is failing with

$ git push minikube master
default-myremote@172.17.0.2: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

When creating myremote, I have used ~/.ssh/id_ras.pub and it wasn't changed. Not sure wh

vjpie2002
vjpie2002 commented Apr 30, 2020

Summary

Add field/label "LIVE For:" to show how much time the Revision was LIVE. Currently when a user clicks on the "History and Rollback", it shows all past Revisions and when it was triggered and completed and also displays the amount of time for which that Revision was LIVE. But it does not mention what these timings/durations are for (as shown in the attached screenshot where it shows dur

liquibot
liquibot commented Apr 27, 2020

Context

As a reader of online docs, it is not clear when doing diff which database if the "reference" against which a "target" is compared. This makes it tough!

As a reader of online docs, hoping to do a diffchangelog, it is not clear how to set the url and referenceURL parameters if i want to apply the generated diffchangelog against one db to migrate it up to the other. Which is which?

R

mpdehaan
mpdehaan commented Dec 6, 2018

For easier sudo configuration with the sudo isolation plugin, we really want the vespene user to be in sudoers.

This is not something that the setup automation currently sets up.

We should at least add a note in the docs for this

agola
KevinGrandon
KevinGrandon commented Mar 19, 2020

We leverage a custom Buildkite plugin with cleanup behavior in a pre-exit hook. When a task times out from timeout_in_minutes, the pre_exit hook is never called.

Current behavior:
The task times out, and the plugins pre_exit hook is never called.

Expected behavior:
The plugins pre_exit hook is called.

brightsparc
brightsparc commented Mar 14, 2018

The documentation indicates

If you discover bugs while in Production, you can revert to previous application version by clicking and approving the change again.

Does this imply you need to revert code and re-commit to have the pipeline build again, or is there a way to simply flip the blue/green deployments back to the previous version. The later would be preferable. In this case would a

Improve this page

Add a description, image, and links to the continuous-deployment 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-deployment topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.