-
Notifications
You must be signed in to change notification settings - Fork 243
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
Integration with pipelines (CI) #1238
Comments
What would the experience look like for this feature request? I would be really interested in see if we can fit the experience that would be required into odo or not. We're making decisions before 1.0 GA that will later be difficult to change. @sspeiche Could you provide details on the experience you think a developer would need/want/use? |
I can see odo maybe generating some basic pipeline definitions. But I'm not sure about something like I can see this being a plugin that is outside of odo core. |
@jorgemoralespou This feature isn't a high priority but agree we should have an idea of the experience. I could image a number of flows that would allow it to fit cleanly under a main noun such as
As part of this effort it would be to flush this flow out a bit more. There could be a phase 2 where some pipeline composition could occur by adding steps/tasks to existing pipelines. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
This feature is still valid /lifecycle frozen |
[kind/Feature]
As a Developer, I would like to be able to easily interact with my CI (pipeline) tool so that I don't have to jump between tools I use throughout my development.
Some scenarios include:
odo pipeline status
or integrated into something likeodo status
.Note: this may be a good candidate for a plugin.
The text was updated successfully, but these errors were encountered: