Integration with pipelines (CI)
[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:
- Deploying or associating a pipeline with an application and/or components
- Provide status information (either through a separate command like
odo pipeline statusor integrated into something likeodo status. - Modifying a pipeline (swapping pipeline definition or adding/removing stages& steps)
Note: this may be a good candidate for a plugin.
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 odo pipeline status, to me that is something that is out of the scope as it is specific to outer loop.
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 odo pipeline ..., there are some samples:
odo pipeline search - find existing pipeline templates to create/associate with
odo pipeline add <named-pipeline> - add an existing pipeline
odo pipeline - could show existing associated pipelines
odo pipeline status [pipeline-name] - shows the status of a pipeline
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 /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
This feature is still valid
/lifecycle frozen