-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix(uat): use CURRENT for classpath component in second deployments #398
Conversation
Unit Tests Coverage Report
Minimum allowed coverage is Generated by 🐒 cobertura-action against da7dabf |
@@ -223,7 +223,7 @@ Feature: GGMQ-1 | |||
} | |||
""" | |||
And I deploy the Greengrass deployment configuration | |||
Then the Greengrass deployment is COMPLETED on the device after 2 minutes | |||
Then the Greengrass deployment is COMPLETED on the device after 299 seconds |
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.
why?
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.
At first deployment we use 5 minutes timeout equals to 300 seconds. 299 used to easy distinguishing first from second with almost the same timeout. When run scenarios locally sometimes 2 minutes is not enough.
@MikeDombo I have added one more commit related to javadoc fixes, please take a look I seen you already approved |
Issue #, if available:
Use new "CURRENT" version feature of OTF in scenarios
Joined with javadoc comment updates
Description of changes:
Why is this change necessary:
Switch to new OTF "CURRENT" version feature
How was this change tested:
Automatically on Linux via github CI + CodeBuild.
Manually on Windows.
Any additional information or context required to review the change:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.