Skip to content

release-23.1: roachtest: clean up artifacts zipping code#112622

Merged
RaduBerinde merged 1 commit intocockroachdb:release-23.1from
RaduBerinde:backport23.1-111151
Oct 18, 2023
Merged

release-23.1: roachtest: clean up artifacts zipping code#112622
RaduBerinde merged 1 commit intocockroachdb:release-23.1from
RaduBerinde:backport23.1-111151

Conversation

@RaduBerinde
Copy link
Copy Markdown
Member

@RaduBerinde RaduBerinde commented Oct 18, 2023

Backport 1/1 commits from #111151.

/cc @cockroachdb/release

Release justification: test-only fix


This change rewrites the artifacts zipping code and adds a test.

Instead of doing the walk twice (with the second one restricted to top-level entries), we first list and filter the directory entries.

This will make it easy to reuse the code to first move go coverage artifacts to their own archive.

Epic: none
Release note: None

This change rewrites the artifacts zipping code and adds a test.

Instead of doing the walk twice (with the second one restricted to
top-level entries), we first list and filter the directory entries.

This will make it easy to reuse the code to first move go coverage
artifacts to their own archive.

Epic: none
Release note: None
@RaduBerinde RaduBerinde requested a review from a team as a code owner October 18, 2023 17:14
@RaduBerinde RaduBerinde requested review from DarrylWong and renatolabs and removed request for a team October 18, 2023 17:14
@blathers-crl
Copy link
Copy Markdown

blathers-crl Bot commented Oct 18, 2023

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@blathers-crl blathers-crl Bot added the backport Label PR's that are backports to older release branches label Oct 18, 2023
@cockroach-teamcity
Copy link
Copy Markdown
Member

This change is Reviewable

@RaduBerinde
Copy link
Copy Markdown
Member Author

TFTR!

@RaduBerinde RaduBerinde merged commit 97eced9 into cockroachdb:release-23.1 Oct 18, 2023
@RaduBerinde RaduBerinde deleted the backport23.1-111151 branch October 18, 2023 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Label PR's that are backports to older release branches v23.1.13

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants