Summary
Read the failing build's console output where you are already asking about it.
Trigger, status, history and console log are the four things anyone opens Jenkins for, and the queue tools cover the case where nothing is running because something ahead of it is wedged. It authenticates as your own user, so its reach is exactly your account's.
What it is
A Jenkins bridge covering job listing and configuration, build triggering with parameters, build history and status, console output, queue monitoring, and navigation through Jenkins folders.
What you get
- Jobs listed, their configuration read, and their status monitored
- Builds triggered with parameters, and running builds stopped
- Build history, and the detail behind a single build
- Console output for a build, which is where a failure is actually explained
- The Jenkins build queue, including builds that are stuck in it
- Folder navigation, for instances organised into folders
Requirements
Node.js and a local build with npm install and npm run build, plus your Jenkins URL, a username and an API token set in the environment. The token is generated from Manage Jenkins then your user's Configure page, and is the recommended credential rather than a password.