[JENKINS-73837] Add support for archiving empty directories in TarArchiver/ZipArchiver

[pyatizbyantsevia]

See JENKINS-73837.
See JENKINS-49296.

Testing done

In my local environment the automated tests ZipArchiverTest.emptyDirectory and TarArchiverTest.emptyDirectory pass successfully (#9809).

Proposed changelog entries

• Add support for archiving empty directories in TarArchiver/ZipArchiver

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@basil

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[welcome]

Yay, your first pull request towards Jenkins core was created successfully! Thank you so much!

A contributor will provide feedback soon. Meanwhile, you can join the chats and community forums to connect with other Jenkins users, developers, and maintainers.

[mawinter69]

Propose to close this as this is a duplicate of #9836 which already covers all places and tests are working

[pyatizbyantsevia]

Propose to close this as this is a duplicate of #9836 which already covers all places and tests are working

really, thank you very much!

It's a shame I didn't see this sooner. Unfortunately, the corresponding pull requests do not appear in the corresponding Jira issues. other contributors may not know that the solution has already been provided (as happened to me)

[mawinter69]

I linked the PR in the Jira now.
I think the time you spent in trying to fix this problem is not wasted. You learned something about Jenkins internals and how testing works.
Maybe you find some other issue that you want to work on here
We could really need more people that help in maintaining core and plugins

[basil]

jenkinsci/stapler-maven-plugin#71 and jenkinsci/jellydoc-maven-plugin#64 are up for grabs, as well