A description of what's happening on Jenkins

[Daniel Lee]

I put it up on a wiki. I'm going to sit with Bob (with additional help!) on Thursday to work through making it more stable.

https://github.com/stan-dev/stan/wiki/Jenkins

These are really my notes as some form of an inventory for Thursday, but if anyone sees some way to make it clearer / needs more info, please ask.

Daniel

[Bob Carpenter]

Thanks for documenting this.

Andrew should blog this if people want to see how the sausage
is really made! It's quite startling to me to see this all laid
out end to end with the tests and equipment. We should include
this in our IES grant report, too, as they paid for the x-platform
testbed, which has served us really well.

I don't think we need to encrypt anything.

+1 to better notification --- that "no test results found" thing
is rattling.

For upstream branch control, would that be something along
the lines of "Jenkins, a's upstream branch is b" or some
other invocation? I've never had to deal with this, but we
want to make it easy, especially as we head into the big
refactor.

You can see from the daily performance reports that there
are funny outliers presumably not due to our software changing
but due to hardware/network issues. This we can just deal with
by eye and perhaps rerunning if we're worried.

- Bob

P.S. Favorite piece of equipment: Andrew's broken laptop

> --
> You received this message because you are subscribed to the Google Groups "stan development mailing list" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.