Skip to content

Conversation

@maitrayshah-cb
Copy link
Contributor

Switching gradle scanning to using lockfiles. Lockfiles will have to be present in the code itself. This allows for more consistent scanning while also reducing salus container size.

  • Single Project
allprojects {
    dependencyLocking {
        lockAllConfigurations()
    }
}

Generate lockfile: gradle dependencies --write-locks

  • Multi Project
allprojects {
    dependencyLocking {
        lockAllConfigurations()
    }

    task resolveAndLockAll {
        doFirst {
            assert gradle.startParameter.writeDependencyLocks
        }
        doLast {
            configurations.findAll {
                // Add any custom filtering on the configurations to be resolved
                it.canBeResolved
            }.each { it.resolve() }
        }
    }
}

Generate lockfile: gradle resolveAndLockAll --write-locks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant