From 7ae31c3b552310ac601a8a37be00d6c24b226837 Mon Sep 17 00:00:00 2001 From: Carlos Villavicencio Date: Fri, 26 Jan 2024 12:12:56 -0500 Subject: [PATCH 1/5] Put server_url back in example_config --- tests/example_config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/example_config b/tests/example_config index f48fedcdc..01501d23d 100644 --- a/tests/example_config +++ b/tests/example_config @@ -16,7 +16,7 @@ # Full url to the ShotGrid server server # e.g. https://my-site.shotgrid.autodesk.com # be careful to not end server_url with a "/", or some tests may fail -server_url : +server_url : http://0.0.0.0:3000 # script name as key as listed in admin panel for your server script_name : test script name api_key : test script api key From c824c87478d8edbbf723b0e99d6d6dabbafaaa5c Mon Sep 17 00:00:00 2001 From: Carlos Villavicencio Date: Fri, 26 Jan 2024 12:28:34 -0500 Subject: [PATCH 2/5] Add variable group name --- azure-pipelines-templates/run-tests.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/azure-pipelines-templates/run-tests.yml b/azure-pipelines-templates/run-tests.yml index dc2734750..6f79d949a 100644 --- a/azure-pipelines-templates/run-tests.yml +++ b/azure-pipelines-templates/run-tests.yml @@ -31,6 +31,9 @@ parameters: name: '' vm_image: '' +variables: + group: sg-credentials + jobs: # The job will be named after the OS and Azure will suffix the strategy to make it unique # so we'll have a job name "Windows Python27" for example. What's a strategy? Strategies are the From 25ad721626ba5d32bf45c6680b8be5483dd765c4 Mon Sep 17 00:00:00 2001 From: Carlos Villavicencio Date: Fri, 26 Jan 2024 12:31:19 -0500 Subject: [PATCH 3/5] Update syntax --- azure-pipelines-templates/run-tests.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/azure-pipelines-templates/run-tests.yml b/azure-pipelines-templates/run-tests.yml index 6f79d949a..e21551e9f 100644 --- a/azure-pipelines-templates/run-tests.yml +++ b/azure-pipelines-templates/run-tests.yml @@ -104,9 +104,9 @@ jobs: # Pass the values needed to authenticate with the Shotgun site and create some entities. # Remember, on a pull request from a client or on forked repos, those variables # will be empty! - SG_SERVER_URL: ${{ variables.ci_site }} - SG_SCRIPT_NAME: ${{ variables.ci_site_script_name }} - SG_API_KEY: ${{ variables.ci_site_script_key }} + SG_SERVER_URL: $(variables.ci_site) + SG_SCRIPT_NAME: $(variables.ci_site_script_name) + SG_API_KEY: $(variables.ci_site_script_key) # The unit tests manipulate the user and project during the tests, which can cause collisions, # so sandbox each build variant. # Ideally, we would use the agent name here. The problem is that the agent name is in a build From 4267f33480a395ad882ae6e2be3247b7c198b2c5 Mon Sep 17 00:00:00 2001 From: Carlos Villavicencio Date: Fri, 26 Jan 2024 12:31:30 -0500 Subject: [PATCH 4/5] Update syntax --- azure-pipelines-templates/run-tests.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/azure-pipelines-templates/run-tests.yml b/azure-pipelines-templates/run-tests.yml index e21551e9f..85d93af2a 100644 --- a/azure-pipelines-templates/run-tests.yml +++ b/azure-pipelines-templates/run-tests.yml @@ -104,9 +104,9 @@ jobs: # Pass the values needed to authenticate with the Shotgun site and create some entities. # Remember, on a pull request from a client or on forked repos, those variables # will be empty! - SG_SERVER_URL: $(variables.ci_site) - SG_SCRIPT_NAME: $(variables.ci_site_script_name) - SG_API_KEY: $(variables.ci_site_script_key) + SG_SERVER_URL: $(ci_site) + SG_SCRIPT_NAME: $(ci_site_script_name) + SG_API_KEY: $(ci_site_script_key) # The unit tests manipulate the user and project during the tests, which can cause collisions, # so sandbox each build variant. # Ideally, we would use the agent name here. The problem is that the agent name is in a build From 5038928d35f69ba467630cdfcfc3d184c9a9dacf Mon Sep 17 00:00:00 2001 From: Carlos Villavicencio Date: Fri, 26 Jan 2024 12:33:41 -0500 Subject: [PATCH 5/5] Change yml block --- azure-pipelines-templates/run-tests.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/azure-pipelines-templates/run-tests.yml b/azure-pipelines-templates/run-tests.yml index 85d93af2a..7c7edf8e9 100644 --- a/azure-pipelines-templates/run-tests.yml +++ b/azure-pipelines-templates/run-tests.yml @@ -31,9 +31,6 @@ parameters: name: '' vm_image: '' -variables: - group: sg-credentials - jobs: # The job will be named after the OS and Azure will suffix the strategy to make it unique # so we'll have a job name "Windows Python27" for example. What's a strategy? Strategies are the @@ -60,6 +57,9 @@ jobs: maxParallel: 3 + variables: + group: sg-credentials + # These are the steps that will be executed inside each job. steps: # Specifies which version of Python we want to use. That's where the strategy comes in.