Visitar URL original
Make `signing` plugin support the configuration cache · Issue #13470 · gradle/gradle · GitHub
Skip to content

Make signing plugin support the configuration cache #13470

Closed

Description

@eskatos

This issue is about making the signing core Gradle plugin support the configuration cache.

Upon completion, all configuration and tasks provided by the signing plugin are compatible with the configuration cache.

Activity

  1. 26 remaining items

  2. martinbonnin commented on Jan 17, 2023

    @martinbonnin
    Contributor

    I also like the feature of #16056 to use a Credential class as configuration instead.

    What does using a Credentialclass brings compared to useInMemoryPgpKeys? In both cases, Gradle would need some logic to not persist the keys and since most CIs use environment variables, I kind of like the simplicity of useInMemoryPgpKeys(System.getenv("KEY"), System.getenv("PASSWORD"))

  3. hfhbd commented on Jan 17, 2023

    @hfhbd
    Contributor

    Mostly a common expected variable name aligned with RepositoryCredentials and Sonatype Publishing Credentials:

    ORG_GRADLE_PROJECT_myMavenRepoUsername
    ORG_GRADLE_PROJECT_sonatypeUsername
    
    ORG_GRADLE_PROJECT_signingUsername // for example
    

    etc.
    And the option to implement your own credential class 🤷🏻‍♂️

    But more important is open question of the cache..

  4. martinbonnin commented on Jan 17, 2023

    @martinbonnin
    Contributor

    Gotcha.

    But more important is open question of the cache..

    Agreed 👍

  5. gabrielittner commented on Jan 17, 2023

    @gabrielittner

    @martinbonnin this sounded to me like when something is obtained through the credential API it wouldn't be persisted in the cache https://docs.gradle.org/7.6/userguide/configuration_cache.html#config_cache:requirements:safe_credentials

  6. moved this from Todo to In Progress in Use Gradle configuration cacheon Jan 22, 2023
  7. moved this from In Progress to Awaiting Upstream Release in Use Gradle configuration cacheon Jan 22, 2023
  8. moved this from Awaiting Upstream Release to Done in Use Gradle configuration cacheon Apr 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions