Skip to content

Conversation

wangyang0918
Copy link
Contributor

This PR tries to use the github actions for the CI. We have the following two jobs.

  • test_ci, this job will run all the unit tests and integration tests
  • e2e_ci, this job will run all the e2e tests
    • The new added e2e test test_kubernetes_application_ha.sh will start a Flink application with HA enabled. Wait for successful checkpoints and then kill the JobManager to verify the restoring.

@wangyang0918 wangyang0918 force-pushed the ci branch 3 times, most recently from 1070eca to 0bec47e Compare February 17, 2022 03:19
@wangyang0918
Copy link
Contributor Author

The CI has been successfully run my personal actions. It will take effect as soon as we merge this PR.

https://github.com/wangyang0918/flink-kubernetes-operator/actions/runs/1856555659

cc @gyfora

@gyfora
Copy link
Contributor

gyfora commented Feb 17, 2022

I will be away during the day today, I will take a look in the evening :)

@morhidi / @mbalassi please review if you have time,

Copy link
Contributor

@morhidi morhidi left a comment

Choose a reason for hiding this comment

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

nice work!

export SHELL=/bin/bash
export DOCKER_BUILDKIT=1
eval $(minikube -p minikube docker-env)
docker build -f ./Dockerfile -t flink-java-operator:ci-latest .
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: we could probably use the flink-kubernetes-operator name here too

docker images
- name: Start the operator
run: |
helm install flink-operator helm/flink-operator --set image.repository=flink-java-operator --set image.tag=ci-latest
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: we could probably use the flink-kubernetes-operator name here too

export SHELL=/bin/bash
export DOCKER_BUILDKIT=1
eval $(minikube -p minikube docker-env)
docker build -f ./Dockerfile -t flink-java-operator:ci-latest .
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: we could probably use the flink-kubernetes-operator name here too

docker images
- name: Start the operator
run: |
helm install flink-operator helm/flink-operator --set image.repository=flink-java-operator --set image.tag=ci-latest
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: we could probably use the flink-kubernetes-operator name here too

Copy link
Member

@tisonkun tisonkun left a comment

Choose a reason for hiding this comment

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

What about publishing the operator image to ghcr.io also? You can see this job for example.

@mbalassi
Copy link
Contributor

Hi @wangyang0918!

This looks great, I like the light-weight approach of using GitHub actions. As far as I understand this solution is also free as this is a public repo with moderate load (for the time being).
Since we are deviating from the Azure Pipelines approach of the Flink repo could you please add a short subsection on the CI to the Developer Guide?

@tisonkun I like publishing the docker images when the CI succeeds (with some rolling tagging policy) and obviously with stable tags on releases. I prefer having these images on DockerHub similarly to the flink repository there. I think this merits its own ticket and a bit of discussion on technical details, would you be so kind to open a ticket under FLINK-25963?

@tisonkun
Copy link
Member

@mbalassi thanks for your reply! Created at https://issues.apache.org/jira/browse/FLINK-26214. We can discuss in details there.

@wangyang0918
Copy link
Contributor Author

cc @mbalassi I have addressed the comments. Please have another look.

@asfgit asfgit closed this in e113440 Feb 17, 2022
@tweise
Copy link
Contributor

tweise commented Feb 17, 2022

@wangyang0918 thanks for contributing this! Will there any indicator on the PR itself whether the CI has passed or not?

@wangyang0918
Copy link
Contributor Author

@tweise Yes. But it could not work now because of apache security requirement. I have attached a PR #7 to fix this.

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.

6 participants