Persistent tail

[raine]

Would it be difficult for tail to keep waiting for new builds instead of quitting?

[coryb]

Not quite sure exactly how that would work. It currently gets the latest job id then polls the job output until it is done. So for it to work like you want it would have to start polling the job details waiting for a new job number then start the polling again.

It seems do-able, but I would not make it the default behavior. I use things like: jenkins tail | grep something which would not work if the tail command would not end

So we could add a --persist option.

-Cory

[raine]

Good points.

I was also thinking there might a command called output that would do the job of getting the output of the latest or nth build. And then tail would be the command that tails indefinitely.

That said, I can see the value of having a command that does the both things as it is currently. Perhaps adding --persist or --forever flag is the best option.

[raine]

Inspired by this project and the requirement for persistent tail, I've been working on my own jenkins cli tool. It's here: raine/ez-jenkins