This repository was archived by the owner on Jul 10, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 393
Update index.md #1957
Open
stephly07
wants to merge
7
commits into
spinnaker:master
Choose a base branch
from
stephly07:patch-12
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update index.md #1957
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
d120832
Update index.md
stephly07 8824daf
Merge branch 'master' into patch-12
dorbin e198079
Merge branch 'master' into patch-12
dorbin 1e6e379
Merge branch 'master' into patch-12
dorbin fb59f17
Merge branch 'master' into patch-12
dorbin 15edab8
Merge branch 'master' into patch-12
dorbin 01ce98b
Merge branch 'master' into patch-12
317brian File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,11 +9,11 @@ sidebar: | |
|
|
||
| In order to programatically trigger pipelines you can send a `POST` call to | ||
| Spinnaker at a preconfigured endpoint. You can use this to trigger pipelines | ||
| when a CI job finishes, from the command line, or from a third-party system. | ||
| The payload, whether it is one you are able to write, or it is provided for | ||
| when a CI job finishes, from the command line or from a third-party system. | ||
| The payload, whether it's one you're able to write, or it's provided for | ||
| you, will be available in the Pipeline's execution. | ||
|
|
||
| > __☞ Note__: You can configure multiple pipelines to trigger off of a single | ||
| > __Note:__ You can configure multiple pipelines to trigger off of a single | ||
| > webhook. | ||
|
|
||
| If you're triggering from a *GitHub* webhook, see the instructions | ||
|
|
@@ -44,8 +44,9 @@ endpoint depends on how you've configured your [Spinnaker | |
| endpoints](/setup/security) -- if you're running on a different endpoint, for | ||
| example `https://api.spinnaker-prod.net`, that'll be shown instead. | ||
|
|
||
| Keeping track of that endpoint as `$ENDPOINT` (it will depend on where | ||
| Spinnaker is installed), save that pipeline, and run: | ||
| Keeping track of that endpoint as `$ENDPOINT` will depend on where | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe just: Or something like that?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These would work better as imperative verbs in numbered steps, but you'd have to do that to the entire article. |
||
| Spinnaker is installed. | ||
| Save that pipeline and run: | ||
|
|
||
| ```bash | ||
| curl $ENDPOINT -X POST -H "content-type: application/json" -d "{ }" | ||
|
|
@@ -58,7 +59,7 @@ arrives, you can provide __Payload Constraints__ in the trigger. These are | |
| key/value pairs where the key must be found in the incoming payload, and the | ||
| value must match using regex. | ||
|
|
||
| For example, if we had configured: | ||
| For example, if we configured: | ||
|
|
||
| {% | ||
| include | ||
|
|
@@ -100,7 +101,7 @@ same configuration screen as the webhook trigger: | |
| [pipeline expressions guide](/guides/user/pipeline-expressions)." | ||
| %} | ||
|
|
||
| If you were to manually execute this pipeline, you would be prompted with the | ||
| If you manually executed this pipeline, you would be prompted with the | ||
| following dialogue: | ||
|
|
||
| {% | ||
|
|
@@ -121,7 +122,7 @@ following payload for example: | |
| } | ||
| ``` | ||
|
|
||
| > __☞ Note__: If you select the __Required__ checkbox for a parameter without | ||
| > __Note:__ If you select the __Required__ checkbox for a parameter without | ||
| > providing a default, the pipeline does not trigger if a parameter is not | ||
| > present. The difference between this and the preconditions covered earlier is | ||
| > that when a precondition isn't met, Spinnaker doesn't even try to run the | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.