Overview of currently processed files in concurrent migration

OttoDeploy
,
1

Could you please add to the top bar the files currently being processed? When I migrate our solutions using parallel migrations I have to scan the log to see what files are currently being processed and which ones are done.

Many thanks
Tobias

2

Hey Tobias,

The data structure doesn’t truly support this well unless we want to essentially parse the log lines to determine what is still running. That is error prone since those log message can and do sometimes change. I’ll add it to our list to look into. Thanks!

-Kyle

3

Thanks for looking into this. That would be a huge UI improvement though I get that it might lead to erroneously not showing something as finished.
But instead of parsing the log can you not just surveil the dmt processes? (and with “just” I meant a very complex process to accomplish this :sweat_smile:)

1 Like
4

I mean OttoFMS is managing those processes already and knows about them. The main issue is that the UI is using the developer API to get the data, so sending across the data about what is running at that very moment is much more difficult than it is to send along the existing log and details for the deployment that are in the database. You’re essentially looking at a slightly fancy log viewer for the deployment, not like an active process manager that knows all.

-Kyle

1 Like
5

So if this is just a log viewer but you have the data on Server could you not:
Add a predefined line to the log with a control char in the beginning like

#FILE XXX STARTED
.
.
.
.
#FILE XXX ENDED

and parse that out without displaying it in the log? If otto already knows about the state of each process that should be doable.

thanks for listening and I will now shut up :sweat_smile: