Pandora Apps Download For Mac
2021年5月26日Download here: http://gg.gg/uqbwt
*Even if you don’t subscribe to Pandora One, Hermes is and always will be open source and free for everyone. Usable Hermes pauses music when your computer sleeps and doesn’t resume on wake.
*Pandora announced todaythat the Pandora desktop app for macOS is now available to download, giving you full-featured access to the streaming service.
*Pandora One Desktop App for Mac, free and safe download. Pandora One Desktop App latest version: Discover new music from your desktop.
May 20, 2019 Pandora today launched a new desktop app for Mac, aimed at all Pandora listeners across both its free and paid tiers. Similar to its mobile apps, Pandora for Mac allows for full access to Pandora. Best Alarm App For Mac Book 2016 Canon Mx300 software, free download For Mac. Pandora App For Mac Laptop. Click on the button below to start downloading DaVinci Resolve Studio 16.0.0 for mac OS X. We are here to provide to clean and fast download for DaVinci Resolve Studio 16. This link is resume able within 24 hours.
Best Alarm App For Mac Book 2016 Canon Mx300 software, free download For Mac. Pandora App For Mac Laptop. Click on the button below to start downloading DaVinci Resolve Studio 16.0.0 for mac OS X. We are here to provide to clean and fast download for DaVinci Resolve Studio 16. This link is resume able within 24 hours. Play the songs, albums, playlists and podcasts you love on the all-new Pandora. Explore subscription plans to stream ad-free and on-demand. Listen on your mobile phone, desktop, TV.Alarm Clock Editor’s Review
Create alarms for your Mac with this handy utility.
One of the biggest things that people – me – do with their computers is keep track of their schedules. I know I’m pretty anal retentive about my calendar. I also know that I can often get lost in my writing when I’ve got a good topic I’m writing about. Its at times like this, that I’m glad that there are applications like Alarm Clock. It’s a Mac app that will help you remember key events and deadlines.
Alarm Clock is a menu item alarm clock for setting either one-time alarms or repeating alarms. Then choose anything in the iTunes library to wake to: songs, playlists, even podcasts. The application takes care of the rest, even waking the computer from sleep if needed.
You can configure your snooze duration to the length you want. You can even increase/decrease your snooze time right from the alarm window. Plus, if you have an apple remote, you can hit snooze without getting out of bed. If waking up to blaring alarms in the morning isn’t your cup of tea, there’s an ’easy wake’ option that gradually increases the alarm volume over time. All of the settings are end user configurable.
App Pro’s: Easy to use, FreePandora App Download For Macbook Pro
App Con’s: Functionality is limited to alarms and a stopwatch
Conclusion: Alarm Clock is a simple program, but what it does, it does very well. This is key system functionality that I haven’t been able to find in this configuration in OS X, even with Reminders; and I’m glad that this app has found its way to my hard drive. I’m certain you’ll like the app as well. The price is certainly right.
MacStadium recently hosted a panel on CI best practices at AltConf, which runs in parallel to Apple’s WWDC and is specifically focused on the Apple app development community. The panelists included: Daniel Hagen, Director of IT for Aspyr Media, publisher of popular Mac games like Call of Duty®, Sid Meier’s Civilization® and SimCity™; Debayan Majumdar, Sr. Mobile Tools Engineer at Pandora, the largest streaming music provider in the US; and Peter Steinberger, CEO of PSPDFKit, the go-to solution for integrating PDFs into your app. It was an interesting discussion as the companies represent very different development teams and CI practices. However, the experiences of these diverse teams did have a few common points.
The group was in agreement that a ’commit often’ culture was the most effective approach to get working apps written, and all three loved TestFlight. There was agreement on using Jenkins if you need a flexible deployment tool; however, this is where the first difference started – PSPDFKit no longer uses Jenkins as their primary CD tool, they have opted to move from Jenkins to BuildKite for ease of use. The relatively small shop values the labor savings, but still uses Jenkins to launch its TestFlight jobs.
Automated testing was the best practice, but how it was implemented varied. Being a game developer, Aspyr had the most limited set of automated testing. Pandora did not weigh in during the panel, but afterwards discussed testing with MacStadium and agreed automating this was vital – they use extensive automated tests for regression testing and basic pipeline CI as developers do commits. PSPDFKit not only uses their MacStadium infrastructure to test iOS code, but also Android code! Peter even commented that, ’the Android simulator, I don’t know if the conference allows swear words, but it sucks. Sorry.’
As is best practice, each organization uses a known good image to base all of their machines off of, but they differed on their implementation method. Aspyr uses Golden Images and Instant Cloning (a vSphere and Jenkins feature) to produce new machines, then updates their Golden Images about once a week. Pandora uses an Anka template as its golden image, and does updates to all their templates with Ansible as needed. PSPDFKit prefers a bare-metal approach, as this reduces technical debt, and again speaks to their team prioritizing ease of use. When a node gives unexpected results, they do a full system reset, then load Chef to return all packages to the desired state. (This takes about four hours.)
Watch the video of the panel discussion for more best practice configurations, favorite automation tricks, and other lessons learned:
Or read on for a transcribed version:
Speakers:
Shawn Lankton, Chief Revenue Officer, MacStadium
Peter Steinberger, Founder & CEO, PSPDFKit
Daniel Hagen, Director of IT, Aspyr Media
Debayan Majumdar, Technical Team Lead, Mobile Tools, Pandora/SiriusXM
Shawn:
We’ve got three great guests with us here today who are going to be doing most of the talking. I’ll let them introduce themselves quickly. Peter, do you want to start?
Peter:
My name is Peter. I work on PSPDFKit; I’m the founder. We are in Dropbox and IBM and Lufthansa, we’re like an SDK that shows PDF on all platforms, not just iOS, but we come from the iOS world and it’s still our most important market. Yeah, CI is very important for us. Like every pull request runs all the platforms automated, and we are happy partner of MacStadium.
Dan:
Hey everyone. My name is Daniel Hagen. I’m the director of IT for Aspyr Media. We are known as the world’s largest Mac publisher of video games. So many of you probably have played a few of ours, hopefully. Yeah, anything from Civilization to Call of Duty to Sims. We’ve played around with a lot of the good games. My background comes from web development. So CI/CD to me is a lot of automated pipelines, automated testing, automated unit tests, that sort of thing. So bring that into a thick client world has been an interesting endeavor. And working with development teams that come from -- probably a little bit stuck in the 1980s -- has been an endeavor of its own. So it’s been a lot of fun to bring that about and make things happen a lot faster and a lot quicker.
Debayan:
My name is Debayan and I lead the Mobile Tools Team at Pandora/SiriusXM now. So for those of you who don’t know, SiriusXM recently acquired Pandora, which makes us the largest music streaming company in the US. We have over 100 million monthly active users. You can imagine the scale at which we have to run our things.
Debayan:
I was actually the first mobile tools engineer or the first DevOps engineer at Pandora. So I can say that we have come a very long way and it’s been a great arduous journey not only building out the CI infrastructure, but just changing the culture and kind of bringing in a DevOps mindset that allows us to scale. I think that has been a very challenging journey and very enriching journey as well.
Shawn:
Thanks. I wanted to just give a few words about what continuous integration is. I think probably everybody in this room came because they already know, but spend two seconds on it. Also, I’m Shawn Lankton. I work at MacStadium. I lead our sales and marketing teams and spend a lot of time thinking about how to make sure that everybody knows what’s out there, how to use it so that we can help them.
Shawn:
Continuous integration is basically part of the DevOps workflow. It really focuses in on the build and test portions. The idea is that you’re going to run a build every time you merge code with a pull request. You’re going to test every time you build. It helps you catch errors faster and brings the faster time to value by shifting things left so you catch them sooner.
Shawn:
Of course, again, as I’m sure you all know, when you do this for the Apple ecosystem, you have to do all your builds and a lot of your tests using Xcode. Xcode only runs on macOS. macOS only runs on genuine Apple hardware, which means you have to find some way to get it and deploy it at scale. Once you have it deployed, you have to automate it, and a lot of the tricks that DevOps teams use for every other platform will not work for macOS. That’s why we have a packed house at 4:00 in the afternoon.
Shawn:
MacStadium helps. In case you’re not familiar, we have data centers around the world. We have about 20,000 Macs deployed in our data centers and we’re buying them pretty much as fast as we can. We have Mac minis, Mac Pros, we have iMac Pros deployed and we work with all of the different virtualization technologies, whether it’s VMware, Anka, or Orka, which we are just announcing this week. If you’d like to learn more about how to use Kubernetes to orchestrate Mac VMs, come talk to us at our booth anytime throughout the week. But I won’t get into that now.
Shawn:
We’re also of course very excited about rack mounted Mac Pros and what the future may hold for that. The fall ends on December 20th in case anybody hadn’t checked their calendar. So we’ll see when that actually ships.
Shawn:
That’s enough about context. I want to spend the rest of the time here talking with these guys about some of their experiences on these topics. We’ll get started. You’ve heard a bit about who they are and what the companies are. But I think it makes a lot of sense to start by understanding what are the end points that these guys are targeting, how are their teams structured, and what are their end users expecting to find in an app. So take it away.
Peter:
Sure. So I probably represent the smaller company side here. We have like two other giants in the room. For us, the important part is, it needs to be very cost effective, it needs to be simple to administer, and of course it should be fast and good.
Peter:
Obviously we need Mac hardware to run our Mac tests. And we also want to use Mac hardware to build Mac software. We started using Jenkins very early on. Since we are like eight years in or seven years in, everybody hates it, but it gets the job done. We’re now having a project to migrate to Buildkite because we slowly see that Jenkins doesn’t really scale well. When you update the plugin, all the jobs need to stop and then Jenkins needs to restart. And then you have to hope that it boots up again because if the plugin update failed then you’ll just get an error and you have to like manually undo it and it’s very, very messy.
Peter:
But there’s a lot of those problems you can live with so I think it’s a decent choice if you look at the options out there. For us it now makes sense to move to a little bit of a better and also more expensive system. Setup wise, we started with iOS. So very early on we wanted to have hosted Macs via a remote company so there is no real office, meaning there’s also no real data center. For a while I had Mac minis at my home and then the cleaning lady unplugged them, which is not really professional and it’s also kind of annoying. So having those things in an actual data center is nice.
Peter:
There’s not that many companies out there where you can actually do that. So you can do your own research. I did, and that’s why I chose MacStadium. So this is may be a marketing plug, but I don’t get any affiliation. They are very good to work with. We looked at the different products. I mean they have like Mac Pros and Xserves as well. Do they still exist?
Shawn:
They still exist. Not many people use them anymore.
Peter:
So we chose the simplest set up possible again because our set up needs to be cost effective. It was just Mac minis. One Mac mini for one user doing one test at a time or sometimes two.
Peter:
In the very early days we set them up manually, just VNC in and like you have someone doing a lot of clicking. That gets annoying very quickly. So don’t do that. We did invest a lot of time in Ansible and automating everything. Once we’re like at 95% done, we found out that Microsoft maintains a really, really good Chef repository with like a cookbook. So you can basically pick what you want from like installing Xcode to a lot more esoteric things.
Peter:
We use Mac minis to not only test iOS but also test macOS and also do Android testing. So for Android OS I use Genymotion because the Android simulator, I don’t know if the conference allows swear words, but it sucks. Sorry.
Peter:
We try also to like keep our set up as simple as possible. There are Macs and then we have obviously Windows for the Windows tests, but we didn’t want to have yet another Linux system for Android. We just reuse macOS to keep the variable small.
Peter:
The main challenge is actually not finding a partner, and these guys are really easy to work with. The main challenge is to make sure the tests are stable, make sure that macOS works, that your automated tests work. A lot of the trouble is actually making sure you’re ready for the new Xcode release, you’re ready for the new macOS release. Apple usually gives you half a year time to update macOS before they release an Xcode version that doesn’t run on the previous macOS version anymore. So you really have to be fast. Now this year is even more interesting because, for example, we’re going to release PDF Viewer for the Mac in fall. Is that recorded? I don’t know, this is just my wish, but eventually you said fall is until December 20th so.
Shawn:
Yeah, you got plenty of time.
Peter:
But this actually forces us to be even faster. We need to have a version running with macOS 10.15 on CI. So for us running them bare metal, like just having the Mac mini and just having that on reduces a lot of variables. There’s a lot of benefits in Orka and all those more fancy orchestrations, but it also is sometimes a little bit more trouble, it’s something that takes a little bit longer for it to work. So that’s one of the reasons why we chose to keep it simple.
Peter:
Also, like we are the scale where this still works. If you have, I don’t know, thousands of devices, then it might get a little more annoying to do that. But we currently have 20, 30, so this is still a number that’s very fine. And sometimes if a Mac makes trouble or it’s weird, you just, we just reset it and like let Chef run. That takes around half a day to install macOS, install Xcode, install the Android Studio, all the things we need, and then it’s basically exactly at the level that we expect it to be. And then we can just add it to our Jenkins form again.
Dan:
It’s interesting hearing some of that and some of the similarities in our environments. Aspyr started going through a transition about a year, year and a half ago to move a lot of our data center services off site. We were running a full build farm internally. Actually I say internally, similar to your story, it lived in a developer’s office. And more than once the power turned off and it shut down the build farm. So that was changed. All the end points that did the builds were moved into our little server closet, and that gave us a little bit more stability. But as we continue to grow and our project count goes up, there’s no way I can continue to grow our build node count internally effectively. And that’s where I stumbled across MacStadium.
Dan:
Again, no affiliation bonus points here, but they are excellent hosts for us. They have provided us a way to expand out when we kind of hit our maximum. Our end points for the most part have been Mac and iOS, although we do also build for PC and Linux and PlayStation and Xbox. You name it, we’ve got it.
Dan:
So for us, Jenkins has been our backend for that, just firing off build scripts that the developers go, ’Hey, it worked on my system I committed to.’ We run on a per force server for source control and that stores it there. Jenkins pulls that script out and kicks it off.
Dan:
The struggle we’ve had lately is kind of to your point about the build image. Every version of OS X needs to have a certain version of Xcode and all the affiliate libraries in order to compile these build artifacts. And traditionally, yes, it’s the go through click, click, click through a remote desktop session just to set it all up.
Dan:
We did get to a point where we kind of found what I call our golden image. We find what we want it to be for that version of Xcode and OS X and we archive that off and keep it around just in case we have to build ancient versions of builds, which we do.
Dan:
And then actually thanks to a tip from MacStadium, we started playing around with a Jenkins plugin called Instant Clone or VMFork, however you may refer to that, where we’re able to then just spin off ephemeral images of our golden image and run our build in that, sync up our code repository, compile and go.
Dan:
A big point of that was getting our CI builds going. It’s been interesting. Our developers come from a background where you only commit when you have something to commit. And we’re changing that culture to a commit and commit often. So you find out what you’re breaking as you break it. And that’s what this pipeline has given us the ability to do. They commit in. It kicks off a quick CI build. Finds out what they just broke. They get an email back and they’re able to quickly iterate off of that instead of waiting for a full feature to be complete, committed in, send it off to build, and then find out. Just kidding… you’ve got to rebuild a lot of that feature. So that’s been helpful for us.
Dan:
The other part about our business that makes us a little bit unique is video games are such a manual testing heavy project. You can’t do automated builds on a majority of our projects. You might be able to do some unit tests around the UI and whether it even loads. That was one of our first unit tests. Does the game load? Does it crash?
Dan:
From there it goes into manual testing, a
https://diarynote.indered.space
*Even if you don’t subscribe to Pandora One, Hermes is and always will be open source and free for everyone. Usable Hermes pauses music when your computer sleeps and doesn’t resume on wake.
*Pandora announced todaythat the Pandora desktop app for macOS is now available to download, giving you full-featured access to the streaming service.
*Pandora One Desktop App for Mac, free and safe download. Pandora One Desktop App latest version: Discover new music from your desktop.
May 20, 2019 Pandora today launched a new desktop app for Mac, aimed at all Pandora listeners across both its free and paid tiers. Similar to its mobile apps, Pandora for Mac allows for full access to Pandora. Best Alarm App For Mac Book 2016 Canon Mx300 software, free download For Mac. Pandora App For Mac Laptop. Click on the button below to start downloading DaVinci Resolve Studio 16.0.0 for mac OS X. We are here to provide to clean and fast download for DaVinci Resolve Studio 16. This link is resume able within 24 hours.
Best Alarm App For Mac Book 2016 Canon Mx300 software, free download For Mac. Pandora App For Mac Laptop. Click on the button below to start downloading DaVinci Resolve Studio 16.0.0 for mac OS X. We are here to provide to clean and fast download for DaVinci Resolve Studio 16. This link is resume able within 24 hours. Play the songs, albums, playlists and podcasts you love on the all-new Pandora. Explore subscription plans to stream ad-free and on-demand. Listen on your mobile phone, desktop, TV.Alarm Clock Editor’s Review
Create alarms for your Mac with this handy utility.
One of the biggest things that people – me – do with their computers is keep track of their schedules. I know I’m pretty anal retentive about my calendar. I also know that I can often get lost in my writing when I’ve got a good topic I’m writing about. Its at times like this, that I’m glad that there are applications like Alarm Clock. It’s a Mac app that will help you remember key events and deadlines.
Alarm Clock is a menu item alarm clock for setting either one-time alarms or repeating alarms. Then choose anything in the iTunes library to wake to: songs, playlists, even podcasts. The application takes care of the rest, even waking the computer from sleep if needed.
You can configure your snooze duration to the length you want. You can even increase/decrease your snooze time right from the alarm window. Plus, if you have an apple remote, you can hit snooze without getting out of bed. If waking up to blaring alarms in the morning isn’t your cup of tea, there’s an ’easy wake’ option that gradually increases the alarm volume over time. All of the settings are end user configurable.
App Pro’s: Easy to use, FreePandora App Download For Macbook Pro
App Con’s: Functionality is limited to alarms and a stopwatch
Conclusion: Alarm Clock is a simple program, but what it does, it does very well. This is key system functionality that I haven’t been able to find in this configuration in OS X, even with Reminders; and I’m glad that this app has found its way to my hard drive. I’m certain you’ll like the app as well. The price is certainly right.
MacStadium recently hosted a panel on CI best practices at AltConf, which runs in parallel to Apple’s WWDC and is specifically focused on the Apple app development community. The panelists included: Daniel Hagen, Director of IT for Aspyr Media, publisher of popular Mac games like Call of Duty®, Sid Meier’s Civilization® and SimCity™; Debayan Majumdar, Sr. Mobile Tools Engineer at Pandora, the largest streaming music provider in the US; and Peter Steinberger, CEO of PSPDFKit, the go-to solution for integrating PDFs into your app. It was an interesting discussion as the companies represent very different development teams and CI practices. However, the experiences of these diverse teams did have a few common points.
The group was in agreement that a ’commit often’ culture was the most effective approach to get working apps written, and all three loved TestFlight. There was agreement on using Jenkins if you need a flexible deployment tool; however, this is where the first difference started – PSPDFKit no longer uses Jenkins as their primary CD tool, they have opted to move from Jenkins to BuildKite for ease of use. The relatively small shop values the labor savings, but still uses Jenkins to launch its TestFlight jobs.
Automated testing was the best practice, but how it was implemented varied. Being a game developer, Aspyr had the most limited set of automated testing. Pandora did not weigh in during the panel, but afterwards discussed testing with MacStadium and agreed automating this was vital – they use extensive automated tests for regression testing and basic pipeline CI as developers do commits. PSPDFKit not only uses their MacStadium infrastructure to test iOS code, but also Android code! Peter even commented that, ’the Android simulator, I don’t know if the conference allows swear words, but it sucks. Sorry.’
As is best practice, each organization uses a known good image to base all of their machines off of, but they differed on their implementation method. Aspyr uses Golden Images and Instant Cloning (a vSphere and Jenkins feature) to produce new machines, then updates their Golden Images about once a week. Pandora uses an Anka template as its golden image, and does updates to all their templates with Ansible as needed. PSPDFKit prefers a bare-metal approach, as this reduces technical debt, and again speaks to their team prioritizing ease of use. When a node gives unexpected results, they do a full system reset, then load Chef to return all packages to the desired state. (This takes about four hours.)
Watch the video of the panel discussion for more best practice configurations, favorite automation tricks, and other lessons learned:
Or read on for a transcribed version:
Speakers:
Shawn Lankton, Chief Revenue Officer, MacStadium
Peter Steinberger, Founder & CEO, PSPDFKit
Daniel Hagen, Director of IT, Aspyr Media
Debayan Majumdar, Technical Team Lead, Mobile Tools, Pandora/SiriusXM
Shawn:
We’ve got three great guests with us here today who are going to be doing most of the talking. I’ll let them introduce themselves quickly. Peter, do you want to start?
Peter:
My name is Peter. I work on PSPDFKit; I’m the founder. We are in Dropbox and IBM and Lufthansa, we’re like an SDK that shows PDF on all platforms, not just iOS, but we come from the iOS world and it’s still our most important market. Yeah, CI is very important for us. Like every pull request runs all the platforms automated, and we are happy partner of MacStadium.
Dan:
Hey everyone. My name is Daniel Hagen. I’m the director of IT for Aspyr Media. We are known as the world’s largest Mac publisher of video games. So many of you probably have played a few of ours, hopefully. Yeah, anything from Civilization to Call of Duty to Sims. We’ve played around with a lot of the good games. My background comes from web development. So CI/CD to me is a lot of automated pipelines, automated testing, automated unit tests, that sort of thing. So bring that into a thick client world has been an interesting endeavor. And working with development teams that come from -- probably a little bit stuck in the 1980s -- has been an endeavor of its own. So it’s been a lot of fun to bring that about and make things happen a lot faster and a lot quicker.
Debayan:
My name is Debayan and I lead the Mobile Tools Team at Pandora/SiriusXM now. So for those of you who don’t know, SiriusXM recently acquired Pandora, which makes us the largest music streaming company in the US. We have over 100 million monthly active users. You can imagine the scale at which we have to run our things.
Debayan:
I was actually the first mobile tools engineer or the first DevOps engineer at Pandora. So I can say that we have come a very long way and it’s been a great arduous journey not only building out the CI infrastructure, but just changing the culture and kind of bringing in a DevOps mindset that allows us to scale. I think that has been a very challenging journey and very enriching journey as well.
Shawn:
Thanks. I wanted to just give a few words about what continuous integration is. I think probably everybody in this room came because they already know, but spend two seconds on it. Also, I’m Shawn Lankton. I work at MacStadium. I lead our sales and marketing teams and spend a lot of time thinking about how to make sure that everybody knows what’s out there, how to use it so that we can help them.
Shawn:
Continuous integration is basically part of the DevOps workflow. It really focuses in on the build and test portions. The idea is that you’re going to run a build every time you merge code with a pull request. You’re going to test every time you build. It helps you catch errors faster and brings the faster time to value by shifting things left so you catch them sooner.
Shawn:
Of course, again, as I’m sure you all know, when you do this for the Apple ecosystem, you have to do all your builds and a lot of your tests using Xcode. Xcode only runs on macOS. macOS only runs on genuine Apple hardware, which means you have to find some way to get it and deploy it at scale. Once you have it deployed, you have to automate it, and a lot of the tricks that DevOps teams use for every other platform will not work for macOS. That’s why we have a packed house at 4:00 in the afternoon.
Shawn:
MacStadium helps. In case you’re not familiar, we have data centers around the world. We have about 20,000 Macs deployed in our data centers and we’re buying them pretty much as fast as we can. We have Mac minis, Mac Pros, we have iMac Pros deployed and we work with all of the different virtualization technologies, whether it’s VMware, Anka, or Orka, which we are just announcing this week. If you’d like to learn more about how to use Kubernetes to orchestrate Mac VMs, come talk to us at our booth anytime throughout the week. But I won’t get into that now.
Shawn:
We’re also of course very excited about rack mounted Mac Pros and what the future may hold for that. The fall ends on December 20th in case anybody hadn’t checked their calendar. So we’ll see when that actually ships.
Shawn:
That’s enough about context. I want to spend the rest of the time here talking with these guys about some of their experiences on these topics. We’ll get started. You’ve heard a bit about who they are and what the companies are. But I think it makes a lot of sense to start by understanding what are the end points that these guys are targeting, how are their teams structured, and what are their end users expecting to find in an app. So take it away.
Peter:
Sure. So I probably represent the smaller company side here. We have like two other giants in the room. For us, the important part is, it needs to be very cost effective, it needs to be simple to administer, and of course it should be fast and good.
Peter:
Obviously we need Mac hardware to run our Mac tests. And we also want to use Mac hardware to build Mac software. We started using Jenkins very early on. Since we are like eight years in or seven years in, everybody hates it, but it gets the job done. We’re now having a project to migrate to Buildkite because we slowly see that Jenkins doesn’t really scale well. When you update the plugin, all the jobs need to stop and then Jenkins needs to restart. And then you have to hope that it boots up again because if the plugin update failed then you’ll just get an error and you have to like manually undo it and it’s very, very messy.
Peter:
But there’s a lot of those problems you can live with so I think it’s a decent choice if you look at the options out there. For us it now makes sense to move to a little bit of a better and also more expensive system. Setup wise, we started with iOS. So very early on we wanted to have hosted Macs via a remote company so there is no real office, meaning there’s also no real data center. For a while I had Mac minis at my home and then the cleaning lady unplugged them, which is not really professional and it’s also kind of annoying. So having those things in an actual data center is nice.
Peter:
There’s not that many companies out there where you can actually do that. So you can do your own research. I did, and that’s why I chose MacStadium. So this is may be a marketing plug, but I don’t get any affiliation. They are very good to work with. We looked at the different products. I mean they have like Mac Pros and Xserves as well. Do they still exist?
Shawn:
They still exist. Not many people use them anymore.
Peter:
So we chose the simplest set up possible again because our set up needs to be cost effective. It was just Mac minis. One Mac mini for one user doing one test at a time or sometimes two.
Peter:
In the very early days we set them up manually, just VNC in and like you have someone doing a lot of clicking. That gets annoying very quickly. So don’t do that. We did invest a lot of time in Ansible and automating everything. Once we’re like at 95% done, we found out that Microsoft maintains a really, really good Chef repository with like a cookbook. So you can basically pick what you want from like installing Xcode to a lot more esoteric things.
Peter:
We use Mac minis to not only test iOS but also test macOS and also do Android testing. So for Android OS I use Genymotion because the Android simulator, I don’t know if the conference allows swear words, but it sucks. Sorry.
Peter:
We try also to like keep our set up as simple as possible. There are Macs and then we have obviously Windows for the Windows tests, but we didn’t want to have yet another Linux system for Android. We just reuse macOS to keep the variable small.
Peter:
The main challenge is actually not finding a partner, and these guys are really easy to work with. The main challenge is to make sure the tests are stable, make sure that macOS works, that your automated tests work. A lot of the trouble is actually making sure you’re ready for the new Xcode release, you’re ready for the new macOS release. Apple usually gives you half a year time to update macOS before they release an Xcode version that doesn’t run on the previous macOS version anymore. So you really have to be fast. Now this year is even more interesting because, for example, we’re going to release PDF Viewer for the Mac in fall. Is that recorded? I don’t know, this is just my wish, but eventually you said fall is until December 20th so.
Shawn:
Yeah, you got plenty of time.
Peter:
But this actually forces us to be even faster. We need to have a version running with macOS 10.15 on CI. So for us running them bare metal, like just having the Mac mini and just having that on reduces a lot of variables. There’s a lot of benefits in Orka and all those more fancy orchestrations, but it also is sometimes a little bit more trouble, it’s something that takes a little bit longer for it to work. So that’s one of the reasons why we chose to keep it simple.
Peter:
Also, like we are the scale where this still works. If you have, I don’t know, thousands of devices, then it might get a little more annoying to do that. But we currently have 20, 30, so this is still a number that’s very fine. And sometimes if a Mac makes trouble or it’s weird, you just, we just reset it and like let Chef run. That takes around half a day to install macOS, install Xcode, install the Android Studio, all the things we need, and then it’s basically exactly at the level that we expect it to be. And then we can just add it to our Jenkins form again.
Dan:
It’s interesting hearing some of that and some of the similarities in our environments. Aspyr started going through a transition about a year, year and a half ago to move a lot of our data center services off site. We were running a full build farm internally. Actually I say internally, similar to your story, it lived in a developer’s office. And more than once the power turned off and it shut down the build farm. So that was changed. All the end points that did the builds were moved into our little server closet, and that gave us a little bit more stability. But as we continue to grow and our project count goes up, there’s no way I can continue to grow our build node count internally effectively. And that’s where I stumbled across MacStadium.
Dan:
Again, no affiliation bonus points here, but they are excellent hosts for us. They have provided us a way to expand out when we kind of hit our maximum. Our end points for the most part have been Mac and iOS, although we do also build for PC and Linux and PlayStation and Xbox. You name it, we’ve got it.
Dan:
So for us, Jenkins has been our backend for that, just firing off build scripts that the developers go, ’Hey, it worked on my system I committed to.’ We run on a per force server for source control and that stores it there. Jenkins pulls that script out and kicks it off.
Dan:
The struggle we’ve had lately is kind of to your point about the build image. Every version of OS X needs to have a certain version of Xcode and all the affiliate libraries in order to compile these build artifacts. And traditionally, yes, it’s the go through click, click, click through a remote desktop session just to set it all up.
Dan:
We did get to a point where we kind of found what I call our golden image. We find what we want it to be for that version of Xcode and OS X and we archive that off and keep it around just in case we have to build ancient versions of builds, which we do.
Dan:
And then actually thanks to a tip from MacStadium, we started playing around with a Jenkins plugin called Instant Clone or VMFork, however you may refer to that, where we’re able to then just spin off ephemeral images of our golden image and run our build in that, sync up our code repository, compile and go.
Dan:
A big point of that was getting our CI builds going. It’s been interesting. Our developers come from a background where you only commit when you have something to commit. And we’re changing that culture to a commit and commit often. So you find out what you’re breaking as you break it. And that’s what this pipeline has given us the ability to do. They commit in. It kicks off a quick CI build. Finds out what they just broke. They get an email back and they’re able to quickly iterate off of that instead of waiting for a full feature to be complete, committed in, send it off to build, and then find out. Just kidding… you’ve got to rebuild a lot of that feature. So that’s been helpful for us.
Dan:
The other part about our business that makes us a little bit unique is video games are such a manual testing heavy project. You can’t do automated builds on a majority of our projects. You might be able to do some unit tests around the UI and whether it even loads. That was one of our first unit tests. Does the game load? Does it crash?
Dan:
From there it goes into manual testing, a
https://diarynote.indered.space
コメント