Hi
I have a FinalBuilder8 project that compiles a VB6 project without any problems when running from FB itself.
However, when this FB project file is used in CI in a stage it will start the FB project, I can see that in the log the forst statements of that project are executed, but when it comes to start the VB6 compiler
it refuses. Nothing to see in the build log that i starts.
When i disable the compile part in the FB8 project file so skipping the compile it runs in CI without problems
It had worked before, it looks like it stopped working after a certain CI update.
To add to this, a FB8 project which build a Visual Studio 2017 project runs fine under CI, only VB6 has this problem
I had alook in the log files CI made. In older log files i see
11:04:54 Prop Define Version
11:04:54 Prop Set Version Numbers
11:04:54 Setting 3 property values on PropertySet propVersionNumber
11:04:54 Property MajorVersion set to 2018
11:04:54 Property MinorVersion set to 01
11:04:54 Property RevisionVersion set to 15
11:04:54 Compile Kaartenbak
11:05:44 Compiler parameters: /m C:\SourceCode\VB6\VB6_Kaartenbak\Dev\Dev\Temp-Kaartenbak.Vbp /out C:\Users\COMPIL~1\AppData\Local\Temp\fbp8788.tmp /outdir C:\Kaartenbak\
in the last one it stops earlier. In the life log in CI you can see the same
12:09:03 Prop Define Version
12:09:03 Prop Set Version Numbers
12:09:03 Setting 3 property values on PropertySet propVersionNumber
12:09:03 Property MajorVersion set to 2018
12:09:03 Property MinorVersion set to 04
12:09:03 Property RevisionVersion set to 25
Also a test project with only a VB6 compile refuses to run in CI
Usually when a process stops responding like that, it’s because it’s either waiting for input (console apps) or showing a message box (gui apps). The VB6 compiler is a gui application, and it’s notorious for showing messageboxes when something goes wrong. Unfortunately it’s impossible to know what it’s showing as there is no way to see it, and it typically doesn’t write that to a log.
My best suggestion would be to login to the server as the same user that the Continua Agent service runs under, and run the command from the command line and see what happens. I see you have a hard coded path to the vb project file, you should really put the project (and the FB project) into your source code repository and let the CI server manage getting the source code - see this blog post :
https://www.finalbuilder.com/resour…nalbuilder
Mmm that makes sense Peter