fix: Update release plugin config to use .set(...) for props and inject nexus secrets via props#3802
Conversation
…ct nexus creds via gradle props
|
Could you please clarify the reason for the change? |
build-logic/root-build/src/main/kotlin/build-logic.root-build.gradle.kts
Show resolved
Hide resolved
|
Hopefully to fix releasing to actually work: https://github.com/pgjdbc/pgjdbc/actions/runs/17837108128 Unless you think it's something else that's causing it. The error in that run is complaining that the username is not populated. |
|
@vlsi Are you going to fix the release workflow or have an alternative idea as to what's wrong? If so, let us know, otherwise going to proceed with this in a few minutes to try it out. |
|
Exactly the same code works for me in a different project: https://github.com/Netcracker/qubership-profiler-agent/blob/c71efd9d52f6d61ddc608d1a46ea9437fa04e3b8/build-logic/root-build/src/main/kotlin/build-logic.root-build.gradle.kts#L10 I don't see reasons to go for properties and so on. So I wonder why do you suggest the changes |
|
Note: you can debug release workflows in your fork repository, so you don't need to merge fixes just to test them. |
3 participants
@davecramer Eyeball this one and I guess let's try it out.