Skip to content
#

continuous-delivery

Here are 717 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
jx
mcabrito
mcabrito commented Apr 15, 2020

Summary

I’m trying to use a Chart Repository by external Nexus, but I’d a problem in pipeline when I’m using the command:

jx step helm release

When this command do the upload chart file, my $CHART_REPOSITORY is changing and including the /api/charts

+ jx step helm release --verbose
DEBUG: Using helmBinary helm with feature flag: template-mode
DEBUG: Initialising Helm 'i
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

werf
lastbackend
jrivard
jrivard commented Feb 28, 2020

New feature: Prevent header timestamp in git.properties to allow for reproducible builds.

The git.properties file output includes the current time as a timestamp in a commented header. This prevents reproducible builds because each build will include a different timestamp.

A feature fix would prevent this timestamp from being written as a comment header.

Note1: For reproducible builds th

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

jithine
jithine commented Apr 7, 2020

What happened:
Shared commands expire due to a side effect of using catbox-s3 for uploading to AWS. Cluster admins must set an expiry time and users suffer if they don't have period builds.

What you expected to happen:
This life cycle for shared command is arbitrary and Screwdriver should not be in the business of policing how long should command owners rebuild the commands and forc

superfigge
superfigge commented Aug 31, 2017

Hi, thanks for a great plugin. We wonder, instead of ending up in the Jenkins job page when clicking jobname status in a box, we want to show another page on the Jenkins machine. As it is now, we first have to click in the box (your nice plugin) and then again on a link. That link shows a deeper result of the job with test results.
So we just want to skip one click and go directly to that result

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

You can’t perform that action at this time.