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.

Sign up for GitHub

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

Jump to bottom

Add instruction about how to release component and make sure changes are included in the pipeline releases #606

Closed
gaoning777 opened this issue Jan 3, 2019 · 4 comments
Closed

Add instruction about how to release component and make sure changes are included in the pipeline releases #606

gaoning777 opened this issue Jan 3, 2019 · 4 comments
Assignees
@gaoning777
Labels
area/components kind/bug priority/p2

Comments

@gaoning777
Copy link
Contributor

No description provided.

@gaoning777
Copy link
Contributor Author

/assign gaoning777

@gaoning777
Copy link
Contributor Author

Will add the instruction after the component integration tests are added: #611

@vicaire
Copy link
Contributor

vicaire commented Mar 26, 2019

What is the status on this one?

@gaoning777
Copy link
Contributor Author

We have a component release script in our release process.

@snyk-bot snyk-bot mentioned this issue May 26, 2021
Open
Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
@jlewi
Create a python3.8 version of the worker image (kubeflow#606)
4c3f7d2 
* Create a python3.8 version of the worker image

* Related to kubeflow/testing#560
* We need this because we need a newer (3.8) version of pylint
  to allow for python3.8 syntax like f strings.

* In this pass we eschewed the following packages which I don't think we
  need anymore

  * ksonnet
  * helm
  * glide (should be using go modules and staged builds)
  * docker
  * nodejs (should be using staged builds)

* Create a skaffold config to build the image.

* Add gcloud and kube-rsa.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gaoning777 gaoning777

Labels
area/components kind/bug priority/p2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gaoning777 @vicaire