The Cloud SDK pipeline uses the Cloud SDK continuous delivery server for building, checking, and deploying extension applications. Projects based on the SAP Cloud SDK archetype will automatically use this pipeline.
Apache License 2.0
65
stars
25
forks
source link
Config schema validation warnings not up to date #35
I see two warning messages in the Config schema validation warnings panel in Jenkins
Issue Description
The warnings displayed after the deployment seem to be outdated.
From the documentation of pipeline v32. the artifactDeployment.nexus now has 'mavenRepository' and 'npmRepository' instead of 'repository' property.
A similar situation is happening for lint.ui5BestPractices where we use the new flag instead of the deprecated one
The pipeline is not failing, but the schema validation warnings are faulty
Search for existing solution beforehand
I searched for a similar GitHub issue before and found none
I assume the config schema validation team is already working on keeping up with the pipeline releases, but I still tought it might be helpful to report this issue here.
Hello developers,
I see two warning messages in the Config schema validation warnings panel in Jenkins
Issue Description
The warnings displayed after the deployment seem to be outdated. From the documentation of pipeline v32. the artifactDeployment.nexus now has 'mavenRepository' and 'npmRepository' instead of 'repository' property.
A similar situation is happening for lint.ui5BestPractices where we use the new flag instead of the deprecated one
The pipeline is not failing, but the schema validation warnings are faulty
Search for existing solution beforehand
I searched for a similar GitHub issue before and found none
I checked the pipeline configuration docs and the general pipeline docs for an answer of my issue
Project type, for example:
I assume the config schema validation team is already working on keeping up with the pipeline releases, but I still tought it might be helpful to report this issue here.
Kind Regards, Manu