Skip to content

Add ability to cache generated dependency.#7340

Merged
vburenin merged 3 commits intovmware:masterfrom
vburenin:cache-deps
Feb 20, 2018
Merged

Add ability to cache generated dependency.#7340
vburenin merged 3 commits intovmware:masterfrom
vburenin:cache-deps

Conversation

@vburenin
Copy link
Contributor

@vburenin vburenin commented Feb 19, 2018

This PR adds ability to cache discovered Go dependencies that are used by 'make' tool to build changed targets. So that, if you are not changing project structure and only working withing existing set of packages regeneration such dependencies is redundant and adds 7-30 seconds (depends on IO speed) each time you are trying to run 'make '.

With this PR you can cut 7-30 seconds for each 'make ' call. To make that possible just define an environment variable as the following:

export VIC_CACHE_DEPS=1

At some point if you add an additional package and need to regenerate dependencies, just run "make cleandeps", so next "make" run will regenerate all dependencies from scratch.

Fixes #7339

go list -f '{{join .Deps "\n"}}' github.com/vmware/vic/"$pkg" 2>/dev/null | \
xargs go list -f '{{if not .Standard}}{{.ImportPath}}{{end}}' 2>/dev/null | \
sed -e 's:github.com/vmware/vic/\(.*\)$:\1/*:'
if [ -n "$VIC_CACHE_DEPS" ]; then
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we note the export VIC_CACHE_DEPS=1 requirement somewhere in this file? It's only mentioned in the commit message, so having it noted here will help.

@gigawhitlocks
Copy link
Contributor

Could we get some docs? <3

@vburenin
Copy link
Contributor Author

vburenin commented Feb 20, 2018

@gigawhitlocks I think it is very important to have docs updates. As well as I am urging to move forward to Go1.10 that should significantly speed up components re-build time. 2-5 seconds instead of 20-45 seconds.

@gigawhitlocks
Copy link
Contributor

gigawhitlocks commented Feb 20, 2018

LGTM

I mostly just mean please copy the description of the feature that you put in the PR into, maybe README.md or something like that so that the rest of us don't forget the name of the flag we need to set and never get to take advantage of your feature!

Approved with PullApprove

@vburenin
Copy link
Contributor Author

@gigawhitlocks done

Copy link
Contributor

@mdharamadas1 mdharamadas1 left a comment

Choose a reason for hiding this comment

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

lgtm

@vburenin vburenin merged commit fd0337b into vmware:master Feb 20, 2018
sflxn pushed a commit that referenced this pull request Mar 1, 2018
* Dump dmesg if container rootfs blocks or fails mount (#7260)

This is to enable bridging of the guest side state with the virtual hardware if we
see issues such as disks not presenting on a pvscsi controller or a mount operation
hanging.

* updating priority definitions to include features (#7292)

* Change default fellows for gandalf (#7310)

* Avoid exposing test credentials in 12-01-Delete (#7306)

To avoid exposing test credentials, use the established `Run VIC
Machine Delete Command` keyword, which in turn calls a secret keyword.

This changes the behavior of the test slightly:
 - It no longer checks for the absence of "delete failed" in output.
 - It will wait up to 30 seconds for the deletion to succeed.
 - It will clean up cert files at the end of the deletion.

* Bug fix in API delete test: disable volume store cleanup (#7303)

* Remove volume store cleanup before re-installing VIC appliance using existing volume stores
* Cleanup dangling volume stores on test teardown

* Add logging for image upload (#7296)

* Reduce datastore searches during non-vSAN delete operations (#6951)

* Optimize portlayer volume cache rebuild on startup (#7267)

This commit modifies the portlayer volume cache's rebuildCache func to
only process the volumes from the volume store that is currently being
added to the cache. rebuildCache is invoked for every volume store
during portlayer startup.

Before this change, rebuildCache would process volumes from all volume
stores in the cache every time a volume store was added. This led to
unneeded extra computation which could slow down portlayer startup and
overwhelm NFS endpoints if NFS volume stores are being used.

Fixes #6991

* Added local ci testing target to makefile (#7170)

Make testing locally as friction-free as possible by

1. Adding a makefile target 'local-ci-test'
2. Using TARGET_VCH added in VIC 1.3 to use an existing VCH
3. Using a custom script that doesn't utilize drone so that if
   the test fails and craters, we can still access the logs
4. Parameters can come from env vars, arguments, or secrets file

Resolves #7162

* Added upload progress bar tracker for ISO images. (#7320)

* Added upload progress bar tracker for ISO images.

Removed concurrent upload since it doesn't make any significant performance imapact.
When I tried to measure performance differene with and without concurrent uppload,
the results were fluctuating in a wide range so no good measurement was possible.

* Document the design for the vic-machine API (#6702)

This document proposes a design for a comprehensive vic-machine API,
the implementation of which will be tracked by #6116.

Subsets of this API (tracked by #5721, #6123, and eventually others)
will be implemented incrementally, and the design will be revised as
those efforts progress to reflect changes to the long-term vision.

* Remove superfluous calls to Set Test VCH Name (#7304)

Several tests explicitly call the `Set Test VCH Name` keyword shortly
after calling `Set Test Environment Variables`.

This can lead to test failures when a VCH name collision occurs;
subsequent tests which re-use the VCH name fail because there may be
leftover certificates from the first VCH with that name.

`Set Test Environment Variables` itself calls `Set Test VCH Name` and
then cleans up old certificate directories. Therefore, the explicit
calls to `Set Test VCH Name` are both superfluous and problematic.

* Ensure that static ip worker is on the same nimbus pod as VC otherwise network connectivity not guaranteed (#7307)

* [skip ci] Add ROBO test plans (#7297)

This commit adds test plans for the ROBO support features in a new
directory (Group19-ROBO) under manual test cases. The existing ROBO-SKU
test has been moved into this directory. The test plans include tests
for the container limit feature, placement without DRS, the license/
feature checks and WAN connectivity.

Fixes #7294

* Add hosts to DVS within the test bed as well (#7326)

* Setup updated for Longevity Tests (#7298)

* Setup updated for Longevity Tests to run on 6.5U1

* [skip ci] Terminate gracefully to gather logs (#7331)

* Terminate gracefully to gather logs

* Remove extra whitespace

* Increase timeout to 70 minutes

* Increase ELM timeout to 70 minutes

* Add repo to slack message since we have multiple repos reporting now (#7334)

* Not sending user credentials with every request (#6382)

* Add concurrent testing tool to tests folder (#6534)

Adds a minimized test case for testing our core vSphere interactions at
varying degrees of concurrency. This is intended to simplify debugging
issues that are suspected to be platform problems, or API usage issues
that are conceptually divorced from the VIC engine product code.

* Refactor Install Harbor To Test Server keyword (#7335)

The secret tag on the `Install Harbor To Test Server` makes it difficult
to investigate failures when they occur.

Only one out of 30+ lines actually uses secret information.

Refactor the keyword to extract the secret information into its own
keyword, allowing the tag to be applied in a more focused way. This is
similar to the pattern used by keywords in `VCH-Util`.

* Add ability to cache generated dependency. (#7340)

* Add ability to cache generated dependency, so not much time wasted during the build process.
* Added documentation to reflect necessary steps to leverage such improvements.

* Ignore not-supported result from RetrieveUserGroups in VC 6.0 (#7328)

* Move build time directives from title to body of PR (#7060)

* Retry the harbor setup as well (#7336)

* Skip non vSphere managed datastores when granting perms (#7346)

* Fix volume leak on group 23 test (#7358)

* Fix github status automation filtering (#7344)

Adds filtering for the event source and consolidates remote API calls.
Details the specific builds and their status for quick reference.

* Drone 0.8 and HaaS updates (#7364)

* Add tether.debug in integration test log bundle (#7422)

* Update the gcs plugin (#7421)

* [skip ci] Suggest subnet/gateway to static ip worker

* Ensure that static ip worker is on the same nimbus pod as VC otherwise network connectivity not guaranteed (#7307)

* Refactored some proxy code to reuse with wolfpack

Refactored the system, volume, container, and stream swagger code
into proxy code.

1) Moved the errors.go from backends to a new folder to be accessed
by all folders outside of the backends folder.
2) Refactored Container proxy and moved from engine/backends to engine/proxy
3) Refactored Volume proxy and moved from engine/backends to engine/proxy
4) Refactored System proxy and moved from engine/backends to engine/proxy
5) Refactored Stream proxy and moved from engine/backends to engine/proxy
6) Adopted some common patterns in all the proxies
7) Moved common networking util calls to engine/networking
8) Fix up unit tests
9) Changed all "not yet implemented messages"
10) Updated robot scripts

More refactoring will be needed to make these proxy less dependent on
docker types and portlayer swagger types.

Helps resolves #7210 and #7232

* Add virtual-kubelet binary to VIC ISO (#7315)

* Start virtual-kubelet inside the VCH (#7369)

* Fix value of the PORTLAYER_ADDR environment variable (#7400)

* Use vic kubelet provider

* Made modifications for virtual kubelet

* Added admin log collection and fix env variable content (#7404)

* Added most-vkubelet target (#7418)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants