If you see below error while building images

[0m[91m2[0m[91m8[0m[91m2[0m[91m9[0m[91m
18:58:16 [0m[91m
18:58:16 gzip: stdin: not in gzip format
18:58:16 [0m[91mtar: [0m[91mChild returned status 1[0m[91m
18:58:16 [0m[91mtar: [0m[91mError is not recoverable: exiting now[0m[91m
18:58:16 [0m"chmod 755 /usr/local/bin/containeragent-watchdog.sh" command filed with exit code 2.
18:58:16 The command '/bin/sh -c /home/builder/docker-build/nosql-install.sh' returned a non-zero code: 2
18:58:16 ~/jobs/build_docker/workspace
18:58:16 Finished: SUCCESS
Please read further and follow the steps mentioned in Resolution.

As of Jan 15 2020, maven changed their policy and now central repo only supports https calls. (https://support.sonatype.com/hc/en-us/articles/3600412873340. This is causing the TIBCO provided Jenkins build jobs to fail for ML 5.3.0 HF1, ML 5.3.0 & lower versions

 In this article, we are providing scripts (attached) that will cater to this change - reference the maven central repositories using https instead of http.

This article has scripts to fix maven host build issues for ML 5.3.0 HF1, ML 5.3.0 & lower versions

Steps to be followed for ML 5.3.0 & lower versions

1. copy "fix_maven_host_for_TML_5.3.0.sh"  to the host where TML Installer is running, i.e.
for TML 5.3.0 & lower versions
scp fix_maven_host_for_TML_5.3.0.sh root@TML_INSTALLER_HOST:/root/fix_maven_host_for_TML_5.3.0.sh

2. Login to TML Installer host, set execute permission to "fix_maven_host_for_TML_5.3.0.sh" i.e.
chmod +x /root/fix_maven_host_for_TML_5.3.0.sh

3. copy "fix_maven_host_for_TML_5.3.0.sh" to TML Installer, i.e.
docker cp /root/fix_maven_host_for_TML_5.3.0.sh tml-installer:/root

4. execute "fix_maven_host_for_TML_5.3.0.sh" in TML Installer host, i.e.
docker exec -it -u root tml-installer /root/fix_maven_host_for_TML_5.3.0.sh

Steps to be followed for ML 5.3.0 HF1

1. copy "fix_maven_host_for_TML_5.3.0-HF1.sh"  to the host where TML Installer is running, i.e.
for TML 5.3.0 HF1
scp fix_maven_host_for_TML_5.3.0-HF1.sh root@TML_INSTALLER_HOST:/root/fix_maven_host_for_TML_5.3.0-HF1.sh

2. Login to TML Installer host, set execute permission to "fix_maven_host_for_TML_5.3.0-HF1.sh" i.e.
chmod +x /root/fix_maven_host_for_TML_5.3.0-HF1.sh

3. copy "fix_maven_host_for_TML_5.3.0-HF1.sh" to TML Installer, i.e.
docker cp /root/fix_maven_host_for_TML_5.3.0-HF1.sh tml-installer:/root

4. execute "fix_maven_host_for_TML_5.3.0-HF1.sh" in TML Installer host, i.e.
docker exec -it -u root tml-installer /root/fix_maven_host_for_TML_5.3.0-HF1.sh


Steps to be followed for quick start

1. Start the quick start 

./quick-start.sh -b true -d true

2. Once the TML installer is up, we can stop the script and apply the Maven fix like below

3. Set execute permission to "fix_maven_host_for_TML_5.3.0.sh" i.e.
chmod +x fix_maven_host_for_TML_5.3.0.sh

4. copy "fix_maven_host_for_TML_5.3.0.sh" to TML Installer, i.e.
docker cp fix_maven_host_for_TML_5.3.0.sh tml-installer:/root

5. execute "fix_maven_host_for_TML_5.3.0.sh" in TML Installer host, i.e.
docker exec -it -u root tml-installer /root/fix_maven_host_for_TML_5.3.0.sh

6. Once the maven host fix is applied, run the quick start again (./quick-start.sh -b true -d true) to build the images successfully