...
- Do not attempt to revert files in releases/ → Even if the release was not needed, we need to keep track on what happened in that repo also the tag needs to be kept in the repo
- Do not attempt to re-tag the repo with the same version → this will fail as the gerrit-release-merge job already tagged it
- Do not modify releases files → Once a releases file is merged, it is immediately processed. If the team needs to release a new build number, please bump your versions and generate another stage-release
- Do not re-use the same stage-release build number for multiple releases files → Once an autorelease package is pushed, it is closed and it cannot be re-released.
FEEDBACK:
Jonathan (AAF):
- I found AAI's "Gizmo" example a bit more helpful than the example listed above, line item 3, because it isn't ONAP specific. AAF's works now as well, if you want to look at that too. Look in "ci-management"
- The new process assumes that you build your Docker Containers with Maven. If you have some other method, you will need to get it to work with Maven. I was able to by using Exec Plugin
- The normal "deploy" for Java Projects in Maven are Jars into Nexus. This, however, is a different step. You can change this up using "Maven Profiles"... I created one just in my Docker Build Directory called "build-docker", which means I could do the following for Maven Params: " install -maven.test.skip exec:exec -Pdocker-build". (note, "Tests already performed twice before... why make this happen again?)
- Do make sure your Docker Build in Maven includes "Push to Docker". LF's Template will cover the Docker Login (they had to add the credentials in my case, once they did, it worked)
- don't miss the "release" file above. Lack of it caused maven to not run at all
- DO NOT BE DISCOURAGED! If you keep cycling, reading the error outputs and pushing through, with LF's help, you'll make it! (Thanks, Jess, Arin, Eric et al)