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

Digital Twin CI/CD workflow #33

Closed
allyoucanmap opened this issue Aug 30, 2024 · 7 comments · Fixed by #41
Closed

Digital Twin CI/CD workflow #33

allyoucanmap opened this issue Aug 30, 2024 · 7 comments · Fixed by #41
Assignees
Labels
DevOps This label marks this as a DevOps activity internal This mark worked required as internal work MS
Milestone

Comments

@allyoucanmap
Copy link
Contributor

allyoucanmap commented Aug 30, 2024

Implement deployment actions/jobs

  • Jenkins CI/CD is necessary to build the project and publish artifacts on geosolutions dockerhub (see the wiki for build and deployment instructions)
  • Proper github action should be provided to built the project and run unit test for each coming PR/commit
@allyoucanmap allyoucanmap added this to the v1.0.0 milestone Aug 30, 2024
@tdipisa tdipisa assigned randomorder and unassigned tdipisa Sep 2, 2024
@tdipisa tdipisa added the DevOps This label marks this as a DevOps activity label Sep 2, 2024
@randomorder randomorder added the estimate needed we need to do an estimate for this ticket label Sep 2, 2024
@randomorder
Copy link
Member

@allyoucanmap can you please link or add instructions on how to manually build the artifcat ?

@allyoucanmap
Copy link
Contributor Author

@randomorder The two artifact that we need to build are frontend and backend images:

frontend

docker compose -f docker-compose.yml build frontend

backend

docker compose -f docker-compose.yml build backend

Here we included deployment instructions.
The project has been created on top of this template so we could take a look also to the github actions for staging and production

Env file here

@randomorder
Copy link
Member

@tdipisa
For the time @allyoucanmap manually published the docker images on the docker hub. They are available [here](docker pull geosolutionsit/digital-twin-toolbox-backend) and [here](docker pull geosolutionsit/digital-twin-toolbox-frontend).

@randomorder randomorder assigned mo3rfan and unassigned randomorder Sep 5, 2024
@randomorder
Copy link
Member

@mo3rfan
can you take over and set up the github actions to automate the docker image builds?

@mo3rfan
Copy link
Contributor

mo3rfan commented Sep 5, 2024

So, build -> test -> deploy the two images on every commit on main branch.
and build -> test for every PR to main branch.

@randomorder Sure, I'll set this up. I estimate about 3 hours.

@tdipisa
Copy link
Member

tdipisa commented Sep 5, 2024

So, build -> test -> deploy the two images on every commit on main branch. and build -> test for every PR to main branch.

@randomorder Sure, I'll set this up. I estimate about 3 hours.

That's sounds good to me (FYI @allyoucanmap).

@randomorder randomorder added the MS label Sep 5, 2024
@tdipisa tdipisa added internal This mark worked required as internal work and removed estimate needed we need to do an estimate for this ticket labels Sep 9, 2024
@randomorder randomorder changed the title CI/CD workflow Digital Twin CI/CD workflow Sep 16, 2024
@tdipisa tdipisa linked a pull request Sep 30, 2024 that will close this issue
@randomorder
Copy link
Member

@mo3rfan please check the comments in the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevOps This label marks this as a DevOps activity internal This mark worked required as internal work MS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants