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

Fixed the issue for bulk-assessments using the --yes flag with bulk assessment tests #2276

Conversation

atharva-kurhade-yb
Copy link
Contributor

Describe the changes in this pull request

Added --yes flag to bulk migration test in functions.sh

Describe if there are any user-facing changes

How was this pull request tested?

Does your PR have changes that can cause upgrade issues?

Component Breaking changes?
MetaDB Yes/No
Name registry json Yes/No
Data File Descriptor Json Yes/No
Export Snapshot Status Json Yes/No
Import Data State Yes/No
Export Status Json Yes/No
Data .sql files of tables Yes/No
Export and import data queue Yes/No
Schema Dump Yes/No
AssessmentDB Yes/No
Sizing DB Yes/No
Migration Assessment Report Json Yes/No
Callhome Json Yes/No
YugabyteD Tables Yes/No
TargetDB Metadata Tables Yes/No

@CLAassistant
Copy link

CLAassistant commented Jan 29, 2025

CLA assistant check
All committers have signed the CLA.

@atharva-kurhade-yb atharva-kurhade-yb changed the title Fixed the issue for bulk-migrations using the --yes flag with bulk migration tests Fixed the issue for bulk-assessments using the --yes flag with bulk assessment tests Jan 29, 2025
@atharva-kurhade-yb
Copy link
Contributor Author

Started a Jenkins Pipeline to test Oracle Bulk Assessments
Link :- https://jenkins.dev.yugabyte.com/job/users/job/yb-voyager-testing/job/yb-voyager-testing-pipeline/4612/

Comment on lines 1740 to 1712
if utils.AskPrompt("No target-db-version has been specified.\nDo you want to continue with the latest stable YugabyteDB version:", ybversion.LatestStable.String()) {
targetDbVersion = ybversion.LatestStable
return nil
} else {
utils.ErrExit("Aborting..")
return nil
}
}

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you might need to rebase your branch with main.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have rebased the branch. Would this have affected the jenkins build or PR?

@atharva-kurhade-yb atharva-kurhade-yb force-pushed the atharva/target-db-version-prompt-for-analyze-schema-and-assess-migration branch from 5696b64 to 71a884a Compare January 30, 2025 07:12
@atharva-kurhade-yb atharva-kurhade-yb merged commit df4aeee into main Jan 30, 2025
67 checks passed
@atharva-kurhade-yb atharva-kurhade-yb deleted the atharva/target-db-version-prompt-for-analyze-schema-and-assess-migration branch January 30, 2025 09:09
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.

4 participants