Deploying Projects from the Command Line

You can automatically deploy projects from the command line or as part of your CI/CD build pipeline using the Studio Automated CI/CD feature.

For detailed information about generating and deploying the runtime artifacts to BPM Enterprise Edition, see the TIBCO_HOME/docker_cicd/readme.txt file.

Generating deployment artifacts

After you have installed the Studio Automated Build support components and created the Docker image, you can use the Docker image to generate deployment artifacts (RASC files) from the BPM Studio projects.

The generate-rascs command also creates a deploy.manifest file in the target folder. This file details the generated .rasc deployment artifacts and the correct order to deploy them for the deploy-rascs command.

The generate-rascs command also creates a deploy.info file in the target folder. The deploy.info file is in JSON format and lists the set of shared-resource definitions that the generated artifacts require.

The sharedResources property in the deploy.info file lists the name and type of the shared resources that are required for the successful deployment.

You can navigate to the shared resources in the BPM Administrator client to verify if the shared resources are created with the name, type, and other properties as defined in the deploy.info file.

Deploying the generated artifacts

The deploy-rascs command deploys the .rasc runtime artifacts created in a folder by a previous generate-rascs execution.