Hi James,
thanks for you assistance.
Sascha
Am Freitag, 4. April 2014 22:49:15 UTC+2 schrieb teilo:
>
> Hi Sascha,
>
> Fix is at https://github.com/jenkinsci/build-flow-plugin/pull/42 if you
> want to get the source and do a local build.
> Otherwise wait for the code to be accepted and either g
Hi Sascha,
Fix is at https://github.com/jenkinsci/build-flow-plugin/pull/42 if you
want to get the source and do a local build.
Otherwise wait for the code to be accepted and either grab the latest build
from Jenkins, or wait for the release.
/James
On Friday, 4 April 2014 08:36:24 UTC+1, Sasc
Thanks for your reply.
Yes, using Fiddler, the last request I see before the error is a GET to
http:///job//descriptorByName/com.cloudbees.plugins.flow.BuildFlow/checkDsl?value=...
with value being the encoded text of the DSL. The DSL itself is some 3900
characters. Then add the encoding ov
Sounds like the flow is validating the dsl via a http get request.
If the flow is large the http request will be too large for some severs to
handle. This intern causes some headers to be lost on the server, to which
jenkins will the think you are not authenticated and will clear your cookie...
Hi!
I have the following problem with the CloudBees plugin:
I am logged in with a user with full permissions in Jenkins. I select a
flow build job and go to "Configure".
The configuration page opens, loads completely and everything looks fine.
After some 10 seconds, without doing anything, I ge
