-
Bug
-
Resolution: Done
-
Medium
-
Guilin Release
-
None
-
None
In our docker maven build. The first sub-module builds a zip artifact. A few sub-modules later, when the actual docker image is being built, we have a shell script that runs several maven commands to retrieve artifacts. One of these artifacts is the zip artifact that was built as part of the first sub-module of the docker build.
On the old docker job, this artifact was found with no problem. You can see this in the attached "old-job.jpg" screen shot. The full log is here: https://jenkins.onap.org/view/appc/job/appc-deployment-master-docker-version-java-daily/605/consoleFull
In the new docker job. It does not find the artifact. It appears to only search in nexus, when previously it was finding the artifact locally. You can see this in the "new-job.jpg" screenshot. The full log is here: https://jenkins.onap.org/job/appc-deployment-maven-docker-stage-master/72/consoleFull
Since it seems to be unable to find the locally built artifact, as a temporary workaround, I changed that version of the artifact that isn't being found to a snapshot version, which exists in nexus (https://gerrit.onap.org/r/c/appc/deployment/+/105017).
A less temporary fix could be copying the platform logic zip file directly from the target directory where it is built.