<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>capableweb</author><text>CircleCI solved this so many years ago, allow users to SSH into the environment the build happens.&lt;p&gt;Workflow is something like:&lt;p&gt;- Guess together a random CI or CD workflow, this is just to kick off the process. You can also start with a empty config.&lt;p&gt;- Something fails, get SSH host+port to connect to&lt;p&gt;- Enter environment and manually do everything you want to be able to automatically do&lt;p&gt;- Execute `history` and copy output, trim it into something nicer and put in your config</text><parent_chain><item><author>IshKebab</author><text>&amp;gt; Congrats kid you&amp;#x27;re A Release Engineer now and your life is hell. Enjoy debugging basic typos on a remote machine with 20 minute latency because you sure can&amp;#x27;t run those Github CI bash-scripts-in-yaml files locally!&lt;p&gt;Yes! Why is this accepted??&lt;p&gt;Gitlab has a way of running CI locally (for Docker based builds anyway; who knows about Windows or Mac) but a) it doesn&amp;#x27;t support the same features at the &amp;quot;proper&amp;quot; one (even basic ones like the `default` key) and b) they deprecated it!&lt;p&gt;Ok in fairness they&amp;#x27;ve stated in a random comment that they won&amp;#x27;t remove it before providing an alternative.... But still, how is this not a core feature of all CI systems?</text></item></parent_chain></comment><story><title>Release engineering is exhausting so here&apos;s cargo-dist</title><url>https://blog.axo.dev/2023/02/cargo-dist</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>brundolf</author><text>What we need is a standard CI language&amp;#x2F;config format across vendors (stuffing a custom DSL inside YAML doesn&amp;#x27;t count)&lt;p&gt;That would allow for a tooling ecosystem of static checkers, offline runners, IDE integrations, etc etc, and would also cut down on the learning barrier every time you switch to a new company that uses a different vendor</text><parent_chain><item><author>IshKebab</author><text>&amp;gt; Congrats kid you&amp;#x27;re A Release Engineer now and your life is hell. Enjoy debugging basic typos on a remote machine with 20 minute latency because you sure can&amp;#x27;t run those Github CI bash-scripts-in-yaml files locally!&lt;p&gt;Yes! Why is this accepted??&lt;p&gt;Gitlab has a way of running CI locally (for Docker based builds anyway; who knows about Windows or Mac) but a) it doesn&amp;#x27;t support the same features at the &amp;quot;proper&amp;quot; one (even basic ones like the `default` key) and b) they deprecated it!&lt;p&gt;Ok in fairness they&amp;#x27;ve stated in a random comment that they won&amp;#x27;t remove it before providing an alternative.... But still, how is this not a core feature of all CI systems?</text></item></parent_chain></comment><story><title>Release engineering is exhausting so here&apos;s cargo-dist</title><url>https://blog.axo.dev/2023/02/cargo-dist</url></story>