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
Copy file name to clipboardExpand all lines: README.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ var config = {
38
38
organization:'your-organization-name',
39
39
project:'your-project-name',
40
40
apiKey:process.env.SENTRY_API_KEY,
41
-
41
+
42
42
// Release version name/hash is required
43
43
release:process.env.GIT_SHA
44
44
})
@@ -98,7 +98,7 @@ var config = {
98
98
]
99
99
}
100
100
```
101
-
101
+
102
102
-`releaseBody`: Object or function that returns the body that will be sent to Sentry. Defaults to sending the version and projects (which is sufficient to create a basic new release in Sentry).
103
103
- The function is given two arguments: `version` and `projects`. `version` is the result of the `release` object (string or function output); `projects` is the `project` configuration parameter (converted to an array if a single string is provided).
104
104
- The most common use case for overriding this field is Sentry's [release commits](https://docs.sentry.io/learn/releases/#releases-are-better-with-commits) feature. To use this, define `releaseBody` per the example below (providing the most recent commit hash through whatever means works best for your build setup). See the Sentry documentation for more details and options.
@@ -108,7 +108,7 @@ var config = {
108
108
plugins: [
109
109
newSentryPlugin({
110
110
releaseBody:function(version, projects) {
111
-
return {
111
+
return {
112
112
version,
113
113
projects,
114
114
refs: [{
@@ -136,6 +136,8 @@ var config = {
136
136
-`uploadFileRequestOptions`: Object of options or function returning object of options passed through to the underlying `request` call on file uploading; see the [request library documentation](https://github.com/request/request#requestoptions-callback) for available options.
137
137
- If a function is provided, it is given one argument: req, an object of options (including url, auth, and body) that the plugin is sending to the underlying request call. (This is useful if you want to configure the request dynamically based on request data such as the filename.)
138
138
139
+
-`uploadFilesConcurrency`: Number of maximum concurrent uploads of source files to the Sentry API. Use this when the number of source files to upload to Sentry is high and you encounter the `RequestError: Error: getaddrinfo ENOTFOUND sentry.io sentry.io:443` error.
140
+
139
141
### What is a `release`?
140
142
141
143
A [release](https://docs.sentry.io/learn/releases/) is a concept that Sentry uses to attach source maps to a known version of your code. The plugin creates one for you, but you need to provide a "name" for a particular version of your code, which is just a string. Sentry can then use the release to record that an error was found in a specific known version of your code. Releases are also used to "version" your source maps -- source maps are uploaded to a specific release, and when a raw JavaScript error is reported, the release reported with the error is used to locate and apply the correct source maps.
@@ -148,7 +150,7 @@ A git commit hash is very useful for releases - it is a string that defines a pa
148
150
newSentryPlugin({
149
151
// ...
150
152
release:function() {
151
-
// Note: this is just an example, it depends on your deployment pipeline
153
+
// Note: this is just an example, it depends on your deployment pipeline
0 commit comments