Skip to content
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

Explicitly archive affectedModuleDetector report folder #336

Merged
merged 1 commit into from
Jul 7, 2022

Conversation

luizgrp
Copy link
Member

@luizgrp luizgrp commented Jul 7, 2022

WHAT

Explicitly archive affectedModuleDetector report folder.

WHY

So the logs are archived in the CI artifact.

HOW

  • Change logFolder of affectedModuleDetector plugin to be inside reports folder;
  • Add */build/reports/affectedModuleDetector/* to build.yml as previous attempt with just changing logFolder did not result in having them archived in the generated artifact, even though I see the configuration to archive **/build/reports/*

Checklist 📋

  • [N/A] Add explicit visibility modifier and explicit return types for public declarations
  • [N/A] Run spotless check
  • Run tests
  • [N/A] Update metalava's signature text files

@luizgrp luizgrp changed the title Change logFolder of affectedModuleDetector to archived folder by CI Explicitly archive affectedModuleDetector report folder Jul 7, 2022
@luizgrp luizgrp merged commit 6519a00 into google:main Jul 7, 2022
@luizgrp luizgrp deleted the amd_report branch July 7, 2022 11:06
@luizgrp luizgrp self-assigned this Dec 8, 2022
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.

2 participants