Re: Problem with Clearcase plugin running many builds in parallel
Hi Vincent, 1.5.2 works fine. Thanks for the assistance and the fix. Sascha Am Montag, 7. Juli 2014 09:54:10 UTC+2 schrieb Vincent Latombe: > > I just released 1.5.2 with the form fix. > > Vincent > > > 2014-07-07 9:07 GMT+02:00 Sascha Herrmann >: > >> Hi! >> >> Thanks. It seems to be just a thing of saving the setting. When I put the >> "2" directly into the endViewDelay tag in the XML and then restart Jenkins, >> then the delay is applied fine and I see the "2" in the settings. >> >> 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-use...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 Clearcase plugin running many builds in parallel
Hi! Thanks. It seems to be just a thing of saving the setting. When I put the "2" directly into the endViewDelay tag in the XML and then restart Jenkins, then the delay is applied fine and I see the "2" in the settings. 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 Clearcase plugin running many builds in parallel
Hi! Version 1.5.1 doesn't work or I am doing it wrong. I set the delay to "2" in the settings, but when I come back to the settings after saving, it's "0" again, and there is no delay applied in endview according to the logs. 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 Clearcase plugin running many builds in parallel
Hi Vincent, sure that's okay. I was going for a simple system property since the error (from your reaction) seemed a bit exotic and has only been reported by me so far. But configuration in the plugin settings is great, thanks. So I will not create that pull request, Sascha Am Montag, 30. Juni 2014 18:12:16 UTC+2 schrieb Vincent Latombe: > > Hi, > > I have implemented your suggestion. I have added a configurable delay > after any endview call (for n. It is set to 0 by default and you can > configure it through the global plugin settings. > > Corresponding build is > > https://jenkins.ci.cloudbees.com/job/plugins/job/clearcase-plugin/71/org.jenkins-ci.plugins$clearcase/artifact/org.jenkins-ci.plugins/clearcase/1.6-SNAPSHOT/clearcase-1.6-SNAPSHOT.hpi > > Let me know if it is okay for you, then I'll issue a 1.5.1 with the fix. > > Cheers, > > Vincent > > > 2014-06-30 12:24 GMT+02:00 Sascha Herrmann >: > >> That was quick. It doesn't work. Immediate timeouts after endview again. >> >> Sascha >> >> Am Montag, 30. Juni 2014 12:21:00 UTC+2 schrieb Sascha Herrmann: >> >>> Hi Vincent, >>> >>> thanks. I will try. I doubt that it will bring an improvement, because >>> we're already ending the view_server processes after the build using a >>> batch script as I mentioned previously. >>> >>> I will update the post with my findings. >>> >>> Thanks again. >>> >>> Sascha >>> >>> Am Montag, 30. Juni 2014 09:32:19 UTC+2 schrieb Vincent Latombe: >>>> >>>> Hi Sascha, >>>> >>>> could you try the given build [1] and see whether you still encounter >>>> the issue? I have added a call to endview after the checkout. I believe it >>>> may also help with the delay you are observing when called initially >>>> (because it may be dependant on the number of active views on the host). >>>> If that do not work, I am open to add a configurable delay, you could >>>> add it to the endview command and open a pull request against the project. >>>> >>>> Cheers, >>>> >>>> Vincent >>>> >>>> [1] https://jenkins.ci.cloudbees.com/job/plugins/job/clearcase- >>>> plugin/70/org.jenkins-ci.plugins$clearcase/artifact/ >>>> org.jenkins-ci.plugins/clearcase/1.6-SNAPSHOT/ >>>> clearcase-1.6-SNAPSHOT.hpi >>>> >>>> Vincent >>>> >>>> >>>> 2014-06-30 8:08 GMT+02:00 Sascha Herrmann : >>>> >>>>> Builds run fine now. Seems that endview takes some time to finish >>>>> before the next command can be called. >>>>> Would it be possible to get a delay like that into the official >>>>> plugin? Maybe configurable with a system property? >>>>> >>>>> Sascha >>>>> >>>>> >>>>> >>>>> Am Freitag, 27. Juni 2014 08:56:09 UTC+2 schrieb Sascha Herrmann: >>>>> >>>>>> Hi! >>>>>> >>>>>> I have quickly added a "Thread.sleep( 5000 )" into >>>>>> BaseSnapshotCheckoutAction#checkout() between endview and setcs on >>>>>> our build machine and will monitor if that improves things. >>>>>> Maybe ClearTool.endViewServer() would be the better place for that >>>>>> delay. Not sure. >>>>>> 5000 millis is probably too much, yes. Just wanted to be on the safe >>>>>> side for the test. >>>>>> >>>>>> First build flows ran successfully. Seems to confirm that there is a >>>>>> timing problem in our environment. >>>>>> Will update the thread with the results in a couple of days when I >>>>>> know for sure. >>>>>> >>>>>> 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-use...@googlegroups.com. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >> 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/d/optout. >> > > -- 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 Clearcase plugin running many builds in parallel
That was quick. It doesn't work. Immediate timeouts after endview again. Sascha Am Montag, 30. Juni 2014 12:21:00 UTC+2 schrieb Sascha Herrmann: > > Hi Vincent, > > thanks. I will try. I doubt that it will bring an improvement, because > we're already ending the view_server processes after the build using a > batch script as I mentioned previously. > > I will update the post with my findings. > > Thanks again. > > Sascha > > Am Montag, 30. Juni 2014 09:32:19 UTC+2 schrieb Vincent Latombe: >> >> Hi Sascha, >> >> could you try the given build [1] and see whether you still encounter the >> issue? I have added a call to endview after the checkout. I believe it may >> also help with the delay you are observing when called initially (because >> it may be dependant on the number of active views on the host). >> If that do not work, I am open to add a configurable delay, you could add >> it to the endview command and open a pull request against the project. >> >> Cheers, >> >> Vincent >> >> [1] >> https://jenkins.ci.cloudbees.com/job/plugins/job/clearcase-plugin/70/org.jenkins-ci.plugins$clearcase/artifact/org.jenkins-ci.plugins/clearcase/1.6-SNAPSHOT/clearcase-1.6-SNAPSHOT.hpi >> >> Vincent >> >> >> 2014-06-30 8:08 GMT+02:00 Sascha Herrmann : >> >>> Builds run fine now. Seems that endview takes some time to finish before >>> the next command can be called. >>> Would it be possible to get a delay like that into the official plugin? >>> Maybe configurable with a system property? >>> >>> Sascha >>> >>> >>> >>> Am Freitag, 27. Juni 2014 08:56:09 UTC+2 schrieb Sascha Herrmann: >>> >>>> Hi! >>>> >>>> I have quickly added a "Thread.sleep( 5000 )" into >>>> BaseSnapshotCheckoutAction#checkout() between endview and setcs on our >>>> build machine and will monitor if that improves things. >>>> Maybe ClearTool.endViewServer() would be the better place for that >>>> delay. Not sure. >>>> 5000 millis is probably too much, yes. Just wanted to be on the safe >>>> side for the test. >>>> >>>> First build flows ran successfully. Seems to confirm that there is a >>>> timing problem in our environment. >>>> Will update the thread with the results in a couple of days when I know >>>> for sure. >>>> >>>> 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-use...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- 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 Clearcase plugin running many builds in parallel
Hi Vincent, thanks. I will try. I doubt that it will bring an improvement, because we're already ending the view_server processes after the build using a batch script as I mentioned previously. I will update the post with my findings. Thanks again. Sascha Am Montag, 30. Juni 2014 09:32:19 UTC+2 schrieb Vincent Latombe: > > Hi Sascha, > > could you try the given build [1] and see whether you still encounter the > issue? I have added a call to endview after the checkout. I believe it may > also help with the delay you are observing when called initially (because > it may be dependant on the number of active views on the host). > If that do not work, I am open to add a configurable delay, you could add > it to the endview command and open a pull request against the project. > > Cheers, > > Vincent > > [1] > https://jenkins.ci.cloudbees.com/job/plugins/job/clearcase-plugin/70/org.jenkins-ci.plugins$clearcase/artifact/org.jenkins-ci.plugins/clearcase/1.6-SNAPSHOT/clearcase-1.6-SNAPSHOT.hpi > > Vincent > > > 2014-06-30 8:08 GMT+02:00 Sascha Herrmann >: > >> Builds run fine now. Seems that endview takes some time to finish before >> the next command can be called. >> Would it be possible to get a delay like that into the official plugin? >> Maybe configurable with a system property? >> >> Sascha >> >> >> >> Am Freitag, 27. Juni 2014 08:56:09 UTC+2 schrieb Sascha Herrmann: >> >>> Hi! >>> >>> I have quickly added a "Thread.sleep( 5000 )" into >>> BaseSnapshotCheckoutAction#checkout() between endview and setcs on our >>> build machine and will monitor if that improves things. >>> Maybe ClearTool.endViewServer() would be the better place for that >>> delay. Not sure. >>> 5000 millis is probably too much, yes. Just wanted to be on the safe >>> side for the test. >>> >>> First build flows ran successfully. Seems to confirm that there is a >>> timing problem in our environment. >>> Will update the thread with the results in a couple of days when I know >>> for sure. >>> >>> 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-use...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 Clearcase plugin running many builds in parallel
Builds run fine now. Seems that endview takes some time to finish before the next command can be called. Would it be possible to get a delay like that into the official plugin? Maybe configurable with a system property? Sascha Am Freitag, 27. Juni 2014 08:56:09 UTC+2 schrieb Sascha Herrmann: > > Hi! > > I have quickly added a "Thread.sleep( 5000 )" into > BaseSnapshotCheckoutAction#checkout() between endview and setcs on our > build machine and will monitor if that improves things. > Maybe ClearTool.endViewServer() would be the better place for that delay. > Not sure. > 5000 millis is probably too much, yes. Just wanted to be on the safe side > for the test. > > First build flows ran successfully. Seems to confirm that there is a > timing problem in our environment. > Will update the thread with the results in a couple of days when I know > for sure. > > 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 Clearcase plugin running many builds in parallel
Hi! I have quickly added a "Thread.sleep( 5000 )" into BaseSnapshotCheckoutAction#checkout() between endview and setcs on our build machine and will monitor if that improves things. Maybe ClearTool.endViewServer() would be the better place for that delay. Not sure. 5000 millis is probably too much, yes. Just wanted to be on the safe side for the test. First build flows ran successfully. Seems to confirm that there is a timing problem in our environment. Will update the thread with the results in a couple of days when I know for sure. 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 Clearcase plugin running many builds in parallel
Hi! Thanks for your reply. IMHO CC isn't better than Subversion or Git. We're using snapshot views because we were running on problems with dynamic views with our particular CC version on our particular (old) Windows Server version we're running. So we had to convert all dynamic views (also the views we were using for Crucible) to snapshot views. Sascha Am Dienstag, 24. Juni 2014 08:52:22 UTC+2 schrieb Dirk Heinrichs: > > Am 23.06.2014 10:15, schrieb Sascha Herrmann: > > But there seems to be a (hardcoded?) limit of how many view_server > processes the albd can spawn. > > > Not that I'm aware of. > > BTW: Why snapshot views? If you don't use dynamic views, CC isn't any > better than Subversion or Git. > > Bye... > > Dirk > -- > > *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions > *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach > *Tel*: +49 2226 159 (Ansage) 1149 > *Email*: d...@recommind.com > *Skype*: dirk.heinrichs.recommind > www.recommind.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/d/optout.
Re: Problem with Clearcase plugin running many builds in parallel
Hmmm Google Groups ... couldn't edit the posting ... tried to delete error on delete wrote a new reply now original reply gone after all. We're on Windows, so there is no limit command. But we can run as many Perforce builds concurrently as we want. I doubt it's an OS limit. 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 Clearcase plugin running many builds in parallel
Hi Jes! Me again :o) Totally forgot. You being an expert in the plugin, what is the reason for the "endview" before the "setcs"? Our IT pinpoints this as the problem, although I don't see why there should be an immediate timeout in the first place. The commands issued earlier by the plugin start the view_server just fine. It seems to me more like a CC issue. The plugin is just calling cleartool after all. Maybe it's a timing issue, the view_server process for the view still in the process of going down, and at that very time the attempt to start it again?! I have no other explanation for an immediate timeout. But that's just guesswork of course. Thanks for your reply. Sascha Am Montag, 23. Juni 2014 10:39:22 UTC+2 schrieb Jes Struck: > > Hey sascha, > > with out vein an expert in this specific plugin, could you maybe tell if > you by, parallel builds mean that you have a lot of different jobs build at > the same time or you have a lot of concurrent executions of the same job? > If the later then look for view name, they might use the same name for all > the executions. > > I have never heard about this limit though i have heard that windows has a > limit on how many process it can run at a time, are you sure it's not that > limit you are running into. try running test limit -p for getting the > number of process. and test limit -t for number of threads. > > > > > > 2014-06-23 10:15 GMT+02:00 Sascha Herrmann >: > >> Running: >> Jenkins ver. 1.532.3 >> Jenkins ClearCase Plug-in ver. 1.5 using snapshot views >> Clearcase 7.1.2.12 >> >> Hi, >> >> we're currently setting up a new CI machine. The machine is quite >> powerful and we're trying to run as many build jobs in parallel as we can. >> >> No we run into two issues related to Clearcase: >> >> 1. It seems that after the catcs and before the setcs, an "endview" is >> issued. We run into the problem that the setcs then fails (with an >> immediate timeout): >> >> 07:12:55 [Misc_HEAD_Printing] $ "C:\Program >>> Files\IBM\RationalSDLC\ClearCase\bin\cleartool" endview -server >>> nightly_Misc_HEAD_Printing_view >> >> >> ... >> >> 07:12:55 Running cleartool setcs, this operation may take a while >>> 07:12:55 [ccview] $ "C:\Program >>> Files\IBM\RationalSDLC\ClearCase\bin\cleartool" setcs -current -overwrite >>> 07:12:55 cleartool: Error: Timed out trying to start view_server for >>> view :E:\oracle\clearcase\nightly_Misc_HEAD_Printing_view.vws >> >> >> Our IT is currently puzzled why this happens. They're asking why the >> plugin issues the "endview" command. So I am wondering if someone else has >> encountered that problem and knows how to circumvent it. I assume that it >> is related to the amount of parallel build jobs, as this problem does not >> show up on our old CI server (which kind of runs build solely in sequence). >> >> 2. As I said, we're running as many builds as possible. But there seems >> to be a (hardcoded?) limit of how many view_server processes the albd can >> spawn. And we're running into that limit, resulting in errors. I found no >> place where I can raise that limit in CC. So for every CC build job, we're >> adding a batch build step, issuing an endview command after the build, >> stopping the view_server process. Which is a fine workaround. But it would >> be great if the plugin would feature an option to end the view after the >> checkout. Not sure if that makes sense in general. It would for us. That's >> more like a feature request :o) >> >> Regards, >> >> 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-use...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > [image: ] > <http://www.praqma.net/> > *Jes Struck, * > Consultant > j...@praqma.net > +45 31 42 09 00 > Skype:jes.struck *Praqma A/S* > www.praqma.net > Allerød Stationsvej 4 > DK-3450 Allerød > +45 36 77 27 62 <http://www.praqma.net/jciusrcph12> > <http://www.praqma.net/jcicodecamp12> > > -- 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 Clearcase plugin running many builds in parallel
Many different jobs at the same time. The limit seems to exist. There are not that many processes running on that machine since we solely use it for Jenkins. Concurrent Perforce builds we can have as many as we want, no problem there. But with Clearcase we noticed that we get errors from cleartool. Only way to stop these was to end the view_server process after a build (these processes tend to linger, one per view, if we don't). No such thing as a limit command on Windows. Sascha Am Montag, 23. Juni 2014 10:39:22 UTC+2 schrieb Jes Struck: > > Hey sascha, > > with out vein an expert in this specific plugin, could you maybe tell if > you by, parallel builds mean that you have a lot of different jobs build at > the same time or you have a lot of concurrent executions of the same job? > If the later then look for view name, they might use the same name for all > the executions. > > I have never heard about this limit though i have heard that windows has a > limit on how many process it can run at a time, are you sure it's not that > limit you are running into. try running test limit -p for getting the > number of process. and test limit -t for number of threads. > > > > > > 2014-06-23 10:15 GMT+02:00 Sascha Herrmann >: > >> Running: >> Jenkins ver. 1.532.3 >> Jenkins ClearCase Plug-in ver. 1.5 using snapshot views >> Clearcase 7.1.2.12 >> >> Hi, >> >> we're currently setting up a new CI machine. The machine is quite >> powerful and we're trying to run as many build jobs in parallel as we can. >> >> No we run into two issues related to Clearcase: >> >> 1. It seems that after the catcs and before the setcs, an "endview" is >> issued. We run into the problem that the setcs then fails (with an >> immediate timeout): >> >> 07:12:55 [Misc_HEAD_Printing] $ "C:\Program >>> Files\IBM\RationalSDLC\ClearCase\bin\cleartool" endview -server >>> nightly_Misc_HEAD_Printing_view >> >> >> ... >> >> 07:12:55 Running cleartool setcs, this operation may take a while >>> 07:12:55 [ccview] $ "C:\Program >>> Files\IBM\RationalSDLC\ClearCase\bin\cleartool" setcs -current -overwrite >>> 07:12:55 cleartool: Error: Timed out trying to start view_server for >>> view :E:\oracle\clearcase\nightly_Misc_HEAD_Printing_view.vws >> >> >> Our IT is currently puzzled why this happens. They're asking why the >> plugin issues the "endview" command. So I am wondering if someone else has >> encountered that problem and knows how to circumvent it. I assume that it >> is related to the amount of parallel build jobs, as this problem does not >> show up on our old CI server (which kind of runs build solely in sequence). >> >> 2. As I said, we're running as many builds as possible. But there seems >> to be a (hardcoded?) limit of how many view_server processes the albd can >> spawn. And we're running into that limit, resulting in errors. I found no >> place where I can raise that limit in CC. So for every CC build job, we're >> adding a batch build step, issuing an endview command after the build, >> stopping the view_server process. Which is a fine workaround. But it would >> be great if the plugin would feature an option to end the view after the >> checkout. Not sure if that makes sense in general. It would for us. That's >> more like a feature request :o) >> >> Regards, >> >> 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-use...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > [image: ] > <http://www.praqma.net/> > *Jes Struck, * > Consultant > j...@praqma.net > +45 31 42 09 00 > Skype:jes.struck *Praqma A/S* > www.praqma.net > Allerød Stationsvej 4 > DK-3450 Allerød > +45 36 77 27 62 <http://www.praqma.net/jciusrcph12> > <http://www.praqma.net/jcicodecamp12> > > -- 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 Clearcase plugin running many builds in parallel
Running: Jenkins ver. 1.532.3 Jenkins ClearCase Plug-in ver. 1.5 using snapshot views Clearcase 7.1.2.12 Hi, we're currently setting up a new CI machine. The machine is quite powerful and we're trying to run as many build jobs in parallel as we can. No we run into two issues related to Clearcase: 1. It seems that after the catcs and before the setcs, an "endview" is issued. We run into the problem that the setcs then fails (with an immediate timeout): 07:12:55 [Misc_HEAD_Printing] $ "C:\Program > Files\IBM\RationalSDLC\ClearCase\bin\cleartool" endview -server > nightly_Misc_HEAD_Printing_view ... 07:12:55 Running cleartool setcs, this operation may take a while > 07:12:55 [ccview] $ "C:\Program > Files\IBM\RationalSDLC\ClearCase\bin\cleartool" setcs -current -overwrite > 07:12:55 cleartool: Error: Timed out trying to start view_server for view > :E:\oracle\clearcase\nightly_Misc_HEAD_Printing_view.vws Our IT is currently puzzled why this happens. They're asking why the plugin issues the "endview" command. So I am wondering if someone else has encountered that problem and knows how to circumvent it. I assume that it is related to the amount of parallel build jobs, as this problem does not show up on our old CI server (which kind of runs build solely in sequence). 2. As I said, we're running as many builds as possible. But there seems to be a (hardcoded?) limit of how many view_server processes the albd can spawn. And we're running into that limit, resulting in errors. I found no place where I can raise that limit in CC. So for every CC build job, we're adding a batch build step, issuing an endview command after the build, stopping the view_server process. Which is a fine workaround. But it would be great if the plugin would feature an option to end the view after the checkout. Not sure if that makes sense in general. It would for us. That's more like a feature request :o) Regards, 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 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
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
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.
