I am trying to integrate Octopus Deploy with the TFS to push the packages and create a release automatically. For achieving this, I have used “Package a application”, “Push package to octopus” and then “Create a release in Octopus”" steps.
In the “Creating a release in Octopus” step, the “Project Name” field is drop down field. As of now, the list is empty. Should it display all the projects which were created in Octopus Deploy? or should we add the project name?
Same is case of Tenant question, environment question. Should we add all those details manually or should it be automatically displayed in drop down list?
The base question is this. Does the connectivity that TFS trying to communicate with Otopus --> is not enabled as of now, creating these problems?
Thanks for getting in touch. If TFS can reach the Octopus Server these pick lists will autofill (some won’t fill until the Project Name is set, since they depend on that). So it may be easier to wait until you have connectivity.
I believe you can still type your Project Name and other details in directly if you are trying to get things set up before you have connectivity, this is how V1 of the extension used to work. Just note that in my testing on VSTS online I couldn’t enter a space, I’m not sure if this is an issue with VSTS online or our extension, I’ll investigate further. However I could work around this by pasting the Project Name into the field.
I hope that helps. If you have more questions can you let me know which version of TFS you are on (self hosted or VSTS online, and the version number if you are self hosted) and which version of the Octopus plugin you have.
Thanks Mark for your reply.
I am facing difficulty in establishing the connectivity between Octopus and TFS. I am using TFS 2015 update 3 and Octopus 3.16.0
The issue is that Octopus server is installed in a virtual machine. So I do not think there is connectivity to TFS.
Could you help me out for this case where TFS is in a VM?
If your VM has an IP address on the network that is directly accessible from the TFS machine the main thing to check is that Octopus has a binding to that address.
You can check which addresses Octopus is bound to by running the Octopus Manager application directly on the Octopus server and checking the Web Portal Bindings. If there is only a binding for localhost, add one for the external IP address. There is some guidance on that here: https://octopus.com/docs/how-to/expose-the-octopus-web-portal-over-https although it concentrates on https. You can just use http if you think that is sufficient.
Once you have the binding set up you should be able to open Octopus in a browser from the TFS machine, if you can do that then the TFS plugin should be able to access Octopus. If you have the binding set up but can’t access Octopus on that bound address in the browser then you may have a firewall or other networking configuration that you’ll need to investigate.