You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by GitBox <gi...@apache.org> on 2022/02/17 09:01:40 UTC

[GitHub] [flink-kubernetes-operator] mbalassi commented on pull request #4: Use github actions for flink-kubernetes-operator CI

mbalassi commented on pull request #4:
URL: https://github.com/apache/flink-kubernetes-operator/pull/4#issuecomment-1042717476


   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](https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration#about-billing-for-github-actions) 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](https://github.com/apache/flink-kubernetes-operator#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](https://hub.docker.com/r/apache/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](https://issues.apache.org/jira/browse/FLINK-25963)?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org