The MSBuild runner is no longer actively supported.

OctopusDeploy / Octopus-TeamCity

| Public | JetBrains TeamCity plugin to trigger releases on build completion

https://octopus.com/teamcity

Other

0 stars 23 forks source link

The MSBuild runner is no longer actively supported. #47

Open Vice93 opened 3 years ago

Vice93 commented 3 years ago

TeamCity now shows the following warning if you select the MSBuild-runner:

"The MSBuild runner is no longer actively supported. It is recommended to use the .NET runner with the 'msbuild' command instead." More info: https://www.jetbrains.com/help/teamcity/2020.2/net.html#.NET-MigratingfromMSBuildRunner

Are there any plans to integrate the current "Octopus Packaging" and "Octopus Publishing" sections of the MSBuild-runner to the .NET runner?

OlympicLarry commented 3 years ago

I added /p:RunOctoPack=true to the command line parameters and that worked. Instructions here: https://octopus.com/docs/packaging-applications/create-packages/octopack

andy250 commented 2 years ago

If you need to specify a package version (which was possible in the VisualStudio step in an own textbox) you can use sth like this - just add it to the "Command line parameters" textbox:

/p:OctoPackPackageVersion=%build.number%