6
6
blurb : An overview of using Danger with BitBucket Server, and some examples
7
7
---
8
8
9
- To use Danger JS with BitBucket Server: you'll need to create a new account for Danger to use,
10
- then set the following environment variables on your CI:
9
+ To use Danger JS with BitBucket Server: you'll need to create a new account for Danger to use, then set the following
10
+ environment variables on your CI:
11
11
12
12
* ` DANGER_BITBUCKETSERVER_HOST ` = The root URL for your server, e.g. ` https://bitbucket.mycompany.com ` .
13
13
* ` DANGER_BITBUCKETSERVER_USERNAME ` = The username for the account used to comment.
@@ -23,8 +23,7 @@ if (danger.bitbucket_server.pr.title.includes("WIP")) {
23
23
}
24
24
```
25
25
26
- The DSL is expansive, you can see all the details inside the [ Danger JS Reference] [ ref ] ,
27
- but the TLDR is:
26
+ The DSL is expansive, you can see all the details inside the [ Danger JS Reference] [ ref ] , but the TLDR is:
28
27
29
28
``` ts
30
29
danger .bitbucket_server .
@@ -72,6 +71,19 @@ if (hasGIF) {
72
71
}
73
72
```
74
73
75
- Plus any other example you can find that uses GitHub, will probably work in BitBucket Server, with a bit of DSL translation.
74
+ Plus any other example you can find that uses GitHub, will probably work in BitBucket Server, with a bit of DSL
75
+ translation.
76
76
77
- Our BitBucket Server support is still pretty new, so we'd love to see improvements and PRs to help make it work for everyone.
77
+ Our BitBucket Server support is still pretty new, so we'd love to see improvements and PRs to help make it work for
78
+ everyone.
79
+
80
+ In addition, it is possible to specify a proxy to be used for the requests using environmental variables. This is useful
81
+ for debugging:
82
+
83
+ ``` ts
84
+ export NODE_TLS_REJECT_UNAUTHORIZED = 0 # Avoid certificate error
85
+
86
+ export http_proxy = http :// 127.0.0.1:8080
87
+ or
88
+ export https_proxy = https :// 127.0.0.1:8080
89
+ ```
0 commit comments