Consistent version number for build and vsixmanifest

versionone / VersionOne.Client.VisualStudio

View and update VersionOne work items directly from Visual Studio

http://versionone.github.io/VersionOne.Client.VisualStudio

BSD 3-Clause "New" or "Revised" License

2 stars 10 forks source link

Consistent version number for build and vsixmanifest #11

Closed ibuchanan closed 11 years ago

ibuchanan commented 11 years ago

The vsixmanifest requires a version number. The build.sh script also requires a version number (from the build.properties). Most of the .NET build jobs in Jenkins grab the version number from the build.properties and use it for things not in the build.sh like naming the distribution zip or the git tag.

Some possible solutions:

Generate the vsixmanifest (like we do the AssemblyInfo.cs files)
Use an environment variable in the vsixmanifest
Export the version number from the vsixmanifest to an environment variable

MatiasHeffel commented 11 years ago

we take care of this

JogoShugh commented 11 years ago

Here's an example of how we generate the AssemblyInfo.cs file: https://github.com/versionone/VersionOne.SDK.NET.APIClient/blob/master/build.sh

davidhaimovich commented 11 years ago

Story: As a Developer I should set the build version in one place, and the version should be present in all places where the version is needed.

Description: Modify build.sh in order to generate vsixmanifest with the version taken from the build.properties.

Acceptance Criteria:

The vsixmanifest should be the same as the version properties defined in build.properties.
The build version should be consistent in all places.

JogoShugh commented 11 years ago

Change the comment style to
Change build.properties VERSION_NUMBER=0.0.1 to 9.0.0
Build job to play with: http://ci-server/view/Platform/job/VersionOne.Client.VisualStudio-davidhaimovich/