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

feat: add artifact upload for coverage e2e #3120

Merged
merged 2 commits into from
Apr 27, 2023

Conversation

UtheMan
Copy link
Contributor

@UtheMan UtheMan commented Apr 27, 2023

What type of PR is this?

What this PR does / why we need it:
Ensures no regression for #2815
Which issue(s) this PR fixes:

Fixes #

Requirements:

Special notes for your reviewer:

Release note:

none

@UtheMan UtheMan temporarily deployed to test April 27, 2023 13:21 — with GitHub Actions Inactive
@coveralls
Copy link

Pull Request Test Coverage Report for Build 4820296174

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 61.885%

Totals Coverage Status
Change from base Build 4814378257: 0%
Covered Lines: 2528
Relevant Lines: 4085

💛 - Coveralls

uses: actions/upload-artifact@v3
with:
name: scenario-logs
path: e2e/scenario-logs
Copy link
Collaborator

@cameronmeissner cameronmeissner Apr 27, 2023

Choose a reason for hiding this comment

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

something I was meaning to do on the ADO side - can we upload a new bundle that doesn't include scenario-logs/*/vmssId.txt? those text files are only there such that we can ensure the ephemeral VMSS's are deleted (we have an 'ensure vmss deletion' step in the ADO pipeline that reads the ids from those text files and does 'az delete --ids ...' on them).

I'm also realizing now that we don't have the same sort of 'ensure vmss deletion' step on the GH action side...

we should really choose ADO/GH and pivot towards that

Copy link
Collaborator

@cameronmeissner cameronmeissner Apr 27, 2023

Choose a reason for hiding this comment

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

might also be worth leaving those text files lying around so we can use them to manually delete stuff via az cli if needed since we don't have that 'ensure vmss deletion' step on this side...

I'll leave it up to you

Copy link
Collaborator

Choose a reason for hiding this comment

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

(can also just go use the portal to delete... :D)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I will be looking into how i could combine ADO running e2e and gh action taking results of that and handling everything else

@UtheMan UtheMan temporarily deployed to test April 27, 2023 19:12 — with GitHub Actions Inactive
@UtheMan UtheMan merged commit ff77b76 into master Apr 27, 2023
@UtheMan UtheMan deleted the mikolaj/coverage-e2e-artifact-upload branch April 27, 2023 19:18
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.

4 participants