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

chore(*): Rebase hr onto v0.9.8-beta #1345

Merged
merged 61 commits into from
Dec 17, 2019

Conversation

tosone
Copy link

@tosone tosone commented Dec 17, 2019

What this PR does / why we need it:

Rebase hr onto v0.9.8-beta.

/cc @zhujian7

Release note:

Rebase hr onto v0.9.8-beta.

caicloud-bot and others added 30 commits June 21, 2019 20:02
) (caicloud#1160)

* fix: resources not freed immediately after stage finished

* fix: remove retry config
… with 0 (caicloud#1169)

* fix: assign resource requirements of cyclone containers with 0

* test: add some test for apply resource requirements
* feat: support all container logs stream and download

* chore: add unit test for folder logs

* fix: output container name
* fix(kaide): skip ssl verify for gitlab

* fix(kaide): skip ssl verify for gitlab again

* fix(kaide): skip ssl verify for gitlab again and again
…er logs (caicloud#1227)

* chore(vendor): add spf13 cobra

* feat(toolbox): add fstream tool to collect init container logs
caicloud-bot and others added 7 commits September 16, 2019 17:54
…aicloud#1283)

* fix: close websocket when workflow run running completed

* refactor: check wfr regularly to reduce cost
* fix: deleting pod stuck on Terminating status

WorkflowRun GC SHOULD Wait all workflowRun related workload pods
deleting completed, then start gc pod to clean date on PV.Otherwise,
if the path which is used by workload pods in the PV is deleted
before workload pods deletion, the pod deletion process will get
stuck on Terminating status.

* fix(gc): deleting pod stuck on Terminating status

If there are pods not finished and this is not the last gc try
process, cyclone will not start gc pod to clean data on PV
* feat(oauth): cherry-pick from v0.8 to v0.9

* feat(oauth): cherry-pick from v0.8 to v0.9

* fix(oauth): fix golint

* fix(oauth): delete unused code

* fix(oauth): format import path
* fix: update tenant pvc not found error (caicloud#1150)

* fix: argument escape problem (caicloud#1152)

* fix: resources not freed immediately after stage finished (caicloud#1157) (caicloud#1160)

* fix: resources not freed immediately after stage finished

* fix: remove retry config

* fest: skip ssl verify for gitlab (caicloud#1166)

* fix: last line log would be missing if not ended with \n (caicloud#1171)

* [release-1.0] fix: assign resource requirements of cyclone containers with 0 (caicloud#1169)

* fix: assign resource requirements of cyclone containers with 0

* test: add some test for apply resource requirements

* fix: use mkdir to acquire lock in git resolver (caicloud#1170)

* perf: improve git resolver performance with --depth (caicloud#1180)

* fix: sonar qube entrypoint bug fixes (caicloud#1183)

* chore: add debug logs for sonar qube image (caicloud#1182)

* [release-1.0] All container logs (caicloud#1184)

* feat: support all container logs stream and download

* chore: add unit test for folder logs

* fix: output container name

* fix: add auth info when get scan results (caicloud#1185)

* chore: add supported kubernetes versions (caicloud#1186)

* fix: low level bug of gitlab v3 version (caicloud#1188)

* chore: disable PVC watcher (caicloud#1191)

* [release-1.0] fix: skip ssl verify for gitlab (caicloud#1196)

* fix(kaide): skip ssl verify for gitlab

* fix(kaide): skip ssl verify for gitlab again

* fix(kaide): skip ssl verify for gitlab again and again
@caicloud-bot caicloud-bot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Dec 17, 2019
@caicloud-bot
Copy link
Collaborator

Thanks for your pull request. Before we can look at your pull request, you'll need to finish a Contributor License Agreement (CLA).

📝 Please follow instructions at https://github.com/caicloud/engineering/blob/master/guidelines/cla.md to complete the CLA.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the caicloud/tools repository. I understand the commands that are listed here.

@caicloud-bot caicloud-bot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. caicloud-cla: no Indicates the PR's author has not signed the Caicloud CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Dec 17, 2019
@tosone tosone changed the title [HAIER-67] chore(*): Rebase hr onto v0.9.8-beta [WIP] [HAIER-67] chore(*): Rebase hr onto v0.9.8-beta Dec 17, 2019
@caicloud-bot caicloud-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 17, 2019
@caicloud-bot caicloud-bot added caicloud-cla: yes Indicates the PR's author has not signed the Caicloud CLA. and removed caicloud-cla: no Indicates the PR's author has not signed the Caicloud CLA. labels Dec 17, 2019
@tosone tosone changed the title [WIP] [HAIER-67] chore(*): Rebase hr onto v0.9.8-beta [HAIER-67] chore(*): Rebase hr onto v0.9.8-beta Dec 17, 2019
@caicloud-bot caicloud-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 17, 2019
@tosone tosone changed the title [HAIER-67] chore(*): Rebase hr onto v0.9.8-beta chore(*): Rebase hr onto v0.9.8-beta Dec 17, 2019
@zhujian7
Copy link
Collaborator

/lgtm

@caicloud-bot caicloud-bot added the lgtm Indicates that a PR is ready to be merged. label Dec 17, 2019
@caicloud-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zhujian7

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

@caicloud-bot caicloud-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 17, 2019
@caicloud-bot caicloud-bot merged commit 024354e into caicloud:release-1.0-hr Dec 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. caicloud-cla: yes Indicates the PR's author has not signed the Caicloud CLA. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants