-
Notifications
You must be signed in to change notification settings - Fork 225
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
Adding Skip Failures parameter for proceeding to the next script even if the previous script failed #239
Comments
Are these V scripts? Issue with this potential parameter will be that if you run the scripts like so:
And later edit V1.2.0__file.sql to pass it will not be executed since its not the max version in the change history table. In either case, parameter aside, a workaround solution can be to structure these scripts as tasks and then call them either manually or via an A script. Since tasks are executed asynchronously your calls should always be successful. |
Hi, thanks for the response. |
@sfc-gh-tmathew Thank you so much. Actually the 230 was the question while the 239 is the request for enhancement. Of course you can merge them. |
Dear @sfc-gh-tmathew , any news regarding this enhancement? |
@zroytman we are working on streamlining the release and testing process so that community contributions don't break existing functionality. This is not something that I am working on right now. FWIW, I worked around for a personal project like this in my devops pipeline using github actions. # Logic before schemachange block
set +e
echo "Preventing Schemachange's exit code from exiting the shell"
schemachange --config-folder myproject
RESULT=$?
if [ $RESULT -eq 0 ]; then
echo "Schemachange deployment completed successfully"
else
echo "Schemachange deployment failed. Proceeding to exception handling"
fi
set -e
# logic after schemachange block
if [ $RESULT -eq 0 ]; then
echo "Completed Successfully"
else
echo "Deployment failed"
exit 1 # do this if you want to control how you exit the pipeline. if you choose to exit 0 then the pipeline will see it as a success.
fi |
Dear community, any updates regarding this enhancement? Thanks a lot! |
Is your feature request related to a problem? Please describe.
I'm using SchemaChange as part of Azure DevOps Pipeline where I'm trying to deploy several sql scripts. In most of my cases the scripts have no dependencies between each other, but SchemaChange stops deployment on the first failure and doesn't proceed with the other scripts.
Describe the solution you'd like
Adding new parameter "Skip Failures" Y/N (True/False) will be helpful in that case, so the deployment process will deploy all the possible scripts without stopping after the first failure.
Thanks.
The text was updated successfully, but these errors were encountered: