RTECO-1003 - Fix teardown_env: use resource property syntax for SERVER_NAME#3469
Merged
naveenku-jfrog merged 2 commits intomasterfrom May 5, 2026
Merged
RTECO-1003 - Fix teardown_env: use resource property syntax for SERVER_NAME#3469naveenku-jfrog merged 2 commits intomasterfrom
naveenku-jfrog merged 2 commits intomasterfrom
Conversation
naveenku-jfrog
added
safe to test
agrasth
approved these changes
May 5, 2026
naveenku-jfrog
force-pushed
the
jfrogpipelines
branch
from
62addb4 to
af22bd1
Compare
naveenku-jfrog
added
safe to test
fluxxBot
approved these changes
May 5, 2026
naveenku-jfrog
added
safe to test
…R_NAME
The plain pipeline variable ${server_name} is not resolved inside a
Jenkins step's buildParameters (it is only available in bash execution
blocks). Fix by writing the server name components to the
cli_coreapps_env_details resource in setup_cli_test and reading them
back with the ${res_<resource>_<key>} syntax that JFrog Pipelines
resolves at the configuration level:
prefix="${server_name%${suffix}}"
write_output "cli_coreapps_env_details" "prefix=${prefix}"
write_output "cli_coreapps_env_details" "suffix=${suffix}"
Both deploy_environment and teardown_env now compose SERVER_NAME as:
"${res_cli_coreapps_env_details_prefix}${res_cli_coreapps_env_details_suffix}"
This removes the hardcoded "cli" literal and fixes the Jenkins job
failing with "ACTION and SERVER_NAME are mandatory parameters".
Co-authored-by: Cursor <cursoragent@cursor.com>
naveenku-jfrog
force-pushed
the
jfrogpipelines
branch
from
4137ed4 to
5165127
Compare
naveenku-jfrog
added
safe to test
naveenku-jfrog
added
safe to test
naveenku-jfrog
added
safe to test
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
${server_name}
pipeline variable is not resolved in Jenkins step buildParameters (only available in bash execution blocks). Usecli${res_cli_coreapps_env_details_suffix}— the same pattern already used indeploy_environment` — so Jenkins receives a non-empty SERVER_NAME and the environment_operate job no longer fails with "ACTION and SERVER_NAME are mandatory parameters".masterbranch.go vet ./....go fmt ./....