Have discussed this with Paul and it's part of the variable scope problem. There are a lot of variables that we have to jump through hoops to get at different times during the jobs. May not be possible to expand these variables for this message until something changes on the Jenkins side or we redesign how we connect to Jenkins.
My 5c - Yes it would be good if we can expand these variables but the message is useful for debugging so I would prefer to keep the 'Obtained Jenkinsfile from' at this position in the code even if we are not able to expand variables at this point.
Have discussed this with Paul and it's part of the variable scope problem. There are a lot of variables that we have to jump through hoops to get at different times during the jobs. May not be possible to expand these variables for this message until something changes on the Jenkins side or we redesign how we connect to Jenkins.
My 5c - Yes it would be good if we can expand these variables but the message is useful for debugging so I would prefer to keep the 'Obtained Jenkinsfile from' at this position in the code even if we are not able to expand variables at this point.