Jenkins setup:
Jenkins 2.452.1
(Unfortunately I can not see much about it, as the installation is on company level and I am lacking permissions to get more info 
)
Anyway, as you already noticed, I am totally new to Jenkins and just want to somehow tackle a problem in the Buildchain of the company, which was not set up by myself and therefore I really know little.
I just hope, that someone, who has more knowledge about the whole thing can easily answer the following question:
We have setup a so called Multipipeline Job for our mobile App.
It is triggered by different events, one of which are PRs created in our Bitbucket Repo.
Here’s the problem: On the first run after creating the PR the environment variables env.CHANGE_ID, env.CHANGE_BRANCH and env.CHANGE_TARGET are not set. After the first successful run, those variables are available in subsequent runs.
For our sonarqube integrations we need this information. It would be very welcome, if they would already be available on the first run, because the sonar quality gates should already be checked on the first run, otherwise people can close the PR without meeting the quality gates for new code.
Can anybody help what I need to do, so the environment variables are set already on the first run?
Any help is much appreciated.
Have a great weekend!
Best regards
Alex