Re: Problem with Build Flow plugin 0.10 on Jenkins 1.532.1
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 grab the latest > build from Jenkins, or wait for the release. > > /James > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Problem with Build Flow plugin 0.10 on Jenkins 1.532.1
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, Sascha Herrmann wrote: > > 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 overhead. The GET request is then some > 6522 bytes. > > When you talk about a fix ... how would we get the fix? Will it go into > the next plugin version? > > Sascha > > Am Mittwoch, 2. April 2014 22:36:57 UTC+2 schrieb teilo: >> >> 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... >> >> I don't see anything in the code to force it to use http post, but I'm >> away from my pc for a while so can't check and fix, should be a few lines >> to change if I am correct at the cause. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Problem with Build Flow plugin 0.10 on Jenkins 1.532.1
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 overhead. The GET request is then some 6522 bytes. When you talk about a fix ... how would we get the fix? Will it go into the next plugin version? Sascha Am Mittwoch, 2. April 2014 22:36:57 UTC+2 schrieb teilo: > > 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... > > I don't see anything in the code to force it to use http post, but I'm > away from my pc for a while so can't check and fix, should be a few lines > to change if I am correct at the cause. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Problem with Build Flow plugin 0.10 on Jenkins 1.532.1
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... I don't see anything in the code to force it to use http post, but I'm away from my pc for a while so can't check and fix, should be a few lines to change if I am correct at the cause. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Problem with Build Flow plugin 0.10 on Jenkins 1.532.1
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 get a "You do not have the Run Scripts permission necessary to edit this field." warning below the flow DSL text area, and I am logged out of Jenkins. Meaning: As soon as I click a link that requires login, I am back on the login page. Using Chrome 33. On Firefox I can also see a: "HTTP/0.9 200 OK Server: Winstone Servlet Engine v0.9.10 Set-Cookie: crowd.token_key=""; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; HttpOnly Content-Type: text/html;charset=UTF-8 Connection: Close Date: Wed, 02 Apr 2014 07:23:16 GMT X-Powered-By: Servlet/2.5 (Winstone/0.9.10) Set-Cookie: ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE=; Path=/ " in the UI. We're using CROWD for user authentication and authorization. The "Set-Cookie" seems to hint that something is triggering a logout by clearing CROWD's cookie. This only happens on configuration pages of build flows. We have hundreds of build jobs. Only the flows show that behaviour. The DSL of the flow is correct. The flows itself run without problems. Problem happens when I try to configure the flow. The error log reveals nothing. Thanks. Sascha -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Problem with Build Flow Plugin
The next version of email-ext should allow concurrent executions, it will just put a warning in the build log if you are trying to use content that doesn't make sense with concurrent builds. On Fri, Nov 15, 2013 at 11:43 AM, Jeremy Morton wrote: > Email notifications at the end of Job2 are one of the things that cause it > to wait for all previously started runs to finish in order to compare > results. :( > > > On Friday, November 15, 2013 12:58:17 PM UTC-5, James Nord (jnord) wrote: > >> That’s not the flow that’s stopping it but job2. >> >> >> >> Most likely you have some post build reports (configuration ) that >> compare to the previous run to generate new/resolved issues (e.g. test >> results, static anlaysis with new violations identified…) >> >> >> >> /James >> >> >> >> *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On >> Behalf Of *Zofia Majenka >> >> *Sent:* 15 November 2013 17:13 >> *To:* jenkins...@googlegroups.com >> >> *Subject:* Problem with Build Flow Plugin >> >> >> >> Hi, >> >> We are using the Build Flow Plugin in Jenkins. This is scenario: >> >> Start the flow 1: Job1 -> Job2 -> Job3 >> >> Start the flow 2: Job1 -> Job2 -> Job3 >> >> Start the flow 3: Job1 -> Job2 -> Job3 >> >> The same flow is started 3 times with a few minutes delay between them. >> >> We have noticed that thought the Job2 in the flow 3 is finished, it hangs >> on upstream notification and the Job3 within the same flow 3 could not be >> started. It waits until the Job2 in flow1 is finished and Job2 in flow2 is >> finished. >> Is it how it always works? The same job started in parallel (several >> execution of the same test flow on different resources) tends to become a >> serial? >> >> >> Start Job2 flow1 >> Start Job2 flow2 >> Start Job2 flow3 >> >> Finish Job2 flow1 >> Finish Job2 flow2 >> Finish Job2 flow3 >> >> Is it possible to start as above but finish like this: >> >> Finish Job2 flow3 and start Job3 >> Finish Job2 flow2 and start Job3 >> Finish Job2 flow1 and start Job3 >> >> >> Or there is something in configuration we are missing? The job is >> configured to be executed in parallel. >> >> Any ideas? How we can make the flow 3 to finish thought the Job2 in flow1 >> takes long time to execute? >> >> Regards >> /Zofia >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-use...@googlegroups.com. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> >>-- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- Website: http://earl-of-code.com -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problem with Build Flow Plugin
That is the standard Jenkins behaviour. You'll notice the same without the build-flow plugin. On Friday, 15 November 2013 17:12:59 UTC, Zofia Majenka wrote: > > Hi, > > We are using the Build Flow Plugin in Jenkins. This is scenario: > > Start the flow 1: Job1 -> Job2 -> Job3 > > Start the flow 2: Job1 -> Job2 -> Job3 > > Start the flow 3: Job1 -> Job2 -> Job3 > > The same flow is started 3 times with a few minutes delay between them. > > We have noticed that thought the Job2 in the flow 3 is finished, it hangs > on upstream notification and the Job3 within the same flow 3 could not be > started. It waits until the Job2 in flow1 is finished and Job2 in flow2 is > finished. > Is it how it always works? The same job started in parallel (several > execution of the same test flow on different resources) tends to become a > serial? > > > Start Job2 flow1 > Start Job2 flow2 > Start Job2 flow3 > > Finish Job2 flow1 > Finish Job2 flow2 > Finish Job2 flow3 > > Is it possible to start as above but finish like this: > > Finish Job2 flow3 and start Job3 > Finish Job2 flow2 and start Job3 > Finish Job2 flow1 and start Job3 > > > Or there is something in configuration we are missing? The job is > configured to be executed in parallel. > > Any ideas? How we can make the flow 3 to finish thought the Job2 in flow1 > takes long time to execute? > > Regards > /Zofia > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problem with Build Flow Plugin
Email notifications at the end of Job2 are one of the things that cause it to wait for all previously started runs to finish in order to compare results. :( On Friday, November 15, 2013 12:58:17 PM UTC-5, James Nord (jnord) wrote: > > That’s not the flow that’s stopping it but job2. > > > > Most likely you have some post build reports (configuration ) that compare > to the previous run to generate new/resolved issues (e.g. test results, > static anlaysis with new violations identified…) > > > > /James > > > > *From:* jenkins...@googlegroups.com [mailto: > jenkins...@googlegroups.com ] *On Behalf Of *Zofia Majenka > *Sent:* 15 November 2013 17:13 > *To:* jenkins...@googlegroups.com > *Subject:* Problem with Build Flow Plugin > > > > Hi, > > We are using the Build Flow Plugin in Jenkins. This is scenario: > > Start the flow 1: Job1 -> Job2 -> Job3 > > Start the flow 2: Job1 -> Job2 -> Job3 > > Start the flow 3: Job1 -> Job2 -> Job3 > > The same flow is started 3 times with a few minutes delay between them. > > We have noticed that thought the Job2 in the flow 3 is finished, it hangs > on upstream notification and the Job3 within the same flow 3 could not be > started. It waits until the Job2 in flow1 is finished and Job2 in flow2 is > finished. > Is it how it always works? The same job started in parallel (several > execution of the same test flow on different resources) tends to become a > serial? > > > Start Job2 flow1 > Start Job2 flow2 > Start Job2 flow3 > > Finish Job2 flow1 > Finish Job2 flow2 > Finish Job2 flow3 > > Is it possible to start as above but finish like this: > > Finish Job2 flow3 and start Job3 > Finish Job2 flow2 and start Job3 > Finish Job2 flow1 and start Job3 > > > Or there is something in configuration we are missing? The job is > configured to be executed in parallel. > > Any ideas? How we can make the flow 3 to finish thought the Job2 in flow1 > takes long time to execute? > > Regards > /Zofia > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-use...@googlegroups.com . > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Problem with Build Flow Plugin
That's not the flow that's stopping it but job2. Most likely you have some post build reports (configuration ) that compare to the previous run to generate new/resolved issues (e.g. test results, static anlaysis with new violations identified...) /James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Zofia Majenka Sent: 15 November 2013 17:13 To: jenkinsci-users@googlegroups.com Subject: Problem with Build Flow Plugin Hi, We are using the Build Flow Plugin in Jenkins. This is scenario: Start the flow 1: Job1 -> Job2 -> Job3 Start the flow 2: Job1 -> Job2 -> Job3 Start the flow 3: Job1 -> Job2 -> Job3 The same flow is started 3 times with a few minutes delay between them. We have noticed that thought the Job2 in the flow 3 is finished, it hangs on upstream notification and the Job3 within the same flow 3 could not be started. It waits until the Job2 in flow1 is finished and Job2 in flow2 is finished. Is it how it always works? The same job started in parallel (several execution of the same test flow on different resources) tends to become a serial? Start Job2 flow1 Start Job2 flow2 Start Job2 flow3 Finish Job2 flow1 Finish Job2 flow2 Finish Job2 flow3 Is it possible to start as above but finish like this: Finish Job2 flow3 and start Job3 Finish Job2 flow2 and start Job3 Finish Job2 flow1 and start Job3 Or there is something in configuration we are missing? The job is configured to be executed in parallel. Any ideas? How we can make the flow 3 to finish thought the Job2 in flow1 takes long time to execute? Regards /Zofia -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Problem with Build Flow Plugin
Hi, We are using the Build Flow Plugin in Jenkins. This is scenario: Start the flow 1: Job1 -> Job2 -> Job3 Start the flow 2: Job1 -> Job2 -> Job3 Start the flow 3: Job1 -> Job2 -> Job3 The same flow is started 3 times with a few minutes delay between them. We have noticed that thought the Job2 in the flow 3 is finished, it hangs on upstream notification and the Job3 within the same flow 3 could not be started. It waits until the Job2 in flow1 is finished and Job2 in flow2 is finished. Is it how it always works? The same job started in parallel (several execution of the same test flow on different resources) tends to become a serial? Start Job2 flow1 Start Job2 flow2 Start Job2 flow3 Finish Job2 flow1 Finish Job2 flow2 Finish Job2 flow3 Is it possible to start as above but finish like this: Finish Job2 flow3 and start Job3 Finish Job2 flow2 and start Job3 Finish Job2 flow1 and start Job3 Or there is something in configuration we are missing? The job is configured to be executed in parallel. Any ideas? How we can make the flow 3 to finish thought the Job2 in flow1 takes long time to execute? Regards /Zofia -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
