You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Coveralls requires a[script](https://github.com/nickmerwin/node-coveralls){:target="\_blank"} that takes standard input and sends it to coveralls.io to report your code coverage. Depending on the framework that you are using, you will have to add a different script to your application.
44
44
45
-
Any coverage reports can be forwarded that are within a[lcov data format](http://ltp.sourceforge.net/coverage/lcov/geninfo.1.php){:target="\_blank"} (including[mocha's LCOV reporter](https://www.npmjs.com/package/mocha-lcov-reporter){:target="\_blank"}). For this, we are going to set-up a “bin” folder, and within the folder a coveralls.js file that contains the following content:
45
+
Any coverage reports can be forwarded that are within a[lcov data format](https://github.com/linux-test-project/lcov){:target="\_blank"} (including[mocha's LCOV reporter](https://www.npmjs.com/package/mocha-lcov-reporter){:target="\_blank"}). For this, we are going to set-up a “bin” folder, and within the folder a coveralls.js file that contains the following content:
You can check out code from one or more repositories in any pipeline phase. Codefresh includes[built-in GIT integration]({{site.baseurl}}/docs/integrations/git-providers/) with all the popular GIT providers and can be used with[git-clone]({{site.baseurl}}/docs/pipelines/steps/git-clone/) steps.
45
46
46
47
-[Cloning Git repositories using the built-in integration]({{site.baseurl}}/docs/example-catalog/ci-examples/git-checkout/)
47
48
-[Cloning Git repositories using manual Git commands]({{site.baseurl}}/docs/example-catalog/ci-examples/git-checkout-custom/)
48
-
-[Checking out from Subversion, Perforce, Mercurial, etc]({{site.baseurl}}/docs/example-catalog/ci-examples/non-git-checkout/)
49
+
-[Checking out from Subversion, Perforce, Mercurial, etc]({{site.baseurl}}/docs/example-catalog/ci-examples/non-git-checkout/)
49
50
50
51
###Build/push examples
51
52
@@ -105,7 +106,6 @@ Codefresh can automatically export secret key-value pairs using the Vault plugin
105
106
106
107
Codefresh can automatically launch environments (powered by Docker swarm) to[preview a Pull Request or feature]({{site.baseurl}}/docs/quick-start/ci-quickstart/on-demand-environments/). The definition of the environment can come from an[existing composition]({{site.baseurl}}/docs/testing/create-composition/), a docker-compose file or an inline YAML. Preview environments can be launched manually or[automatically from pipelines]({{site.baseurl}}/docs/pipelines/steps/launch-composition/).
Copy file name to clipboardExpand all lines: _docs/pipelines/triggers/git-triggers.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -182,7 +182,7 @@ The *modified files* field is a very powerful Codefresh feature that allows you
182
182
files affected by a commit are in a specific folder (or match a specific naming pattern). This means that
183
183
you can have a big GIT repository with multiple projects and build only the parts that actually change.
184
184
185
-
>Currently the field*modified files* is available only for GitHub, GitLab, Azure DevOps and[Bitbucket Server and Data Center](https://confluence.atlassian.com/bitbucketserver/add-a-post-service-webhook-776640367.html){:target="\_blank"} repositories, since they are the only GIT providers
185
+
>Currently the field*modified files* is available only for GitHub, GitLab, Azure DevOps and[Bitbucket Server and Data Center](https://confluence.atlassian.com/bitbucketserver/manage-webhooks-938025878.html){:target="\_blank"} repositories, since they are the only GIT providers
186
186
that send this information in the webhook. We will support other GIT providers as soon as they add the respective feature.
187
187
188
188
###Using the Modified files field to constrain triggers to specific folder/files