Ok this is pure wishlist stuff 
How about tracking the number of lines of output when a process like compiling finishes successfully, and using that to provide a better estimate of progress on the next compile?
Say a compile produces 2000 lines of output. Well, next time you’re compiling that step, you know that after 100 lines it’s done roughly 5% of the job…
Steve
Steve,
Interesting suggestion, but not something we really want to do. It shouldn’t be too important to know the progress of a particular action, especially when the external process doesn’t provide this information. I reckon that when you start your build, you should go and make a cup of coffee and relax a bit 
But seriously, the overall progress will be less important to you when you’ve got a stable build process that’s scheduled and you get an email (from the build) notifying you that it’s finished.
cheers,
.t8
Heh, I bet you’re right. This isn’t something that has any bearing on anything, and we’re only talking processes that take 1-2 minutes anyway. Consider it a frivolous request for some overengineering…
In other news, our build process is finally up and running. Very nice. Now to automate other things which weren’t considered “part of the build process”
Steve
Good news indeed