Have you answered the Jenkins X survey yet?
If no, then
Decomposition of Jenkins X
This document outlines the work for decomposing Jenkins X into a series of reusable libraries.
At the moment, the source code that comprises the main JX binary is tightly coupled and difficult to work on. Changes have unintended consequences and this makes the codebase fragile.
One of the design goals in Accelerate is to have a Loosely Coupled Architecture - in particular:
The goal is for your architecture to support the ability of teams to get their work done—from design through to deployment—without requiring high-bandwidth communication between teams.
The main JX repository contains over 250k lines of code, creating Apps / Extensions / Binary Plugins is difficult without adding a dependency back onto the JX repo.
It should be possible to separate the repository out into a series of reusable libraries so only what is needed can be imported.
There are currently a number of proposed repositories/modules, some of these are currently in flight.
- jx-api: JX CRDs / Installation Requirements
- jx-kube-client: A helper module to create a Kubernetes rest config
- jx-vault-client: Deprecated this has been implemented to aid decomposition, it will not be supported longer term.
- go-scm: All SCM operations
- jx-kube/jx-helpers: It may make sense to refactor some of the higher level utils/kube functions within JX into its own package to make them reusable.
- Metapipeline Client
- codegen: this currently exists within the JX repository and is often copied between projects.
- Version Streams: Would these make sense to be moved out of JX?
- Updatebot (jx create pr)? This would have value outside of the core JX codebase
- Storage APIs?
- Cloud APIs?
2.1. Action Plan
- Agree on a way forward!
- Ensure Kubernetes Dependency Updates PR is merged.
- Re-introduce jx-api as a dependency within jx
- Test and Release
Once we have completed this once, we should be able to repeat the following process a number of times
- Identify code to be extracted
- Extract code into new repo
- Release new repository
- Reintroduce library as a dependency inside JX
- Repeat as required.
2.2 Considerations for New Repositories
All new repositories should aim for the following:
- Basic documentation to explain how the module should be used
- A full set of linters, suggesting (asciicheck bodyclose deadcode dogsled dupl errcheck goconst gofmt goimports gosec gosimple govet ineffassign interfacer misspell staticcheck structcheck typecheck unconvert unparam unused varcheck), ideally add gocyclo, nestif & gocritic
- Tests (we should define a base level for code coverage, I’d expect this to be quite low initially)
- Go Report Card
- Should aim to use Semantic Versioning
- Change Logs
Q: It may be possible to template this out? or even use a buildpack to create this?
3. Acceptance Criteria
I think we can say that this has been successful when new Apps / Operators / Plugins can be created for Jenkins-X without having to depend on the JX repository. We must provide all the wiring to make this easy.
It should be easier to do the right thing, than the wrong thing.
When should we start this? We should aim to start this immediately, new functionality should be written in this decomposed way, if we ultimately decide that this is a bad idea, Its far easier to refactor something into the JX codebase than it is to refactor something out.
I have an idea for a module? Great, add it to the list.
Shouldn’t we plan out what modules we are going to need first? It’s very hard to understand exactly what we can extract in a timely manner, without trying to do it. I’m expecting there to be a number of failed attempts / false starts on this - and this is ok. For instance, we may discover that we need to perform a refactor inside JX before we can pull out a module, this is ok. It’s all part of continuously improving.
Won’t extra modules add additional overhead? Yes they will, but they will also bring much larger advantages. We should aim
dependabot (on a weekly schedule) to update dependencies in sub projects, afterall, this is what we would expect
the community to use. If we find that we are constantly version chasing from one module to the next, then that code is too
highly coupled and we need to rethink (refactor or take a different approach)
5. Additional Benefits
It may make sense to use this as an opportunity to dog-food Jenkins-X. We should create a buildpack to allow the easy creation of new modules that contains all of the build & lint configuration required.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.