News for hackers. Stuff that matters.
Re:Concourse CI by gabrielr on Monday July 17, 2017 @08:13AM (#14787752)
> Just trying to find logs is a pain, and getting the UI to show a full log output is basically impossible

Have you tried `fly watch`? It will stream logs from in-flight builds, or show the full output of completed ones.

Re:Concourse CI by mugsie on Monday July 17, 2017 @08:26AM (#14787826)
sure - I can use fly. if I got to the page, find the link to download the right version of fly, then remember the archine incantation to login, find a job, and find the logs.

Or - I can go to my Jenkins build page, and click "Show full log".

For me, I find the initial quick searching through logs much quicker in a browser.

And, I have found that on longer builds the web UIs log streaming can actually crash the browser.

Re:Concourse CI by jadeklerk on Monday July 17, 2017 @05:30PM (#14792433)
The arcane incantation to login? Seriously? It's literally fly login. You're being ridiculous.
Re:Concourse CI by mugsie on Monday July 17, 2017 @06:18PM (#14792719)
Well, to be clear, it's fly login --team-name internal --concourse-url https://<url> -k (I think)

Vs just going to the jenkins UI.

Re:Concourse CI by jadeklerk on Monday July 17, 2017 @10:16PM (#14793868)
It's fly login -t <my target>

You can save targets.

Also, if you want logs to appear somewhere you can pretty easily set up a after-fail job to ftp em somewhere.