Hi Guys, As noted on most of my recent forum posts - we’re running 100% of our deployment logic via FinalBuilder 8 project files through Continua CI’s “FinalBuilder” action. The user interactions that control which branch the FB8 is set to deploy from - are communicated from Continua CI input var…

Hi @ktopaz , There’s no way to submit code changes to Continua CI from FinalBuilder and we don’t currently have plans to implement this. Why not add your build repositories to Continua CI? You could then either: use the files checked out by Continua CI and simplify your FinalBuiilder project; or un…

[image] Sparky: How are you currently triggering your builds? The main advantage of using Continua CI repositories is that you can trigger a build on a commit to the project source code. This is the essence of continuous integration. As we prepare to move from our current FBServer + FB7 to C…

Hi @ktopaz , [image] ktopaz: A developer manually triggers a build on CCI, using variable input form, he specifies a git branch name or a git commit id to build from - these options are passed to FB8 project file which has the internal logic to fetch the exact branch head or commit id and buil…

[image] Sparky: Note that one of these is to allow selection of commit id, in addition to branch and tag name, in the Queue options dialog. That’s great news! Once the commit id selection feature is introduced and we’ll be able to select either a branch name or a commit id - I will modify ou…

Dave, Would it be possible to simply allow the repository branch input fields to allow free input? I am talking about these: [image] If these fields can have their auto-complete still, AND allow free text input that I can later read from a variable ( $Source.RepoName.FreeInput$) It will allow o…

Hi @ktopaz , Sorry, this is not something we can consider. This field is used to select the changesets to associate with the build and is core to the operation of Continua CI. I don’t understand why you would want to enter a value that is not a branch here? Why not use a separate variable? Perhaps y…

That was just a thought based on what you wrote earlier in this thread. A separate variable will do just fine as well. We currently use a custom variable - that is manually populated in the variable input form when starting a build. The only thing I would like to solve here - is the confusion cre…

Hi @ktopaz , Eventually, we will include an input for entering the commit id for each repository. For now, I would suggest making the ‘Input_GitCommitId’ not a required field and describing it as an override e.g. “Enter a commit id to override the branch for (RepoName) repository”. You can then use…