A provider for strider that integrates with GitHub to provide easy setup of your projects. It registers webhooks and sets up ssh keys (if you so choose).
Note: Supports using '[skip ci]' in your commit message to skip commits triggering a job.
If you are running on localhost:3000
the default settings should work just fine.
SERVER_NAME
The url of your strider server. Defaults to http://localhost:3000
.
The following variables only need to be overridden if you are using github enterprise. See 'Enterprise Setup' below.
PLUGIN_GITHUB_APP_ID
Defaults to client ID of Strider-CD Github App
PLUGIN_GITHUB_APP_SECRET
Defaults to client secret of Strider-CD Github App
PLUGIN_GITHUB_API_DOMAIN
Defaults to https://github.com
PLUGIN_GITHUB_API_ENDPOINT
Defaults to https://api.github.com
You'll need to create an Application on your GitHub Enterprise Server. Log in to GitHub Enterprise and navigate to
https://your-github-url.com/settings/applications/new
and set authentication URL to
https://your-strider-server:port/auth/github/callback
.
Define the environment variables. Here is an example:
export SERVER_NAME="http://111.11.11.111:3000"
export PLUGIN_GITHUB_APP_ID="a342d32c23c23"
export PLUGIN_GITHUB_APP_SECRET="5af64a67af586847afbc6796769769d97a961"
export PLUGIN_GITHUB_API_DOMAIN="https://github.my-organization.com"
export PLUGIN_GITHUB_API_ENDPOINT="https://github.my-organization.com/api/v3"
NOTE SERVER_NAME
must be the same exact host that you used for the 'Authentication URL' in step 1. For example,
if you used http://111.11.11.111:3000/auth/guthub/callback
in step 1, your SERVER_NAME
must be
http://111.11.11.111:3000
. Also note that the protocol must be the same between the two (if you used http://
in step 1, you must use http://
in SERVER_NAME
and not https://
).
Reboot strider and navigate link a github account as normal, you should see your enterprise repos!
/settings/profile
. Make sure the following are defined and set properly.
Due to the fact that Github posts to the Strider app when there is an event (commit, PR, etc) it is very difficult to test all of the functionality when developing/fixing bugs locally. An alternative is to use something like localtunnel.
$ npm install -g localtunnel
$ lt --port <strider-port>