allure-framework / allure-framework/allure2
Required property not found: ALLURE_JIRA_ENDPOINT
- Dominant language
- HTML
- Stars
- 5.5k
- Forks
- 782
- Avg merge
- 2d 33m
- Merged PRs (30d)
- 16
Description
We are using Allure Bamboo plugin: allure-2.13.5 (same issue was on allure-2.13.3) and JIRA Allure plugin.
**To Reproduce**
Steps to reproduce the behavior:
1. Run test via maven command in Bamboo (JUNIT 4)
2. Allure report tab
3. Allure report was not generated
4. See error: Caused by: org.buildobjects.process.ExternalProcessFailureException: External process '/bin/bash /usr/local/allure-2.13.5/bin/binary/bin/allure generate -o /data/bamboo/current/temp/1595937362497-1/report /data/bamboo/current/temp/1595937362497-0/e08cd4b1-39c6-432d-86d7-d8db9fd46a29 /data/bamboo/current/temp/1595937362497-0/9de27bc0-c5f3-4d8f-b8c2-7f5cde67f38b' returned 1 after 1810ms
Exception in thread "main" io.qameta.allure.exception.PropertyNotFoundException: Required property not found: ALLURE_JIRA_ENDPOINT
If we deleted 2.13.5\allure-2.13.5\plugins\jira-plugin from Bamboo, the report was generated.
Variables for Jira are set in Bamboo.
**Expected behavior**
Report is generated
Contributor guide
Research direction
Start with the installed plugins/jira-plugin and reproduce the Bamboo `allure generate` command with the JIRA variables configured. Compare the failing run with the run where the JIRA plugin is removed; done means the report is generated without the missing ALLURE_JIRA_ENDPOINT error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100