-
Bug
-
Resolution: Duplicate
-
Minor
-
None
During my update from 2.235.5 to 2.249.1 everything worked fine so far. Anyhow: This morning a few users of several Jenkins installations called me, as their Build monitor tab disappeared.
What I did:
- Create a new jenkins docker container "jenkins/jenkins:lts" (2.249.1)
- Stop the old container
- Start the new container with the linked Jenkins Homedir (08:41 PM)
I still have the old "SCM Sync Configuration Plugin" that pushes all changes to the jenkins configuration immediately to my backup GIT repository. Therefore I saw, that at 08:42PM, directly after the new Jenkins container was started, the config.xml was updated by jenkins and the build monitor plugin configuration was removed.
At this point, no plugin updates were performed, just the jenkins migration. I decided to create this issue here, as the config removal was due to the update.
Build Monitor version 1.12+build.201809061734
- duplicates
-
-
- Closed
-
- is caused by
-
-
- Resolved
-
- is duplicated by
-
-
- Closed
-
- links to
[JENKINS-63678] Jenkins upgrade to 2.249.1 removes Build monitor tab with statusFilter view
| Link |
New:
This issue duplicates |
| Summary | Original: Jenkins upgrade to 2.249.1 removes Build monitor tab | New: Jenkins upgrade to 2.249.1 removes Build monitor tab with statusFilter view |
| Link |
New:
This issue is caused by |
| Remote Link | New: This issue links to "PR-4466 (Web Link)" [ 25913 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
| Link |
New:
This issue is duplicated by |
| Comment |
[ Hey everyone,
To perform the upgrade, I followed the standard procedure of creating a new Jenkins Docker container with the "jenkins/jenkins:lts" image (version 2.249.1) and then stopped the old container. Upon starting the new container, I noticed that my "SCM Sync Configuration Plugin" was still active, which automatically backs up the Jenkins configuration to a GIT repository. Checking the backup, I observed that the config.xml file had been updated by Jenkins, right after the new container started, and the build monitor plugin configuration was removed. It's important to note that I hadn't performed any plugin updates at this point, only the Jenkins migration. I decided to bring this issue to the community's attention as the configuration removal seems to be directly linked to the update. Has anyone else experienced a similar problem? ] |