One Octopus project to kick off multiple projects


We use teamcity in conjunction with Octopus to create our releases. Our scenario is such that we have 7-8 different services (modules inside our application), that are built independently. We have an individual octopus project for each service (teamcity creates the release with the required parameters for each of them).

So for instance we’d have

  1. Module 1 with Release Version 1.4.5
  2. Module 2 with Release Version 1.4.9
  3. Module 3 with Release Version 1.4.17, and so on.

We can go in individually to each of these octopus projects, and hit “Deploy Release”, and that works fine. But is there a way to create another “Overall” Octopus project, that could be configured to deploy “the latest version” of each of these projects.
Something of this sort : #{Octopus.Version.LastMajor}.#{Octopus.Version.LastMinor}.#{Octopus.Version.NextPatch} for each of them.

How would we configure this “Overall” project ?

Thanks for your help.


Thanks for getting in touch! The easiest approach to accomplish an automatic deployment of another project from a central one would be to use the Chain Deployment library step template. This step was written by the community, and you can find it here.

This step allows you to specify another project and release version to trigger a deployment of it. Leaving the Release Number field empty will automatically select the latest release of the project, and you can also configure it to create a new release if preferred. This step handles a single project, so you could configure multiple steps based on this template where each specifies a different project.

Does this sound like a good solution for your scenario? Let me know what you think and if you have any further questions. :slight_smile:

Best regards,


Hi Kenny,

Thanks, yes that was just the solution I was looking for.

Thanks much !