ChrisCarrAu
/ azure-pipeline-with-keyvault.yaml
Last active
December 26, 2020 04:51
— forked from cdennig/azure-pipeline-with-keyvault.yaml
Azure DevOps Terraform with KeyVault + Service Connection
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| trigger: | |
| - master | |
| pool: | |
| vmImage: 'ubuntu-latest' | |
| variables: | |
| - group: kvintegratedvargroup | |
| steps: |
ChrisCarrAu
/ gist:ee69ec381780b717ec77e74db31ff10f
Last active
November 30, 2017 07:08
Converting TFS to Git (maintaining TFS labels in Git)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Migrating TFS to Git is relatively straightforward with tools such as git-tfs, but how to do it and maintian your labels in a useful way? This is the problem I had to solve recently and this is how I did it. | |
| Requirements: | |
| 1. Migrate all version control history (10+ years) from TFS to Git | |
| 2. Maintain all of the labels in TFS which were used to mark code releases so that the correct version of code can be hot-fixed or reviewed. | |
| I tried to migrate this all in a single Git repository, but the TFS repository had been branched sufficiently that it made the result unintelligible. | |
| I opted for a cleaner approach which met the requirements and also gave the developers a solid platform from which to start with their new Git repository. Create two Git repositories. One for history containing all of the source, atomic checkins and commit comments, and the other containing the releases (from labels) and which would be the base for the new repository. |