[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... Thanks I do have a windows 10 laptop setup with Ubuntu but it takes forever now to boot up since I added Docker. I like Linux but can never get around to dedicating a machine for it at home. Glad to help but do not let the rest of the Jenkins team know that I am s busy now just writing Mobile apps and Microservices ugh. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... Do not feel bad I found the Android Emulator Plugin was using the Linux / rather than the windows \ when appending to the ANDROID_SDK_HOME on a Windows OS. Yes, I reported it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41834) Android Emulator module using / rather than \ when appending...
Title: Message Title Tony Anecito created an issue Jenkins / JENKINS-41834 Android Emulator module using / rather than \ when appending... Issue Type: Bug Assignee: Christopher Orr Components: android-emulator-plugin Created: 2017/Feb/08 3:53 AM Environment: Windows 10 Jenkins 2.44 Android Emulator Plugin 2.15 Java 1.8.0_91 Priority: Minor Reporter: Tony Anecito Emulator plugin fails to run emulator.exe or adb.exe because when plugin appended to the ANDROID_SDK_HOME it uses / slash instead of \ slash. Please fix and make sure elsewhere in the code you use the proper slash depending upon OS. Add Comment
[JIRA] (JENKINS-39097) PANIC : Broken AVD system path
Title: Message Title Tony Anecito commented on JENKINS-39097 Re: PANIC : Broken AVD system path I am having the same issue. I hope someone who knows the answer will comment. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... Sure. I will try it and let you know as soon as Jenkins makes it available. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... Here is the console output. I do not know where to find the build logs. FATAL: Failed to create a directory at C:\Users\\.jenkins\jobs\Disaster Center\builds\11\archive\C:\Users\\.jenkins\workspace\Disaster Center\app\build\outputs\apk java.io.IOException: Failed to create a directory at C:\Users\\.jenkins\jobs\Disaster Center\builds\11\archive\C:\Users\.jenkins\workspace\Disaster Center\app\build\outputs\apk at hudson.util.IOUtils.mkdirs(IOUtils.java:66) at hudson.FilePath.mkdirsE(FilePath.java:2914) at hudson.FilePath.access$2000(FilePath.java:195) at hudson.FilePath$42$1.visit(FilePath.java:2133) at hudson.util.DirScanner.scanSingle(DirScanner.java:49) at hudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2804) at hudson.FilePath$42.invoke(FilePath.java:2128) at hudson.FilePath$42.invoke(FilePath.java:2121) at hudson.FilePath.act(FilePath.java:996) at hudson.FilePath.act(FilePath.java:974) at hudson.FilePath.copyRecursiveTo(FilePath.java:2121) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at org.jenkinsci.plugins.androidsigning.SignApksBuilder.perform(SignApksBuilder.java:194) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Archiving artifacts Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... Okay, the signing does not fail if I un-check the archive signed jars. You can close this issue and mention in a windows example the correct suffix for the zipalign. Thanks for the quick replies! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... Ok there is an checkbox for the plugin for archiving. I unselected that since I already have a post-build action to archive the apks and that does work. I am not sure why the plugin was not allowed to create a directory for archiving that is what the error was. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... Ok it was not an issue with the anti-virus and adding the .exe solved creating the signed apk but archiving failed but that is not an issue with the plugin I think. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... I am thinking it is a permissions issue and Jenkins conflicting with anti-virus software. I am running some tests now to confirm my guess. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... Ok I will try. FYI, I did take the complete command line put it in a batch file and ran it from the directory the plugin tried and it worked. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... Almost worked. I get the error about zipalign not being a valid win32 application I will have to figure that one out. It works fine from a command line. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... I already had ANDROID_HOME setup just like you mentioned and that did not solve this issue. Perhaps that has not been released yet or perhaps it is looking in a specific directory I do not have the zipalign.exe in? I did add zipalign as you suggested and that worked. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... Thanks for the update I will try that also so I do not need the one-off as you mentioned. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito edited a comment on JENKINS-41787 Re: Android Signing plugin command not correct... Thanks I will give it a try. Yes examples would be a big help. FYI, I usually do not include an executable in the path for the variable just the path to the directory where it resides otherwise the path would get full of executable s. So you might want to do it that way.I will try what you suggest and then comment on if it fixed the issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito edited a comment on JENKINS-41787 Re: Android Signing plugin command not correct... Thanks I will give it a try. Yes examples would be a big help. FYI, I usually do not include an executable in the path just the path to the directory where it resides otherwise the path would get full of executable s. So you might want to do it that way.I will try what you suggest and then comment on if it it fixed the issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito commented on JENKINS-41787 Re: Android Signing plugin command not correct... Thanks I will give it a try. Yes examples would be a big help. FYI, I usually do not include an executable in the path just the path to the directory where it resides otherwise the path would get full of executable s. So you might want to do it that way. I will try what you suggest and then comment on it it fixed the issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito created an issue Jenkins / JENKINS-41787 Android Signing plugin command not correct... Issue Type: Bug Assignee: Robert St. John Components: android-signing-plugin Created: 2017/Feb/07 4:39 AM Environment: Windows 10 Priority: Blocker Reporter: Tony Anecito Jenkins 2.44, android-signing-plugin 2.0.7, Windows 10, Java 1.8.0_91 When the signing plugin runs during the build I get an error: Total time: 4 mins 24.557 secs Build step 'Invoke Gradle script' changed build result to SUCCESS [SignApksBuilder] found zipalign path in env ANDROID_ZIPALIGN=d:\android-studio\build-tools\25.0.2 [Disaster Center] $ d:\android-studio\build-tools\25.0.2 -f -p 4 "C:\Users\\.jenkins\workspace\Disaster Center\app\build\outputs\apk\app-release-unsigned.apk" "C:\Users\\.jenkins\workspace\Disaster Center\app\build\outputs\apk\app-release-unsigned-aligned.apk" Access is denied FATAL: Cannot run program "d:\android-studio\build-tools\25.0.2" (in directory "C:\Users\\.jenkins\workspace\Disaster Center"): CreateProcess error=5, Access is denied java.io.IOException: Cannot run program "d:\android-studio\build-tools\25.0.2" (in directory "C:\Users\\.jenkins\workspace\Disaster Center"): CreateProcess error=5, Access is denied at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.(Proc.java:245) at hudson.Proc$LocalProc.(Proc.java:214) at hudson.Launcher$LocalLauncher.launch(Launcher.java:846) at hudson.Launcher$ProcStarter.start(Launcher.java:384) at hudson.Launcher$ProcStarter.join(Launcher.java:395) at org.jenkinsci.plugins.androidsigning.SignApksBuilder.perform(SignApksBuilder.java:158) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at
