I sometimes have a similar issue with Travis CI, if I can&#x27;t use one of their built in integrations or something. A simple workaround is to just upload an artifact to S3 after a successful build. Then on another system scan the bucket with a cron or listen for an S3 event notification for further processing. You can put a lifecycle policy on the bucket so it cleans up after a while too.<p>It&#x27;s sort of annoying to have to add on another system to the pipeline, but I think it&#x27;s generally reasonable. Managing artifacts shouldn&#x27;t really be part of the CI system anyway, I feel it&#x27;s better to handle that stuff separately.