Hi
We are trying to update our TFS Online environments to use the new “Octopus Deploy Build and Release Tasks” package.
The basic steps are
- Create Connected Service
- Package Application (optional, this packager is shit at the moment by the way)
- Push Packages to Octopus
- Create Octopus Release (optional)
So any normal scenario would be
- Nuget restore
- Build
- Test
- Package
- Copy and Publish
- Push and possibly release unless you manage this from octopus
Now, since the packager is shit and if you manage to get it working it will not actually do the same as we expect from octopack since it includes everything in the nuget file what we are left with is the option where we use the msbuild argument to construct our octopacks.
- Nuget restore
- Build with /p:RunOctoPack=true
- Test
- Push and possibly release unless you manage this from octopus
The above scenario is fair enough and would work great if the Octopus push module only would understand the arguments from octopack. The thing is that OctoPack are leaving great information in the log like OctoPackPackageVersion, OctoPackBuiltPackages and so on but the “Push Packages to Octopus” module cant use them.
The documentation commonly suggests that we manually should name our releases and so on, this isn’t an option either if you are using CI.
So the questions
- What variables would we be able to use or how do we make them available to the “Push Packages to Octopus”-step
- Will you fix the Package application-step to something that works?
Thanks