allure-framework / allure-framework/allure2

Add ability to Jira environment variables to Allure properties

Open
#1,104 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
5.5k
Forks
782
Avg merge
2d 33m
Merged PRs (30d)
16

Description

**Is your feature request related to a problem? Please describe.**
I am intending to use the Jira plugin to post test results to Jira from Jenkins. For the ALLURE_JIRA_USERNAME and ALLURE_JIRA_PASSWORD I would like to set them using Jenkins' credentials. Unfortunately, the allure function is below is unable to access credential variables. It can access parameters or global variables only. I do not wish to set the password in either.

Function that is unable to read Jenkins credentials:
`allure([
includeProperties: false,
jdk: '',
properties: [],
reportBuildPolicy: 'ALWAYS',
results: [[path: 'allure']]
])`

**Describe the solution you'd like**
It would be very useful if we could pass the environment variables and their values to the function through the properties list.

**Additional context**
Error given is "Exception in thread "main" io.qameta.allure.exception.PropertyNotFoundException: Required property not found: ALLURE_JIRA_PASSWORD"

Contributor guide

Open the contributing guide

Research direction

Start by tracing the Jenkins allure function, its properties list, and the Jira plugin handling of ALLURE_JIRA_USERNAME and ALLURE_JIRA_PASSWORD. Confirm how credential-backed environment variables are exposed and define done as allowing those values to be passed through properties without requiring parameters or global variables.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.