<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Azure DevOps.tips</title><link>https://www.azuredevops.tips/</link><description>About Azure DevOps Tips</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Mon, 20 Jul 2020 08:29:41 +0800</lastBuildDate><atom:link href="https://www.azuredevops.tips/index.xml" rel="self" type="application/rss+xml"/><item><title>Generate PlantUML in you CI/CD Pipeline</title><link>https://www.azuredevops.tips/generateplantumlinpipeline-yaml/</link><pubDate>Mon, 20 Jul 2020 08:29:41 +0800</pubDate><author>Author</author><guid>https://www.azuredevops.tips/generateplantumlinpipeline-yaml/</guid><description>This is part of a series creating around PlantUML and Diagrams as Code.
Authoring Plant UML files in Visual Studio Code Creating Image file from PlantUML using command line Creating Pipeline to build and check-in Diagrams as Code (This Post) Optimise the Pipeline In the previous posts in the series we have looked how to author as well as how to build the PlantUML files using command line tools.</description></item><item><title>Generate PlantUML using Command Line</title><link>https://www.azuredevops.tips/generate-plantuml-using-command-line/</link><pubDate>Sun, 19 Jul 2020 23:00:41 +0800</pubDate><author>Author</author><guid>https://www.azuredevops.tips/generate-plantuml-using-command-line/</guid><description>This is part of a series creating around PlantUML and Diagrams as Code.
Authoring Plant UML files in Visual Studio Code Creating Image file from PlantUML using command line (This Post) Creating Pipeline to build and check-in Diagrams as Code Optimise the Pipeline You may have read my previous post about using Visual Studio Code Extension to create a PlantUML files. https://www.azuredevops.tips/build-diagramsplantuml/. In this post I will cover how to bulk generate image files.</description></item><item><title>Create First Project</title><link>https://www.azuredevops.tips/create-first-project/</link><pubDate>Sat, 18 Jul 2020 16:29:41 +0800</pubDate><author>Author</author><guid>https://www.azuredevops.tips/create-first-project/</guid><description>In a Azure DevOps Organisation you can have multiple projects. It is best to think about these project around a Product or a actual Project with a fixed delivery.
You Project Tasks, Test Scripts, Source Code Repository, Build and Release scripts will live in this Project.
What is the difference with Public vs Private Projects. Private means you can keep the whole project under lock and key so no-one else can get to it unless you grant them permission.</description></item><item><title>Build Diagrams with PlantUML</title><link>https://www.azuredevops.tips/build-diagramsplantuml/</link><pubDate>Wed, 01 Apr 2020 07:10:41 +0800</pubDate><author>Author</author><guid>https://www.azuredevops.tips/build-diagramsplantuml/</guid><description>This is part of a series creating around PlantUML and Diagrams as Code.
Authoring Plant UML files in Visual Studio Code (This Post) Creating Image file from PlantUML using command line Creating Pipeline to build and check-in Diagrams as Code Optimise the Pipeline Build Diagrams – PlantUML So in the previous post we looked at Mermaid diagrams which are built into Azure DevOps Wiki. This is a great low friction way to include diagrams if you haven’t read the tip head over to https://azuredevops.</description></item><item><title>Wiki Mermaid Diagrams</title><link>https://www.azuredevops.tips/wikimermaid-diagrams/</link><pubDate>Sun, 01 Mar 2020 16:29:41 +0800</pubDate><author>Author</author><guid>https://www.azuredevops.tips/wikimermaid-diagrams/</guid><description>Have you ever wanted to create some diagrams to explain the flow or sequence along with you documentation. You can use some tool like Microsoft Visio, export or screen grab the picture then paste it into the wiki. Then when it comes to updating it you have to try and find that Visio file make the change and repeat the export.
In the series of Diagrams in Azure DevOps Wiki I will be showing you how you can put diagrams along side you Wiki documentation.</description></item><item><title>Repo – Allow Build Agent to Commit Code</title><link>https://www.azuredevops.tips/allow-build-agent-to-commit-code/</link><pubDate>Sat, 29 Feb 2020 16:29:41 +0800</pubDate><author>Author</author><guid>https://www.azuredevops.tips/allow-build-agent-to-commit-code/</guid><description>&lt;p>Being able to commit code and other aspects into git source code is something you may find odd. After all the source code is is your companies intellectual property, so why would you want to let you build agent make changes to your code? If you keep your documentation next to your source code for example a wiki, you may want to automatically generate your release notes and check them in.&lt;/p></description></item><item><title>Wiki – Linked Pages on Work Items</title><link>https://www.azuredevops.tips/wikilinkedpagesonworkitems/</link><pubDate>Fri, 28 Feb 2020 16:29:41 +0800</pubDate><author>Author</author><guid>https://www.azuredevops.tips/wikilinkedpagesonworkitems/</guid><description>Azure DevOps wiki enable you to link the page to work items. Which really useful, but it isn’t obvious without going to the links tab on the work item and see that there are linked wiki pages. See picture below of the tabs.
Being able to see on the front page of the work item the list of linked wiki pages and being able to get to those wiki pages would be useful.</description></item><item><title>Wiki Features</title><link>https://www.azuredevops.tips/wikifeatures/</link><pubDate>Wed, 26 Feb 2020 16:29:41 +0800</pubDate><author>Author</author><guid>https://www.azuredevops.tips/wikifeatures/</guid><description>Azure DevOps has features that enable you to get more engagement from you readers including comments, enabling users to follow the page and search. See below some of the features.
Follow If you want to be notified when the wiki page changes you can follow the page. On the top right of the page is a follow button, click it to follow. If you need to unfollow then click it again.</description></item><item><title>Getting Started with Wiki</title><link>https://www.azuredevops.tips/gettingstarted-with-wiki/</link><pubDate>Mon, 24 Feb 2020 16:29:41 +0800</pubDate><author>Author</author><guid>https://www.azuredevops.tips/gettingstarted-with-wiki/</guid><description>So what is a wiki? It is a way to collaborate between multiple people.
Azure DevOps has two types of Wikis:
Project Wiki Coded Wiki Project Wikis You can only have one project wiki. This Wiki can be viewed by all users, including Stakeholders.
Coded Wiki You can have multiple coded wikis, but be aware at the moment these can’t be viewed by stakeholders. See https://developercommunity.visualstudio.com/idea/365939/allow-stakeholders-to-view-wikis-published-from-co.html for an update of this feature.</description></item><item><title>Azure DevOps Status</title><link>https://www.azuredevops.tips/azuredevops-status/</link><pubDate>Sun, 23 Feb 2020 16:29:41 +0800</pubDate><author>Author</author><guid>https://www.azuredevops.tips/azuredevops-status/</guid><description>When you are using a Cloud Service like Azure DevOps, it is always helpful to check the status of the Service.
There are two different ways to check the status, via the website, and the second way is via the Visual Studio Extension.
First the website Open status.dev.azure.com in your prefered browser, and you can see the status.
Send via Extension Install via marketplace.visualstudio.com/items?itemName=UtkarshShigihalliandTarunArora.VSTSStatusInspector or launch Visual Studio and Search into the Manage Extensions online for “Azure DevOps Status Monitor”.</description></item></channel></rss>