Skip to content

Github Job Names with '&' in them cause errors during CR creation. #61

@david-v-pierce-usps

Description

@david-v-pierce-usps

https://github.com/ServiceNow/servicenow-devops-change/blob/729fbe8fa5aa4c5f5192fcc8751a4b4b3d97a83b/src/lib/do-fetch.js#L36C138-L36C150

The pipelinename parameter here doesn't appear to have its inputs encoded, so if I have a pipeline names something like "CR Creation & Update" instead of "CR Creation and Update" it breaks the search, and the creation step will fail because SNOW returns an HTTP 500.

I can rename my pipelines but not having to worry about this would be pretty cool too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions