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.

Sign up for GitHub

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

Jump to bottom

Implement devfile support #2467

Closed
sspeiche opened this issue Dec 17, 2019 · 7 comments
Closed

Implement devfile support #2467

sspeiche opened this issue Dec 17, 2019 · 7 comments
Labels
area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
2.0

Comments

@sspeiche
Copy link
Contributor

Implement devfile support per agreed upon implementation plan #2290

This is needed to support new model for inner loop (hot redeploy) touch points and further work on supporting specific runtimes.
@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 Dec 17, 2019
@sspeiche sspeiche added this to the 1.2 milestone Dec 17, 2019
@rajivnathan rajivnathan mentioned this issue Dec 17, 2019
Closed
7 tasks
@kadel
Copy link
Member

kadel commented Dec 18, 2019

The first stage will be just consuming devfiles (odo push).
A detailed description will be in #2470

@rajivnathan
Copy link
Contributor

/area devfile

@openshift-ci-robot openshift-ci-robot added the area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. label Dec 18, 2019
@kanchwala-yusuf kanchwala-yusuf mentioned this issue Jan 29, 2020
Closed
@kadel kadel mentioned this issue Feb 10, 2020
Closed
@jichenjc
Copy link
Contributor

jichenjc commented Mar 6, 2020

@kadel could you please help to show where we can find when the devfile will be in release ? I was told odo-init-image will be replaced by this devfile feature, can I know when it might happen? Thanks

@sspeiche sspeiche modified the milestones: 1.2, 1.3 Mar 17, 2020
@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 Jun 15, 2020
@girishramnani
Copy link
Contributor

/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 Jun 19, 2020
@girishramnani
Copy link
Contributor

This issue is quite huge as we can observe the https://github.com/openshift/odo/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Fdevfile
but currently features that are essential to have feature parity that are left are https://github.com/openshift/odo/issues?q=is%3Aopen+is%3Aissue+label%3Arequired-for-v2+label%3Aarea%2Fdevfile

Now mostly all of them have people assigned to them (except 1) and many have PRs as well. so this epic will be done for 2.0 milestone.

@girishramnani girishramnani mentioned this issue Aug 19, 2020
Closed
@girishramnani
Copy link
Contributor

the feature parity so far is attained and we have another epic #3782 for follow up for devfile support.
Closing this issue as the AC is achieved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
7 participants
@kadel @sspeiche @openshift-bot @girishramnani @jichenjc @rajivnathan @openshift-ci-robot