Thank you! Looks good. Especially the blogpost at the bottom of that page
about the Microsoft partnership was enlightening.
On Tuesday, February 21, 2017 at 1:32:09 PM UTC+1, Daniel Beck wrote:
>
>
> > On 21.02.2017, at 13:12, rouke.b...@infosupport.com
> wrote:
> >
> > Is there any
> On 21.02.2017, at 13:12, rouke.broer...@infosupport.com wrote:
>
> Is there any documentation on the change to ci.jenkins.io? The only thing I
> can find right now is this thread:
> https://groups.google.com/forum/#!topic/jenkinsci-dev/439-IDYNSVY about a
> trial on using ci.jenkins.io to
I don't know if we have more details for now than what we have in the
thread you mentioned
On Tue, Feb 21, 2017 at 1:12 PM, wrote:
> Is there any documentation on the change to ci.jenkins.io? The only thing
> I can find right now is this thread:
Is there any documentation on the change to ci.jenkins.io? The only thing I
can find right now is this
thread: https://groups.google.com/forum/#!topic/jenkinsci-dev/439-IDYNSVY
about a trial on using ci.jenkins.io to figure out what's required for
moving to azure.
On Tuesday, February 21,
I reconfigured
https://jenkins.ci.cloudbees.com/job/plugins/job/selenium-plugin/ to use
Java 8
The best solution for you will be to switch to ci.jenkins.io and then
you'll be free to use "everything" you want using a Jenkinsfile
Don't forget to add a warning in your changelog about the Java 8
I am unsure where to request Java 8 builds for the selenium jenkins plugin,
so I'll ask here.
The selenium jenkins plugin needs Java 8 because selenium itself needs java
8 and the plugin has a dependency on the selenium package.
Git url: https://github.com/jenkinsci/selenium-plugin/pulls
--