[BIOSAL] Travis CI based build/test in GitHub

[Boisvert, Sebastien]

> From: George K. Thiruvathukal [gkt at cs.luc.edu]
> Sent: Saturday, November 08, 2014 10:27 PM
> To: Boisvert, Sebastien
> Cc: biosal at lists.cels.anl.gov
> Subject: Re: [BIOSAL] Travis CI based build/test in GitHub
> 
> 
> 
> 
> Alright, I think all went according to plan!
> 
> 
> I updated the table with a new heading "Travis Build Status". I believe you can change this entry

I merged it master.

Note: you should have done this using 2 distinct commits (I know, I am nitpicky).


> 
> 
> [![Build Status](https://travis-ci.org/gkthiruvathukal/biosal.svg?branch=granularity)](https://travis-ci.org/gkthiruvathukal/biosal)
> 
> 
> to
> 
> [![Build Status](https://travis-ci.org/sebhtml/biosal.svg?branch=energy)](https://travis-ci.org/sebhtml/biosal)
> 
> 
> if you want to add your branch's build status to the table.
> 
> Might not hurt to put the overall "master" build status at the top of page as before.
> 

I would use the jenkins build since it runs unit-tests, example-tests, and application-tests.

> [![Build Status](https://travis-ci.org/sebhtml/biosal.svg?branch=master)](https://travis-ci.org/sebhtml/biosal)
> 
> 
> The key thing to remember is that you need to enable Travis for each of the GitHub projects/forks. Travis automagically finds the branch that changed when triggering a
>  build.
> 

OK thanks

> George
> 
> 
> 
> 
> 
> 
> George K. Thiruvathukal, PhD
> 
> Professor of Computer Science, Loyola University Chicago
> 
> Director, Center for Textual Studies and Digital Humanities
> Guest Faculty, Argonne National Laboratory, Math and Computer Science Division
> Editor in Chief, Computing in
>  Science and Engineering (IEEE CS/AIP)
> 
> (w) gkt.tv (v)
>  773.829.4872
> 
> 
> 
> 
> 
> 
> 
> On Sat, Nov 8, 2014 at 9:49 PM, George K. Thiruvathukal 
> <gkt at cs.luc.edu> wrote:
> 
> 
> Yes! I will notify you when all is done!
> 
> George
> 
> 
> 
> 
> 
> George K. Thiruvathukal, PhD
> 
> Professor of Computer Science, Loyola University Chicago
> 
> Director, Center for Textual Studies and Digital Humanities
> Guest Faculty, Argonne National Laboratory, Math and Computer Science Division
> Editor in Chief, Computing in
>  Science and Engineering (IEEE CS/AIP)
> 
> (w) gkt.tv (v)
>  773.829.4872
> 
> 
> 
> 
> 
> 
> 
> 
> On Sat, Nov 8, 2014 at 9:19 PM, Boisvert, Sebastien 
> <boisvert at anl.gov> wrote:
> 
> I merged your branch.
> 
> Can you move the build status in the branch tables (you could put it after
> "granularity" in the table "Branches" in the README).
> 
> > From: George K. Thiruvathukal [gkt at cs.luc.edu]
> > Sent: Saturday, November 08, 2014 8:46 PM
> > To: Boisvert, Sebastien
> > Cc: 
> biosal at lists.cels.anl.gov
> > Subject: Re: [BIOSAL] Travis CI based build/test in GitHub
> 
> >
> >
> >
> >
> > ​Seb,
> >
> > I just realized that the top-level message probably should be "biosal". Sorry! I sometimes think of biosal and thorium as the same thing, even though they're not! :)
> >
> >
> > I'll work on the ​answer to the junit.xml question. It's not clear to me that Travis supports all of these things yet, especially for visualizing the tests. I'm guessing it will be supported at some point soon though.
> >
> >
> >
> > Do you want me to amend the commit messages in some way, or can we live with a small amount of imperfection?
> >
> >
> > George
> >
> >
> >
> > George K. Thiruvathukal, PhD
> >
> > Professor of Computer Science, Loyola University Chicago
> >
> > Director, Center for Textual Studies and Digital Humanities
> > Guest Faculty, Argonne National Laboratory, Math and Computer Science Division
> > Editor in Chief, Computing in
> >  Science and Engineering (IEEE CS/AIP)
> >
> > (w) 
> gkt.tv (v)
> >  773.829.4872
> >
> >
> >
> >
> >
> >
> >
> > On Sat, Nov 8, 2014 at 8:05 PM, Boisvert, Sebastien
> > <boisvert at anl.gov> wrote:
> >
> > Can you tell Travis-CI to pick up the JUnit XML files (*/*.junit.xml) so that it shows the results ?
> >
> > > From:
> > 
> biosal-bounces at lists.cels.anl.gov [biosal-bounces at lists.cels.anl.gov] on behalf of George
> >  K. Thiruvathukal [gkt at cs.luc.edu]
> > > Sent: Saturday, November 08, 2014 5:53 PM
> > > To:
> > 
> biosal at lists.cels.anl.gov
> > > Subject: [BIOSAL] Travis CI based build/test in GitHub
> > >
> > >
> > >
> > >
> >
> > > Hi,
> > >
> > >
> > > There is separate value to doing build/test automation using the hosted Jenkins setup at ANL, so I started a new thread for something that is directly supported by GitHub and fully cloud hosted. It is a bit of a coincidence that Seb and I were both thinking
> > >  about testing today, so I don't want to mess up the thread he opened up on Jenkins builds. (I was starting to do it for another project and said, why not try it for Thorium/Biosal, too?)
> > >
> > >
> > > On my "granularlity" branch, I have done a similar proof-of-concept to Seb's incredible work on the Jenkins side. The notable difference is that this is using the hosted Travis CI solution. So to be similar to Seb's earlier posting today, here is a bit
>  about
> > >  the demo I have put together:
> > >
> > >
> > > build:
> > 
> https://travis-ci.org/gkthiruvathukal/biosal (Build History tab)
> > >
> > >
> > > console:
> > 
> https://travis-ci.org/gkthiruvathukal/biosal (Console tab)
> > >
> > >
> > > tests:
> > 
> https://travis-ci.org/gkthiruvathukal/biosal (Console tab)
> > >
> > >
> > > doc:
> > 
> https://github.com/gkthiruvathukal/biosal/tree/granularity
> > >
> > >
> > > One this last one (doc), note that you can see whether the build succeeded and the tests passed. I integrated this with the README.md page (just scroll down).
> > >
> > >
> > > It's basically all present in one place but incredibly easy to understand the results. I especially like the colorized console output, which I know is one of Seb's favorite features as he always reminds me to use a proper editor and enable colors! :-)
> > >
> > >
> > > I will be writing up some notes about the overall approach, but you can look at .travis.yml (top level), which is what triggers the build/test scenario above. I don't think this is in competition with your Jenkins work, because Travis doesn't have as much
> >  biodiversity
> > >  when it comes to the node types supported. At some point, however, we might want to see whether we can add some nodes to the setup being used by Travis, which apparently relies on contributed build boxes.
> > >
> > >
> > > Best,
> > > George
> > >
> > >
> > >
> > >
> > >
> > >
> > > George K. Thiruvathukal, PhD
> > >
> > > Professor of Computer Science, Loyola University Chicago
> > >
> > > Director, Center for Textual Studies and Digital Humanities
> > > Guest Faculty, Argonne National Laboratory, Math and Computer Science Division
> > > Editor in Chief, Computing in
> > >  Science and Engineering (IEEE CS/AIP)
> > >
> > > (w)
> > 
> gkt.tv (v)
> > >  773.829.4872
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> 
> 
> 
> 
> 
> 
> 
> 
>