feat: Building projects in source #5933
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Added event tracking for feature * Correctly pass event value and fix typing
* Resolve symlinks at root level and mount to container * Continue early instead of nesting in if statement * make format * Added integration test * make format * Use node project to test local deps and building in source * Removed old test data * Update test class name to reference testing symlinks * Use correct skip decorator from unittest * Changed mount mode to read only * Removed the removed mount parameter in tests * Remove kwarg in method call
* Added skeleton for build in source click option * Fix tests and renamed option * Added description and updated click option to include build * Disable build tests again until esbuild resolution fix * Revert template change * Make hook name option mutually exclusive with build in source * Fix integration test message assert
lucashuy
changed the title
* Added nodejs tests * make format * Enable retries * Run build test inside of a scratch directory * make format * Updated Makefile test to properly use scratch directory and moved source copy to setup * Changed copytree call to in house version * Removed redundant parent method calling * make format
* Bump npm version to 10.2.3 for linux testing * Upgrade node to 18.18.2
* Enable and use new test data folder paths * Added nodejs tests
* Resolve Layer symlinks before mounting container * Use .get instead of if else * Added integration tests * Unprivate static method and make format * Create paths using pathlib * Remove debug flag * Revert "Resolve Layer symlinks before mounting container" This reverts commit e557067. * Resolve links when creating tarfile for Docker build call * make format * Removed debug line * Updated arugment with optional typing
…ur (#6372) * Use develop version of Lambda Builders * Run nodejs local dep command in scratch directory and clean up aws-sam folder * Exclude the folder of the modified file from trigger sync flows on Linux * Revert "Use develop version of Lambda Builders" This reverts commit fde143e. * Add test validing ignoring Linux modified folder events * Fix test
mndeveci
reviewed
Dec 4, 2023
| NODE_VERSION: "14.17.6" | ||
| NODE_VERSION: "18.18.2" |
There was a problem hiding this comment.
Does this affect other tests? And do we need to change settings for windows as well?
There was a problem hiding this comment.
This shouldn't affect the other tests since as far as I remember, they don't rely on npm specific behaviour. As for changing this on Windows, I can double check if we needed to bump the version in Windows or not. This was changed since the tests on Linux were hardcoded to a lower npm version, but for Windows this is not set.
There was a problem hiding this comment.
The tests are passing on Windows (ref: https://ci.appveyor.com/project/AWSSAMCLI/aws-sam-cli-canary-windows-dev/builds/48658868/job/ql8agf8u9fgncwtj?fullLog=true), though it might be worth it to pin npm on Windows too.
mndeveci
approved these changes
Dec 4, 2023
mildaniel
approved these changes
Dec 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue(s) does this change fix?
Why is this change necessary?
How does it address the issue?
What side effects does this change have?
Mandatory Checklist
PRs will only be reviewed after checklist is complete
make prpassesmake update-reproducible-reqsif dependencies were changedBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.