chore(ci): restore CI on push workflow

[mwangggg]

fixes: #277

[mwangggg]

not sure if I should update setup-java version to 21?

[andrewazores]

I was actually about to say the opposite. The published artifact builds with JDK 11 for wider compatibility:

cryostat-core/.github/workflows/maven-publish.yaml

Line 26 in 17a29a3

java-version: '11'

so I think this should either match and build with 11 only, or it should be an 11/17/21 matrix.

[mwangggg]

I'll leave it as 11 then

[github-actions]

ARCH	IMAGE
amd64	ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-amd64
arm64	ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-arm64

To run smoketest:

# amd64          
CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-amd64 sh smoketest.sh

# or arm64
CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-arm64 sh smoketest.sh

[github-actions]

ARCH	IMAGE
amd64	ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-amd64
arm64	ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-arm64

To run smoketest:

# amd64          
CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-amd64 sh smoketest.sh

# or arm64
CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-arm64 sh smoketest.sh

[github-actions]

ARCH	IMAGE
amd64	ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-amd64
arm64	ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-arm64

To run smoketest:

# amd64          
CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-amd64 sh smoketest.sh

# or arm64
CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-core:pr-279-bb9044bd32c31e86351dec7feca9f05aaba4d758-linux-arm64 sh smoketest.sh

[github-actions]

ARCH	IMAGE
amd64	ghcr.io/cryostatio/cryostat-core:pr-279-7ef1d805db9e3461c88934c9c130677d907e9bc2-linux-amd64
arm64	ghcr.io/cryostatio/cryostat-core:pr-279-7ef1d805db9e3461c88934c9c130677d907e9bc2-linux-arm64

To run smoketest:

# amd64          
CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-core:pr-279-7ef1d805db9e3461c88934c9c130677d907e9bc2-linux-amd64 sh smoketest.sh

# or arm64
CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-core:pr-279-7ef1d805db9e3461c88934c9c130677d907e9bc2-linux-arm64 sh smoketest.sh

[github-actions]

ARCH	IMAGE
amd64	ghcr.io/cryostatio/cryostat-core:pr-279-7ef1d805db9e3461c88934c9c130677d907e9bc2-linux-amd64
arm64	ghcr.io/cryostatio/cryostat-core:pr-279-7ef1d805db9e3461c88934c9c130677d907e9bc2-linux-arm64

To run smoketest:

# amd64          
CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-core:pr-279-7ef1d805db9e3461c88934c9c130677d907e9bc2-linux-amd64 sh smoketest.sh

# or arm64
CRYOSTAT_IMAGE=ghcr.io/cryostatio/cryostat-core:pr-279-7ef1d805db9e3461c88934c9c130677d907e9bc2-linux-arm64 sh smoketest.sh

[andrewazores]

I, uh, think that was a little excessive 😅

I suspect this is the problem:

cryostat-core/.github/workflows/ci.yaml

Line 4 in 17a29a3

group: ci-${{ github.run_id }}

The concurrency group is based on the run ID, but each time the PR is relabelled or a new commit is pushed I think that triggers a new run with a new ID, so many concurrent jobs can be running in the background on the same actual code if we're just relabelling the PR etc.

[andrewazores]

/build_test

[andrewazores]

Just to test that out ^

https://github.com/cryostatio/cryostat-core/actions/runs/6580357398

[andrewazores]

Nice, it passed - would be even nicer if the status got reported, either as a comment again like we already have elsewhere, or as a status check item