-
Notifications
You must be signed in to change notification settings - Fork 138
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The current logic to define if a build has logs or not is based on is_docker_step. This related logic is not always valid, since it is based on step type and step content, but there are many way to have a result that could be a docker start, one of them being to call another step. The main issue is that we don't always now if this other step is a docker step or not before runtime. Moreover the logic becamore more and more complex adding more conditions like commands, _run_, docker_params, ... Moreover, the log list is completed before the build start, meaning that if the build is killed before completion, some logs may be missing but will be listed. This is also an issue when trying to access logs before the correspondong step ran. This commit changes the logic by adding the log file to the list (and start log) when starting a docker, wich should give a more consistent result.
- Loading branch information
Showing
3 changed files
with
16 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters