Enabled SPDX document validation for CI#878
Conversation
rnjudge
force-pushed
the
enable-spdx-validation
branch
8 times, most recently
from
1ccd214 to
be0d669
Compare
|
Added changes to
|
|
@nishakm this PR downloads a specific version of the spdx tooling for the CI tests. I don't see a way to always download the latest from bintray so I wonder if we just want to update the version in the CI tooling with each release? It seems there's a new SPDX tool every few months but this might slow down as the SPDX tool gets to be more stable. |
Can we build it from source? |
Good call. |
rnjudge
force-pushed
the
enable-spdx-validation
branch
6 times, most recently
from
9ceec3f to
17112fa
Compare
As development increases for Tern, it is getting harder to maintain the generation of valid SPDX documents for container images. This commit enables CI checks for the SPDX documents that Tern produces to make sure the documents are valid. Resolves tern-tools#713 Signed-off-by: Rose Judge <rjudge@vmware.com>
rnjudge
force-pushed
the
enable-spdx-validation
branch
from
17112fa to
a3aacb2
Compare
|
@nishakm The commit now builds from source.
|
2 participants
As development increases for Tern, it is getting harder to maintain the
generation of valid SPDX documents for container images. This commit
enables CI checks for the SPDX documents that Tern produces to make sure
the documents are valid.
Resolves #713
Signed-off-by: Rose Judge rjudge@vmware.com