You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the approach currently being pursued in PR #38, log files generated by the application will simply disappear at the end of every Jenkins job run. Though some log history is available through the Jenkins UI (Console Output), this isn't accessible by support staff outside of the T&L developer group, or very neatly formatted.
@lsloan mentioned in a recent conversation that the original intention was to use the Canvas API to store log files on a Canvas course site, where they could be reviewed by support staff. If time and energy allow, we could explore this or other alternatives in the future.
The text was updated successfully, but these errors were encountered:
With the approach currently being pursued in PR #38, log files generated by the application will simply disappear at the end of every Jenkins job run. Though some log history is available through the Jenkins UI (Console Output), this isn't accessible by support staff outside of the T&L developer group, or very neatly formatted.
@lsloan mentioned in a recent conversation that the original intention was to use the Canvas API to store log files on a Canvas course site, where they could be reviewed by support staff. If time and energy allow, we could explore this or other alternatives in the future.
The text was updated successfully, but these errors were encountered: