-
-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest release of Appium has broken shell commands #153
Comments
Hi @tking16 , pass all needed parameters that the container need and just run this last command inside sh command, it should fix the issue. let me know if you still have the issue. it is interesting that you deploy container every time there is a test instead of having device farm before. could you also write documentation about that @tking16 ? you can commit the documentation under examples/jenkins if you like, so it will benefit the other users that there are ways to use this project. |
I have a Jenkinsfile which runs our Appium Smoke tests, for the past few days the jenkins job has been failing with absolutely no clear explaining, it all runs perfectly fine until it enters the Appium container and tries to run it's first
sh
command, in which it will hang for about 5 minutes then fail with:[Pipeline] container [Pipeline] { [Pipeline] sh process apparently never started in /home/jenkins/agent/workspace/android-at-tests@tmp/durable-0f6a0121 (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
So I've now just changed the image from
image: "appium/appium"
toimage: "appium/appium:v1.22.0-p0"
and it's working, which leads me to believe a recent update is causing the hang to occur. Maybe since a big refactor?Jenkinsfile code to reproduce issue:
The text was updated successfully, but these errors were encountered: