Message-ID: <1986539270.1725.1406073207662.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1724_1615171050.1406073207662" ------=_Part_1724_1615171050.1406073207662 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
When editing global configuration of a SonarQube instance in Jen= kins (adding, removing or renaming) you may end up with jobs that are no lo= nger associated with an existing SonarQube instance.
Here is a script to get the list of these jobs:
Here is a script to reassign broken jobs to a different SonarQube instan=
ce (just remember to update the
newSonarInstance value to=
the name of the SonarQube instance you want to use for broken jobs):