Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
-
Jenkins builds are failing with the below errors for all the branches (in all environments)
Found LiferayCloudProject_v2_0_0
Visiting the following service directories:
BUILD each service in service root directory: /var/jenkins_home/workspace/
COPY service files to services build path: /var/jenkins_home/workspace/build
Successfully visited services
Stashed 0 file(s)
Archiving build/**
Archiving artifacts
‘build/**’ doesn’t match anything, but ‘**’ does. Perhaps that’s what you mean?
No artifacts found that match the file pattern "build/**". Configuration error?
Environment
- Liferay PaaS
Resolution
-
These errors or behaviors can be observed when the issue is caused by Jenkins being unable to pull the code from GitHub. One possible reason for this could be the expiration of the token
-
In this scenario, the token can be verified, and generate a new one if needed.
- If the token is valid and the error persist, please check the value of the rest of the infra enviroment variables, because some of them may be incorrect:
https://learn.liferay.com/w//liferay-cloud/platform-services/continuous-integration#environment-variables-reference
Additional Information
-
Setting Environment Variables
- For the
LCP_CI_SCM_TOKEN
value, use the personal access token created for your GitHub organization. For instructions on creating and accessing this token, see GitHub’s documentation.
- For the
Subscriber Exclusive Content
A Liferay Enterprise Subscription provides access to over 1,500 articles that include best practices, troubleshooting, and other valuable solutions. Sign in for full access.
Sign In