Deploy Dentrix release 1.0.0. Success: Step 2: Slack - Notify Deployment Success: Apply retention policy on Tentacles For Octopus 2022.4, we currently recommend Octopus CLI 9.1. On some platforms you may need to install additional dependencies. Again, ensure that octo runs successfully. Waiting for 1 deployment(s) to complete… tar.gz for your system from the Octopus download page, extract somewhere appropriate and symlink octo into your PATH. Deploying Dentrix 1.0.0.508 to: Development (Guided Failure: Not Enabled) Finding deployment process for project: Dentrix Authenticated as: Mike Cousins Deploy] Finding project: Dentrix ![]() Octopus version: 3.2.15 API version: 3.0.0 Running command: octo.exe create-release -server -apikey SECRET -project Dentrix -enableservicemessages -version 1.0.0.508 -deployto Development -progress I’m using TeamCity to create the Octopus release and the release number field seems to be populated correctly.įrom the log though it seems to be using that value in the version parameter, not the packageversion parameter: Release 1.0.0.508 created successfully!Īs you can see I’m trying to deploy 508 but it grabbed 506 and labelled it 508.Īlso, in Octopus I have it set to use the version number from the Nuget package but it’s not doing that and it’s labelling it as 508 in Octopus as well. 1 Copy to Azure Storage 1.0.0.506 Latest available in NuGet repository Introduction This article will discuss setting up an environment for CI (Continuous Integration) and CD (Continuous Delivery) using Team City, Octopus, Visual Studio and GIT. Using version number provided on command-line. Any custom build containers are separate from your concourse container and exist outside the concourse installation. Everything you need for your CI/CD can be defined in your git repo. Finding latest NuGet package for step: Copy to Azure Storage Another neat side of concourse is that all you need is the default concourse container on your build server. It specifies the version when it creates the release so then everything gets messed up because it believes it’s a newer version that it actually is. ![]() Occasionally the Octopus step will grab an old version of the Nuget package and deploy it. I have two separate steps in TeamCity, one to create the Nuget package and one to create the release in Octopus.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |