I tried to use codemagic for my flutter app to run in on iOS. Successfully builded the application, but there is no option for [Explore Build Machine via SSH or VNC Client], which i gonna run from VNC. I watched it from this tutorial : https://www.youtube.com/watch?v=m3_6z2wfHiY
Is there any way to show the IP/ Go premium?
Thanks
Trying to find the docs, but not finding the way
Solved. Forget to check when building the Apps. LOL
Related
I'm running the Jenkins as a Docker container on a Virtual Machine on Google Cloud Platform. On the very first screen of setup, I can see that a lot of plugins did not install in my Jenkins server?
Please let me know how to resolve this issue? Is it something due to with the security on the cloud by default which restricts downloading of plugins?
Refer following link for screenshot:-
https://storage.googleapis.com/mydockerissues/Jenkins%20Plugins%20Issue.PNG
Cheers
Something similar happened to me when running Jenkins on Docker on my local machine. To get everything to install I had to keep retrying. It took several retries but eventually I got everything installed.
I'm not sure why this is the case. Maybe it fails downloads whose dependencies aren't installed yet?
For CI purposes I have a need to set up a cluster of build slaves capable of building iOS apps. For now I'm relying on a single MacMini -with the aim to deploy several more in the future- and I'd like to virtualize several slaves on top of it. Some of these virtual slaves will build the iOS app, others will be smaller Linux slaves for miscellaneous purposes.
I'm completely new to Docker, so my main question is whether it's possible to dockerize Xcode 9.2 and/or MacOS in order to virtualize my iOS build slaves. I've seen very little literature out there on whether this can be achieved and I've found some images in hub.docker.com but they're not documented and don't appear to be very popular.
I'm going through a Docker tutorial right now and eventually will be attempting this -and if I'm successful I'll be answering my own question here for the benefit of others- but given the lack of information I have doubts on whether it is even possible or where I should even start.
Any tips or pointers on this would be greatly appreciated.
Or if anyone knows for fact that this is not possible and can explain why, that would also save me a lot of time.
OS X does not use the Linux kernel, so it cannot run in a Docker container
XCode is not open-sourced and does not have a Linux installer, so it cannot be used in a Linux Docker image.
It seems like your best bet is to build a Packer template using something like packer-macos osx-vm-templates and integrate that into your pipeline.
Look at Docker-OSX which runs macOS with Xcode support inside Docker.
You can connect to that macOS via SSH or VNC. It might be possible to use the same approach in CI/CD.
Related link from readme: "I want to use Docker-OSX for CI/CD-related purposes (sign into Xcode, Transporter)"
I tried setting up playground using
https://fabric-composer.github.io/tutorials/getting-started-playground.html
I followed the docker steps everything started OK, was able to access Fabric Composer Playground by clicking on this link: http://localhost:8080
But now what??? I tried to upload a sample model file but it shows error.
How do I try this out. Do I have install Ubuntu on my windows machine to really be able to try out fabric composer?? Pleas help
You can install and run the fabric composer locally on linux only. For that you can use VMWare and install ubuntu on it.
And then follow the installation steps here.
If you don't want to do so, then alternatively you can use the online composer playground and can export(download) your .bna file whenever you want.
Hope this helps you!
I am working on automating testing for my company using Appium Python + AWS Device Farm for iOS devices.
However, when I uploaded my .ipa file and Appium Python test to AWS Device farm, the run stuck and showed me that the status is "Errored", and if I click into the run for a detailed view, it says "Pending" on all of the device runs (See screenshots below: )
I am pretty sure it is not the problem with my Appium Python test script, because when combining the same script with another .ipa file (from another App), the run works fine on AWS Device Farm. The thing is that by using the same handling, I was able to export .ipa off other App and had them run just fine on AWS Device Farm. This only happens to this particular .ipa file of the same App, but it is the company's official App that I must automate the test for, so I can't just not test it.
Does anyone know how I could fix this problem?
Thanks so much!
The question has been kindly answered and resolved by the AWS Device Farm team here:
https://forums.aws.amazon.com/thread.jspa?threadID=245483
Description
We are using appium in our cucumber suite within TeamCity 8 on an Apple MacMini running Mavericks. The problem is that appium seems to fail to interact with the iOS Simulator when it is ran from TeamCity at login (via Automator).
The only combination that I have found to work is to run the following from the Terminal in an interactive session:
sh /Applications/buildagent/bin/agent.sh start
What does not work?
running agent.sh start from an ssh session
creating a shell script with Automator that launches at login (the macmini is set to login automatically)
Theory
My theory is that it has something to do with Preferences -> Security & Privacy -> Accessibility. The only way that it works when launching from Terminal is if Terminal is added to this list of allowed applications. I'm not sure what I need to add to this list in order for this to work automatically at login.
Any help would be greatly appreciated.
Many iOS tests will not run without an interactive session. For example, unit tests using the iOS simulator will not work.
Edit: By interactive session, I mean the TeamCity agent must be started from the desktop, not via an SSH session. Otherwise nothing can communicate with the Simulator.
You are correct, you need to allow Appium to interact with Automator.
Solutions straight from the documentation:
If you're running Appium from an NPM install: sudo authorize_ios
If you're running Appium from source: sudo grunt authorize
If you are running Appium.app, you can authorize iOS through the GUI. This prompt pops up the first time you click "Launch/Run" on the GUI and it tries to open the simulator