Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Freeze releases structure #447

Closed
hryamzik opened this issue May 25, 2016 · 4 comments
Closed

Freeze releases structure #447

hryamzik opened this issue May 25, 2016 · 4 comments
Labels

Comments

@hryamzik
Copy link

Can I possibly ask you to stop moving files in releases archives? I've written some automation that takes linux 64 bit archive from the latest guthub release and extracts it to FS.

Recently node_exporter just contained the node_exporter binary, now it's the node_exporter-0.12.0.linux-amd64 directory.

@grobie
Copy link
Member

grobie commented May 25, 2016

The new standard is to always include a directory for all official prometheus components. All old release processes will be updated to adhere to that guideline.

@hryamzik
Copy link
Author

Thanks, and can I relay on linux-amd64 substring in linux 64 archives?

- name: get package url
  set_fact:
      prometheus_json: "{{ item }}"
  with_items: github_release.assets
  when: "'linux-amd64' in item.name"

@grobie
Copy link
Member

grobie commented May 25, 2016

Yes. The folder and tarball names have the format {software}-{version}.{os}-{arch}. The tarballs will always be gzip compressed and have the extension .tar.gz.

@hryamzik
Copy link
Author

Perfect, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants