temporarily configure mistral to publish to pypi

We have a few projects that import Mistral code as though it was a
library. Those projects rely on being able to run unit tests through
tox, which wants to pip install Mistral. We have several very old
versions of the project on PyPI, but not the new Newton releases. We
will tag a new Newton release using the same SHA as the most recent
patch release to trigger publishing after this patch is merged. When the
work to create mistral-lib is done, we can revert this patch.

Change-Id: I9fb8be010b2b9c5466c8b293fdc72763323ad2dd
Needed-by: I1c98b9f120da81caeb27750f419b3712aeefaaff
Signed-off-by: Doug Hellmann <doug@doughellmann.com>

jenkins/jobs/projects.yaml

@@ -6573,7 +6573,12 @@
       - python-jobs
       - openstack-publish-jobs
       - openstack-releasenotes-jobs
-      - openstack-server-release-jobs
+      # A couple of projects import mistral as a library to make
+      # plugins work. Until the mistral-lib work is done, we need to
+      # publish mistral itself to pypi for unit test jobs for those
+      # other projects.
+      # - openstack-server-release-jobs
+      - pypi-jobs
       - 'gate-{name}-python35{suffix}':
           suffix: '-nv'
       - '{pipeline}-{component}-devstack-dsvm':

zuul/layout.yaml

@@ -10929,7 +10929,12 @@ projects:
       - name: python34-jobs
       - name: python35-jobs-nv
       - name: openstack-server-publish-jobs
-      - name: openstack-server-release-jobs
+      # A couple of projects import mistral as a library to make
+      # plugins work. Until the mistral-lib work is done, we need to
+      # publish mistral itself to pypi for unit test jobs for those
+      # other projects.
+      # - name: openstack-server-release-jobs
+      - name: publish-to-pypi
       - name: check-requirements
       - name: release-notes-jobs
     check: