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

update documentation for building on darwin #4796

Merged
merged 1 commit into from
Jan 17, 2020

Conversation

ivelichkovich
Copy link
Contributor

otherwise you can't build docker when working in a darwin environment, you get incompatible architectures from go build.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jan 16, 2020
@k8s-ci-robot
Copy link
Contributor

Welcome @ivelichkovich!

It looks like this is your first PR to kubernetes/dashboard 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/dashboard has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 16, 2020
@ivelichkovich
Copy link
Contributor Author

/assign @ianlewis

@codecov
Copy link

codecov bot commented Jan 16, 2020

Codecov Report

Merging #4796 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4796      +/-   ##
==========================================
- Coverage   45.43%   45.42%   -0.02%     
==========================================
  Files         214      214              
  Lines        9977     9977              
  Branches       94       94              
==========================================
- Hits         4533     4532       -1     
- Misses       5180     5181       +1     
  Partials      264      264
Impacted Files Coverage Δ
...p/backend/integration/metric/common/aggregation.go 89.09% <0%> (-1.82%) ⬇️

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 2deefb1...c8644cd. Read the comment docs.

@floreks
Copy link
Member

floreks commented Jan 16, 2020

Add that before npm run build block.

@ivelichkovich
Copy link
Contributor Author

Moved it, I can move it around more or change the text if needed

@@ -82,6 +82,12 @@ Open a browser and access the UI under `localhost:9090`. The following processes

In order to package everything into a ready-to-run Docker image, use the following task:
Copy link
Member

Choose a reason for hiding this comment

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

This part should be after export GOOS=linux

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ah yeah that makes more sense, updated

@ivelichkovich
Copy link
Contributor Author

while we're at it, is there a faster way to build this docker image? If I'm only changing the go for example, the frontend takes ages to build, is there a way I can just manually run go build and build a docker container from that?

@ivelichkovich
Copy link
Contributor Author

Also what should I do about the test coverage?

@floreks
Copy link
Member

floreks commented Jan 17, 2020

while we're at it, is there a faster way to build this docker image? If I'm only changing the go for example, the frontend takes ages to build, is there a way I can just manually run go build and build a docker container from that?

We do not have separate task for that, but you could manually compile backend binary, replace it in the dist directory and run only gulp docker-image:head:cross. I don't see why you would build the image on your own frequently. You develop on serve and then do the final test on prod. That should be enough most of the time.

Also what should I do about the test coverage?

Don't worry about that. Those calculations have a margin of error.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 17, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floreks, ivelichkovich

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 17, 2020
@k8s-ci-robot k8s-ci-robot merged commit 5000b90 into kubernetes:master Jan 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants