Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 18.216.45.133
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
lib /
node_modules /
npm /
node_modules /
is-ci /
Delete
Unzip
Name
Size
Permission
Date
Action
node_modules
[ DIR ]
drwxr-xr-x
2022-01-26 16:43
LICENSE
1.07
KB
-rw-r--r--
2022-01-10 12:20
README.md
1.27
KB
-rw-r--r--
2022-01-10 12:20
bin.js
70
B
-rwxr-xr-x
2022-01-10 12:20
index.js
55
B
-rw-r--r--
2022-01-10 12:20
package.json
1.62
KB
-rw-r--r--
2022-01-10 12:20
Save
Rename
# is-ci Returns `true` if the current environment is a Continuous Integration server. Please [open an issue](https://github.com/watson/is-ci/issues) if your CI server isn't properly detected :) [](https://www.npmjs.com/package/is-ci) [](https://travis-ci.org/watson/is-ci) [](https://github.com/feross/standard) ## Installation ```bash npm install is-ci --save ``` ## Programmatic Usage ```js const isCI = require('is-ci') if (isCI) { console.log('The code is running on a CI server') } ``` ## CLI Usage For CLI usage you need to have the `is-ci` executable in your `PATH`. There's a few ways to do that: - Either install the module globally using `npm install is-ci -g` - Or add the module as a dependency to your app in which case it can be used inside your package.json scripts as is - Or provide the full path to the executable, e.g. `./node_modules/.bin/is-ci` ```bash is-ci && echo "This is a CI server" ``` ## Supported CI tools Refer to [ci-info](https://github.com/watson/ci-info#supported-ci-tools) docs for all supported CI's ## License [MIT](LICENSE)