Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warn against version range usage #7731

Merged
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,10 @@ references:
---

Plugins depend on specific versions of libraries and of other plugins, each of which is versioned independently.
Each dependency may have dependencies of its own and different versions of different libraries and plugins may not be compatible with each other.
Each dependency may have dependencies of its own, and different versions of different libraries and plugins may not be compatible with each other.
Moreover, the dependencies can change with each Jenkins release, so managing these dependencies manually can be difficult and time consuming.
Avoid using version ranges when developing plugins, as this reduces the repeatability of builds and can create dependency management problems.
The expected pattern for dependencies is to have pinned dependencies updated by <<Dependabot>> or Renovabot.
MarkEWaite marked this conversation as resolved.
Show resolved Hide resolved

Jenkins has tools that simplify dependency management:

Expand Down
Loading