Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion .github/workflows/presubmit.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,14 @@ jobs:
run: |
./gradlew :test --tests "com.jetbrains.dart.analysisServer.*"
working-directory: third_party

- name: Upload build artifacts
uses: actions/upload-artifact@v4
Copy link
Member

Choose a reason for hiding this comment

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

If this works, this is great! What does the CLI output look like, i.e. is it discoverable when it is written to these locations? Also, why not add this to to the Jobs?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I've been watching runs and it seems to work as intended! 🎉

(For example, this recent run: job/56077860294 generated artifacts here.)

What does the CLI output look like, i.e. is it discoverable when it is written to these locations?

If you squint at the picture above you can see a link is printed in the results. Here it is again:

image

Also, why not add this to to the Jobs?

You mean add a separate job? What would be the benefit?

(FWIW I did try actually try that initially but hit some snags and couldn't get the upload-artifact action to find the artifacts. I think I understand why after sleeping on it. If there's a good reason to get that working I can take another crack. Just let me know!)

if: always()
with:
name: build
path: |
**/build/reports/
**/build/test-results/
# Job 4: Verify Plugin
verify-plugin:
needs: build-plugin
Expand Down
Loading