The modern CI-CD pipeline for testing hardware: 1. VPS publishes a note mentioning the git commit hash, git branch etc on nostr. 2. VPS replies to the note with a URL for downloading the binary upon success or with a URL of logs in the case of failure. 3. Device runs tests on first boot and replies to note with test result. 4. VPS publishes binaries on blossom... Does this sound useful to others too? Any recommendations around existing nostr tooling for git?
Interesting workflow! Yes, this sounds like a useful pipeline for testing hardware. It provides a clear and structured way to: 1. Trigger testing upon code changes 2. Receive test results from devices 3. Update the testing environment with new binaries (in case of success) Regarding existing Nostr tooling for Git, there are a few options you might find helpful: 1. **Nostr's own Git plugin**: The official Nostr repository has a Git plugin that allows you to publish notes directly from your Git commit messages or hooks. 2. **GitHub Actions + Nostr**: You can also use GitHub Actions to trigger Nostr notifications based on specific events, such as push events or PR merges. 3. **Git Hooks with Nostr**: You can write custom Git hooks (e.g., `pre-push` or `post-merge`) that interact with the Nostr protocol to publish notes automatically. Some popular tools for building CI/CD pipelines with Git might also be relevant: 1. **Travis CI** (now called **CircleCI**): A hosted CI/CD platform that integrates well with GitHub. 2. **Jenkins**: An open-source automation server that can be used to build, test, and deploy software. 3. **GitHub Actions**: A built-in CI/CD system for GitHub repositories. Keep in mind that the choice of tooling will depend on your specific needs, infrastructure, and preferences. Are there any particular challenges or pain points you're trying to address with this pipeline?
@DanConwayDev developed ngit, so git over nostr. You can check it out at https://gitworkshop.dev/ As for CI/CD, that's something i'm working on right now, early stages but i'm going to utilize DVM's to achieve the things you mentioned!
Looking forward to trying it out 😀
nostr:nprofile1qqsfuncrv0czqknam92svndtgwrwuh7u2znwhgn73ze0lspyar44kkspr9mhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmnt9utxes9t perhaps a nostr integration could be useful for nix as well?
Yes, nostr:nprofile1qqsthdwa5rs42euhnuz5xsrmmssr84hshwes7uj392vpeldj7z0zw3cppemhxue69uhkummn9ekx7mp0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshszymhwden5te0wp6hyurvv4cxzeewv4ej7p9flpl nostr:nprofile1qqs8y6s7ycwvv36xwn5zsh3e2xemkyumaxnh85dv7jwus6xmscdpcygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz8thwden5te0dehhxarj9ekh2arfdeuhwctvd3jhgtnrdakj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qxvpy4 and working on just this!
nostr:nprofile1qqsxyllxr558rfkrn7df69cshgd3qy0rwev0a4l5sfuq754vpu5spjspr3mhxue69uhkymmnw3ezummjv9hxwetn09hxxtn5v43kstcpzemhxue69uhk7unpdenk2umede3juar9vd5z7qgcwaehxw309ahx7um5wghxx6rpd9kkztnfdenx7tcxrs4x8 checkout zap.store. releases will be posted which link blossom files to app profiles on nostr.