Additional configuration options when releasing Python packages to a Python package index

[fridex]

Is your feature request related to a problem? Please describe.

As a user of AICoE-CI, I would like to provide a base container image that should be used during the build process of wheel files so that Python packages are built inside the supplied builder environment (that can have additional libraries required for the build process, e.g. bazel, ...).

As a user of AICoE-CI, I would like to provide an option so that auditwheel repair is run on the built Python wheels to conform desired manylinux standards.

Describe the solution you'd like

Provide required flags and options. It might be good to give it a better design (e.g. say which manylinux standard should be met during the build process for auditwheel repair feature and pick the appropriate manylinux container image automatically under the hood).

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[codificat]

I don't think this has been reviewed yet...
/remove-lifecycle rotten

/kind feature
/triage needs-information
/priority awaiting-more-evidence

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[harshad16]

/lifecycle frozen