This article has not yet been verified against Umbraco 8.

    The concepts and code examples might not work if you are running Umbraco 8.0 or a later version. If you are using Umbraco 7, this article is perfect for you!

    You are more than welcome to report any issues found on the Documentation Issue Tracker.

    Pushing upgrades to a Child Project

    When a project has one or more Child Projects it will appear on the Project page, and the user can click to get an overview of all the Child Projects based on the current project.

    Manage Baseline Children

    From this page you will have an overview af all the Child Projects this Baseline project has. This is also where you go, when you want to push upgrades from your Baseline Project to the Child Projects.

    Upgrading Child Projects

    1. Select the Child Projects you want to push your upgrades to - you can select as many or as few as you like!
    2. Click Update selected children
    3. Make sure the selection looks correct then click Confirm
    4. Follow the process as the upgrades are pushed to the child projects one by one
    5. When the Child Projects turn green the upgrade was a success

    Upgrade Child Projects

    Deploying Minor upgrades to Child projects

    To do a minor upgrade of a Baseline project and its Child projects, the initial task is to run the minor upgrade on the Baseline project it self. This is done in the Umbraco Cloud portal by clicking the "Upgrade available!" button on the Development environment, once the environments on the project are in sync.

    Following Minor upgrades guide and process will leave the Baseline project upgraded to the latest version, while all the children are untouched for now.

    Once the upgrade has been verified on the Baseline project, and you've made sure everything works as expected, you should go to the Manage Child Projects page on the Baseline.

    On this page you'll notice that all the children now have an available upgrade. At this point you are able to select the projects to upgrade.

    At first any pending changes made on the Baseline will be deployed to the child site. Once the changes have been deployed, the child site will be upgraded to the same version as the Baseline site. All the products (CMS, Courier to Deploy and Forms) will be upgraded.

    Minor upgrade labels

    We recommend that you setup a Development environment on your Child project before deploying the upgrade. That way you'll have an environment to test on, and verify that everything has been deployed correctly.

    Once you are happy with the Development environment, you can go ahead and deploy to the Live environment as well.

    The upgrade itself will happen, once you click the upgrade button. This will start by triggering the update, where all the files are updated on the children from the baseline. Once the files are in place we also run the upgrade process, making sure that the children are fully upgraded.

    When using the feature, it is important that the Baseline Child projects have been setup following our best practices for handling config files. This means that any changes to the Child project, should be applied via a config transform file. The reason is that the Child projects config files will be merged by choosing the parents config files first, to ensure that changes to config files, that has been made in the minor upgrade, will also be applied to the child projects.

    Errors while upgrading children from baseline

    If for some reason the update of a Child projects fails, or the Child project is left in a bad state, where it has some wrong configuration files, it is most likely because the Child project was unable to be merged properly.

    When updating Child projects from a Baseline project, a configuration from the Child project will take precedence over the Baseline project configuration. This means that when the update from the baseline to the child runs, the configuration file sometimes won’t be changed.

    To fix this, it is important to follow the flow shown in Handling configuration files. It prevents that the child will update configuration files, and will ensure the best flow between the baseline and the child.

    If the flow isn't used, then the repository will be in a state where the code has been updated, but the configuration files hasn’t been updated. The solution is to manually fix the configuration files on the child project. Do a compare of the configuration files on the baseline and the child, and make sure that all changes has been added to the child’s configuration files.