Add template for running D2D on project build and source archive

[keshav-space]

Resolves: aboutcode-org/scancode.io#1774

[tdruez]

@keshav-space We need some documentation on how to use this.

[keshav-space]

@keshav-space We need some documentation on how to use this.

@tdruez added usage example in the README

[tdruez]

It would be nice to add a workflow that displays the usage of the new template on a small Python or Java.

[pombredanne]

@keshav-space gentle ping... what's your ETA?

[keshav-space]

@tdruez We now have an end-to-end working example for Python in docs.

[tdruez]

@keshav-space That's good but instead of putting this in the docs, it should be in the workflows and running as part of the check to ensure everything works on code changes.

Also, see https://github.com/aboutcode-org/scancode-action/blob/main/.github/workflows/map-deploy-to-develop.yml

[keshav-space]

@tdruez We now have a running workflow that does source-binary mapping on https://github.com/bastikr/boolean.py using D2D template.

[tdruez]

@keshav-space Just to understand, why building the binaries in the context of this workflow instead of using already existing builds from the source project?
What is the benefit of this new implementation compared to already existing https://github.com/aboutcode-org/scancode-action/blob/main/.github/workflows/map-deploy-to-develop.yml ?

[keshav-space]

@tdruez this would be used in cases where we don’t already have a release binary, but we want to run source binary mapping in a pull/merge request or manual trigger.