search

microsoft / tfs-cli

Cross-platform CLI for Microsoft Team Foundation Server and Visual Studio Team Services
MIT License
369 stars 132 forks source link

[VSTS-Ext-Tools] Support overriding build versions in task.json #202

Open jessehouwing opened 7 years ago

jessehouwing commented 7 years ago

The VSTS Developer Tools - Build and Release tasks offer the option to override the version number of build tasks embedded in the extension. This is very helpful for extension builders who have adopted a CI/CD style to develop and test their extensions.

In addition to syncing the task version numbers completely, we recently also introduced overwriting only part of the version number, to make sure the build tasks are auto-updated on the agent, but can be independently major-versioned, as major version changes have bigger impact on build tasks.

image

Having a --sync-task-version=m.m.b or something similar would be useful.

T-Hugs commented 7 years ago

@jessehouwing Can you clarify what exactly the --sync-task-version option does?

jessehouwing commented 7 years ago

As we implemented it in the vsts developer tools, it takes the extension manifest, looks up all build extension points, opens the task.json in each build extension and overwrites the version number it finds there with the version of the extension manifest or from the overrides, if specified.

We added the option to not overwrite all version parts, since major version has special meaning in Build & release. So you can opt to only override the patch or the patch+minor parts.

On Apr 12, 2017 22:12, "Trevor Gau" notifications@github.com wrote:

@jessehouwing https://github.com/jessehouwing Can you clarify what exactly the --sync-task-version option does?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Microsoft/tfs-cli/issues/202#issuecomment-293693675, or mute the thread https://github.com/notifications/unsubscribe-auth/AD-uS2PoIe5fgKjm5tjqCPHZ59SYw2MBks5rvTA8gaJpZM4MyGxO .