News for hackers. Stuff that matters.
Re:How to fuck up software releases by anon9001 on Monday October 14, 2019 @03:48AM (#21246026)
I can do every step on your list with any CI platform. I do something extremely similar to build apps for ios (macos), android (linux), and web (linux). I think it's so important that it's one of the first things I do on any project.

I wanted to give you an example, but it all seems so easy, I'm not sure where you're getting stuck.

Re:How to fuck up software releases by gdfasfklshg4 on Monday October 14, 2019 @05:37AM (#21246462)
Can you really do a legal review from a CI platform?
Re:How to fuck up software releases by wwright on Monday October 14, 2019 @06:52AM (#21246826)
If it can be automated, then obviously, yeah.

If not fully automated, many CI platforms allow you to pause the pipeline by requiring manual confirmation from an authorized user. I know Jenkins and CircleCI support this off the top of my head. You could have the CI perform any relevant searches or diffs, then display that to the user to get manual confirmation. It’s still not “perfect”, but it does allow you to reliably get someone to look at the data and say “yes” or “no.”

Re:How to fuck up software releases by anon9001 on Monday October 14, 2019 @11:41AM (#21249487)
Yeah, that's one approach. Another might be to commit some kind of `./legal/sign-off-v1.0.0` so you can see who did it, and so travis can know if it should deploy the build or not