-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
CI Pipeline interface #74
Comments
Also started working on a |
validate-ci
to check whether the CI configuration is valid or notlab ci lint
to check whether the CI configuration is valid or not
That looks cool, can we maybe have some colours and arrows? |
lab ci lint
to check whether the CI configuration is valid or not
Put this up in an effort to support I've already written a working implementation with those changes. Once the API is exposed should be able to bring in the functionality in short order. |
Also relying on these changes for the pipeline interface: jroimartin/gocui#130 |
Have mostly replicated the current progress in https://github.com/rivo/tview which has been nicer to work with overall.
|
[#74] Add (beta) CI Pipeline interface: live view-only
The above has been released in Also |
Is there a way to close the view (except for Ctrl-c)? |
[#74] support exiting `ci view` with ESC and "q"
@twouters Thanks for the feedback, I've added support for exiting with q and esc in |
Put lunixbochs/vtclean#7 up to support cleaning gitlab's trace file response. Hopefully that gets merged in and we can use it directly, but I'll give it a week while I get the remaining changes together in lab. Code for running/retrying jobs has been written and seems to function (pending tests). The vtclean change is to support viewing trace logs in the pipeline interface, which is mostly coded up, but has some formating issues due to the escape sequences returned in the API |
Going to call this good as of #175, any future bugs or features will be tracked in new issues. |
NOTICE: Description fully cannibalized by @zaquestion
Still debating if such a thing should be in lab, but could always move it into its own tool and be called by lab.
Support
Also add
lab ci lint
commandRef: https://docs.gitlab.com/ce/api/lint.html
The text was updated successfully, but these errors were encountered: