Skip to content

Commit c695b60

Browse files
authored
chore(cli-integ): explain how to stage in CodeArtifact (#27182)
---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
1 parent e01faff commit c695b60

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

packages/@aws-cdk-testing/cli-integ/README.md

+22
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,28 @@ To run a specific test, add `-t` and a substring of the test name. For example:
5656
bin/run-suite -a cli-integ-tests -t 'load old assemblies'
5757
```
5858

59+
### Running a test suite against binaries
60+
61+
Some test suites require package binaries stages in CodeArtifact repositories to run. This requires you to do a full build, then create a CodeArtifact repository in your own account, uploading the packages there, and then running the tests in a shell configured to have NPM, Pip, Maven etc look for those packages in CodeArtifact.
62+
63+
```shell
64+
# Build and pack all of CDK (will take ~an hour)
65+
$ ./build.sh
66+
$ ./pack.sh
67+
68+
# Use publib to upload to CodeArtifact
69+
$ npm install -g publib-ca
70+
$ publib-ca create
71+
$ publib-ca publish /path/to/dist
72+
73+
# Run the tests against those repositories (may need to substitute 0.0.0 w/ local number)
74+
$ source ~/.publib-ca/usage/activate.bash
75+
$ bin/run-suite --use-cli-release=0.0.0 <SUITE_NAME>
76+
77+
# Clean up
78+
$ publib-ca delete
79+
```
80+
5981
## Tools
6082

6183
There are a number of tools in the `bin/` directory. They are:

0 commit comments

Comments
 (0)