Build and test Python without bazel

[chaodaiG]

What would you like to be added:

Build and test Python without bazel, the related bazel rules are:

• py_binary
• py_test

Things to be considered:

• This will need to co-exist with current bazel rules for a short while, delete Python test targets from bazel once this confirmed working
• Test driven by make rule and bash scripts
• Ensure hermetic testing, including fixed tools version, like python, python3, dependencies
• Test results are in junit results format

Why is this needed:

This is part of #23796

Recommended testing approach:

• Make test invokable by make test
• Create a PullRequest with change, manually run job by commenting /test pull-test-infra-test-beta
• [Optional]: if there is any tool that needs to exist in test image, update image at

  test-infra/config/jobs/kubernetes/test-infra/test-infra-presubmits.yaml

  Line 145 in 6e0d21e

  - image: gcr.io/k8s-staging-test-infra/kubekins-e2e:v20211005-06df33eb71-test-infra

/sig testing
/help

[k8s-ci-robot]

@chaodaiG:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

What would you like to be added:

Build and test Python without bazel, the related bazel rules are:

• py_binary
• py_test

Things to be considered:

• This will need to co-exist with current bazel rules, we'll migrate everything over at once
• Test driven by make rule and bash scripts
• Ensure hermetic testing, including fixed tools version, like python, python3, dependencies
• Test results are in junit results format

Why is this needed:

This is part of #23796

/sig testing
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[khalludi]

/assign

[chaodaiG]

/assign

As mentioned in #24034, I will start working on this issue based on @khalludi 's effort

[BenTheElder]

IMHO we should make this just py_test / py_lint, we don't need PAR or anything like that -- we will package things in docker images or not at all.

I think we already have py_test movement?

[chaodaiG]

IMHO we should make this just py_test / py_lint, we don't need PAR or anything like that -- we will package things in docker images or not at all.

I think we already have py_test movement?

yeah we already have all of the py_test and py_lint working. it should be fine to mark this as done

[chaodaiG]

/close

[k8s-ci-robot]

@chaodaiG: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.