Introduction
Introduction
IntroductionInstall CloudBees CD/RO within KubernetesConfigure Helm chartsKubernetes platform-specific configurationsKubernetes configuration optionsConfigure IP protocols for Helm chart componentsConfigure GitOps with Helm chartsVerify Helm chartsCreate custom Docker imagesVerify Docker images
IntroductionInstallation user requirementsInstallation typesDefault installation directoriesVerify installation binariesAgent security recommendations
IntroductionInstall a default configurationInstall a custom configurationRun an express agent GUI installationRun an express GUI installation (agent-only installer)Run an advanced GUI installation (agent-only installer)Install CloudBees Analytics
IntroductionRun an express server command-line installationRun an advanced command-line installationRun an express agent command-line installationExpress agent command-line installation (agent-only installer)Advanced command-line installation (agent-only installer)Install the CloudBees Analytics server with the interactive command-line installer
IntroductionRun a silent installationSilent installation argumentsLinux silent installation examplesWindows silent installation examplesCloudBees Analytics server unattended installation
IntroductionUNIX agent interactive command-line installationSilent installation method for UNIX or macOS agents
IntroductionPrerequisitesPermissions to install or upgrade remote agentsInstall remote agents using the web interfaceInstall via the API
CloudBees Tools installation
Move the artifact repository in LinuxMove the artifact repository in Windows
Connect CloudBees CD/RO to a Microsoft SQL server
Install the MySQL JDBC connector
IntroductionUninstall CloudBees CD/RO on Linux, Unix, or macOSUninstall on WindowUninstall the CloudBees Analytics server on LinuxUninstall the CloudBees Analytics server on Windows
IntroductionZones and gatewaysConfigure custom CAs and CRLs in non-clustered environmentsConfigure custom CAs and CRLs in clustered environmentsConfigure agent environment variablesLicensesCreate and manage usersEdit user settingsCreate and manage groupsPersonasConfigure an external databaseConfigure CloudBees CD/RO to use an alternate databaseInstall services for non-root/non-sudo Linux installationsConfigure autostart for non-root/non-sudo Linux installationsConfigure universal access to the plugins directoryConfigure an environment proxy serverSystem health monitoringIncrease file descriptors on Linux and Linux Docker containersAdjust swappiness on LinuxSet variables on Windows agent machinesServer propertiesServer settingsSource code synchronization
IntroductionConfigure initial events for Workload InsightsConfigure OpenSearch Dashboards to work with CloudBees Analytics
IntroductionArchitecture of a CloudBees CD/RO clusterResource, agent, and procedure considerationsSoftware for clusteringDependencies for clusteringConfigure clusteringSeparate agents from CloudBees CD/RO serversPrepare your cluster resourcesInstall and configure a load balancerInstall ZooKeeperConfigure a multi-ZooKeeper clusterInstall CloudBees CD/RO softwareConfigure repository serversConfigure machines to operate in clustered modeRun a cluster in single-server modeAdd the configuration to ZooKeeperUpload configuration files to ZooKeeperGet cluster information from ZooKeeperAdd a node to an existing clusterConfigure web server propertiesConfigure repository server propertiesConfigure CloudBees CD/RO agentsConfigure the cluster workspaceConfigure CloudBees CD/RO repositoriesAdd trusted agents to clustersVerify CloudBees CD/RO servicesAccess CloudBees CD/RO with clusteringHealth check for the CloudBees CD/RO clusterAdditional ways to improve a clusterInstall the CloudBees Analytics server in cluster modeUse self-signed certificates in CloudBees CD/RO on KubernetesConfigure Disaster Recovery and recover from a disaster
Sign in to CloudBees CD/ROAccess the Home pageMy work dashboardGuided tutorialsLearn about the object modelSearch and filter
IntroductionIntrinsic properties listed by object typeReserved words in CloudBees CD/ROObject types in CloudBees CD/ROSpecial characters in CloudBees CD/RO object namesContext-relative shortcuts to property pathsProperty error codesConfigure properties or property sheetsProperty BrowserProperty reference use case
IntroductionResource poolsCreate or edit resource pools
IntroductionView workspacesCreate or edit workspacesWorkspace file
IntroductionCreate a projectSchedules
IntroductionPipeline stages and gatesPipeline access controlPipeline tasksUse the CloudBees CD/RO API to define tasksDefine manual tasksEntry and exit gatesPipeline conditionsPipeline start and end stages and stage skippingWait dependenciesNative CI integrationPipeline UIAuthor and run pipelinesDefine stage gate rulesPipeline objects and conditionsPipeline stage summaryCredentials in pipelinesRun pipelinesView pipeline runsExample: Create a manual task in a pipelineExample: Plugin pipeline tasksExample: Integrate test automation in release pipelinesExample: Leverage test data management and service virtualization in release pipelines
IntroductionRelease planning, scheduling, and trackingRelease and environment reservations calendarVisibility and status of release pipelinesRelease definitionDeploy with Argo RolloutsRelease dashboardPlanned versus actual view for pipeline statusPath to production viewRelease summaryRun and end releases
Introduction
IntroductionManage procedure runsProcedure run detailsUsing CloudBees CD/RO in your environmentJob step executionPostprocessors: Collecting data for reports
IntroductionWorkflow listsCreate or edit workflow definitionsWorkflow definition detailsRun workflowWorkflow detailsWorkflow LogTransition workflow
Introduction
IntroductionCreate and manage applicationsApplication process run detailsCreate application processesAdd process stepsProcess branchingConfigure plugin process stepsDefine manual stepsExample: Manual step with runtime parametersAttach credentials to processesFull-stack dependency viewApplication deployment optionsConfiguration drift
IntroductionMaster component examplesMaster components list
Introduction
IntroductionStage artifactsCapture snapshotsApplication rollbackManage dependencies
IntroductionCreate environmentsDefine environment tier mapsInventory trackingEnvironment inventoryGlobal environment inventoryEnvironment reservationsLock environmentsModel dynamic environmentsAutomated environment discoveryCreate a deployment task to trigger third-party toolsGenerate a deployment packageExample: Dynamic environment with Amazon and ChefExample: Deploy and troubleshoot applicationsExample: Deploy applications with provisioned cloud resourcesExample: Implement deployment strategies
IntroductionArtifactsArtifact versionsRepositories
Create object tagsCreate object schedules
IntroductionConfigure webhook triggersConfigure polling triggers
IntroductionConfigure email notificationsSelect and edit email messages for application or microservice processes
Introduction
IntroductionInstall CloudBees CD/RO pluginsCreate plugin configurationsManage pluginsCreate pluginsManage the plugin catalog

Move the artifact repository in Windows

2 minute readReference

In this scenario, the DATA directory definition in C:\ProgramData\CloudBees\Software Delivery Automation\conf\repository\wrapper.conf or C:/Program Files/cloudbees/sda/repository/bin/wrapper-windows-x86-64.exe (depending on where CloudBees CD/RO is installed) has these settings:

  • set.default.INSTALL_DIRECTORY=C:/cloudbees/sda

  • set.default.DATA_DIRECTORY=C:/cloudbees/sda

If the Windows server where the current artifact repository is stored is full and you want to move it to a new device with more disk space, map the artifact repository to a new network location.

In this procedure, the set.default.DATA_DIRECTORY value will change to the NEW_DATA_DIRECTORY value. The REPOSITORY_BACKING_STORE value in C:\ProgramData\CloudBees\Software Delivery Automation\conf\repository\server.properties will remain the same, relative to the DATA_DIRECTORY, which will be NEW_DATA_DIRECTORY.

In the example, the DATA_DIRECTORY will be changed to d:\ecdata, and the REPOSITORY_BACKING_STORE value will be relative to this directory.

The REPOSITORY_BACKING_STORE value is always relative to the DATA_DIRECTORY and cannot be set to a fully qualified absolute path.

  1. Publish the artifact under the current directory (C:\ProgramData\CloudBees\Software Delivery Automation\repository-data\<artifact_name>\<version>):

    ectool publishArtifactVersion --artifactName <artifact_name> --version <version> --fromDirectory <directory> --compress 0
    ▼

    Example: To publish an artifact under the current directory ( C:\ProgramData\CloudBees\Software Delivery Automation\repository-data\jdoe\2001\1.0.0 ), enter:

    ectool publishArtifactVersion --artifactName "jdoe:2001" --version "1.0.0" --fromDirectory d:/temp/artest --compress 0
    ▼

    The from Directory ( d:/temp/artest ) contains the files to be uploaded.

  2. Stop the repository server one of these ways:

    • Use the Windows service pane.

    • If you have admin user permissions, enter net stop CommanderRepository.

  3. Move the artifact repository data from the current /DATA_DIRECTORY directory to the /NEW_DATA_DIRECTORY directory using one of these methods:

    • Use Windows Explorer.

    • Enter move * <destinationDirectory> where the <destinationDirectory> is the /NEW_DATA_DIRECTORY directory.

      Example: To move the data to D:\ECDATA, enter move * d:\ecdata.

  4. In C:\ProgramData\CloudBees\Software Delivery Automation\conf\repository\wrapper.conf, change set.default.DATA_DIRECTORY=C:/ProgramData/cloudbees/sda to set.default.DATA_DIRECTORY=/NEW_DATA_DIRECTORY.

    Example: Change set.default.DATA_DIRECTORY=C:/ProgramData/cloudbees/sda to set.default.DATA_DIRECTORY=D:/ECDATA.

  5. Create a logs/repository/ subdirectory under the NEW_DATA_DIRECTORY using one of these methods:

    • Use Windows Explorer.

    • Enter the mkdir command as in the following example:

      Example: Create D:\ECDATA\logs\repository using the following commands.

      mkdir D:\ECDATA\logs
      ▼
      mkdir D:\ECDATA\logs\repository
      ▼

  6. Copy C:\ProgramData\CloudBees\Software Delivery Automation\conf\repository\server.properties and C:\ProgramData\CloudBees\Software Delivery Automation\conf\repository\keystore to the NEW_DATA_DIRECTORY/conf/repository directory using one of these methods:

    • Use Windows Explorer.

    • Enter the mkdir command as in the following example:

      Copy the directories to the /ECDATA/conf/repository using the following commands:

      mkdir /ECDATA/conf
      ▼
      mkdir /ECDATA/conf/repository
      ▼
      copy C:\ProgramData\CloudBees\Software Delivery Automation\conf\repository\
server.properties D:\ECDATA\conf\repository\
      ▼
      copy C:\ProgramData\CloudBees\Software Delivery Automation\conf\repository\
keystore D:\ECDATA\conf\repository\
      ▼

  7. Start the repository server using Windows Service pane.

  8. Check if CloudBees CD/RO has started using the artifact repository in the new network location:

    netstat -aon | find “8200”
    ▼

    Example:

    C:\windows\system32> netstat -aon | find "8200"
    ▼
    TCP    0.0.0.0:8200           0.0.0.0:0              LISTENING       22868
    ▼

    This shows that the DATA_DIRECTORY repository has moved to D:\ECDATA.

    The repository service.log, repository.log and repository.pid files will be created in the D:\ECDATA \logs\repository directory.

  9. Publish a new artifact and check if it is published:

    ectool getArtifactVersions | grep artifactVersionName
    ▼
Move the artifact repository in Linux