Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Eng]: version bump will be failed if repo contains new module #18249

Closed
dingmeng-xue opened this issue May 19, 2022 · 0 comments · Fixed by #18565
Closed

[Eng]: version bump will be failed if repo contains new module #18249

dingmeng-xue opened this issue May 19, 2022 · 0 comments · Fixed by #18565
Assignees

Comments

@dingmeng-xue
Copy link
Member

Description

When we introduce new module, it doesn't have serialized cmdlets information under Tools.Common folder. It leads version bump is failed.

Unhandled exception. System.ArgumentNullException: Value cannot be null. (Parameter 'path')
   at System.IO.File.WriteAllText(String path, String contents)
   at VersionController.Models.VersionMetadataHelper.SerializeCmdlets(String fileName, ModuleMetadata moduleMetadata) in C:\Dev\Azure\azure-powershell\tools\VersionController\Models\VersionMetadataHelper.cs:line 70
   at VersionController.Models.VersionBumper.UpdateSerializedCmdlet() in C:\Dev\Azure\azure-powershell\tools\VersionController\Models\VersionBumper.cs:line 337
   at VersionController.Models.VersionBumper.BumpAllVersions() in C:\Dev\Azure\azure-powershell\tools\VersionController\Models\VersionBumper.cs:line 73
   at VersionController.Program.BumpVersions() in C:\Dev\Azure\azure-powershell\tools\VersionController\Program.cs:line 214
   at VersionController.Program.Main(String[] args) in C:\Dev\Azure\azure-powershell\tools\VersionController\Program.cs:line 78

The stack trace points to below method

public static void SerializeCmdlets(string fileName, ModuleMetadata moduleMetadata)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants