Repository navigation
[JENKINS-64553] ItemListener.onUpdated() isn't fired when modifying Item #11870
Description
When a Seed job creates a new Item (e.g. a Job) by this plugin ItemListener.onCreated() is fired as expected.
When a Seed job is executed for second (or yet another) time ItemListener.onUpdated() isn't fired even the Item is modified by this way.
Originally reported by pajasoft, imported from: ItemListener.onUpdated() isn't fired when modifying Item
- assignee: mawinter69
- status: Closed
- priority: Major
- component(s): core, job-dsl-plugin
- label(s): 2.452.2-fixed
- resolution: Fixed
- resolved: 2024-05-27T17:44:35+00:00
- votes: 1
- watchers: 6
- imported: 2025-11-24
Raw content of original issue
When a Seed job creates a new Item (e.g. a Job) by this plugin ItemListener.onCreated() is fired as expected.
When a Seed job is executed for second (or yet another) time ItemListener.onUpdated() isn't fired even the Item is modified by this way.
Activity
jenkins-infra-bot commentedon Jan 5, 2021
Remote link associated with this issue:
jenkins-infra-bot commentedon May 24, 2024
mawinter69:
Raw content of original comment:
The root cause is in core where after posting the xml the ItemListener is not called. Same happens when using the CLI to update a job.
jenkins-infra-bot commentedon Jun 18, 2024
Raw content of original comment:
On my side this is not fully fixed after upgrading to 2.452.2 At least not using organization folder. When saving them via UI all good, but not via JobDSL or CLI
Basically I have an inline pipeline with a marker file (pom.xml) that build everything that have a pom.xml at the root.
When updating this inline pipeline via CLI or JobDSL it's not propagated on child. So when running job and "old" pipeline is used.
When saving via UI everything works and is updated.
Not sure if it's the same bug or something related to multibranch or even `inline-pipeline`
I will try to give reproduction steps later
jenkins-infra-bot commentedon Jun 19, 2024
Raw content of original comment:
I've created a repo to reproduce the issue: https://github.com/jonesbusy/jenkins-reproduce
My workaround for my use case is to reforce the scan of the organisation folder which update children items.
Not sure if it's the normal behavior when updating jobs via CLI or JobDSL. Saving via the UI rescan the organization folder which update the items
So it's probably a different issue than this one