|
Dear All,
When more than one builds are running concurrently in Jenkins, Jenkins in not showing the build status even the particular build is finished. It is waiting till the completion of all the builds which are running currenlty. Anybody can tell will it be a problem with Jenkins code or with the plugin? I am new to Jenkins community. Anybody can tell:- 1. How the build is getting triggered in the Jenkins?, Which module is doing this? 2. What are the main modules presented in Jenkins? 3. The functionalities of each module? 4. Why Jenkins are designed with different projects.? Thanks.. JoyAlbin |
|
If you have the static analysis plugins (checkstyle pmd etc) then those plugins will cause the build to wait if you have "compute new issues" (not sure of the exact text).
Bypassing compute new issues should cause latter builds not to block. https://issues.jenkins-ci.org/browse/JENKINS-11761 /James > -----Original Message----- > From: [hidden email] [mailto:jenkinsci- > [hidden email]] On Behalf Of Albin Joy > Sent: 13 March 2012 07:54 > To: Jenkins Developers > Subject: Jenkins is waiting for completion of all the concurrent build to give > output status > > Dear All, > > When more than one builds are running concurrently in Jenkins, Jenkins in not > showing the build status even the particular build is finished. It is waiting till the > completion of all the builds which are running currenlty. > > Anybody can tell will it be a problem with Jenkins code or with the plugin? > > I am new to Jenkins community. > > Anybody can tell:- > 1. How the build is getting triggered in the Jenkins?, Which module is doing > this? > 2. What are the main modules presented in Jenkins? > 3. The functionalities of each module? > 4. Why Jenkins are designed with different projects.? > > Thanks.. > JoyAlbin ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the [hidden email] and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ************************************************************************************** |
|
Hi James,
You mean to say this issue has already fixed in the latest jenkins version?. Any other settings I have to do to activate this feature? Can you please clarify me?
On Tue, Mar 13, 2012 at 7:01 PM, Nord, James <[hidden email]> wrote: If you have the static analysis plugins (checkstyle pmd etc) then those plugins will cause the build to wait if you have "compute new issues" (not sure of the exact text). Thanks &Regards Albin Joy |
|
In reply to this post by Nord, James
This will also happen in general during concurrent builds for any
"publisher" plugins which have their getRequiredMonitorService method returning a value of BuildStepMonitor.BUILD. Regards, Chris On 03/13/2012 12:01 PM, Nord, James wrote: > If you have the static analysis plugins (checkstyle pmd etc) then those plugins will cause the build to wait if you have "compute new issues" (not sure of the exact text). > > Bypassing compute new issues should cause latter builds not to block. > > https://issues.jenkins-ci.org/browse/JENKINS-11761 > > > /James > >> -----Original Message----- >> From: [hidden email] [mailto:jenkinsci- >> [hidden email]] On Behalf Of Albin Joy >> Sent: 13 March 2012 07:54 >> To: Jenkins Developers >> Subject: Jenkins is waiting for completion of all the concurrent build to give >> output status >> >> Dear All, >> >> When more than one builds are running concurrently in Jenkins, Jenkins in not >> showing the build status even the particular build is finished. It is waiting till the >> completion of all the builds which are running currenlty. >> >> Anybody can tell will it be a problem with Jenkins code or with the plugin? >> >> I am new to Jenkins community. >> >> Anybody can tell:- >> 1. How the build is getting triggered in the Jenkins?, Which module is doing >> this? >> 2. What are the main modules presented in Jenkins? >> 3. The functionalities of each module? >> 4. Why Jenkins are designed with different projects.? >> >> Thanks.. >> JoyAlbin > > > ************************************************************************************** > This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the [hidden email] and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. > > NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 > ************************************************************************************** |
|
Dear All, Any solution to make it up..? Anybody can help me for a solution?
On Wed, Mar 14, 2012 at 7:04 AM, Christopher Orr <[hidden email]> wrote: This will also happen in general during concurrent builds for any "publisher" plugins which have their getRequiredMonitorService method returning a value of BuildStepMonitor.BUILD. Thanks &Regards Albin Joy |
|
This post has NOT been accepted by the mailing list yet.
In reply to this post by joyalbin
Dear all,
Anybody can tell me, how we can enable or disable "CanComputeNew" option in the Jenkins CI? Thanks |
|
In reply to this post by joyalbin
That particular issue was fixed in the static code analysis plugins[1]. If you use any of these plugins then there is an option that needs to be set per job on each of the plugin configuration sections (I don’t recall the exact UI name of the option only the xml variable – which isn’t much help I’m afraid) /James [1] https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins From: [hidden email] [mailto:[hidden email]] On Behalf Of Albin Joy Hi James, You mean to say this issue has already fixed in the latest jenkins version?. Any other settings I have to do to activate this feature? Can you please clarify me? On Tue, Mar 13, 2012 at 7:01 PM, Nord, James <[hidden email]> wrote: If you have the static analysis plugins (checkstyle pmd etc) then those plugins will cause the build to wait if you have "compute new issues" (not sure of the exact text). > -----Original Message----- > From: [hidden email] [mailto:[hidden email] > [hidden email]] On Behalf Of Albin Joy > Sent: 13 March 2012 07:54 > To: Jenkins Developers > Subject: Jenkins is waiting for completion of all the concurrent build to give > output status > > Dear All, > > When more than one builds are running concurrently in Jenkins, Jenkins in not > showing the build status even the particular build is finished. It is waiting till the > completion of all the builds which are running currenlty. > > Anybody can tell will it be a problem with Jenkins code or with the plugin? > > I am new to Jenkins community. > > Anybody can tell:- > 1. How the build is getting triggered in the Jenkins?, Which module is doing > this? > 2. What are the main modules presented in Jenkins? > 3. The functionalities of each module? > 4. Why Jenkins are designed with different projects.? > > Thanks.. > JoyAlbin ************************************************************************************** -- |
|
In reply to this post by joyalbin
Which post-build actions are you using?
On 03/14/2012 12:46 AM, Albin Joy wrote: > Dear All, > > I need to display the build finished status as soon as the build > completed, even though the same job is running with another build. > Any solution to make it up..? > Anybody can help me for a solution? > > On Wed, Mar 14, 2012 at 7:04 AM, Christopher Orr <[hidden email] > <mailto:[hidden email]>> wrote: > > This will also happen in general during concurrent builds for any > "publisher" plugins which have their getRequiredMonitorService > method returning a value of BuildStepMonitor.BUILD. > > Regards, > Chris > > > > On 03/13/2012 12:01 PM, Nord, James wrote: > > If you have the static analysis plugins (checkstyle pmd etc) > then those plugins will cause the build to wait if you have > "compute new issues" (not sure of the exact text). > > Bypassing compute new issues should cause latter builds not to > block. > > https://issues.jenkins-ci.org/__browse/JENKINS-11761 > <https://issues.jenkins-ci.org/browse/JENKINS-11761> > > > /James > > -----Original Message----- > From: [hidden email] > <mailto:[hidden email]> [mailto:jenkinsci- > <mailto:jenkinsci-> > [hidden email] <mailto:[hidden email]>] On > Behalf Of Albin Joy > Sent: 13 March 2012 07:54 > To: Jenkins Developers > Subject: Jenkins is waiting for completion of all the > concurrent build to give > output status > > Dear All, > > When more than one builds are running concurrently in > Jenkins, Jenkins in not > showing the build status even the particular build is > finished. It is waiting till the > completion of all the builds which are running currenlty. > > Anybody can tell will it be a problem with Jenkins code or > with the plugin? > > I am new to Jenkins community. > > Anybody can tell:- > 1. How the build is getting triggered in the Jenkins?, Which > module is doing > this? > 2. What are the main modules presented in Jenkins? > 3. The functionalities of each module? > 4. Why Jenkins are designed with different projects.? > > Thanks.. > JoyAlbin > > > > ******************************__******************************__************************** > This message is confidential and intended only for the > addressee. If you have received this message in error, please > immediately notify the [hidden email] > <mailto:[hidden email]> and delete it from your system as > well as any copies. The content of e-mails as well as traffic > data may be monitored by NDS for employment and security > purposes. To protect the environment please do not print this > e-mail unless necessary. > > NDS Limited. Registered Office: One London Road, Staines, > Middlesex, TW18 4EX, United Kingdom. A company registered in > England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 > ******************************__******************************__************************** > > > > > > -- > Thanks &Regards > Albin Joy > |
|
Sorry for reopeing this issue again.
I disabled all the "static code analysers" in my build. Still the latest build is waiting for the completion of the old build. Scenario: Two builds are running concurrently on the same job. PC-Lint and Findbugs are enabled using "make" command (Execute Shell). But the plugins are disabled. The latest build dont have any Java code changes. So, the latest build finished all of its excution. The old build is doing PC-lint for its own cnages. But still, the latest build is waiting for the PClint execution completion of the old build. Once the Old build finished, latest build also will get finished soon. No "static code analyzers" are running. Please anybody help me to understand, why the latest build is wating for the "make" command execution of the old build. What is the dependency for the latest build on old build in this case? Thanks |
|
Hi there,
On 03/20/2012 02:57 AM, joyalbin wrote: > Sorry for reopeing this issue again. > I disabled all the "static code analysers" in my build. Still the latest > build is waiting for the completion of the old build. > > Scenario: > Two builds are running concurrently on the same job. > PC-Lint and Findbugs are enabled using "make" command (Execute Shell). > But the plugins are disabled. > > The latest build dont have any Java code changes. > So, the latest build finished all of its excution. The old build is doing > PC-lint for its own cnages. > But still, the latest build is waiting for the PClint execution completion > of the old build. > Once the Old build finished, latest build also will get finished soon. > > No "static code analyzers" are running. > > Please anybody help me to understand, why the latest build is wating for the > "make" command execution of the old build. > What is the dependency for the latest build on old build in this case? If you're just running "Execute shell" steps, is it possible that the PC-Lint tool is blocking? e.g. it has a lock file or similar which prevents concurrent execution? Chris |
|
Dear All,
I had seen in the jenkins code,
if the BuildStepMonitor is BUILD, the the build wait to reach the checkpoint-COMPLETE.
Any anybody explain me, is this the real code flow or in which scenario the Jenkins run through this flow.
Please anybody explain me....
Thanks |
| Powered by Nabble | Edit this page |
