From 02d1b36e7afe2642d06537ec80c33ab07b85bb7a Mon Sep 17 00:00:00 2001 From: Mohamed Abdel Nasser Date: Mon, 17 Feb 2020 00:27:37 +0200 Subject: [PATCH 1/7] docs: update versioned_docs/deployment with travis-ci --- .../version-2.0.0-alpha.41/deployment.md | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/website/versioned_docs/version-2.0.0-alpha.41/deployment.md b/website/versioned_docs/version-2.0.0-alpha.41/deployment.md index f12cf898b76c..98598ad60969 100644 --- a/website/versioned_docs/version-2.0.0-alpha.41/deployment.md +++ b/website/versioned_docs/version-2.0.0-alpha.41/deployment.md @@ -146,3 +146,35 @@ Render offers [free static site hosting](https://render.com/docs/static-sites) w | **Publish Directory** | `build` | That's it! Your app will be live on your Render URL as soon as the build finishes. + +## Automating Deployments Using Continuous Integration + +Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the `yarn deploy` script whenever your docs get updated. In the following section, we'll be covering how to do just that using [Travis CI](https://travis-ci.com/), a popular continuous integration service provider. + + +### Using Travis CI + +1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) +1. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate. +1. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the `More options` > `Setting` > `Environment Variables` section of your repository. +1. Create a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). +1. Create a `.travis.yml` on the root of your repository with below text. + +```yaml +# .travis.yml +language: node_js +node_js: + - '8' +branches: + only: + - master +cache: + yarn: true +script: + - git config --global user.name "${GH_NAME}" + - git config --global user.email "${GH_EMAIL}" + - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc + - yarn && GIT_USER="${GH_NAME}" yarn deploy +``` + +Now, whenever a new commit lands in `master`, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the `yarn deploy` script. From 97f7a3a0ec07da992d7659cdcd47760d93d7becf Mon Sep 17 00:00:00 2001 From: Mohamed Abdel Nasser Date: Mon, 17 Feb 2020 00:30:14 +0200 Subject: [PATCH 2/7] docs: update docs/deployment with travis-ci --- website/docs/deployment.md | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/website/docs/deployment.md b/website/docs/deployment.md index f12cf898b76c..98598ad60969 100644 --- a/website/docs/deployment.md +++ b/website/docs/deployment.md @@ -146,3 +146,35 @@ Render offers [free static site hosting](https://render.com/docs/static-sites) w | **Publish Directory** | `build` | That's it! Your app will be live on your Render URL as soon as the build finishes. + +## Automating Deployments Using Continuous Integration + +Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the `yarn deploy` script whenever your docs get updated. In the following section, we'll be covering how to do just that using [Travis CI](https://travis-ci.com/), a popular continuous integration service provider. + + +### Using Travis CI + +1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) +1. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate. +1. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the `More options` > `Setting` > `Environment Variables` section of your repository. +1. Create a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). +1. Create a `.travis.yml` on the root of your repository with below text. + +```yaml +# .travis.yml +language: node_js +node_js: + - '8' +branches: + only: + - master +cache: + yarn: true +script: + - git config --global user.name "${GH_NAME}" + - git config --global user.email "${GH_EMAIL}" + - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc + - yarn && GIT_USER="${GH_NAME}" yarn deploy +``` + +Now, whenever a new commit lands in `master`, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the `yarn deploy` script. From 940ddb6a1857bbdab38e9046a276d8620ac3a06b Mon Sep 17 00:00:00 2001 From: Mohamed Abdel Nasser Date: Tue, 18 Feb 2020 19:16:15 +0200 Subject: [PATCH 3/7] Transfer update to a new version --- .../version-2.0.0-alpha.41/deployment.md | 32 ------------------- 1 file changed, 32 deletions(-) diff --git a/website/versioned_docs/version-2.0.0-alpha.41/deployment.md b/website/versioned_docs/version-2.0.0-alpha.41/deployment.md index 98598ad60969..f12cf898b76c 100644 --- a/website/versioned_docs/version-2.0.0-alpha.41/deployment.md +++ b/website/versioned_docs/version-2.0.0-alpha.41/deployment.md @@ -146,35 +146,3 @@ Render offers [free static site hosting](https://render.com/docs/static-sites) w | **Publish Directory** | `build` | That's it! Your app will be live on your Render URL as soon as the build finishes. - -## Automating Deployments Using Continuous Integration - -Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the `yarn deploy` script whenever your docs get updated. In the following section, we'll be covering how to do just that using [Travis CI](https://travis-ci.com/), a popular continuous integration service provider. - - -### Using Travis CI - -1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) -1. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate. -1. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the `More options` > `Setting` > `Environment Variables` section of your repository. -1. Create a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). -1. Create a `.travis.yml` on the root of your repository with below text. - -```yaml -# .travis.yml -language: node_js -node_js: - - '8' -branches: - only: - - master -cache: - yarn: true -script: - - git config --global user.name "${GH_NAME}" - - git config --global user.email "${GH_EMAIL}" - - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc - - yarn && GIT_USER="${GH_NAME}" yarn deploy -``` - -Now, whenever a new commit lands in `master`, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the `yarn deploy` script. From 02e553091b5c6c3123823145cbc25a9584dc5958 Mon Sep 17 00:00:00 2001 From: Mohamed Abdel Nasser Date: Tue, 18 Feb 2020 19:17:39 +0200 Subject: [PATCH 4/7] Update node version --- website/docs/deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/deployment.md b/website/docs/deployment.md index 98598ad60969..532521be4114 100644 --- a/website/docs/deployment.md +++ b/website/docs/deployment.md @@ -164,7 +164,7 @@ Continuous integration (CI) services are typically used to perform routine tasks # .travis.yml language: node_js node_js: - - '8' + - '10' branches: only: - master From 63f7ba3d605a8a11fd44d27f3a1ebb537ad57388 Mon Sep 17 00:00:00 2001 From: Mohamed Abdel Nasser Date: Tue, 18 Feb 2020 19:27:37 +0200 Subject: [PATCH 5/7] update v-2.0.0-alpha.43 with Travis CI deployment instructions --- .../version-2.0.0-alpha.43/deployment.md | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/website/versioned_docs/version-2.0.0-alpha.43/deployment.md b/website/versioned_docs/version-2.0.0-alpha.43/deployment.md index f12cf898b76c..532521be4114 100644 --- a/website/versioned_docs/version-2.0.0-alpha.43/deployment.md +++ b/website/versioned_docs/version-2.0.0-alpha.43/deployment.md @@ -146,3 +146,35 @@ Render offers [free static site hosting](https://render.com/docs/static-sites) w | **Publish Directory** | `build` | That's it! Your app will be live on your Render URL as soon as the build finishes. + +## Automating Deployments Using Continuous Integration + +Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the `yarn deploy` script whenever your docs get updated. In the following section, we'll be covering how to do just that using [Travis CI](https://travis-ci.com/), a popular continuous integration service provider. + + +### Using Travis CI + +1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) +1. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate. +1. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the `More options` > `Setting` > `Environment Variables` section of your repository. +1. Create a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). +1. Create a `.travis.yml` on the root of your repository with below text. + +```yaml +# .travis.yml +language: node_js +node_js: + - '10' +branches: + only: + - master +cache: + yarn: true +script: + - git config --global user.name "${GH_NAME}" + - git config --global user.email "${GH_EMAIL}" + - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc + - yarn && GIT_USER="${GH_NAME}" yarn deploy +``` + +Now, whenever a new commit lands in `master`, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the `yarn deploy` script. From 6b534951948e802537171c6c5162ea76b1a33e6f Mon Sep 17 00:00:00 2001 From: Mohamed Abdel Nasser Date: Tue, 18 Feb 2020 21:52:14 +0200 Subject: [PATCH 6/7] Remove updates from v2.0.0-alpha.43 --- .../version-2.0.0-alpha.43/deployment.md | 32 ------------------- 1 file changed, 32 deletions(-) diff --git a/website/versioned_docs/version-2.0.0-alpha.43/deployment.md b/website/versioned_docs/version-2.0.0-alpha.43/deployment.md index 532521be4114..f12cf898b76c 100644 --- a/website/versioned_docs/version-2.0.0-alpha.43/deployment.md +++ b/website/versioned_docs/version-2.0.0-alpha.43/deployment.md @@ -146,35 +146,3 @@ Render offers [free static site hosting](https://render.com/docs/static-sites) w | **Publish Directory** | `build` | That's it! Your app will be live on your Render URL as soon as the build finishes. - -## Automating Deployments Using Continuous Integration - -Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the `yarn deploy` script whenever your docs get updated. In the following section, we'll be covering how to do just that using [Travis CI](https://travis-ci.com/), a popular continuous integration service provider. - - -### Using Travis CI - -1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) -1. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate. -1. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the `More options` > `Setting` > `Environment Variables` section of your repository. -1. Create a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). -1. Create a `.travis.yml` on the root of your repository with below text. - -```yaml -# .travis.yml -language: node_js -node_js: - - '10' -branches: - only: - - master -cache: - yarn: true -script: - - git config --global user.name "${GH_NAME}" - - git config --global user.email "${GH_EMAIL}" - - echo "machine github.com login ${GH_NAME} password ${GH_TOKEN}" > ~/.netrc - - yarn && GIT_USER="${GH_NAME}" yarn deploy -``` - -Now, whenever a new commit lands in `master`, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the `yarn deploy` script. From 509127c70d55eec12d019cbfbbc37d3e9e64c57e Mon Sep 17 00:00:00 2001 From: Yangshun Tay Date: Wed, 19 Feb 2020 09:11:16 +0800 Subject: [PATCH 7/7] Update deployment.md --- website/docs/deployment.md | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/website/docs/deployment.md b/website/docs/deployment.md index 532521be4114..b0433c02a607 100644 --- a/website/docs/deployment.md +++ b/website/docs/deployment.md @@ -147,18 +147,15 @@ Render offers [free static site hosting](https://render.com/docs/static-sites) w That's it! Your app will be live on your Render URL as soon as the build finishes. -## Automating Deployments Using Continuous Integration +### Deplying to Travis CI -Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and yes, deploying changes to your website. All you need to do to automate deployment of your website is to invoke the `yarn deploy` script whenever your docs get updated. In the following section, we'll be covering how to do just that using [Travis CI](https://travis-ci.com/), a popular continuous integration service provider. +Continuous integration (CI) services are typically used to perform routine tasks whenever new commits are checked in to source control. These tasks can be any combination of running unit tests and integration tests, automating builds, publishing packages to NPM, and deploying changes to your website. All you need to do to automate deployment of your website is to invoke the `yarn deploy` script whenever your website is updated. The following section covers how to do just that using [Travis CI](https://travis-ci.com/), a popular continuous integration service provider. - -### Using Travis CI - -1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) -1. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate. -1. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the `More options` > `Setting` > `Environment Variables` section of your repository. -1. Create a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). -1. Create a `.travis.yml` on the root of your repository with below text. +1. Go to https://github.com/settings/tokens and generate a new [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) +1. Using your GitHub account, [add the Travis CI app](https://github.com/marketplace/travis-ci) to the repository you want to activate. +1. Open your Travis CI dashboard. The URL looks like https://travis-ci.com/USERNAME/REPO, and navigate to the `More options` > `Setting` > `Environment Variables` section of your repository. +1. Create a new environment variable named `GH_TOKEN` with your newly generated token as its value, then `GH_EMAIL` (your email address) and `GH_NAME` (your GitHub username). +1. Create a `.travis.yml` on the root of your repository with the following: ```yaml # .travis.yml @@ -177,4 +174,4 @@ script: - yarn && GIT_USER="${GH_NAME}" yarn deploy ``` -Now, whenever a new commit lands in `master`, Travis CI will run your suite of tests and, if everything passes, your website will be deployed via the `yarn deploy` script. +Now, whenever a new commit lands in `master`, Travis CI will run your suite of tests and if everything passes, your website will be deployed via the `yarn deploy` script.