I connected Azure DevOps to Visual Studio and when I press "Publish Git Repo" everything is working fine.
But it always creates a Scrum process Dashboard.
I made Agile as default and disabled all of the others in my organisation.
Now Visual Studio throws this error
VS403119: You cannot add a team project with process Scrum as it is disabled. Either choose a different process, or enable process Scrum and try again.
So it means the setting is somewhere in Visual Studio.
The only thing I found about it is this two years old question.
Do you know the setting or some config file to change the default process board when publishing to the Azure DevOps from Visual Studio?
Visual Studio always specifies Scrum process when creating Azure Devops project via its Team Explorer, as I know there's no VS settings available to manage this behavior.
As a workaround you can create the project with Agile process in web portal first, add local project/solution into source control and choose Target Project(Click Advanced) before publishing the repo:
Actually this behavior is VS-specific cause Azure Devops itself supports specifying process template even by Rest API. So I decide to post a feature request related to your requirements in User Voice forum with VS tag instead of Azure Devops tag. The product team would provide the updates if they view it.
Related
Some time ago I went to Azure DevOps Services, to create a new Team Project. The name of this Team Project is “Small Apps”.
When I created Small Apps, I created it using Git and Scrum, but didn't add any project a part of the Small Apps team project. Today I had an idea that I wanted to test out. So, I fired up VS 2017 and tried to connect to Small Apps in my Azure DevOps. Nothing doing. Couldn’t find it from VS 2017. I could find other team projects I’ve created in Azure DevOps (formerly VSTS) using either TFVC or Git, but I couldn’t find Small Apps.
Why is that?
Where in Visual Studio are you looking for your project? If you created a project but the repo hasn't been created (or cloned in Visual Studio) yet, you won't find it in Visual Studio.
Please (create and) clone the Git repo first, then you will find it on your machine.
We have several Web Apps and WebJobs with different configurations for different environment, e.g. Test and Release.
Each WebJob is deployed to a Web App using "Publish as Azure WebJob" in Visual Studio.
We are using the Config Transform extension to transform the App.config that consist of different config sections, connection strings and app settings that needs to be transformed. This works fine for local Debug and for Release.
The problem is that when we use "Publish as Azure WebJob" there is no way to specify which configuration to use and Release is always built and published even if Test is selected inside Visual Studio.
We have also tried to deploy the WebJob together with the Web App but it almost always hangs, same as described in Stuck when publishing Web App to Azure with WebJob
We don't need to use config transform if that's not possible, e.g. we could configure directly in Azure. But I haven't found a way to configure config sections directly in Azure.
Yes this is a known VS tooling pain point that comes up often. The short answer is that web.config style transforms aren't supported for general application types like Console apps.
This has been discussed recently in the context of WebJobs in our public repo here. That issue also links to the VS User Voice issue for this. That item also links to the SlowCheetah VS extension which some users have said works for them. You might give that a try.
If that doesn't work for you, then you'll have to manually manage your settings via the app settings blade in the Azure portal.
I added a prebuild step to change the webjob-publishing-setting.json file and the app.config file depending on which Configuration is selected.
The webjob-publishing-settings.json only had the name. Then from Visual Studio 2019 I used "Publish as Azure WebJob" and that created a second webjob with the new name and new configuration.
Works great!
When creating a new project in Visual Studio Online, I can set all it's required settings online, but then I have to connect to it through Visual Studio and configure the check-in policy there before handing it over to the team to use.
I don't work on every project, I create it and then hand it over to the team who will take it further so I don't want to have to connect to each project that gets created.
There is not a direct way to enable TFS check-in policy except connecting to the team project and setting in the team explorer.
Or you'll need to use the Team Foundation Server SDK to implement the function that set check-in policy programmatically, here is a blog "How to Set Check-in Policies for all Projects in Team Foundation Server using PowerShell?", you may have a look: http://manasbhardwaj.net/set-checkin-policies-projects-team-foundation-server-using-powershell/
I have an azure website that I have successfully linked to a team project in VSO. When I go to the "deployments" tab of this site in azure management, it says:
The team project is linked. Visual Studio Online will build and deploy
your project to Windows Azure on your next check-in.
Below, it gives options to check in from VS2012 or 2010. I am using VS 2013.
In VS, I am able to check in changes and see those changes building in the cloud in the team explorer. My expectation is that after the changes build, they should be auto deployed to the website. This is not happening. I have made several checkins, and none are deployed to the website. It's probably that I have something configured incorrectly, but I'm not sure how to debug this.
In the Build Settings I am using the TFvcContinuousDeploymentTemplate.12.xaml build process template. One thing I did notice is that the under the Deployment Parameters, I noticed that Windows Azure Deployment Environment is empty, but if I try to populate that I'm not sure what to enter for "Web site name" or "Webspace" under the web site radio buttom.
I have followed instructions on these websites to no avail:
http://azure.microsoft.com/en-us/documentation/articles/cloud-services-continuous-delivery-use-vso/
http://channel9.msdn.com/Events/Build/2014/3-584
http://www.visualstudio.com/en-us/get-started/deploy-to-azure-vs.aspx
How can I check on the status of the deployment? How can I make sure that the project/solution is correctly configured to deploy/publish and not just build?
Some additional info:
To set up the continuous deploy, I goto azure management portal, click websites, open the website in question. Click the Deployments tab. It says "The team project is linked, Visual studio online will build and deploy your project to Windows Azure on your next check in". Under YOUR SERVER is lists the correct visual studio online URL for my source project (https://------.visualstudio.com). This is my first time trying CD. It has not successfully deployed yet, but the build is working. Every time I check in changes, a cloud build is triggered and it is successful.
I'm new to this, so I am likely making some unfounded assumption, but after going through the instructions multiple times I'm not sure what I can be missing.
Thank you!
l19 has the right idea in the comment responding to my post. I needed to specify a Windows Azure Deployment Environment. The website name is the name of the website. Webspace is a bit trickier, and unfortunately the documentation link in visual studio redirects to a not found page. This has to be precise (e.g., "west us" won't work). I was able to figure out the proper string by creating a new project from azure and associating it with vso from the start. In this case, the build definition was correctly configured. I opened the Windows Azure Deployment Environment and saw that the webspace was set to "eastuswebspace", so I used the same string in my real build definition and it worked.
Friends,
I am trying to setup Continuous Integration with Azure WebJobs. I have a Web and a WebJobs project in the solution. I have continuous integration and deployment already setup for the web app in Visual Studio Online (*.visualstudio.com).
I also connected the WebJobs and the Web app using the Visual Studio ASP.Net extensions - Right click the WebSite project in VS 2013 > Add > Existing Azure WebJob project. It created webjobs-list.json file in the website project.
I was expecting that when the Web app deployment happens to Azure Website after the Visual Studio Online build, it will deploy the WebJobs too. But it is not doing so.
How do we automate the WebJobs deployment after Visual Studio Online build in visualstudio.com?
The WTE team is aware of the TFS publishing issues. I've been personally working on developing a workaround with which I'm comfortable but haven't finalized it yet. My team is working on an improvement to the WebJobs publishing experience from VSO. This item is absolutely on our agenda to repair, and will be included in the next VS update. In the meantime I'm trying to come up with a workaround for the time being; once that workaround is prescriptive enough to post, I'll write a post summarizing the process on our team blog.
This looks like the way to do it with VSTS
https://blogs.msdn.microsoft.com/tfssetup/2016/05/18/deploying-and-schedule-azure-webjobs-from-vsts-to-azure-web-app-with-bonus-cron-scheduling/
Basically,
Use VS to link your web job to a web app.
Create a new Buildtask that uploads the WebJob.zip file.
Profit.