Commit1f42a99

Vladimir Mechkauskas

committed

-- removed comma

1 parent168cccc commit1f42a99Copy full SHA for 1f42a99

File tree

-8

lines changed

-8

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`---`
`2`	`2`	`title:"Introduction to Codefresh pipelines"`
`3`		`-description:"",`
	`3`	`+description:""`
`4`	`4`	`group:configure-ci-cd-pipeline`
`5`	`5`	`redirect_from:`
`6`	`6`	`-/docs/introduction-to-codefresh-pipelines/`
`@@ -71,4 +71,4 @@ Visit [DockerHub Trigger]({{site.baseurl}}/docs/pipeline-triggers/configure-dock`
`71`	`71`
`72`	`72`	It is possible to trigger Codefresh pipeline execution periodically, using timer, and`cron` expression.
`73`	`73`
`74`		`-Visit[Cron Trigger]({{site.baseurl}}/docs/pipeline-triggers/configure-cron-trigger/) page for more details.`
	`74`	`+Visit[Cron Trigger]({{site.baseurl}}/docs/pipeline-triggers/configure-cron-trigger/) page for more details.`

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`---`
`2`	`2`	`title:"Cron Trigger"`
`3`		`-description:"",`
	`3`	`+description:""`
`4`	`4`	`group:pipeline-triggers`
`5`	`5`	`redirect_from:`
`6`	`6`	`-/docs/configure-cron-trigger/`
`@@ -48,4 +48,4 @@ From now on, every 20 minutes Codefresh will trigger pipeline execution for 2 pi`
`48`	`48`	The following variables will be available for any Codefresh pipeline linked to a`cron``trigger-event`.
`49`	`49`
`50`	`50`	-`EVENT_MESSAGE` - free text message (specified during creation)
`51`		--`EVENT_TIMESTAMP` - event timestamp in RFC 3339 format
	`51`	+-`EVENT_TIMESTAMP` - event timestamp in RFC 3339 format

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`---`
`2`	`2`	`title:"DockerHub Trigger"`
`3`		`-description:"",`
	`3`	`+description:""`
`4`	`4`	`group:pipeline-triggers`
`5`	`5`	`redirect_from:`
`6`	`6`	`-/docs/configure-dockerhub-trigger/`
`@@ -87,4 +87,4 @@ The following variables will be available for any Codefresh pipeline linked to a`
`87`	`87`	-`EVENT_TAG`- Docker image tag
`88`	`88`	-`EVENT_PUSHER`- user who pushed this Docker image
`89`	`89`	-`EVENT_PUSHED_AT`- timestamp for push event
`90`		--`EVENT_PAYLOAD`- original DockerHub Webhook JSON payload
	`90`	+-`EVENT_PAYLOAD`- original DockerHub Webhook JSON payload

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`---`
`2`	`2`	`title:"Pipeline Triggers"`
`3`		`-description:"",`
	`3`	`+description:""`
`4`	`4`	`group:pipeline-triggers`
`5`	`5`	`redirect_from:`
`6`	`6`	`-/docs/pipeline-triggers/`
@@ -63,4 +63,4 @@ Every triggered pipeline get an `event` payload as environment variables with `E
`63`	`63`
`64`	`64`	There are two types of payload. Most interesting event properties are passed as individual variables (depending on`trigger-type`) and the original event payload is also passed inside the`EVENT_PAYLOAD` variable.
`65`	`65`
`66`		-Any step, within triggered Codefresh pipeline, has access to above`EVENT_*` variables.
	`66`	+Any step, within triggered Codefresh pipeline, has access to above`EVENT_*` variables.

Comments

(0)