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

[Enhancement] Pass the version number in the command line #120

Closed
erichexter opened this issue Aug 1, 2013 · 6 comments
Closed

[Enhancement] Pass the version number in the command line #120

erichexter opened this issue Aug 1, 2013 · 6 comments

Comments

@erichexter
Copy link

It looks like I have to create some sort of artifact (file) in order to version my db globally. Why cant I just pass this a parameter of the rh.exe ?

@k4gdw
Copy link

k4gdw commented Aug 1, 2013

From what I can tell by just a cursory glance through the documentation RH.exe does not have a command line argument for version.. If you want that capability, it should be relatively simple, compared to some other customization's, to add it. However, it would be much easier to just edit _BuildInfo.xml.

@erichexter
Copy link
Author

I agree with it being easier to just create a file, I was going to go with
the txt version. I have found that by using octopus deoy I already have the
version number as a variable in the deploy.ps1. So it would be one less
piece of friction

On Thursday, August 1, 2013, Bryan Johns wrote:

From what I can tell by just a cursory glance through the documentation
RH.exe does not have a command line argument for version.. If you want that
capability, it should be relatively simple, compared to some other
customization's, to add it. However, it would be much easier to just edit
_BuildInfo.xml.


Reply to this email directly or view it on GitHubhttps://github.com//issues/120#issuecomment-21914819
.

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

@k4gdw
Copy link

k4gdw commented Aug 1, 2013

I'm using custom MSBuild scripts on a couple of projects at my day job. We
have a custom target that reads the version from _BuildInfo.xml, increments
the build number, and writes it back out. Then it shoves the version number
into a shared AssemblyInfo file prior to building the solution. Then it
fires off RH which gets it's version info from the compiled dll before
finally running any unit tests.

We use a 4 digit semver http://semver.org/ version number of
MAJOR.MINOR.PATCH.BUILD. The only time we need to manually edit
_BuildInfo.xml is when we bump major, minor, or patch to set the lower
digits to 0.

Bryan Johns
K4GDW
http://www.greendragonweb.com

Do not meddle in the affairs of dragons, for you are crunchy and taste good
with ketchup.

On Thu, Aug 1, 2013 at 7:14 AM, Eric Hexter notifications@github.comwrote:

I agree with it being easier to just create a file, I was going to go with
the txt version. I have found that by using octopus deoy I already have
the
version number as a variable in the deploy.ps1. So it would be one less
piece of friction

On Thursday, August 1, 2013, Bryan Johns wrote:

From what I can tell by just a cursory glance through the documentation
RH.exe does not have a command line argument for version.. If you want
that
capability, it should be relatively simple, compared to some other
customization's, to add it. However, it would be much easier to just
edit
_BuildInfo.xml.


Reply to this email directly or view it on GitHub<
https://github.com/chucknorris/roundhouse/issues/120#issuecomment-21914819>

.

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter


Reply to this email directly or view it on GitHubhttps://github.com//issues/120#issuecomment-21932154
.

alexandermlharris added a commit to alexandermlharris/roundhouse that referenced this issue Jan 27, 2014
 - Add version property to the ConfigurationPropertyHolder
alexandermlharris added a commit to alexandermlharris/roundhouse that referenced this issue Jan 27, 2014
 - Add Version options to command line switch
alexandermlharris added a commit to alexandermlharris/roundhouse that referenced this issue Jan 27, 2014
 - Add CommandLineVersionResolver.cs which extracts version directly from a string.
 - Update VersionResolverBuilder.cs to include the new resolver. Logic now groups the file based resolvers together and skips them if the command line resolver is valid.
 - Added Version property to the configuration objects.
 - Fix small typo / spelling error (already submitted in Pull Request chucknorris#134
@ferventcoder ferventcoder added this to the Release 0.8.7 milestone Jun 3, 2015
ChrisMissal added a commit that referenced this issue Jul 22, 2015
…a_commandline

(GH-120) Pass version number in the command line
@morganphilo
Copy link

Has this been resolved? I see this in the documentation as --version but in the latest stable version v0.8.6.0 it does not work

@kunalbuxani
Copy link

I've been setting up a new project wondering why I the --version switch wasn't working. Turns out upgrading to this week's 0.8.7 release fixes the problem.

@BiggerNoise
Copy link
Member

I'll take that as confirmation that the issue is resolved!

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.

6 participants