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

February 1st, 2021 Community Meeting #551

Closed
qu1queee opened this issue Jan 28, 2021 · 5 comments
Closed

February 1st, 2021 Community Meeting #551

qu1queee opened this issue Jan 28, 2021 · 5 comments

Comments

@qu1queee
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 😸
@qu1queee
Copy link
Contributor Author

qu1queee commented Jan 29, 2021

@adambkaplan
Copy link
Member

Demo of the ko tool - #553 (comment)

image

@adambkaplan
Copy link
Member

Long term - submit as a sandbox project to CNCF or CD Foundation

@imjasonh
Copy link
Contributor

imjasonh commented Feb 1, 2021

Notes about ko that I shared on the call: https://hackmd.io/9RNfkSRDTVuLjUJ583XsOw?view

@qu1queee
Copy link
Contributor Author

qu1queee commented Feb 1, 2021

Meeting minutes:

  • We discussed Improve BuildRun Failure State Transitions #558 , we agree on aiming for the One-try shot approach. Tekton does a similar approach for Tasks/TaskRuns. @SaschaSchwarze0 to follow-up on the corrections we will need to do in the code for achieving this.
  • @xiujuan95 provide some insights on a PoC to support building from local source code. This is basically a flow where we push the user source code into a registry, and then we pull it into the Tekton workspace of a BuildRun. In this approach there is the need of having a new strategy, that prepend a step from where the source code image will be pulled. From the community call, if there is something from the PoC that could go into Tekton, we should do that. For CodeEngine, we will continue spiking on this PoC, mainly around how to enhance the performance. Also, to fully support this feature, we need the CLI, @qu1queee mentioned an ongoing work based on Define root command and initial subcommands cli#2
  • We spoke about Using Builds in Tekton pipelines #529. Custom Tasks still a very alpha feature in Tekton, but it will be good to continue prototyping this idea in combination with Shipwright. This would also serve as good feedback for the Tekton community.
  • @adambkaplan provide us a reminder on the new mailing list.
  • @imjasonh provide us a demo around https:/google/ko and we are looking forward for adopting this into our repository.
  • @zhangtbj provided more info on the rational behind Enhance PodInformer in Tekton side for pipeline controller #559 . This would be probably available on the next Tekton release.
  • @adambkaplan started a discussion around long term goals of the project, e.g. into which communities we could evolve. Nothing concrete at the moment.

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

3 participants