added github actions to build and release

[kbudde]

Hi,

I've added a github action to build and deploy as travis was doing it before.
You must add the following secrets to your repository:

• DOCKERHUB_USERNAME
• DOCKERHUB_TOKEN

#323

[davideicardi]

LGTM! Thank you very much!

Maybe we should delete .github/workflows/maven.yml ?

I don't have permission to setup github actions variables, I think we need @ekoutanov .

[kbudde]

The maven.yml will also run on PRs. Therefore I think it's better to keep it.

[mcs]

Feel free to do whatever you want with the maven.yml. I just added it to my former PR because there "just" was Travis CI which I could not use for server-side test execution.

[kbudde]

@ekoutanov I would really love to see a release without log4j issues.
Can you please set up the secrets?

[ekoutanov]

I'll try to get around to it.

[davideicardi]

@kbudde @ekoutanov @mcs
According to #260 Bintray is no longer available. Maybe we should use Github release only?

https://github.com/marketplace/actions/upload-files-to-a-github-release

[ekoutanov]

@kbudde @ekoutanov @mcs According to #260 Bintray is no longer available. Maybe we should use Github release only?

https://github.com/marketplace/actions/upload-files-to-a-github-release

yeah, Bintray's kaput. We can skip it if the binaries can be uploaded elsewhere.

[kbudde]

@davideicardi , @ekoutanov I fixed it and updated the description.

The github workflow will now create the github release and a tag(!) if the version in pom.xml does end on "-SNAPSHOT".
The github release has the kafdrop-VERSION.jar attached.
See here for an example: https://github.com/kbudde/kafdrop/releases/tag/3.28.0

@ekoutanov only the dockerhub token is needed anymore.
Bintray was removed. For github the default token is used.

I've also cleaned up the CI files.

Release workflow:

• Update pom.xml (remove -SNAPSHOT from version)
• Commit and push to master
• Update pom.xml (increment version + add suffix -SNAPSHOT again)
• Commit and push

Each commit on master will push container to dockerhub: obsidiandynamics/kafdrop:*version* (e.g. obsidiandynamics/kafdrop:3.28.0-SNAPSHOT, obsidiandynamics/kafdrop:3.28.0)
If the version is not a snapshot release, another image is pushed: obsidiandynamics/kafdrop:latest.
So latest will always point to last release.

[davideicardi]

Great work @kbudde ! Thank you!

[ekoutanov]

Added secrets

[davideicardi]

@kbudde The new action seems to work without problems!
I just released a new version 3.28.0.