android-signing plugin build failed on jenkins.ci.cloudbees.com

22 views
Skip to first unread message

Robert St. John

unread,
Jan 20, 2017, 12:49:47 PM1/20/17
to Jenkins Developers
Hello,

I noticed that the last (and only) build of the android-signing plugin failed on jenkins.ci.cloudbees.com.  The problem appears to be that the job is using JDK 1.7, whereas the plugin requires JDK 1.8.  Do I need to make a modification to my POM to force the job to use JDK 1.8?  Will this prevent the plugin from being installed from the Jenkins management UI?

Thanks.

Robert

Slide

unread,
Jan 20, 2017, 1:27:25 PM1/20/17
to Jenkins Developers
Hi Robert,

I don't think jenkins.ci.cloudbees.com supports JDK8 yet...but I could be wrong. You may want to talk to rtyler about having it hosting on ci.jenkins.io instead. It will not stop you from releasing a version of the plugin, or from it showing up in the management UI.

Regards,

Alex

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a8635a71-bbe4-4887-abea-06fe6809c6d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Robert Sandell

unread,
Jan 23, 2017, 5:49:00 AM1/23/17
to jenkin...@googlegroups.com
I've configured it to use "JDK 8 (latest)" And manually started a new build that passed.

/B

On Fri, Jan 20, 2017 at 7:27 PM, Slide <slide...@gmail.com> wrote:
Hi Robert,

I don't think jenkins.ci.cloudbees.com supports JDK8 yet...but I could be wrong. You may want to talk to rtyler about having it hosting on ci.jenkins.io instead. It will not stop you from releasing a version of the plugin, or from it showing up in the management UI.

Regards,

Alex
On Fri, Jan 20, 2017 at 10:49 AM Robert St. John <rest...@gmail.com> wrote:
Hello,

I noticed that the last (and only) build of the android-signing plugin failed on jenkins.ci.cloudbees.com.  The problem appears to be that the job is using JDK 1.7, whereas the plugin requires JDK 1.8.  Do I need to make a modification to my POM to force the job to use JDK 1.8?  Will this prevent the plugin from being installed from the Jenkins management UI?

Thanks.

Robert

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVd4Cbc2P0sHteTWeiOH27E2OYvhtO8HKC9VkoAq%3DpTu_w%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.



--
Robert Sandell
Software Engineer
CloudBees Inc.

Arnaud Héritier

unread,
Jan 23, 2017, 5:52:41 AM1/23/17
to jenkin...@googlegroups.com
Yes there is no problem with JDK 8 but by default we are still in JDK 7 like Jenkins is targeting 
It doesn't avid to use JDK 8 and target J7 but by default we are still proposing J7 for now

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS36hbaPpASRVaCNF-4smf0ArDpVfY_wfsoHgOALPA1aPg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.



--
-----
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Robert St. John

unread,
Jan 23, 2017, 10:29:02 AM1/23/17
to Jenkins Developers
Thanks; much appreciated!


On Monday, January 23, 2017 at 3:49:00 AM UTC-7, Robert Sandell wrote:
I've configured it to use "JDK 8 (latest)" And manually started a new build that passed.

/B
On Fri, Jan 20, 2017 at 7:27 PM, Slide <slide...@gmail.com> wrote:
Hi Robert,

I don't think jenkins.ci.cloudbees.com supports JDK8 yet...but I could be wrong. You may want to talk to rtyler about having it hosting on ci.jenkins.io instead. It will not stop you from releasing a version of the plugin, or from it showing up in the management UI.

Regards,

Alex
On Fri, Jan 20, 2017 at 10:49 AM Robert St. John <rest...@gmail.com> wrote:
Hello,

I noticed that the last (and only) build of the android-signing plugin failed on jenkins.ci.cloudbees.com.  The problem appears to be that the job is using JDK 1.7, whereas the plugin requires JDK 1.8.  Do I need to make a modification to my POM to force the job to use JDK 1.8?  Will this prevent the plugin from being installed from the Jenkins management UI?

Thanks.

Robert

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages