1. 07 Nov, 2018 3 commits
  2. 06 Nov, 2018 1 commit
  3. 05 Nov, 2018 1 commit
  4. 02 Nov, 2018 10 commits
  5. 01 Nov, 2018 2 commits
    • Robert Knight's avatar
      Create qa deployment of the client · 6ae6d731
      Robert Knight authored
      Add a new build stage to Jenkins CI builds of the master branch which
      deploys a "QA" build to S3. This QA build:
      
       - Has a pre-release version number of the form `X.Y.Z-{commit hash}`
       - Has a stable URL at https://cdn.hypothes.is/hypothesis@qa
         (as opposed to https://cdn.hypothes.is/hypothesis for the prod build)
       - Loads the sidebar app from qa-h (https://qa.hypothes.is/app.html)
       - Does not update the changelog or create a Git tag or GitHub release
      
      This build is currently not deployed to npm at all, but we might need to
      do that in future if we were to create a QA deployment of the browser
      extension with it.
      
      ---
      
       - Add a QA deploy step to the Jenkins build.
       - Skip GitHub release creation and changelog updates for pre-release
         versions used for QA deployments.
       - Remove the preversion.sh script, which is no longer needed since the
         builds always run in Jenkins and not on a developer's system.
       - Support specifying the npm tag to check in `wait-for-npm-release.sh`,
         though this is not used in the final version of this commit.
      6ae6d731
    • Robert Knight's avatar
      Add S3 deployment script to replace s3-npm-publish · dc514d39
      Robert Knight authored
      Replace the generic Docker-based s3-npm-publish tool with a JS script in the
      client repo which is tailored more specifically to the needs of client
      deployments:
      
       - Avoid creating the `hypothesis@X.Y` and `hypothesis@X` aliases which we
         never used.
      
       - Support uploading a copy of the entry point under a version-indepenent
         alias, regardless of whether this is a pre-release or not.
      
         This will enable creating a stable URL which points to the current QA
         version of the client.
      
       - Deploy the package directly from the current working directory. This saves
         the need to wait for publication to npm to complete, or the need to
         actually publish the package to npm at all in the case of the QA
         release.
      dc514d39
  6. 31 Oct, 2018 4 commits
  7. 25 Oct, 2018 3 commits
  8. 23 Oct, 2018 7 commits
  9. 22 Oct, 2018 5 commits
  10. 19 Oct, 2018 4 commits