There are other files that can affect the correctness of the code rather
than the src files like the deployment yamls, Makefile etc.
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
This workflow will push up to 2 images with 4 tags, depending on
if they changed since the last image.
* query-service:<git sha>
* query-service:master
* frontend:<git sha>
* frontend:master
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
As of now, the 'e2e-k3s' workflow will require the 'ok-to-test' label in
order to get triggered.
In addition to that, on each change to the PR on the relevant files,
Github will remove the label from it and it will be required again.
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
* ci: adding 'e2e' GH workflows
The flow contains of multiple steps:
* build 'query-service' and 'frontend' images and push them to the image registry
* deploy a disposable k3s cluster
* deploy the app on the cluster
* set a tunnel to allow accessing the UI from the web browser
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
* ci: requiring the 'ok-to-test' label for running some workflows
As of now, the 'e2e' workflow will require the 'ok-to-test' label in
order to get triggered.
In addition to that, on each change to the PR, Github will remove the
label from it and it will be required again.
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
The flow contains of multiple steps:
* build 'query-service' and 'frontend' images and push them to the image registry
* deploy a disposable k3s cluster
* deploy the app on the cluster
* set a tunnel to allow accessing the UI from the web browser
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
query-service job is currently building flattener and flattener job is
currently building query-service.
This PR should fix that mix.
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
