Skip to content

[CUBRIDQA-1435] Use ERROR_BACKUP and private-only SSH in core-dump JIRA comment - #774

Merged
junsklee merged 1 commit into
CUBRID:developfrom
junsklee:fix/analyze-failure-error-backup
Jul 15, 2026
Merged

[CUBRIDQA-1435] Use ERROR_BACKUP and private-only SSH in core-dump JIRA comment#774
junsklee merged 1 commit into
CUBRID:developfrom
junsklee:fix/analyze-failure-error-backup

Conversation

@junsklee

Copy link
Copy Markdown
Contributor

http://jira.cubrid.org/browse/CUBRIDQA-1435

코어 덤프 리포팅 시 analyze_failure.sh가 생성하는 JIRA 코멘트의 백업 경로와 Test Server 접속 정보를 실제 상태에 맞게 정정함. 코멘트 경로를 실제 백업 위치인 ~/ERROR_BACKUP으로 통일하고, Test Server에는 사설 IP 접속 명령만 노출하도록 변경함.

Changes

  • CTP/common/script/analyze_failure.shfix_backup_dir_namedo_not_delete_core에서 ERROR_BACKUP으로 변경하여 All Info/Core Location/DB-Volume Location/Error Log Location이 모두 실제 백업 루트(~/ERROR_BACKUP, CTP/shell/init_path/shell_utils.sh 기준)를 사용하도록 정정
  • login_info(-l gateway:port) 기반 게이트웨이 SSH 프리픽스 조합 로직을 제거하여 Test Serveruser@IPTEST_INFO_ENV의 사설 IP 접속 명령(ssh -p <port> <user>@<private_ip>)만 노출하도록 변경
  • -l 옵션 파싱 자체는 유지하여 기존 호출부 호환성 유지
  • build/timestamp/case명/core 파일명/Related Case 등 나머지 코멘트 포맷은 변경 없이 유지

…RA comment

- analyze_failure.sh: fix_backup_dir_name do_not_delete_core -> ERROR_BACKUP
  so All Info / Core Location / DB-Volume Location / Error Log Location match
  where shell_utils.sh actually backs up crash data (~/ERROR_BACKUP)
- Drop the -l/login_info gateway SSH prepend so Test Server shows only the
  private 'ssh -p <port> <user>@<private_ip>' from TEST_INFO_ENV
- Keep -l option parsing for backward compatibility with existing callers
@greptile-apps

greptile-apps Bot commented Jul 15, 2026

Copy link
Copy Markdown

Reviews (1): Last reviewed commit: "[CUBRIDQA-1435] Use ERROR_BACKUP and pri..." | Re-trigger Greptile

Comment thread CTP/common/script/analyze_failure.sh
@junsklee
junsklee requested review from kwonhoil and swi0110 July 15, 2026 06:30
@junsklee
junsklee merged commit 8622d3b into CUBRID:develop Jul 15, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants