bug 1432364 - remove scriptworker requirement for docker images. r=nthomas
authorAki Sasaki <asasaki@mozilla.com>
Thu, 28 Jun 2018 12:38:27 -0700
changeset 450306 2870a1a9df1bf840da42700d38e61b33aef3856e
parent 450305 29881f03bb5eebecc6364941406d0c114d123a94
child 450307 ee9465ce4a25b4fb295fb5f6a04433fa23e95612
push id234
push usermozilla@hocat.ca
push dateSat, 10 Nov 2018 00:08:05 +0000
treeherdermozilla-esr60@f2569ad7bd92 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersnthomas
bugs1432364
milestone60.3.1
bug 1432364 - remove scriptworker requirement for docker images. r=nthomas
taskcluster/docs/docker-images.rst
--- a/taskcluster/docs/docker-images.rst
+++ b/taskcluster/docs/docker-images.rst
@@ -102,21 +102,19 @@ by specifying the docker image name in t
 referred to by a ``<repo>@<repodigest>`` string:
 
 Example:
 
 .. code-block:: none
 
     image: taskcluster/decision:0.1.10@sha256:c5451ee6c655b3d97d4baa3b0e29a5115f23e0991d4f7f36d2a8f793076d6854
 
-Each image has a repo digest, an image hash, and a version. The repo digest is
-stored in the ``HASH`` file in the image directory  and used to refer to the
-image as above.  The version is in ``VERSION``.  The image hash is used in
-`chain-of-trust verification <https://scriptworker.readthedocs.io/en/latest/chain_of_trust.html>`_
-in `scriptworker <https://github.com/mozilla-releng/scriptworker>`_.
+Each image has a repo digest and a version. The repo digest is stored in the
+``HASH`` file in the image directory and used to refer to the image as above.
+The version is in ``VERSION``.
 
 The version file only serves to provide convenient names, such that old
 versions are easy to discover in the registry (and ensuring old versions aren't
 deleted by garbage-collection).
 
 Each image directory also has a ``REGISTRY``, defaulting to the ``REGISTRY`` in
 the ``taskcluster/docker`` directory, and specifying the image registry to
 which the completed image should be uploaded.
@@ -166,22 +164,17 @@ Docker Registry Images
 
 Landing docker registry images takes a little more care.
 
 Once a new version of the image has been built and tested locally, push it to
 the docker registry and make note of the resulting repo digest.  Put this value
 in the ``HASH`` file, and update any references to the image in the code or
 task definitions.
 
-The change is now safe to use in Try pushes.  However, if the image is used in
-building releases then it is *not* safe to land to an integration branch until
-the whitelists in `scriptworker's constants.py
-<https://github.com/mozilla-releng/scriptworker/blob/master/scriptworker/constants.py>`_
-have also been updated. These whitelists use the image hash, not the repo
-digest.
+The change is now safe to use in Try pushes.
 
 Special Dockerfile Syntax
 -------------------------
 
 Dockerfile syntax has been extended to allow *any* file from the
 source checkout to be added to the image build *context*. (Traditionally
 you can only ``ADD`` files from the same directory as the Dockerfile.)