Skip to content

Merge to master - v0.9.0 #170

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

Merged
merged 4 commits into from
May 11, 2020
Merged

Merge to master - v0.9.0 #170

merged 4 commits into from
May 11, 2020

Conversation

sriram-mv
Copy link
Contributor

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

sriram-mv and others added 3 commits May 7, 2020 12:36
* feat: Makefile based builder for provided runtimes

Why is this change necessary?

* provided runtimes are runtimes that are custom built with own
bootstraps etc, and its hard to determine which language it actually is.
A generic makefile based builder gives the control back to the user on
how the project needs to be built.

How does it address the issue?

* Provide a way to build for provided runtimes, which does not exist
today.

* tests: add unit, functional and integration tests

Why is this change necessary?

* Tests to ensure that the makefile based approach for provided runtimes
works.

* fix: set environment variables in addition to current

Why is this change necessary?

* On Windows, certain env variables are required for functioning of
binaries within the Makefile

How does it address the issue?

* pass current environmental variables along with new ones over to the
subprocess runner.

What side effects does this change have?

* None

* fix: does this work on windows?

* chore: add pytest logging

* fix: inject artifacts dir based on shell

Why is this change necessary?

* on powershell on windows vs git bash on windows, paths are treated
differently.

How does it address the issue?

* Dynamically change path by looking up `sh`. If present, its unix path
else its windows paths.

What side effects does this change have?

* `sh` is the check which determines which path to use. If `sh` aint
present, this will end up in breaking the workflow.

* fix: only check for shells on windows

Why is this change necessary?

* on unix, its not necessary to transform the artifacts_dir path.

How does it address the issue?

* Do a check if we are windows, before attempting to look for binaries.

What side effects does this change have?

* None.

* fix: default for env is None, not {}

* fix: address comments

* fix: pass in the manifest file as argument for make

Why is this change necessary?

* Without this, the make manifest file is always assumed to be present
with the source_dir.

How does it address the issue?

* An explicitly passed in manifest file path is now not ignored.

What side effects does this change have?

* None.

* fix: address comments
* Allow hooks to be executed

NPM will not execute hooks when install is called as root. Since this is very common in scenarios where containers are involved, it makes sense to enable this flag

* Fix tests

Co-authored-by: Sriram Madapusi Vasudevan <[email protected]>
Why is this change necessary?

* New minor versions of python updated in the appveyor images.
@sriram-mv sriram-mv merged commit 30818b9 into master May 11, 2020
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.

3 participants