type ods should support builds without deploymentmeans

[tbugfinder]

Is your feature request related to a problem? Please describe.
Code development projects should be of type ods (by definition).
Type ods and ods-service have additional (not described) expectations being e.g. deploymentmeans which relates to an Openshift DeploymentConfig.
There are "code development" projects which do not fit into this schema, e.g. AWS Lambda repositories which then might be used in other repositories for deployment.

Describe the solution you'd like
a) Better describe the types ods, ods-service, ff.
b) Add a parameter to skip the deploymentmeans in certain cases or move such dedicated project to a new type (ods-code).

Describe alternatives you've considered
a) As a workaround some "random" DeploymentConfig can be added which will be deployed. A ready to use helm chart would be helpful.

Additional context
N/A

[gerardcl]

what about changing the concept to "ReleaseMeans" so we can support other types of release means, for example, release mean based on helm or tailor (as per current deployment mean implementation/support concept) and then also ones like you suggest (e.g.: for libraries, binaries, code) or mobile app builds (e.g.: ios, android)?