-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3
-
Severity 3 - Minor
-
92
-
Summary:
For use cases such as waiting for "aws sso login" to be completed during the Bitbucket pipeline build process, the output is not displayed on the log results if the user moves out of the pipeline page.
Steps to reproduce:
- Define use cases such as "aws sso login" on your build
- Trigger the pipeline and stay on the pipeline page, you should be able to get link to authenticate the process and the build will proceed further followed by authentication process
- Trigger the build and move to a different page, after sometime navigate back to pipeline page to complete the authentication, the build is hung and the output log is not displayed for authentication
- Stop the build, logs will be displayed correctly
- Refresh the page, the log output for SSO login is cleared from the screen
Expected results:
The pipeline log should display build output irrespective of any of the above scenario
Actual results:
The logs results are not streamed consistently
Workaround:
Stay on the build page and complete the SSO authentication process
Another variant that works for us, and gives a bit cleaner output:
aws sso login --profile $AWS_PROFILE --no-browser --debug 2>&1 2> >(grep "Browser will not be automatically opened" -A 10)