search

odpi / ci-management

3 stars 7 forks source link

Publish egeria docker images to dockerhub using odpi organization #44

Closed planetf1 closed 4 years ago

planetf1 commented 5 years ago

As part of the egeria build process we create docker images for a variety of components. For example the core egeria code is built at https://github.com/odpi/egeria/tree/master/open-metadata-resources/open-metadata-deployment/docker/egeria

Currently these are either built locally, or for general consumption I have posted using my docker repo 'planetf1' . for example see https://cloud.docker.com/u/planetf1/repository/docker/planetf1/egeria-egeriavdc

We need to ensure that anyone can pull these images for use - including as part of deploying out helm chart such as https://github.com/odpi/egeria/tree/master/open-metadata-resources/open-metadata-deployment/charts/vdc

There is already an odpi organization on dockerhub - see https://hub.docker.com/r/odpi/ci

can we make use of this as part of our build process. Since the images take a while to build this is an optional extension to the regular build process

mvn clean install -Ddocker -Ddocker.repo=odpi

should suffice

However it would be interesting to see what 'best practice' is in this space - for example how do other linux foundation projects tackle this.

Another approach is to configure dockerhub itself to perform the image build for us.

I should also note that we are posting egeria code, and that of other projects we use, though all are Apache 2.0 licensed.

schannamallu commented 5 years ago

I'm not familiar with the docker stuff in linux foundation, i'll get more details about this docker process implemented in other linux foundation projects and i'll get back to you asap.

schannamallu commented 5 years ago

Below is the information I gathered regarding docker build

GIT --> Jenkins job cloning the repository having Dockerfile --> using docker commands to build the docker image, then tag the image , so that the image can be pushed to the DockerHub repository.

Once the image is available in the docker hub repository, users who have authorization to the docker hub repository can pull the images , and using docker run we can deploy the container to target server by using the images present in the dockerhub

(For achieving above, we need to install Docker plugin and make sure the Docker is installed on the Docker hsot where the image has to be built/container has to be deployed)

Could you please give us reference to any sample jenkins pipeline job , which builds the docker image from Dockerfile and deploys the container on the target server

schannamallu commented 5 years ago

@planetf1 , Using maven and docker option checking the docker push in sandbox. Getting some issues will try to fix them. Will post you the update once done.

planetf1 commented 5 years ago

Thanks. feel free to msg if you have trouble with the maven setup. Open to suggestions as to the best way to run.

NOTE I found a bug yesterday on the RANGER build. I will submit a fix for that shortly -> https://github.com/odpi/egeria/pull/870 will merge asap

schannamallu commented 5 years ago

@planetf1 Thanks for offering assistance. As suggested in our earlier thread,
mvn clean install -Ddocker -Ddocker.repo=odpi Parameter has been added. For some reason, Jobs are failing. Below is the error message for your reference.

[ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.10:build (build-and-tag-latest) on project open-metadata-docker-atlas: Could not build image: java.util.concurrent.ExecutionException: com.spotify.docker.client.shaded.javax.ws.rs.ProcessingException: java.io.IOException: No such file or directory -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.10:build (build-and-tag-latest) on project open-metadata-docker-atlas: Could not build image at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)

planetf1 commented 5 years ago

is docker installed on the build machine?

schannamallu commented 5 years ago

@planetf1 , Image I am using by default contains the docker.. Not sure why I am getting the above issue.

planetf1 commented 5 years ago

Do you have the complete log?

schannamallu commented 5 years ago

@planetf1 We installed Docker Binary and started Docker Service. However, we getting different error now. It says, Permission Denied with UNIX SOCKET Issue. It is sounding like, Maven is executing as docker binary as Normal user. Any direction here would be much appreciated.

Error Message Below for your reference.

[ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.10:build (build-and-tag-latest) on project open-metadata-docker-atlas: Could not build image: java.util.concurrent.ExecutionException: com.spotify.docker.client.shaded.javax.ws.rs.ProcessingException: java.io.IOException: Permission denied -> [Help 1]


    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Could not build image
    at com.spotify.plugin.dockerfile.BuildMojo.buildImage (BuildMojo.java:234)
    at com.spotify.plugin.dockerfile.BuildMojo.execute (BuildMojo.java:129)
    at com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute (AbstractDockerMojo.java:265)
    at com.spotify.plugin.dockerfile.AbstractDockerMojo.execute (AbstractDockerMojo.java:254)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: com.spotify.docker.client.exceptions.DockerException: java.util.concurrent.ExecutionException: com.spotify.docker.client.shaded.javax.ws.rs.ProcessingException: java.io.IOException: Permission denied
    at com.spotify.docker.client.DefaultDockerClient.propagate (DefaultDockerClient.java:2828)
    at com.spotify.docker.client.DefaultDockerClient.request (DefaultDockerClient.java:2692)
    at com.spotify.docker.client.DefaultDockerClient.version (DefaultDockerClient.java:580)
    at com.spotify.docker.client.DefaultDockerClient.authRegistryHeader (DefaultDockerClient.java:2871)
    at com.spotify.docker.client.DefaultDockerClient.build (DefaultDockerClient.java:1478)
    at com.spotify.docker.client.DefaultDockerClient.build (DefaultDockerClient.java:1445)
    at com.spotify.plugin.dockerfile.BuildMojo.buildImage (BuildMojo.java:227)
    at com.spotify.plugin.dockerfile.BuildMojo.execute (BuildMojo.java:129)
    at com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute (AbstractDockerMojo.java:265)
    at com.spotify.plugin.dockerfile.AbstractDockerMojo.execute (AbstractDockerMojo.java:254)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: java.util.concurrent.ExecutionException: com.spotify.docker.client.shaded.javax.ws.rs.ProcessingException: java.io.IOException: Permission denied
    at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.getValue (AbstractFuture.java:299)
    at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.get (AbstractFuture.java:286)
    at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture.get (AbstractFuture.java:116)
    at com.spotify.docker.client.DefaultDockerClient.request (DefaultDockerClient.java:2690)
    at com.spotify.docker.client.DefaultDockerClient.version (DefaultDockerClient.java:580)
    at com.spotify.docker.client.DefaultDockerClient.authRegistryHeader (DefaultDockerClient.java:2871)
    at com.spotify.docker.client.DefaultDockerClient.build (DefaultDockerClient.java:1478)
    at com.spotify.docker.client.DefaultDockerClient.build (DefaultDockerClient.java:1445)
    at com.spotify.plugin.dockerfile.BuildMojo.buildImage (BuildMojo.java:227)
    at com.spotify.plugin.dockerfile.BuildMojo.execute (BuildMojo.java:129)
    at com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute (AbstractDockerMojo.java:265)
    at com.spotify.plugin.dockerfile.AbstractDockerMojo.execute (AbstractDockerMojo.java:254)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: com.spotify.docker.client.shaded.javax.ws.rs.ProcessingException: java.io.IOException: Permission denied
    at com.spotify.docker.client.shaded.org.glassfish.jersey.apache.connector.ApacheConnector.apply (ApacheConnector.java:481)
    at com.spotify.docker.client.shaded.org.glassfish.jersey.apache.connector.ApacheConnector$1.run (ApacheConnector.java:491)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)```
schannamallu commented 5 years ago

@planetf1 Somehow, it is reading egeria docker pom.xml. However, i am getting localhost:80 No Such file ERROR. Any direction here would be much appreciated. 


[INFO] Installing /w/workspace/odpi-egeria-sonar/open-metadata-resources/open-metadata-deployment/docker/atlas/pom.xml to /tmp/r/org/odpi/egeria/open-metadata-docker-atlas/1.1-SNAPSHOT/open-metadata-docker-atlas-1.1-SNAPSHOT.pom
[INFO] 
[INFO] --- dockerfile-maven-plugin:1.4.10:build (build-and-tag-latest) @ open-metadata-docker-atlas ---
[INFO] dockerfile: null
[INFO] contextDirectory: /w/workspace/odpi-egeria-sonar/open-metadata-resources/open-metadata-deployment/docker/atlas
[INFO] Building Docker context /w/workspace/odpi-egeria-sonar/open-metadata-resources/open-metadata-deployment/docker/atlas
[INFO] Path(dockerfile): null
[INFO] Path(contextDirectory): /w/workspace/odpi-egeria-sonar/open-metadata-resources/open-metadata-deployment/docker/atlas
[INFO] 
[INFO] Image will be built as registry-1.docker.io/odpi/apache-atlas:latest
[INFO] 
Mar 22, 2019 6:10:20 PM com.spotify.docker.client.shaded.org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
Mar 22, 2019 6:10:20 PM com.spotify.docker.client.shaded.org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {}->unix://localhost:80
Mar 22, 2019 6:10:20 PM com.spotify.docker.client.shaded.org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
Mar 22, 2019 6:10:20 PM com.spotify.docker.client.shaded.org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {}->unix://localhost:80
Mar 22, 2019 6:10:20 PM com.spotify.docker.client.shaded.org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
Mar 22, 2019 6:10:20 PM com.spotify.docker.client.shaded.org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {}->unix://localhost:80
[WARNING] An attempt failed, will retry 1 more times```
schannamallu commented 5 years ago

@planetf1 these is are error log getting when i am running build

" [INFO] Docker image - Atlas ............................... FAILURE [ 4.134 s] [INFO] Docker image - Configuration ....................... SKIPPED [INFO] Docker image - Egeria .............................. SKIPPED [INFO] Docker image - Gaian ............................... SKIPPED [INFO] Docker image - OMRS Monitor ........................ SKIPPED [INFO] Docker image - Ranger .............................. SKIPPED [INFO] Open Metadata Test Resources ....................... SKIPPED [INFO] Open Metadata Access Service FVT Resources ......... SKIPPED [INFO] Open Metadata Test Resources ....................... SKIPPED [INFO] Asset Consumer OMAS FVT ............................ SKIPPED [INFO] Subject Area OMAS FVT 1.1-SNAPSHOT ................. SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 08:20 min [INFO] Finished at: 2019-03-27T08:48:57Z [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.10:build (build-and-tag-latest) on project open-metadata-docker-atlas: Could not build image: java.util.concurrent.ExecutionException: com.spotify.docker.client.shaded.javax.ws.rs.ProcessingException: java.io.IOException: Permission denied -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.10:build (build-and-tag-latest) on project open-metadata-docker-atlas: Could not build image at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) "

FYI :https://github.com/spotify/dockerfile-maven/issues/272

schannamallu commented 5 years ago

@planetf1

planetf1 commented 5 years ago

Thanks. I'll be interested to hear how you get on

schannamallu commented 5 years ago

@planetf1 , Finally we are able to start the docker builder. Now docker image build step is starting. But its failing while executing apache-atlas snapshot. Is some thing we need to change in the build code. https://jenkins.odpi.org/sandbox/view/All/job/odpi-egeria-sonar/8/console Logs: Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/groovy/groovy-all/2.4.0/groovy-all-2.4.0.jar (6.9 MB at 3.1 MB/s) [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Reactor Summary: [INFO] [INFO] [INFO] [INFO] Apache Atlas Server Build Tools 1.0 ................ SUCCESS [ 10.439 s] [INFO] [INFO] apache-atlas 2.0.0-SNAPSHOT ........................ FAILURE [ 35.224 s] [INFO] [INFO] Apache Atlas Test Utility Tools 2.0.0-SNAPSHOT ..... SKIPPED [INFO] [INFO] Apache Atlas Integration 2.0.0-SNAPSHOT ............ SKIPPED [INFO] [INFO] Apache Atlas Client 2.0.0-SNAPSHOT ................. SKIPPED [INFO] [INFO] atlas-client-common 2.0.0-SNAPSHOT ................. SKIPPED [INFO] [INFO] Apache Atlas Common 2.0.0-SNAPSHOT ................. SKIPPED [INFO] [INFO] atlas-client-v1 2.0.0-SNAPSHOT ..................... SKIPPED [INFO] [INFO] Apache Atlas Server API 2.0.0-SNAPSHOT ............. SKIPPED [INFO] [INFO] Apache Atlas Graph Database Projects 2.0.0-SNAPSHOT SKIPPED [INFO] [INFO] Apache Atlas Graph Database API 2.0.0-SNAPSHOT ..... SKIPPED [INFO] [INFO] Graph Database Common Code 2.0.0-SNAPSHOT .......... SKIPPED [INFO] [INFO] Apache Atlas JanusGraph DB Impl 2.0.0-SNAPSHOT ..... SKIPPED [INFO] [INFO] Apache Atlas Graph Database Implementation Dependencies 2.0.0-SNAPSHOT SKIPPED [INFO] [INFO] Apache Atlas Authorization 2.0.0-SNAPSHOT .......... SKIPPED [INFO] [INFO] Shaded version of Apache hbase client 2.0.0-SNAPSHOT SKIPPED [INFO] [INFO] Shaded version of Apache hbase server 2.0.0-SNAPSHOT SKIPPED [INFO] [INFO] Apache Atlas Repository 2.0.0-SNAPSHOT ............. SKIPPED [INFO] [INFO] Apache Atlas Notification 2.0.0-SNAPSHOT ........... SKIPPED [INFO] [INFO] Open Metadata support for Atlas 2.0.0-SNAPSHOT ..... SKIPPED [INFO] [INFO] atlas-client-v2 2.0.0-SNAPSHOT ..................... SKIPPED [INFO] [INFO] Apache Atlas UI 2.0.0-SNAPSHOT ..................... SKIPPED [INFO] [INFO] Apache Atlas Web Application 2.0.0-SNAPSHOT ........ SKIPPED [INFO] [INFO] Apache Atlas Documentation 2.0.0-SNAPSHOT .......... SKIPPED [INFO] [INFO] Apache Atlas FileSystem Model 2.0.0-SNAPSHOT ....... SKIPPED [INFO] [INFO] Apache Atlas Plugin Classloader 2.0.0-SNAPSHOT ..... SKIPPED [INFO] [INFO] Apache Atlas Hive Bridge Shim 2.0.0-SNAPSHOT ....... SKIPPED [INFO] [INFO] Apache Atlas Hive Bridge 2.0.0-SNAPSHOT ............ SKIPPED [INFO] [INFO] Apache Atlas Falcon Bridge Shim 2.0.0-SNAPSHOT ..... SKIPPED [INFO] [INFO] Apache Atlas Falcon Bridge 2.0.0-SNAPSHOT .......... SKIPPED [INFO] [INFO] Apache Atlas Sqoop Bridge Shim 2.0.0-SNAPSHOT ...... SKIPPED [INFO] [INFO] Apache Atlas Sqoop Bridge 2.0.0-SNAPSHOT ........... SKIPPED [INFO] [INFO] Apache Atlas Storm Bridge Shim 2.0.0-SNAPSHOT ...... SKIPPED [INFO] [INFO] Apache Atlas Storm Bridge 2.0.0-SNAPSHOT ........... SKIPPED [INFO] [INFO] Apache Atlas Hbase Bridge Shim 2.0.0-SNAPSHOT ...... SKIPPED [INFO] [INFO] Apache Atlas Hbase Bridge 2.0.0-SNAPSHOT ........... SKIPPED [INFO] [INFO] Apache Atlas Kafka Bridge 2.0.0-SNAPSHOT ........... SKIPPED [INFO] [INFO] Apache Atlas Distribution 2.0.0-SNAPSHOT ........... SKIPPED [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] BUILD FAILURE [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Total time: 55.293 s [INFO] [INFO] Finished at: 2019-04-17T19:37:29Z [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.1:findbugs (findbugs) on project apache-atlas: Unable to parse configuration of mojo org.codehaus.mojo:findbugs-maven-plugin:3.0.1:findbugs for parameter pluginArtifacts: Cannot assign configuration entry 'pluginArtifacts' with value '${plugin.artifacts}' of type java.util.Collections.UnmodifiableRandomAccessList to property of type java.util.ArrayList -> [Help 1] [INFO] [ERROR] [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [INFO] [ERROR] [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles: [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginConfigurationException [INFO] [ERROR] [INFO] [ERROR] After correcting the problems, you can resume the build with the command [INFO] [ERROR] mvn -rf :apache-atlas [ERROR] The command '/bin/sh -c mvn clean install -DskipTests -Pdist,embedded-hbase-solr -f ./atlas/pom.xml' returned a non-zero code: 1

planetf1 commented 5 years ago

Ah yes -- we noticed that broke a couple of days ago when we do the build ourselves.

There is a PR to fix -> https://github.com/odpi/egeria/pull/920 I expect we will merge today or tomorrow.

Thanks! Great news....

planetf1 commented 5 years ago

i have now merged the PR, so hopefully the docker build will no pass. can you retry? thanks

schannamallu commented 5 years ago

@planetf1, Now my odpi job able to create docker image.. Got an issue while pushing that image to docker hub.. Looks like the login issue. Debugging further.

Logs: [INFO] --- dockerfile-maven-plugin:1.4.10:push (push-latest) @ open-metadata-docker-atlas --- [INFO] The push refers to repository [registry-1.docker.io/odpi/apache-atlas] [INFO] Image d1169bb4f2ab: Preparing [INFO] Image 2d44fc6f9192: Preparing [INFO] Image 219c1f709425: Preparing [INFO] Image cab01ebf7b3d: Preparing [INFO] Image 5b4ccbb5d868: Preparing [INFO] Image ee610d18148e: Preparing [INFO] Image dee6aef5c2b6: Preparing [INFO] Image a464c54f93a9: Preparing [INFO] Image ee610d18148e: Waiting [INFO] Image dee6aef5c2b6: Waiting [INFO] Image a464c54f93a9: Waiting [ERROR] denied: requested access to the resource is denied [WARNING] An attempt failed, will retry 1 more times org.apache.maven.plugin.MojoExecutionException: Could not push image at com.spotify.plugin.dockerfile.PushMojo.execute (PushMojo.java:90) at com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute (AbstractDockerMojo.java:265) at com.spotify.plugin.dockerfile.AbstractDockerMojo.execute (AbstractDockerMojo.java:254)

schannamallu commented 5 years ago

@planetf1, The odpi organization on dockerhub - see https://hub.docker.com/r/odpi/ci , Can I push images using any credentials or I need to use specific odpi credentials. Can you grant the permissions for user - odpiadmin.

schannamallu commented 5 years ago

@planetf1 i am getting this error in below "" https://jenkins.odpi.org/sandbox/view/All/job/odpi-egeria-sonar/3/console INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Reactor Summary: [INFO] [INFO] [INFO] [INFO] Apache Atlas Server Build Tools 1.0 ................ SUCCESS [ 4.921 s] [INFO] [INFO] apache-atlas 2.0.0-SNAPSHOT ........................ SUCCESS [ 29.047 s] [INFO] [INFO] Apache Atlas Test Utility Tools 2.0.0-SNAPSHOT ..... SUCCESS [ 38.081 s] [INFO] [INFO] Apache Atlas Integration 2.0.0-SNAPSHOT ............ SUCCESS [ 51.547 s] [INFO] [INFO] Apache Atlas Client 2.0.0-SNAPSHOT ................. SUCCESS [ 1.326 s] [INFO] [INFO] atlas-client-common 2.0.0-SNAPSHOT ................. SUCCESS [ 12.992 s] [INFO] [INFO] Apache Atlas Common 2.0.0-SNAPSHOT ................. SUCCESS [ 15.386 s] [INFO] [INFO] atlas-client-v1 2.0.0-SNAPSHOT ..................... SUCCESS [ 13.943 s] [INFO] [INFO] Apache Atlas Server API 2.0.0-SNAPSHOT ............. SUCCESS [ 10.334 s] [INFO] [INFO] Apache Atlas Graph Database Projects 2.0.0-SNAPSHOT SUCCESS [ 0.788 s] [INFO] [INFO] Apache Atlas Graph Database API 2.0.0-SNAPSHOT ..... SUCCESS [ 12.999 s] [INFO] [INFO] Graph Database Common Code 2.0.0-SNAPSHOT .......... SUCCESS [ 9.943 s] [INFO] [INFO] Apache Atlas JanusGraph DB Impl 2.0.0-SNAPSHOT ..... SUCCESS [ 57.475 s] [INFO] [INFO] Apache Atlas Graph Database Implementation Dependencies 2.0.0-SNAPSHOT SUCCESS [ 3.493 s] [INFO] [INFO] Apache Atlas Authorization 2.0.0-SNAPSHOT .......... SUCCESS [ 14.406 s] [INFO] [INFO] Shaded version of Apache hbase client 2.0.0-SNAPSHOT SUCCESS [ 16.281 s] [INFO] [INFO] Shaded version of Apache hbase server 2.0.0-SNAPSHOT SUCCESS [ 23.944 s] [INFO] [INFO] Apache Atlas Repository 2.0.0-SNAPSHOT ............. SUCCESS [01:13 min] [INFO] [INFO] Apache Atlas Notification 2.0.0-SNAPSHOT ........... SUCCESS [ 19.740 s] [INFO] [INFO] Open Metadata support for Atlas 2.0.0-SNAPSHOT ..... SUCCESS [01:16 min] [INFO] [INFO] atlas-client-v2 2.0.0-SNAPSHOT ..................... SUCCESS [ 10.550 s] [INFO] [INFO] Apache Atlas UI 2.0.0-SNAPSHOT ..................... SUCCESS [01:13 min] [INFO] [INFO] Apache Atlas Web Application 2.0.0-SNAPSHOT ........ SUCCESS [01:52 min] [INFO] [INFO] Apache Atlas Documentation 2.0.0-SNAPSHOT .......... SUCCESS [ 16.574 s] [INFO] [INFO] Apache Atlas FileSystem Model 2.0.0-SNAPSHOT ....... SUCCESS [ 5.294 s] [INFO] [INFO] Apache Atlas Plugin Classloader 2.0.0-SNAPSHOT ..... SUCCESS [ 10.253 s] [INFO] [INFO] Apache Atlas Hive Bridge Shim 2.0.0-SNAPSHOT ....... SUCCESS [ 17.269 s] [INFO] [INFO] Apache Atlas Hive Bridge 2.0.0-SNAPSHOT ............ SUCCESS [ 26.936 s] [INFO] [INFO] Apache Atlas Falcon Bridge Shim 2.0.0-SNAPSHOT ..... SUCCESS [ 14.237 s] [INFO] [INFO] Apache Atlas Falcon Bridge 2.0.0-SNAPSHOT .......... SUCCESS [ 13.278 s] [INFO] [INFO] Apache Atlas Sqoop Bridge Shim 2.0.0-SNAPSHOT ...... SUCCESS [ 6.596 s] [INFO] [INFO] Apache Atlas Sqoop Bridge 2.0.0-SNAPSHOT ........... SUCCESS [ 13.454 s] [INFO] [INFO] Apache Atlas Storm Bridge Shim 2.0.0-SNAPSHOT ...... SUCCESS [ 12.574 s] [INFO] [INFO] Apache Atlas Storm Bridge 2.0.0-SNAPSHOT ........... SUCCESS [ 15.130 s] [INFO] [INFO] Apache Atlas Hbase Bridge Shim 2.0.0-SNAPSHOT ...... SUCCESS [ 13.988 s] [INFO] [INFO] Apache Atlas Hbase Bridge 2.0.0-SNAPSHOT ........... SUCCESS [ 24.662 s] [INFO] [INFO] Apache Atlas Kafka Bridge 2.0.0-SNAPSHOT ........... SUCCESS [ 10.830 s] [INFO] [INFO] Apache Atlas Distribution 2.0.0-SNAPSHOT ........... SUCCESS [12:29 min] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Total time: 27:21 min [INFO] [INFO] Finished at: 2019-04-22T20:28:49Z [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Removing intermediate container 81d184b919e0 [INFO] ---> 2910091bffcd [INFO] Step 25/41 : RUN mkdir -p atlas-bin [INFO] [INFO] ---> Running in 91a793b5ec68 [INFO] Removing intermediate container 91a793b5ec68 [INFO] ---> 0bfef85e8936 [INFO] Step 26/41 : RUN tar xzf /root/atlas/distro/target/bin.tar.gz --strip-components 1 -C /root/atlas-bin [INFO] [INFO] ---> Running in e08a270ba2f3 [INFO] Removing intermediate container e08a270ba2f3 [INFO] ---> 84e7a873043a [INFO] Step 27/41 : WORKDIR /root/atlas [INFO] [INFO] ---> Running in 3cdcd3683f1f [INFO] Removing intermediate container 3cdcd3683f1f [INFO] ---> b825a92f6217 [INFO] Step 28/41 : RUN git log > git.log && echo ${branch} > git.branch && git remote -v >> git.remote [INFO] [INFO] ---> Running in fb8c07442701 [INFO] Removing intermediate container fb8c07442701 [INFO] ---> 7cdf9c96757e [INFO] Step 29/41 : FROM openjdk:8-jdk-alpine [INFO] [INFO] Pulling from library/openjdk [INFO] Image bdf0201b3a05: Pulling fs layer [INFO] Image 9e12771959ad: Pulling fs layer [INFO] Image c4efe34cda6e: Pulling fs layer [INFO] Image bdf0201b3a05: Downloading [INFO] Image 9e12771959ad: Downloading [INFO] Image 9e12771959ad: Verifying Checksum [INFO] Image 9e12771959ad: Download complete [INFO] Image c4efe34cda6e: Downloading [INFO] Image bdf0201b3a05: Verifying Checksum [INFO] Image bdf0201b3a05: Download complete [INFO] Image bdf0201b3a05: Extracting [INFO] Image c4efe34cda6e: Verifying Checksum [INFO] Image c4efe34cda6e: Download complete [INFO] Image bdf0201b3a05: Pull complete [INFO] Image 9e12771959ad: Extracting [INFO] Image 9e12771959ad: Pull complete [INFO] Image c4efe34cda6e: Extracting [INFO] Image c4efe34cda6e: Pull complete [INFO] Digest: sha256:2a52fedf1d4ab53323e16a032cadca89aac47024a8228dea7f862dbccf169e1e [INFO] Status: Downloaded newer image for openjdk:8-jdk-alpine [INFO] ---> 3675b9f543c5 [INFO] Step 30/41 : RUN apk add python bash [INFO] [INFO] ---> Running in 96560a2384ae [INFO] fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/main/x86_64/APKINDEX.tar.gz [INFO] fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/community/x86_64/APKINDEX.tar.gz [INFO] (1/8) Installing ncurses-terminfo-base (6.1_p20190105-r0) [INFO] (2/8) Installing ncurses-terminfo (6.1_p20190105-r0) [INFO] (3/8) Installing ncurses-libs (6.1_p20190105-r0) [INFO] (4/8) Installing readline (7.0.003-r1) [INFO] (5/8) Installing bash (4.4.19-r1) [INFO] Executing bash-4.4.19-r1.post-install [INFO] (6/8) Installing expat (2.2.6-r0) [INFO] (7/8) Installing gdbm (1.13-r1) [INFO] (8/8) Installing python2 (2.7.15-r3) [INFO] Executing busybox-1.29.3-r10.trigger [INFO] OK: 151 MiB in 62 packages [INFO] Removing intermediate container 96560a2384ae [INFO] ---> d26765ff67f1 [INFO] Step 31/41 : COPY --from=build /root/atlas-bin/ /root/atlas-bin/ [INFO] [INFO] ---> 2cc6a3e36a2c [INFO] Step 32/41 : COPY --from=build /root/atlas/git. / [INFO] [INFO] ---> 25c0e175a3f4 [INFO] Step 33/41 : WORKDIR /root/atlas-bin/conf [INFO] [INFO] ---> Running in e8646b9de305 [INFO] Removing intermediate container e8646b9de305 [INFO] ---> 35c18df69125 [INFO] Step 34/41 : RUN sed -i "s|^atlas.graph.storage.lock.wait-time=10000|atlas.graph.storage.lock.wait-time=100|g" atlas-application.properties [INFO] [INFO] ---> Running in ba6bfa29fa02 [INFO] Removing intermediate container ba6bfa29fa02 [INFO] ---> 1c99577ed616 [INFO] Step 35/41 : RUN echo "atlas.notification.relationships.enabled=true" >> atlas-application.properties [INFO] [INFO] ---> Running in 2eb575dd74f7 [INFO] Removing intermediate container 2eb575dd74f7 [INFO] ---> dc75078ec874 [INFO] Step 36/41 : ENV JAVA_TOOL_OPTIONS="-Xmx1024m" [INFO] [INFO] ---> Running in edef49387533 [INFO] Removing intermediate container edef49387533 [INFO] ---> 88d09fedc21c [INFO] Step 37/41 : ENV MANAGE_LOCAL_SOLR true [INFO] [INFO] ---> Running in 0e11609e6500 [INFO] Removing intermediate container 0e11609e6500 [INFO] ---> d82516059feb [INFO] Step 38/41 : ENV MANAGE_LOCAL_HBASE true [INFO] [INFO] ---> Running in f5c059ad92a5 [INFO] Removing intermediate container f5c059ad92a5 [INFO] ---> 28bb0968c052 [INFO] Step 39/41 : ENV PATH /root/atlas-bin/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin [INFO] [INFO] ---> Running in 5abc1604b352 [INFO] Removing intermediate container 5abc1604b352 [INFO] ---> e280dcc46943 [INFO] Step 40/41 : EXPOSE 21000 [INFO] [INFO] ---> Running in 8a4ee0d031b3 [INFO] Removing intermediate container 8a4ee0d031b3 [INFO] ---> 1111643ef8fc [INFO] Step 41/41 : ENTRYPOINT ["/bin/bash", "-c", "/root/atlas-bin/bin/atlas_start.py; tail -fF /root/atlas-bin/logs/application.log"] [INFO] [INFO] ---> Running in bc3b631a791c [INFO] Removing intermediate container bc3b631a791c [INFO] ---> 2ac76fce6938 [INFO] Successfully built 2ac76fce6938 [INFO] Successfully tagged registry-1.docker.io/odpi/apache-atlas:latest [INFO] [INFO] Detected build of image with id 2ac76fce6938 [INFO] Building jar: /w/workspace/odpi-egeria-sonar/open-metadata-resources/open-metadata-deployment/docker/atlas/target/open-metadata-docker-atlas-1.1-SNAPSHOT-docker-info.jar [INFO] Successfully built registry-1.docker.io/odpi/apache-atlas:latest [INFO] [INFO] --- dockerfile-maven-plugin:1.4.10:tag (tag-version) @ open-metadata-docker-atlas --- [INFO] Tagging image 2ac76fce6938 as registry-1.docker.io/odpi/apache-atlas:1.1-SNAPSHOT [INFO] Building jar: /w/workspace/odpi-egeria-sonar/open-metadata-resources/open-metadata-deployment/docker/atlas/target/open-metadata-docker-atlas-1.1-SNAPSHOT-docker-info.jar [INFO] [INFO] --- dockerfile-maven-plugin:1.4.10:push (push-latest) @ open-metadata-docker-atlas --- [INFO] The push refers to repository [registry-1.docker.io/odpi/apache-atlas] [INFO] Image ec47be14f842: Preparing [INFO] Image 6c2641b80e34: Preparing [INFO] Image d85da0a973e5: Preparing [INFO] Image 595578982db7: Preparing [INFO] Image d8e2275a99a1: Preparing [INFO] Image ee610d18148e: Preparing [INFO] Image dee6aef5c2b6: Preparing [INFO] Image a464c54f93a9: Preparing [INFO] Image ee610d18148e: Waiting [INFO] Image dee6aef5c2b6: Waiting [INFO] Image a464c54f93a9: Waiting [ERROR] denied: requested access to the resource is denied [WARNING] An attempt failed, will retry 1 more times org.apache.maven.plugin.MojoExecutionException: Could not push image at com.spotify.plugin.dockerfile.PushMojo.execute (PushMojo.java:90) at com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute (AbstractDockerMojo.java:265) at com.spotify.plugin.dockerfile.AbstractDockerMojo.execute (AbstractDockerMojo.java:254) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: com.spotify.docker.client.exceptions.DockerException: denied: requested access to the resource is denied at com.spotify.plugin.dockerfile.LoggingProgressHandler.handleError (LoggingProgressHandler.java:105) at com.spotify.plugin.dockerfile.LoggingProgressHandler.progress (LoggingProgressHandler.java:63) at com.spotify.docker.client.ProgressStream.tail (ProgressStream.java:77) at com.spotify.docker.client.DefaultDockerClient$ResponseTailReader.call (DefaultDockerClient.java:2734) at com.spotify.docker.client.DefaultDockerClient$ResponseTailReader.call (DefaultDockerClient.java:2718) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624) at java.lang.Thread.run (Thread.java:748) [INFO] The push refers to repository [registry-1.docker.io/odpi/apache-atlas] [INFO] Image ec47be14f842: Preparing [INFO] Image 6c2641b80e34: Preparing [INFO] Image d85da0a973e5: Preparing [INFO] Image 595578982db7: Preparing [INFO] Image d8e2275a99a1: Preparing [INFO] Image ee610d18148e: Preparing [INFO] Image dee6aef5c2b6: Preparing [INFO] Image a464c54f93a9: Preparing [INFO] Image ee610d18148e: Waiting [INFO] Image dee6aef5c2b6: Waiting [INFO] Image a464c54f93a9: Waiting [ERROR] denied: requested access to the resource is denied [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Egeria 1.1-SNAPSHOT ................................ SUCCESS [ 15.916 s] [INFO] Egeria Developer Resources ......................... SUCCESS [ 3.355 s] [INFO] Open Metadata Implementation ....................... SUCCESS [ 0.548 s] [INFO] Open Metadata Frameworks ........................... SUCCESS [ 0.099 s] [INFO] Open Connector Framework (OCF) ..................... SUCCESS [ 22.730 s] [INFO] Open Discovery Framework (ODF) ..................... SUCCESS [ 4.434 s] [INFO] Governance Action Framework (GAF) .................. SUCCESS [ 0.702 s] [INFO] Repository Services (OMRS) ......................... SUCCESS [ 0.126 s] [INFO] Repository Services Connector APIs ................. SUCCESS [ 12.082 s] [INFO] Adapters ........................................... SUCCESS [ 4.647 s] [INFO] Open Connectors .................................... SUCCESS [ 0.209 s] [INFO] Repository Services Connectors ..................... SUCCESS [ 0.210 s] [INFO] Open Metadata Archive Connectors ................... SUCCESS [ 0.095 s] [INFO] Open Metadata Archive File Connector ............... SUCCESS [ 0.280 s] [INFO] Audit Log Connectors ............................... SUCCESS [ 0.090 s] [INFO] Audit Log File Connector ........................... SUCCESS [ 0.280 s] [INFO] Audit Log Console Connector ........................ SUCCESS [ 0.216 s] [INFO] Cohort Registry Store Connectors ................... SUCCESS [ 0.097 s] [INFO] Cohort Registry File Store ......................... SUCCESS [ 4.939 s] [INFO] Open Metadata Collection Stores Connectors ......... SUCCESS [ 0.170 s] [INFO] In-memory Repository Connector ..................... SUCCESS [ 4.750 s] [INFO] Graph Repository Connector ......................... SUCCESS [ 7.528 s] [INFO] REST Client Connectors ............................. SUCCESS [ 0.059 s] [INFO] REST Client Connector API .......................... SUCCESS [ 0.220 s] [INFO] Spring REST Client Connector ....................... SUCCESS [ 0.665 s] [INFO] REST Client Factory ................................ SUCCESS [ 0.166 s] [INFO] OMRS REST API Connector ............................ SUCCESS [ 0.407 s] [INFO] Event Bus Connectors ............................... SUCCESS [ 0.070 s] [INFO] Open Metadata Topic Connectors ..................... SUCCESS [ 0.063 s] [INFO] Kafka Open Metadata Topic Connector ................ SUCCESS [ 0.374 s] [INFO] In-memory Open Metadata Topic Connector ............ SUCCESS [ 0.159 s] [INFO] Open Metadata Governance Servers ................... SUCCESS [ 0.084 s] [INFO] Administration Services ............................ SUCCESS [ 0.069 s] [INFO] Administration Services API ........................ SUCCESS [ 5.079 s] [INFO] Configuration Store Connectors ..................... SUCCESS [ 0.088 s] [INFO] Configuration File Store Connector ................. SUCCESS [ 0.165 s] [INFO] Authentication Plugins ............................. SUCCESS [ 0.079 s] [INFO] http-helper ........................................ SUCCESS [ 3.902 s] [INFO] IBM Information Governance Catalog Repository Connector SUCCESS [ 0.172 s] [INFO] IBM Information Governance Catalog REST API Client Library SUCCESS [ 36.120 s] [INFO] IBM Information Governance Catalog Repository Connector SUCCESS [ 1.661 s] [INFO] Open Metadata Access Services (OMAS) ............... SUCCESS [ 0.135 s] [INFO] Governance Engine OMAS ............................. SUCCESS [ 0.674 s] [INFO] Governance Engine OMAS Common ...................... SUCCESS [ 1.421 s] [INFO] Governance Daemon Connectors ....................... SUCCESS [ 0.059 s] [INFO] Security Synchronization Connectors ................ SUCCESS [ 0.053 s] [INFO] ranger-connector ................................... SUCCESS [ 0.316 s] [INFO] Connector Configuration Factory .................... SUCCESS [ 0.357 s] [INFO] Repository Services Implementation ................. SUCCESS [ 6.589 s] [INFO] Repository Services with Spring .................... SUCCESS [ 0.707 s] [INFO] Asset Catalog OMAS ................................. SUCCESS [ 0.055 s] [INFO] Asset Catalog OMAS API ............................. SUCCESS [ 0.205 s] [INFO] Asset Catalog OMAS Client .......................... SUCCESS [ 2.530 s] [INFO] Asset Catalog OMAS Server-side ..................... SUCCESS [ 0.430 s] [INFO] Asset Catalog OMAS with Spring ..................... SUCCESS [ 0.176 s] [INFO] Connected Asset OMAS ............................... SUCCESS [ 0.059 s] [INFO] Connected Asset OMAS API ........................... SUCCESS [ 7.710 s] [INFO] Connected Asset OMAS Client ........................ SUCCESS [ 2.301 s] [INFO] Asset Consumer OMAS ................................ SUCCESS [ 0.079 s] [INFO] Asset Consumer OMAS API ............................ SUCCESS [ 6.964 s] [INFO] Asset Consumer OMAS Client ......................... SUCCESS [ 0.240 s] [INFO] Asset Consumer OMAS Server-side .................... SUCCESS [ 0.436 s] [INFO] Asset Consumer OMAS with Spring .................... SUCCESS [ 0.156 s] [INFO] Asset Lineage OMAS ................................. SUCCESS [ 0.072 s] [INFO] Asset Lineage OMAS API ............................. SUCCESS [ 0.237 s] [INFO] Asset Lineage OMAS Client .......................... SUCCESS [ 0.072 s] [INFO] Asset Lineage OMAS Server-side ..................... SUCCESS [ 0.320 s] [INFO] Asset Lineage OMAS with Spring ..................... SUCCESS [ 0.121 s] [INFO] Asset Owner OMAS ................................... SUCCESS [ 0.052 s] [INFO] Asset Owner OMAS API ............................... SUCCESS [ 5.130 s] [INFO] Asset Owner OMAS Client ............................ SUCCESS [ 0.152 s] [INFO] Asset Owner OMAS Server-side ....................... SUCCESS [ 0.072 s] [INFO] Asset Owner OMAS with Spring ....................... SUCCESS [ 0.077 s] [INFO] Community Profile OMAS ............................. SUCCESS [ 0.077 s] [INFO] Community Profile OMAS API ......................... SUCCESS [ 5.458 s] [INFO] Community Profile OMAS Client ...................... SUCCESS [ 0.213 s] [INFO] Community Profile OMAS Server-side ................. SUCCESS [ 0.512 s] [INFO] Community Profile OMAS with Spring ................. SUCCESS [ 0.124 s] [INFO] Connected Asset OMAS Server-side ................... SUCCESS [ 0.416 s] [INFO] Connected Asset OMAS with Spring ................... SUCCESS [ 0.128 s] [INFO] Data Platform OMAS ................................. SUCCESS [ 0.049 s] [INFO] Data Platform OMAS API ............................. SUCCESS [ 4.112 s] [INFO] Data Platform OMAS Client .......................... SUCCESS [ 0.124 s] [INFO] Data Platform OMAS Server-side ..................... SUCCESS [ 0.062 s] [INFO] Data Platform OMAS with Spring ..................... SUCCESS [ 0.069 s] [INFO] Data Process OMAS .................................. SUCCESS [ 0.046 s] [INFO] Data Process OMAS API .............................. SUCCESS [ 0.059 s] [INFO] Data Process OMAS Client ........................... SUCCESS [ 0.061 s] [INFO] Data Process OMAS Server-side ...................... SUCCESS [ 0.051 s] [INFO] Data Process OMAS with Spring ...................... SUCCESS [ 0.074 s] [INFO] Data Science OMAS .................................. SUCCESS [ 0.043 s] [INFO] Data Science OMAS API .............................. SUCCESS [ 0.079 s] [INFO] Data Science OMAS Client ........................... SUCCESS [ 0.059 s] [INFO] Data Science OMAS Server-side ...................... SUCCESS [ 0.066 s] [INFO] Data Science OMAS with Spring ...................... SUCCESS [ 0.063 s] [INFO] DevOps OMAS ........................................ SUCCESS [ 0.045 s] [INFO] DevOps OMAS API .................................... SUCCESS [ 0.059 s] [INFO] DevOps OMAS Client ................................. SUCCESS [ 0.058 s] [INFO] DevOps OMAS Server-side ............................ SUCCESS [ 0.056 s] [INFO] DevOps OMAS with Spring ............................ SUCCESS [ 0.084 s] [INFO] Digital Architecture OMAS .......................... SUCCESS [ 0.033 s] [INFO] Digital Architecture OMAS API ...................... SUCCESS [ 4.896 s] [INFO] Digital Architecture OMAS Client ................... SUCCESS [ 0.087 s] [INFO] Digital Architecture OMAS Server-side .............. SUCCESS [ 0.059 s] [INFO] Digital Architecture OMAS with Spring .............. SUCCESS [ 0.065 s] [INFO] Discovery Engine OMAS .............................. SUCCESS [ 0.052 s] [INFO] Discovery Engine OMAS API .......................... SUCCESS [ 0.291 s] [INFO] Discovery Engine OMAS Client ....................... SUCCESS [ 0.165 s] [INFO] Discovery Engine OMAS Server-side .................. SUCCESS [ 0.406 s] [INFO] Discovery Engine OMAS with Spring .................. SUCCESS [ 0.136 s] [INFO] Governance Engine OMAS Client ...................... SUCCESS [ 9.522 s] [INFO] Governance Engine OMAS Server-side ................. SUCCESS [ 7.088 s] [INFO] Governance Engine OMAS with Spring ................. SUCCESS [ 0.109 s] [INFO] Governance Program OMAS ............................ SUCCESS [ 0.061 s] [INFO] Governance Program OMAS API ........................ SUCCESS [ 4.393 s] [INFO] Governance Program OMAS Client ..................... SUCCESS [ 0.201 s] [INFO] Governance Program OMAS Server-side ................ SUCCESS [ 0.316 s] [INFO] Governance Program OMAS with Spring ................ SUCCESS [ 0.105 s] [INFO] Information View OMAS .............................. SUCCESS [ 0.054 s] [INFO] Information View OMAS Client ....................... SUCCESS [ 0.055 s] [INFO] Information View OMAS API .......................... SUCCESS [ 0.290 s] [INFO] Information View OMAS Server-side .................. SUCCESS [ 13.573 s] [INFO] Information View OMAS Spring ....................... SUCCESS [ 0.281 s] [INFO] IT Infrastructure OMAS ............................. SUCCESS [ 0.051 s] [INFO] IT Infrastructure OMAS API ......................... SUCCESS [ 4.040 s] [INFO] IT Infrastructure OMAS Client ...................... SUCCESS [ 0.055 s] [INFO] IT Infrastructure OMAS Server ...................... SUCCESS [ 0.080 s] [INFO] IT Infrastructure OMAS with Spring ................. SUCCESS [ 0.097 s] [INFO] Project Management OMAS ............................ SUCCESS [ 0.044 s] [INFO] Project Management OMAS API ........................ SUCCESS [ 4.358 s] [INFO] Project Management OMAS Client ..................... SUCCESS [ 0.069 s] [INFO] Project Management OMAS Server-side ................ SUCCESS [ 0.055 s] [INFO] Project Management OMAS with Spring ................ SUCCESS [ 0.072 s] [INFO] Security Officer OMAS .............................. SUCCESS [ 0.045 s] [INFO] Security Officer OMAS API .......................... SUCCESS [ 0.059 s] [INFO] Security Officer OMAS Client ....................... SUCCESS [ 0.069 s] [INFO] Security Officer OMAS Server-side .................. SUCCESS [ 0.073 s] [INFO] Security Officer OMAS with Spring .................. SUCCESS [ 0.074 s] [INFO] Software Developer OMAS ............................ SUCCESS [ 0.046 s] [INFO] Software Developer OMAS API ........................ SUCCESS [ 0.070 s] [INFO] Software Developer OMAS Client ..................... SUCCESS [ 0.056 s] [INFO] Software Developer OMAS Server-side ................ SUCCESS [ 0.069 s] [INFO] Software Developer OMAS with Spring ................ SUCCESS [ 0.062 s] [INFO] Stewardship Action OMAS ............................ SUCCESS [ 0.046 s] [INFO] Stewardship Action OMAS API ........................ SUCCESS [ 0.064 s] [INFO] Stewardship Action OMAS Client ..................... SUCCESS [ 0.094 s] [INFO] Stewardship Action OMAS Server-side ................ SUCCESS [ 0.056 s] [INFO] Stewardship Action OMAS with Spring ................ SUCCESS [ 0.063 s] [INFO] Subject Area OMAS .................................. SUCCESS [ 0.062 s] [INFO] Subject Area OMAS api .............................. SUCCESS [ 5.121 s] [INFO] Subject Area OMAS Client ........................... SUCCESS [ 0.655 s] [INFO] Subject Area OMAS Server-side ...................... SUCCESS [ 6.007 s] [INFO] Subject Area OMAS with Spring ...................... SUCCESS [ 0.425 s] [INFO] Data Privacy OMAS .................................. SUCCESS [ 0.050 s] [INFO] Data Privacy OMAS API .............................. SUCCESS [ 4.225 s] [INFO] Data Privacy OMAS Client ........................... SUCCESS [ 0.074 s] [INFO] Data Privacy OMAS Server-side ...................... SUCCESS [ 0.053 s] [INFO] Data Privacy OMAS with Spring ...................... SUCCESS [ 0.065 s] [INFO] Data Engine OMAS ................................... SUCCESS [ 0.043 s] [INFO] Data Engine OMAS API ............................... SUCCESS [ 0.162 s] [INFO] Data Engine OMAS Client ............................ SUCCESS [ 0.063 s] [INFO] Data Engine OMAS Server-side ....................... SUCCESS [ 8.175 s] [INFO] Data Engine OMAS with Spring ....................... SUCCESS [ 5.058 s] [INFO] Discovery Engine Services .......................... SUCCESS [ 0.057 s] [INFO] Discovery Engine API ............................... SUCCESS [ 0.090 s] [INFO] Discovery Engine Server-side ....................... SUCCESS [ 0.287 s] [INFO] Discovery Engine Client ............................ SUCCESS [ 0.224 s] [INFO] Discovery Engine with Spring ....................... SUCCESS [ 0.236 s] [INFO] Open Lineage Services .............................. SUCCESS [ 0.042 s] [INFO] Open Lineage API ................................... SUCCESS [ 0.123 s] [INFO] Open Lineage Server-side ........................... SUCCESS [ 0.959 s] [INFO] Open Lineage Client ................................ SUCCESS [ 0.087 s] [INFO] Open Lineage with Spring ........................... SUCCESS [ 0.248 s] [INFO] Security Synchronization Services .................. SUCCESS [ 0.042 s] [INFO] Security Synchronization Services API .............. SUCCESS [ 0.075 s] [INFO] Security Sync Services Server-side ................. SUCCESS [ 0.355 s] [INFO] Open Metadata Conformance Suite .................... SUCCESS [ 1.787 s] [INFO] Open Metadata Conformance Suite API ................ SUCCESS [ 0.479 s] [INFO] Open Metadata Conformance Suite Server-side ........ SUCCESS [ 1.066 s] [INFO] Stewardship Services ............................... SUCCESS [ 0.043 s] [INFO] Stewardship Services API ........................... SUCCESS [ 0.068 s] [INFO] Stewardship Services Server-side ................... SUCCESS [ 0.155 s] [INFO] Virtualization Services ............................ SUCCESS [ 0.027 s] [INFO] virtualization-services-api ........................ SUCCESS [ 0.094 s] [INFO] virtualization-services-server ..................... SUCCESS [ 0.578 s] [INFO] Administration Services Server-side ................ SUCCESS [ 0.697 s] [INFO] Administration Services Client ..................... SUCCESS [ 0.335 s] [INFO] Administration Services with Spring ................ SUCCESS [ 0.448 s] [INFO] Stewardship Services Client ........................ SUCCESS [ 0.084 s] [INFO] Stewardship Services with Spring ................... SUCCESS [ 0.094 s] [INFO] Open Metadata Conformance Suite with Spring ........ SUCCESS [ 0.567 s] [INFO] Server Chassis ..................................... SUCCESS [ 0.061 s] [INFO] Server Chassis for Spring .......................... SUCCESS [ 12.657 s] [INFO] Access Services Connectors ......................... SUCCESS [ 4.941 s] [INFO] Data Store Connectors .............................. SUCCESS [ 0.051 s] [INFO] Gaian Connector .................................... SUCCESS [ 2.265 s] [INFO] Structured File Connector .......................... SUCCESS [ 2.414 s] [INFO] View Generator Connectors .......................... SUCCESS [ 0.051 s] [INFO] Governance Engine Plugins .......................... SUCCESS [ 0.034 s] [INFO] Ranger Gaian Plugin ................................ SUCCESS [ 20.444 s] [INFO] Gaian Impersonation support ........................ SUCCESS [ 2.061 s] [INFO] Open Metadata User Interfaces ...................... SUCCESS [ 0.034 s] [INFO] Access Services User Interface ..................... SUCCESS [01:55 min] [INFO] Server Configuration User Interface ................ SUCCESS [ 0.069 s] [INFO] Open Metadata Conformance Suite Client ............. SUCCESS [ 10.659 s] [INFO] Open Metadata Distribution Files ................... SUCCESS [ 0.054 s] [INFO] Open Metadata Packages ............................. SUCCESS [ 0.073 s] [INFO] Open Metadata Client Package ....................... SUCCESS [ 0.678 s] [INFO] Open Metadata Native Package ....................... SUCCESS [ 0.083 s] [INFO] Open Metadata Caller Package ....................... SUCCESS [ 0.120 s] [INFO] Open Metadata Adapter Package ...................... SUCCESS [ 0.107 s] [INFO] Open Metadata Assemblies ........................... SUCCESS [01:21 min] [INFO] Open Metadata Publication Processes ................ SUCCESS [ 0.159 s] [INFO] Egeria Website ..................................... SUCCESS [ 0.190 s] [INFO] Open Metadata Resources ............................ SUCCESS [ 0.041 s] [INFO] Open Metadata Samples .............................. SUCCESS [ 0.037 s] [INFO] Access Services Samples ............................ SUCCESS [ 0.031 s] [INFO] Governance Program OMAS Client Samples ............. SUCCESS [ 0.228 s] [INFO] Subject Area OMAS Samples .......................... SUCCESS [ 0.153 s] [INFO] Open Metadata Demos ................................ SUCCESS [ 0.086 s] [INFO] Cohort demo using the in Memory repository ......... SUCCESS [ 0.044 s] [INFO] Virtualizer to be deprecated ....................... SUCCESS [ 3.382 s] [INFO] Open Metadata Tutorials ............................ SUCCESS [ 0.158 s] [INFO] Open Metadata Deployment ........................... SUCCESS [ 0.341 s] [INFO] Open Metadata Docker Images ........................ SUCCESS [ 0.059 s] [INFO] Docker image - Atlas ............................... FAILURE [47:26 min] [INFO] Docker image - Configuration ....................... SKIPPED [INFO] Docker image - Egeria .............................. SKIPPED [INFO] Docker image - Gaian ............................... SKIPPED [INFO] Docker image - OMRS Monitor ........................ SKIPPED [INFO] Docker image - Ranger .............................. SKIPPED [INFO] Open Metadata Test Resources ....................... SKIPPED [INFO] Open Metadata FVT Resources ........................ SKIPPED [INFO] OMAS FV and SV Tests ............................... SKIPPED [INFO] Asset Consumer OMAS FVT ............................ SKIPPED [INFO] Subject Area OMAS FVT .............................. SKIPPED [INFO] Open Metadata Open Types Test Resources ............ SKIPPED [INFO] Open Types Test generator .......................... SKIPPED [INFO] Open Types Test generator 1.1-SNAPSHOT ............. SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 56:22 min [INFO] Finished at: 2019-04-22T20:45:19Z [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.10:push (push-latest) on project open-metadata-docker-atlas: Could not push image: denied: requested access to the resource is denied -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.10:push (push-latest) on project open-metadata-docker-atlas: Could not push image at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: Could not push image at com.spotify.plugin.dockerfile.PushMojo.execute (PushMojo.java:90) at com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute (AbstractDockerMojo.java:265) at com.spotify.plugin.dockerfile.AbstractDockerMojo.execute (AbstractDockerMojo.java:254) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) Caused by: com.spotify.docker.client.exceptions.DockerException: denied: requested access to the resource is denied at com.spotify.plugin.dockerfile.LoggingProgressHandler.handleError (LoggingProgressHandler.java:105) at com.spotify.plugin.dockerfile.LoggingProgressHandler.progress (LoggingProgressHandler.java:63) at com.spotify.docker.client.ProgressStream.tail (ProgressStream.java:77) at com.spotify.docker.client.DefaultDockerClient$ResponseTailReader.call (DefaultDockerClient.java:2734) at com.spotify.docker.client.DefaultDockerClient$ResponseTailReader.call (DefaultDockerClient.java:2718) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624) at java.lang.Thread.run (Thread.java:748) [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :open-metadata-docker-atlas Build step 'Conditional steps (multiple)' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 12670 killed; [ssh-agent] Stopped. [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] done Finished: FAILURE

planetf1 commented 5 years ago

Permission to access the 'ODPi' account on docker hub is needed. I don't have access to this account, but hopefully someone in the ODPi/Linux foundation does.

It seems as if 'odpi' is a user on docker hub with 2 very old repos. I assume they were created at ODPi/LF, but can't be sure. I did pull the ubuntu image, and it appears to be base ubuntu + maven, so probably a docker image for a build process? 3 years old though.

Ideally we would need a dockerhub organization 'ODPi'

The odpiadmin user would then need adding to the organization and given permission

@jmertic - any ideas? Do you know about odpi and dockerhub?

If not the options seem to be

jmertic commented 5 years ago

Yes - I do know there was a legacy org account and I'm trying to track down the credentials. Will provide an update once I've got them.

Thank you,

John Mertic Director of Program Management - Linux Foundation ASWF, ODPi, and Open Mainframe Project jmertic@linuxfoundation.org +1 234-738-4571 Schedule time with me at https://calendly.com/jmertic

On Tue, Apr 23, 2019 at 5:43 AM Nigel Jones notifications@github.com wrote:

Permission to access the 'ODPi' account on docker hub is needed. I don't have access to this account, but hopefully someone in the ODPi/Linux foundation does.

It seems as if 'odpi' is a user on docker hub with 2 very old repos. I assume they were created at ODPi/LF, but can't be sure. I did pull the ubuntu image, and it appears to be base ubuntu + maven, so probably a docker image for a build process? 3 years old though.

Ideally we would need a dockerhub organization 'ODPi'

The odpiadmin user would then need adding to the organization and given permission

@jmertic https://github.com/jmertic - any ideas? Do you know about odpi and dockerhub?

If not the options seem to be

  • contact dockerhub to see if they can help - perhaps by contacting the current owner - maybe we can re-use
  • (less desirable) create a new org with a different name. Ideas? Whilst we could use egeria etc I feel we should keep with odpi if we possibly can? though maybe due the way dockerhhub works (each repository is basically just one container ... albeit with many variants/versions) having egeria/XX and egeria/YY is better?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/odpi/ci-management/issues/44#issuecomment-485731343, or mute the thread https://github.com/notifications/unsubscribe-auth/AACIOIKUUIVRFUBA6S6FAG3PR3K5BANCNFSM4G3ZIFUA .

schannamallu commented 5 years ago

Hi @jmertic, Did you got chance to find out the credentials..

jmertic commented 5 years ago

Having trouble tracking this down. Maybe we should just setup a new one called egeria?

planetf1 commented 5 years ago

So create an organization called egeria. then images would be egeria/egeria or egeria/ranger etc...?

I'd prefer odpi, but then if the name is effectively gone we have no choice.

I could I guess email docker to see if they can contact the owner? I'm sceptical but possibly worth a try?

jmertic commented 5 years ago

I tried that and got nothing back yet.

I prefer ODPi too - let me trying again today and if we don’t hear anything back then go with the Egeria name.

On Tue, Apr 30, 2019 at 4:22 AM Nigel Jones notifications@github.com wrote:

So create an organization called egeria. then images would be egeria/egeria or egeria/ranger etc...?

I'd prefer odpi, but then if the name is effectively gone we have no choice.

I could I guess email docker to see if they can contact the owner? I'm sceptical but possibly worth a try?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/odpi/ci-management/issues/44#issuecomment-487859716, or mute the thread https://github.com/notifications/unsubscribe-auth/AACIOIIL5IG6MKE4YSTO4ULPS76VHANCNFSM4G3ZIFUA .

-- Thank you,

John Mertic Director of Program Management - Linux Foundation ASWF, ODPi, and Open Mainframe Project jmertic@linuxfoundation.org +1 234-738-4571 Schedule time with me at https://calendly.com/jmertic

planetf1 commented 5 years ago

Ok thanks.. Note we will want to create an organization - then we can grant users access to it. Currently 'odpi' is just a user.

jmertic commented 5 years ago

Figured it out - switched odpi to an org and added @planetf1 and @schannamallu as admins

schannamallu commented 5 years ago

@jmertic , I can use the user - odpiadmin to push images rite?

jmertic commented 5 years ago

Sure thing!

planetf1 commented 5 years ago

Great step. thanks @jmertic.

@schannamallu I'll let you push the images. I cn do a manual build but I think yours is close - it was just waiting on the ids.

Nearly there!

schannamallu commented 5 years ago

@planetf1, Yes, I can create the images. But pushing images is still failing with the odpiadmin credentials. Do you need to add odpiadmin as owner or any other permissions to push the image..

CC: @jmertic

planetf1 commented 5 years ago

let me try to push some from a local build

planetf1 commented 5 years ago

I tried a local build. however the push failed in the same way

Checking on the website, my dockerhub id (planetf1) is not a member of any organization ...

schannamallu commented 5 years ago

@planetf1 @jmertic I am able to push the docker image to odpiadmin repo but not egeria docker using ci-cd https://cloud.docker.com/u/odpiadmin/repository/list please find the logs: https://jenkins.odpi.org/sandbox/view/All/job/odpi-egeria-sonar/4/console

when i check the docker file of egeria ,it says 

COPY --from=build /root/egeria/open-metadata-distribution/open-metadata-assemblies/target/egeria-*-omag-server/servers/omag-server-*/server-chassis-spring-*.jar /server-chassis-spring.jar
COPY --from=build /root/egeria/open-metadata-distribution/open-metadata-assemblies/target/egeria-*-distribution/egeria-omag-*/user-interface/access-services-user-interface-*.jar /access-services-user-interface.jar

when i check the docker container the paths are different

in docker container

root@fb5563c15816:~# ls -al /root/egeria/open-metadata-implementation/server-chassis/server-chassis-spring/target/

-rw-r--r-- 1 root root 77045876 May 12 13:59 server-chassis-spring-1.1-SNAPSHOT.jar
-rw-r--r-- 1 root root     6119 May 12 13:59 server-chassis-spring-1.1-SNAPSHOT.jar.original

root@fb5563c15816:~# ls -al /root/egeria/open-metadata-implementation/user-interfaces/access-services-user-interface/target/

-rw-r--r-- 1 root root 54553383 May 12 14:25 access-services-user-interface-1.1-SNAPSHOT.jar
-rw-r--r-- 1 root root  1419226 May 12 14:25 access-services-user-interface-1.1-SNAPSHOT.jar.original

In Dockerfile : /root/egeria/open-metadata-distribution/open-metadata-assemblies/target From Container: /root/egeria/open-metadata-implementation/server-chassis/server-chassis-spring/target/

From the dev team please change the path in the dockerfile of egeria. that will solve our egeria build problem.

planetf1 commented 5 years ago

Thanks. Yes we did find this. See https://github.com/odpi/egeria/issues/1006. It is a core egeria issue caused I believe by some recent changes in the base (one reason we want the official build in place). Apologies for the delay (traveling). The delay in part is because the assembly should contain the dockerfile, and we need to correct it. That being said the pragmatic fix is to use the original copy as you suggest, so I'll do a PR for that.

planetf1 commented 5 years ago

The issue is now fixed, and I have successfully rebuilt all the docker images and pushed to the odpi repo manually.

SO I think we can allow the automation to run now - daily?

Any further issues with the actual function of the images will be egeria issues as usual (am retesting now)

schannamallu commented 5 years ago

@planetf1 in Jenkins the node fails while executing the docker profile since it is taking time+node resources i am planning to split the building images section as 3,3 or 4,2.

planetf1 commented 5 years ago

Currently the longest two components are

It should be fine to build individual images if required.

planetf1 commented 5 years ago

The above PR is now merged, so builds should be clean. Can we get them scheduled?

schannamallu commented 5 years ago

Hi @planetf1 , From sandbox i was able to build docker images as 3,3. i also tried 6 as1 but the node fail in the execution of final image. I though this may be due node resource problem ,i am testing the 6 as 1 one more time by increasing the node to 8GB. i will update you soon.

planetf1 commented 5 years ago

Docker build does take a lot of disk space too. If you are unsure about any logs let me know. Sometimes the build process errors aren't the easiest to figure.

schannamallu commented 5 years ago

Hi @planetf1 , I ran 2 job in Jenkins 6 as 1 , i got a node error i don't know why node is throwing that error . can you please have a look . even i modified the node vertical scale up and build time out to 180 min. i observer both builds fail at exactly 1hr 9min ..Strange!!!

https://jenkins.odpi.org/sandbox/view/ALL/job/odpi-egeria-docker/2/console https://jenkins.odpi.org/sandbox/view/ALL/job/odpi-egeria-docker/1/console

cc: @tykeal

planetf1 commented 5 years ago

This definately looks like some kind of infrastructure related timeout:

[INFO] [INFO] --- frontend-maven-plugin:1.6:npm (npm run r.js) @ security-admin-web ---
[INFO] [INFO] Running 'npm run r.js -- -o ../security-admin-web-2.0.0-SNAPSHOT/minify.build.js' in /root/ranger/security-admin/target/jsmain
[INFO] [INFO] 
[INFO] [INFO] > security-admin@2.0.0 r.js /root/ranger/security-admin/target/jsmain
[INFO] [INFO] > r.js "-o" "../security-admin-web-2.0.0-SNAPSHOT/minify.build.js"
[INFO] [INFO] 
[INFO] [INFO] 
[INFO] [INFO] Tracing dependencies for: Main
[INFO] [INFO] Uglify file: /root/ranger/security-admin/target/security-admin-web-2.0.0-SNAPSHOT/scripts/Main.min.js

^^^ Up to this point we are just running our maven build

vvv but then this isn't maven reporting failures 

FATAL: command execution failed
java.io.EOFException
    at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680)
    at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155)
    at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861)
    at java.io.ObjectInputStream.<init>(ObjectInputStream.java:357)
    at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49)
    at hudson.remoting.Command.readFrom(Command.java:140)
    at hudson.remoting.Command.readFrom(Command.java:126)
    at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)
    at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Caused: java.io.IOException: Unexpected termination of the channel

^^^ And that termination looks like whatever container etc was running the build has 'disappeared' and the calling script/program is then reporting an error.

I would guess there is a 69 minute timer somewhere.....

Another possibility might be to create a set of docker builds in jenkins, one for each docker image. That would keep each run smaller. Overall the build is taking 2 hours for me too - with ranger taking the longest. I actually wish we didn't have to build ranger, but there are no pre-canned containers I've found

We could even split the ranger build if necessary - part one being to build a basic image of the base apache ranger code at our desired version. That would only change very slowly - a few times per year. Maybe we push to dockerhub manually Then we just build the delta on top of that regularly.. (configuration scripts etc). We could also work on trying to push it back to the ranger community & maybe automate on dockerhub .. but those options all take time.

How about 1 build per container? would that help? If we (the dev team) can then update the configuration to add new images as needed I think it would be a reasonable workaround?

schannamallu commented 5 years ago

@planetf1 yah correct ,we go with each docker build/push per job. Please update the dev and let me know the mvn goal? if goes smooth we will create docker tab

planetf1 commented 5 years ago

My hope is to just change the docker invocation. One option is to 'cd' to the correct subdirectory first, but I thought it better to add '-pl' to the mvn invocation. However I'm having trouble getting it to work. hoping for an answer at https://stackoverflow.com/questions/56382763/want-to-only-build-specific-submodules-of-a-maven-project

schannamallu commented 5 years ago

@planetf1 , yesterday i build 3,3 docker images by calling mvn -f xx/xx/pom.xml clean install . i got success .

planetf1 commented 5 years ago

Ok, we could do that then... since our parents are all correctly specified it should work fine too. If there's no need to change the actual source I will leave as is.

So could we just have jobs that each do one of these ....

mvn -f open-metadata-resources/open-metadata-deployment/docker/egeria clean install
mvn -f open-metadata-resources/open-metadata-deployment/docker/configure clean install
mvn -f open-metadata-resources/open-metadata-deployment/docker/gaian clean install
mvn -f open-metadata-resources/open-metadata-deployment/docker/omrs-monitor clean install
mvn -f open-metadata-resources/open-metadata-deployment/docker/ranger clean install
mvn -f open-metadata-resources/open-metadata-deployment/docker/atlas clean install
mvn -f open-metadata-resources/open-metadata-deployment/docker/apache-atlas clean install

Then if we add another image, we can add the invocation to the script/job definition

schannamallu commented 5 years ago

@planetf1 ,

the individual docker jobs are successful in the sandbox. soon we will move this config to the production. i will let know once it finish.

https://jenkins.odpi.org/sandbox/view/ALL/job/odpi-docker-egeria-apache-atlas/2/console https://jenkins.odpi.org/sandbox/view/ALL/job/odpi-docker-egeria-atlas/2/console https://jenkins.odpi.org/sandbox/view/ALL/job/odpi-docker-egeria-configure/3/console https://jenkins.odpi.org/sandbox/view/ALL/job/odpi-docker-egeria-egeria/2/console https://jenkins.odpi.org/sandbox/view/ALL/job/odpi-docker-egeria-gaian/2/console https://jenkins.odpi.org/sandbox/view/ALL/job/odpi-docker-egeria-monitor/2/console https://jenkins.odpi.org/sandbox/view/ALL/job/odpi-docker-egeria-ranger/3/console

planetf1 commented 5 years ago

Good news - thanks Maybe on a new tab egeria-docker? That may make finding easier?)

schannamallu commented 5 years ago

@planetf1, Now added all the docker jobs. Can you check once. I will close this issue

101