A violation against the OSS Rules of Play has been detected.

Rule ID: rl-license_file-1
Explanation: Does it have a license file? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-1
Explanation: Does README mention REUSE? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

On s4sdk-docker-neo-cli dockerfile, which is used as a default for Piper's neoDeploy step, the SDK version used is still 2.161.3, which is already deprecated in SAP's documentation for dev tools: https://tools.hana.ondemand.com/#cloud . I think it should be updated to Java EE 7 Web Profile TomEE 7, or at least to the last version 2.161.9.

There's even a warning about this when trying to deploy with piper:

We are using Jenkins pipeline with Project Piper for build and deploy to Cloud Foundry. About a week or so ago the deployment started to fail with org not found (see below). Nothing changed in our pipeline and manually logging in via CLI using the cf login command works fine (org can be targeted).

API endpoint:   https://api.cf.eu10.hana.ondemand.com (API version: 2.141.0)
User:           ****
No org or space targeted, use 'cf target -o ORG -s SPACE'
Organization 'XXXXXXXXXX' not found.
FAILED

Earlier today I modified the pipeline to use an older version of s4sdk/docker-cf-cli (v24 instead of latest) and the deployment started to work.

Something was changed between v24 and latest that broke the targeting of org/space during cf login.

Currrently, the cx-server-companion.sh and cx-server script seem to only support the configuration of an own docker registry via the server.cfg file for the jenkins container itself:

            if [ ! -z "${docker_registry}" ]; then
                image_name="${docker_registry}/${docker_image}"
            else
                image_name="${docker_image}"
            fi

However, when actually being forced to use your own repository, you are left with no other option than to:

• somehow transfer the companion docker image to your local cache
• and to disable the nexus cache via the server.cfg at the moment

Are there any plans to enhance the support for a corporate docker registry at the moment?

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-4
Explanation: Is it compliant with REUSE rules? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-3
Explanation: Is it registered in REUSE? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html