![]() ![]() Relative paths need to be relative to something, and in windows that is typically the Current Directory for the process, however this is not viable in a multi-threaded application. The best practice is to fully expand the relative path before using it. ![]() Side Note: FinalBuilder does not support using unrooted relative paths. This will give us the root folder of our repository, which we can then use as the basis for other path variables. The REPO variable has a default value of ".", we will use the Path Manipulation action to expand that relative path when our build starts, using the FBPROJECTDIR variable as the base path. You can of course modify these variables to suite your needs. So to deal with this, we will define some FinalBuilder Project Variables. This means our folder structure above will be rooted differently for each build. The reason for this is to allow multiple builds of the same configuration to be run concurrently (for example, building different branches at the same time). Build WorkspaceĬontinua CI runs each build in a separate, clean build workspace folder. This is the file structure I'll be using as the example in this post. Don't forget to add ignores for the finalbuilder log file as you don't want to commit that to the repo. Note the Output folder is ignored by our version control system (via. So in a typical repository, you might have a folder structure that looks something like this : fbp8 for FinalBuilder 8), as that will make it possible to diff project file changes using your usual diff tool (we use Beyond Compare 4). Make sure you save your projects in uncompressed format (ie. We typically create a Build folder in each repository that has our FinalBuilder projects, installer scripts etc. This will ensure that the Continua CI agent will be able to access the projects. The very first thing we need to do is add our FinalBuilder project to our version control system. I'm going to assume you are familiar with FinalBuilder to speed this along. This allows the best of both worlds, develop and debug your build process on your development machine, and then later run it on your CI server. In this post, I'm going to look at how to structure a FinalBuilder project so that it will run on your dev machine, or on your Continua CI Server without modification. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |