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-28154] Reproduce in unittest #17

Closed

Conversation

Projects
None yet
3 participants
@olivergondza
Copy link
Member

commented Jun 19, 2015

JENKINS-28154

I tried to exercise as much operators/keywords as possible, though only in (membership operator, not foreach separator) seems to cause this problem. I also whitelisted some methods.

@jenkinsadmin

This comment has been minimized.

Copy link
Member

commented Jun 19, 2015

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

@olivergondza

This comment has been minimized.

Copy link
Member Author

commented Jun 23, 2015

@jglick

This comment has been minimized.

Copy link
Member

commented Jul 21, 2015

If you mark this

@Ignore("TODO JENKINS-28154")

I would consider it mergeable.

@olivergondza

This comment has been minimized.

Copy link
Member Author

commented Jul 21, 2015

It can be merged as is after jenkinsci/groovy-sandbox#26 is integrated 😉.

@jglick

This comment has been minimized.

Copy link
Member

commented Aug 19, 2015

Once #22 is merged, you should merge with master and this will get rechecked.

@jglick

This comment has been minimized.

Copy link
Member

commented Aug 20, 2015

BTW it was not necessary to close this, as when #23 is merged, GH will automatically display this as merged as well (since the branch head would be an ancestor of the master branch head).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.