Closed deveaud-m closed 1 week ago
Please do not do this for the Siemens instance of SW360.
In the past the stakeholders considered any pro-active actions as a waste of valuable resources.
Nevertheless we will have a look at these endpoint(s).
Please do not do this for the Siemens instance of SW360.
- No one at Siemens uses the initial scan report.
- Just because some creates a release does not mean at all that a clearing is required.
In the past the stakeholders considered any pro-active actions as a waste of valuable resources.
Nevertheless we will have a look at these endpoint(s).
Thanks for the fast response.
I won't do it for the Siemens instance of SW360, no worries ;)
In our effort to improve automation between SW360 and the clearing backend, we are thinking about polling the new releases uploaded to SW360 in a nightly job and get the initial scan report back to SW360.
There is an endpoint called
/recentReleases
available in SW360 for this purpose: https://github.com/eclipse-sw360/sw360/blob/main/rest/resource-server/src/docs/asciidoc/releases.adoc#listing-recent-releases.Unfortunately it does not seem to be available via the Python wrapper yet.
Are there plans to integrate the endpoint in this library any time soon?
/cc @t-graf @gernot-h