Release pipeline and Integration test refactor#291
Conversation
Moved integration tests into more structured folders and updated imports Updated release pipeline to run individually grouped RP tests in concurrent tasks
|
Leaving this open as a draft currently - would like to get our next release out before we overhaul the release pipeline :) |
| ) | ||
| # Wait for RBAC to catch-up | ||
| sleep(20) | ||
| sleep(60) |
There was a problem hiding this comment.
This didn't seem to help the test_dt_twin_lifecycle_int tests, but I'm not sure if that's because it actually needs more time, or if the timing of RBAC isn't the issue here. The failing command executes successfully locally after the test fails, so my assumption was that the timing just needs to be tuned a bit more.
There was a problem hiding this comment.
Let's keep an eye on this, one potential cause I am thinking is a token caching issue. Looking into it a bit, interestingly enough, role-assignment propagation delays can take up to 30 minutes and for faster turn-around you can force a refresh by logging out and in again - official guidance.
|
Overall great improvements and refactoring's. |
Moved dev test environment setup into template Moved extension install and version detection into template Modified parameters / var / and adjusted pipelines to use new values and templates
25f7d1b to
7509e40
Compare
| ) | ||
|
|
||
| sleep(20) # Wait for service to catch-up | ||
| sleep(60) # Wait for service to catch-up |
There was a problem hiding this comment.
Another RBAC timer increase that did seem to help tests pass.
* Release pipeline and Integration test refactor * Moved integration tests into more structured folders and updated imports * Updated release pipeline to run individually grouped RP tests in concurrent tasks * Added correct unit test params to merge.yml * Path updates for credscan suppression * Moved dev test environment setup into template * Moved extension install and version detection into template * Modified parameters / var / and adjusted pipelines to use new values and templates
Moved integration tests into more structured folders and updated imports
Updated release pipeline to run individually grouped RP tests in concurrent tasks (which allows for re-runs of failed test files for specific RPs)
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Thank you for contributing to the IoT extension!
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
pytest <project root> -vv