Skip to content

Support Windows and OS X #216

Closed
steveklabnik opened this Issue Aug 17, 2011 · 208 comments
@steveklabnik

This will have to be done in steps, so I might break this issue down as support gets closer. Eventually, I'd like to make it such that the yaml file has something like:

os:
  :windowsxp
  :osx
  :linux

Or whatever. So you can build on multiple operating systems as well as just Linux.

This has some interesting issues:

1) licensing
2) availablility
3) combinatorial explosion of rubies and platforms

@thibaudgg

This is something in the pipe? it would be great to test stuff like Guard.

@steveklabnik

Yep, it'll be happening at some point.

@thibaudgg

Awesome :)

@arturadib

Major +1 here!

Perhaps that can be added to the "Future plans (with your help)" section of https://love.travis-ci.org/ ? :)

@thbar
thbar commented Mar 2, 2012

This would be awesome to test out SQLServer related stuff (like what I have on adapter_extensions).

Raw thoughts: maybe a partnership with Microsoft could help provide Windows licenses for open-source projects, while the pro version pricing would include an add-on to support Windows worker?

For SQLServer specifically: there's a Express version which is installed by the sqlserver chef cookbook by default - I believe it would be free to use for that kind of use.

@Adron
Adron commented Mar 3, 2012

I'd bet Microsoft... if the right person could be found, would actually be up for this. They've got a ton of software/services they'll provide for startups and open source related companies for free.

@TooTallNate

👍

@michaelklishin

Both OS X and Windows will be supported one day. We have contacts at both Apple and Microsoft to help make this happen. But it is a non-trivial undertaking. For example, all of our cookbooks will have to be seriously revisited. Doing this in upcoming months means a lot of other features and infrastructure improvements (growing at 40 repos/day does not come effortlessly) that benefit everybody will be seriously affected.

So, 2nd half of the year. No need to +1 more, we hear questions about more OSes and CPU architectures every few days.

@mrdavidlaing

When you guys need extra hands for this one, please ping me.

@henrikhodne
Travis CI member

@michaelklishin Any progress on this? Looks like @mrdavidlaing would like to help out.

@Adron
Adron commented May 22, 2012

Count me in too. I'd love to be able to bring Travis to the OS-X part of the dev world. :) (and the MS side too I'll admit)

@michaelklishin

You should @joshk about who to talk to about figuring out a blank OS X image that runs in VirtualBox. And then we can discuss what to do about the cookbooks.

@henrikhodne
Travis CI member

@michaelklishin I can get OS X running in VirtualBox all right, the problem I think is licensing. OS X is after all a proprietary, commercial OS.

@joshk
Travis CI member
joshk commented May 22, 2012
@bootstraponline

@joshk You should figure out licensing first before using OS X in VirtualBox.

@joshk
Travis CI member
joshk commented May 23, 2012
@kykim
kykim commented May 24, 2012

so, i've spent a good bit of time with this. VirtualBox for OSX does not "behave" as well as VB for Linux. As a result it's difficult to get some of the cookbooks to work properly. i'm not 100% sure we'll ever get to work without a serious investment of development to make OSX a first class citizen of VB.

@joshk
Travis CI member
joshk commented May 24, 2012
@henrikhodne
Travis CI member

I tried working on it yesterday. OS X Snow Leopard Server is supported, but experimental, on VirtualBox. I haven't actually tried it yet, but I will later today.

@kykim
kykim commented May 25, 2012

I can't recall the specific cookbook - but the guest additions for OSX are non-existant, and the mapping of SSH ports from the host env to the guest env seems to "disappear"

@michaelklishin

@kykim guest additions have nothing to do with the cookbooks. So Vagrant was unable to access the VM over SSH? How did you run provisioning in that case?

@kykim
kykim commented May 25, 2012

sorry - wasn't too clear about the real issues.

i was manually stepping through the provisioning steps to get a box that i could start.
then I tried stepping through what the cookbooks would do via vagrant.
neither of each really "worked" well.

in the end, i couldn't automate the provisioning, nor get vagrant to work well (which i suspect is a guest additions issue).

i have some ideas on how to tackle this, which i'll happily discuss offline.

@nicolasmccurdy

👍

@dscape
dscape commented Jul 30, 2012

Any progress here?

This makes it super hard to test windows environments, which normally break based on assumptions developers do about things that exist.

Would be super helpful to know some estimates!

Nuno

@michaelklishin

@dscape no progress. We are up to other things, people who tried running OS X in a VM ran into problems. Porting the entire CI environment to Windows is several months of work.

The estimate is still "some day".

@joshk
Travis CI member
joshk commented Jul 30, 2012
@ncb000gt
ncb000gt commented Aug 3, 2012

👍

@EhevuTov

Combinatorial explosion is a big reason why I use Travis. I'm really looking forward to Windows support.

OS:
  :windows
    :64bit
    :32bit

...would be ideal

@steveklabnik

Sure. I made that comment a year ago; things were very different back then. :)

@EhevuTov

Oh, of course. I didn't mean to come across as criticizing. I love the work you guys are doing. Keep it up!

@joshk
Travis CI member
joshk commented Aug 20, 2012
@lancejpollard

👍

@joshk
Travis CI member
joshk commented Oct 2, 2012
@Adron
Adron commented Oct 2, 2012

Any word and any word on how I could help or contribute back to the effort?

@joshk
Travis CI member
joshk commented Oct 2, 2012
@ericcj
ericcj commented Oct 3, 2012

is the intention to support xcode builds with this?

@joshk
Travis CI member
joshk commented Oct 3, 2012
@jacob-carlborg

It's easy to install Mac OS X using VirtualBox. It's even not very hard to run Mac OS X on regular PC, natively. The only issue is that the Apple EULA doesn't allow this. But if that can be/has been solved then there is no problem.

@joshk
Travis CI member
joshk commented Oct 25, 2012
@ronen ronen referenced this issue in SchemaPlus/schema_plus Oct 26, 2012
Closed

Add support for SQL Server #68

@glennblock

Hey guys

Late to the party, but I work on the team that handles support for node.js in Windows and Azure. I have started a discussion internally to see if we can move forward getting Windows support for Travis.

@svenfuchs
Travis CI member

@glennblock: ❤️

@resurtm resurtm referenced this issue in yiisoft/yii Nov 6, 2012
Closed

Setup Oracle and MSSQL test server #1358

@Adron
Adron commented Nov 6, 2012

Cheers, @glennblock -> as always, lemme know if you guys want me to help on getting bits going. Cheers.

@joshk
Travis CI member
joshk commented Nov 6, 2012
@jacob-carlborg

@joshk that's great to hear, I'm waiting with excitement :)

@staticfloat

@joshk: Loving this, I'm part of a multiplatform project and this is the #1 feature on our wishlist for Travis. Such a great service you guys provide for us all. :)

@berkus
berkus commented Nov 7, 2012

Great CI tool I discovered just today. Would love to see Windows and OSX builds, shoot if you need any specific help with these.

@ZogStriP

@glennblock ❤️

@joshk
Travis CI member
joshk commented Nov 24, 2012
@Adron
Adron commented Nov 28, 2012

Looking forward to consolidating ALL my projects on Travis CI. :) That's gonna be a bad ass blog entry I'm going to love to write up. Plus that'll make by CI soooooo much freaking easier. \m/ \m/

@jperl
jperl commented Dec 14, 2012

@glennblock ❤️

@jakepetroules

We at @axr will be quite excited to take advantage of Windows and OS X support!

@mattheworiordan

+1 for Windows .NET support, that would be excellent

@parndt
@glennblock

@parndt which part?

@parndt
@glennblock
@joshk
Travis CI member
joshk commented Dec 28, 2012
@glennblock

@joshk for WIndows?

I think we (@microsoft) may be able to do something to help with some VMs, at least that's my hope.

@joshk
Travis CI member
joshk commented Dec 28, 2012
@glennblock
@glennblock

@joshk it was great to connect. Let's make this thing move forward!

@fitzchak
fitzchak commented Jan 1, 2013

+1 for Windows .NET support, that would be excellent!

@darvin
darvin commented Jan 7, 2013

+1 for OSX/Xcode support! Is there a way to specify a worker on-premises? cause in such case there is no hurry with licensing and stuff.

@joshk
Travis CI member
joshk commented Jan 8, 2013
@tjordanchat

People are already doing Dot Net development using Travis. git-tfs is one of them using a Mono C Sharp compiler. I would rather see more Open Source work like git-tfs rather than projects building against a private company OS. Richard Stallman in Computer World said "You shouldn't write software to use .NET. No exceptions" http://blogs.computerworlduk.com/open-enterprise/2010/07/richard-stallman-on-net-mono-and-dotgnu/index.htm In other words, no software developed for dot net is truly open source. Stallman does not saying you should not develop for Windows, he says just don't use their environment for development.

@rkh
Travis CI member
rkh commented Jan 11, 2013

In other words, no software developed for dot net is truly open source.

So what?

I smell troll.

@tjordanchat

If Microsoft pays for the effort or if it is made available to Pro users who pay for it then that is fine but the Open Source community's donations were not donated to advance a private, closed source companies interests.

@glennblock

@tjordanchat this is not about Microsoft, this is about folks in the community that are developing OSS modules for Windows, Mac and Linux USING Microsoft technology.

As for Stallman he's entitled to his opinion, and that's all it is.

@vmg
vmg commented Jan 11, 2013

Richard Stallman in Computer World said "You shouldn't write software to use .NET. No exceptions"

Oh well. Then it's all settled then. Hahahahaha.

Seriously, though. There's a lot of people writing great OSS for .NET, including us at GitHub, and these people would love to test their projects with Travis. Get over it and stop trolling.

@glennblock
@tjordanchat

It is a legal issue. I and many others donated to Travis-ci with the understanding that this was for open source. If money is being diverted for private interests than I and many others will have a problem with that. I would not want to give to a charity for the poor and see the money instead being diverted to build golf courses for millionaires.

@glennblock

@tjordanchat this is enabling folks building OSS projects, what is the issue?

@roidrage
Travis CI member

@tjordanchat I can understand your concerns. The thing to keep in mind is that even though Stallman might disagree with that, both Windows and C# are active platforms where open source is built on.

@skottler

Guess what - Stallman isn't always right! There isn't a legal issue here, no one is talking about taking donations and buying Windows licenses; they're talking about helping improve the lives of people people who are building open source software, albeit on a closed platform.

@tjordanchat

With Open Source you can build it from the ground up without paying anybody else. If Windows was free and had it's source published then I would have no problem with Travis-ci using my money for this effort but until then if they do divert donated money to an project which requires the benefactor to purchase Windows, I will be upset and will look into if they can legally use money donated for an Open Source project for projects requiring the purchase of an OS.

@skottler

@tjordanchat where in this thread do you see anyone mention buying Windows or OSX licenses?

@tjordanchat

Anyone who wants to test on Windows OS wants their product to run on the Windows OS. Travis-ci benefits you but then you turn around and sell what you developed using the open source worlds money but then you sell to people running the Windows OS. This is not how money donated for open source causes are meant or permitted to be used. With Mono this is okay because mono also runs on open source OSs. You guys can just follow open source paradigms and develop using tools such as Mono which were made to run on all platforms, including free ones which we have the source to. You can open up your source but that does not make it Open Source.

@paulcbetts

@joshk @rkh I've mentioned this before, but if I can solve any problems on the Windows side, let me know.

@willglynn

@tjordanchat I think you're confusing open source software with free software. Stallman himself wrote "Why 'Free Software' is better than 'Open Source'", from which I quote:

The official definition of “open source software,” as published by the Open Source Initiative, is very close to our definition of free software; however, it is a little looser in some respects, and they have accepted a few licenses that we consider unacceptably restrictive of the users. However, the obvious meaning for the expression “open source software” is “You can look at the source code.” This is a much weaker criterion than free software; it includes free software, but also some proprietary programs, including Xv, and Qt under its original license (before the QPL).

It is perfectly acceptable to for there to be open-source software that only runs on Windows according to the accepted definition of "open source".

@sigmavirus24

@tjordanchat also be well aware that the GPLv{2,3} allow you to sell your product so long as you either ship a copy of the code to the customer, or provide it on their request within a certain amount of time. Of course the customer only has a couple month window to request the code, so after that, you're free to say "We can't provide it.". Just in case you've never read the license.

@tjordanchat

The point is that Microsoft is sending it's developers to use, for free, resources which they can provide themselves but rather mooch off the good will of the open source community. The open source community gave you Mono, for free, and that's not good enough. You want the open source community to pay for a resource for you so that you can develop an application which runs exclusively on a proprietary OS. One in which I would have to pay your hero money for. Yet you want this resource for free but you won't even do us the courtesy of compiling it with Mono so that we can run your software for free, on the platform of "our" choice.

@glennblock

@tjordanchat no one said that. We are ready willing and able to work to make this happen. I am here to start the discussion of what it will take. If people want to help great, but we're not saying that we are not willing to put in the man power.

@joshk
Travis CI member
joshk commented Jan 12, 2013

Wow, this was a pretty amazing thread to wake up to!

As a little update to you guys, we have made amazing progress on getting Travis to run builds on Windows. This was more of a technical challenge than anything else and we will have a guest blog post coming out soon with more info about the progress.

As for Mac builds, we have found an amazing sponsor who is going to provide the hardware and licenses, all that is left is adapting the code to talk to their Mac cloud and run the build. (There are some other tech challenges, but they are quite small as Mac and Linux have enough in common).

I have been very very busy working on the new VM setup and worker code which will help make this all possible, while also eliminating the stupid and painful false timeouts we see in test runs. I am working on the blog post this weekend so I can share with everyone what is going on.

You guys all rock, huge ❤️ ❤️ ❤️ to everyone of you, and a jumping High 5 or two!

Josh

p.s. @xpaulbettsx thanks for the offer, and I am sure we will need it with some recent changes we have made regarding how we will be running the builds. I'll email you and Keno soon with an update.

@tjordanchat

I know from personal experience that when you ask for donations over the internet that you better actually represent what you advertise that you represent. If @joshk means that Pro money will be spent on Microsoft development then that is okay but if same represents that money donated to Travis-ci.org will be diverted towards Microsoft specific interests without any funding for that specific interest other than donations for open source, then I believe that Travis-ci.org will have legal problems.

@paulcbetts

@tjordanchat You've stated the same opinion multiple times in this thread. Please either contribute new information that hasn't been stated previously, or refrain from commenting.

@tjordanchat

@xpaulbettsx, I was responding to @joshk, Chill.

@tjordanchat

New information? okay. Anything you can do on Windows, you can do with Mono. And it will run on any platform. Actually that is not new. That is well known.

@alex
alex commented Jan 12, 2013

"Anything you can do with an operation system, you can do with a language runtime." it's abundantly clear you have no idea what you're talking about.

@tjordanchat

@alex the instruction set on a microprocessor is not different than a language. Languages are an effort of portability amongst hardware platforms in addition to a short hand way of declaring your intent. Windows is a proprietary OS owned by Bill Gates. The C programming language is not owned by Bill Gates. Windows is though. Point being that C compiles on all platforms.

@alax
alax commented Jan 12, 2013

@tjordanchat I think you meant to reference @alex. You referenced me instead (I am @alax).

@joshk
Travis CI member
joshk commented Jan 12, 2013

Hey Guys,

Lets keep the discussion in here as civil as possible as I feel its going a little off topic and maybe getting a little heated :)

@tjordanchat I am sorry you do not feel that supporting the open source communities which use .Net or Microsoft platforms, or Objective-C or Mac platforms, as being worthwhile.

We at Travis believe every open source user should be able to use Travis to test their code. Of course, that's easier said than done :)

I know @tjordanchat that you point to using Mono to test .Net code or Windows libs on, but I think you have forgotten a very important point of Travis and CI in general, we make it easier to test against hardware your users actually use. For example, ever had one of those issues that code passes locally but not on Travis? That's because slight changes in Archs, or how file systems are treated, or case sensitivity, or a whole raft of issues can lead to you finding bugs which you may not normally encounter. That's why we want to help people test on 32bit and 64bit Archs in the future, or testing your ruby or node app on Linux and Windows, as some people do deploy to different archs and OS's, including Windows, and is the main reason why you may want to make sure your library works their too.

Instead of going on for paragraphs why supporting Mac and Windows is a good thing to do, I think we need to blog about it instead! :)

I did want to touch upon the legal issues regarding donations for a second. Can I ask, did you donate? And if you did, how much was it and what did you want that money to go towards? How about people who did donate because they wanted us to support Windows and Mac testing, do you think they mind we spent some of the donated money towards spending time emailing companies to find sponsors for other OS support?

I can confirm we have spent NO money on hardware or licenses. Also, a person who has helped push Windows support forward does not work for Travis but works on the JuliaLang project and has been helping us because he wants to test JuliaLang on Windows on Travis. That is pretty awesome for someone from the community to help us like that if I do say so myself!

If anyone has any further questions or issues regarding some of these issues, please feel free to contact support@travis-ci.org.

From here on in, let's try to keep this thread focused and related to supporting the OSS communities who want to test their libs and projects and code on Mac and Windows environments.

❤️ ❤️ ❤️

Josh

@tjordanchat

I do not. I did not donate money here for the well to do. I believed that I was deceived in giving my donation as I was assured that my donation was not to be used for private interests. I believe that I deserve a refund, as this site is not Open Source certified and I will be seeking a refund of the money that I gave to Travis-ci.org, no matter what it takes. Because it is right.

@joshk
Travis CI member
joshk commented Jan 12, 2013

Hi Tim,

When the Love Campaign launched we promised to work on four big ticket items: private build support, pre-tested pull requests, build artifacts, and more languages. You can find these goals listed on the love website here : http://love.travis-ci.org. We have delivered on each one of these items, and are continuing to deliver more awesome everyday. :)

We are a small bootstrapped open source company providing a free service to open source users, it is a bit sad you don't see the value in what we have provided or delivered.

Although .Net and Objective C support falls under the 'moar languages' item, and we have no legal obligation to refund your donation, I am going to make an exception this once.

I tried searching for your donation on the Love site but could not find it. Can you please confirm how much you donated, what date you donated, and the email address you entered so I can find it in Stripe.

Tim, you will always be free to use Travis for your open source testing, and one day I hope you see value in testing on all Archs and OSs.

Josh

@tjordanchat

Sweet talk @joshk but legally you can not divert money intended for free open source projects towards proprietary systems.

@roidrage
Travis CI member

@tjordanchat if you could let us know the details of your donation, feel free to mail us (support@travis-ci.org), and I'll issue a refund right away.

Thank you for bringing up this discussion, and for voicing your opinion. If you're not happy with how the money you've donated is used, you definitely deserve to have it refunded.

@nima
nima commented Jan 30, 2014

Any update on supporting multiple OSes in a single `.travis.yml'? Would be great to have a "common" section or some other means that would allow for eliminating repetition, for example:

os: linux
...
---
os: osx
...
---
os: [osx, windows]
...

👍

@rkh
Travis CI member
rkh commented Jan 30, 2014

We will roll out multi-os support soon. Technically, our VM setup already supports it, but our Mac VMs still lack a lot of software for different programming languages. Also, we need to increase the number of Mac VMs.

@leviwilson
@nima
nima commented Jan 30, 2014

@rkh - very awesome news!

@thibaudgg

@rkh 😍

@Adron
Adron commented Jan 30, 2014

:) +1

@redteam316

+1 for multi-os support.

I have been playing around with travis lately and the biggest problem currently is that when pushing to different branches, sometimes travis-ci.org doesn't seem to do a new build and maybe the service hook doesn't send the changes(I think this is the cause of several bug reports saying the image doesn't update, even when refreshing and clearing the browser cache). A perfect solution would be to have a single .travis.yml in the master branch of a repo and always send any pushes to the master branch.

I think Travis-CI really shows potential and I'm excited about multi-os support.

@FeodorFitsner

While Travis team is working hard to add Windows support you might want to check out AppVeyor CI 2.0 - dedicated build VMs, parallel testing, built-in deployment to multiple environments, NuGet hosting, YAML configs. There is free plan for projects with public repositories.

I'm the developer of this service.

@beatspaul

+1 for Windows build support

@tnachen
tnachen commented Feb 27, 2014

+1 here from Apache Drill project

@stevenvachon

Still waiting for Windows support. Thank you.

@JamesMGreene

Any updates? We would love to see this for cross-platform PhantomJS CI build verifications.

cc: @ariya @detro @Vitallium

@mcandre
mcandre commented Mar 10, 2014

+1

@Pro
Pro commented Mar 10, 2014

👍

@Jorge-C Jorge-C referenced this issue in biocore/scikit-bio Mar 17, 2014
Closed

setup Travis to test against OS X #184

@ElDeveloper

👍

@henrikhodne henrikhodne changed the title from Support Windows and Mac OSX. to Support Windows and OS X Mar 17, 2014
@akashivskyy

👍, I would like to test my PHP project which requires to be run on OS X.

@leviwilson
@akashivskyy

Yeah, but how can I tell Travis to test my PHP project against 5.5, 5.4, hhvm on a Mac?

@leviwilson

Just noting they have OSX. If it doesn't come pre-baked with what you need, you can use the build lifecycle to setup what you need.

@BanzaiMan
Travis CI member

Currently, Objective-C projects (and only Objective-C projects) run on Mac VMs.

@jsdevel jsdevel referenced this issue in joeferner/node-java Apr 3, 2014
Closed

Installation needs a flying V. Mighty Ducks style. #111

@jsdevel
jsdevel commented Apr 3, 2014

+1. Windows and Mac support is highly needed.

@Alxandr
Alxandr commented Apr 3, 2014

I'm currently watching the keynote from day 2 of the MS Build conference, and they're talking about azure's new capability to stamp out machines as wanted from an preexisting image. Doesn't this sound a lot like what's needed to run travis on windows? Maybe see if getting a deal with Microsoft (I think I read something about them wanting to support earlier in this thread).

Just a thought though.

@utensil
utensil commented Apr 5, 2014

+1. OSX support for non Objective-C projects is needed, so is multi-OS configuration in a single .travis.yml and in a single branch.

@jescalan

+1

@adri
adri commented Apr 12, 2014

+1

@fxlb
fxlb commented Apr 12, 2014
@jbtule
jbtule commented Apr 14, 2014

+1 is not helpful, it makes people who are interested in following the issue unsubscribe because of all the spam. Instead of +1 just click subscribe at the top. Thanks.

@ErikSchierboom

Hopefully you'll manage to pull this off! Good luck.

@zcbenz zcbenz referenced this issue in electron/electron May 6, 2014
Closed

Setup CI for Linux and Windows #190

@tedivm
tedivm commented May 7, 2014

+1

This would make my life so much easier. There are a few windows specific pieces of functionality in my code base that I'd really like to have tested here.

@JamesMGreene

OS X is now supported

:metal:

Half the battle. Now on to Windows.... 👍

@stormbrew

Awesome. Is there a way to scope pre-/post-install tasks so they can be brew on osx and apt-get on linux?

@jacob-carlborg

This is great news, awesome 😃

@nulltoken

Is there a way to scope pre-/post-install tasks so they can be brew on osx and apt-get on linux?

@stormbrew See https://github.com/libgit2/libgit2sharp/blob/vNext/.travis.yml which does just this

@stormbrew

@nulltoken yeah that mechanism had occurred to me, and it's ok. I was hoping for a more structured approach, but this is roughly what I'll end up doing if there isn't one.

@tedivm
tedivm commented May 13, 2014

Is there a way to add an OS to the allowed failures list?

@roidrage
Travis CI member

@tedivm there currently isn't.

@JamesMGreene

I would agree with @stormbrew, that mechanism doesn't seem very maintainable, especially when Windows gets added as the syntax will be different (unless using a Bash shell emulator like Cygwn/Msysgit/etc.).

I was expecting something more build-matrix-esque:

before_install:
 - windows:
    - .\CI\windows\travis.install.deps.bat
 - mac:
    - ./CI/mac/travis.install.deps.sh
 - linux:
    - ./CI/linux/travis.install.deps.sh
@roidrage
Travis CI member

@JamesMGreene we're at the early stages of supporting multiple operations systems, so your expectations may eventually be fulfilled.

@JamesMGreene

Duly noted, @roidrage, and very excited for things to come. 👍 ❤️

@BanzaiMan
Travis CI member

@tedivm @roidrage

matrix:
  allow_failures:
    - os: osx

should categorically allow failures on any job on OS X workers.

@tedivm
tedivm commented May 14, 2014

Awesome 👍

I'm really excited about this, particularly for one of my projects which has to deal with a lot of cross compatibility issues.

@myint
myint commented May 15, 2014

OS X testing isn't working for me. It looks like Travis just ignores my os block.

https://travis-ci.org/myint-test-org/test-osx

So I tried forking an existing project that Travis does test on OS X and Linux.

https://travis-ci.org/pyca/cryptography

But when I run my fork on Travis using their exact .travis.yml, Travis still does not run on OS X. See how my build matrix compares. It is missing the "OS" coolumn.

https://travis-ci.org/myint/cryptography/builds/25239850

@fxlb
fxlb commented May 15, 2014

If you want the feature turned on for your repository, get in touch with the Travis support via email at support@travis-ci.com.

@rkh
Travis CI member
rkh commented May 15, 2014

@BanzaiMan Maybe we should output a warning if you specify OS but aren't feature flagged.

@simi
simi commented May 15, 2014

👍 @rkh. Any ideas how to implement it? Output it in build log as a warning similar to projects, where .travis.yml is not present?

@rkh
Travis CI member
rkh commented May 15, 2014

👍 @rkh. Any ideas how to implement it? Output it in build log as a warning similar to projects, where .travis.yml is not present?

Yes, something like that. I'm not sure if we remove the os section from the payload if the repo is not feature flagged or if we silently hand it on to travis-build.

@fxlb
fxlb commented May 15, 2014

At present, when the feature is 'off', the TRAVIS_OS_NAME env variable is void.
Anyway to have it set to 'linux' to have same script usable with feature 'on' and feature 'off' ?
(e.g. - if [ "$TRAVIS_OS_NAME" = linux ]; then ......)

@rkh
Travis CI member
rkh commented May 15, 2014

As a work around, you can use uname.

@fxlb
fxlb commented May 15, 2014

Thanks, uname is OK for now.
But for future, I think TRAVIS_OS_NAME is better.

@BanzaiMan
Travis CI member

We should retain everything in the payload, including os. We just ignore it when expanding the build matrix if the feature is not available to the repository.

@stormbrew

For a slightly less noisy version of @nulltoken's approach to using having differing pre-install steps on osx vs. linux, this is how I'm doing it: stormbrew/channel9@9bab83e

This probably won't work when windows support comes along, though.

@fxlb
fxlb commented May 16, 2014

Now gcc command is not the GNU gcc:

$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 5.1 (clang-503.0.38) (based on LLVM 3.4svn)
Target: x86_64-apple-darwin13.1.0
Thread model: posix

Is there a plan to have GNU gcc native in builder ?

@roidrage
Travis CI member

@fxlb gcc is installed via Xcode, which now defaults to clang. You'll find gcc in /usr/local/bin by way of the gcc-4.2 package.

@fxlb
fxlb commented May 16, 2014

thanks, but gcc 4.2 is rather old.
brew install gcc give gcc 4.8.2.
Could we have this version in the builder ?

@roidrage
Travis CI member

You can install it yourself by way of brew update && brew install gcc

@roidrage
Travis CI member

As this thread is already quite large, please file any support requests as separate tickets.

@robrich
robrich commented Jun 12, 2014

+1

@henrikhodne henrikhodne locked and limited conversation to collaborators Jun 12, 2014
@meeh420 meeh420 added a commit to PurpleI2P/i2pd that referenced this issue Jul 14, 2014
@meeh420 meeh420 Trying the multi section setting. 3957717
@marutosi marutosi added a commit to marutosi/openproject that referenced this issue Nov 17, 2014
@marutosi marutosi use linux and osx at .travis.yml 6505138
@marutosi marutosi added a commit to marutosi/openproject that referenced this issue Apr 28, 2015
@marutosi marutosi use linux and osx at .travis.yml 8bd6fe5
@roidrage
Travis CI member

I'm closing this issue as we do have Mac support available. As for Windows, we do have ideas on it, and once we know more, we'll update this ticket.

@roidrage roidrage closed this Jul 23, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Something went wrong with that request. Please try again.