Unlike FinalBuilder Server, Continua is not tied to FinalBuilder, FinalBuilder is just another Build Runner. This might appear like a step backwards for long time FinalBuilder Server users, however that tight integration was part of what made it so difficult to extend FinalBuilder Server.
The FinalBuilder Action in Continua only supports FinalBuilder 7. If the FinalBuilder build is later than 7.0.0.1761 then the custom logger will be enabled, so the log will show in a tree rather than a flat text list. This is still a work in progress, we still need to make some adjustments to FinalBuilder's output to get the logging looking 100% in Continua, and it's possible that may not happen until FB8. You can execute FB6 and earlier versions but you will need to add Agent Property collectors (they determine the location of a tool) and then use the Execute Program action.
For Continua to run your FinalBuilder Project, it must live in a version control repository which is linked to the configuration. This is because everything that is needed to build a project must be pushed to the agent.
In the Continia FinalBuilder Action, you will need to point it to the FinalBuilder Project in your repository, for example :
The $Source.MyRepository$ above evaluates to the repositories checkout folder in the build workspace on the agent, FinalBuilderProjects would be where my fb project file lives in my repository.
I encourage you to read the Concepts section in the documentation (there's not a whole lot there right now, we're working on it) before jumping in, purely because Continua is quite different from FinalBuilder Server.
Does that mean we need additional FinalBuilder Pro licenses for every build agent? How about the local agent? Is that licensed with the existing FinalBuilder Pro licenses?
You will need a FinalBuilder license for each agent you want it to run on, whether it is remote or local. Unlike FinalBuilder Server, Continua is not tied to FinalBuilder, it can use MSBuild or other build tools, of course it can use FinalBuilder very well too. We are planning to create a cheaper build machine license for FinalBuilder (although that will be for FB8 not 7).
We want to install Continua CI(Server,Agent and Services) on our Local machines and Final Builder is installed onsome other Build server.Is it possible to connect to Final Builder in the Build server from Continua CI from our local machine? Please suggest us if possible.
Can you please tell me is it necessary that Final Builder and Continua CI should be installed on the same machine?
I have one query regarding this. Is it possible to go only with Continua to perform “all the operations” we had done in Final Builder 7 without uisng FinalBuilder Runner action provided in Continua at all (without installing FinalBuilder as a Continua agent.)
FinalBuilder 7 has around 700 actions, Continua CI has around 50 actions. Continua CI does not have the scripting features of FinalBuilder, limited logic (no loops for example). Yes, for some projects you could just use Continua CI, however if you are already using FinalBuilder, you obbviously have need for a more capable build tool, Continua CI (or any of it’s competitors) will never be able to provide that level of functionality.
You really shouldn’t be adding the .fb7lck and .fbl7 files into your repositories. The .fbpinf file can be stored in a repo, it contains things like auto incremented version numbers etc. If you don’t want these files in your repos, you should probably add them to the ignore files for your repos.