Re: [DISCUSS] Switching to CentOS for Jenkins Docker base image

[Richard Bywater]

Ah - hadn't realised they also did Docker image. Thanks for pointing that
out.

Richard.

On Wed, 27 Feb 2019 at 13:17, Slide  wrote:

> Looks like AdoptOpenJDK had some different options as well for base Docker
> images.
>
> https://hub.docker.com/r/adoptopenjdk/openjdk8
>
> On Tue, Feb 26, 2019, 16:49 Richard Bywater  wrote:
>
>> If the concern is regarding packaging, would it be worthwhile switching
>> the images to drag in something like a AdoptOpenJDK archive and use that
>> instead? (Presumably would need to create symlinks etc. for binaries). I
>> took a look at the CentOS OpenJDK11 package and it was hard to tell how
>> up-to-date it was given it seems to be from November 2018 but AdoptOpenJDK
>> has a build from late January.
>>
>> Richard.
>>
>> On Wed, 27 Feb 2019 at 11:52, Mark Waite 
>> wrote:
>>
>>>
>>> On Tue, Feb 26, 2019 at 3:31 PM R. Tyler Croy 
>>> wrote:
>>>
 (replies inline)

 On Tue, 26 Feb 2019, Matt Sicker wrote:

 > Based on the details regarding Debian and Ubuntu's poor maintenance
 of JDK
 > packages, I'd support using a different distro like CentOS. That
 certainly
 > pushes myself away from defaulting to ubuntu or debian for Java Docker
 > images.


 Agreed! I think this is worthwhile to do. The first responsibility IMO
 of our
 containers is to provide the most stable and secure Jenkins environment
 for end
 users.

 We already maintain an Alpine image, to where if there are people
 depending on
 a Debian-based image, making that available as another set of tags is
 also
 always an option.


>>> Adding tags for CentOS images seems least likely to break existing users.
>>>
>>> Since the base Jenkins docker image does not include certain critical
>>> programs
>>> (like "git-lfs"), I needed to extend the image by installing additional
>>> packages with
>>> the operating system package management system.  It works well and lets
>>> me
>>> test interesting cases faster.
>>>
>>> If we add a CentOS image, I'm very much in favor of it.  +1 if so
>>>
>>> If we replace the Debian image with a CentOS image, that will be
>>> disruptive
>>> to me and those like me that needed additional operating system specific
>>> extensions in the image.  I can adapt, but there will be others that will
>>> grumble about adapting.
>>>
>>> Is the proposal to add CentOS or to replace Debian with CentOS?
>>>
>>> Mark Waite
>>>
>>>

 +1

 --
 GitHub:  https://github.com/rtyler

 GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2

 --
 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+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/20190226223130.wbcx2dr6ln5lf2g4%40grape
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>> --
>>> Thanks!
>>> Mark Waite
>>>
>>> --
>>> 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+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHk38Oi7zcKarTLZ_6L%2By12nmAa1o9-7VaAxn4MR2612g%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwczub-i9bouUoRyu%2BsSD7FcvBXu9yuEQVxHsa%3DFdo%3DsUw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcnJ7N%2B3iTQS9n3S4zJ7N4zHvWOBayoqXwK38Nm0kU93g%40mail.gmail.com
> 
> .
>

Re: [DISCUSS] Switching to CentOS for Jenkins Docker base image

[Slide]

Looks like AdoptOpenJDK had some different options as well for base Docker
images.

https://hub.docker.com/r/adoptopenjdk/openjdk8

On Tue, Feb 26, 2019, 16:49 Richard Bywater  wrote:

> If the concern is regarding packaging, would it be worthwhile switching
> the images to drag in something like a AdoptOpenJDK archive and use that
> instead? (Presumably would need to create symlinks etc. for binaries). I
> took a look at the CentOS OpenJDK11 package and it was hard to tell how
> up-to-date it was given it seems to be from November 2018 but AdoptOpenJDK
> has a build from late January.
>
> Richard.
>
> On Wed, 27 Feb 2019 at 11:52, Mark Waite 
> wrote:
>
>>
>> On Tue, Feb 26, 2019 at 3:31 PM R. Tyler Croy 
>> wrote:
>>
>>> (replies inline)
>>>
>>> On Tue, 26 Feb 2019, Matt Sicker wrote:
>>>
>>> > Based on the details regarding Debian and Ubuntu's poor maintenance of
>>> JDK
>>> > packages, I'd support using a different distro like CentOS. That
>>> certainly
>>> > pushes myself away from defaulting to ubuntu or debian for Java Docker
>>> > images.
>>>
>>>
>>> Agreed! I think this is worthwhile to do. The first responsibility IMO
>>> of our
>>> containers is to provide the most stable and secure Jenkins environment
>>> for end
>>> users.
>>>
>>> We already maintain an Alpine image, to where if there are people
>>> depending on
>>> a Debian-based image, making that available as another set of tags is
>>> also
>>> always an option.
>>>
>>>
>> Adding tags for CentOS images seems least likely to break existing users.
>>
>> Since the base Jenkins docker image does not include certain critical
>> programs
>> (like "git-lfs"), I needed to extend the image by installing additional
>> packages with
>> the operating system package management system.  It works well and lets me
>> test interesting cases faster.
>>
>> If we add a CentOS image, I'm very much in favor of it.  +1 if so
>>
>> If we replace the Debian image with a CentOS image, that will be
>> disruptive
>> to me and those like me that needed additional operating system specific
>> extensions in the image.  I can adapt, but there will be others that will
>> grumble about adapting.
>>
>> Is the proposal to add CentOS or to replace Debian with CentOS?
>>
>> Mark Waite
>>
>>
>>>
>>> +1
>>>
>>> --
>>> GitHub:  https://github.com/rtyler
>>>
>>> GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2
>>>
>>> --
>>> 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+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/20190226223130.wbcx2dr6ln5lf2g4%40grape
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHk38Oi7zcKarTLZ_6L%2By12nmAa1o9-7VaAxn4MR2612g%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwczub-i9bouUoRyu%2BsSD7FcvBXu9yuEQVxHsa%3DFdo%3DsUw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcnJ7N%2B3iTQS9n3S4zJ7N4zHvWOBayoqXwK38Nm0kU93g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Switching to CentOS for Jenkins Docker base image

[Richard Bywater]

If the concern is regarding packaging, would it be worthwhile switching the
images to drag in something like a AdoptOpenJDK archive and use that
instead? (Presumably would need to create symlinks etc. for binaries). I
took a look at the CentOS OpenJDK11 package and it was hard to tell how
up-to-date it was given it seems to be from November 2018 but AdoptOpenJDK
has a build from late January.

Richard.

On Wed, 27 Feb 2019 at 11:52, Mark Waite  wrote:

>
> On Tue, Feb 26, 2019 at 3:31 PM R. Tyler Croy  wrote:
>
>> (replies inline)
>>
>> On Tue, 26 Feb 2019, Matt Sicker wrote:
>>
>> > Based on the details regarding Debian and Ubuntu's poor maintenance of
>> JDK
>> > packages, I'd support using a different distro like CentOS. That
>> certainly
>> > pushes myself away from defaulting to ubuntu or debian for Java Docker
>> > images.
>>
>>
>> Agreed! I think this is worthwhile to do. The first responsibility IMO of
>> our
>> containers is to provide the most stable and secure Jenkins environment
>> for end
>> users.
>>
>> We already maintain an Alpine image, to where if there are people
>> depending on
>> a Debian-based image, making that available as another set of tags is also
>> always an option.
>>
>>
> Adding tags for CentOS images seems least likely to break existing users.
>
> Since the base Jenkins docker image does not include certain critical
> programs
> (like "git-lfs"), I needed to extend the image by installing additional
> packages with
> the operating system package management system.  It works well and lets me
> test interesting cases faster.
>
> If we add a CentOS image, I'm very much in favor of it.  +1 if so
>
> If we replace the Debian image with a CentOS image, that will be disruptive
> to me and those like me that needed additional operating system specific
> extensions in the image.  I can adapt, but there will be others that will
> grumble about adapting.
>
> Is the proposal to add CentOS or to replace Debian with CentOS?
>
> Mark Waite
>
>
>>
>> +1
>>
>> --
>> GitHub:  https://github.com/rtyler
>>
>> GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/20190226223130.wbcx2dr6ln5lf2g4%40grape
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Thanks!
> Mark Waite
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHk38Oi7zcKarTLZ_6L%2By12nmAa1o9-7VaAxn4MR2612g%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwczub-i9bouUoRyu%2BsSD7FcvBXu9yuEQVxHsa%3DFdo%3DsUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Jennifer Briden]

Hello! Yes, we have prioritized those issues and a few minor UI
improvements.

Craig, I'd like to set up some time with you to introduce myself and
establish a way to more quickly and directly get your input. I will reach
out to you in email via my CloudBees address, if that works for you.

Jenn

On Tue, Feb 26, 2019, 15:32 Michael Neale  wrote:

> So just checking in on this excellent list as of this week:
>
>- https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a
>job in Blue Ocean - Looks like Gavin is starting this (sounded like some
>good progress).
>- https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does
>not group changes for multiple SCM providers by SCM - Nicu has started on
>that (shouldn't be major hopefully)
>- https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see
>executors in Blue Ocean UI - Craig can this be closed? as your changes
>merged in (once released) should resolve this
>- https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit build
>information in Blue ocean UI - This one will be probably the biggest one,
>and I am not sure how it can be tackled given build config can be highly
>dynamic based on plugins installed. If there is a way to scope this a bit
>better may make it easier to start.
>
>
>
>
> On Sunday, February 3, 2019 at 10:38:02 AM UTC+11, Craig Rodrigues wrote:
>>
>> Hi,
>>
>> I like the Blue Ocean UI a lot!  I am trying to use Blue Ocean
>> as my "daily driver" when interacting with Jenkins.
>> I spend a lot of my day starting/stopping jobs, examining logs,
>> editing build descriptions, and disabling/enabling builds.
>>
>> However, there are some gaps in the Blue Ocean UI.
>>
>> The gaps are small, but annoying enough that I need to keep switching
>> back to the classic UI.  This is annoying.
>>
>> I mentioned this in this other discussion thread:
>> https://groups.google.com/d/msg/jenkinsci-dev/zNukeuLK4Og/DGwWnJyGCAAJ
>> , but wanted to pull out this list to a separate discussion.
>>
>> Here are my top pet peeves, which I classify as "pot holes":
>>
>>
>>- https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a
>>job in Blue Ocean
>>- https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does
>>not group changes for multiple SCM providers by SCM
>>- https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see
>>executors in Blue Ocean UI
>>- https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit
>>build information in Blue ocean UI
>>
>>
>> If anyone wants to collaborate on fixing these bugs, please communicate
>> on the Gitter channel: https://gitter.im/jenkinsci/blueocean-plugin
>>
>> --
>> Craig
>>
>>
>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/46600b1b-9853-4648-abfc-3f9869ef27be%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAGuTKx%2BJJFKa9Tp%3DjNunEy%2Bz09degQXUZXTVkX%3D1mAqC4dRnmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Michael Neale]

So just checking in on this excellent list as of this week:

   - https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a 
   job in Blue Ocean - Looks like Gavin is starting this (sounded like some 
   good progress). 
   - https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does 
   not group changes for multiple SCM providers by SCM - Nicu has started on 
   that (shouldn't be major hopefully)
   - https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see 
   executors in Blue Ocean UI - Craig can this be closed? as your changes 
   merged in (once released) should resolve this
   - https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit build 
   information in Blue ocean UI - This one will be probably the biggest one, 
   and I am not sure how it can be tackled given build config can be highly 
   dynamic based on plugins installed. If there is a way to scope this a bit 
   better may make it easier to start. 




On Sunday, February 3, 2019 at 10:38:02 AM UTC+11, Craig Rodrigues wrote:
>
> Hi,
>
> I like the Blue Ocean UI a lot!  I am trying to use Blue Ocean
> as my "daily driver" when interacting with Jenkins.
> I spend a lot of my day starting/stopping jobs, examining logs,
> editing build descriptions, and disabling/enabling builds. 
>
> However, there are some gaps in the Blue Ocean UI.
>
> The gaps are small, but annoying enough that I need to keep switching
> back to the classic UI.  This is annoying.
>
> I mentioned this in this other discussion thread: 
> https://groups.google.com/d/msg/jenkinsci-dev/zNukeuLK4Og/DGwWnJyGCAAJ
> , but wanted to pull out this list to a separate discussion.
>
> Here are my top pet peeves, which I classify as "pot holes":
>
>
>- https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a 
>job in Blue Ocean
>- https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does 
>not group changes for multiple SCM providers by SCM
>- https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see 
>executors in Blue Ocean UI
>- https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit build 
>information in Blue ocean UI
>
>
> If anyone wants to collaborate on fixing these bugs, please communicate on 
> the Gitter channel: https://gitter.im/jenkinsci/blueocean-plugin
>
> --
> Craig
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/46600b1b-9853-4648-abfc-3f9869ef27be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Switching to CentOS for Jenkins Docker base image

[Mark Waite]

On Tue, Feb 26, 2019 at 3:31 PM R. Tyler Croy  wrote:

> (replies inline)
>
> On Tue, 26 Feb 2019, Matt Sicker wrote:
>
> > Based on the details regarding Debian and Ubuntu's poor maintenance of
> JDK
> > packages, I'd support using a different distro like CentOS. That
> certainly
> > pushes myself away from defaulting to ubuntu or debian for Java Docker
> > images.
>
>
> Agreed! I think this is worthwhile to do. The first responsibility IMO of
> our
> containers is to provide the most stable and secure Jenkins environment
> for end
> users.
>
> We already maintain an Alpine image, to where if there are people
> depending on
> a Debian-based image, making that available as another set of tags is also
> always an option.
>
>
Adding tags for CentOS images seems least likely to break existing users.

Since the base Jenkins docker image does not include certain critical
programs
(like "git-lfs"), I needed to extend the image by installing additional
packages with
the operating system package management system.  It works well and lets me
test interesting cases faster.

If we add a CentOS image, I'm very much in favor of it.  +1 if so

If we replace the Debian image with a CentOS image, that will be disruptive
to me and those like me that needed additional operating system specific
extensions in the image.  I can adapt, but there will be others that will
grumble about adapting.

Is the proposal to add CentOS or to replace Debian with CentOS?

Mark Waite


>
> +1
>
> --
> GitHub:  https://github.com/rtyler
>
> GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/20190226223130.wbcx2dr6ln5lf2g4%40grape
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHk38Oi7zcKarTLZ_6L%2By12nmAa1o9-7VaAxn4MR2612g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Switching to CentOS for Jenkins Docker base image

[R. Tyler Croy]

(replies inline)

On Tue, 26 Feb 2019, Matt Sicker wrote:

> Based on the details regarding Debian and Ubuntu's poor maintenance of JDK
> packages, I'd support using a different distro like CentOS. That certainly
> pushes myself away from defaulting to ubuntu or debian for Java Docker
> images.


Agreed! I think this is worthwhile to do. The first responsibility IMO of our
containers is to provide the most stable and secure Jenkins environment for end
users.

We already maintain an Alpine image, to where if there are people depending on
a Debian-based image, making that available as another set of tags is also
always an option. 


+1

--
GitHub:  https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/20190226223130.wbcx2dr6ln5lf2g4%40grape.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Switching to CentOS for Jenkins Docker base image

[Matt Sicker]

Based on the details regarding Debian and Ubuntu's poor maintenance of JDK
packages, I'd support using a different distro like CentOS. That certainly
pushes myself away from defaulting to ubuntu or debian for Java Docker
images.

On Tue, Feb 26, 2019 at 3:23 PM Baptiste Mathus  wrote:

> Hey everyone,
>
> We had a discussion at the regular Platform SIG meeting, and we thought we
> would socialize this idea/subject with a larger group of people.
>
> Many events or issues have recently collided that led many us to question
> the Docker image variants that the Jenkins Project provides, especially the
> base images that these are based on.
> Currently, we provide 3 variants, all are based on openjdk's provided
> images
> * Debian based
> * Debian Slim based (https://hub.docker.com/_/debian/#debiansuite-slim)
> * Alpine based
>
> Given a few recent events around Debian or Ubuntu JDK [1], we started
> thinking it might be good to switch to a different base image.
> (The situation around the JDK support is BTW even worse for Alpine. Which
> led to switching Evergreen already [2]).
>
> So we have started thinking CentOS would seem like a good alternative
> choice, given how central Java is to this platform in general.
> In this regard, going to Fedora could probably be a possibility too.
>
> We are really interested in hearing your opinions around this. Please
> voice your concerns, if any.
> If you think this sounds like a sensible move, please don't hesitate to
> let us know either :).
>
> Thanks!
>
> -- Baptiste
>
> [1] Summary of the recent JDK issues in Debian and Ubuntu
> 
> [2] The ticket for switching Evergreen to CentOS, already done
> https://issues.jenkins-ci.org/browse/JENKINS-55547
>
>
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7kdR1cqVaKsU7A4wOvyGWYyUrUKjAbtMCP6QC5oHpEjQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Matt Sicker
Software Engineer, CloudBees

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ow9m40A_zzX%3Dfxk7KT9GJiHVRnKshXSZMCRnVPpBDvW9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[DISCUSS] Switching to CentOS for Jenkins Docker base image

[Baptiste Mathus]

Hey everyone,

We had a discussion at the regular Platform SIG meeting, and we thought we
would socialize this idea/subject with a larger group of people.

Many events or issues have recently collided that led many us to question
the Docker image variants that the Jenkins Project provides, especially the
base images that these are based on.
Currently, we provide 3 variants, all are based on openjdk's provided images
* Debian based
* Debian Slim based (https://hub.docker.com/_/debian/#debiansuite-slim)
* Alpine based

Given a few recent events around Debian or Ubuntu JDK [1], we started
thinking it might be good to switch to a different base image.
(The situation around the JDK support is BTW even worse for Alpine. Which
led to switching Evergreen already [2]).

So we have started thinking CentOS would seem like a good alternative
choice, given how central Java is to this platform in general.
In this regard, going to Fedora could probably be a possibility too.

We are really interested in hearing your opinions around this. Please voice
your concerns, if any.
If you think this sounds like a sensible move, please don't hesitate to let
us know either :).

Thanks!

-- Baptiste

[1] Summary of the recent JDK issues in Debian and Ubuntu

[2] The ticket for switching Evergreen to CentOS, already done
https://issues.jenkins-ci.org/browse/JENKINS-55547

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7kdR1cqVaKsU7A4wOvyGWYyUrUKjAbtMCP6QC5oHpEjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Questions about developing pipeline DSL plugin

[liyudong123]

Hi all,
I'm a student from China University of Geosciences and I'm trying to create 
a pipeline compatible plugin. I have encountered some problems when I am 
learning the workflow-remote-loader-plugin 
 source code. 
Class FileLoaderDSLImpl 

 defines 
several methods for example withGit() . In the definition of this method it 
uses a local variable 'script' to call its methods like deleteDir() and 
checkout() (line 95).  But I cannot find the definition of checkout() in 
class CpsScript , could anyone tell me where this method is defined or how 
to use the variable 'script'?
Thank you for your time.
Li Yudong

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4461aefe-3373-45c1-bfb9-e8f65dbf4286%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Copying file from Master to slave

[Ullrich Hafner]

Additionally think carefully about the design of your code. Which part of the 
code should run on the master, which part on the slave. It might be also 
required to consider MasterToSlaveCallable.



> Am 26.02.2019 um 09:12 schrieb Joseph P :
> 
> You want to use FilePath class as much as possible, it has methods that work 
> regardless if it is on master or agent.
> 
> See the JavaDoc: https://javadoc.jenkins.io/hudson/FilePath.html
> 
> 
> On Tuesday, February 26, 2019 at 8:44:02 AM UTC+1, Nikhil Bhoski wrote:
> I have my plugin which creates a file in the jenkins workspace. however if i 
> configure slave and force the job to run on slave then i see file on slave is 
> not getting created.
> 
> I am using workspace.getRemote() to get the workspace path and Java 
> File.copy() utility to copy the file in workspace.getRemote() path . However 
> the file is not getting created on slave. Any suggestions to make it work ?
> 
> --
> 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+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/1e0a992a-6528-4f15-8399-e8ce0befb66f%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/DF3C31E1-BF8F-4D18-96E0-06EAE2459E1A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Copying file from Master to slave

[Joseph P]

You want to use FilePath class as much as possible, it has methods that 
work regardless if it is on master or agent.

See the JavaDoc: https://javadoc.jenkins.io/hudson/FilePath.html


On Tuesday, February 26, 2019 at 8:44:02 AM UTC+1, Nikhil Bhoski wrote:
>
> I have my plugin which creates a file in the jenkins workspace. however if 
> i configure slave and force the job to run on slave then i see file on 
> slave is not getting created. 
>
> I am using workspace.getRemote() to get the workspace path and Java 
> File.copy() utility to copy the file in workspace.getRemote() path . 
> However the file is not getting created on slave. Any suggestions to make 
> it work ?
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1e0a992a-6528-4f15-8399-e8ce0befb66f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.