Cannot create and deploy a release using powershell for a project having the process "DEPLOY A RELEASE" in it

Yadukrishnan_P · 23 October 2018 16:44

.
Consider “X” is my project and , I want to create release for this project using powershell and using rest APIs. But If I use the above process (Deploy Release of another project) The invoke web request doesn’t work properly. showing error =>
"Invoke-WebRequest : The remote server returned an error: (400) Bad Request.
At line:53 char:6
+ $r = Invoke-WebRequest -Uri $OctopusURL/api/releases -Method Post -He …
**+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~**
** + CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException**
** + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand** " Tried a lot but showing error.

I use this below powershell (Click URL) for creating release and deploy

github.com

OctopusDeploy/OctopusDeploy-Api/blob/master/REST/PowerShell/Deployments/CreateReleaseAndDeployment.ps1

##CONFIG##

$apiKey = "" #Octopus API Key
$OctopusURL = "" #Octopus URL
 
$ProjectName = "" #project name
$EnvironmentName = "" #environment name

##PROCESS##

$Header =  @{ "X-Octopus-ApiKey" = $apiKey }
 
#Getting Environment and Project By Name
$Project = Invoke-WebRequest -Uri "$OctopusURL/api/projects/$ProjectName" -Headers $Header| ConvertFrom-Json
 
$Environment = Invoke-WebRequest -Uri "$OctopusURL/api/Environments/all" -Headers $Header| ConvertFrom-Json
 
$Environment = $Environment | ?{$_.name -eq $EnvironmentName}

#Getting Deployment Template to get Next version

This file has been truncated. show original

If I have a simple process without the deploy a release process, it will work. But if I use this process (deploy release of another project) it doesn’t work and shows the above error.

Kenneth_Bates · 24 October 2018 03:40

Hi Yadukrishnan,

Thanks for getting in touch! I’ve given this script a test and reproduced this behavior both with Deploy a Release steps and standard package steps. However it works if you don’t have these steps (i.e. just a script step in my testing).

Since the Deploy a Release step exposes release versions of the ‘child projects’ in the same way as package steps expose packages and versions, I think all you’ll have to add to this POST to /api/releases is the package version for each package step. Does the following sample script get this going as expected?

gist.github.com

https://gist.github.com/Dalmirog/0fa1116a496b8b545a7d

file.ps1

$apiKey = "" #Octopus API Key
$OctopusURL = "" #Octopus URL
$ProjectName = "" #project name

$Header =  @{ "X-Octopus-ApiKey" = $apiKey }
 
#Getting Project By Name
$Project = Invoke-WebRequest -Uri "$OctopusURL/api/projects/$ProjectName" -Headers $Header| ConvertFrom-Json

#Getting Deployment Template to get next release version

This file has been truncated. show original

You’d need to input the values of your Deploy a Release step and release version of the child project in this line:

"SelectedPackages":[{"StepName":"Deploy1","Version":"1.0.3"},

I hope this helps, and I look forward to hearing how you go!

Best regards,

Kenny

Yadukrishnan_P · 24 October 2018 10:37

Hi, Thank you so much for your kind and immediate support, it works for me.

Kenneth_Bates · 24 October 2018 23:14

Hi Yadukrishnan,

That’s great to hear it works for you! You’re very welcome, and please don’t hesitate to reach out if you have any further questions moving forward.

Best regards,

Kenny

Yadukrishnan_P · 25 October 2018 06:09

Hi, Is there any way to get the status (I mean Success, Progressing, or Failed) of a deployment to powershell ? I can’t find a proper API Key and Value for this. My Concern is here :
If the deployment is success then I need to proceed to next step in my script. If the deployment is progressing I need to wait until it become complete. If deployment is failed I need to get the failed status to my script.

Kenneth_Bates · 30 October 2018 02:20

Hi Yadukrishnan,

Thanks for following up! You can certainly track the deployment status, either for individual steps or the deployment as a whole. There are some built-in system variables that contain this information during a deployment, and you can reference them at the following link.

https://octopus.com/docs/deployment-process/variables/system-variables#Systemvariables-DeploymentStatusTrackingdeploymentstatus

I hope this helps! Let me know how you go or if you have any further questions moving forward.

Best regards,

Kenny

system · 29 November 2018 02:20

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.