publishToConfluence - Something went wrong #1369
Comments
|
@arutscheidt thanks again for the detailed report. Let me try to start answering the questions and helping you:
Those are Gradle specific logs. docToolchain heavily uses Gradle under the hood, which is a build tool like Maven. It internally caches a lot of stuff and also tasks. The logs occur if you re-run a task but literally nothing has changed meanwhile (e.g. a filecontent etc) You can safely be sure, that you use the current version that is also displayed when you execute a docToolchain command (in your case 3.2.2)
That tells you that you did already configure your crednetials correctly and you can authenticate against the target API. It does not verify any other config issue, eg. invalid spacekey Since this behaviour is not reproducable on my end and from what i can see at the stacktrace (the operation fails with the very first API call to confluence using the spacekey), i assume that here is the issue. Could you please verify that you configured the correct SpaceKey? Please mind here: SpaceKey is not necessarily the DisplayName of your Space! Eg. Given my Space is called "docToolchain" the acutal SpaceKey that i need to configure for docToolchain and the use with the API will be "docToolcha". You can get the infos right from the addressbar of your browser when navigating into your target space. If that is not helpful please let me know, in order to investigate further :) |
|
Hello Paco, thanks for the quick reply. I censored the groovy file and accidently saved it and don't know if I created the stackstreace before or after. Some questions:
|
|
Found it, there is a bug when the API config ends with "/". For the short term just change the config |
|
No problem, I am happy that I could help to improve the product :-) It works now. Thanks for the fast help. I am sure that I found a doubleslash somewhere in the logs and also tried the api without '/'. Maybe a typical problem like: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When executing the dtcw script, the build failes with no further explanation (just response 404).
To Reproduce
Steps to reproduce the behavior:
./dtcw publishToConfluence -PconfluenceUser='UserName-PconfluencePass=API-TokenStackTrace
Expected behavior
Upload my content to Confluence and
BUILD SUCCESSFUL
Screenshots
n/a
Configuration
Additional context
I downloaded the last version yesterday via
Invoke-WebRequest doctoolchain.org/dtcw.ps1 -Outfile dtcw.ps1However, in the log I found a hint, that publishToConfluence has an old version???
But maybe this is a configuration issue.
Verification successful
./dtcw verifyConfluenceApiAccessis successful with the given credentialsProject structure
content.adoc
00_document_history.adoc
groovy file (censored)
The text was updated successfully, but these errors were encountered: