Closed ishaker93 closed 3 years ago
I'm not sure this is related to either the Jira or jq orbs. I'm guessing that the environment variable values have been set to something that bash can't reason with, similar to https://stackoverflow.com/questions/18042369/bash-export-not-a-valid-identifier.
I also meet this issue, the image I use is node:current-alpine during build.
I also meet this issue, the image I use is node:current-alpine during build.
I'm not sure this is related to either the Jira or jq orbs. I'm guessing that the environment variable values have been set to something that bash can't reason with, similar to https://stackoverflow.com/questions/18042369/bash-export-not-a-valid-identifier.
@gmemstr I will check that Thanks.
I also meet this issue, the image I use is node:current-alpine during the build.
did you manage to solve it?
@ishaker93 - If you're using an alpine image, you may need to install bash first
Hello all, If you are al alpine user please see this comment: https://github.com/CircleCI-Public/jira-connect-orb/issues/64#issuecomment-881542494
Orb version: 1.3.0
What happened
install JQ fails:
Here is the output of that step:
-->
The workflow failed because of the JQ installation, The JIRA connection functions on my Jira service management as a change request but without defining the failure or the success of the workflow.
Expected behavior
The success of the workflow but it gives fails because the JQ install fails. Showing the success or the failure of the workflow at the Jira service management change request.