Removes npm-git.sh scripts (#4853)

This commit is contained in:
Florent Vilmart
2018-06-25 20:59:54 -04:00
parent dccd7d7a1d
commit b660ca5ed8
4 changed files with 21 additions and 52 deletions

View File

@@ -55,7 +55,7 @@ after_script:
jobs: jobs:
include: include:
# release on github latest branch # release on npm on tags
- stage: release - stage: release
node_js: '8.10' node_js: '8.10'
env: env:
@@ -63,13 +63,6 @@ jobs:
after_script: skip after_script: skip
script: skip script: skip
deploy: deploy:
- provider: script
skip_cleanup: true
script: ./resources/npm-git.sh && npm install -g https://github.com/parse-community/parse-server#latest
on:
branch:
- master
- 3.x
- provider: npm - provider: npm
skip_cleanup: true skip_cleanup: true
email: email:

View File

@@ -8,6 +8,14 @@
* Adds support for JS SDK 2.0 job status header * Adds support for JS SDK 2.0 job status header
### 2.8.3
[Full Changelog](https://github.com/parse-community/parse-server/compare/2.8.3...2.8.2)
#### Improvements:
* Removes npm-git scripts as npm supports using git repositories that build, thanks to [Florent Vilmart](https://github.com/flovilmart)
### 2.8.2 ### 2.8.2
[Full Changelog](https://github.com/parse-community/parse-server/compare/2.8.2...2.8.1) [Full Changelog](https://github.com/parse-community/parse-server/compare/2.8.2...2.8.1)

View File

@@ -393,16 +393,24 @@ If you believe you've found an issue with Parse Server, make sure these boxes ar
# Want to ride the bleeding edge? # Want to ride the bleeding edge?
The `latest` branch in this repository is automatically maintained to be the last It is recommend to use builds deployed npm for many reasons, but if you want to use
commit to `master` to pass all tests, in the same form found on npm. It is
recommend to use builds deployed npm for many reasons, but if you want to use
the latest not-yet-released version of parse-server, you can do so by depending the latest not-yet-released version of parse-server, you can do so by depending
directly on this branch: directly on this branch:
``` ```
npm install parseplatform/parse-server.git#latest npm install parse-community/parse-server.git#master
``` ```
## Experimenting
You can also use your own forks, and work in progress branches by specifying them:
```
npm install github:myUsername/parse-server#my-awesome-feature
```
And don't forget, if you plan to deploy it remotely, you should run `npm install` with the `--save` option.
# Contributing # Contributing
We really want Parse to be yours, to see it grow and thrive in the open source community. Please see the [Contributing to Parse Server guide](CONTRIBUTING.md). We really want Parse to be yours, to see it grow and thrive in the open source community. Please see the [Contributing to Parse Server guide](CONTRIBUTING.md).

View File

@@ -1,40 +0,0 @@
#!/bin/sh -e
# This script maintains a git branch which mirrors master but in a form that
# what will eventually be deployed to npm, allowing npm dependencies to use:
#
# "parse-server": "parseplatform/parse-server#latest"
#
# From: https://github.com/graphql/graphql-js/blob/master/resources/npm-git.sh
BUILD_DIR=latest
BRANCH="${TRAVIS_BRANCH}"
TARGET="latest"
if [ "$BRANCH" != "master" ];
then
TARGET="$BRANCH-preview"
fi
npm run build
mkdir -p $BUILD_DIR
cp package.json $BUILD_DIR/
cp README.md $BUILD_DIR/
cp LICENSE $BUILD_DIR/
cp PATENTS $BUILD_DIR/
cp CHANGELOG.md $BUILD_DIR/
cp postinstall.js $BUILD_DIR/
cp -R lib $BUILD_DIR
cp -R bin $BUILD_DIR
cp -R public_html $BUILD_DIR
cp -R views $BUILD_DIR
cd $BUILD_DIR
git init
git config user.name "Travis CI"
git config user.email "github@fb.com"
git add .
git commit -m "Deploy $BRANCH to $TARGET branch"
git push --force --quiet "https://${GH_TOKEN}@github.com/parse-community/parse-server.git" master:$TARGET