Skip to content
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

Open
sspeiche opened this issue Jan 27, 2019 · 5 comments
Open

Integration with pipelines (CI) #1238

sspeiche opened this issue Jan 27, 2019 · 5 comments
Labels
area/outerloop Issues or PRs related to outer-loop use cases kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.

Comments

@sspeiche
Copy link
Contributor

[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 status or integrated into something like odo status.
  • Modifying a pipeline (swapping pipeline definition or adding/removing stages& steps)

Note: this may be a good candidate for a plugin.

@sspeiche sspeiche added this to the backlog milestone Jan 28, 2019
@sspeiche sspeiche added the kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks label Jan 28, 2019
@jorgemoralespou
Copy link
Contributor

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?

@kadel
Copy link
Member

kadel commented Feb 2, 2019

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.

@sspeiche
Copy link
Contributor Author

sspeiche commented Feb 4, 2019

@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.

@openshift-bot
Copy link

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

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 6, 2020
@sspeiche
Copy link
Contributor Author

sspeiche commented Jan 7, 2020

This feature is still valid

/lifecycle frozen

@openshift-ci-robot openshift-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 7, 2020
@girishramnani girishramnani added area/component kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation labels Jan 8, 2020
@sspeiche sspeiche modified the milestones: backlog, 1.3 Feb 17, 2020
@sspeiche sspeiche modified the milestones: 2.0, 2.1 (planning) Jun 3, 2020
@kadel kadel added estimated-size/S (5-10) Rough sizing for Epics. Less then one sprint of work for one person and removed estimated-size/S (5-10) Rough sizing for Epics. Less then one sprint of work for one person labels Apr 6, 2021
@serenamarie125 serenamarie125 modified the milestones: 2.3 (planning), 2.4 Apr 26, 2021
@serenamarie125 serenamarie125 modified the milestones: 2.4 (planning), 2.5+ (planning) Sep 7, 2021
@rm3l rm3l removed this from the backlog (planning) milestone Sep 29, 2022
@rm3l rm3l added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Oct 7, 2022
@rm3l rm3l added area/outerloop Issues or PRs related to outer-loop use cases and removed area/component labels Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/outerloop Issues or PRs related to outer-loop use cases kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
Projects
Status: No status
Development

No branches or pull requests

8 participants