Skip to content

Project Child Syncing Improvements
Compare
Choose a tag to compare
@BobJWalker BobJWalker released this 03 Sep 19:27
1.4.0
b2f829a

The project child syncing functionality of the space cloner is now more robust. It now supports the following use cases:

  • Sync just the deployment process between a parent project and child project
  • Sync just the runbook processes between the parent project and child project
  • Select specific runbooks to clone
  • Sync the channel version rules
  • Sync the release version setting

In addition, a new file ProjectSyncer.ps1 has been created. It is designed to make it easier to sync projects in the same space. Fewer variables to worry about.

In this example, the project syncer will only clone the runbooks "Spin Up Azure SQL Server Database" and "Delete Azure SQL Server Database" from the parent project "DBUp SQL Server" to "DBUp Clone Tester". It won't sync the deployment process.

ProjectSyncer.ps1 `
        -SourceOctopusUrl "https://samples.octopus.app" `
        -SourceOctopusApiKey "API KEY!" `
        -SourceSpaceName "Target - SQL Server" `
        -ParentProjectName "DBUp SQL Server" `
        -ChildProjectsToSync "DbUp Clone Tester" `
        -RunbooksToClone "Spin Up Azure SQL Server Database,Delete Azure SQL Server Database" `
        -OverwriteExistingVariables $true `
        -AddAdditionalVariableValuesOnExistingVariableSets $true `
        -OverwriteExistingCustomStepTemplates $false `
        -OverwriteExistingLifecyclesPhases $false `
        -CloneProjectChannelRules $true `
        -CloneProjectRunbooks $true `
        -CloneProjectVersioningReleaseCreationSettings $true `
        -CloneProjectDeploymentProcess $false
Assets 2
Loading