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

e2e: remove dependencies on k8s-kind node #1438

Closed
cofyc opened this issue Dec 27, 2019 · 1 comment · Fixed by #2036
Closed

e2e: remove dependencies on k8s-kind node #1438

cofyc opened this issue Dec 27, 2019 · 1 comment · Fixed by #2036
Assignees
Labels
test/e2e e2e test

Comments

@cofyc
Copy link
Contributor

cofyc commented Dec 27, 2019

Feature Request

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

Current CI relies on k8s-kind node which is not scalable and will fail if k8s-kind is not available.

node('k8s-kind') {
dir("${PROJECT_DIR}"){
deleteDir()
unstash 'tidb-operator'
if ( !(BUILD_BRANCH ==~ /[a-z0-9]{40}/) ) {
stage('upload tidb-operator binary and charts'){
//upload binary and charts
sh """
cp ~/bin/config.cfg ./
tar -zcvf tidb-operator.tar.gz images/tidb-operator charts
filemgr-linux64 --action mput --bucket pingcap-dev --nobar --key builds/pingcap/operator/${GITHASH}/centos7/tidb-operator.tar.gz --file tidb-operator.tar.gz
"""
//update refs
writeFile file: 'sha1', text: "${GITHASH}"
sh """
filemgr-linux64 --action mput --bucket pingcap-dev --nobar --key refs/pingcap/operator/${BUILD_BRANCH}/centos7/sha1 --file sha1
rm -f sha1 tidb-operator.tar.gz config.cfg
"""
}
}
}
}

Describe the feature you'd like:

Remove dependencies on k8s-kind node.

@tennix tennix added the test/e2e e2e test label Dec 30, 2019
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test/e2e e2e test
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants