Skip to content

Commits on Feb 6, 2021

  1. chore(ci): deploy to docs.angularjs.org from within the correspondi…

    …ng directory
    
    Previously, in order to deploy to Firebase from
    `scripts/docs.angularjs.org-firebase/`, we had to copy the
    `firebase.json` file to the repository root and adjust the contained
    paths accordingly.
    
    By running the `firebase` CLI directly (instead of via `yarn`), we are
    able to deploy from `docs.angularjs.org-firebase/` directly. This
    simplifies the deployment (and local testing) process and paves the way
    for also deploying from `code.angularjs.org-firebase/` in a subsequent
    commit.
    gkalpak committed Feb 6, 2021
  2. chore(ci): copy deployment files inside the respective Firebase direc…

    …tories
    
    We have the `scripts/{code,docs}.angularjs.org-firebase/` directories,
    which contain the necessary code and config for deploying built files to
    the `code-angularjs-org` and `docs-angularjs-org` Firebase projects
    respectively.
    
    Previously, some of the files that needed to be deployed to Firebase (or
    Google Cloud) were placed outside these directories (e.g. in
    `deploy/{code,docs}/`).
    
    Since these files are only used for deploying to Firebase/Google Cloud,
    this commit changes the deployment process to instead copy the files
    inside the directories. In a subsequent commit, this will allow
    simplifying the deployment process, by running it from inside each
    directory instead of having to copy the `firebase.json` files to the
    repository root (and adjust the paths).
    
    These are the destination directory changes:
    
    | Before       | After                                       |
    |--------------|---------------------------------------------|
    | deploy/code/ | scripts/code.angularjs.org-firebase/deploy/ |
    | deploy/docs/ | scripts/docs.angularjs.org-firebase/deploy/ |
    gkalpak committed Feb 6, 2021

Commits on May 24, 2020

Commits on May 23, 2020

  1. chore(ci): move over to CircleCi config

    This commit gets rid of all references to Travis and, belatedly, Jenkins.
    Now all CI is done on CircleCI and releases are run locally.
    
    The CI no longer updates the docs and code.angularjs.org for jobs that are
    not on the `master` branch.
    
    During releases, the docs and code should be uploaded manually.
    petebacondarwin committed May 23, 2020

Commits on Dec 11, 2018

  1. chore(modules): execute modules unit tests in one karma run

    SauceLabs  is struggling to keep connecting and disconnecting
    for each of the modules unit test runs. This commit puts most of
    the module tests into IIFEs so that they can be run in one go.
    
    * ngMock is still tested separately since unlike the other tests
    it doesn't want to have a pre-built version of ngMock available.
    
    * ngAnimate is still tested separately because it does some funny
    things with globals that were difficult to isolate in the main modules
    test run.
    petebacondarwin committed Dec 11, 2018

Commits on Oct 15, 2018

  1. test(modules): properly isolate module tests

    Closes #16712
    Narretz committed Oct 15, 2018

Commits on Oct 11, 2018

  1. chore(*): update minimum Yarn version, do some Yarn-related cleanups

    Included changes:
    
    *Update minimum Yarn version from 1.3.2 to 1.10.1*
    
    Yarn 1.10 added the integrity field to the lockfile, making newer Yarn users
    have their lockfile changed a lot if they run `yarn`. This commit updates the
    required Yarn version to be at least 1.10.1 and changes Travis & Jenkins to use
    Yarn 1.10.1
    
    *Change the package.json's engines grunt field to grunt-cli*
    
    The grunt field suggested it's the grunt package version we're checking while
    we check the grunt-cli version instead.
    
    *Stop separating Yarn script arguments from script names via " -- "*
    
    The " -- " separator is necessary in npm but not in Yarn. In fact, it's
    deprecated in Yarn and some future version is supposed to start passing this
    parameter directly to the scripts which may break them.
    
    *Don't install grunt-cli globally during the build*
    
    It's enough to use `yarn grunt` instead of `grunt` and the global grunt-cli
    installation is no longer needed.
    
    *Use `yarn grunt` instead of `yarn run grunt`*
    
    The former form is shorter.
    
    *Don't define the `grunt` Yarn script*
    
    As opposed to npm, `yarn binName` invokes a binary named `binName` exposed
    by the respective package so the `grant` Yarn script is no longer needed.
    
    *Allow Node versions newer than 8; bump the minimum*
    
    Closes #16714
    mgol committed Oct 11, 2018

Commits on Mar 1, 2018

  1. chore(docs.angularjs.org): only deploy production index.html as entry…

    … file
    
    Previously, we rewrote index.html to index-production.html, but Firebase ignored
    this, probably because an exact file match always takes priority. This lead
    to the problem thatthe root - angularjs.org - didn't include the angular.js source
    files from the CDN
    Narretz committed Mar 1, 2018

Commits on Feb 12, 2018

  1. chore(docs.angularjs.org): serve snapshots for googlebot

    This commit restores serving the plain partials (content) when a docs
    page is accessed with ?_escaped_fragment_=.
    The Google Ajax Crawler accesses these urls when the page has
    `<meta type="fragment" content="!">` is set.
    
    During the migration to Firebase, this was lost, which resulted in Google
    dropping the docs almost completely from the index.
    
    We are using a Firebase cloud function to serve the partials. Since
    we cannot access the static hosted files from the function, we have to
    deploy them as part of the function directory instead, from which they
    can be read.
    
    Related to #16432
    Related to #16417
    Narretz committed Feb 12, 2018

Commits on Feb 8, 2018

  1. chore(docs.angularjs.org): actually fix deployment

    When a file is symlinked, relative paths obviously aren't correct anymore.
    This error was masked because Travis didn't fail the job when Firebase
    couldn't find the public folder.
    To fix, we copy the file and adjust the folder path
    Narretz committed Feb 8, 2018
  2. chore(docs.angularjs.org): deploy sitemap.xml

    Closes #16445
    Narretz committed Feb 8, 2018

Commits on Jan 23, 2018

  1. chore(docs.angularjs.org): fix firebase deploy

    Travis looks for the firebase.json in the repo root,
    but we moved each firebase project in its own sub-folder.
    To fix, we create a symlink before deployment.
    Narretz committed Jan 23, 2018

Commits on Jan 16, 2018

  1. chore(docs.angularjs.org): copy unminified angular files

    e2e tests use the unminified files even in production deployment
    Narretz committed Jan 16, 2018

Commits on Jan 8, 2018

  1. chore(*): get rid of Bower in favor of Yarn aliases & checked-in pack…

    …ages
    
    Bower was used to install multiple versions of jQuery which is now handled
    using Yarn aliases. The remaining two packages, closure-compiler and
    ng-closure-compiler were installed from zip files which is not supported by Yarn
    (see yarnpkg/yarn#1483); the first of them exists
    on npm as the google-closure-compiler but only versions newer than we used are
    published and they don't work with ng-closure-compiler so - instead - both were
    checked in to the repository.
    
    Fixes #16268
    Fixes #14961
    Ref yarnpkg/yarn#1483
    mgol authored and Narretz committed Jan 8, 2018

Commits on Dec 14, 2017

  1. fix(ngScenario): completely remove the angular scenario runner

    The runner has been deprecated and undocumented since 2014:
    See commit 8d6d126899d4b1927360599403a7592011243270
    
    Closes #9405
    
    BREAKING CHANGE:
    
    The angular scenario runner end-to-end test framework has been
    removed from the project and will no longer be available on npm
    or bower starting with 1.7.0.
    It was deprecated and removed from the documentation in 2014.
    Applications that still use it should migrate to
    [Protractor](http://www.protractortest.org).
    Technically, it should also be possible to continue using an
    older version of the scenario runner, as the underlying APIs have
    not changed. However, we do not guarantee future compatibility.
    Narretz committed Dec 14, 2017

Commits on Oct 20, 2017

  1. chore(travis): deploy to docs and code when distTag=latest

    We now deploy to code.angularjs.org and docs.angularjs.org
    when we are on the branch which has distTag=latest set in the
    package.json, i.e. the stable branch.
    
    Previously, we deployed to docs only when distTag=latest and
    the commit was tagged, and to code only on the master branch.
    Narretz committed Oct 20, 2017

Commits on Aug 23, 2017

  1. chore(docs.angularjs.org): fix docs deploy for source file changes

    Since the embedded examples in the docs app now include the local source files instead
    of CDN files, we need to include the source files into the folder that is deployed
    to Firebase hosting
    Narretz committed Aug 23, 2017

Commits on Jul 13, 2017

  1. chore(*): deploy (docs|code) .angularjs.org to Firebase via Travis

    - code.angularjs.org and docs.angularjs.org are two separate Firebase projects
    - both are automatically deployed via Travis config
    - Travis is split up into 2 build stages: first, all tests are run, and if they pass, the deploy
    stage runs a single job with both deployments (actual deployment depends on the state of the commit)
    - docs. is deployed directly to Firebase hosting
    - code. is uploaded to Firebase Google Cloud Storage and uses Firebase hosting rewrites to acces the
    files
    - jenkins builds still push the code builds to the code.angularjs.org Github repository
    
    Closes #9674
    Closes #16093
    Narretz committed Jul 13, 2017

Commits on Jun 13, 2017

  1. chore(grunt): increase task readability

    Narretz authored and petebacondarwin committed Jun 13, 2017

Commits on Mar 22, 2017

  1. chore(*): remove unused docs/bower_components mentions

    mgol committed Mar 22, 2017

Commits on Nov 29, 2016

  1. chore(grunt): check node, yarn and grunt-cli versions

    If global versions of node, yarn or grunt-cli don't match what we expect then blow up.
    petebacondarwin committed Nov 29, 2016
  2. chore(dependencies): USE YARN (and node 6)

    petebacondarwin committed Nov 29, 2016

Commits on Nov 15, 2016

  1. chore(docs): improve version picker

    Closes #15385
    petebacondarwin committed Nov 15, 2016

Commits on Nov 11, 2016

  1. chore(promises-tests): make timeout longer (correctly)

    petebacondarwin committed Nov 11, 2016

Commits on Nov 10, 2016

  1. chore(promises-tests): make timeout longer

    petebacondarwin committed Nov 10, 2016

Commits on Oct 21, 2016

  1. chore(gruntfile): check the node version before starting

    We specify the node version that is required to run the build in the `.nvmrc`
    file. So let's check that the current node version satisfies this and report
    a helpful message if it is not.
    petebacondarwin committed Oct 21, 2016

Commits on Aug 10, 2016

  1. chore(eslint): enable quotes: ["error", "single"]

    The quotes rule had to be disabled for e2e tests generated from ngdoc
    because dgeni templates use double quotes as string delimiters.
    
    Since we can't have guarantees that dgeni template wrappers will follow
    the same JS code style the Angular 1 repo uses, we should find a way
    to enforce our ESLint setup only for the parts in this repo, perhaps
    via prepending a generated `/* eslint-enable OUR_RULES */` pragma.
    
    Closes #15011
    mgol committed Aug 10, 2016

Commits on Aug 5, 2016

  1. chore(*): switch from JSHint/JSCS to ESLint

    Thanks to @Narretz for help in fixing style violations and to @gkalpak
    for a very extensive review.
    
    Closes #14952
    mgol committed Aug 5, 2016
  2. chore(package.json): add grunt-cli to devDependencies, update grunt-*…

    … packages
    
    The Travis build.sh script has to be updated as the previous way of
    specifying parameters to the code run in Grunt tasks stopped working
    with the newest Grunt.
    mgol committed Aug 5, 2016

Commits on Jul 13, 2016

  1. test(jQuery): Run tests with jQuery 3

    Closes #14874
    mgol committed Jul 13, 2016
Older