RE: problems when integrate cygwin's bash script into jenkins
And here is the detailed java exception log. But I don't know what does it mean. Br, Tony Zhang, Tz GSM Team @ Beijing, China From: ZHANG Xinchun A Sent: Friday, October 12, 2012 11:39 AM To: 'jenkinsci-users@googlegroups.com' Subject: problems when integrate cygwin's bash script into jenkins Hello All, I run into this problem. I have cygwin and Jenkins installed on my pc. And I have a bash script ci.sh If I click the mintty.exe from the desktop to start the terminal and run the script. It would run ok. but if I invoke the bash.exe from Jenkins. The java part in the script always report some fatal error as following, both under condition of invoking Bash.exe with --login -i or not. I google around and I see some similar reports as my problem but not a solution. Could anybody provide some information on this? Thanks a lot Br, Tony Zhang, Tz GSM Team @ Beijing, China # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x7c910a19, pid=6176, tid=7720 # # JRE version: 6.0_21-b07 # Java VM: Java HotSpot(TM) Client VM (17.0-b17 mixed mode windows-x86 ) # Problematic frame: # C [ntdll.dll+0x10a19] # # An error report file with more information is saved as: # E:\cygwin\home\zhiqunwa\workspace33\o\hs_err_pid6176.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. hs_err_pid6176.log Description: hs_err_pid6176.log
Serializing commits to multiple git repositories
I want to make an automatic approve/promote ONE commit at a time with multiple git repositories. Background: The issue is that a commits is too often breaking the product(dev env) and causing productivity issues for the team. - 10 git repositories. - all 10 has unit tests. - 50 Jenkins jobs integration tests are running. - Integration tests find many issues that is very hard to test for in unit tests. We have resources to run the a large set of integration test on every commit. The issue is to serialize the commits and rejects commits that break integration tests. I am sure I am NOT the first to want to do this type of thing. Do anybody have a pointer to a description on who somebody have done this before? My web search has been without results. What I am thinking of using is a combination of Jenkins, Gerrit [1], the Gerrit/Android tool 'repo' [2], Gerrit trigger plugin [3] Multijob plugin [4], and possibly Repo plugin [5]. If anybody have been able to accomplish the desired serialization of commits across git repositories I would VERY much like to know how. Any information is of interest. As little as listing the tools is of interest. Regards Asmund [1] http://code.google.com/p/gerrit/ [2] http://code.google.com/p/git-repo/ [3] https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger [4] https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin [5] https://wiki.jenkins-ci.org/display/JENKINS/Repo+Plugin
答复: How can jenkins master share slave nodes.
Yes, I do want to share the logical slave, because if there is a master that delivered a job to slave1 (physical machine), and I want another master to deliver its job to slave2(physical); in this case, we can balance the jobs between different physical machine. Shen Hui BB - F2 - AW264|x28530 发件人: vf-2 [via Jenkins] [mailto:ml-node+s361315n4643048...@n4.nabble.com] 发送时间: 2012年10月12日 13:15 收件人: Shen,Hui 主题: Re: How can jenkins master share slave nodes. Not sure if i understand you correctly. A slave is only a logical unit, it has not to be a physical machine. You can have multiple slaves running on one host, without interfering each other. So, every master can have as many slave as you want on any hosts, as long as each slave (not host) has its own root-fs. Then it does not matter hou many hosts you have, you can have 5 *independent* jenkins master-slave cluster across your build farm, each one does not care (does not know) the existence of other clusters. You can share all the hardware resources of you 20 hosts, the slave configuration is totally orthognal. So you can share the hardware resources across 5 independent clasters, each has (theoretically) as many slaves as necessary. but if you want to share the (logical unit) *slave*, i dont think it is possible, even it is, i can not find any reason to do so. Shen Hui [hidden email]/user/SendEmail.jtp?type=nodenode=4643048i=0 schrieb: Hi buddy, I have 5 masters, and suppose I have a slave pool with 20 nodes. Can these 5 master share these 20 slaves; because if i separate 20 slave into 5 group(each has 4), each attached to a master, that's meaning a single master can schedule only with 4 slaves; so there is this case, some groups are busing, and other may be idle. i'd like these 20 slaves can share jobs schedule among these 5 masters. Can anybody help me on this? Appreciate very much. -- View this message in context: http://jenkins.361315.n4.nabble.com/How-can-jenkins-master-share-slave-nodes-tp4642699.html Sent from the Jenkins users mailing list archive at Nabble.comhttp://Nabble.com. -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. If you reply to this email, your message will be added to the discussion below: http://jenkins.361315.n4.nabble.com/How-can-jenkins-master-share-slave-nodes-tp4642699p4643048.html To unsubscribe from How can jenkins master share slave nodes., click herehttp://jenkins.361315.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4642699code=c2hlbmh1aTAyQGJhaWR1LmNvbXw0NjQyNjk5fC0yMTI1MDQwODgy. NAMLhttp://jenkins.361315.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://jenkins.361315.n4.nabble.com/How-can-jenkins-master-share-slave-nodes-tp4642699p4643063.html Sent from the Jenkins users mailing list archive at Nabble.com.
Re: PMD plugin breaks with Jenkins 1.456 and up
Can you please post your environment as comment in Jira: https://issues.jenkins-ci.org/browse/JENKINS-15490 Ulli Am Freitag, 27. Juli 2012 14:34:14 UTC+2 schrieb Kjetil Ødegaard: I'm trying to upgrade Jenkins and the PMD plugin, but I keep getting an exception [1] on certain Maven jobs which use PMD. Is this a known problem? It works fine if I downgrade Jenkins to 1.455. Versions 1.456, 1.457, 1.460, 1.465 and 1.473 all fail with this exception. PMD plugin version 3.29, analysis-core version 1.42. No other hpi plugins. Thanks for any help with this, —Kjetil [1] [INFO] Trace org.apache.commons.logging.LogConfigurationException: java.lang.IllegalAccessError: tried to access class org.apache.commons.logging.impl.LogFactoryImpl$3 from class org.apache.commons.logging.impl.LogFactoryImpl (Caused by java.lang.IllegalAccessError: tried to access class org.apache.commons.logging.impl.LogFactoryImpl$3 from class org.apache.commons.logging.impl.LogFactoryImpl) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:637) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:704) at org.apache.commons.digester.Digester.init(Digester.java:304) at hudson.plugins.pmd.parser.PmdParser.parse(PmdParser.java:51) at hudson.plugins.analysis.core.AbstractAnnotationParser.parse(AbstractAnnotationParser.java:52) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:358) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:317) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:266) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath.act(FilePath.java:832) at hudson.FilePath.act(FilePath.java:814) at hudson.plugins.pmd.PmdReporter.perform(PmdReporter.java:112) at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:304) at hudson.maven.Maven2Builder.postExecute(Maven2Builder.java:155) at hudson.maven.MavenBuilder$Adapter.postExecute(MavenBuilder.java:310) at hudson.maven.agent.PluginManagerInterceptor$1MojoIntercepterImpl.callPost(PluginManagerInterceptor.java:170) at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:183) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:151) at hudson.maven.Maven2Builder.call(Maven2Builder.java:77) at hudson.maven.Maven2Builder.call(Maven2Builder.java:53) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at
Re: scm-sync-configuration: huge logs since last update (version 0.0.6)
Hi, I've made a release based on the current git source code to fix this logging issue, if anyone is interested, the hpi can be found here: http://dl.dropbox.com/u/28698412/scm-sync-configuration.hpi Cheers, Reynald On Wed, Oct 10, 2012 at 9:59 AM, Reynald Borer reynald.bo...@gmail.com wrote: Hello everybody, I've recently updated the scm-sync-configuration plugin of my Jenkins installation and this plugin is now quite verbose with logs. My log file grew of around 2gb per day. This issue has already been reported in https://issues.jenkins-ci.org/browse/JENKINS-15266 and is already fixed, will a new release of this plugin be done with this fix soon? If not, I might consider installing a snapshot version instead. Thanks, Reynald
Re: What is the difference between multi configuration job and matrix based job?.
I guess you're referring to the parent build that appears when executing a multi-configuration job, which monitors the child builds. This doesn't actually consume an additional executor. But if you want to control which slave this runs on, you can use the Matrix Tie Parent Plugin: https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Tie+Parent+Plugin Regards, Chris On 12/10/12 07:42, Varghese Renny wrote: Why using additional executor for slave node running multiconfiguration job? Regards, varghese
remote build
Hi I have set parameter in my Jenkins. In earlier my Jenkins job was triggered using remote token that time i have not set any parameter in my job. After i set parameter, how to trigger my Jenkins job using remote build token? Please anyone suggest me?
Re: 答复: How can jenkins master share slave nodes.
On Fri, Oct 12, 2012 at 2:59 AM, Shen Hui shenhu...@baidu.com wrote: Yes, I do want to share the logical slave, because if there is a master that delivered a job to slave1 (physical machine), and I want another master to deliver its job to slave2(physical); in this case, we can balance the jobs between different physical machine. I don't think jenkins currently has any way to track other sources of load on the slaves. Why not run all your jobs on one master so the queuing will work more efficiently? -- Les Mikesell lesmikes...@gmail.com
graphite integration
Dear List, In our organization we have graphite (http://graphite.wikidot.com) to evaluate servers performances. I was reading this article: http://codeascraft.etsy.com/2010/12/08/track-every-release/ and would be nice to have something to link jenkins with graphite and track deployments on servers graphs.. I thinking to a post build step action .. that sends the build info to graphite using the graphite api ( http://graphite.wikidot.com/url-api-reference ) and draw a vertical line like mentioned in article. Regards Federico
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.
I tried setting up a slave: with the following config (Master / Slave Java Versions) Master: java -version java version 1.6.0_24 OpenJDK Runtime Environment (IcedTea6 1.11.4) (6b24-1.11.4-1ubuntu0.12.04.1) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Slave: java -version java version 1.6.0_06 Java(TM) SE Runtime Environment (build 1.6.0_06-b02) Java HotSpot(TM) 64-Bit Server VM (build 10.0-b22, mixed mode) EXCEPTION: Installing chromedriver to /home/kahmed/tools/chromedriver ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. java.lang.NullPointerException at org.jenkinsci.plugins.chromedriver.DownloadableImpl.getType(DownloadableImpl.java:91) at org.jenkinsci.plugins.chromedriver.DownloadableImpl.select(DownloadableImpl.java:78) at org.jenkinsci.plugins.chromedriver.DownloadableImpl.resolve(DownloadableImpl.java:35) at org.jenkinsci.plugins.chromedriver.ComputerListenerImpl.process(ComputerListenerImpl.java:43) at org.jenkinsci.plugins.chromedriver.ComputerListenerImpl.preOnline(ComputerListenerImpl.java:34) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:370) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:317) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:454) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:293) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) [10/12/12 10:21:47] [SSH] Connection closed. ERROR: Connection terminated java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:90) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) ERROR: [10/12/12 10:21:47] slave agent was terminated java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:90) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
Re: graphite integration
fridodev, try https://github.com/katzj/jenkins-to-graphite.git -Kamal From: fridodev frido...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Friday, October 12, 2012 9:02 AM Subject: graphite integration Dear List, In our organization we have graphite (http://graphite.wikidot.com/) to evaluate servers performances. I was reading this article: http://codeascraft.etsy.com/2010/12/08/track-every-release/ and would be nice to have something to link jenkins with graphite and track deployments on servers graphs.. I thinking to a post build step action .. that sends the build info to graphite using the graphite api ( http://graphite.wikidot.com/url-api-reference ) and draw a vertical line like mentioned in article. Regards Federico
Real-time log parsing?
I'm running multi-hour test cycles and my users have a demand for real-time results. If test #50 failed 45 minutes in, they want to be able to see it without waiting five hours for the rest of the tests to run. We've had this problem for longer than we've had Jenkins, so our solution is to have a log parser separate from Jenkins tail the build log, reading it as it's being written and writing test results to a database powering a non-Jenkins web site. Said process is also reading other auxiliary files (far too many to turn into Jenkins artifacts), so it has to run on the host the slave node and the build are running on, not the machine hosting the Jenkins server. The problem with this is that we have to make sure that everything gets appended to a log file on disk (so the parser can tail it) and to standard output (so that we can see it). Accidentally opening the log file for write rather than append truncates the log and the parser gets lost. Is there a way for a process on the slave node machine to tail the build log that Jenkins is getting? Can Jenkins' output log be replicated in real time in the workspace? Can a groovy JAR be run asynchronously inside the slave as it's building, and watch the bytes go by? Any other ideas? --Rob The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
Jenkins Database Envy - is it just me?
I've been using Jenkins for a couple of years (starting back before the Hudson/Jenkins fork) and it has saved my career on several occasions. However, I'm getting some database envy. I want to be able to read from and write to the database of builds and build results without HTTPing through the server. I'd also like to not have everything in core all the time (the lazy-loading feature in 1.485 was, IMHO, a case of DB envy). What I'd love to see is to have the file-based persistence layer connecting to a JDBC data source, probably shipping with embedded HSQLDB or something by default. But my question is: is it just me? I'm using Jenkins in a fairly heavy-duty way (and investigating if we should upgrade to CloudBees Enterprise Edition), and effectively have a separate database, build parser, and build results web site so that we can see results going back several years and query it in multiple ways. I don't think that I'm your typical Jenkins user. In fact, I can see reasons not to use a DB persistence layer: the files that the Jenkins server keeps for its configuration and logs are pretty human-readable, and having a DB persistence layer would require a DB connection to look at. I also realize that, even if we did want to go to a DB layer, this would be an expensive process that would take resources away from adding more features to Jenkins. So how many people would like to see a DB layer, how many wouldn't, and how many don't care how it keeps its data under the hood? --Rob Mandeville Litle Co. The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
Re: Jenkins Database Envy - is it just me?
On Fri, Oct 12, 2012 at 10:39 AM, Mandeville, Rob rmandevi...@litle.com wrote: I’ve been using Jenkins for a couple of years (starting back before the Hudson/Jenkins fork) and it has saved my career on several occasions. However, I’m getting some database envy. I want to be able to read from and write to the database of builds and build results without HTTPing through the server. I’d also like to not have everything in core all the time (the lazy-loading feature in 1.485 was, IMHO, a case of DB envy). What I’d love to see is to have the file-based persistence layer connecting to a JDBC data source, probably shipping with embedded HSQLDB or something by default. But my question is: is it just me? I've always thought that filesystems were a nice place to keep files... -- Les Mikesell lesmikes...@gmail.com
Re: Jenkins Database Envy - is it just me?
My thoughts on the discussion I have also tried to work with Jenkins which have the same requirement: I want to be able to read from and write to the database of builds and build results without HTTPing through the server. I’d also like to not have everything in core all the time Though, do we need a database? Maybe we just need to improve the Jenkins cmd-line and some of the features in which Jenkins manages its build-data. I personally like designing/developing systems using VIEW-Objects, Business-Objects and Data-Access-Objects. The Data-Access-Objects can access either a dbase, filesystem, or anything you desire, without affecting the core. ... Marek On Fri, Oct 12, 2012 at 11:39 AM, Mandeville, Rob rmandevi...@litle.comwrote: I’ve been using Jenkins for a couple of years (starting back before the Hudson/Jenkins fork) and it has saved my career on several occasions. However, I’m getting some database envy. I want to be able to read from and write to the database of builds and build results without HTTPing through the server. I’d also like to not have everything in core all the time (the lazy-loading feature in 1.485 was, IMHO, a case of DB envy). What I’d love to see is to have the file-based persistence layer connecting to a JDBC data source, probably shipping with embedded HSQLDB or something by default. ** ** But my question is: is it just me? ** ** I’m using Jenkins in a fairly heavy-duty way (and investigating if we should upgrade to CloudBees Enterprise Edition), and effectively have a separate database, build parser, and build results web site so that we can see results going back several years and query it in multiple ways. I don’t think that I’m your typical Jenkins user. In fact, I can see reasons not to use a DB persistence layer: the files that the Jenkins server keeps for its configuration and logs are pretty human-readable, and having a DB persistence layer would require a DB connection to look at. I also realize that, even if we did want to go to a DB layer, this would be an expensive process that would take resources away from adding more features to Jenkins. ** ** So how many people would like to see a DB layer, how many wouldn’t, and how many don’t care how it keeps its data under the hood? ** ** --Rob Mandeville Litle Co. ** ** The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
remove from group
Re: Real-time log parsing?
You can certainly tail the build log file while the build is in progress; it will be in $JENKINS_HOME/jobs/$JOB_NAME/builds/$BUILD_NUMBER, where $BUILD_NUMBER is the active build. I'm not sure of an easy way to get this number from the command line, you might just have to list the build subdirectories in date order and pick the one at the end. You could probably do it with a system Groovy script as well; I'll take a quick look at that, so let me know if you'd like to pursue this option or if the command line is good enough. On Friday, October 12, 2012 8:25:18 AM UTC-7, Mandeville, Rob wrote: I’m running multi-hour test cycles and my users have a demand for real-time results. If test #50 failed 45 minutes in, they want to be able to see it without waiting five hours for the rest of the tests to run. We’ve had this problem for longer than we’ve had Jenkins, so our solution is to have a log parser separate from Jenkins “tail” the build log, reading it as it’s being written and writing test results to a database powering a non-Jenkins web site. Said process is also reading other auxiliary files (far too many to turn into Jenkins artifacts), so it has to run on the host the slave node and the build are running on, not the machine hosting the Jenkins server. The problem with this is that we have to make sure that everything gets appended to a log file on disk (so the parser can “tail” it) and to standard output (so that we can see it). Accidentally opening the log file for “write” rather than “append” truncates the log and the parser gets lost. Is there a way for a process on the slave node machine to “tail” the build log that Jenkins is getting? Can Jenkins’ output log be replicated in real time in the workspace? Can a groovy JAR be run asynchronously inside the slave as it’s building, and watch the bytes go by? Any other ideas? --Rob The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
Minimal Set of Firewall Exceptions - Instance Hardening
When Jenkins installs on windows it seems to open 'ALL PORTS' for java.exe. Is this actually required? What are the minimal set of ports need by both a slave node and master node. I have the master node configured to communicate with slaves on a fixed port. I assume all I would need is this fixed port open on both slave and master. I also think I should just have open 8080 on the master to be able to access the web ui. -barrett
