Skip to content

Conversation

@rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented Feb 19, 2025

We were cd'ing into the wrong directories.

The current mechanism builds jsii packages as part of the release step. This is good because it saves time (they all get built in parallel, and it's not part of the regular build), but it's bad because if one of them fails then it'll be hard to fix and retry.

Not sure what to make of this; currently we build jsii packages both at build time and at release time, which is extra silly. We'll have to pick one.


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

We were cd'ing into the wrong directories.
@rix0rrr rix0rrr requested a review from a team February 19, 2025 18:35
Signed-off-by: github-actions <[email protected]>
@aws-cdk-automation aws-cdk-automation added this pull request to the merge queue Feb 19, 2025
Merged via the queue into main with commit e8904b8 Feb 19, 2025
17 checks passed
@aws-cdk-automation aws-cdk-automation deleted the huijbers/fix-jsii-publishing branch February 19, 2025 21:31
kaizencc pushed a commit that referenced this pull request Feb 19, 2025
Follow up to #71.

In contrast to single package jsii publishing, our artifacts don't
contain the entire repo, but rather just the compilation result of a
specific package. This means that upon extraction, it needs to be placed
in the specific package directory instead of the root.

Currently release is failing with:

```console
Error: Expected to find .jsii file in /home/runner/work/aws-cdk-cli/aws-cdk-cli/.repo/packages/@aws-cdk/cli-lib-alpha, but no such file found
```

Which is expected because it operates on an uncompiled repo. Extraction
of the artifact to the correct location will overlay the repo with the
compiled code.

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license
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