Radek Antoniuk
Radek Antoniuk
warden: Jan, did you have any chance to work on this? Also see the related ticket as this might be quite useful.
[Originally related to: JENKINS-17498]
carlescapdevila: We also need this behaviour for our use case. Many of our projects use a shared library which runs the Jira issue updater: many projects might have not configured...
[Originally related to: JENKINS-10817]
warden: Maybe the "Generate Release Notes" would help in this? In there all the issues affected by Jenkins builds will be identified.
warden: This should be possible via pipeline plugin and environment variables in v. 2.3.
> Using the path: . option causes the token stored in the .git folder to leak. In this case, a breaking change might be reasonable to prevent this risk. Instead...
> Accept this PR now in its current form, but delay a release of the Jira plugin until the October LTS release of Jenkins is available. This takes advantage of...
@topicus-pw-dvdouden thanks for spending time on this. Would you have time to open a PR including a test case for this?
@rijkvanzanten [looking at this discussion](https://github.com/directus/directus/discussions/11897), can you shed some light on the hectic status changes of this issue on the roadmap? I don't understand [why there is no specific issue...