Document Properties
Kbid2923K1
Last Modified16-Jun-2020
Added to KB10-Sep-2019
Public AccessEveryone
StatusOnline
Doc TypeGuidelines, Concepts & Cookbooks
Product
  • ICM 7.10
  • Intershop CaaS

Guide - Azure DevOps for CaaS Projects

1 Introduction

Intershop recommends Azure DevOps as tooling to support the CI processes. A project-ready Azure DevOps environment can be provided by Intershop as a service. It already contains a Git repository with the responsive blueprint store and the necessary build pipelines. Also boards for agile management are included in Azure DevOps.

This way professional project development can be started right away without the need to set it up manually.

1.1 References

1.2 Quick Developer Setup

1.2.1 Clone the Source Code of the Project

The Blueprint project with all necessary cartridges is provided in an Azure DevOps Git repository when Intershop sets up the project. 

This repository must be cloned to the developer machine:

Cloning the Repository
git clone https://example@dev.azure.com/example/example/_git/example

You can either set a password for the git account or provide your public key. 

1.2.2 Add Developer Specific Configuration

Edit the file environment.properties based on you local configuration, e.g.,

  • Set database connection
  • Set path to the license file

Provide a file development.properties containing the development specific configurations, e.g.,

  • Check source
  • Pre-loading

See also Cookbook - Gradle Developer Workflow.

1.2.3 Build and Deploy the Project Locally

Run the following commands to build and deploy the project:

Build and Deploy the Project
gradle_environment.bat
gradlew enableHotCodeReloading
gradlew publish
gradlew deployServer

1.2.4 Push Local Changes and Trigger CI Build

As soon as you have pushed your local changes to the Azure DevOps Git repository, the CI Build pipeline will be started.

See also Concept - Continuous Delivery Tools.

1.2.5 Trigger Release Build

To trigger a release build that publishes the binaries release with a specific version of the Nexus binary repository, you just need to add a release label in form of a git tag.

Nexus:


Disclaimer

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.

Customer Support
Knowledge Base
Product Resources
Tickets