-
Notifications
You must be signed in to change notification settings - Fork 183
404 on view configSubmit if there are more than one missing views #31
Comments
After some more fiddling it seems this is rather random... I deleted all the views in the nested view, ran the sync job again and it worked. After that I deleted them AGAIN and it failed like this at the last view it had to create. Very. Confusing. |
This is the stacktrace what I get: getting project names from http://localhost:8080/jenkins/api/json FAILURE: Build failed with an exception. |
If someone is still watching this, I may have fixed this here: #49 |
We don't use Jenkins anymore, so I won't be able to comment on this :( |
No worries, just like I found this issue when I was looking for a solution, others will probably find it too. |
I got the same problem. Is there any solution? stacktrace: Exception in thread "main" java.lang.Exception: Unexpected failure with path http://localhost:8080/jenkins/api/json, HTTP Status Code: 404, full map: [path:api/json] |
You can use my fork, didn't have any problems since using it |
If you are frequently getting random 404's, I think that is indicative of other issues with your Jenkins/Tomcat setup. Retrying repeatedly is more of a hack than a solution. I'd rather find out what the real problem is. We've seen very similar (identical?) issues when working with Jenkins instances that were proxied by Apache/Nginx. I'd have to really jog my memory but I'll try and dig up what that was exactly. |
Make sure to enable CSRF Protection by going to Global Security and selecting Prevent Cross Site Request Forgery exploits. This should enable the proper access to |
Hi,
not sure what's happening here, but I constantly get this exception:
This only happens when the job needs to create more than one view.
When I run the job several times again until all the views are created it runs like it should - maybe our server is just not fast enough to create the view so configuring fails? No idea... Jenkins is pretty fast, so I don't think this is the problem...
Jenkins version: 1.492
The text was updated successfully, but these errors were encountered: