Open cesarmax22 opened 8 months ago
Please rerun the skipped tasks with --info
to find out the reason of being skipped.
I think I know the reason. My project had a version ending with -SNAPSHOT.
anyways, I'm not 100% sure, but I think it can be improved. When we run the whole release in 2 steps: 1- publishToSonatype + closeSonatypeRepo 2- findSonatypeRepo + releaseSonatype
I don't think it's necessary in 2 to check if project.version ends with -SNAPSHOT (and therefore skipping tasks); because we're not publishing anything; we're releasing what's already published, right?
not big deal but it may give you a headache to troubleshoot. I had to actually debug the plugin to find this out
regards
Yes, that might be a problem. findSonatypeRepo
has been added "recently" and the majority of people use approach where publishTo*
is used together with close/rerelease*
. However, you can override the default value:
just by settings useStaging
to true
, probably depending on your some custom property passed with -P
to force/override executing those tasks in the second run.
quick question
after running:
1- publishToSonatype + closeSonatypeRepo
in order for the developers to start testing, we need the actual sonatype repositories versions (or names) so to test against that. I am trying to come up with a way that developers do not have to manually log in to nexus so to determine what's the nexus repository so to add it to the test app.
do you have any idea to accomplish that?
we'll be running a pre-release.yaml workflow that will end up publishing and closing nexus repository through your plugin; so I was thinking that workflow might output the nexus repository/ies so the dev can see right straight from github CI what are the repos to be tested
does it make sense? I can't think of anything other than forking your plugin and printing on console?
I think it is quite specific to your workflow and I'm not convinced that adding it to the core plugin would be the best idea.
However, the close task keep the staging repository id in its properties. You could create your own task (even "inline task" in your build.gradle or as a separate plugin to share across your projects) which be orchestrated after the close task and read that value, doing with it whatever you want (e.g. sending a message to your IM). Would it work you?
Hi,
I'm trying to achieve the following. I want to have 2 CI workflows:
./gradlew clean publishReleasePublicationToSonatype closeSonatypeStagingRepository -Dorg.gradle.parallel=false --stacktrace
. This is so we can smoke test properly -> this works FINE. Staging repository is successfully created and closed in sonatype./gradlew findSonatypeStagingRepository releaseSonatypeStagingRepository
The problem in B, is that I'm getting:therefore is not being released to maven central.
Since A and B are different workflows, I am doing a checkout of the project on each of them. Just mentioning.
Here is B (release-workflow.yaml)