Continua API availability?

I’ve seen posts regarding a Continua API, but most of them are from a year or more ago mentioning that the API was not ready yet.

Is there an API at this point?  With the release of FinalBuilder 8 and the incompatibility with FinalBuilder Server, we find the file watcher triggers we used to not b directly translatable to Continua and would like to write an application that would be a file watcher to then trigger a project.

Thanks,

Jeremy

Hi Jeremy

The http api is still planned, but at this stage only a proof of concept has been implemented, as were still focusing on fleshing out features.

What part of the FB Server file triggers did not map to Continua, perhaps we can help resolve that?

Vincent,

We have 2 processes that don’t map cleanly, though it’s not that we can’t change the process to make work with continua.

1. We have 2 licenses of Finalbuilder. This gave us 2 licenses of Finalbuilder Server. We have a project on PC1 that writes out a file to a location that triggers a build on PC2. This enables us to split the task among the two machines to reduce the time it takes (in this case it is building all of our localized installers).

2. We have a service that monitors our defect tracking system (TestTrack by Seapine), and when an item meets a specific criteria (enters a specific state), the service writes a file to a location where then Finalbuilder server triggers a project to build a small module, then when the build is done the service picks up the finished build and emails it to a group of individuals.

Item 1 we have already figured out a way to do. We are working through the approval process to get more agent/builder licenses of Continua, and we can setup a project that then triggers two different projects to build on two different agents.

Item 2 we haven’t found a “clean” solution for other than checking a file in to a repo and create a continua project to watch that repo and then trigger that finalbuilder project.

Hi Jeremy,

Continua has a File System repository type. This polls the file system and detects any file changes. You can then link a repository trigger to this repository to trigger a build when any files change. You can additionally, for example, restrict this to trigger only when files are added and when a file path matches a regular expression.

Thanks for pointing that out, I’d missed it. We’ll be trying this and I’ll get back to you.

The File System Repo is working for us.

Thanks again.