Add a note regarding deploy maven jobs

Maven deploy jobs still need to remain Jenkins Maven Project types,
perhaps we can take another look at migration to freestyle once upstream
enhancement MNG-5666 is resolved.

    https://issues.apache.org/jira/browse/MNG-5666

Change-Id: Ib8729d426dfdc72cb352ef47233fb8a0b2b8df00
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>

diff --git a/jjb/releng-templates-java.yaml b/jjb/releng-templates-java.yaml
index 9caa5f984e93ffa5fe38c907b96c05972d2b8aee..1226b9ca8b6ac0ed8bd51148cfe75f4b2f7d2e04 100644 (file)
--- a/jjb/releng-templates-java.yaml
+++ b/jjb/releng-templates-java.yaml
@@ -66,6 +66,10 @@
     #     stream:    release stream (eg. stable-lithium or beryllium)
     #     branch:    git branch (eg. stable/lithium or master)
 
+    # Need to keep jobs that deploy to Nexus at end of build as Maven
+    # projects. Maybe reconsider this once upstream moves deploy to a
+    # separate lifecycle:
+    #     https://issues.apache.org/jira/browse/MNG-5666
     project-type: maven
     node: '{build-node}'
     jdk: '{jdk}'
@@ -308,6 +312,10 @@
     #     stream:    release stream (eg. stable-lithium or beryllium)
     #     branch:    git branch (eg. stable/lithium or master)
 
+    # Need to keep jobs that deploy to Nexus at end of build as Maven
+    # projects. Maybe reconsider this once upstream moves deploy to a
+    # separate lifecycle:
+    #     https://issues.apache.org/jira/browse/MNG-5666
     project-type: maven
     node: '{build-node}'
     jdk: '{jdk}'