github / github/platform-samples
pre-receive hook script require-jira-issue.sh is not working as expected
- Vorherrschende Sprache
- Shell
- Sterne
- 2.2k
- Forks
- 1.9k
- Ø Merge
- 7 T. 19 Std.
- Gemergte PRs (30 T.)
- 1
Beschreibung
Hello Team,
Copied https://github.com/github/platform-samples/blob/master/pre-receive-hooks/require-jira-issue.sh to the repository in GitHub Enterprise Server. Configured pre-receive hook following steps from https://docs.github.com/en/enterprise-server@3.5/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
`git push` is always failing with the below error.
```
[root@test devops-experiments]# git push origin hook-test
Username for 'https://test.server.com': 729494
Password for 'https://user@test.server.com':
Counting objects: 4, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 328 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: require-jira-issue.sh: failed with exit status 1
remote: grep: Invalid range end
remote: ERROR:
remote: ERROR: Your push was rejected because the commit
remote: ERROR: c975243bb888fc20aee6abec2122f2e4872e712c in hook-test
remote: ERROR: is missing the JIRA Issue 'JIRA-123'.
remote: ERROR:
remote: ERROR: Please fix the commit message and push again.
remote: ERROR: https://help.github.com/en/articles/changing-a-commit-message
remote: ERROR
To https://test.server.com/test/devops-experiments
! [remote rejected] hook-test -> hook-test (pre-receive hook declined)
error: failed to push some refs to 'https://test.server.com/test/devops-experiments
[root@test devops-experiments]#
```
Beitragsleitfaden
Rechercherichtung
Start with pre-receive-hooks/require-jira-issue.sh and inspect the grep expression associated with the reported “Invalid range end” error. Reproduce the push with the example commit messages, then verify that a commit containing JIRA-123 is accepted while a commit without a JIRA issue is rejected.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- git, shell
- Bereich
- devops
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100