4 ms·

Anything for artifacts perhaps? ;) We use external runners(not blacksmith) and had to work around this manually. https://github.com/actions/download-artifact/is

• aayushshah15 1y ago
  [cofounder of blacksmith here] This is on our radar! The primitives mentioned in this blog post are fairly general and allow us to support various types of artifact storage and caching protocols.
  • AOE9 1y ago
    Small blacksmith.sh user here, have yous any plans on reducing billing from per minute to something smaller like per second?
    • tsaifu 1y ago
      Hi! no plans for more resolution than per minute currently
      • AOE9 1y ago
        Shame, I am not sure how others use actions but I like really small granular ones to make it easy to see what's wrong at a glance. E.g. formatting checks per language per project in my monorepo etc. Each check is like 10 seconds and I have like 70+, so the per minute is biting me ATM.
        • tagraves 1y ago
          Come check out RWX :). We have per second billing but I think it won't even matter for your use case because most of those checks are going to take 0s on RWX. And our UI is optimized for showing you what is wrong at a glance without having to look at logs at all.
          • AOE9 1y ago
            Sorry not for me * Your per min billing is double blacksmith's * RWX is a proprietary format? vs blacksmith's one line change. * No fallback option, blacksmith goes down and I can revert back to GitHub temporarily.
• pbardea 1y ago
  Also might be worth checking out our sticky disks for your use-case: https://github.com/useblacksmith/stickydisk https://github.com/useblacksmith/stickydisk. It can be a good option for persisting artifacts across jobs - especially when they're larger