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

Support for Builds v2 #4094

Closed
serenamarie125 opened this issue Oct 7, 2020 · 7 comments
Closed

Support for Builds v2 #4094

serenamarie125 opened this issue Oct 7, 2020 · 7 comments
Labels
kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.

Comments

@serenamarie125
Copy link

serenamarie125 commented Oct 7, 2020 •
edited
Loading

Description

As a developer, I want a way to have odo deploy to utilize build guidance in devfile to use Builds v2 as an alternative to classic builds (BuildConfigs)

Builds v2 overview:
https://docs.google.com/presentation/d/1iNDCHpXYBk7OJ1vgrI2zOsYg36q0CeJXT4GsGABsWB8/edit?usp=sharing

Acceptance Criteria

There is a way for odo user to optionally utilize Builds v2 as an alternative to classic builds.
@sspeiche sspeiche added this to the backlog milestone Oct 7, 2020
@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 Oct 7, 2020
@kadel
Copy link
Member

kadel commented Oct 7, 2020

We are basing everything around Devfiles. First, we will need a way to define image build in Devfile v2.

@sspeiche
Copy link
Contributor

sspeiche commented Oct 7, 2020

This about making sure we have a good experience with generating Build CRDs vs BuildConfigs.

@serenamarie125
Copy link
Author

Goal is to have this available with OpenShift 4.8

@girishramnani girishramnani removed this from the backlog milestone Oct 20, 2020
@serenamarie125 serenamarie125 added this to the 2.2 (Planning) milestone Nov 5, 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 Feb 4, 2021
@dharmit
Copy link
Member

dharmit commented Feb 4, 2021

/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 Feb 4, 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 this to odo Project Oct 3, 2022
@rm3l rm3l moved this to To Do 📝 in odo Project Oct 3, 2022
@rm3l rm3l removed the status in odo Project Oct 3, 2022
@kadel kadel added the priority/Medium Nice to have issue. Getting it done before priority changes would be great. label Feb 6, 2023
@kadel kadel added priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. and removed priority/Medium Nice to have issue. Getting it done before priority changes would be great. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels Feb 20, 2023
@rm3l rm3l moved this to To Do 📝 in odo Project Jun 26, 2023
@rm3l rm3l removed the status in odo Project Jun 27, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Nov 2, 2023

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 2, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Dec 2, 2023

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Dec 2, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 2, 2023
@github-project-automation github-project-automation bot moved this to Done ✅ in odo Project Dec 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
Projects
odo Project
Archived in project
Milestone
No milestone
Development

No branches or pull requests
8 participants
@kadel @rm3l @dharmit @sspeiche @openshift-bot @girishramnani @serenamarie125 @openshift-ci-robot