Hi all, just a little clarification to prevent potential confusion why some branches and pull requests are built by Travis and others aren't. The branch/PR must contain the .travis.yml file and building for the repository containing that branch has to be enabled in Travis (by the repository owner).
Since we did that for the official DSpace/DSpace repository over the last few days, it means that any branches forked and pull requests opened before that time (or based on those older commits) will not build automatically. The solution if you want to build your branches is to either a) create them from current master or b) rebase them on current master, so they will already contain .travis.yml. Do not add .travis.yml on top of an already existing branch that you want us to pull - that would create a conflict, because master already contains .travis.yml. I hope that made things more clear, not less :) If in doubt, don't hesitate to ask. P.S. Should you request Travis to build a branch without a .travis.yml file, you would see a build failure. That's because Travis supports more languages than just Java and the default is Ruby. Since there is no rakefile, the build will fail. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
