March 8th, 2021 Community Meeting

[qu1queee]

• 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 😸

[zhangtbj]

• There are more test failures in the PR after switch to Github Action, I manually re-ran the test several times. Add some retry, or...?

[sbose78]

Got some things to discuss on the webhook-driven Builds:
#51

[sbose78]

Usage of ClusterBuildStrategy in an exploratory project: https://github.com/sabre1041/ansible-builder-shipwright : Grab an “Execution Environment Definition” file from a Git repo, do an in-cluster build and deploy an Ansible control node from it.

[adambkaplan]

Shipwright operator spinning up - https://github.com/shipwright-io/operator

[qu1queee]

Meeting minutes:

• We discussed the ongoing issues around CI. Mainly two dimensions, one is that the infrastructure where we run might lead to issues before running the tests or timeouts while running the tests. The second dimension is around flaky test that we still have. From @imjasonh we still have rigid tests that we should improve.
• We discussed an issue where @sbose78 provided some updates. We discuss different ways on how to address the current limitations with Tekton Triggers. As a next step we should provide a TEP for allowing Tekton triggers to support other non Tekton CRDs. @sbose78 to confirm. In general we are looking for collaboration here, to leverage both Tekton and Shipwright. @gabemontero have more insights on this topic in general.
• We discussed a prototype on using Shipwrigh/Build to generate an Ansible execution environment. A new Ansible strategy should become part of Shipwright/Build upstream. While discussing this @zhangtbj mentioned the need to expose more information on our default strategies via our website. @sbose78 brought the point on enhancing our Try It! main README. There is an open PR for enhancing this and another side discussion to also improve this, see Main README is referencing the organization name rather than the Build controllers #441 .
• From @alicerum , looking for feedback on Initial foundation of the CLI application cli#4 .