• Robert Knight's avatar
    Update browser extension after a new prod client release · b9b83d99
    Robert Knight authored
    Trigger a build of the "master" branch of the "browser-extension" project after
    a new client production release with the `BUILD_TYPE` parameter set to
    `update-hypothesis-client` to trigger an update to the Hypothesis client.
    
    In implementing this, I ran into a couple of issues that caught me out
    initially:
    
     - The `build` command must take a job name rather than a project (which
       is essentially a folder of jobs), ie. `browser-extension/master`
       rather than `browser-extension`. See [1].
    
     - To pass a value for a choice parameter, the easiest option is just to
       pass a string [2]
    
    [1] https://stackoverflow.com/questions/46471467/
    [2] https://stackoverflow.com/a/41760715/434243
    b9b83d99
Name
Last commit
Last update
.github Loading commit data...
bin Loading commit data...
docs Loading commit data...
embedding-examples Loading commit data...
images Loading commit data...
scripts Loading commit data...
src Loading commit data...
.babelrc Loading commit data...
.dockerignore Loading commit data...
.eslintignore Loading commit data...
.eslintrc Loading commit data...
.gitignore Loading commit data...
.npmignore Loading commit data...
.npmrc Loading commit data...
.prettierignore Loading commit data...
.prettierrc Loading commit data...
.python-version Loading commit data...
.travis.yml Loading commit data...
CODE_OF_CONDUCT Loading commit data...
Dockerfile Loading commit data...
Jenkinsfile Loading commit data...
LICENSE Loading commit data...
Makefile Loading commit data...
README.md Loading commit data...
gulpfile.js Loading commit data...
package.json Loading commit data...
requirements-dev.in Loading commit data...
tox.ini Loading commit data...
yarn.lock Loading commit data...