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

Tekton pipeline client should use generate name #683

Merged
merged 3 commits into from
Jun 16, 2020

Conversation

jlewi
Copy link
Contributor

@jlewi jlewi commented Jun 15, 2020

  • Use generateName to generate names for pipelines; we can use labels
    to attach semantic/metadata information to the pipeline.

Related to #682: tekton_client.py submitting pipelineruns with names that
are too long

@k8s-ci-robot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kubeflow-bot
Copy link

This change is Reviewable

* Use generateName to generate names for pipelines; we can use labels
  to attach semantic/metadata information to the pipeline.

Related to kubeflow#682: tekton_client.py submitting pipelineruns with names that
 are too long

* tekton_client should use PythonFire to generate the CLI rather
  than arg parser.
@jlewi jlewi marked this pull request as ready for review June 15, 2020 20:11
@jlewi
Copy link
Contributor Author

jlewi commented Jun 15, 2020

/assign @Bobgy

/assign @IronPan
/assign @Ark-kun

@Ark-kun or @IronPan would one of you mind doing a quick review of this? I need these changes to be merged to see if it fixes the issues with the Tekton pipelines. Its 4am right now in Shanghai so @Bobgy won't be around for a while.

@Ark-kun
Copy link

Ark-kun commented Jun 16, 2020

/lgtm
There seem to be many extra changes in this PR...

@jlewi
Copy link
Contributor Author

jlewi commented Jun 16, 2020

@Ark-kun Mostly cleanup related to testing the original change

  • Replacing ArgParser with Fire made it easy to add an entrypoint to allow running tekton_client.py locally which was one of the easiest ways to test it
  • Likewise adding python3 support to run_e2e_workflow.py made it easier to run locally
  • Improved the exception handling in retries to print out the stack trace because retry logic was making it hard to see where the error was actually occuring.

@jlewi
Copy link
Contributor Author

jlewi commented Jun 16, 2020

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlewi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 44fef48 into kubeflow:master Jun 16, 2020
jlewi pushed a commit to jlewi/testing that referenced this pull request Jun 16, 2020
* The CLI code isn't actually doing anything when invoked with "junit-and-upload". This was a bug introduced by kubeflow#683

Related to kubeflow#685
jlewi pushed a commit to jlewi/testing that referenced this pull request Jun 16, 2020
* The CLI code isn't actually doing anything when invoked with "junit-and-upload". This was a bug introduced by kubeflow#683

Related to kubeflow#685
k8s-ci-robot pushed a commit that referenced this pull request Jun 17, 2020
* The CLI code isn't actually doing anything when invoked with "junit-and-upload". This was a bug introduced by #683

Related to #685
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants