Skip to content
#

pipelines-as-code

Here are 43 public repositories matching this topic...

kedro
lorenabalan
lorenabalan commented Feb 26, 2020

Description & context

Users can specify names for their nodes to identify them more easily. When a name is not explicitly specified, Kedro auto-generates a default name. You can see this in the name property on Node.
The current auto-generated name for a node looks something like this: func_name(inputs) -> outputs. (see implementation of __str__ method on the Node class)

This is

FredrikWendt
FredrikWendt commented Oct 7, 2017

Given a gocd server
And a pipeline A is added in group Group1
When a pipeline B is added in group group1
Then Group1 should contain pipelines: A, B

However, right now, when pipeline B is read by the plugin, the error presented in GoCD server "Error" section (the red button in top right corner), shows:

`2+ errors :: Group with name 'infrastructure' already exists;; Group with name 'infrast

atharvai
atharvai commented Oct 23, 2019

The readme isn't enough. There are many properties that show single examples but not any reference values or what is expected. forexample, for auto deleting artifacts there's a single example shows but this page shows various options: https://docs.gocd.org/current/configuration/delete_artifacts.html . the README for this plugin does not specify all these options for even the json properties are.

Improve this page

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

Learn more

You can’t perform that action at this time.