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

Export or publish nixpkgs revision #35

Closed
acowley opened this issue Jun 13, 2020 · 3 comments
Closed

Export or publish nixpkgs revision #35

acowley opened this issue Jun 13, 2020 · 3 comments

Comments

@acowley
Copy link

acowley commented Jun 13, 2020

I apologize if this is documented, but I couldn't find it.

We're trying to use GitHub actions with a cron schedule to provide a rolling release of nixos-rocm. We want a daily rebuild to pick up nixos-unstable advances, so we don't pin nixpkgs in our build. But then I'd like to report what revision of nixpkgs was used in the most recent build since I think we will bump into the free tier storage limits fairly quickly, meaning that we won't have many historical versions in the cache.

Is there an existing way of having a badge or something that lists the specific revision the action picked up with its channel setting?

@domenkozar
Copy link
Member

That's a good idea - https://github.com/cachix/cachix-action/issues/46

@acowley
Copy link
Author

acowley commented Jun 14, 2020

Ack, and I spent some time deciding which repo to open the issue with. The echo is great, and I should add that to my workflow. Do you know how to better surface that information for users? I thought of the badge thing, but really I just want something more visible than clicking through the main GitHub web UI. I’ll dig to see if the latest logs are accessible in some easy way.

@domenkozar
Copy link
Member

The action could put the version in the output, then you could use that to generate an image with something like https://github.com/marketplace/actions/bring-your-own-badge. That's the best I can think of :)

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

No branches or pull requests

2 participants