Deployment Error - Can't get past this error - HELP!

Abhishek_Logishetty · 12 January 2016 20:46

How can I get past this error? Its driving me crazy. I have
1.) Project setup
2.) Tentacles setup
3.) Environments setup

But I keep getting same error back, see below

There was a problem with your request.
At least one step must be enabled.
Once you have corrected these problems you can try again.
If the problem is related to a variable you will need to update the variables for this release or recreate the release for the changes to take effect.
If the problem is related to the deployment process you will need to create a new release for the changes to take effect.

Dalmiro · 12 January 2016 21:47

Hi,

Thanks for reaching out. Could you please send us a screenshot of the Environments screen where the env Dev can be seen along with all its machines? I just want to make sure you have at least one machine with the role “web” on it.

Also please let us know which version of Octopus are you running.

Thanks,
Dalmiro

Vanessa_Love · 12 January 2016 22:23

Hi Abhishek,

Just to jump in here before you provide this information. Can you try to create a new release please. For each release we snapshot the process and variables. So if you created anything after creating the first release it doesn’t have the right stuff associated.

If that doesn’t help, then please provide the information Dalmiro requested.

Vanessa

Abhishek_Logishetty · 12 January 2016 22:40

Hey Dalmiro,

I have able to find problem, the packages are not getting posted in the right directory i.e. http://{servername}/Nuget/Packageshttp://{servername}/Nuget/Packages. I am having issues deploying my package from TFS to Octopus Deploy.

Software’s installed
Octopus 3.2.15
TFS 2015
Visual Studio 2015

I have OctoPack installed for the project and I have the following argument “/p:RunOctoPack=true” setup for MSBuild
[cid:image002.png@01D14D57.06961E50]

I also have “Create Octopus Release” task installed for TFS, I have connection setup and provided the api key in “Additional Octo.exe Arguments”.
[cid:image001.png@01D14D56.95C49670]

I am able to get the build successful but the package doesn’t get posted to http://{servername}/Nuget/Packageshttp://{servername}/Nuget/Packages. I need help get help to get and also having versioning issues. Would Octopack take care of the versioning?

Regards,
Abhishek Logishetty

Dalmiro · 13 January 2016 17:33

Hi Abhishek,

The package isn’t being pushed to the repository because you are missing the MSBuild parameters that tell Octpack to do so. The missing parameters are

/p:OctoPackPublishPackageToHttp=[YourNugetFeedURL]

/p:OctoPackPublishApiKey=[YourAPIKey]

RE the versioning, Octopack will not exactly take care of it out of the box, but It’ll give you tools to do so.

I encourage you to take a step back and read our full documentation about Octopack. It talks about the parameters you were missing and how Octopack sets the version of the packages.

http://docs.octopusdeploy.com/display/OD/Using+OctoPack (also watch the video on the doc).

Regards,
Dalmiro

Abhishek_Logishetty · 13 January 2016 20:12

Hey Dalmiro,

Thanks for replying back, now I am able to build and get release created in Octopus. But now I am working on other issue i.e. getting “Include Change set Comments” and “Include Work Items” and I am not able to find much documentation about it. See below screenshot

[cid:image001.png@01D14E0B.E59159D0]

Below are the errors in the log I have received
[cid:image002.png@01D14E0C.5EEC17C0]

Are there any other changes I have to make? How can I make this to work? Do you have any documentation on how to set it up?

Regards,
Abhishek Logishetty

Dalmiro · 14 January 2016 21:10

Hi Abhishek,

The error shown on image002.png says 401 - Unauthorized which means that the API kep you used with that step does not belong to a user with enough privileges to do that action in Octopus.

Could you please make sure you are using an API Key that belongs to a user with enough permissions?

Regards,
Dalmiro

Abhishek_Logishetty · 14 January 2016 22:23

Hey Dalmiro,

I have made sure the API key and the user used in TFS is the same user. And the user is admin on both the systems. Below is a small code snippet I have written to check to see if the user is able to connect to TFS, but it’s not working.

Code Snippet
clear
$changesUri = “http://{Servername}:8080/tfs/DefaultCollection/8db7724e-a082-43a7-9a1f-b30decd87aa1/_apis/build/builds/138/changes”
$user = “{username}”
$pass= “{password}”
$secpasswd = ConvertTo-SecureString $user -AsPlainText -Force
$cred = New-Object System.Management.Automation.PSCredential ($pass, $secpasswd)

$headers = @{Authorization = “Bearer $personalAccessToken”}
$changesResponse = Invoke-WebRequest -Uri $changesUri -Method Get -Credential $cred –UseBasicParsing
Write-Host $changesResponse

Output:
[cid:image001.png@01D14EE5.F2524410]

Installed Software’s:
TFS 2015 on-premise
Octopus 3.2.15
Visual Studio 2015
Windows server 2012

We have most of the issues fixed with build, release and deployment. But we are unable to solve this. Are there any other access level needed to be given to TFS user.

Thank you for taking time and writing to us. Your feedback is highly appreciated.

Regards,
Abhishek Logishetty

FYI: we have demo planned next week, we are trying to get this fixed.

Abhishek_Logishetty · 14 January 2016 23:15

Below is the log from our build.

[cid:image002.png@01D14EEF.13E4B140]

From: Logishetty, Abhishek (BIC Consultant)
Sent: Thursday, January 14, 2016 4:23 PM
To: ‘Dalmiro Grañas’ tender2+de3e41cc9e@tenderapp.com
Cc: Seawright, Power (BIC USA) Power.Seawright@brother.com
Subject: RE: Deployment Error - Can’t get past this error - HELP!!! [Problems #43864]

Hey Dalmiro,

I have made sure the API key and the user used in TFS is the same user. And the user is admin on both the systems. Below is a small code snippet I have written to check to see if the user is able to connect to TFS, but it’s not working.

Code Snippet
clear
$changesUri = “http://{Servername}:8080/tfs/DefaultCollection/8db7724e-a082-43a7-9a1f-b30decd87aa1/_apis/build/builds/138/changeshttp://{Servername}:8080/tfs/DefaultCollection/8db7724e-a082-43a7-9a1f-b30decd87aa1/_apis/build/builds/138/changes”
$user = “{username}”
$pass= “{password}”
$secpasswd = ConvertTo-SecureString $user -AsPlainText -Force
$cred = New-Object System.Management.Automation.PSCredential ($pass, $secpasswd)

$headers = @{Authorization = “Bearer $personalAccessToken”}
$changesResponse = Invoke-WebRequest -Uri $changesUri -Method Get -Credential $cred –UseBasicParsing
Write-Host $changesResponse

Output:
[cid:image001.png@01D14EE5.F2524410]

Installed Software’s:
TFS 2015 on-premise
Octopus 3.2.15
Visual Studio 2015
Windows server 2012

We have most of the issues fixed with build, release and deployment. But we are unable to solve this. Are there any other access level needed to be given to TFS user.

Thank you for taking time and writing to us. Your feedback is highly appreciated.

Regards,
Abhishek Logishetty

FYI: we have demo planned next week, we are trying to get this fixed.

Dalmiro · 18 January 2016 15:10

Hi Abhishek,

I contacted my Teammate who developed that extension (who is also on vacation btw) and he said the following:

- I think the issue might be with the user the build agent is running as. It needs to be connected as a user that has permissions to view work items and check-ins.

Can you ask him how he connected the build agent? And what user that agent is connecting to TFS as?

- It might also be worth asking if they're running Update 1. I have a vague recollection of somehow not working on peek until then

Regards,
Dalmiro