scm-sync-configuration-plugin icon indicating copy to clipboard operation
scm-sync-configuration-plugin copied to clipboard

"Display SCM Sync Status" hides parts of the jenkins ui

Open novas0x2a opened this issue 10 years ago • 15 comments

If we enable "Display SCM Sync Status" the overlay covers parts of the jenkins ui; this can be seen:

  • if you have a long executor list, scrolling to the bottom will make the sync stats overlay cover the bottom executors, making it impossible to see them.
  • it covers the bottom of the console output, cutting off the last few lines.

We've tested this in 1.583 and 1.593.

novas0x2a avatar Dec 12 '14 22:12 novas0x2a

Same here, it gets worse if there are errors, as the footer increases with height and covers more of the page.

crossrail-jenkins avatar Aug 05 '15 13:08 crossrail-jenkins

Same for me

Mikhael-Danilov avatar Oct 03 '16 16:10 Mikhael-Danilov

Go into Configure system, and scroll down to the SCM Sync configuration section, then uncheck the "Display SCM Sync Status" checkbox.

markhu avatar Nov 21 '17 22:11 markhu

This is also a problem when you aren't logged in so you aren't able to dismiss the errors. There should be a hard limit of 5-10 errors shown, for anything beyond that it should be suggested to enable the logger and/or have a dedicated SCM Status page somewhere.

dragon788 avatar Mar 14 '18 18:03 dragon788

Can confirm this issue is plaguing us as well. With SCM Sync Status enabled, and with a long list in the log, the user is prevented from logging and therefore cannot clear the log to fix the issue. The workaround I use is to use Chrome developer tools to hide the footer, log in, then clear the log. This realistically makes use of SCM Sync Status completely broken. Any ETA on a fix for this?

ryanback avatar Mar 29 '18 14:03 ryanback

I believe the fix is in the code but they need to create a new release and push it to the Jenkins plugin repository. The build posted previously by another user worked in our environment, and we are looking to build an internal version ourselves just to make sure it's always available for our processes.

dragon788 avatar Mar 30 '18 02:03 dragon788

The problem gets worse on new versions of Jenkins. It looks like they are now html encoding the text that plugins add to the footer, as a results the hyperlink with a javascript onClick() is displayed in print but admins are unable to click the link, therefore you can not dismiss the GUI, which as stated above takes up progressively more and more space as errors stack up

dsmorse avatar Nov 13 '18 18:11 dsmorse

Does anyone have any workarounds for this issue?

aodeniyide avatar Nov 14 '18 05:11 aodeniyide

Can we execute the javascript that normally executes in the "click here" in the jenkins script console or something?

mroelandts avatar Jan 09 '19 09:01 mroelandts

@ryanback has the solution we were using as well before we simply disabled the plugin entirely. We've been moving to config as code and using SCM as a 'backup' rather than as a driver for the changes didn't really make sense to us.

dragon788 avatar Jan 09 '19 13:01 dragon788

In Chrome, I was able to right click and hit inspect element. I picked the elements which were huge and hiding them. Until I was able to hide the HTML of scm sync error message, disabled the sync status and applied. ugh! Lucky me!

ghost avatar Feb 18 '19 01:02 ghost

If you're using an ad blocker in your browser, you can add this element to the "block list". Now you will never see it anymore, and if you want to see it, just disable adblocker for your jenkins again

mroelandts avatar Feb 18 '19 08:02 mroelandts

To @aodeniyide, @MatthiasRoelandts and others... There is a quite simple workaround using Chrome and the Developer Tools... Go to the "Console" tab and enter "removeLog()" at the ">" prompt. This will purge the log for good!

jdall avatar Mar 12 '19 14:03 jdall

The markup is corrupted, therefore you must enter removeLog() in the js console manually. Tested in Safari / macOS Mojave.

robertoschwald avatar May 24 '19 10:05 robertoschwald

Is there any chance to fix in the near future? other than doing removeLog() in console

dineshviswanath avatar Dec 20 '19 10:12 dineshviswanath