Merge branch 'master' into patch-1

Author: Pezi777

user/build-matrix.md

@@ -216,6 +216,43 @@ script: env $EXTRA_TESTS ./test.py $TEST_SUITE
 ```
 {: data-file=".travis.yml"}
 
+### Explicitly included jobs with only one element in the build matrix
+
+As a special case, if your build matrix has only one element _and_ you have
+explicitly included jobs, matrix expansion is not done and the explicit jobs
+_completely_ define your build. For example:
+
+```yaml
+language: python
+python:
+  - '3.5'
+matrix:
+  include:
+    - env: EXTRA_TESTS=true
+# only defines one job with `python: 3.5` and `env: EXTRA_TESTS=true`
+```
+{: data-file=".travis.yml"}
+
+If you need the (sole) job from the matrix in such a case, too,
+add a blank job entry to the explicit list (as it would
+[inherit all values from the matrix](#explicitly-included-jobs-inherit-the-first-value-in-the-array)
+with no changes):
+
+```yaml
+language: python
+python:
+  - '3.5'
+matrix:
+  include:
+    -
+    - env: EXTRA_TESTS=true
+# defines two jobs:
+#   - python: 3.5
+#   - python: 3.5
+#     env: EXTRA_TESTS=true
+```
+{: data-file=".travis.yml"}
+
 ## Rows that are Allowed to Fail
 
 You can define rows that are allowed to fail in the build matrix. Allowed

user/deployment/npm.md

@@ -16,6 +16,10 @@ publishes to npmjs.com, however if you have a `publishConfig.registry` key in yo
 A minimal `.travis.yml` configuration for publishing to [npmjs.com][npmjs] with npm version 2+ looks like:
 
 ```yaml
+language: node_js
+node_js:
+  - "11.13"
+
 deploy:
   provider: npm
   email: "YOUR_EMAIL_ADDRESS"

user/installing-dependencies.md

@@ -14,7 +14,7 @@ To install Ubuntu packages that are not included in the standard [precise](/user
 
 ```yaml
 before_install:
-  - sudo apt-get install -y libxml2-dev
+  - sudo apt-get -y install libxml2-dev
 ```
 {: data-file=".travis.yml"}
 
@@ -23,24 +23,24 @@ By default, `apt-get update` does not get run automatically. If you want to upda
 ```yaml
 before_install:
   - sudo apt-get update
-  - sudo apt-get install -y libxml2-dev
+  - sudo apt-get -y install libxml2-dev
 ```
 {: data-file=".travis.yml"}
 
 The second way is to use the [APT addon](#installing-packages-with-the-apt-addon):
 
 ```yaml
 before_install:
-  - sudo apt-get install -y libxml2-dev
+  - sudo apt-get -y install libxml2-dev
 addons:
   apt:
     update: true
 ```
 {: data-file=".travis.yml"}
 
-> Do not run `apt-get upgrade` in your build as it downloads up to 500MB of packages and significantly extends your build time.
+> Do not run `apt-get upgrade` in your build as it downloads up to 500MB of packages and significantly extends your build time. Additionally, some packages may fail to update, which will lead to a failed build.
 >
-> Use the `-y` parameter with apt-get to assume yes as the answer to each apt-get prompt.
+> Use the `-y` parameter with apt-get to assume yes to all queries by the apt tools.
 
 ### Installing Packages from a custom APT repository
 
@@ -50,9 +50,9 @@ For example, to install gcc from the ubuntu-toolchain ppa
 
 ```yaml
 before_install:
-  - sudo add-apt-repository ppa:ubuntu-toolchain-r/test -y
-  - sudo apt-get update -q
-  - sudo apt-get install gcc-4.8 -y
+  - sudo add-apt-repository -y ppa:ubuntu-toolchain-r/test
+  - sudo apt-get -q update
+  - sudo apt-get -y install gcc-4.8
 ```
 {: data-file=".travis.yml"}
 
@@ -66,8 +66,8 @@ This example adds the APT repository for Varnish 3.0 for Ubuntu 12.04 to the loc
 before_script:
   - curl http://repo.varnish-cache.org/debian/GPG-key.txt | sudo apt-key add -
   - echo "deb http://repo.varnish-cache.org/ubuntu/ precise varnish-3.0" | sudo tee -a /etc/apt/sources.list
-  - sudo apt-get update -qq
-  - sudo apt-get install varnish -y
+  - sudo apt-get -qq update
+  - sudo apt-get -y install varnish
 ```
 {: data-file=".travis.yml"}
 

user/languages/julia.md

@@ -37,6 +37,7 @@ julia:
 Acceptable formats are:
  - `nightly` will test against the latest [nightly build](https://julialang.org/downloads/nightlies.html)
 of Julia.
+ - `X` will test against the latest release for that major version. (Applies only to major versions 1 and later.)
  - `X.Y` will test against the latest release for that minor version.
  - `X.Y.Z` will test against that exact version.
 

user/migrate/open-source-repository-migration.md

@@ -19,20 +19,18 @@ When a repository is migrated, the following information will be transferred to
 * Cron jobs configured for the repository
 * Last build status - the build badge in travis-ci.com will reflect this status until new builds are triggered
 * Next build number
+* Previous build history
 
 ### What information will not be transferred to travis-ci.com?
 
-The following information will not be transferred to travis-ci.com when a repository is migrated.
+The following information will not be transferred to travis-ci.com when a repository is migrated:
 
-* Previous build history - your builds from before the migration to travis-ci.com will remain on travis-ci.org until the  complete build- history migration (sometime in early Q3 2019)
 * Caches - they will be re-created automatically on the first build on travis-ci.com
 
 ## Do I need to make any other changes?
 
 You only need to make any changes yourself if you use any of the following features:
 
-* **build badges**:  make sure to update the URL to reflect the new repository setup in travis-ci.com. In the future, we will automatically redirect travis-ci.org badge URLs to the corresponding travis-ci.com ones.
-
 * **"Protected Branches" feature in GitHub** to require a passing Travis CI build before merging a Pull Request: make sure to edit your required status checks to now use `Travis CI - Pull Request` and/or `Travis CI - Branch`. See: [Required status checks at GitHub](https://help.github.com/articles/about-required-status-checks/).
 
 * **[Travis CLI](https://github.com/travis-ci/travis.rb)**: after migration make sure to add the `--com` flag or [make it your default endpoint](https://github.com/travis-ci/travis.rb#endpoint) by running: `travis endpoint --com --set-default`.
@@ -45,16 +43,15 @@ Your repository on travis-ci.org will be automatically deactivated (that is, it
 
 With this read-only mode:
 
-* All the previous build history will be accessible at travis-ci.org
 * The "Trigger build" functionality won't be available in travis-ci.org
 * It won't be possible to restart a previous job that ran in travis-ci.org
 * The Settings page for your repository will become inactive - the transferred repository settings will now be available in travis-ci.com instead.
 
-In the future, when all the previous build history is migrated, we will provide redirections from all API/web requests going to travis-ci.org to travis-ci.com.
+In the future, we will provide redirections from all API/web requests going from travis-ci.org to travis-ci.com.
 
 ## How long does the migration process take?
 
-The migration process for a repository should not take more than a couple of seconds.
+The migration process for each repository should not take more than a couple of seconds.
 
 ## Can I migrate multiple repositories at once?
 
@@ -77,14 +74,14 @@ If you are already using GitHub Apps for your account in travis-ci.com, you need
 
 3. When activating the Travis CI GitHub App, grant access to the repositories (both public and private) that you want to build in travis-ci.com. Save the changes.
 
-4. Once back in your Travis CI profile, the selected repositories will be listed there. Those projects that were already building in travis-ci.com, or any new public or private projects will now be active in travis-ci.com.
+4. Once back in your Travis CI profile, the selected repositories will be listed there. Those projects that were already building in travis-ci.org will appear in the Migrate tab for your account.
 
 ### The migration steps
 
-1. Once you have granted access via GitHub Apps to the repositories you'd like to build and transfer, a new ["Migrate" tab](https://travis-ci.com/account/migrate) will appear in your account page with a list of the repositories to migrate:
+1. Once you have granted access via GitHub Apps to the repositories you'd like to build and transfer, on the ["Migrate" tab](https://travis-ci.com/account/migrate), there will be a list of the repositories available to migrate:
   ![Migration repository list](/user/images/oss-migration/repos-to-migrate.png)
 
-2. Select the repositories you'd like to migrate and click "Migrate selected repositories",  You'll be asked for a final confirmation - please remember that your build history will not be migrated at this time (See: [What information will not be transferred to travis-ci.com?](#what-information-will-not-be-transferred-to-travis-cicom)).
+2. Select the repositories you'd like to migrate and click "Migrate selected repositories",  You'll be asked for a final confirmation - please remember that you'll need to update protected branches (See: [Do I need to make any other changes?](#do-i-need-to-make-any-other-changes)).
 
 3. Confirm the migration. The icons next to your repository name will show the migration status ("processing", or "migrated"):
   ![Migration statuses](/user/images/oss-migration/migration-statuses.png)