Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Update trigger topic#547

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
NimRegev merged 2 commits intomasterfromclassic-skip-trigger
Jan 24, 2023
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions_docs/configure-ci-cd-pipeline/triggers.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -9,9 +9,9 @@ toc: true
---


To create an effective CI/CD process, it should be possible to triggeraCodefreshpipeline execution not only on code repository events (like `push` or `PR`), but also on any "interesting" CD-related event, coming from some external system.
To create an effective CI/CD process, it should be possible to trigger Codefreshpipelines not only on code repository events (like `push` or `PR`), but also on any "interesting" CD-related event, coming from some external system.

Codefresh not only allows you to define different pipelines on a single project butitalso offers you the capability to trigger them with completely separate mechanisms.
Codefresh not only allows you to define different pipelines on a single project but also offers you the capability to trigger them with completely separate mechanisms. You can even skip triggering a pipeline by including predefined flags in the commit message.


## Codefresh Trigger Types
Expand DownExpand Up@@ -95,6 +95,8 @@ For more information see:
You can easily disable a trigger manually if you don't want to be active anymore.
On the triggers tab click the gear icon on the top right (*Open advanced options*).



{% include image.html
lightbox="true"
file="/images/pipeline/triggers/enable-triggers.png"
Expand All@@ -108,6 +110,9 @@ max-width="70%"
Then click the toggle switch on each trigger that you want to enable/disable. You can later enable the same trigger again
by clicking the same switch.

>For Git triggers, you can also skip triggering the pipeline without disabling the trigger by adding a predefined string to the commit message. See [Skip triggering pipeline on commit]({{site.baseurl}}/docs/configure-ci-cd-pipeline/triggers/git-triggers/#skip-triggering-pipeline-on-commit).


## What to read next

* [Creating pipelines]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/)
Expand Down
20 changes: 15 additions & 5 deletions_docs/configure-ci-cd-pipeline/triggers/git-triggers.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -46,14 +46,23 @@ The Git Trigger is comprised of the following settings:
* *Trigger Name* - a freetext trigger name (required).
* *Description* - a freetext description (optional).
* *Repository* - you can select any repository even something different than the one that is used for the code checkout.
* *Commit Checkbox* - if enabled will trigger this pipeline for any commit.
* *PR Checkboxes* - various checkboxes for filtering the Pull request event.
* *Trigger by* - Commit and PR trigger options. Push Commit when enabled triggers this pipeline for any commit.
The commit checkbox (by default it is enabled) means that this pipeline will run for *any* commit as long as its source branch matches the naming scheme. This includes commits on pull requests.
The PR checkboxes mean that this pipeline will run only on the respective events that happen on a Pull Request. You can select multiple checkboxes to further fine-tune the exact event. If you are interested in all events, select the checkbox *Any Pull Request event*.

Thecommit checkbox (by default it is enabled) means that this pipeline will runfor*any* commit as long as its source branch matches the naming scheme. This includes commits on pull requests.
>Theindividual Pull request checkboxes are available onlyforGitHub repositories.

The PR checkboxes mean that this pipeline will run only on the respective events that happen on a Pull Request. You can select multiple checkboxes to further fine-tune the exact event. If you are interested in all events, select the checkbox *Any Pull Request event*.
## Skip triggering pipeline on commit
The default behavior triggers the pipeline on a commit action.
Override the default behavior by adding any one of the predefined strings anywhere in the commit message.

>The individual Pull request checkboxes are available only for GitHub repositories.
>Remember to include the opening and closing parentheses when adding the strings.

* `[skip ci]`
* `[ci skip]`
* `[no ci]`
* `[skip codefresh]`
* `[codefresh skip]`

## Configure Filter Settings

Expand All@@ -71,6 +80,7 @@ max-width="50%"
* *Pull Request Target* branch - this is a regular expression and will trigger only when a Pull request is created against any branch that matches it.
* *Modified Files* - allows you to constrain the build and trigger it only if the modified files from the commit match this [glob expression](https://en.wikipedia.org/wiki/Glob_(programming)).


### Pull Request Target Branch and Branch

The Pull Request Target Branch field allows you to trigger this pipeline only when the target of a Pull Request (i.e. where the pr is going to be merged at) matches the
Expand Down
[8]ページ先頭
©2009-2025 Movatter.jp