Closed jstrachan closed 3 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Provide feedback via https://jenkins-x.io/community.
/close
@jenkins-x-bot: Closing this issue.
the next phase of the modularity work is creating a new jx CLI based on small modular binary plugins.
The idea is to provide a similar CLI for jx 2.x or 3.x built from the ground up with binary plugins so it’s easier to incrementally refactor / replace / improve the code, it’s quality, reporting and testing.
As part of this effort it would be good to review the UX and try improve it so it’s more intuitive - while also allowing for more flexibility & to support different personas. Eg someone administrating Jenkins X versus a developer working on some microservices may want different CLI sub commands.
From a UX perspective we may want to align with other UX approaches - eg https://github.com/knative/client/blob/master/conventions/cli.md & integrate with other CLIs as plugins like tekton / istio CLIs?
There is a PoC for the new 3.x CLI at jenkins-x/jx-cli