Repository navigation
jenkins: triggering build by comment fails #146
Description
Bot has started failing when a repository collaborator posts a comment trying to trigger Jenkins builds.
Seeing 403 responses from Jenkins:
14:29:58.319Z INFO bot: Emitting GitHub event (req_id=9a72f191-0b2d-43bd-bed5-da166834054e, pr=nodejs/citgm/#402, action=issue_comment.created)
14:29:58.499Z DEBUG bot: Triggering Jenkins build (req_id=9a72f191-0b2d-43bd-bed5-da166834054e, pr=nodejs/citgm/#402, action=issue_comment.created)
14:29:58.777Z ERROR bot: Error while triggering Jenkins build (req_id=9a72f191-0b2d-43bd-bed5-da166834054e, pr=nodejs/citgm/#402, action=issue_comment.created)
Error: Expected 201 from Jenkins, got 403I have verified both Jenkins tokens needed are correct: bot account API token and remote auth token for the citgm-continuous-integration-pipeline build. Those tokens has not changed since deploying this functionality and it was verified to work back then.
Not sure what could be the cause of sudden 403s. Has Jenkins been updated lately @nodejs/build?
Activity
gibfahn commentedon Jun 9, 2017
The earliest failure I can find is May 1 nodejs/citgm#402 (comment)), and the last good run I can find is
April 25 nodejs/citgm#400 (comment).
I'd assume the most likely culprit is a plugin update, presumably one of the Github ones
Current versions are (note that the number on the left is the installed version, the one on the right is the available update):
BridgeAR commentedon Apr 12, 2018
@gibfahn would you be so kind and check if the error persists? There were a couple of new releases for both of those plugins and I guess they were updated on our side as well, so we can retry with those updates and see if the issue got resolved in the meanwhile.
gibfahn commentedon Apr 12, 2018
nodejs/citgm#553 (comment)
Seems to be going well
BridgeAR commentedon Apr 12, 2018
🎉 that is awesome! So this issue seems fixed and we can move forward, right?
gibfahn commentedon Apr 12, 2018
Looks like it. I'll close this for now, we can continue the discussion in nodejs/build#1180