# Beats build artifact lifetimes **URL:** \ **Category:** Beats\ **Created:** [January 24, 2019, 2:36am UTC](https://discuss.elastic.co/t/beats-build-artifact-lifetimes/165520 "2019-01-24T02:36:47Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![hilt86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hilt86/32/20308_2.png) [@hilt86](https://discuss.elastic.co/u/hilt86)\ **Post date:** [January 24, 2019, 2:36am UTC](https://discuss.elastic.co/t/beats-build-artifact-lifetimes/165520/1 "2019-01-24T02:36:47Z")
Hi Folks, I am using the arm beats nightlies from [Jenkins / Google Cloud storage](https://beats-ci.elastic.co/job/elastic+beats+6.x+multijob-package-linux/gcsObjects/)for some docker containers and when I rebuilt one the other day the resource had moved. I am wondering if I need to copy the packages to a permanent location or whether the builds will hang around for a reasonable amount of time? Also Google storage doesn't allow curl or wget (which breaks Docker image building), for example if you have a url like [https://storage.cloud.google.com/beats-ci-artifacts/snapshots/packetbeat/packetbeat-oss-7.0.0-SNAPSHOT-armhfp.rpm.sha512](https://storage.cloud.google.com/beats-ci-artifacts/snapshots/packetbeat/packetbeat-oss-7.0.0-SNAPSHOT-armhfp.rpm.sha512) you need to update the host to [storage.googleapis.com](http://storage.googleapis.com), which is a real hassle.. Is there a reliable and programmatic way we can access these builds? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 21, 2019, 4:36am UTC](https://discuss.elastic.co/t/beats-build-artifact-lifetimes/165520/2 "2019-02-21T04:36:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.