10 docs tagged with "artifacts"

Artifacts are the physical files that make up a specific version of an application.

This topic describes how to fetch artifacts from a Maven repository. You can access artifacts stored in a Maven repository using the fileUri property of Deploy artifacts. To use this feature, you must configure the Maven repositories that Deploy will search for artifacts.

This topic covers the configuration options available for customizing how Deploy handles large artifact deployments, including the in-memory processing threshold, executable detection regex, and JVM heap sizing guidance.

Deploy 26.1 and later supports deploying artifacts larger than 2 GB. Large artifacts are transferred using a streaming approach instead of being fully loaded into memory, which significantly reduces memory pressure during deployment. This topic covers which artifact types are supported, how permissions are handled, storage compatibility, and best practices.

This topic explains how to disable placeholder scanning in Deploy during package import.

Artifacts are the physical files that make up a specific version of an application.

This topic provides information on how Deploy stores all its data in the repository. The Explorer interface allows you to access, view, and manually edit the configuration items (CIs) stored in the repository.

This topic explains how Deploy processes archive formats internally, why the 2 GB boundary exists for ZIP archives, how adaptive permissions work when POSIX metadata is unavailable, and which storage backends support large artifacts.

This topic describes how to configure Deploy to store and retrieve artifacts using two local storage repository formats.

This topic provides some helpful tips and tricks to use when managing deployment packages.