Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-31380] Remove token overlapped build variable. #110

Closed
wants to merge 1 commit into from

Conversation

KostyaSha
Copy link
Member

@KostyaSha
Copy link
Member Author

Token supports options so ${BUILD_ID()} is expected as token. Seems they can't be removed from plugin.

@jenkinsadmin
Copy link
Member

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@slide
Copy link
Member

slide commented Nov 4, 2015

Not sure what you mean it supports options. There are no parameters defined for BUILD_ID.

@slide
Copy link
Member

slide commented Nov 4, 2015

Strange, this works fine for me. It's done via the missingMethod for the context of the Groovy shell.

@KostyaSha
Copy link
Member Author

@slide see test case. As i understand ${VAR()} expected to be a token even VAR exists as standard var. I will think about using groovy templates in some other way.

@slide
Copy link
Member

slide commented Nov 4, 2015

@KostyaSha yes, I know. This is handled via EmailExtScript which is set as the base class for the script for the groovy. When a "method" in this case something like ${BUILD_ID()} is used, the methodMissing in EmailExtScript will be called and will look at ALL TokenMacro's to see if there is something that fits. This is working locally for me after removing BUILD_ID from email-ext.

@slide
Copy link
Member

slide commented Nov 4, 2015

@KostyaSha I was still running on a codebase that had BUILD_ID as a TokenMacro. When I removed it, I found the issue as you did, but I have a fix for it.

@slide
Copy link
Member

slide commented Nov 4, 2015

Will fix this a different way.

@slide slide closed this Nov 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants