Add CI/CD and Tests about liveactionmap HOT 14 CLOSED

I'm glad to help writing a CI workflow for github actions and help for the deploy pipeline

from liveactionmap.

@GabrieleCalarota thanks for offering to help! With the docker container finally set up, we can finally start integrating a CI workflow.

from liveactionmap.

I'm writing a CI pipeline in this PR on my forked repo

GabrieleCalarota#2

It will need a lot of rework, as the project is not born along with linting

from liveactionmap.

As I see that the PR is merged is this Issue still valid or to be closed?

from liveactionmap.

It's still valid because CD pipeline and tests still need to be implemented.

from liveactionmap.

Ah, Sorry.

from liveactionmap.

Hey, So sadly I never worked with GitHub CI. However is there a chance to have a simple webhook trigger to have it auto-deploy on my docker host? @GabrieleCalarota Can you hop in discord so we can discuss the details?

from liveactionmap.

Hey, So sadly I never worked with GitHub CI. However is there a chance to have a simple webhook trigger to have it auto-deploy on my docker host? @GabrieleCalarota Can you hop in discord so we can discuss the details?

Sure, why don't we use GitHub discussions?

from liveactionmap.

They're not enabled here. And personally, at least discord feels more... I think easy would be a suitable word?

from liveactionmap.

If there is a chance to add

curl -X POST \
     --fail \
     -F token=GITLAB_TOKEN \
     -F ref=GITLAB_REF_NAME \
     https://gitlab.com/api/v4/projects/34155787/trigger/pipeline

to the CI after all tests are complete?

from liveactionmap.

If there is a chance to add

curl -X POST \
     --fail \
     -F token=GITLAB_TOKEN \
     -F ref=GITLAB_REF_NAME \
     https://gitlab.com/api/v4/projects/34155787/trigger/pipeline

to the CI after all tests are complete?

Yes, there should be a way or an action for doing normal POST or webhook triggers. But why don't we move the CD pipeline to github instead of having the deployment somewhere else where from the code?

Also is that the official deployment of the repo? @kinshukdua

from liveactionmap.

Yeah it is, we're discussing it over on discord.

from liveactionmap.

Ok fine, sorry didn't have time to download it yet

Anyway: https://github.com/marketplace/actions/trigger-gitlab-ci

I think this action would do the trick, will you set GITLAB_TOKEN and GITLAB_REF_NAME as repo secret?
For best practice, I would add also GITHUB_URL and PROJECT_ID as secrets

the code at the end would be :

- name: trigger Job
  uses: appleboy/gitlab-ci-action@master
  with:
    url: ${{ secrets.GITLAB_URL }}
    token: ${{ secrets.TOKEN }}
    project_id: ${{ secrets.PROJECT_ID }}
    ref: ${{ secrets.GITLAB_REF_NAME }}

from liveactionmap.

If you could take a look @GabrieleCalarota since I don't know how to make it run only after merge. Atm, it seems to run on merge requests as well,
And erm, It seams to have failed

from liveactionmap.