Creating Mashery Local Docker Images

The Jenkins job, build_docker, is used to create the Mashery Local Docker images.

 

The release version together with build number are used to compose the Docker image tag. For example, in the screenshot shown above, RELEASE_VERSION is "5.2.0"; in the Build History pane, it shows the build "#1" has been done, so Docker images in build #1 have the tag "v5.2.0.1".

TM_CONNECTORS

In the TM_CONNECTORS section, you can choose to build "OAuth2 JWT Authenticator" into the Traffic Manager container (tml-tm).

You can also choose the following Docker images to build:

  • BUILD_DOCKER_NOSQL - NoSQL container (tml-nosql)
  • BUILD_DOCKER_LOG - Log container (tml-log)
  • BUILD_DOCKER_SQL - SQL container (tml-sql)
  • BUILD_DOCKER_CACHE - Cache container (tml-cache)
  • BUILD_DOCKER_TM - Traffic Manager container (tml-tm)
  • BUILD_DOCKER_CM - Cluster Manager container (tml-cm)

UPDATE_PACKAGES

In the UPDATE_PACKAGES section, you can choose to update all packages during the build. Or you can upload a .csv file that contains the list of packages to update during the build. An example list of packages is shown below: 

python.x86_64
libssh2
systemd
bind-license
openssl-libs
device-mapper.x86_64
device-mapper-libs.x86_64

Configuring Azure Access in the Mashery Local Installer

To configure access to Azure in the Mashery Local installer, run the configure_azure Jenkins job from the Prepush tab:

Complete the Project configure_azure dialog as follows:

  • DIRECTORY_ID - The Directory (tenant) ID .
  • APPLICATION_ID - The Application (client) ID .
  • CLIENT_SECRET - The client secret.
  • RESOURCE_GROUP - The Resource Group, which will be created if it does not already exist.
  • RESOURCE_GROUP_REGION - The Resource Group Region.
  • CONTAINER_REGISTRY - The Container Registry, which will be created if it does not already exist.