Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion src/main/scss/pluginSetupWizard.scss
Original file line number Diff line number Diff line change
Expand Up @@ -263,7 +263,6 @@
top: 0;
right: 0;
left: 0;
padding: 0 10px;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

possible to add a test that suggested plugin link works?

its very rare for someone to use setup wizard while developing as its automatically skipped so something like this can slip through.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

possible to add a test that suggested plugin link works?

The "None" link is already in InstallWizardTest.wizardInstallSuggestedTest. I can update this test to cover "All" and "Suggested" links, but I don't understand why the CI didn't catch this issue for 2.527. 🤔

Running ATH locally fails:

JENKINS_VERSION=2.527 mvn test -Dtest=InstallWizardTest#wizardInstallCustomPluginsTest

(pass with JENKINS_VERSION=2.526)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If ATH already covers this then its fine, do you know what change broke it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If ATH already covers this then its fine, do you know what change broke it?

TBH, I didn't get yet the root of the issue.

From 2.526...2.527 comparison, and focusing on package.json changes, I suspect the following bumps:

  • postcss-loader from 8.1.1 to 8.2.0
  • saas from 1.91.0 to 1.92.1

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://stackoverflow.com/a/7525678 disagrees:

at least in my test, it does not reliably detect if an element is covered by another due to CSS positioning.

Have you tried it / found other sources?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you tried it / found other sources?

I tried it as part of jenkinsci/acceptance-test-harness#2178.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but I don't understand why the CI didn't catch this issue for 2.527. 🤔

it did -> jenkinsci/acceptance-test-harness#2175

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice:

Element <a class="plugin-select-none" href="#"> is not clickable at point (643,92) because another element <input class="form-control" name="searchbox" type="text"> obscures it

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://github.com/jenkinsci/acceptance-test-harness/runs/50269977447 because renovate is force pushing over PRs and the fail will eventually be hard to find when this PR is merged and released.

height: 2.75em;
z-index: 100;
background: rgb(0 0 0 / 0.03);
Expand Down
Loading