New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: build on prem images #8393
Conversation
CC_SPEC_KSQL_BRANCH = "master" | ||
CCLOUD_DOCKER_REPO = 'confluentinc/cc-ksql' | ||
CCLOUD_DOCKER_HOTFIX_REPO = 'confluentinc/cc-ksql-hotfix' | ||
# need to update below automatically? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how is this handled in the existing scripts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently it gets updated manually ;/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think after we get 0.23 out, we can try to make this more automatically update
release_stabilization.py
Outdated
mvn_docker_args["docker.registry"] = DOCKER_UPSTREAM_REGISTRY | ||
mvn_docker_args["docker.test-registry"] = DOCKER_UPSTREAM_REGISTRY | ||
mvn_docker_args["docker.upstream-tag"] = CP_VERSION + "-latest" | ||
mvn_docker_args["skip.docker.build"] = "true" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we want to skip the docker build? I'm a bit confused. Looking at what we used to have:
mvn --batch-mode -Pjenkins clean package dependency:analyze site validate -U \
"${MAVEN_TEST_ARG}" \
"-Dspotbugs.skip" \
"-Dcheckstyle.skip" \
"-Ddocker.tag=${MAVEN_ARTIFACT_VERSION}" \
"-Ddocker.registry=${DOCKER_REGISTRY}" \
"-Ddocker.upstream-tag=${UPSTREAM_VERSION}-latest" \
"-Dskip.docker.build=false"
(copying source since it's not a public repo: https://github.com/confluentinc/ksqldb-release/blob/5ef81dff58c19350d0c7496a251a8f6c7a2945c0/build-packages.sh#L167-L174)
are those the right original lines that build the docker image?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nope you're right, this was just a mistake, good catch!
* fix: add more scripts * feat: build on prem images * fix: remove extra files for now * chore: swap boolean values, so we dont skip docker build
Description
Add scripts to stabilization callback in order to build on prem docker images for standalone ksqldb releases
Testing done
No behaviour change for ksqldb.
Reviewer checklist