-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
Currently the BuildTrigger is the only Publisher that gets called when a job is
renamed.
The snippet of code that seems to do that is (Job.java line 340):
// update BuildTrigger of other projects that point to this object.
// can't we generalize this?
for( Project p : parent.getProjects() ) {
BuildTrigger t = (BuildTrigger)
p.getPublishers().get(BuildTrigger.DESCRIPTOR);
if(t!=null)
}
How about creating a notification interface and alerting all plugins
implementing this interface when a job is renamed? This will allow people
writing plugins to also make use of this nice functionality.
[JENKINS-891] More elegant way of doing job renames
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Component/s | New: core [ 15593 ] | |
Component/s | Original: www [ 15484 ] |
Workflow | Original: JNJira [ 130964 ] | New: JNJira + In-Review [ 200260 ] |
Wrong component: this issue has no relevance for the tasks plugin.