Why doesn't Inno Setup compiler set the version info correctly from hudson?

Question

If I run Inno Setup compiler from a command line/batch file it creates an exe with the version information in the file name.

However, when I run from hudson (same command line) I don't get the version information.

Perhaps I am missing something.

Is this a known issue?

This is the way I am doing it in the iss script file.

#define FileVerStr GetFileVersion(SrcApp)

EDIT:

The env vars are all set for all users - not just my login - so the service has access to everything that the command line build does.

EDIT: See my answer for a resolution of this.

Answer 1

You are likely running Hudson on Windows given the technology mentioned.

When there is a discrepancy between what happens on the command line and what Hudson does, it is often because Hudson is running as a service on Windows. This means it is running as the service user, which is distinct from your login account.

I would look for an environment variable that you have defined in your user profile that may enable this behavior, that is not being set for the service user.

Answer 2

I am not exactly sure how to describe how I "fixed" this/worked around it.

It seems the GetFileVersion() method does not use the same base path as the other part of the Inno functionality that determines where the source files/installable files are.

The SAME relative paths used for:

// this is for determining what files get put into the install image
[Files]
Source: ..\Build\ForRelease\MyExeName.exe; DestDir: {app}

and

#define SrcApp "..\Build\ForRelease\MyExename.exe"
#define FileVerStr GetFileVersion(SrcApp)

apparently do not use the same mechanism to resolve the file name/path. So what i did to work around this was to copy the exe file that contains the version info to two additional different locations (aside from ..\Build\ForRelease) - one where hudson starts the processes and also to the path where the inoo script is. (I am too lazy to figure out which one is the one that makes it all work.

Again, this works fine from my batch file but not from hudson. It is essentially a strange interaction with how Inno works I guess.

Answer 3

Like "tim" has said, then relative paths doesn't work as expected for defines.

#define MyAppVer GetFileVersion(SourcePath + "\..\Build\Release\MyExeName.exe")
#if MyAppVer == ""
    #error MyAppVer - Version information not found!
#endif

By prefixing with SourcePath then the relative path will start from the path where the InnoSetup-script is located.