Start a Velocity development session

Start a Velocity development session from JetBrains

Once you have a Velocity run configuration ready, you can start your first development session.

From the options at the top of the IDE, ensure the run configuration you just created is selected and click either Run or Debug.

• Run - build an image with your code and deploy it to the remote environment. The remote pod now runs with the logic you have in your local IDE. Code changes will be synced to the remote environment and the workload will be updated accordingly (see Making your first code change)

• Debug - run the configuration and debug the application that is currently running in the remote pod (see Hitting your first breakpoint section)

Your development session is ready when the debugger status displays Debugger Connected, or your Kubernetes Pod logs are printed in the Velocity output, prefixed by the remote pod and container names. For example:

Additionally, the Velocity tool window opens, where you can view all related events. From the top of the IDE, you can see the run configuration is running, and you can stop the service as well:

Make your first code change

Once you see logs coming from your application, it means your application is ready and you can start developing with Velocity.

To make a code change and have it synced to the remote pod:

1. Make the code change you would like to apply

2. Save the changes

3. From the Velocity tool window, click S or R:
4. Once you see the K8s logs renew, the new code is already up and running in the remote pod.

Hit your first breakpoint

To debug with Velocity, once you start the Velocity session, set relevant breakpoints from your IDE as you would if you were debugging locally.

Add Breakpoints

End a Velocity development session

From the Velocity terminal (tool window), or from the toolbar at the top of the IDE, click . Once stopped, the original image that was running prior to the Velocity development session is restored.

Stop the Session