Phoenix and Ecto have recently (I gather) gotten explicit support for many-to-many associations (via join tables).
It is basically a markdown file with tags to denote the fields (the properties on the JSON response objects returned from the VSTS REST API) to be replaced when the tool generates the report file.
The only real change from standard markdown is the use of the **Source Branch** : $($build.source Branch) ###Associated work items @@[email protected]@ * **$($widetail.fields.'System.
Note 2: We have some special handling in the values, only one of there will contain a value, the other is blank.
Thus allowing the template to work for both GIT and TFVC builds.
This step usually only takes a few minutes to complete: This is an extremely cool feature because the Configuration Mode view enables you to select (load) or deselect (unload) the files or directories (items) that you want to work with so that you don't have to load the whole repository.
You can also see the size for every file/directory.
So I decided to create a set to tools to try to help.
The tools are available on my github account in two forms: The use of a template allows the user to define the layout and fields shown in the release notes document.
Work Item Type') $($widetail.id)** [Assigned by: $($widetail.fields.'System. Title') @@[email protected]@ ###Associated change sets/commits @@[email protected]@ Note 1: We can return the builds start Time and/or finish Time, remember if you are running the template within an automated build the build by definition has not finished so the finish Time property is empty to can’t be parsed.