in the case of remote servers that run your jobs it might be nice to have some sort of daemon process that monitors a set of specified log files and transfers them to the central octopusci server via some api. Then the central octopusci server could process those log files and correlate them with jobs. We should also include gems that can be used in Rails, etc to provide integration into the logging so that we can associate a section of log files with a job.
I haven't really thought this out but it would be awesome if I had a job that ran cucumber tests and some test failed and not only did the ci server provide me with access to the rails logs but it also helped me isolate where in the logs I should be looking based on job and maybe even feature/scenario/test depending on the framework and the logs
in the case of remote servers that run your jobs it might be nice to have some sort of daemon process that monitors a set of specified log files and transfers them to the central octopusci server via some api. Then the central octopusci server could process those log files and correlate them with jobs. We should also include gems that can be used in Rails, etc to provide integration into the logging so that we can associate a section of log files with a job.
I haven't really thought this out but it would be awesome if I had a job that ran cucumber tests and some test failed and not only did the ci server provide me with access to the rails logs but it also helped me isolate where in the logs I should be looking based on job and maybe even feature/scenario/test depending on the framework and the logs