-
Notifications
You must be signed in to change notification settings - Fork 229
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
Forward compatibility for refresh update sites button change #1080
Conversation
plugins.WorkflowPluginTest.sshGitInsideDocker is the only test failing now, reckon that's related to the change? @timja |
Unsure, but it is failing in plugin manager code so better safe than sorry. I've reran it in case there was an upstream failure |
@@ -88,7 +88,7 @@ public void checkForUpdates() { | |||
// The check now button is a form submit (POST) with a redirect to the same page only if the check is successful. | |||
// We use the button itself to detect when the page has changed, which happens after the refresh has been done | |||
// And we check for the presence of the button again | |||
WebElement checkButton = find(by.link("Check now")); | |||
WebElement checkButton = find(by.css("form[action='checkUpdatesServer'] .jenkins-button")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
better to use the id?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The button prior to this PR didn't have an ID
I had assumed the old button would have been wrapped in a form, instead it does some JS magic to do the post instead.
The test is failing in the plugin manager so likely needs adjusting |
Testing jenkinsci/jenkins#7770