gecko-dev/taskcluster/docker/index-task
Victor Porof 9b61ac0482 Bug 1561435 - Format taskcluster/, a=automatic-formatting
# ignore-this-changeset

Differential Revision: https://phabricator.services.mozilla.com/D35938

--HG--
extra : source : 469efde53a4fd604ffc7044779ce7cbad4576811
2019-07-05 10:59:45 +02:00
..
.eslintrc.js
Dockerfile
README
insert-indexes.js Bug 1561435 - Format taskcluster/, a=automatic-formatting 2019-07-05 10:59:45 +02:00
package.json
yarn.lock

README

Index-Image
===========

This image is designed to be used for indexing other tasks. It takes a task
definition as follows:
```js
{
  ...,
  scopes: [
    'index:insert-task:my-index.namespace',
    'index:insert-task:...',
  ],
  payload: {
    image: '...',
    env: {
      TARGET_TASKID: '<taskId-to-be-indexed>',
    },
    command: [
      'insert-indexes.js',
      'my-index.namespace.one',
      'my-index.namespace.two',
      '....',
    ],
    features: {
      taskclusterProxy: true,
    },
    maxRunTime: 600,
  },
}
```

As can be seen the `taskId` to be indexed is given by the environment variable
`TARGET_TASKID` and the `command` arguments specifies namespaces that it must
be index under. It is **important** to also include scopes on the form
`index:insert-task:<...>` for all namespaces `<...>` given as `command`
arguments.