When the job tries to sign the jar artifacts, it finds the m2repo empty which means there are no artifacts being prepared for deployment. Looks like the build performs an install phase but not a deploy one I think. Do you guys know how to make sure the job actually gathers artifacts to get them ready to sign and deploy?
09:59:26 ERROR: git-review 1.24 requires argparse, which is not installed.
09:59:26 ERROR: openstacksdk 0.31.1 has requirement ipaddress>=1.0.17; python_version < "3.3", but you'll have ipaddress 1.0.16 which is incompatible.
09:59:26 ERROR: openstacksdk 0.31.1 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: pyasn1-modules 0.2.5 has requirement pyasn1<0.5.0,>=0.4.1, but you'll have pyasn1 0.1.9 which is incompatible.
09:59:26 ERROR: python-heatclient 1.16.2 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: oslo-config 6.10.0 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: yq 2.7.2 has requirement PyYAML>=3.11, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: requests 2.22.0 has requirement idna<2.9,>=2.5, but you'll have idna 2.4 which is incompatible.
09:59:26 ERROR: oslo-serialization 2.29.1 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: cliff 2.15.0 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
...
09:59:57 [aai-aai-common-maven-stage-master] $ /w/tools/hudson.tasks.Maven_MavenInstallation/mvn35/bin/mvn -f -s /tmp/settings6002355141556927426.xml -gs /tmp/global-settings1115787293230334266.xml -DGERRIT_BRANCH=master -DPROJECT=aai/aai-common -DMVN=/w/tools/hudson.tasks.Maven_MavenInstallation/mvn35/bin/mvn -DSTREAM=master -DARCHIVE_ARTIFACTS= -DGERRIT_PROJECT=aai/aai-common -Dsha1=origin/master -DMAVEN_OPTS= -DGERRIT_REFSPEC=refs/heads/master -DM2_HOME=/w/tools/hudson.tasks.Maven_MavenInstallation/mvn35 -DSTAGING_PROFILE_ID=176c31dfe190a -DMAVEN_VERSIONS_PLUGIN=true -DMAVEN_PARAMS= -DnewVersion=1.5.2 versions:set versions:update-child-modules versions:commit -B
09:59:57 POM file specified with the -f/--file command line argument does not exist
...
10:00:11 [INFO] Downloading from EvoSuite: http://www.evosuite.org/m2/org/codehaus/mojo/maven-metadata.xml
10:00:11 [WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to EvoSuite (http://www.evosuite.org/m2): Connect to www.evosuite.org:80 [www.evosuite.org/5.9.82.144] failed: Connection refused (Connection refused)
10:00:11 [WARNING] Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to EvoSuite (http://www.evosuite.org/m2): Connect to www.evosuite.org:80 [www.evosuite.org/5.9.82.144] failed: Connection refused (Connection refused)
10:00:11 [INFO] Downloading from EvoSuite: http://www.evosuite.org/m2/org/codehaus/mojo/versions-maven-plugin/maven-metadata.xml
10:00:11 [WARNING] Could not transfer metadata org.codehaus.mojo:versions-maven-plugin/maven-metadata.xml from/to EvoSuite (http://www.evosuite.org/m2): Connect to www.evosuite.org:80 [www.evosuite.org/5.9.82.144] failed: Connection refused (Connection refused)
but it contains some links to internal att.com. Keong Limthe initial doc did, but I cleaned them up, can you point to the spots I missed? - Jimmy
James Forsyth I still see it in: "AID page", related-link in "resource" format example, url in resource_and_url example, simple example, syntax example.
Aha - the hyperlinks didn't update.
Looking forward to further discussion and experimentation!
Understanding the architecture of AAI is not easy - hard to understand how the code is laid out and how things flow. Need documention which will describe how the microservices are connected, which repos support which functions, etc. Pavel Paroulek says that he had to reverse engineer the dependencies to see how the repos are connected. Recommended to focus on the resources repo for understanding the core function of AAI.
The Docker and Kubernetes engines may run as root until such time as the products support non-root execution.
Applications may run as root within a container.
The process ID of a container must not run as the root ID with the exception of containers supporting ONAP features that require the container to run as the root ID.
Containers may run with root privileges.
Project containers that run as the root ID must document this in the release notes along with the functionality that requires the container to run as the root ID.
project = AAI AND issuetype = Bug and status not in (Closed, Delivered) ORDER BY fixVersion ASC, priority DESC, updated ASC
count
true
serverId
425b2b0a-557c-3c0c-b515-579789cceedb
JIRA Issue Count (talking about AAI):
Jira
server
ONAP JIRA
jqlQuery
project != AAI AND (text ~ "AAI" OR text ~ "A?AI" OR text ~ "A??AI" OR text ~ "A???AI") AND issuetype = Bug and status not in (Closed,Delivered,Done) ORDER BY priority DESC, updated ASC
