You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Key Differences

Whilst both Continua and FinalBuilder Server (FBS) are both Continuous Integration Servers, they quite different in how they operate. Continua CI was designed based on the feedback of FinalBuilder, and with a view to making it appeal to more users (FinalBuilder Server is only of use to FinalBuilder Users). The differences in concepts between the two products make it difficult to create an automated migration from FBS to Continua.  

Working with FinalBuilder Projects

Perhaps the biggest difference for FBS users is where the FinalBuilder Project Files live. In FBS, the project FB project files are managed by FBS and FBS projects reference FB projects. In Continua, your FinalBuilder Project files must be in a version control that is referenced by your Configuration. Continua is not tied to FinalBuilder in any way, FinalBuilder is just one of a number of different Build Runner Actions available. 

Where and when the build Runs

FinalBuilder Server projects all run on the same machine, the one where FinalBuilder Server is installed. This unfortunately limits how many builds can be run concurrently. FinalBuilder Server also doesn't allow multiple builds of the same project to run concurrently, so for example a CI build triggered by a checkin, and a manually started build for the same project cannot run at the same time. The main reason for this is that the working folder and source code are managed by the FinalBuilder project.

Continua CI uses Build Agents to run the builds. Agents can be installed on the same machine as Continua Server, or on other machines. Each agent can run multiple concurrent builds(limited only by hardware resources), and each build get's its own working folder and copy of the source code (which is managed by Continua). When a build is queued in Continua, it's requirements (compilers & other tools needed) are evaluated against the available Agents capabilities, and a suitable agent is selected. The build will run when a suitable agent is able to run the build. This may be immediately or at a later time. If no suitable agent is available, then the build will stay on the queue until one becomes available or the build is cancelled by a user.

Continua and FinalBuilder

 

  • No labels