Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect SkipSectionExpression value in azure-pipelines-extensions/Extensions/ServiceNow/Src/Tasks/CreateAndQueryChangeRequest/CreateAndQueryChangeRequestV2/ #1139

Open
hard2reid opened this issue Mar 23, 2023 · 0 comments

Comments

@hard2reid
Copy link

hard2reid commented Mar 23, 2023

When trying to create a new change via an Environment check the call to get the change request number via $(endpoint.url)/api/now/table/change_request?x_mioms_azpipeline_stage_id=$(checks.stageId)&x_mioms_azpipeline_build_id=$(build.buildId)&x_mioms_azpipeline_stage_attempt=$(checks.stageAttempt)&sysparm_fields=number,sys_id,correlation_id
is being called when it should be skipped.
That is because the SkipSectionExpression has "or(eq(eq('$(system.hosttype)', 'checks'), false), or(eq(eq(taskInputs['changeRequestAction'], 'createNew'), false), eq(isNullOrEmpty(variables['CHANGE_SYSTEM_ID']), false)))"
The eq(isNullOrEmpty(variables['CHANGE_SYSTEM_ID']), false)) should be eq(isNullOrEmpty(variables['CHANGE_SYSTEM_ID']), true)).

NOTE: The previous version has the correct flag value of true but for some reason it was changed to false.

What is happening is the call is being made and it returns an empty result and no further calls are made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant