Keep pipeline job and comment consistent #46
Comments
kiwik
added a commit
to theopenlab/project-config
that referenced
this issue
Apr 11, 2018
In Kubernetes/OpenStack integration scenario, we should keep pipeline name, job name and trigger comment consistence, that build consist user experience for developer from k8s community, and easy to understand how to trigger the specific jobs when the job failed. - update all of pipeline name, job name and trigger comment for k8s jobs - run all of jobs in separate pipeline when PR commit and update, and report to github independently - branch-v1.10.0 should be just branch-v1.10 Partial-Bug: theopenlab/openlab#46
kiwik
added a commit
to theopenlab/openlab-zuul-jobs
that referenced
this issue
Apr 11, 2018
In Kubernetes/OpenStack integration scenario, we should keep pipeline name, job name and trigger comment consistence, that build consist user experience for developer from k8s community, and easy to understand how to trigger the specific jobs when the job failed. - branch-v1.10.0 should be just branch-v1.10 Partial-Bug: theopenlab/openlab#46
animationzl
pushed a commit
to theopenlab/openlab-zuul-jobs
that referenced
this issue
Apr 11, 2018
In Kubernetes/OpenStack integration scenario, we should keep pipeline name, job name and trigger comment consistence, that build consist user experience for developer from k8s community, and easy to understand how to trigger the specific jobs when the job failed. - branch-v1.10.0 should be just branch-v1.10 Partial-Bug: theopenlab/openlab#46
kiwik
added a commit
to theopenlab/project-config
that referenced
this issue
Apr 12, 2018
powellchristoph
pushed a commit
to powellchristoph/cloud-provider-openstack
that referenced
this issue
Jan 19, 2022
In Kubernetes/OpenStack integration scenario, we should keep pipeline name, job name and trigger comment consistence, that build consist user experience for developer from k8s community, and easy to understand how to trigger the specific jobs when the job failed. - update all of pipeline name, job name and trigger comment for k8s jobs - run all of jobs in separate pipeline when PR commit and update, and report to github independently - branch-v1.10.0 should be just branch-v1.10 Fixes theopenlab/openlab#46
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Kubernetes/OpenStack integration scenario, we should keep pipeline name, job name and trigger comment consistence, that build consist user experience for developer from k8s community, and easy to understand how to trigger the specific jobs when the job failed.
The text was updated successfully, but these errors were encountered: