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

November 2nd Community Meeting #457

Closed
zhangtbj opened this issue Oct 31, 2020 · 5 comments
Closed

November 2nd Community Meeting #457

zhangtbj opened this issue Oct 31, 2020 · 5 comments

Comments

@zhangtbj
Copy link
Contributor

  • Please add a topic in this thread and add a link to the Github issue associated with the topic.
  • Please make sure you give folks enough time to review/discuss the topic offline on Github before coming into the meeting
  • (optional) Paste the image of an animal smile
@otaviof
Copy link
Member

otaviof commented Oct 31, 2020

#419 -- talk about source vs. sources vs. inputs, and touch on upon introducing v1alpha2, as well as raise any concerns and ideas regarding the EP.

image

@qu1queee
Copy link
Contributor

qu1queee commented Nov 2, 2020

  • Build validations and error messages
  • Extending the Build controller ownerreferences
  • BuildRun conditions enhancement

dog

@adambkaplan
Copy link
Member

Announcement - https://shipwright.io is live!

image

"Mallard Duck 4628" by Joanna Lee Osborn is licensed under CC BY 2.0

@zhangtbj
Copy link
Contributor Author

zhangtbj commented Nov 2, 2020

Just FYI about the buildpack buildstrategy step refinement: #455

russian-blue-cat

@qu1queee
Copy link
Contributor

qu1queee commented Nov 2, 2020

Meeting minutes:

  • we discussed [EP] Remote Artifacts #419 . We would like to keep spec.source but also introduce spec.sources to not break the API. Also, we want to stick to the v1alpha1 for a while. @otaviof to provide new changes on the proposal.
  • we discussed the need of treating the Build Status.Reason with more care. We would introduce error codes prepended to the Build, so that the error message modifications become not that important. Ideally the error codes should not change over time, allowing third party dependencies to be able to rely on the error codes.
  • we discussed the need of extending the ownersreferences a Build have , to include secrets. This will allow the Build controller to reconcile on changes of that resource, ensuring further validations of the Build config can happen after the Build was created.
  • @adambkaplan introduced the now available https://shipwright.io . Also this is a call for action for the community, in order to get more contributions around blog posts for the shipwright/build.
  • @zhangtbj brought some nice enhancements around shrinking the amount of steps we need for the Buildpacks strategies, via Modify buildpacks sample build strategy to use updated pattern from Tekton catalog #455 .
  • @adambkaplan also mention that he would provide updates on WIP - Operator sdk v0.18 #443 later this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants