Skip to content
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

Merged
merged 17 commits into from
Mar 8, 2022
Merged

ci: switch from gitlab to github #723

merged 17 commits into from
Mar 8, 2022

Conversation

maxgfr
Copy link
Member

@maxgfr maxgfr commented Mar 3, 2022

fix #759

package.json Outdated
@@ -23,5 +23,8 @@
"name": "cdtn-admin",
"volta": {
"node": "14.18.0"
},
"engines": {
"node": "v14.18.0"
Copy link
Contributor

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 ?

Copy link
Member

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

Copy link
Contributor

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.

Copy link
Member

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 😅

Copy link
Member

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

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bien vu ! :)

@m-maillot m-maillot marked this pull request as ready for review March 7, 2022 14:50
Copy link
Member Author

@maxgfr maxgfr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥

Comment on lines 15 to 23
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/"
Copy link
Member Author

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

@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 8, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 2 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migration de cdtn-admin sur github
5 participants