Dan Miser - Bump

Sunday, September 04, 2005

In the spirit of the old "touch" application, which allowed you a command line interface to set the date/time stamp of the file to a specific value, I am now releasing "bump". It's a utility that allows you to set version information on files. Some may argue that this isn't a good idea, but you could make the same argument for countless other utilities, too. Besides, you can already do this by jumping through more hoops if you use a resource editor. Basically, if you know what you're doing, and you need this functionality, now you have it. In the initial release, you can get help on the syntax by just typing the command "bump". The syntax for a bump command looks like this:


bump filename.exe

This will increment the build portion of the file version information for that file by 1. If you don't have versioin information for that file, it won't work. However, you can also use this syntax to either create version information, or set existing version information to a specific value:


bump filename.exe 1.2.3.4

The version string requires all 4 values to be set (major, minor, release, and build).

I'd like to thank Colin Wilson, since I used some of his code to create this utility. I sent my changes back on to him, so hopefully, he'll find those useful.

My wishlist of features coming up for this utility (some are already started, or in various states of undone):

Support RES files
Allow for a "touch" option to be integrated into this utility
Allow for batch file processing
Allow for string values to be passed into this utility
Finish the GUI version
Finish the COM version
Finish the FinalBuilder version (I am currently using the console version inside FB within a List Iterator and it works awesome!)

Leave a comment here if you find it useful.

Sunday, September 04, 2005 9:40:00 PM (Central Standard Time, UTC-06:00)

Tuesday, September 06, 2005 3:12:00 AM (Central Standard Time, UTC-06:00)

thanx a lot!

Very interesting tool for integration in the build and release process!

Ralf Grenzing

Tuesday, September 06, 2005 8:38:00 AM (Central Standard Time, UTC-06:00)

I like the idea, and I'm thinking through how to use it.

GetLatest on the source.

Compile.

Bump.

I don't think this gives the results I want.

Now that I think about it, I don't see how this could ever work. Can you give more details on how you use this in FB?

Thanks,

Brad.

Brad White

Tuesday, September 06, 2005 9:18:00 AM (Central Standard Time, UTC-06:00)

Assume you have multiple packages with different version numbers. These packages are included inside CAB files for ActiveForm deployment. After you compile, you bump the version number in the bpl, and then adjust the INF file for the CAB file. In addition, we have some custom tools that generate the INF file, so it becomes very handy in that situation.

I'm really just finding this useful in a very fast-paced change build (e.g. beta). It gives me a shortcut to get builds out very quickly vs. going through the formal process of changing the version number before you compile. As we move to production releases, I would not use this technique.

Dan

Dan Miser

Thursday, September 08, 2005 10:10:00 AM (Central Standard Time, UTC-06:00)

That's what I thought you were saying, but I'm still missing something.

Let's say the copy in VCS says the version is 1.2.3.4. You get the latest and compile.

your exe thinks the version is 1.2.3.4. Now you bump the build and it becomes 1.2.3.5.

This is great.

The next day you get the latest from VCS and compile and the exe thinks the version is

1.2.3.4. Bump it and it becomes 1.2.3.5.

I don't see how that helped me.

Brad White

Thursday, September 08, 2005 1:50:00 PM (Central Standard Time, UTC-06:00)

Dan --

Perfect for FinalBuilder. This is great for people that release libraries and want to make sure that they have proper versioning.

Nick

Nick Hodges

Tuesday, September 13, 2005 10:21:00 AM (Central Standard Time, UTC-06:00)

That's great Dan.

That will be very usefull to me as I had bad experiences with my build process to deploy only the differences, like build all in a new repository tree and compare everything at a binary level. When I build it with version information I always false in the comparison cause the builds are differents, I tried to make the comparison ignore the version information but I got no sucess in some cases. With it I can build without version, compare, copy the different ones and set the version, but I'll need to update all the version information.

Let me know if you need any help to make the new features (just not to the GUI version... ;) ) (danielm at cpd dot ufsm dot br)

Daniel Mirapalheta

Tuesday, September 27, 2005 5:43:00 AM (Central Standard Time, UTC-06:00)

I would like to add that my tool ChangeRes does something similar but then on the delphi project file.

ChangeRes Project.res [VERSIONINFO] FileVersion=...+1

to increase the buildnumber or

ChangeRes Project.res [VERSIONINFO] FileVersion=1.2.3.4

to set complete version. You can also set any other version resource part.

See: http://www.tiriss.com/changeres for more info

Regards

Tjipke van der Plaats

Comments are closed.