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

branch names with two JIRA ticket ID's fail #46

Open
kevin-- opened this issue Jul 10, 2024 · 1 comment · May be fixed by #50
Open

branch names with two JIRA ticket ID's fail #46

kevin-- opened this issue Jul 10, 2024 · 1 comment · May be fixed by #50
Assignees
Labels
bug Something isn't working

Comments

@kevin--
Copy link

kevin-- commented Jul 10, 2024

Repro

  • build a branch with a name that has two ticket IDs in it
  • e.g. bugfix/PRJ-4976-also-fixes-PRJ-5027
  • seems like the script finds two keys successfully, but the request fails

CircleCI Step Output

Script

#!/bin/bash --login -eo pipefail
#!/bin/bash

# This script requires Bash v4+ or zsh.
# MacOS on CircleCI ships with Bash v3.x as the default shell
# This script determines which shell to execute the notify script in.

if [[ "$(uname -s)" == "Darwin" && "$SHELL" != "/bin/zsh" ]]; then
  echo "Running in ZSH on MacOS"
  /bin/zsh -c "setopt KSH_ARRAYS BASH_REMATCH; $JIRA_SCRIPT_NOTIFY"
else 
  /bin/bash -c "$JIRA_SCRIPT_NOTIFY"
fi

Log

Running in ZSH on MacOS
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Issue keys found:
PRJ-4976PRJ-5027
Notification type: build
Posting payload to CircleCI for Jira Forge app
jq: parse error: Invalid escape at line 1, column 250
Error parsing response
Exiting...

Exited with code exit status 1
@marboledacci
Copy link
Contributor

Just to confirm, this is happening on MacOS right?

@marboledacci marboledacci self-assigned this Dec 20, 2024
@marboledacci marboledacci added the bug Something isn't working label Dec 20, 2024
@marboledacci marboledacci linked a pull request Dec 20, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants