07-12-2024 2:27 PM - edited 07-15-2024 11:16 AM
Hello 🙂
We have been using SAP CI/CD service for a while. Successfully, until recently, when we started getting fails every time. No change was made to the applications.
What setting could cause this ? Was there a recent update in the tool ?
This is the error we get at first :
Missing or empty 'version' attribute in package.json at /home/jenkins/agent/workspace/sij-room-cx_DEV
"sij-room-cx_DEV" is the name of the job.
And if we add a version attribute in the package.json :
Failed to create a UI5 project from module approuter at /home/jenkins/agent/workspace/sij-room-partnerexhidemo_DEV. Make sure the path is correct and a project configuration is present or supplied.
In attachment, the logs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi :-),
In this log the npmExecuteScripts worked out just fine. Probably because there was no build script executed that does not work.
Instead it fails in the deployment with the following error:
[2024-07-15T11:58:08.581Z] info cloudFoundryDeploy - -----> Nodejs Buildpack version 1.8.25
[2024-07-15T11:58:08.581Z] warn cloudFoundryDeploy - [31;1m**WARNING**[0m buildpack version changed from 1.8.24 to 1.8.25
[2024-07-15T11:58:08.581Z] info cloudFoundryDeploy - -----> Bootstrapping python
[2024-07-15T11:58:08.581Z] info cloudFoundryDeploy - -----> Installing python 3.11.9
[2024-07-15T11:58:08.581Z] info cloudFoundryDeploy - Copy [/tmp/buildpacks/badd377bdd2a2a0d/dependencies/21946bb90387e2dbfa40b0d6ca474060/python_3.11.9_linux_x64_cflinuxfs4_dea1f79d.tgz]
[2024-07-15T11:58:11.108Z] info cloudFoundryDeploy - BuildpackCompileFailed - App staging failed in the buildpack compile phase
[2024-07-15T11:58:11.108Z] info cloudFoundryDeploy - FAILED
For that the BTP CF colleagues would be the right address. Maybe open a Service Now ticket for component BC-CP-CF providing the cloudFoundryDeploy specific log messages.
Cheers!
Oliver
Thank you. After adding the version as follows, you can find the logs in attachment :
{
"name": "approuter",
"version": "1.0.0",
"dependencies": {
"@sap/approuter": "^16"
},
"scripts": {
"build": "ui5 build",
"start": "node node_modules/@sap/approuter/approuter.js"
},
"devDependencies": {
"@ui5/cli": "^3.8.0"
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
It was a good idea (and thank you, I will remember this possibility in the future), but unfortunately it did not fix the build in this case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The pipeline tries to run the npm run build command and fails there. The application does not seem to be set up correctly to run this. For example: Do you have a ui5.yaml? Maybe this can help: https://sap.github.io/ui5-tooling/v3/pages/GettingStarted/
We are not ui5 experts either, so it would probably be best to reach out to the UI5 community.
If you just want the pipeline to run then you may rename the "build" script in the package.json to something else, e.g. "ui5-build", and it will not run the build, but only do an npm install and continue.
Hope that helps,
Oliver
User | Count |
---|---|
70 | |
8 | |
8 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.