You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fixing dead link
* shortening links
* minor text changes
* dst timezone fix
* Adding serverless job types
* Adding display name
* fixing serverless pool type
* ordering job pool properties
* fix for empty step sections
* adding pipeline and job demands for non serverless agent jobs
* added blog posts
* updated docs to reflect changes in demands
* changing the way how jobs are ID-ed and reffed by in demands
* fixing duplication of demands in the case of multiple jobs
* commenting emptying construct for steps
* documentation on changing job id and build number
* re-ordering triggers
* fixing wrong syntax for included / excluded when multiple found
* strong typing some arrays to include arrayed single / null tasks
* more strong-typing
* fixing job properties for time-outs
* camelcasing for timeouts
* adding multi sliced ToDO
* strongtyping returned array and remove from child call
* adding checkout properties
* adding 1.1 doc changes except resources
* adding pipeline wide timeouts
* finalizing v1.1 docs
* updating PSD
This first update to AzDoAPITools was inspired by Microsofts own [Export to YAML](https://devblogs.microsoft.com/devops/replacing-view-yaml/) functionality introduced in [sprint 178](https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-178-update#improve-yaml-conversion-in-the-classic-build-designer) inspired me to update my own tooling. After seeing some of the YAML generated by Microsoft I noticed that my tool needed some polishing to make it more in line to the native functionality. I added some ToDo's from the already existing list and added some functionality which I had not taken into account previously. With this update AzDoAPITools is up on par if not better than Microsofts functionality. I have done a comparisson with version 1.0 of AzDoAPITools vs Microsoft "Export to YAML" in [my blog](https://www.continuous-data.nl/azure-devops/full-review-of-the-new-export-to-yaml-feature-in-azure-devops/).
- Changed Job id / displayName notation (added displayname and use actual API id as id instead of displayName as id)
20
+
- Changed order of triggers according to MS Export Tool ordering
21
+
- Changes order of job properties to MS Export Tool ordering
22
+
- fixed syntax for included / excluded paths and branches notation
23
+
- Fixed rare occurrence where executor of script would happen to be in a DST timezone where the target zone would not be.
24
+
- Fixed empty jobs syntax. will now be converted as empty array [] rather than a started array.
25
+
- Fixed notation for job properties for timeout and canceltimeout.
26
+
- updated documentation
27
+
9
28
## Introduction
10
29
11
-
AzDoAPITools is a project which was born when doing a migration from classical pipelines to YAML pipelines for a customer. Which is the current function of the published module. The module will convert Task Groups and classical build pipelines to usable all in one YAML pipelines / step templates.
30
+
AzDoAPITools is a project which was born while doing a migration from classical pipelines (GUI-based) to YAML pipelines (Pipeline as code) for a customer. Which is the current function of the published module. The module will convert Task Groups and classical build pipelines to usable all in one YAML pipelines / step templates.
12
31
13
32
In the future you can expect other automations which i have done for customers such as automatic branching / mass policy application etc. to be bundled in this module.
14
33
34
+
In [this blog post](https://www.continuous-data.nl/tools/intro-azdoapitools/) I have written an introduction into this tool and in [this blog post](https://www.continuous-data.nl/azure-devops/full-review-of-the-new-export-to-yaml-feature-in-azure-devops/) there is a comparison with the in-built "Export to YAML" functionality which was created by Microsoft in November 2020.
0 commit comments