-
Notifications
You must be signed in to change notification settings - Fork 296
Skip generation of multiple config files along with build #1029
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
Skip generation of multiple config files along with build #1029
Conversation
abhishekkumams
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just one nit. Thanks for making the build faster.
seantleonard
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for updating this! Will definitely speed up the CI/CD runs, because generating config files for all databases was VERY time consuming. Sometimes took longer than the actual tests.
* accepting database type instead of bool * using database type in pipelines * changing leftover param to database type * updating docs * renaming param to generateConfigFile * renaming param to generateConfigFileForDbType
* accepting database type instead of bool * using database type in pipelines * changing leftover param to database type * updating docs * renaming param to generateConfigFile * renaming param to generateConfigFileForDbType
* Skip generation of multiple config files along with build (#1029) * accepting database type instead of bool * using database type in pipelines * changing leftover param to database type * updating docs * renaming param to generateConfigFile * renaming param to generateConfigFileForDbType * Adding support for nullable/varchar(*) result columns for stored-procedure (#1038) * adding support for nullable result columns * fix formatting * fixing nits * fixing test * Fix broken links (#1046) * Removing references to Cosmos Database in CLI/Engine/Pipelines/Config file names/Build commands. (#1045) * Removing references to Cosmos DatabaseType in CLI/Engine code * updating cosmos commands * updating scripts to use cosmosdb_nosql * updating pipeline files * updating cosmos -> cosmosdb_nosql * Renaming cosmos config file * fix pipeline issue * fix pipeline issue * fix pipeline issue * updating launch settings * debugging error * debugging error * debugging error * debugging error * Updating schema -> graphql-schema for cosmosdb_nosql * Reverting graphql-schema -> schema * Replacing references to cosmos with cosmosdb_nosql Co-authored-by: Ayush Agarwal <agarwalayush@microsoft.com> * Cli check for stored procedure Operations (#1041) * validation for stored-procedure permission in CLI * fix formatting * fixing tests * fix formatting * fix summary * fixing nits * fix formatting * fix formatting * addressing leftover comments from PR-1045 (#1052) * addressing leftover comments from PR-1045 * updating remaining references to cosmos in readme * updating cosmos getting started doc Co-authored-by: Ayush Agarwal <agarwalayush@microsoft.com> Co-authored-by: Shyam Sundar J <shyamsundarj@microsoft.com> Co-authored-by: Ayush Agarwal <34566234+ayush3797@users.noreply.github.com> Co-authored-by: Ayush Agarwal <agarwalayush@microsoft.com>
Why make this change?
dotnet build -p:generateConfigFiles=trueis used to generate the config files.MsSqlpipeline, it would be sufficient to generate only the config file for MsSql database type. Likewise, for other pipelines. Additionally, generating the config files for all database types leads to longer execution times for the pipeline runs.What is this change?
generateConfigFilesproperty is re-named togenerateConfigFileForDbType.generateConfigFileForDbTypeproperty accepts the database type (instead oftrue/false) and generates the config file for only that particular database.How was this tested?
Sample Request(s)