...so that I can make sure the integration tests run and so that I update the integration tests to test the feature I am developing.
This will also ease the development process by automating the docker image generation and publication and having that done in github actions and pushed to docker hub from there, rather than doing that manually from a laptop.
📖 Additional Details
Integration tests are tests which requires the deployment of muultiple components, which source code is distributed in different github repositories. We want to aggregate them in application repositories (e.g. registry) which contains the code to deploy the different components from docker images and run the integration test.
I was thinking we could publish docker images with a suffix named after the branch, for example registry-api:1.2.0-SNAPSHOT.{name of the branch}
I don't know what would trigger the generation of the image and the deployment in an integration environment. Every commit/push sounds too often and not needed. In my previous job we were using a slack channel to command a robot which would deploy in the integration environment: deploy {env-name} {application} {branch}
I guess that could be managed in jenkins.
We can discuss the details more during one breakout meeting.
💪 Motivation
...so that I can make sure the integration tests run and so that I update the integration tests to test the feature I am developing.
This will also ease the development process by automating the docker image generation and publication and having that done in github actions and pushed to docker hub from there, rather than doing that manually from a laptop.
📖 Additional Details
Integration tests are tests which requires the deployment of muultiple components, which source code is distributed in different github repositories. We want to aggregate them in application repositories (e.g. registry) which contains the code to deploy the different components from docker images and run the integration test.
I was thinking we could publish docker images with a suffix named after the branch, for example registry-api:1.2.0-SNAPSHOT.{name of the branch}
I don't know what would trigger the generation of the image and the deployment in an integration environment. Every commit/push sounds too often and not needed. In my previous job we were using a slack channel to command a robot which would deploy in the integration environment:
deploy {env-name} {application} {branch}I guess that could be managed in jenkins.
We can discuss the details more during one breakout meeting.
⚖️ Acceptance Criteria
Given When I perform Then I expect
⚙️ Engineering Details