> I'd like to integrate the new BroControl and BTests test suites into > the Jenkins runs, what's the best way to do that?
Since the BTest tests don't depend on Bro at all, it's probably best to set up a new job that polls the btest master branch for changes directly and then runs the test suite. For BroControl tests, I think maybe it should be in a new job that's triggered from the UpdateRepos job (alongside the Compile* jobs). > Is Jenkins triggering the tests via "make test" or in some other way? Another way. > Also, I'm thinking we should switch Jenkins to use btest's brief output so > that > it skips all the "ok" tests in its mails for brevity. Makes sense. Does that still show "skipped" tests? I think that may have been a reason for the more verbose output -- I wanted to know whether tests were passing versus just being skipped. > Maybe be could create separate target "jenkins" for running the tests there? Don't think we need something like that. Did you want to play around with making changes to the Jenkins config? Else I'll try to get BroControl/BTest stuff added sometime this week. - Jon _______________________________________________ bro-dev mailing list [email protected] http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
