Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- After a user left our company (who had previously created a GitHub Personal Access Token (PAT), which we use to connect to our repository), Jenkins builds are no longer working as expected.
- In the logs, we see errors such as the following:
ERROR: {"message":"Not Found","documentation_url":"https://docs.github.com/rest/reference/repos#get-a-repository"}
java.io.FileNotFoundException: https://api.github.com/repos/[organization]/[repository]
...
Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"Not Found","documentation_url":"https://docs.github.com/rest/reference/repos#get-a-repository"}
Environment
- Liferay PaaS
Resolution
- Since a Github PAT grants access to all repositories within the organizations that the user who generated the token has access to, if that user is removed from the organization, all workflows in that organization's repositories using the token of that user will stop working as expected.
- To allow Jenkins to begin completing builds again via the webhook, replace the value within the CI service's LCP_CI_SCM_TOKEN environment variable with that of a currently valid token.
Additional Information
- Please note that if a PAT is being used, GitHub recommends (in this third-party documentation) that rather than using PATs from your own account, it is recommended to instead use one that was generated for a new account that is only granted access to the specific repositories that are needed for the workflow.
-
Related information can be found in the following articles:
- Configuring Your GitHub Repository
- Continuous Integration (and Jenkinsfile environment variable reference)