I could merge this but I don't know who owns the current app in the jetbrain market.

cc @edwtjo @pSub could add the needed secret to this github repository?

Please ping on this PR again if none of the application owner is responding and we need to look into a different way to publish it on jetbrains.

I would like to help with this. However, currently I cannot figure out how to login in my jetbrains account. There seems to be something wrong. Whenever I login with my personal account (used to upload nix-idea), I am logged in with my professional account. I hope I can figure this out later.

@pSub should we write to plugins-admin@jetbrains.com about this? https://plugins.jetbrains.com/docs/marketplace/

Sorry for the delay, I was ill.

I've contacted the support and the access to the plugin has been restored for me. I've also create a permanent token. However, I cannot see the settings section for this repository to add the secret. @Mic92 Are you able to see the settings section?

@pSub I cannot either right now. I pinged some folks on IRC to give you more rights.

done, you are now both admins

@zimbatm Thank you!

@Mic92 @JojOatXGME I've added a permanent token as a secret (called JETBRAINS_TOKEN) to this repository. For all I care, go ahead and try it.

@Mic92 If you want to publish a new release, you can either push tag v0.3.0.0 (including the changes from the pull request) or merge the changes and run the workflow from the Actions section of GitHub. In both cases, you still need to bump the version number and run task patchChangelog manually afterwards.

I triggered a test run here: https://github.com/NixOS/nix-idea/runs/1346448422?check_suite_focus=true

Looks like the tooling still needs some fixes WARNING: Illegal reflective access by com.intellij.util.ReflectionUtil to field java.awt.event.InvocationEvent.runnable

Mhh... Task buildSearchableOptions logs an exception but does not fail. Task publishPlugin fails but the error message “Failed to upload plugin” is not very helpful. I guess I should add the --stacktrace option to get more insights if something similar happens in the future.

Any idea how I can test the task without actually uploading the plugin? Or do you think it is fine to publish the plugin under a different name just to test the publication system? I can reproduce the exception in buildSearchableOptions but the failure might be caused by something else.

@JojOatXGME I think it should be fine to debug publishing under a different name. Maybe make it clear from the description that this is not the official nix plugin and only for testing deployment.

You may also find this useful for testing: https://github.com/marketplace/actions/debugging-with-tmate

@Mic92 I cannot reproduce the issue. My run succeeded and I only made a few changes which I would not expect to fix the issue. Maybe it was a temporary failure of the network or JetBrains Marketplace?

In such case, you can either

• delete the GitHub release and restart the job, or
• upload the plugin manually to the marketplace.

In addition to adding the --stacktrace option, I could split the workflow into two workflows. That would allow to restart each workflow separately in the future. Then, you would be able to restart the publication to JetBrains without deleting the GitHub release. However, depending on the reproducibility of the build, both targets might then get a slightly different binary.

I guess it is also possible to build and save the binary in one workflow, and publish the build results in separate workflows. Anyway, I expect that such process would be more comlicated and I wanted to keep it simple at first. However, if you have any suggestions or references on how to address such problems, I'm happy to read them.

This is the restart: https://github.com/NixOS/nix-idea/runs/1360104046?check_suite_focus=true

Next try: https://github.com/NixOS/nix-idea/runs/1360140607?check_suite_focus=true

And another https://github.com/NixOS/nix-idea/runs/1360166286?check_suite_focus=true

This is the restart: https://github.com/NixOS/nix-idea/runs/1360104046?check_suite_focus=true

This build failed because the GitHub release already exists. Unfortunatly, the create-release action dosen't have an option to continue if the release does already exist. (EDIT: This is way you would need to delete the GitHub release for this to work. See my last comment.)

Next try: https://github.com/NixOS/nix-idea/runs/1360140607?check_suite_focus=true

This build failed because you did not change the version number. Therefore, the version number did not match the tag. You should run the patchChangelog task and change the version number in the gradle.properties. See this commit in my fork.

Beside that: My offer to split both steps into two seperate actions is still valid.

I get the same error again: https://github.com/NixOS/nix-idea/runs/1360166286?check_suite_focus=true#step:12:33

I cannot read the jetbrains secret so I cannot upload manually.

I get the same error again: https://github.com/NixOS/nix-idea/runs/1360166286?check_suite_focus=true#step:12:33

Ok. That is strange. I will create a new pull request which adds the --stacktrace option. Maybe that gives us more insights. Not sure what I could do otherwise. Shall I also split the workflow into two workflows as mentiond above?

I'm not sure if you want to keep the tags v0.3.0.1 and v0.3.0.2 and the GitHub release for 0.3.0.2. You may want to delete them. Not sure.

Maybe #17 fixes the problem. From what I understand in https://youtrack.jetbrains.com/issue/IDEA-234557 it should.

@pSub As far as I understand it, it should fix the exception in buildSearchableOptions. However, for me it doesn't look like this exception is actually causing the problem with the publication. At least my build had the same exception but the publication succeeded. Anyway, I might be wrong.

I created pull request #18 to add the --stacktrace option. It might help to identify the problem. I think you shold merge this change bevore trying it again. (EDIT: I mean if you want to try it again.) I'm currently also locking into spliting the workflow into two workflows.

I also cannot delete tags/releases btw.

With my changes from #19, you can trigger the publication without creating a new release. You could then try to publish the plugin again. Since we added the --stacktrace option, we might get some more informations about the failure.