-
Notifications
You must be signed in to change notification settings - Fork 65
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
Promotion Success / Process Failed #276
Comments
More people experienced this: sbt/sbt-ci-release#223 |
I think we need to confirm two things:
Unfortunately, I don't have any s01 sonatype account, so help for confirming these two points is appreciated. |
Got the same issue after upgrading sbt-ci-release But the relelease went fine: https://repo1.maven.org/maven2/com/carto/analyticstoolbox/core_2.12/0.0.3/ |
I had a chance to look into it a bit: 3.9.7...3.9.11 There is indeed a regression introduced in terms of #242, which is solved now by having a TlDR; the per project A tiny proof with the green release. I am not sure if that is a desired behavior. P.S. And theoretically that could be not directly #242, but smth around as well. |
@pomadchin Thanks. It seems @darkfrog26 also has this setting, but experiencing the same error occasionally:
To identify the cause, adding some info log to see which repository URLs are actually used around here would be the next step: sbt-sonatype/src/main/scala/xerial/sbt/Sonatype.scala Lines 416 to 418 in 245cf62
|
@xerial hmmm the only difference with my build is that I have it set both per project and globally ._.' what a tricky behavior to debug. |
It looks like the issue of configuration scopes. I guess depending on the context within sbt, extracting project settings via Project.extract(state) references unexpected projects.
An approach would be changing sonatypeXXX commands into an sbt task definition or finding a way to get a consistent reference to the root project when calling |
Probably I've found the cause:
This setting is not referencing
If s01.oss.sonatype.org is set in sonatypeCredentialHost, the url should be https://s01.oss.sonatype.org/service/local |
@xerial, awesome! When will this be released? |
* Use ThisBuild / sonatypeXXX settings within commands * reformat * cleanup * Cleanup * cleanup
Released sbt-sonatype 3.9.12 with a fix in #285. I'm not sure this will solve the problem, but let me know if you still experience the issue. |
@xerial thank you, this is great! I won't be able to check it immediately sadly 🤦 I have only one package that is shipped via the fresh sonatype repo. Until the next release than (will try to do it as soon as its possible to cut one). |
All of my open-source projects are now on s01, so I'll drop a message if I see this again. Thanks, @xerial! |
Hi, I appreciate all the effort to improve experience for publishing to s01 :) Unfortunately, the changes in #285 are not backwards compatible and will break all of our existing builds publishing to s01 using sbt-typelevel.
|
For the record, I have also experienced the problem originally reported in this issue (for example in typelevel/sbt-typelevel#84 (comment)). However, I have seen it on the legacy host (not s01) and every time it has happened the release has always completed successfully anyway. So IMHO I don't think this is related at all to the credential host. |
I am getting the same problem since I upgraded to 3.9.12:
Thanks |
We need to release a new version, which fixes this regression. Use sbt-sonatype 3.9.11 for a while. I'm a bit busy this week |
I still get the original error of this issue (error after promotion) with |
Released sbt-sonatype 3.9.13, which reverted #276. |
This issue is related to #309 |
Describe the bug
After I get the message "The promote stage is in progress", it starts showing:
Execution failed: [404: Not Found] Request failed: {"errors":[{"id":"*","msg":"No activity for repository: comoutr-1003"}]}. Retrying in 15.00 sec. - (SonatypeClient.scala:172)
Perpetually. It would appear as though the promotion was successful, but the plugin never finishes because it just keeps getting the "No activity" response.
How to reproduce the issue
It doesn't always happen, but it is frequently happening ever since I migrated to "https://s01.oss.sonatype.org/service/local"
Additional context
Just released 3.6.6 and it happened with it, but I believe it was successfully released.
The text was updated successfully, but these errors were encountered: