[JIRA] (JENKINS-58310) Can I use the android signing plugin to sign android app bundles?

2019-07-08 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58310  
 
 
  Can I use the android signing plugin to sign android app bundles?   
 

  
 
 
 
 

 
Change By: 
 Robert St. John  
 
 
Issue Type: 
 Task New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200418.1562139892000.4033.1562587440580%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58310) Can I use the android signing plugin to sign android app bundles?

2019-07-08 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John edited a comment on  JENKINS-58310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can I use the android signing plugin to sign android app bundles?   
 

  
 
 
 
 

 
 Some [brief research|https://developer.android.com/studio/build/building-cmdline#sign_cmdline] unfortunately reveals that the plugin cannot sign AABs, currently.  I can probably get around to implementing a solution that uses Java's  [  {{JarSigner}} |https://docs.oracle.com/en/java/javase/11/docs/api/jdk.jartool/jdk/security/jarsigner/JarSigner.html]  API.   Pull requests are welcome as well, if you're so inclined.   In the interim, you should be able to use Java's  `  {{ jarsigner ` }}  command-line utility and the  [  Credentials Binding Plugin |https://plugins.jenkins.io/credentials-binding]  to sign your AABs.  Just be aware of some of the [security concerns|https://jenkins.io/doc/pipeline/steps/credentials-binding/#withcredentials-bind-credentials-to-variables] that go along with that approach.   You could also enroll in Google Play's app signing, as the [Android docs describe|https://developer.android.com/guide/app-bundle#get_started], if that's an option for you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200418.1562139892000.4025.1562585280163%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58310) Can I use the android signing plugin to sign android app bundles?

2019-07-07 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-58310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can I use the android signing plugin to sign android app bundles?   
 

  
 
 
 
 

 
 Some brief research unfortunately reveals that the plugin cannot sign AABs, currently. I can probably get around to implementing a solution that uses Java's JarSigner API. In the interim, you should be able to use Java's `jarsigner` command-line utility and the Credentials Binding Plugin to sign your AABs. Just be aware of some of the security concerns that go along with that approach.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200418.1562139892000.3887.1562562060264%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58310) Can I use the android signing plugin to sign android app bundles?

2019-07-03 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-58310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can I use the android signing plugin to sign android app bundles?   
 

  
 
 
 
 

 
 To be quite honest, I don't know.  Do you have a build you can try already?  I'll look into it when I get a few spare moments in the next couple of days.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200418.1562139892000.810.1562153580147%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49290) Could not find com.android.tools.build:gradle:3.0.1.

2018-10-04 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John edited a comment on  JENKINS-49290  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Could not find com.android.tools.build:gradle:3.0.1.   
 

  
 
 
 
 

 
 Posting your Gradle scripts would be helpful.  Make sure you have the Google Maven repository in your top-level build script under the {{  buildscript \{ ... } }}  block, as the Android Developer [documentation shows|https://developer.android.com/studio/build/#top-level].{code:java} buildscript {repositories {google()jcenter()}dependencies {classpath 'com.android.tools.build:gradle:3.2.0'}}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-49290) Could not find com.android.tools.build:gradle:3.0.1.

2018-10-04 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John edited a comment on  JENKINS-49290  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Could not find com.android.tools.build:gradle:3.0.1.   
 

  
 
 
 
 

 
 Posting your Gradle scripts would be helpful.  Make sure you have the Google Maven repository in your top-level build script under the {{buildscript \{ ... }}} block, as the Android Developer [documentation shows|https://developer.android.com/studio/build/#top-level].  {code :java } buildscript {repositories {google()jcenter()}dependencies {classpath 'com.android.tools.build:gradle:3.2.0'}}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-49290) Could not find com.android.tools.build:gradle:3.0.1.

2018-10-04 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-49290  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Could not find com.android.tools.build:gradle:3.0.1.   
 

  
 
 
 
 

 
 Posting your Gradle scripts would be helpful.  Make sure you have the Google Maven repository in your top-level build script under the {{buildscript { ... }}} block, as the Android Developer documentation shows. 

 

 buildscript {

repositories {
google()
jcenter()
}

dependencies {
classpath 'com.android.tools.build:gradle:3.2.0'
}
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-49290) Could not find com.android.tools.build:gradle:3.0.1.

2018-08-13 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-49290  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Could not find com.android.tools.build:gradle:3.0.1.   
 

  
 
 
 
 

 
 mahesh ordex, can you provide your solution for the others that seem to be having the same problem? dub o, if you post your Gradle scripts and Jenkins build log, I can take a look for you.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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-41846) artifact archiving error - concatenated absolute paths

2017-03-02 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed the way the plugin determines relative paths within the workspace  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41846  
 
 
  artifact archiving error - concatenated absolute paths   
 

  
 
 
 
 

 
Change By: 
 Robert St. John  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-35671) Define Run.getEnvironmentForExpansion

2017-02-17 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-35671  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Define Run.getEnvironmentForExpansion   
 

  
 
 
 
 

 
 The issue reference in that previous commit message should have been JENKINS-29144 - sorry about that.  
 

  
 
 
 
 

 
 
 

 
 
 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-41846) artifact archiving error - concatenated absolute paths

2017-02-08 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41846  
 
 
  artifact archiving error - concatenated absolute paths   
 

  
 
 
 
 

 
Change By: 
 Robert St. John  
 
 
Summary: 
 artifact archiving error -  doubled  concatenated absolute  paths  
 

  
 
 
 
 

 
 
 

 
 
 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-41846) artifact archiving error - doubled paths

2017-02-08 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41846  
 
 
  artifact archiving error - doubled paths   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Robert St. John  
 
 
Components: 
 android-signing-plugin  
 
 
Created: 
 2017/Feb/08 3:12 PM  
 
 
Environment: 
 Windows 10, android-signing 2.0.7, Jenkins 2.44, Java 1.8.0_91  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Robert St. John  
 

  
 
 
 
 

 
 This issue was discovered while addressing JENKINS-41787. See the relevant logging in the comments. At some point, the plugin's archive action results in appending the source artifact's absolute path to the absolute path of the build's archive, resulting in an IOException.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

[JIRA] (JENKINS-41787) Android Signing plugin command not correct...

2017-02-08 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed by https://github.com/jenkinsci/android-signing-plugin/commit/262e9eee64b82148c16a6cb8bd59be101988bc7a, in the message of which I forgot to reference this ticket.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41787  
 
 
  Android Signing plugin command not correct...   
 

  
 
 
 
 

 
Change By: 
 Robert St. John  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-41787) Android Signing plugin command not correct...

2017-02-08 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John started work on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Robert St. John  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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...

2017-02-07 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Android Signing plugin command not correct...   
 

  
 
 
 
 

 
 Thanks for your concern. Rest assured, I don't feel bad. I appreciate your feedback and efforts to make the software better, and I am glad it's getting some use. Admittedly, I also consciously discriminate against Windows because I do not enjoy the developer experience. That's probably due mostly to inertia and ignorance, though, so I'm glad users such as you are around to keep me on the level and remind me that mine is not the only perspective out there. I have a Windows VM setup now, so hopefully I can minimize any more OS-related discrepancies for future releases. Let me know if you have any more issues.  
 

  
 
 
 
 

 
 
 

 
 
 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...

2017-02-07 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John edited a comment on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Android Signing plugin command not correct...   
 

  
 
 
 
 

 
 Thanks for the log, much appreciated.  I just released version 2.0.8  of the plugin  which should allow you to use {{ANDROID_HOME}} from the OS or the Jenkins system configuration.  I'd appreciate your feedback whenever you get a chance to try it.   Jenkins might take a little while before making it available in the update manager.  
 

  
 
 
 
 

 
 
 

 
 
 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...

2017-02-07 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Android Signing plugin command not correct...   
 

  
 
 
 
 

 
 Thanks for the log, much appreciated. I just released version 2.0.8 which should allow you to use ANDROID_HOME from the OS or the Jenkins system configuration. I'd appreciate your feedback whenever you get a chance to try 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-41787) Android Signing plugin command not correct...

2017-02-07 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John edited a comment on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Android Signing plugin command not correct...   
 

  
 
 
 
 

 
 Do you mind also posting your build log from when the archive artifacts failed?  I'd like to verify that's not another issue with the plugin.   You could also email it to me separately if you like.  
 

  
 
 
 
 

 
 
 

 
 
 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...

2017-02-07 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Android Signing plugin command not correct...   
 

  
 
 
 
 

 
 Do you mind also posting your build log from when the archive artifacts failed? I'd like to verify that's not another issue with the plugin.  
 

  
 
 
 
 

 
 
 

 
 
 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...

2017-02-07 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Android Signing plugin command not correct...   
 

  
 
 
 
 

 
 No problem, I'm glad you got it working. I'll try to get a Windows test environment setup to avoid future Windows discrepancies. Hopefully I can a release done today to fix this 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...

2017-02-07 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Android Signing plugin command not correct...   
 

  
 
 
 
 

 
 You might need to resort to using the ANDROID_ZIPALIGN variable and add .exe to the end. I've not had a chance to test on Windows, so I might need to put in a fix to add the .exe extensions on Windows hosts.  
 

  
 
 
 
 

 
 
 

 
 
 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...

2017-02-07 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Android Signing plugin command not correct...   
 

  
 
 
 
 

 
 ANDROID_ZIPALIGN is intended to be more of a one-off override that you can setup in the Jenkins system configuration or on a per-job basis. If you are relying on the environment variables Jenkins inherits from your OS, the plugin will currently attempt to find zipalign in the latest version of the build-tools package located in the directory referenced by ANDROID_HOME, so you can setting ANDROID_HOME at the OS level instead. In your case, that appears to be d:\android-studio.  
 

  
 
 
 
 

 
 
 

 
 
 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...

2017-02-07 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John edited a comment on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Android Signing plugin command not correct...   
 

  
 
 
 
 

 
 {{ANDROID_ZIPALIGN}} is intended to be more of a one-off override that you can setup in the Jenkins system configuration or on a per-job basis.  If you are relying on the environment variables Jenkins inherits from your OS, the plugin will currently attempt to find {{zipalign}} in the latest version of the build-tools package located in the directory referenced by {{ANDROID_HOME}}, so you can setting {{ANDROID_HOME}} at the OS level instead.  In your case, that appears to be {{d:\android-studio}}.   I will consider also trying to find {{zipalign}} from the OS {{PATH}} variable as well, but that would be in a future release.  
 

  
 
 
 
 

 
 
 

 
 
 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...

2017-02-06 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John edited a comment on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Android Signing plugin command not correct...   
 

  
 
 
 
 

 
 The logging you provided indicates that you simply need to append {{\zipalign}} to the value of your {{ANDROID_ZIPALIGN}} variable, so the full value of {{ANDROID_ZIPALIGN}} should be {{d:\android-studio\build-tools\25.0.2\zipalign}}.  The plugin expects the value of {{ANDROID_ZIPALIGN}} to be the full path to the {{zipalign}} executable, rather  than  the parent directory.  My apologies if that is not clear in the [README|https://github.com/jenkinsci/android-signing-plugin].  I'll modify it to provide specific examples.  Please let me know in a comment if that fixes your problem.Cheers  
 

  
 
 
 
 

 
 
 

 
 
 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...

2017-02-06 Thread restj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert St. John commented on  JENKINS-41787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Android Signing plugin command not correct...   
 

  
 
 
 
 

 
 The logging you provided indicates that you simply need to append \zipalign to the value of your ANDROID_ZIPALIGN variable, so the full value of ANDROID_ZIPALIGN should be d:\android-studio\build-tools\25.0.2\zipalign. The plugin expects the value of ANDROID_ZIPALIGN to be the full path to the zipalign executable, rather the parent directory. My apologies if that is not clear in the README. I'll modify it to provide specific examples. Please let me know in a comment if that fixes your problem. Cheers  
 

  
 
 
 
 

 
 
 

 
 
 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.