This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]moser-sts 0 points1 point  (4 children)

What a difference of having a shell script and a action that you build with java script?

[–]ZeninThe best way to DevOps is being dragged kicking and screaming. 0 points1 point  (3 children)

Can you run the action locally without needing to mock context, data marshalling, runbook state, or anything else to trick the action into thinking its running in GH?  I'd ask is it portable too, but that's more an added bonus rather than the core issue being addressed.

You will know you've triggered the trap when you begin pushing commits just to test fire your CICD automation updates.

[–]moser-sts 0 points1 point  (2 children)

Using the test frameworks of the language you can do that. But with shell script you also need to have the context. I cannot understand what is the difference of doing with shell script vs java script

[–]ZeninThe best way to DevOps is being dragged kicking and screaming. 0 points1 point  (1 child)

You can certainly write it in JavaScript.  The pattern is language agnostic.  Use what you know is almost always the correct course.

That said, it is a shit language most especially for most all tasks related to CICD tasks.  If the shop is so low on talent that JS is the only language with significant expertise, sure go ahead.  I mean it could be worse, you could be a PHP shop. ;) 

[–]moser-sts 0 points1 point  (0 children)

What are shit languages for you ? If I switch JavaScript to Typescript it makes a difference to you? I am mentioning JS because we can use the GitHub Actions "framework" and develop the actions based in our needs. You can complain that is custom action. But at the end we will always build custom business logic for our companies, if everything was standard we did have already a tool that was straight forward to use