Skip to content

ci: set ARTIFACTS_DIR to KOKORO_ARTIFACTS_DIR in build script for Kokoro attestation#407

Merged
AnshulPatni merged 1 commit into
GoogleCloudPlatform:mainfrom
AnshulPatni:fix-build-artifacts-dir
Jul 14, 2026
Merged

ci: set ARTIFACTS_DIR to KOKORO_ARTIFACTS_DIR in build script for Kokoro attestation#407
AnshulPatni merged 1 commit into
GoogleCloudPlatform:mainfrom
AnshulPatni:fix-build-artifacts-dir

Conversation

@AnshulPatni

Copy link
Copy Markdown
Contributor

During CI validation builds (.kokoro/build.sh), Kokoro attestation generation failed post-build:
failed precondition no artifacts found for fileset artifacts, which is required;AppErrorCode=9

While .kokoro/build.sh successfully copied built jars using find (BUILD SUCCESS), line 118 defined ARTIFACTS_DIR as ${REPO_DIR}/artifacts (/src/git/functions-framework-java/artifacts/). When .kokoro/build.cfg (artifact_globs: "artifacts/*") evaluated post-build relative to the container root $KOKORO_ARTIFACTS_DIR (/src/artifacts/*), no matching artifacts were found.

By setting ARTIFACTS_DIR="${KOKORO_ARTIFACTS_DIR}/artifacts", built jars and poms are staged directly into the container root where build.cfg fileset globs expect them, enabling complete post-build attestation generation.

…oro attestation

Change-Id: If5be41f46e95e030818956d786d14992b18a27d2
@AnshulPatni AnshulPatni merged commit 638157f into GoogleCloudPlatform:main Jul 14, 2026
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants