55 docs tagged with "system administration"

This topic explains how to manage active tasks using the Monitoring section.

This topic covers creating a package retention policy (policy.PackageRetentionPolicy) to manage package retention based on a regular expression

Deploy records and archives information about all tasks that it executes. This information is available through the statistics, graphs, and task archives on the Reports screen.

This topic provides information about how to backup Deploy server.

This topic describes how to perform a basic installation of Deploy - either a simple setup with the default configuration, or a manual setup in which you can choose specific options. If you are installing Deploy in a production-ready environment that includes options like a separate, clustered database server, load balancing for your Deploy servers, an active/hot-standby cluster configuration for your Deploy servers, and other security, monitoring, and performance considerations, see Production install.

This topics provides information about the best practices for maintaining Deploy/Release tools.

This topic covers the high availability (HA) configuration in Deploy. To support high availability (HA), you can configure Deploy in clustered active/hot-standby mode. In this mode, only one Deploy node is active at one time, while the hot standby node is ready to become active if needed.

You can configure the following advanced Deploy client settings in /centralConfiguration/deploy-client.yaml.

This topic describes how to set up a failover configuration using an external relational database, allowing for high availability of Deploy instances.

This topic describes how to configure Deploy authentication using the OpenID Connect (OIDC) protocol.

This topic describes how to configure Keycloak to authenticate Deploy users and REST API calls (using the Bearer Token Authorization).

This topic covers how to configure communication between Deploy satellites and the Deploy master to ensure secure and effective operations.

This topic addresses how to resolve SSL handshake issues with Deploy when using a self-signed certificate by configuring a dedicated truststore for the command-line interface (CLI).

This topic provides information about how to configure task execution engine.

This topic provides a step-by-step guide on connecting Deploy to your Atlassian Crowd instance.

This topic describes Data Anonymization, which is the process of protecting private or sensitive information, such as passwords, by deleting or encrypting personally identifiable information.

This topic addresses how to apply a default connectivity Configuration Item (CI) to multiple new CIs in Deploy using reserved names for consistency.

You can install the Deploy command-line interface (CLI) on any remote computer and connect to the Deploy server.

This topic describes how to use maintenance mode in Deploy to safely restart the server and temporarily prevent new deployments and tasks from starting.

This topic covers the repository object in the Deploy command-line interface (CLI) allows you to export the Deploy repository tree to a ZIP file that can be imported into the same Deploy server or into another Deploy server. The ZIP file contains all configuration item (CI) properties, including artifact files.

The Feature Settings page allows you to toggle or configure the optional features Digital.ai Deploy.

This topic describes how to customize the appearance and login screen of Deploy.

This topic describes how to manage internal server error visibility in Deploy.

This topic addresses Cross site request forgery(CSRF), which is a class of attack that forces an end user to execute unwanted actions on an application when the user is authenticated. The Digital.ai Deploy frontend uses endpoints protected with CSRF .

This topic provides information on how to install and configure a satellite server.

You can install and run Deploy Satellite as a service on your Unix or Microsoft Windows machine. The satellite service wrapper requires Java Development Kit 8 or higher to be installed on the target Unix or Windows machine.

This topic provides information about how Deploy runs on the Java Virtual Machine (JVM) and utilizes two classloaders one for the server itself, and one for the plugins and extensions. A plugin can have an .xldp or a .jar extension. The XLDP format is a ZIP archive that bundles a plugin with all of its dependencies.

This topic provides information about the software and hardware requirements to install and run Digital.ai Deploy.

This topic details how licenses work in Deploy, distinguishing between Trial Edition and Enterprise Edition.

This topic describes how to configure Deploy to work with the log analysis tool.

This topic provides information about the logs in Deploy.

This topic describes how to change the encryption key password and the admin user's password in Deploy.

This topic describes how to verify an SSH connection using the Oslogin API with Overthere.

This topic describes the Permission service in Digital.ai Deploy.

This topic provides information on how Digital.ai Deploy operates on the Java Virtual Machine (JVM) with two classloaders: one for the server and one for plugins and extensions. Plugins can be packaged in either .xldp or .jar formats, with the XLDP format being a ZIP archive that includes the plugin and all its dependencies.

This topic explains the roles and permissions in Deploy.

This topic in Deploy explains how to schedule a control task.

This topic describes how to set up an active-active cluster for Deploy with multiple master and multiple external workers.

This topic describes how to set up and configure LDAP with Deploy.

This topic provides Deploy provides information about fine-grained security settings based on roles and permissions that you can configure in the GUI and through the command-line interface (CLI).

This topic describes the default permission settings in Deploy after installation. Initially, no permissions are granted to any user, except for administrator users, who have all permissions.

This topic provides information on shutting down Deploy.

This topic describes the file.encoding system property, which defines the file encoding setting on the Deploy server. By default, it is set to UTF-8 to ensure compatibility with most systems.

This topic provides instructions for starting the Deploy server.

This topic describes how to define one or more sets of credentials in the Configuration section of the CI Library for use with source artifacts. Admin global permissions are required to define these credentials. Once defined, you can use them to provide a username and password for any HTTP URL that requires authentication.

This article describes how to define one or more sets of proxy servers to be used with source artifacts in the Configuration section of the CI Library.

This topic describes how to manage credentials for multiple remote hosts that share the same authentication details. To simplify credential management, you can configure a single CI to define shared credentials for any remote host requiring authentication. When defining an overthere host connection, you can then select the shared credentials CI.

This topic provides information about the XLDEPLOYSERVER_HOME/work directory, which is used to temporarily store data that cannot be kept in memory.

This topic describes how to install a trial version of Deploy.

This page describes common networking errors and their solutions.

You can perform an unattended install of the Deploy server, for example, using Puppet.

This topic provides information on how to update the digital certificate.

This topic describes the prerequisites, considerations and process for upgrading Deploy from version 10.1 or later to the current version.

This topic provides information on upgrading Deploy. When you upgrade to a new version of Deploy, you must also upgrade your satellite servers to the corresponding version of the satellite distribution ZIP.

This topic provides information on verifying OS login and metadata SSH connections to a GCP instance. It includes steps to ensure that OS login is properly configured and that SSH connections using metadata are functioning correctly.