Build BETA Requirements

[qu1queee]

Idea:

We would like to discuss with the community around what features/issues/enhancements we would like to have for moving out of Alpha into a BETA release.

For new issues related to BETA, please tag them with the beta label

[qu1queee]

Must-have:

• Bump tekton pipeline pkg
• Bump operator-sdk pkg
• Bump go dev env
• Bump kube version ( >= v1.18 )

List of key features:

• Support list of "env" variables in the Build spec #224 Support list of ENV variables in the Build spec( e.g. should make them available at the pod level )
• Automatically trigger the first BuildRun #82 Automatically trigger the first BuildRun
• leverage tekton SCM trigger support #51 Integrate with tekton triggers(events) for building images. "Event trigger"
• Define tag policies for images #171 Define Tag policies for images( e.g. autogenerate tag by commit id )
• Move to Conditions instead of Status in the BuildRun #307 Move to Conditions for the CRD´s
• Sample build strategies should be secure by default #169 SSL by default
• s2i support (@sbose78). Open question around which strategy would be the desired for openshift.

Tekton missing features:

• HA support
• Liveness and Readiness support
• QPS/Burst support
• Reduce metrics

Users feature requests:

• Feature Request: Trigger builds on build definition changes #303 Trigger builds on Build definition changes
• Support Ruby runtime in Paketo

[sbose78]

Could we also review buildv1 Items with this label somehow pertain to getting equivalent buildv1 function in buildv2 ?

[sbose78]

We'll need to have tls enabled in community strategies #425

[qu1queee]

@sbose78 regarding

Could we also review buildv1 Items with this label somehow pertain to getting equivalent buildv1 function in buildv2 ?

Lets move that discussion for the next community session, what do you think?

[qu1queee]

@sbose78 pls chime in if you think we need to address something from your above comments soon.

[adambkaplan]

I think we should add Volume support as a beta feature. This would involve significant changes to the API

#478

[qu1queee]

https://github.com/shipwright-io/build/milestone/3 is open, closing this issue in favor of that. We will be having grooming calls where we can discuss the milestone state and if changes require to be done.