Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
Description
While a traditional project's config.xml can simply be inspected for plugins it is using, which is useful for example to ensure that the project is not loaded in an inappropriate server, this is not true of Pipeline scripts—steps it uses might be defined in various plugins, or metasteps like checkout might have configuration which refers to various plugins.
There should be a way for the job itself to declare which plugins it wants loaded. The simplest approach would simply be a step which fails if some of the requested plugins are missing or too old:
requirePlugins ['junit@1.6', 'parallel-test-executor']
However as this is logically part of the job configuration as a whole, rather than something to be executed at a particular point in the build, it might make more sense as a JobProperty; a build started with missing plugins would immediately fail with an informative message. Using a property does not preclude defining the list from the script itself, using the properties step.
The configuration form for the property or step could use JENKINS-31582 to inspect the last build and suggest which plugins to list.
Attachments
Issue Links
- depends on
-
JENKINS-31582 Log / document the plugin usage in the flow nodes
-
- Resolved
-
- is duplicated by
-
JENKINS-51557 Plugin Dependency for pipeline files
-
- Fixed but Unreleased
-
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
- links to
Activity
Just a quick status update as I've been unable to push this forward in the last few months: I'm leaving myself assigned so that this shows up on my JIRA board for now, because I hope to be able to get back to it some day.
BUT, I'm posting this so that anyone feeling an itch to push this to completion just feel free to take over. Then either just reassign to you, or ping me privately for any question (related to taking over the development of this, I don't mean any usage question. Because then it'd be the users ML instead).
Thank you!
While commenting on JENKINS-49651 I had an idea that could make this almost automatic:
Extend plugin metadata with (RPM style) Provides for pipeline symbols (& extensions,... ) they implement. With that metadata available in the Update Center a build that tries to use say the junit step could instead of failing the build be paused and the user could be prompted if they want to install the plugin that provides that step of if they want to abort the build:
- Pipeline execution detects unknown step / use of a global / unknown type referenced.
- Pipeline execution paused (like with an input step?)
- Query Update Center metadata if there are plugins that provide the missing references
- Prompt the user to install those plugins or fail the build (possibly saving ignored dependencies)
- User selects to install the missing plugins -> continue the pipeline execution
- maximum user satisfaction
So, we're disagreeing about whether to have a generic require or a plugin specific one?
What about implementing the generic syntax, but with only plugin name for now?
require plugin: 'junit-plugin'Then we have the concept and can consider expanding it (or not) later?