Skip to content

Conversation

@nodece
Copy link
Member

@nodece nodece commented Jun 1, 2023

Motivation

This PR addresses the following issues:

  1. Fix the errors that arise when using custom docker.organization, because we use hard-coded images in the Dockerfile, which always pulls images from the apachepulsar organization.
  2. When publishing the older versions of Pulsar, the latest tag will be broken: [Bug] Latest docker image version should be 2.11.0 #19544.

Modifications

  • Use the dynamic base image in the Dockerfile by the ARG.
  • Use the Maven property to set the latest image, default to ${project.version} instead of latest, if you want to build the latest tag, please add -Dpulsar.latest.image.tag=latest to mvn command.
  • Using the mvn command to build and publish the images instead of the docker command.

Documentation

  • doc
  • doc-required
    • Update the release doc
  • doc-not-needed
  • doc-complete

@github-actions github-actions bot added the doc-required Your PR changes impact docs and you will update later. label Jun 1, 2023
@nodece
Copy link
Member Author

nodece commented Jun 1, 2023

/pulsarbot rerun-failure-checks

@nodece nodece force-pushed the improve-build-pulsar-images branch from a5d0a37 to c87fdd1 Compare June 2, 2023 02:39
@nodece nodece force-pushed the improve-build-pulsar-images branch from c87fdd1 to 7b8488f Compare June 2, 2023 03:56
@nodece nodece changed the title [fix][build] Improve the build of pulsar images [fix][build] Improve the build and publish of pulsar images Jun 2, 2023
@nodece nodece force-pushed the improve-build-pulsar-images branch from 7b8488f to 14f07cd Compare June 2, 2023 03:58

# Trino writes logs to this directory (at least during tests), so we need to give the process permission
# to create those log directories. This should be removed when Trino is removed.
RUN chmod g+w /pulsar/trino
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need this change?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverted.

Signed-off-by: Zixuan Liu <nodeces@gmail.com>
@nodece nodece force-pushed the improve-build-pulsar-images branch from 14f07cd to 6e89859 Compare June 2, 2023 04:04
@nodece nodece requested a review from jiazhai June 2, 2023 04:07
@jiazhai
Copy link
Member

jiazhai commented Jun 2, 2023

Thanks for the help. overall lgtm.
It looks like the build process is covered by the current CI process. Is the image publishing process also tested in the current CI?

@nodece
Copy link
Member Author

nodece commented Jun 2, 2023

Thanks for the help. overall lgtm. It looks like the build process is covered by the current CI process. Is the image publishing process also tested in the current CI?

Thank @jiazhai for your review, let me research the publishing process in the CI.

Signed-off-by: Zixuan Liu <nodeces@gmail.com>
@nodece
Copy link
Member Author

nodece commented Jun 2, 2023

Waiting for #20435 into master, and then rebase this PR.

@nodece nodece marked this pull request as draft June 2, 2023 08:43
@github-actions
Copy link

github-actions bot commented Jul 3, 2023

The pr had no activity for 30 days, mark with Stale label.

@github-actions github-actions bot added the Stale label Jul 3, 2023
@nodece
Copy link
Member Author

nodece commented Jul 3, 2023

#20435 has resolved these issues and now closes this PR.

@nodece nodece closed this Jul 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc-required Your PR changes impact docs and you will update later. Stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] pulsar-all 3.0.0 docker image contains Pulsar 2.11.0 [Bug] Latest docker image version should be 2.11.0

2 participants