Skip to content
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

#13779: Decouple docker from maven #30

Merged
merged 13 commits into from
Nov 15, 2024
Merged

#13779: Decouple docker from maven #30

merged 13 commits into from
Nov 15, 2024

Conversation

ademarcqrtsl
Copy link
Contributor

Minimal changes to "Decouple docker from maven".

Tested locally and with the image added in dockerhub

steps to validate it works:

  1. open docker_run/docker-compose.yaml
  2. replace 0.0.0 by ademarcq-13779.239 at line 19
  3. run docker-compose up on in docker_run folder
  4. check url http://localhost:8080/PrometheusDbExporter/metrics, you should have metrics

@ademarcqrtsl ademarcqrtsl changed the title Ademarcq/13779 #13779: Decouple docker from maven Nov 6, 2024
@ademarcqrtsl ademarcqrtsl requested a review from igbanam November 6, 2024 15:30
Copy link
Contributor

@igbanam igbanam left a comment

Choose a reason for hiding this comment

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

We may not need an .env file.

What do you think?

@@ -0,0 +1 @@
PROJECT_VERSION=0.0.0
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like you're using this for sane defaults?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, it's used for defaults only.

docker_build/prometheus.db.exporter.docker Show resolved Hide resolved
@@ -16,7 +16,7 @@ services:
retries: 5

prometheusdbexporter:
image: simpledotorg/prometheusdbexporter:0.0.0
image: simpledotorg/prometheusdbexporter:ademarcq-13779.236
Copy link
Contributor

Choose a reason for hiding this comment

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

Does this mean we are fixing all subsequent runs to this version?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

thanks for spotting this.

yes, it should have stayed 0.0.0, I just wrongly committed a file after my local tests

Copy link
Contributor

@igbanam igbanam left a comment

Choose a reason for hiding this comment

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

…per our conversation above

Copy link
Contributor

@igbanam igbanam left a comment

Choose a reason for hiding this comment

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

LGTM

@ademarcqrtsl ademarcqrtsl merged commit b153434 into master Nov 15, 2024
1 check passed
@ademarcqrtsl ademarcqrtsl deleted the ademarcq/13779 branch November 21, 2024 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants