UrbanCode Velocity is the free version of our value stream management tool that is perfect for small teams. We answered basic questions on our “Get Started” page, but here are a few more FAQs about Community Edition.
What are the system requirements for Community Edition?
4 CPU Cores and 8 GBs of RAM is the recommended minimum for Docker Compose installs. Linux, MacOs, and Windows OS are supported. However, the OS support is based on the Docker Platform of your choosing. Since the CE and SE features set are the same, so are their system requirements.
If you are looking to configure Velocity for production however, please follow the recommended system requirements on our documentation. Note: We do not support Docker Compose for production usage.
Is there a tutorial I can follow to get started?
Yes! Our resources page is a great place to start.
If you’re looking for a hands-on tutorial, follow our workbook. The value stream workbook will explain how to configure a working value stream using Jenkins, JIRA, and GitHub.
Are there any sample or template value streams I can follow?
The value streams workbook has a sample value stream, along with a full tutorial, to help you get started:
Our documentation also has a ton of examples on how to construct your value stream to including link rules, metrics, stages, etc.
What is the difference between a Velocity plugin and an integration?
Like the other UrbanCode products, Velocity supports a growing set of plugins. In Velocity, an integration is the instantiation of the plugin itself. Since you might have multiple configuration of a plugin (such as the JIRA plugin configured for different projects or servers), we want to be able to specify a distinction.
Why can’t I download Velocity plugins from the UrbanCode website?
One of the great things about Velocity is that plugin framework handles the management of plugins. UrbanCode Velocity plugins are hosted as Docker images in our Docker registry and pulled automatically during install and upgrade. Once installed locally, UrbanCode Velocity will pull from its internal registry to faster integration runtimes.
If your network team prevents downloads from our public docker registry, you can configure Velocity to pull from a known custom registry located behind your firewall.
How do I connect a configured Velocity integration to my value stream?
Every value stream is composed of the data from your configured integrations, such as JIRA, GitHub, or UrbanCode Build. Today, those integrations must be configured inside the VSM json.
For example, add this snippet to the integrations section of your VSM JSON to assigned two configured integrations:
Once imported, Velocity will automatically grab the values from the integration configured in the settings. If you export the VSM JSON, you’ll see there will more configuration values below your newly mapped integrations.
If you prefer to create a new integration via the VSM JSON, you can supply all plugin configuration values as well. Please refer the plugin document our web site as each plugin requires different values for configuration.