Create an Azure DevOps Extension

[cinnamon-msft]

Suggested new feature or improvement

Functionality at parity with the Dev Home GitHub Extension.

• Cloning ADO repositories
• ADO widgets working on the Dev Home dashboard

Scenario

No response

Additional details

No response

[JanRajnoha]

I hope this extension will be top priority, I use ADO for example more than GitHub

[actionthomas]

Please make it compatible with Azure DevOps Server too

[qJake]

Yes please! GitHub is great, but being able to use this awesome app against our large DevOps enterprise org would be even better!

Bonus points for custom query and chart object support!

[drchilds]

I'd like to weigh-in and add my voice to this request.

[johnkattenhorn]

I am looking forward to this feature 😊

[aksoftware98]

@cinnamon-msft I'm thinking of starting implementing this task, as I have worked on something similar before and it will be a big addition to me and many other developers who rely heavily on AZ DevOps. But regarding the authentication for the extension do you need to implement full Microsoft Authentication or use Personal Access Token pasted in the Settings of the Extension so it will be used to authenticate the endpoint? Any ideas about that?

[TheJaysH]

Why wasnt this a day one feature. mad. I dont really use GitHub. (really cool app though <3)

[aksoftware98]

Why wasnt this a day one feature. mad. I dont really use GitHub.

The product is just started, and I think it's obvious, GitHub has +100M users compared to the number of users who use Azure DevOps on a daily bases, I think GitHub deserves the priority. But it's very indeed. I started investigating the repo to get started with it

[actionthomas]

@cinnamon-msft I'm thinking of starting implementing this task, as I have worked on something similar before and it will be a big addition to me and many other developers who rely heavily on AZ DevOps. But regarding the authentication for the extension do you need to implement full Microsoft Authentication or use Personal Access Token pasted in the Settings of the Extension so it will be used to authenticate the endpoint? Any ideas about that?

For on-prem Azure Devops Server, Windows Integrated authentication should be used.

[cinnamon-msft]

@cinnamon-msft I'm thinking of starting implementing this task, as I have worked on something similar before and it will be a big addition to me and many other developers who rely heavily on AZ DevOps. But regarding the authentication for the extension do you need to implement full Microsoft Authentication or use Personal Access Token pasted in the Settings of the Extension so it will be used to authenticate the endpoint? Any ideas about that?

We're working directly with the ADO team to implement this one, just as a heads up :)

[jrdodds]

Settings -> Accounts should support Azure DevOps accounts.

[cleferman]

also interested in this!

[AClerbois]

I need it :-)

[mikebattista]

I wanted to get a sense for everyone's expectations and priorities here given the breadth of functionality that Azure DevOps supports.

Here are some principles and constraints guiding the initial goals for the extension:

• Support Azure DevOps and Azure DevOps Server
• Support functional parity with GitHub for Machine Configuration
• Support functional parity with GitHub for widgets while preserving familiar look and feel of the equivalent Azure DevOps widgets
• Support additional Azure DevOps widgets over time based on priority and demand
• Make it easy to import existing widgets from existing Azure DevOps Dashboards (need to explore what's possible here)

Azure DevOps and Dev Home Widget platforms are different so initially we'll need to prioritize which widgets we support. The initial set of widgets chosen below is based on what we support for GitHub today and top usage data from Azure DevOps.

Here is the current thinking on short-term goals for the extension:

• Accounts
  • Ability to connect MSA and AAD accounts to Dev Home for connecting to Azure DevOps and Azure DevOps Server
• Machine Configuration
  • Ability to clone/configure Git repos within Azure DevOps as with GitHub
  • QUESTION: What about TFVC repos? Is that a priority to support?
• Widgets (in priority order)
  1. Query Results QUESTION: How much control do you expect to have over the size of widgets? How much horizontal scrolling is acceptable?
  2. Query Tile
  3. Query Chart QUESTION: Which chart types are most important to you?
  4. Pull Requests
  5. Assigned to Me
  6. Burndown (STRETCH)
  7. Sprint Burndown (STRETCH)
  • Ideally if you've already set up these widgets in Azure DevOps, it should be easy to import those into Dev Home with a few clicks without having to reconfigure them. We need to explore what's possible here.
  • QUESTION: Are you looking to load an existing Azure DevOps Dashboard within Dev Home as is? What's the value of that compared to just interacting with the dashboard within Azure DevOps in the browser itself?
  • QUESTION: If you're looking to load individual widgets as described above to view them alongside widgets from other extensions, what other widgets are top priority for you?
• QUESTION: What other aspects of Azure DevOps would you like to see integrated into Dev Home?

Let us know what you think!

[JanRajnoha]

For me this list of features will be absolutely enough (mainly query results, pull requests, query chart (pie with grouped tasks by state), query tile and cloning). TFVC repos support would be nice addition.

[qJake]

QUESTION: How much control do you expect to have over the size of widgets? How much horizontal scrolling is acceptable?

I would expect that it would respect the column sizes to the best of its ability, and if I configure a query with a lot of columns, or columns with large horizontal sizing, that it simply won't "fit" and some scrolling is acceptable! Personally, I'm okay creating alternate queries specifically for Dev Home as well.

QUESTION: Which chart types are most important to you?

Line chart, pie chart, bar chart, in that order. 🙂 Build and release statuses would be a nice-to-have as well.

QUESTION: What about TFVC repos? Is that a priority to support?

We switched to Git from TFVC (just as Microsoft did back in 2018 for Windows), so I would imagine that Git has more overall market share than TFVC at this point in time. However, we obviously don't want to leave those folks behind - so I'd imagine whatever the % market share is for TFVC is how high of a priority it should be.

QUESTION: Are you looking to load an existing Azure DevOps Dashboard within Dev Home as is? What's the value of that compared to just interacting with the dashboard within Azure DevOps in the browser itself?

Since Dev Home is a different platform, I would not expect this functionality to exist - I would just expect that I could create new widgets or import existing ones and arrange them in Dev Home separately from how they exist in DevOps Boards.

[mikebattista]

Thanks.

@qJake by "build and release statuses" are you referring effectively to the Build History and Release Pipeline Overview widgets?

[qJake]

@mikebattista Yes! 👍

[ronzinms]

Hello. Any ballpark timeframe on the ADO extension ? Thanks !

[MizardX]

Hello. Any ballpark timeframe on the ADO extension ? Thanks !

This issue is currently in the Dev Home v0.5 milestone, which has a due date of September 15, 2023.

[mikebattista]

Hello. Any ballpark timeframe on the ADO extension ? Thanks !

This issue is currently in the Dev Home v0.5 milestone, which has a due date of September 15, 2023.

The milestones are tentative, but we're working on it.

October/November seems more realistic based on current trajectory.

[JanRajnoha]

Why ADO is not a priority for you? I think you work on everything else but not on this. And with previous experience, ADO extension will be fully functional probably in December, because of bugs, and in this estimation I'm optimist, because in iteration 0.6 you want to bring Enterprise GitHub, which will have higher priority in bug fixing. Overall, ADO will be available after more than half a year after the first preview release (but I'm expecting up to 9 months after first preview release).

[blogcraft]

It looks like Microsoft won't invest more in Azure DevOps in favor of Github (There have been no new features in years, only small updates) which is a shame... Clearly, it's no longer a priority.

[Zhaph]

Even the ability to check out my repos in Dev Home would be nice - or point to an existing repo on disk.

[vladimirgomezf]

Please I think that is very important the Azure Dev Ops support, at least as important as the GitHub support!! And please Microsoft has developers to work on this without going to ruin... I work for a USA company and we use ADO for all our projects so please consider this as a priority please!!!

[cinnamon-msft]

This is a top priority for us and is in this month's milestone. :)

[cinnamon-msft]

We've just published the repo for the Azure extension 🎉 https://github.com/microsoft/devhomeazureextension We're planning to release this next week in the Microsoft Store and then we'll close this issue as completed! :smile:

[jrdodds]

For me, the Dev Home Azure Extension appeared in the Microsoft Store this morning. Looks like it was released last night.

[MISTikus]

I guess this extension does not work with Azure DevOps Server?

[mikebattista]

I guess this extension does not work with Azure DevOps Server?

Not yet but we do intend to support this. The work is tracked by https://github.com/microsoft/DevHomeAzureExtension/issues/45.