-
Bug
-
Resolution: Won't Fix
-
Critical
-
Jenkins 2.277.1 running on Red Hat Enterprise Linux 7.9 EC2 instance
When I try to save a newly created job by clicking either the Save or Apply buttons, I do not
receive a green message saying that the job configuration has been saved. It just leaves me in the job and doesn't retain any changes. Normally when the Apply button is clicked it presents a green message saying that it is saved. And normally when clicking the Save button it exits from the created job and back to the main job window. None of which is happening at this moment and not sure why.
This is also happening when we attempt to clone prior existing jobs. We cannot make any new changes to jobs as they're not being saved. We just updated our Jenkins release from v2.263.4-1.1 to 2.277.1-1.1. I have attached the jenkins log file and screenshots of how it should normally work when clicking these buttons on job creation and/or configuration. I've also attached screenshots of what is actually happening when we click the Save/Apply buttons during job creation and/or editing a previously created job. This is a major blocker as we cannot create, clone, modify, new and existing jobs currently in Jenkins.
Just FYI - I scoured and parsed through all the current Jenkins issues to date and could not find any issue related to what we're currently experiencing.
The deprecated coding-webhook plugin was the root cause of the issue..
As noted in the 2.277.1 upgrade guide and changelog, please remove deprecated plugins. Please remove plugins with known security issues. Please remove plugins that are unused.
- is duplicated by
-
JENKINS-65505 Cannot save job configuration for maven projects with Jenkins 2.289
- Closed