-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: switch from gitlab to github #723
Conversation
87d55d7
to
60a11a7
Compare
package.json
Outdated
@@ -23,5 +23,8 @@ | |||
"name": "cdtn-admin", | |||
"volta": { | |||
"node": "14.18.0" | |||
}, | |||
"engines": { | |||
"node": "v14.18.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sre sans ça la github action est en node 16. C'est la bonne approche ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ca permet de forcer la gh-action en 14 ? stylé !
si ca permet de ne pas le specifier aussi dans le workflow ca me parait top
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non, malheureusement. Ca permet de spécifier la version de node attendue par yarn. Pour la github workflow, on a dû utiliser l'action setup-nodes.
- uses: actions/setup-node@v2
with:
node-version: '14.18.0'
Cela me semble être la bonne approche, je ne vois pas comment préciser la version de node différement dans une action github. Et ça me semble logique car cela fait partie du test aussi.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ha ok, j'avais espéré que l'action exploite cette info dans le package.json 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nb: il y a possibilité d'utiliser un .nvmrc actions/setup-node#338
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bien vu ! :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥
.github/workflows/security.yml
Outdated
steps: | ||
- name: Register docker image for frontend | ||
uses: SocialGouv/actions/autodevops-build-register@local-cache-cdtn | ||
with: | ||
project: "cdtn-admin" | ||
imageName: cdtn-admin/cdtn-admin-frontend | ||
token: ${{ secrets.GITHUB_TOKEN }} | ||
dockerfile: "./targets/frontend/Dockerfile" | ||
dockercontext: "./targets/frontend/" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
on pourrait faire une matrix ici dans le futur comme ça avec trivy en bas, ça va bien correspondre
This reverts commit b1f02e4.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
fix #759