From 03d0c57896fabd260ee250835a1c63b594321d5f Mon Sep 17 00:00:00 2001 From: Daniel Peach Date: Mon, 16 Oct 2017 14:31:10 -0400 Subject: [PATCH] fix(artifact): s/ul/ol --- app/scripts/modules/core/src/help/help.contents.ts | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/app/scripts/modules/core/src/help/help.contents.ts b/app/scripts/modules/core/src/help/help.contents.ts index d48eb6fad33..b1fa0c4d7ee 100644 --- a/app/scripts/modules/core/src/help/help.contents.ts +++ b/app/scripts/modules/core/src/help/help.contents.ts @@ -91,11 +91,11 @@ module(HELP_CONTENTS, [])

Regex is accepted, so you could for example match on a filepath like so name = .*\\.yaml to match all incoming YAML files.

`, 'pipeline.config.expectedArtifact.ifMissing': `

If no artifact was supplied by your trigger to match against this expected artifact, you have a few options: -

+
    +
  1. Attempt to match against an artifact in the prior pipeline execution's context. This ensures that you will always be using the most recently supplied artifact to this pipeline, and is generally a safe choice.
    2. +
  2. If option 1 fails, or isn't specified, you can provide a default artifact with all required fields specified to use instead.
    3. +
  3. Fail the pipeline if options 1 or 2 fail or aren't selected.
    4. +

`, 'pipeline.config.expectedArtifact.defaultArtifact': `

If your artifact either wasn't supplied from a trigger, or it wasn't found in a prior execution, the artifact specified below will end up in your pipeline's execution context.

`,