build(workflows): execute the CI via GitHub Actions #1144
Conversation
EtienneM
force-pushed
the
build/376/github_action_ci
branch
7 times, most recently
from
247e449 to
2c4e926
Compare
EtienneM
force-pushed
the
build/376/github_action_ci
branch
4 times, most recently
from
ff626ff to
9252255
Compare
![semgrep-code-scalingo[bot]](https://avatars.githubusercontent.com/u/4868969?s=60&v=4){kind=small}
EtienneM
force-pushed
the
build/376/github_action_ci
branch
17 times, most recently
from
da32292 to
a50f1bc
Compare
EtienneM
force-pushed
the
build/376/github_action_ci
branch
14 times, most recently
from
86b272a to
29ade66
Compare
EtienneM
force-pushed
the
build/376/github_action_ci
branch
5 times, most recently
from
95b6301 to
bde3d17
Compare
EtienneM
force-pushed
the
build/376/github_action_ci
branch
from
bde3d17 to
ee9b5aa
Compare
| jobs: | ||
| detect-modules: | ||
| name: Detect the Go modules declared in go-utils | ||
| runs-on: ubuntu-22.04 |
There was a problem hiding this comment.
question: do we want to try and run on 24.04?
There was a problem hiding this comment.
Yes we can. We never faced any issue with Go related to the OS hence I'm tempted to keep trusting Go and not test on both OS (22.04 and 24.04). WDYT?
There was a problem hiding this comment.
We could slightly move to 24.04, but it is fine as is. I am mostly wondering because it caused issues on codeship, so we might want to be "early than late".
There was a problem hiding this comment.
The issue we faced on CodeShip with Ubuntu 24.04 is that with this version, they stopped deploying a MongoDB. As our CI scripts supposed that MongoDB is installed, they all suddenly failed. So it's not really related to the new OS version but to a major change in their base image.
Fix #376
I want to test this for a few days on
master. If we eventually don't face any issue with this setup, I'll eventually remove CodeShip integration on this repository.CHANGELOG.md