Send console output in the comment

[benjamin-rtblw]

We configured Jenkins to keep the 50 last builds and sometimes, when a revision makes Jenkins crash, I have the following message on my revision :

Build is unstable

Link to build: https://jenkins.ourdomain.com/job/ourjob/1244/ See console output for more information: https://jenkins.ourdomain.com/job/ourjob/1244/console

But when I click on the link (the console for example), I’m redirected to a Jenkins build that has since been deleted. Is it possible (maybe with the checkbox “Add Custom Comment”) to tell Jenkins to post the console output on Phabricator revision?

Thanks Ben

[ascandella]

Great point, we actually have the same issue at Uber occasionally.

There are two ways to implement this, and either would be relatively simple, but the plugin is more or less in maintenance mode right now so I wouldn't have the bandwidth to implement myself.

We could either paste the full text as part of the comment (and make a checkbox option to enable this behavior) or post it as a Harbormaster artifact, like we currently do for the URL. I'm not sure what the UX would look like for the harbormaster artifact, but I know that it supports more than just URLs (for example, you could post a harbormaster artifact of a completed build JAR).

[aeonmani]

Started by user Saurav Kumar Running as SYSTEM Building in workspace /var/lib/jenkins/workspace/New_Node-Server The recommended git tool is: NONE using credential abe316b9-f2fe-423b-b5e2-9a34d840ccaf

git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/New_Node-Server/.git # timeout=10 Fetching changes from the remote Git repository git config remote.origin.url https://git.kent.co.in/a-pandey/poc_tuya_eh.git # timeout=10 Fetching upstream changes from https://git.kent.co.in/a-pandey/poc_tuya_eh.git git --version # timeout=10 git --version # 'git version 2.25.1' using GIT_ASKPASS to set credentials git fetch --tags --force --progress -- https://git.kent.co.in/a-pandey/poc_tuya_eh.git +refs/heads/:refs/remotes/origin/ # timeout=10 git rev-parse refs/remotes/origin/dev_0.0.1_notification^{commit} # timeout=10 Checking out Revision d98382c609cfff7b4d96b3d7e2496c330ade218e (refs/remotes/origin/dev_0.0.1_notification) git config core.sparsecheckout # timeout=10 git checkout -f d98382c609cfff7b4d96b3d7e2496c330ade218e # timeout=10 Commit message: "changed error handler" git rev-list --no-walk d98382c609cfff7b4d96b3d7e2496c330ade218e # timeout=10 [Checks API] No suitable checks publisher found. [New_Node-Server] $ /bin/sh -xe /tmp/jenkins16815865095137068261.sh

• tar -czvf new_node-server.tar.gz README.md apnsnotification config doc jest.config.js new_node-server.tar.gz package.json src test tsconfig.json tuyaEventNotification README.md apnsnotification/ apnsnotification/VoIP_Dev.crt.pem apnsnotification/VoIP_Dev.key.pem apnsnotification/apnsPushNotification.js config/ config/config.json doc/ doc/use.md jest.config.js new_node-server.tar.gz package.json src/ src/index.ts src/config.ts src/utils.ts test/ test/client.test.js test/const.js test/utils.test.js tsconfig.json tuyaEventNotification/ tuyaEventNotification/index.js tuyaEventNotification/Logger.js Archiving artifacts SSH: Connecting from host [jenkins] SSH: Connecting with configuration [New_Node-Server] ... SSH: EXEC: completed after 201 ms SSH: Disconnecting configuration [New_Node-Server] ... ERROR: Exception when publishing, exception message [Exec exit status not zero. Status [126]] Build step 'Send build artifacts over SSH' changed build result to UNSTABLE [Checks API] No suitable checks publisher found. Finished: UNSTABLE

plz tell me how to resolve this issue