Journey Platform API Developer resources for building Journey Platform solutions
Continuous IntegrationContinuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early. (CI) is an essential ingredient in a software development process, which helps improve software quality, provide reliable, repeatable, and well designed automated processes to save time, reduce the chance of human errors, and identify errors early. The Temenos Journey Platform provides the services and tools to facilitate in Continuous Integration of Journey applications.
Continuous Integration is the frequent building and testing of new code changes, assisted by software tools that automate the process. It is often referred to as a pipeline. A typical CI environment includes the following components:
CI environments are implemented using software tools that work alone or together to support the creation of pipelines. Implementation is usually achieved via configuration, rather than a specific development. Sometimes, as is the case with our Transact REST APIs, you might have to provide support services to enable application specific deployment or configuration.
There is often crossover in functionality between tools, which blurs the functional boundaries. In GitLab, for example, version control, build and CI services are all available in a single-source system.
We don't prescribe the use of specific tools to apply CI techniques to the Journey platform application development process. Customers are free to configure their existing Ant-compatible CI systems with Ant tasks from the Transact Fluent SDK to provide the underlying automation.
For customers who don't have existing CI infrastructure, we recommend the following tools:
Journey Manager supports Continuous Integration practices through the following three key features:
Journey platform implements CI model as shown below.
In this model, application developers, using Maestro, Manager, and other IDEs, collaborate in a development environment. They work with assets including forms, templates, organization properties, delivery channels, services, and service connections. They configure JSON files to define the contents of application packages. Changes in the development environment are committed to the version control system, from where they can be checked out, packaged into application packages and deployed to other environments by Ant tasks interacting with the Transact REST APIs. This is summarized below:
The Manager CI workflow involves the following steps:
Next, learn about version control systems.