[FOLIO-3222] Update all Jenkins Github authentication to use personal access token Created: 30/Jun/21  Updated: 12/Jul/21  Resolved: 12/Jul/21

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps Sprint 117, DevOps Sprint 118
Development Team: FOLIO DevOps

 Description   

Github is requiring personal access or OAuth tokens for all authenticated Git operations. The cutoff is "mid-2021". They are also implementing "brown outs" which are manifested temporary authentication failures when using username/password combinations. https://github.blog/2020-07-30-token-authentication-requirements-for-api-and-git-operations/

Update Jenkins/Github integration and all Jenkins pipelines to use tokens. Update existing tokens to take advantage of Github's latest token format, and enable two-factor authentication on the FOLIO Jenkins Github account.



 Comments   
Comment by John Malconian [ 30/Jun/21 ]
  • Generated new personal access token for the Jenkins github account.
  • Added new access token to Jenkins credential config.
  • Updated all pipeline scripts in folio-infrastructure that used old token or u/p to use new access token.
  • Updated any scripts in jenkins-pipeline-libs that used old token or u/p to to use new access token.
  • Updated build-platform-complete-snapshot and build-platform-core-snapshot pipelines to use to new access token.
  • Updated GH access token in general Jenkins configuration and github branch source plugin.
Comment by John Malconian [ 12/Jul/21 ]

Opted to update the Jenkins Github password instead of enabling 2-factor authentication which could be problematic to manage.

Generated at Thu Feb 08 23:26:31 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.