I want to get build id or any other information that i can get from Octopus deploy REST API and use it to get build details from TeamCity API
Currently using release number from octopus to filter team city build(locator:number)
Related
I'm trying to list all TC (TeamCity) builds/projects triggered by a specific Bitbucket repo (And do it for every repo we have).
What is the best way to do it with TC Rest API?
I am having 3 “Deploy a Release” steps in a Octopus project. I need to deploy each steps in a different Azure WebApp. How can achieve the this.
For example I have an octopus project named ‘Fruit’, and I have 3 steps in the project, each one to “Deploy a Release”
Step 1: Apple - To be deployed on an Azure Web-app ‘Alpha’ in Dev Environment.
Step 2: Orange - To be deployed on an Azure Web-app ‘Bravo’ in Dev Environment.
Step 3: Mango - To be deployed on an Azure Web-app ‘Charlie’ in Dev Environment.
All the azure web apps are under the same account. Kindly help.
Assuming that you will be having separate package feeds (alpha package,...) for each steps, you should be able to achieve deployment to each web app in same environment by using variables scoped to each specific step.
variable scoping
We are trying to push a nuget package from an Azure DevOps build pipeline to an Azure Artifacts feed. However, in the nuget push step, we're not able to select a target feed. It says "No results found.", although we have three feeds! All feeds have the Project Collection Build Service account set up for contributor privileges. The build pipeline is running in the Project Collection authorization scope.
Any suggestions what the problem might be?
Team city is often used for building and then use Octopus for deploy. I wonder if I can use a successful octopus deploy to trigger a team city build? If it is possible, how to do this? Thanks.
You could use an integration between Octopus Subscriptions (basically webhooks) to call off to TeamCity's API, but you'd have to create that manually, there's no built-in "connectors".
I'd question why you want to do this though?
You could simply add a script step at the end of your deployment which would call the TeamCity URL to trigger a build.
There appears that there is also a community step in the library for doing a HTTP GET or HTTP POST.
Ensure you set the Run Condition to Success so that it will only be triggered when the full deployment has been completed.
I am using Team City and Web Deploy to build and deploy an ASP.NET Web Application.
I have DEV.pubxml and QA.pubxml publish profiles configured.
I want to override the publishUrl property in those files through Team City so that each of my Team City build configurations can deploy to different locations on my web servers.
It looks like this isn't the right property to override, and that you want PublishDir instead. See this response to another SO thread.