Skip to main content

Artifact

ArtifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. represent deployment or build artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project.. In the context of docker these are container images. When an artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. is linked to a softwareProject in the project model, it signifies that the artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. is created by the softwareProject (e.g. the docker image for the backend). This will add the necessary build steps in the build pipeline if the artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. is of a recognizable type.

ArtifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. can also linked to a service (regardless of whether they are created by the softwareProject or not). In this case the artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. will be consumed by the service and the service will provide a runtime environment for it. Having an artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. linked to a service, but not a to a softwareProject allows you to use docker images in a service that are not created by the softwareProject (e.g. a postgres database image).

An artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. in the project setup is not the same as an artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. in the context of expandersExpanderA unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.. See Project Setup Model.

Each artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. created by a softwareProject requires a directory docker/<artifact.name; format="kebabcase">. See Directory structure.

Fields​

Technical name​

This is the actual name of the artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project.. This is separate from the name fieldFieldA property of a DataElement expanded to a database column and user interface input element. which is mainly used by the model itself. This is done to avoid name conflicts and collisions.

caution

Neither the artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. name nor the technicalName should contain any /! If there is a group for the docker images they should be added as the group fieldFieldA property of a DataElement expanded to a database column and user interface input element..

Group​

If specified, the group fieldFieldA property of a DataElement expanded to a database column and user interface input element. add a prefix to the technical name.

Version​

Specify the version of the artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. a service will use. If empty, the latest version will be used.

Type​

The currently supported artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. types are:

  • jee-applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution.-image
  • angular-frontend-image
  • gateway-image
  • custom

Some types such as the jee-applicationApplicationThe overarching model container grouping all components, domain logic, and configurations for an enterprise solution.-image will expand a Dockerfile for the artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project..

Example​

Options​

Option
project.artifact.baseImage Artifact

Override the fully qualified name of the artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. base image. Only applies to artifactsArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. of types that expand a Dockerfile.

<options>
  <project.artifact.baseImage>docker.normalizedsystems.org/nsx-tomee-base:8.0.19-3.17.0</project.artifact.baseImage>
</options>
Option
project.artifact.registry Artifact

Specify a registry for the artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. for the service to look into

<options>
  <project.artifact.registry/>
</options>
Option
project.artifact.moveSqlOnRelease Artifact

Move the sql files of this artifactArtifactA build or deployment result, such as a Docker container image or Java archive, produced by a software project. on release.

Using the SQL Migrations Setup example, when creating a 1.3.0 release, the V2.5__migration-name.sql file will be moved from the NEXT directory to a new 1.3.0 directory.

Prerequisite

This option requires the SQL Migration Setup to be used.

<options>
  <project.artifact.moveSqlOnRelease/>
</options>