News for hackers. Stuff that matters.
Re:GitHub Actions limitations and gotchas by chad_oliver on Wednesday September 08, 2021 @03:36PM (#28461968)
The biggest limitation I'm hitting with Github Actions right now is that there's no real support for queueing jobs up. Github actions do support a 'concurrency group' primitive that will prevent two actions in the same concurrency group from running at the same time, but this only allows you to have one item executing and one item queued up. If you try to queue up another one, the first queued item will be cancelled.

In our case we've got some cypress tests that we want to run on a specific on-premise server every time we create a pull request. They take about 20 minutes to run, and we're creating a lot of pull requests, so you have to carefully check what github actions are executing before you create a pull request or push new changes to it. I'd love support for proper queues like what teamcity and other CI systems have.

Re:GitHub Actions limitations and gotchas by AltF4me on Wednesday September 08, 2021 @04:58PM (#28462969)
Turnstyle?

We've had similar issues with Terraform deployments.

https://github.com/softprops/turnstyle

Re:GitHub Actions limitations and gotchas by jhgb on Wednesday September 08, 2021 @04:31PM (#28462657)
> The biggest limitation I'm hitting with Github Actions right now is that there's no real support for queueing jobs up.

Maybe they need to reinvent JES and JCL. :)

Re:GitHub Actions limitations and gotchas by AltF4me on Wednesday September 08, 2021 @04:59PM (#28462986)
Turnstyle?

We've had similar issues with Terraform deployments.

https://github.com/softprops/turnstyle

Re:GitHub Actions limitations and gotchas by aidanr on Wednesday September 08, 2021 @04:58PM (#28462973)
Now that made me smile! Add in a dose of CA-7 and job's a goodun.