-
Notifications
You must be signed in to change notification settings - Fork 2
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
[TS] LPS-114817 #137
[TS] LPS-114817 #137
Conversation
…ve Media images associated with it
To conserve resources, the PR Tester does not automatically run for every pull. If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed. If your pull was never tested, comment "ci:test" to run the PR Tester for this pull. |
ci:test:sf |
ci:test:relevant |
✔️ ci:test:sf - 1 out of 1 jobs passed in 4 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-114817 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-acceptance-pullrequest(master)#5460 |
ci:forward |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
Skipping previously passed test suites: |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#89557 |
It seems that the trigger of updating FileEntry is still necessary but feel free to remove it if that was errant to begin with.
Also, I believe this is the solution but not entirely positive based on the AM framework. If you'd like it implemented in a different way or location please let me know.
Thanks.