From: Lott, Christopher (cl778h) <cl778h@att.com>
Date: Tue, 21 Apr 2020 19:55:20 +0000 (-0400)
Subject: Drop removed CLM jobs from python job groups
X-Git-Tag: v0.53.2~1^2
X-Git-Url: https://gerrit.linuxfoundation.org/infra/gitweb?a=commitdiff_plain;h=refs%2Fchanges%2F46%2F63746%2F2;p=releng%2Fglobal-jjb.git

Drop removed CLM jobs from python job groups

Drop jobs gerrit-python-xc-clm and github-python-xc-clm from
the two python job groups. Those templates were replaced by
gerrit-tox-nexus-iq-clm and github-tox-nexus-iq-clm. Not adding
those templates to the job groups because successful use requires
additional project configuration to report the package requirements.

Totally baffling that the tox test didn't catch this botch in the
change set that removed those templates.

Change-Id: Ibea19818ebf45cfc541cf910fe90cc3b1b3579ca
Issue-ID: RELENG-2821
Signed-off-by: Lott, Christopher (cl778h) <cl778h@att.com>
---

diff --git a/jjb/lf-python-job-groups.yaml b/jjb/lf-python-job-groups.yaml
index ad022355..11b31107 100644
--- a/jjb/lf-python-job-groups.yaml
+++ b/jjb/lf-python-job-groups.yaml
@@ -6,7 +6,6 @@
     # for a Gerrit-based Python project to verify commits using tox.
 
     jobs:
-      - gerrit-python-xc-clm
       - gerrit-tox-verify
       - gerrit-tox-merge
 
@@ -17,7 +16,6 @@
     # for a Github-based Python project to verify commits using tox.
 
     jobs:
-      - github-python-xc-clm
       - github-tox-verify
       - github-tox-merge
 
diff --git a/releasenotes/notes/tox-nexus-iq-python-job-groups-3fda2e30d7f3e5ef.yaml b/releasenotes/notes/tox-nexus-iq-python-job-groups-3fda2e30d7f3e5ef.yaml
new file mode 100644
index 00000000..822e7d8d
--- /dev/null
+++ b/releasenotes/notes/tox-nexus-iq-python-job-groups-3fda2e30d7f3e5ef.yaml
@@ -0,0 +1,15 @@
+---
+fixes:
+  - |
+    Drop jobs gerrit-python-xc-clm and github-python-xc-clm from
+    the two python job groups. Those templates were replaced by
+    gerrit-tox-nexus-iq-clm and github-tox-nexus-iq-clm. Not adding
+    those templates to the job groups because successful use requires
+    additional project configuration to report the package requirements.
+
+upgrade:
+  - |
+    Before upgrading to this version of global-jjb, must remove any uses
+    of the job templates named above.  These jobs did not yield any results,
+    so it's unlikely they were being used, and dropping them entirely
+    should not cause any loss of information.