1. 61
  1.  

  2. 15

    I am really pleased with sourcehut. Neovim project needed CI for OpenBSD and FreeBSD. I was dreading the yak-shaving, but spent ~20 minutes and now we are set up: https://builds.sr.ht/~jmk/neovim

    1. 2

      Agreed. It was very simple :)

    2. 20

      Other than noting that this is basically just advertising for a new feature of sr.ht, it should probably be tagged release (since it’s a new feature) and not practices or virtualization (since it doesn’t really teach anything about virtualization).

      1. 5

        Sorry, I still don’t fully grok the tags on lobsters.

        1. 2

          No worries! Practice makes perfect. :)

      2. 6

        The number of times I’d wished I had this feature on Travis.

        Instead you just end up blindly pushing changes to the branch in the hope that it works :P

        1. 4
          1. 3

            Only on Travis-ci.com (the paid version), and not Travis-ci.org (the free version).

            1. 4

              sr.ht is also a paid service, right?

              1. 4

                It’s up to you whether to pay or run the exact same free software on your own infra.

                1. 2

                  Is it easy to run on your own? That’s kind of cool. I may pay them anyway but still run it myself.

                  1. 9

                    https://man.sr.ht/installation.md

                    Reach out to the mailing list if you run into trouble :)

                    1. 1

                      Wow, cool! Thanks :)

                  2. 1

                    You can also run travis-ci.org on your own infra (I currently do this) but there isn’t a lot of info about it.

                2. 3

                  The trick is that for public repos, you have to email support: https://docs.travis-ci.com/user/running-build-in-debug-mode/#enabling-debug-mode

                  1. 1

                    Weird… I guess that they’re trying to prevent wasted containers by adding manual process in the middle?

                    1. 2

                      It’s a security risk, especially for public repos.

                      1. 2

                        Eeeek, that’s rough. builds.sr.ht’s SSH access uses the SSH keys we already have on your account for git authentication et al.

                        1. 1

                          You get that from Github, too. But I also think it doesn’t help, because GH projects are liberal with adding people to orgs/repos and while they cam be grouped, there’s no way to assign structures roles. GH as an identity provider is mediocre at best.

                        2. 1

                          Like, in terms of things which they may do in the shells, DDoSing by creating too many, etc? They use your SSH key from GitHub to prevent others from SSHing in, right?

                          1. 4

                            They use your SSH key from GitHub to prevent others from SSHing in, right?

                            Not AFAIR. It gives a temporary login/password in the build log (which is public). And anyone who logs in can see the unencrypted secrets (e.g. API keys used for pushing to GitHub).

                            1. 1

                              oooooooh… yipes. Super dangerous. CircleCI uses SSH keys to improve on this.

                    2. 1

                      Aren’t they doing some funky reorganization to eliminate the split? I haven’t looked closely so I might be wrong.

                    3. 2

                      I guess I’ve just been too cheap to pay then ;)

                    4. 1

                      This feature is on Travis, but their new configuration API is so excruciatingly painful and lacking of reasonable documentation that it fails to help when it’s really needed.

                      1. 1

                        With Gitlab you can debug CI stages on your machine by starting a local Gitlab Runner.

                      2. 4

                        we keep the VM alive until you log out or until your normal build time limit has elapsed

                        Immediately on logout? There should be like a couple minute window after logout when you can log back in, because connections can drop, accidental Ctrl-D in the wrong window can happen, etc.

                        soon you’ll be just a few keystrokes away from an ARM or PowerPC shell, too

                        Let me guess, EC2 and IntegriCloud? :)

                        1. 16

                          Aye, I’ll improve upon this over time.

                          Regarding EC2 and IntegriCloud, no - sr.ht is run entirely on owned hardware in a private rack in a colocated datacenter. I don’t put your data in the hands of megacorps.

                          1. 2

                            I don’t put your data in the hands of megacorps.

                            I’m impressed.

                          2. 1

                            There should be like a couple minute window after logout when you can log back in, because connections can drop, accidental Ctrl-D in the wrong window can happen, etc.

                            Not just for this exact scenario, but you can use SSH Sockets for this purpose!

                            1. 1

                              I’ve had that enabled for years. Not sure how it would help when the TCP connection gets dropped because of network problems.

                            2. 1

                              accidental Ctrl-D in the wrong window can happen

                              Set IGNOREEOF and you can (mostly) avoid that problem.

                              1. 0

                                You can always rebuild there, yeah?

                              2. 2

                                Does anyone know how instashell is implemented? It’s dead cool to type instashell netbsd/latest and then have a useable NetBSD shell!

                                1. 1

                                  YAS!!! Thank you =^.^=