This repository was archived by the owner on Nov 12, 2018. It is now read-only.
Keep pipeline/job name and trigger comment consistence #18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
report to github independently
Partial-Bug: theopenlab/openlab#46