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

Make SecureGroovyScriptTest work in PCT with Lockable Resources #352

Merged
merged 1 commit into from
Nov 16, 2021

Conversation

basil
Copy link
Member

@basil basil commented Jun 13, 2021

See jenkinsci/bom#552. While trying to add Lockable Resources to the BOM, I started tripping on this test. The test assumes there is one ._script element in the form, but when Lockable Resources is present there is another one earlier on the page for Lockable Resources. The test finds that one instead (it's looking for the first one) and then goes off the rails. Instead I'm having the test pick the last one rather than the first one, which in this case is the one that it's looking for. This gets the test to pass both with and without Lockable Resources present.

@basil
Copy link
Member Author

basil commented Jul 31, 2021

Any chance this could be merged so that we can add Lockable Resources to BOM compatibility runs?

@timja
Copy link
Member

timja commented Jul 31, 2021

@bitwiseman

@basil
Copy link
Member Author

basil commented Nov 16, 2021

@car-roll Any chance this could be merged in order to improve BOM compatibility runs?

@car-roll car-roll merged commit d9b052e into jenkinsci:master Nov 16, 2021
@basil basil deleted the lockable-resources branch November 16, 2021 18:50
@car-roll car-roll added the tests label Nov 16, 2021
@jglick jglick added test and removed tests labels Dec 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants