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

Ingester binaries & Docker #1086

Merged
merged 2 commits into from
Sep 28, 2018

Conversation

ledor473
Copy link
Member

Which problem is this PR solving?

Resolves #1031

Short description of the changes

This supersede #1033

Makefile Outdated
build-ingester:
CGO_ENABLED=0 installsuffix=cgo go build -o ./cmd/ingester/ingester-$(GOOS) $(BUILD_INFO) ./cmd/ingester/main.go

.PHONY: build-ingester-linux
Copy link
Member Author

Choose a reason for hiding this comment

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

This was added by @zoidbergwill but there's no build-collector-linux nor a build-agent-linux, so I see 2 options:

  1. I remove this and we recommend using GOOS=linux make build-ingester
  2. I add one for every binary

Copy link
Contributor

Choose a reason for hiding this comment

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

Ahhh, I see now, only the all in one has a -linux job. Recommending GOOS=linux make build-ingester would definitely be good enough. I thought I'd found some other ones that did the same, my bad.

Copy link
Member Author

@ledor473 ledor473 Sep 26, 2018

Choose a reason for hiding this comment

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

Hum I missed the all-in-one one! Not sure why we have a specific step for it

Copy link
Member

Choose a reason for hiding this comment

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

don't think we need build-ingester-linux. Not sure why all-in-one needs it either.

Copy link
Member Author

Choose a reason for hiding this comment

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

It's used by ./scripts/travis/build-all-in-one-image.sh, but I can add that cleanup to the PR

@ledor473
Copy link
Member Author

DCO complains about the commit from @zoidbergwill so I'm not sure how to handle that.

Expected "William Stewart [email protected]", but got "William Stewart [email protected]"

@zoidyzoidzoid
Copy link
Contributor

Whoops, those are both me. What's the easiest way to fix it? Could I rebase that commit and fix my sign-off / author e-mail?

@codecov
Copy link

codecov bot commented Sep 26, 2018

Codecov Report

Merging #1086 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master   #1086   +/-   ##
======================================
  Coverage     100%    100%           
======================================
  Files         140     140           
  Lines        6622    6622           
======================================
  Hits         6622    6622

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d73db1e...2ed6798. Read the comment docs.

@zoidyzoidzoid
Copy link
Contributor

@ledor473
Copy link
Member Author

Thanks @zoidbergwill 👍 I've rebase my change and DCO is ✅ now.

@yurishkuro
Copy link
Member

zoidbergwill

+1

@yurishkuro
Copy link
Member

futurama refs are 1st class citizen in this repo

Copy link
Member

@yurishkuro yurishkuro left a comment

Choose a reason for hiding this comment

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

don't know why the builds are failing, but the change lgtm

@davit-y davit-y mentioned this pull request Sep 27, 2018
9 tasks

FROM scratch

COPY --from=certs /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ca-certificates.crt
Copy link
Member

Choose a reason for hiding this comment

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

are certificates needed?

Copy link
Member

Choose a reason for hiding this comment

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

at this point prob not, but I assume it's feasible that people might use certs to auth to Kafka.

@pavolloffay
Copy link
Member

Thanks @zoidbergwill +1 I've rebase my change and DCO is white_check_mark now.

@ledor473 maybe forgot to push?

@ledor473
Copy link
Member Author

Seems like I forgot to sign my 2nd commit indeed. It's fixed now

@yurishkuro
Copy link
Member

should this be rebased or merge master in? 'cause there's a fix for Kafka tests in master.

zoidyzoidzoid and others added 2 commits September 27, 2018 13:44
Signed-off-by: William Stewart <[email protected]>
Signed-off-by: Louis-Etienne Dorval <[email protected]>
@ledor473
Copy link
Member Author

Rebased, squashed and confirmed that I've signed my commit 👍

@pavolloffay pavolloffay merged commit f441f1d into jaegertracing:master Sep 28, 2018
@yurishkuro
Copy link
Member

Awesome!

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.

4 participants