Closed rodrigonull closed 3 months ago
@ricardozanini @wmedvede Can you help us verify what could be causing the E2E tests failure?
@rodrigonull are the docker.io images published?
@rodrigonull are the docker.io images published?
yes, the images are published as you can see here: https://hub.docker.com/r/apache/incubator-kie-sonataflow-operator/tags https://hub.docker.com/r/apache/incubator-kie-sonataflow-builder/tags https://hub.docker.com/r/apache/incubator-kie-sonataflow-devmode/tags
Is this repo part of any of our automations? I'm afraid this can cause some unwanted interference with sonataflow-operator
currently on on kie-tools
during the 10.0.0 release.
Is this repo part of any of our automations? I'm afraid this can cause some unwanted interference with
sonataflow-operator
currently on onkie-tools
during the 10.0.0 release.
Yes, the nightly job is still running. I guess we need to disable it until we release 10? Or we can just disable image publishing. That is an option too.
Yeah, IDK, I think we shouldn't be publishing anything out of this repo before Apache KIE 10...
And after Apache KIE 10, we need to decide what to do...
After 10.x the image publishing must be done from this repo.
@rodrigonull can you force push to run the CI again?
@ricardozanini Not sure why. As far as I can tell, we never agreed on moving the kogito-swf-builder
and kogito-swf-devmode
images from kogito-images
to kogito-serverless-operator.
@tiagobento lol, yes I meant kogito-image
. I thought I was there.
@rodrigonull, have you rebased this branch? I'm asking because I recently opened a PR, and e2e works perfectly.
@ricardozanini Rebased. All green now :)
Fixes image names on CI after the migration to dockerhub and also fixes the script to bump the project version.