Isn't Build Pipeline Plugin just a view on top of independent jobs (connected by build causes, triggers, etc.)?
If so, there's nothing special about such a job. Maybe TransientActionFactory if there's Build Pipeline specific configuration such as a JobProperty, and check for that before creating actions (or in your actions, depending on how caching works exactly). > On 04.10.2016, at 23:06, Gustavo Henrique <[email protected]> wrote: > > Which extension point can I use as alternative to > TransientProjectActionFactory for jobs using the Build Pipeline Plugin? > I have an old plugin that uses: > > public class ProjectAction implements Action { > ... > } > > @Extension > public class ProjectActionFactory extends TransientProjectActionFactory { > @Override > public Collection<? extends Action> createFor(AbstractProject project) { > return Arrays.asList(new ProjectAction(project)); > } > } > > My jobMain.jelly doesn't works for jobs using Pipeline. > > -- > 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/a3a39902-0bc0-4b3b-92e6-fc1ad8140cbc%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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/42945A5C-4630-4EFF-AC1C-C9F309433EF3%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
