/build-$CI_COMMIT_SHORT_SHA.zip -u system -p $CI_DB_PASS --IAgreeToTheEula --clean artifacts: paths: - ./build-$CI_COMMIT_SHORT_SHA.zip ex
/build-$CI_COMMIT_SHORT_SHA.zip -u system -p $CI_DB_PASS --IAgreeToTheEula --clean artifacts: paths: - ./build-$CI_COMMIT_SHORT_SHA.zip ex
/citi-demo.conf \ -t $(CI_DB_JDBC) \ -o /app/output/buildArtifact.zip \ -u '$(USER)' \ -p $(PASSWORD) \ --IAgreeToTheEula \ --clean - task
/citi-demo.conf \ -t $(CI_DB_JDBC) \ -o /app/output/buildArtifact.zip \ -u '$(USER)' \ -p $(PASSWORD) \ --IAgreeToTheEula \ --clean - task
with an "Error" severity the exit code (%ERRORLEVEL%) will be set to 1. Issues with a "Warning" severity will not cause the exit code to
/scg/sql-code-analysis-documentation/code-analysis-for-sql-server-command-line
>/<service> --baselineVersion 1 -u <UserName> -p <Password> --IAgreeToTheEula … to - this should be a .zip file (Required) --project (-P
>:<port>/<service> --baselineVersion 1 -u <UserName> -p <Password> --IAgreeToTheEula Added schema option … to - this should be a .zip fi
returnStatus: true, label: "Build", script: "rca build -P \"${ProjectPath}\" -t ${CiDatabaseJdbc} -o \"${BuildArtifactPath}\" -c -f -v -u
returnStatus: true, label: "Build", script: "rca build -P \"${ProjectPath}\" -t ${CiDatabaseJdbc} -o \"${BuildArtifactPath}\" -c -f -v -u
", "-U", "MyUser", "-P", "MyPassword", "-d", "MyDatabase", "-Q", "SELECT 1"] interval: 10s retries: 20 The build step is here being contro
system -p $PROD_DB_PASS --IAgreeToTheEula dependencies: - build artifacts: paths: - ./release-prod-$CI_COMMIT_SHORT_SHA.zip expire_in: 1
/dso/redgate-change-automation/example-ci-cd-pipelines/gitlab
Record). See the next step for more information. When using Azure: Choose a Generation 2 image, as Generation 1 images cannot use GPT for
/redgate-clone/administration/installation-steps/step-1-installation-requirements
/buildArtifact.zip \ -t $(PRODUCTION_DB_JDBC) \ -o /app/output/release.zip \ -u '$(USER)' \ -p $(PASSWORD) \ -f \ --IAgreeToTheEula - task
/dso/redgate-change-automation/example-ci-cd-pipelines/azure-devops
and found no errors or warnings in the sql 1 - CAO did not exit cleanly - please see the logs 2 - CAO had one or more internal errors, me
cmstepone.gif The sections in Step 1 help you complete the custom metric definition. Enter custom metric details Adding a metric name is c
https://www.red-gate.com/assets/purchase/assets/license.pdf. (Required) rca baseline -t jdbc:oracle:thin:@//<host>:<port>/<service> --bas
You may encounter an issue and this error will come up in the logs: FileSystemException: Expected a single volume for partition 1 on disk
/clone4/troubleshooting/common-issues/expected-a-single-volume-for-partition-1-on-disk
a backup using one of three compression levels. Arguments 1 Compression level 1 is the fastest compression, but results in larger backup
/sdc15/using-the-command-line/command-line-syntax/switches-used-in-the-command-line
These instructions only apply to Source Control for Oracle 1. You don't need to follow them in the latest version of Source Control for O
You may encounter an issue and this error will come up in the logs: FileSystemException: Expected a single volume for partition 1 on disk
/clone5/troubleshooting/common-issues/expected-a-single-volume-for-partition-1-on-disk
These instructions only apply to Source Control for Oracle 1. You don't need to follow them in the latest version of Source Control for O
cmstepone.gif The sections in Step 1 help you complete the custom metric definition. Enter custom metric details Adding a metric name is c
Position? 1 Default Value None Accept Pipeline Input False Accept Wildcard Characters false -DatabaseName <String> Name of the database A
When performing a backup on a 64-bit edition of SQL Server, you may encounter the following error: SQL error -1: SQL Network Interfaces:
/sbu6/errors-and-warnings/sql-server-errors/sql-error-1-sql-network-interfaces
These instructions only apply to Source Control for Oracle 1. You don't need to follow them in the latest version of Source Control for O
