You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By now there's a workaround creating the tag manually and proceeding with the following release steps.
Fix the creation of that git tag.
The solution can be tested by removing the dependency of nebula tasks on the publication tasks here and by deleting the tags that might be created doing so manually.
The text was updated successfully, but these errors were encountered:
@athkalia , the issue seems to be with TC bot credentials leaking to the publication task from somewhere (ref). The publication is configured to use developer's access token, but it gets shadowed by the TC bot credentials. I think that the DevProd team is better equipped to figure out where those are configured in the TC project.
But I guess we can conduct the initial investigation and reach out to you if we find anything out. We rarely release this plugin, so I am not sure when we'll get to it.
I see. I would appreciate it if you did the initial investigation (maybe as part of the next time you release it). If no fix is identified, then the Dev Prod team can look at this as well as a last resort.
As reported on Slack by @pshevche, releasing a new version of
test-retry-gradle-plugin
fails to create the a git tag.By now there's a workaround creating the tag manually and proceeding with the following release steps.
Fix the creation of that git tag.
The solution can be tested by removing the dependency of
nebula
tasks on the publication tasks here and by deleting the tags that might be created doing so manually.The text was updated successfully, but these errors were encountered: