Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow custom publishing strategy #28

Closed
blindpirate opened this issue May 16, 2024 · 0 comments · Fixed by #29 or gradle/gradle#29170
Closed

Allow custom publishing strategy #28

blindpirate opened this issue May 16, 2024 · 0 comments · Fixed by #29 or gradle/gradle#29170
Assignees

Comments

@blindpirate
Copy link
Contributor

In current implementation, build scan is always publishIfAuthenticated, which means that if users want to customize the publishing strategy, it's impossible - because buildScan.publishing seems to be stacked instead overwriting each other.

We should allow users to customize their publishing. From: @bamboo :

I don't want to publish build scans for every build I run so I tried to write an init script using develocity.buildScan.publishing.onlyIf { ... } but that seemed to have no effect in the Gradle build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant