Hi all,
I currently have some projects builded on TeamCity using autobuild and in latest PBAutobuild version everything works, but I have one question.
We have our sourcecode in GtiHub repos, there is GitVersion utility which can generate version numbers (we are using them in .NET projcet for version numbering in our .NET projects)
Is there some way how to include env variables in json used for build with pbautobuild? Or is there some other way how to do automatic version numbering using pbautobuild?
Thank you Ales
GitVersion is commandline utility so, I can run that utility before PBAutobuild.
I can use workaround, so I can generate json file for PBAutobuild from template and do the versioning there.
But it would be nice if instead of
-----
"Version": {
"PropertiesDisplayedForExecutable": {
"ProductName": "Konzultace",
"CompanyName": "Prodata Praha s.r.o.",
"Description": "Konzultace - Prodata Praha s.r.o.",
"Copyright": "Prodata Praha s.r.o.",
"ProductVersion": "16.0.0.1",
"FileVersion": "16.0.0.1"
},
"ExecutableVersionUsedByInstaller": {
"ProductVersion": [
16,
0,
0,
1
],
"FileVersion": [
16,
0,
0,
1
]
}
}
-----
you can do something like this
"Version": {
"PropertiesDisplayedForExecutable": {
"ProductName": "Konzultace",
"CompanyName": "Prodata Praha s.r.o.",
"Description": "Konzultace - Prodata Praha s.r.o.",
"Copyright": "Prodata Praha s.r.o.",
"ProductVersion": "$ProdVersion",
"FileVersion": "$FileVersion"
},
"ExecutableVersionUsedByInstaller": {
"ProductVersion": [
$Ver_Major,
$Ver_Minor,
$Ver_Patch,
$Ver_Build
],
"FileVersion": [
$Ver_Major,
$Ver_Minor,
$Ver_Patch,
$Ver_Build
]
}
}
May be there are more use cases where other parts of json could be filled with env_vars, but file version is what I would like.
Best Regards Ales
Thank you for your feedback. I will submit your suggestions to the product team.
Regards,
Ken