search

doy / rbw

unofficial bitwarden cli
https://git.tozt.net/rbw
Other
620 stars 83 forks source link

Feature Request: CICD #15

Closed jakeswenson closed 1 year ago

jakeswenson commented 4 years ago

I'd like to help add automated build and "deployment" support to rbw if there is interest in getting that contribution.

I'd like to suggest the following process:

  1. Project Maintainer @doy would initiate a new release using cargo release 1.1. this results in a new tagged version being created (1.0, 1.1, 1.2, etc.)
  2. Using GitHub actions a build for that tag is run. 2.1. This creates a GitHub release 2.2. Then a matrix build is run for every platform that needs to be supported (linux, mac, etc)
  3. Each build uploads its artifacts to the GitHub release in 2.1.

I have an example of this in place already for my otpcli tool that we could use as a starting point if that makes sense @doy?

doy commented 4 years ago

i would like to get ci of some sort set up for running tests, but i already have a release process that i'm happy with.

fugkco commented 3 years ago

@doy what's your current release process? Would you be opposed to uploading the binaries to GitHub releases? One thing that i don't like is that I have to build rbw if I want to upgrade it, I'd much prefer downloading a binary.

doy commented 3 years ago

i currently publish binary packages for arch linux and debian/ubuntu, as described at https://github.com/doy/rbw#installation . is there something else you would like?

onedr0p commented 2 years ago

Yes, it would be nice if you could post the binaries to this Github repo, or post the static binary somewhere. Not everyone on Linux uses the AUR or Debian. Thanks.

fugkco commented 2 years ago

Forgot about this. Just the binaries would be nice on GitHub, or elsewhere.

doy commented 2 years ago

the debian packages i publish at https://git.tozt.net/rbw/releases/deb/ are binary packages - it should be straightforward to extract the binaries from them (this is what i was doing to generate the rbw-bin aur package when it existed, for instance).

onedr0p commented 2 years ago

the debian packages i publish at https://git.tozt.net/rbw/releases/deb/ are binary packages - it should be straightforward to extract the binaries from them (this is what i was doing to generate the rbw-bin aur package when it existed, for instance).

To be fair it's also pretty straight forward to set up a GitHub workflow to attach debs, rpms and the static binary (and support different architectures!) to github releases. Why not solve the problem for everyone and learn something new in the process?

Github doesn't need to be the only place you support downloading the app but it's much easier than manually doing it every release on your personal git site. You have a mirror here, so you do see some benefit to GitHub already.