-
Updated
Jul 9, 2020 - Java
pipelines-as-code
Here are 43 public repositories matching this topic...
Proposed by @headcrabmeat in #50
Discussions in issues are ok but when the issue is closed it is not easily available to newcomers.
Write how-to pages resuming the solutions described in issues and troubleshooting for common issues and misunderstandings.
Show timestamps in the steps console output, e.g.
[13:03:00] starting test...
[13:03:00] test 1 success
[13:03:02] test 2 sucesss
[13:08:16] test 3 timeout
This can help in debugging to give users an idea how long individual steps in the log took.
I find that there are two ways to fetch github token in the pipeline library
withCredentialsto lookupcd-githubsee: https://github.com/fabric8io/fabric8-pipeline-library/blob/0bff0f50a2af9a0dcc4d2c4abb28d1eafcbfdfb9/vars/mavenCI.groovy#L14Fabric8Command.getGitHubTokenwhich uses a different mechanism. See: https://github.com/fabric8io/fabric8-pipeline-library/blob/0bff0f50a2af9a0
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
-
Updated
May 2, 2017 - Groovy
-
Updated
Apr 15, 2020 - Java
Improve docs
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.
-
Updated
Jul 6, 2017 - Groovy
-
Updated
Feb 2, 2017 - Groovy
-
Updated
Aug 22, 2017 - Groovy
-
Updated
Dec 27, 2018 - Python
-
Updated
Jul 6, 2020 - JavaScript
-
Updated
Oct 25, 2017 - JavaScript
-
Updated
Apr 18, 2020 - Go
-
Updated
Apr 30, 2019 - Python
-
Updated
Jun 23, 2020 - Groovy
-
Updated
Sep 27, 2018 - C#
-
Updated
May 15, 2018 - Scala
-
Updated
Jul 30, 2018 - Shell
-
Updated
Sep 22, 2019 - Python
-
Updated
Aug 11, 2019
-
Updated
Jul 3, 2020 - Go
-
Updated
Jul 9, 2020 - Python
-
Updated
May 10, 2018 - Scala
-
Updated
Sep 8, 2019 - Python
-
Updated
Jun 4, 2020 - Apex
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.
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."
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
nameproperty onNode.The current auto-generated name for a node looks something like this:
func_name(inputs) -> outputs. (see implementation of__str__method on theNodeclass)This is