Welcome to Flow Customer Service!

Stay updated with announcements, get answers from the community, and share your feature suggestions with us.
You can also submit a request or send us an email at support@startflowing.zendesk.com.



Geoff Bullen June 7, 2013 7 Tips & Tricks

By default FLOW comes configured to use an in memory data source.  If you want it to save between restarts, add the below to ${FLOW_HOME}\config\flowconfig.groovy.   Create the file if it doesn't yet exist

Note:  ${FLOW_HOME} defaults to ${user.home}\.flow


println "Overriding settings with Flow environment specific file."
    jenkinsCliUrl = 'http://localhost:8082/jenkins'
    jenkinsUrl = 'http://localhost:8082/jenkins'
    schemaStrategy = 'true'
dataSource {
    dbCreate = "update"
    url = "jdbc:h2:file:${System.getProperty("user.home") + "/.flow/"}database/flowDemo;MVCC=TRUE"
    username = "flow"
    password = "flow"


** You should see the text "Overriding settings with Flow environment specific file." in the console

Sylvain Benner June 7, 2013 40 Community Help

I've tried moving my jenkins.war version and setting HUDSON_HOME and FLOW_HOME but I can' t see the Jenkins Jobs section when creating a flow.

How to correctly bind FLOW to an existing Jenkins instance ?

Geoff Bullen June 3, 2013 4 Tips & Tricks

To trigger a FLOW from an external event such as a commit to your version control system simply call the following URL:  


With FLOW_KEY being the Flow name with any spaces replaced by underscores.   For example if your FLOW is called "Continuous Delivery", the URL will look similar to:   http://localhost:8082/flowui/remoteTrigger/Continuous_Delivery

 ** This is how we trigger a FLOW when a commit is made in BitBucket