Sign and publish pipeline in Buildkite #1175
Conversation
mrodm
force-pushed
the
sign_publish_second_pipeline
branch
from
9ec6b1c to
aed1851
Compare
💚 Build Succeeded
Expand to view the summary
Build stats
🤖 GitHub commentsExpand to view the GitHub comments
To re-run your PR in the CI, just comment with:
|
| cleanup() { | ||
| echo "Deleting temporal files..." | ||
| cd ${WORKSPACE} | ||
| rm -rf tmp.elastic-package.* |
There was a problem hiding this comment.
Nit. Have a common base variable for the tmpdir folder pattern so we don't forget to update this if we change the template for mktemp?
| rm -rf tmp.elastic-package.* | |
| rm -rf ${TMP_FOLDER_TEMPLATE_BASE}.* |
|
|
||
| echo "Publishing package ${packageZip}" | ||
| publishPackage "${package}" | ||
| done |
There was a problem hiding this comment.
Will something like this pipeline work to publish packages from integrations repositories?
There was a problem hiding this comment.
Yes, something like this script would be the steps to be used/followed in integrations (iterating for each package defined) or other repositories like endpoint-package or apm-server.
Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
| SIGNING_PACKAGES_GCS_CREDENTIALS_PATH=kv/ci-shared/platform-ingest/signing_packages_gcs_artifacts_credentials | ||
| PACKAGE_UPLOADER_GCS_CREDENTIALS_PATH=kv/ci-shared/platform-ingest/package_storage_uploader |
There was a problem hiding this comment.
Moved to shared path and renamed variables
💚 Build Succeeded
cc @mrodm |
mrodm
changed the title
4 participants
This PR adds the missing steps to sign and publish the given test package:
pre-commandhook