How can I run a finalbuilder project multiple times. This would have to be in finalbuilder server as well.
What I am trying to do is use a parameter file to execute within a finalbuilder project. Currently if I start the project up passing in the paramter file. It will work fine. If I then try and start a second project up with a different parmeter file, it does not start.
What I am trying to do is have a backend project file the executes and loads parameters from a build startup parameter file. This way I will only have 1 project file. This reduces down fixing various issue across many projects.
What about using the Include Project action inside a “master” project? Then you can just iterate through the multiple runs, specifying different settings via the variables.
Thanks for the response! The Include Project action can be used and have it start up this project many times? Does this affect the LCK file that is executed!
Now I do see how and Can use a different project as an include like what I did before with my VBScripts so I would have a frontend type script that loads the include project. And the only thing could be that this frontend project has the VARIABLES used for the include project.
Is this what you were referring to? Sorry trying to understand your Include Project action.
Yes, that's exactly it. The Include Project action can load another project and pass various variable values to it at runtime.
You will need to have two projects, though - a master project and a "child" project. This should be worthwhile in the long run, because it helps keep your structure clean.
Angus, Thanks for the feedback. Actually we get even more complexed. What I will have then is this:
1. Main project - Does all the stuff that is unique to this build, with parameters that can be passed.
2. Include Project - Does all the Global items and housed in a global location for all projects to use.
3. A Staging project for the above that pass in paramters to the main project since we build various projects from one projects, or in Perforce we branch and want to build using the latest location.
***** Note: This is the one I was after for executing the project with many parameters passed *****
4. An Execute Startup project, that will check the lck file for the Staging project for that related project. This one will go away quickly so other projects can execute other projects. **** Like a queuing project ***
I will have to execute my old wait process and read in a startup file if the project is executed with other paramters.
This is where I would love to load balance across many servers so if one is not executed I can push the project to that machine to launch.
Also, this is where Finalbuilder server would be implemented. with a wait process or retry for the job that wants to be executed with the triggers required.
This of coarse would have to be via CMD line since there are MANY automated ways to execute this process.
If you know of a better way please feel free to let me know!
How can I use the system variables from the main project within the include project, for example I use %FBPROJECTDIR% throughtout the projects and if I want to use this variable within the include project, how can I do this. Thiis would be the only issue I am seeing with an standard include project that is housed in a central location.
The actual variable %FBPROJECTDIR% will always evaluate relative to the running project (ie the included project.) If the included projects are located in other directories, this will be a different value.
My recommended solution would be to define a project variable in the child projects called (for instance) ROOTDIR and then set this variable to %FBPROJECTDIR% as part of the Include Project action in the parent. Then you can use %ROOTDIR% in place of %FBPROJECTDIR%.
Thanks for the feeback, I already thought this would be the case it would be nice to have some global variable setting that can be passed to the included projects that are not re-evaluated. For example PWD(present working directory). It would be nice to pass this to another script to have the second project utilize from the working directory that it was called upon.