Documentation: Mention dirMode and fileMode in reproducible archives section

[sdavids]

https://docs.gradle.org/current/userguide/working_with_files.html#sec:reproducible_archives

dirMode and fileMode should be mentioned in this section also:

Groovy:

tasks.withType(AbstractArchiveTask).configureEach {
    preserveFileTimestamps = false
    reproducibleFileOrder = true
    dirMode = 0755
    fileMode = 0644
}

Kotlin:

tasks.withType<AbstractArchiveTask>().configureEach {
  isPreserveFileTimestamps = false
  isReproducibleFileOrder = true
  dirMode = 493  // 0755
  fileMode = 420 // 0644
}

Different OSes, different umasks, and/or the version control system of choice might lead to non-reproducible builds if one do not set dirMode and fileMode explicitly.

[lptr]

Perhaps we should have a single switch to turn these all on at once? I mean, for most users the intention is to have reproducible archives, and the ability to configure each necessary aspect individually is just confusing and leads to unexpected results (=non-reproducible archives).

One way to achieve this would be to adopt https://github.com/Johni0702/gradle-reproducible-builds-plugin as a built-in feature.

[DPUkyle]

@lptr I'm a bit nervous about forcefully setting dirMode and fileMode for all archive tasks. For example, the order in which these CopySpecs are mutated isn't clear, and I worry that some other child CopySpec which attempts to set unique permissions for particular files/dirs would be clobbered by the "global" configuration.

[wolfs]

@DPUkyle if the {dir,file}Mode of the child copy spec is explicitly set, then it will take precedence over the setting in the root spec.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[wolfs]

We should update the documentation.

[lptr]

This somehow got into the "Epics" column!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[msgilligan]

We should update the documentation.

The documentation really needs to be updated. I (and another contributor) spent hours tracking this issue down after having too much confidence that Gradle was configured correctly given it's announced support for "reproducible builds" and me having read the documentation thoroughly.