I’m trying out the Artifactory orbs and encountering the same problem on each.
I’d like the build integration’s build number to be my pipeline number, so I added this block to a job:
steps: ... - artifactory/build-integration: build-name: blahblahblah build-number: '<< pipeline.number >>
However this gets interperted as an integer and causes a build error (that annoyingly isn’t caught by the CLI’s validate command):
Type error for argument build-number: expected type: string, actual value: "1234567890" (type integer) Error calling command: 'artifactory/build-integration' Error calling job: 'job' Error calling workflow: 'workflow'
I’ve been unable to force this to be interpreted as a string and have had to resort to storing the pipeline number in an environment variable and using that. I’d like to not have to remember to do that in every job; how can I make the pipeline number a string?