loading table of contents...

Frontend Developer Manual / Version 2107

Table Of Contents

5.20 Continuously Deploying Themes

Using a continuous integration (CI) server provides a development team with the possibility to centrally automate the build process and trigger builds on changes in a source control management system (SCM). In modern CI systems, the complete process is defined as a pipeline of steps. One step of such a pipeline may set up or update a test system with the latest artifacts.

This section describes how you define a build step in Jenkins to automatically import themes on change. This comprises three components:

  • Theme Artifacts
  • Theme Importer
  • Jenkins job description language

Section 5.20.4, “Import Released Themes from Maven Repository” describes a different approach, where you release and retrieve theme artifacts to and from a Maven repository.

Theme Artifacts

A theme artifact is a ZIP archive and is build as part of the frontend Maven module in the Blueprint workspace. After building the workspace, you can find it below frontend/target/themes (see Section 4.2, “Theme Structure”.

Theme Import Tooling

To import a theme, there is the import-themes CoreMedia command line client (see Section 5.4.24, “Theme Importer” in Blueprint Developer Manual ), which is build by the Maven module theme-importer-application which resides in the studio-server workspaces.

Jenkins Job Description DSLs

The most common CI server for Java development is Jenkins and there are currently two relevant ways to define a build using infrastructure as code for Jenkins:

  • Job DSL: A Groovy based DSL to describe jobs in Jenkins

  • Jenkinsfile: The DSL provided by Jenkins to describe jobs

Search Results

Table Of Contents

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.