OpenShift Build and Deploy a JEE Application with S2I: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 23: Line 23:
  oc new-app <''name''> \
  oc new-app <''name''> \
   --param APPLICATION_NAME=<''application-name''> \
   --param APPLICATION_NAME=<''application-name''> \
   --param SOURCE_REPOSITORY_URL=https://gogs.cicd.svc.cluster.local:3000/gogs/openshift-tasks-private \  
   --param SOURCE_REPOSITORY_URL=https&#58;//gogs.cicd.svc.cluster.local:3000/gogs/openshift-tasks-private \  
   --param SOURCE_REPOSITORY_REF=master \
   --param SOURCE_REPOSITORY_REF=master \
   --param CONTEXT_DIR=/
   --param CONTEXT_DIR=/

Revision as of 08:18, 25 November 2017

Internal

Overview

Process

"Join" Projects

If the source repository pod runs in a collocated OpenShift project, and we want to use the internal DNS name, we need to join the projects. 

oadm pod-network join-projects --to=cicd lab

Create the Application

oc new-app <name> \
 --param APPLICATION_NAME=<application-name> \
 --param SOURCE_REPOSITORY_URL=<git-url> \ 
 --param SOURCE_REPOSITORY_REF=master \
 --param CONTEXT_DIR=/

oc new-app <name> \
 --param APPLICATION_NAME=<application-name> \
 --param SOURCE_REPOSITORY_URL=https://gogs.cicd.svc.cluster.local:3000/gogs/openshift-tasks-private \ 
 --param SOURCE_REPOSITORY_REF=master \
 --param CONTEXT_DIR=/

This creates:

  • a build configuration
  • an image stream
  • a deployment configuration
  • a route
  • a service

Add Source Repository Secrets

oc secrets new=basicauth <secret-name> --username=... --password=...
oc secrets link builder <secret-name>
oc set build-secret --source bc/<build-config-name> <secret-name>
Retrieved from "https://kb.novaordis.com/index.php?title=OpenShift_Build_and_Deploy_a_JEE_Application_with_S2I&oldid=32434"