Generated BuildAndPublish.yml doesn't include gitversion

[refactorinc]

Describe the solution you'd like The BuildAndPublish.yml is not configured for gitversion following current guidelines/conventions/agreements Ideally gitversion is configured for all new projects

Describe alternatives you've considered Doing this manually but it takes time and something else does not get done.

[rdarko]

• [ ] Add the flag as false so it activly needs to be enabled and Gitversion.yml file needs to be added to the repository manually
• [ ] with the next version the Gitversion.yml file will be shipped to and the flag will be set to true by default (has to be done after https://github.com/GFlisch/Arc4u.Guidance.Doc/issues/139)
• [ ] test if gitversion nuget package is sufficient for creating the version

[HaGGi13]

As described in the first task of the previous comment the used template parameter list in the hook-in template (BuildAndPublish.yml) must be extended by: gitversionEnabled: false
By the way, this is the default value.

Following a more complete example (note the last line):

stages:
- template: Build/BuildAndPublish.yml@templates
  parameters:
    serviceName: MyService
    projectName: MyProject
    folderPrefix: ''
    sonarQubeEnabled: false
    collectCodeCoverage: true
    publishTestResult: false
    publishCodeCoverageResult: false
    gitversionEnabled: false

[GFlisch]

@HaGGi13 . Is the GitVersion not have to be set to true?

[HaGGi13]

@HaGGi13 . Is the GitVersion not have to be set to true?

It depends on if you want to have GitVersion enabled by default for newly created projects. It's possible to enable it in the build template itself, so that it's enabled for all builds by default - opposite of current situation. Unfortunately, I cannot estimate the impact it will have.

[rdarko]

set gitVersionEnabled: false