Hello Jesse, I'm afraid I don't completely understand what is wrong and how I should approach the issue.
You seem to have one `Action` holding on to others, which does not make > sense. > I have the exact same situation as in this post [1] <https://jenkins.io/blog/2016/05/25/update-plugin-for-pipeline/#build-actions-vs-project-actions>: I have one Action, the DiceQTResultBuildAction, that takes care of the display and an icon for a build, and it is also the one that the Recorder adds to the build to be preserved with the build. But then I also have DiceQTResultProjectAction, which shows a chart over past builds on the project dashboard, and which I also need to add a route to a special display and to add its own link and icon. This works nicely in the Freestyle project, but again according to this post [1] <https://jenkins.io/blog/2016/05/25/update-plugin-for-pipeline/#build-actions-vs-project-actions>, the build action needs to make the project action discoverable to Jenkins, otherwise the project dasboard doesn't work. Either attach all the `Actions` at top level (`Run.addAction`), or make the > nested structures extend `Object` and implement `RunAction2` on the actual > single `Action`. > By the actual single Action you mean the Build action? What is considered here as a top level? Won't extending Object remove the ability to show icons on the appropriate level? Thank you and best regards, Matej [1] https://jenkins.io/blog/2016/05/25/update-plugin-for-pipeline/#build-actions-vs-project-actions Dne torek, 20. junij 2017 18.31.20 UTC+2 je oseba Jesse Glick napisala: > > You seem to have one `Action` holding on to others, which does not > make sense. Either attach all the `Actions` at top level > (`Run.addAction`), or make the nested structures extend `Object` and > implement `RunAction2` on the actual single `Action`. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b33116b5-115f-42f4-82d0-b08297517c7c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
