How do you enable Safe Merge and Dry Run? Navigate to Dry Run won't prompt you to complete the merge If you’d like to check your potential merge but don’t intend to finalize it just yet, Recent main and feature branch revisions, runs predefined automation jobs or TeamCity How does it work? Safe Merge creates a temporary merge commit combining the most Requested merge without actually merging potentially harmful changes into the main branch. With Safe Merge, you can run integration checks on the Layer of protection to the main branch to ensure that a merge commit doesn't result Read this article to learn more about Automation parameters in Space and how to use them.Īre you working on a fast-paced project on a growing team? You can now add an extra Secrets let you provide jobs with sensitive data like passwords or access tokens. Such parameters are common for the entire project, like a URL for a service or a file path.

Provide project secrets and parameters to a job.

See the list of predefined parameters in this article. You can get a current Git commit ID, a job execution number, information about the worker operating system, and other context data.

Get details about job execution context.

Parametrize later steps in your build using parameters calculated in previous steps.įor example, use parameters for an image that runs your build and dynamically resolve it during build execution. We introduced a new DSL block, job.parameters, where you can define parameters and provide their default values.īefore running a job, users can change these default values, choose another Docker image to run on, or provide custom command-line parameters.

You can now reference Automation parameters in most of the fields in the Automation script.

We reworked and improved the entire parameters subsystem in Space Automation! Now, it's much more than just a way to provide env variables for your jobs.

Download jetbrains space docker