Don't let your butler skip leg day.
https://www.cloudbees.com/node?qt-homepage_tab_carousel=1#qt-homepage_tab_carousel
Also who's pumped for Jenkins 2.0?
>>51832829
>docker
>>51832829
We use Jenkins at my work. Intern so I don't get too much exposure to it. I know that it can be used as a frontend for doing a whole bunch of shit on Linux VMs, but what else is it good for?
>>51832929
Basically, Docker is meant to make it so that you can have easily recreatable and isolated Linux environments. With normal Jenkins the server may be configured to use a certain version of a compiler, while the developer uses another version. Some code might compile on the developer's computer but not on the server because of differences between versions. Docker eliminates this by making it so that everyone know what compiler version to write code for, and allows them to test using the same configuration that the server is using. Docker gets rid of "works on my machine!" since everyone is running and developing for the same "machine."
>>51833102
>>51832929
pretty sure travis CI can already do this
>>51833128
It does, and I use Travis for a lot of my projects. Jenkins is nice for:
* Building other peoples software
* Not paying $100+ per month for private repositories
* Triggering jobs with stuff other than Git commits
* Doing tasks other than building software
>>51833283
i didnt know travis ci only supported github. Makes little sense to me
>>51833283
>Travis
>using SaaS
Absolutely disgusting
>>51833102
>everyone is running and developing for the same "machine."
This is why I think docker is disgusting - packing everything in to an unmanageable box isn't fixing the problem, it's just ignoring them. We already had this with virtual machines, they're called appliances and they're considered shit for a reason.
>>51833400
containers =! vm/appliances
>>51833489
I have nothing against containers, but docker is the same shit as appliances with the same problems.
>>51833529
its not
