I’m wondering if it’s possible to use an AWS CodeBuild step to trigger an OctopusDeploy release by connecting to my on-prem API from within the yaml build step.
So if I create an Ubuntu build agent, I would assume the yaml build would need to install octo.exe and then I can pass variables into a call to the API?
That sounds workable. As long as you can execute the Octo CLI you should be able to create or deploy a release.
It may be easier to use the create-release command with the --deployTo=VALUE argument rather than the deploy-release command as the latter requires a specific release version to be passed in.
Full details on each command and available arguments are available here:
Thanks! I’ve found what looks like the install command I need to run in my yaml file and it looks like it’s doing something with an api key in there. I’ve already got an api key ready to go so would I need to change anything from this install statement?
I’m getting a failure and not really sure why. Here’s the actions part of the yaml script and I’ve attached the log. CodeBuild didn’t like the sudo so I removed it and also used apt-get.
It gets as far as install octopuscli=7.4.3124 but fails. It looks like the last thing it’s doing is waiting for user input but then it clears a similar request further up the chain so not sure if that’s actually the problem.