Re: Propose viglesiasce as maintainer for Google Source Plugin

['Vic Iglesias' via Jenkins Developers]

I believe I've gotten all the ducks in a row. Can someone flip the bit?

https://github.com/jenkinsci/google-source-plugin/issues/10


On Thursday, October 10, 2019 at 3:27:52 PM UTC-7, Marky Jackson wrote:
>
> Thanks Vic
>
> On Oct 10, 2019, at 3:26 PM, 'Vic Iglesias' via Jenkins Developers <
> jenkin...@googlegroups.com > wrote:
>
> Thanks folks!
>
> Issue created here:
> https://github.com/jenkinsci/google-source-plugin/issues/10
>
> On Thursday, October 10, 2019 at 10:08:50 AM UTC-7, Marky Jackson wrote:
>>
>> Thank you kindly Andrey!
>>
>> On Oct 10, 2019, at 9:58 AM, Andrey Stroilov  wrote:
>>
>> Confirming approval for this. Will +1 issue when it is created.
>>
>> On Wed, Oct 9, 2019 at 6:41 PM Marky Jackson  wrote:
>>
>>> Can you also open an issue in that repo and have Andrey +1 there?
>>>
>>> On Oct 9, 2019, at 2:02 PM, 'Vic Iglesias' via Jenkins Developers <
>>> jenkin...@googlegroups.com> wrote:
>>>
>>> I'd like to propose myself as maintainer of the Google Source Plugin 
>>> .
>>>
>>> GitHub: https://github.com/viglesiasce
>>>
>>> The plugin is currently in a broken state due to using deprecated APIs. 
>>> I'd like to be able to merge a fix which builds on a patch from last year 
>>> from Oleg:
>>> https://github.com/jenkinsci/google-source-plugin/pull/9
>>>
>>> +Andrey Stroilov (current maintainer) has agreed.
>>>
>>> Thanks,
>>>
>>> Vic
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAAQDQ4hMr-wRLvdEWu9j2rJSGuSubk4vJv%3D916kZE30EW4O5rA%40mail.gmail.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 jenkin...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/759ff463-faa8-4794-a5fe-1a8d6f13969f%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/cc873889-adea-4dfd-8ccb-aadcc10a8372%40googlegroups.com.

Re: 2019 Elections: voting is delayed

[Richard Bywater]

Given that there's been a few people who have requested to be removed from
the list, would it make sense for the election nomination process to be
updated whereby a nominee has to accept their nomination?

The worst case scenario is that someone doesn't spot that they've been
nominated and ends up elected even though they have no wish. Obviously not
likely to end up in that position but appears it would be a possibility
with the current process.

Richard.

On Sat, 19 Oct 2019, 1:14 PM Kohsuke Kawaguchi,  wrote:

> Updated
> https://docs.google.com/document/d/15rJYkBjWLGZTL87xeJ4P2Y1LNn7C0EBb0wkDVUSfLmQ/edit#
>
> On Fri, Oct 18, 2019 at 9:36 AM Marky Jackson 
> wrote:
>
>> Sitting here with Oleg and just found out that I am included in the board
>> member elections, I withdraw my nomination for the board position.
>> I would like to continue forth on the infra officer nomination.
>>
>>
>> {
>> "regards" : {
>>  "name" : “marky”,
>>  "phone" : "+1 (408) 464 2965 <+1%20(408)%20464%202965>”,
>>  "email" : “marky.r.jack...@gmail.com",
>>  "team" : “jackson5“,
>>  “role” : “software engineer"
>>  }
>>  }
>>
>> On Oct 15, 2019, at 3:02 PM, Kohsuke Kawaguchi  wrote:
>>
>> 
>> The proposed time table that we published earlier had Oct 14th as the
>> start of voting, but due to a logistical challenge of running a vote with
>> this many people, we need a bit more time to sort this out.
>>
>> So the start of voting will be delayed. I currently do not have an ETA,
>> but hopefully it shouldn't take too long.
>>
>> --
>> Kohsuke Kawaguchi
>>
>> --
>> 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/CAN4CQ4zGX0zaavFELOovrbtr%3DoefOXrTEKDan-Mu2Z4TMTOYcA%40mail.gmail.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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/2A7682DC-F9FB-4B40-801A-3F6910FC4899%40gmail.com
>> 
>> .
>>
>
>
> --
> Kohsuke Kawaguchi
>
> --
> 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/CAN4CQ4wnEQ-n78k1b9XZ40vk3ewb5jU4jzUMzNskQq9AG0sZ_Q%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hweRTN55%3DMOFnRF2QJ-bQCgJvzp6JSt7j2G%2BTGPKKPzDQQ%40mail.gmail.com.

Re: 2019 Elections: voting is delayed

[Kohsuke Kawaguchi]

Updated
https://docs.google.com/document/d/15rJYkBjWLGZTL87xeJ4P2Y1LNn7C0EBb0wkDVUSfLmQ/edit#

On Fri, Oct 18, 2019 at 9:36 AM Marky Jackson 
wrote:

> Sitting here with Oleg and just found out that I am included in the board
> member elections, I withdraw my nomination for the board position.
> I would like to continue forth on the infra officer nomination.
>
>
> {
> "regards" : {
>  "name" : “marky”,
>  "phone" : "+1 (408) 464 2965 <+1%20(408)%20464%202965>”,
>  "email" : “marky.r.jack...@gmail.com",
>  "team" : “jackson5“,
>  “role” : “software engineer"
>  }
>  }
>
> On Oct 15, 2019, at 3:02 PM, Kohsuke Kawaguchi  wrote:
>
> 
> The proposed time table that we published earlier had Oct 14th as the
> start of voting, but due to a logistical challenge of running a vote with
> this many people, we need a bit more time to sort this out.
>
> So the start of voting will be delayed. I currently do not have an ETA,
> but hopefully it shouldn't take too long.
>
> --
> Kohsuke Kawaguchi
>
> --
> 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/CAN4CQ4zGX0zaavFELOovrbtr%3DoefOXrTEKDan-Mu2Z4TMTOYcA%40mail.gmail.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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/2A7682DC-F9FB-4B40-801A-3F6910FC4899%40gmail.com
> 
> .
>


-- 
Kohsuke Kawaguchi

-- 
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/CAN4CQ4wnEQ-n78k1b9XZ40vk3ewb5jU4jzUMzNskQq9AG0sZ_Q%40mail.gmail.com.

Re: Proposal to switch from OpenJDK to AdoptOpenJDK

[Mark Waite]

Thanks very much for starting the discussion.

I'm interested in evaluating the switch from OpenJDK to AdoptOpenJDK.  I've
been using JDK 8 and 11 hotspot builds from AdoptOpenJDK for many months
with very good results.

Several of the OpenJDK providers (Red Hat, Amazon, Azul) seem to be
limiting their platform support much more than AdoptOpenJDK does.  So long
as we can get the platforms we need (Debian, CentOS, UBI), I'm interested
in evaluating the change.

I thought there were specific barriers that prevent Alpine Linux support,
though I see that Azul provides an Alpine Linux build for 8, 11, and 13.

On Fri, Oct 18, 2019 at 2:09 PM Jim Crowley  wrote:

> I posted this proposal on GitHub,
> https://github.com/jenkinsci/docker/issues/893, but also wanted to get
> the feedback of the community here.
>
>
>
>
> As we start to look into supporting multiple architectures, we might want
> to pivot from using OpenJDK to AdoptOpenJDK. There are couple reasons
> behind this.
>
>
>
> First, it makes our build scripts and Dockerfiles easier to maintain.
> Currently, in publish-experimental.sh, we have logic that handles pulling
> from the “right” OpenJDK for a specific architecture. This could be remove
> as the AdoptOpenJDK Docker image, https://hub.docker.com/_/adoptopenjdk,
> has a manifest file that will handle pulling the correct image for the
> given architecture.
>
>
>
>
>
> Second, the OpenJDK image’s we are pulling from to build out our
> multi-arch images, s390x/ openjdk:8-jdk, arm32v7/openjdk:8-jdk, etc. will
> not be updated anymore. This has to do with OpenJDK not publishing
> “official” binaries for these architectures. More information on this issue
> can be found here,
> https://github.com/docker-library/openjdk/issues/364#issuecomment-540821603
> .
>
>
>
>
>
> Third, this would pair nicely with the proposal to add OpenJ9,
> https://github.com/jenkinsci/docker/issues/884. The AdoptOpenJDK image
> has tags that support OpenJ9, so it should not be to much more work to
> support this additional tag for our Jenkins images.
>
>
>
> The only roadblock right now is the base image/tag support the official
> AdoptOpenJDK image on DockerHub. Currently, they only support an Ubuntu and
> Widows Server Core base image. I talked with the Adopt team, Alpine and
> Debian, Ubi base images are coming down the pipeline. This is aimed at the
> next PR to the official DockerHub image repository. CentOS/ClefOS are also
> coming but I do not have an ETA.
>
> Now we could wait for the official image or we could use the unofficial
> images the Adopt team does produce. Using the unofficial images does
> provide us with Alpine, Debian, etc support quicker. But they will be
> unofficial images, which I know some users do not like to use.
>
>
> Either way, I wanted to get community feedback! So please let me know what
> you think of this proposal.
>
> --
> 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/6eb646a8-6835-4720-beca-9afe95fa0ca0%40googlegroups.com
> 
> .
>


-- 
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/CAO49JtGVshvshWpfU2iJbCDRsttOttA9yEF4z3%2Bq7Ve6wYAe6g%40mail.gmail.com.

Re: 2.190.1 and 2019-09-25 security advisory

[Daniel Beck]

> On 18. Oct 2019, at 17:40, Jim Sinclair  wrote:
> 
> Can you please update the Security advisory to include 2.190.1 if it applies?

Our security advisories don't list which releases have the fix, it only lists 
the first release of each release line (in the case of core, weekly and LTS) to 
have the fix. All subsequent releases are implied. So 2.190.1 isn't listed 
because it is the successor of 2.176.4.

The reason it appears in the LTS changelog for 2.190.1 is that the section 
"changes since 2.190" specifically lists, well, everything that is new in 
2.190.1 compared 2.190. This section is basically irrelevant to admins who are 
on the LTS line anyway, but it makes sense to document somewhere what changed 
over 2.190. It's very unusual that we need to back port something to a ".1" LTS 
release that was already in a previous LTS release, but is has happened before, 
and would always be listed here.

Note how the August 28 advisory is also mentioned in the same changelog entry, 
since those fixes were only in the 2.192 weekly and therefore had to be 
backported. Yet, that advisory doesn't mention 2.190.1 either, and for the same 
reason as in the September 25 advisory: In neither case was it the first LTS 
release containing the fixes.

I added the note for 2.176.4, because it was not a regularly scheduled release. 
According to https://jenkins.io/download/lts/ this release should not exist, 
and the note explains why it does anyway.

-- 
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/7B10CA47-A706-4613-8CF2-48CC87A722DF%40beckweb.net.

Proposal to switch from OpenJDK to AdoptOpenJDK

[Jim Crowley]

 

I posted this proposal on GitHub, 
https://github.com/jenkinsci/docker/issues/893, but also wanted to get the 
feedback of the community here.

 


As we start to look into supporting multiple architectures, we might want 
to pivot from using OpenJDK to AdoptOpenJDK. There are couple reasons 
behind this.

 

First, it makes our build scripts and Dockerfiles easier to maintain. 
Currently, in publish-experimental.sh, we have logic that handles pulling 
from the “right” OpenJDK for a specific architecture. This could be remove 
as the AdoptOpenJDK Docker image, https://hub.docker.com/_/adoptopenjdk, 
has a manifest file that will handle pulling the correct image for the 
given architecture. 

 

 

Second, the OpenJDK image’s we are pulling from to build out our multi-arch 
images, s390x/ openjdk:8-jdk, arm32v7/openjdk:8-jdk, etc. will not be 
updated anymore. This has to do with OpenJDK not publishing “official” 
binaries for these architectures. More information on this issue can be 
found here, 
https://github.com/docker-library/openjdk/issues/364#issuecomment-540821603.

 

 

Third, this would pair nicely with the proposal to add OpenJ9, 
https://github.com/jenkinsci/docker/issues/884. The AdoptOpenJDK image has 
tags that support OpenJ9, so it should not be to much more work to support 
this additional tag for our Jenkins images.



The only roadblock right now is the base image/tag support the official 
AdoptOpenJDK image on DockerHub. Currently, they only support an Ubuntu and 
Widows Server Core base image. I talked with the Adopt team, Alpine and 
Debian, Ubi base images are coming down the pipeline. This is aimed at the 
next PR to the official DockerHub image repository. CentOS/ClefOS are also 
coming but I do not have an ETA.

Now we could wait for the official image or we could use the unofficial 
images the Adopt team does produce. Using the unofficial images does 
provide us with Alpine, Debian, etc support quicker. But they will be 
unofficial images, which I know some users do not like to use.


Either way, I wanted to get community feedback! So please let me know what 
you think of this proposal. 

-- 
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/6eb646a8-6835-4720-beca-9afe95fa0ca0%40googlegroups.com.

Re: 2.190.1 and 2019-09-25 security advisory

[Jesse Glick]

On Fri, Oct 18, 2019 at 1:15 PM Jim Sinclair  wrote:
> Can you please update the Security advisory

I was about to suggest you simply

https://github.com/jenkins-infra/jenkins.io/edit/master/content//security/advisory/2019-09-25.adoc

until I noticed that this part of the advisory is generated from YAML
and the generator may not support multiple values for `fixed`. If in
doubt, file a ticket under `INFRA`.

-- 
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/CANfRfr3ZQ%3DSf8t9T%3DLJyW8%3D7F-wL_W60LhT%2BoT9-uwJs8AUJkA%40mail.gmail.com.

2.190.1 and 2019-09-25 security advisory

[Jim Sinclair]

The 2019-09-25 Security Advisory 
 has:
*Affected Versions * 
   
   - Jenkins weekly up to and including 2.196 
   - Jenkins LTS up to and including 2.176.3 

*Fix* 
   
   - Jenkins weekly should be updated to version 2.197 
   - Jenkins LTS should be updated to version 2.176.4 


However the LTS Changelog  has:
*What's new in 2.190.1 (2019-09-25)*
Changes since 2.190: 

   - Important security fixes. (2019-09-25 security advisory 
   , 2019-08-28 security 
   advisory ) 

*Also under 2.176.4:*
2.176.4 and 2.190.1 contain the same security fixes.

Can you please update the Security advisory to include 2.190.1 if it 
applies?

--Jim Sinclair

-- 
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/71b31c9e-b2a4-4096-be3c-a2133ff9409c%40googlegroups.com.

Re: Plugin Pull Request Approval

[Julio Guereca]

Thank you for the information! I have been trying to work with the original 
maintainer and was hoping there would be a workaround!

On Wednesday, October 16, 2019 at 10:32:34 PM UTC-7, Ullrich Hafner wrote:
>
>
> Am 16.10.2019 um 19:58 schrieb Julio Guereca  >:
>
> Hi All!!
>
> I am attempting to merge a pull request for a plugin (
> https://github.com/jenkinsci/bigpanda-plugin/pull/1)
>
> Reading through some instructions, I did attempt to create a Jira ticket 
> but could not find the *bigpanda-plugin *for the component field and 
> didn't feel like I could move forward on this.
>
> I would like to know how I can either get this Pull Request approved or 
> how I can approve it myself
>
>
> Pull requests can only by approved by the development team of a plugin. So 
> you need to wait for an approval (or merge) from that team. Since the last 
> commit is five years ago I doubt that you get any responses. (I would help 
> though that your PR title describes the actual changes in the PR).
>
> Did you already ping the developers of the plugin? Maybe this plugin looks 
> for a new maintainer anyway...
>
> This is my first time attempting to publish a plugin for Jenkins so any 
> guidance would be greatly appreciated.
>
> Thank you again for your time
>
> -- 
> 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 jenkin...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/22253d28-1c67-4413-b15f-9a2a7eedcb19%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/27445249-d00f-4c4a-942e-a1fd56a07cc8%40googlegroups.com.

Re: Plugin Pull Request Approval

[Julio Guereca]

Hi Oleg, 

Thank you for responding. I've responded to some messages on the Pull 
Request and hopefully that does provide some additional clarify on my 
changes. 

In such a case that the changes are deprecating the old functionality of a 
plugin, is it a better practice to publish a new plugin all together. 

I am aware the current state of the plugin should be in use by anyone and 
therefore I am not concerned about impacting users.

On Thursday, October 17, 2019 at 3:27:55 PM UTC-7, Oleg Nenashev wrote:
>
> I am not sure what this pull request does.
> My first impression is that it is rather a new plugin suggested on the top 
> of existing one, with breaking changes for current users
>
> On Thursday, October 17, 2019 at 7:32:34 AM UTC+2, Ullrich Hafner wrote:
>>
>>
>> Am 16.10.2019 um 19:58 schrieb Julio Guereca :
>>
>> Hi All!!
>>
>> I am attempting to merge a pull request for a plugin (
>> https://github.com/jenkinsci/bigpanda-plugin/pull/1)
>>
>> Reading through some instructions, I did attempt to create a Jira ticket 
>> but could not find the *bigpanda-plugin *for the component field and 
>> didn't feel like I could move forward on this.
>>
>> I would like to know how I can either get this Pull Request approved or 
>> how I can approve it myself
>>
>>
>> Pull requests can only by approved by the development team of a plugin. 
>> So you need to wait for an approval (or merge) from that team. Since the 
>> last commit is five years ago I doubt that you get any responses. (I would 
>> help though that your PR title describes the actual changes in the PR).
>>
>> Did you already ping the developers of the plugin? Maybe this plugin 
>> looks for a new maintainer anyway...
>>
>> This is my first time attempting to publish a plugin for Jenkins so any 
>> guidance would be greatly appreciated.
>>
>> Thank you again for your time
>>
>> -- 
>> 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 jenkin...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/22253d28-1c67-4413-b15f-9a2a7eedcb19%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3df0496a-1441-4873-87f5-54b9c4b2d0fa%40googlegroups.com.

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

[Tim Jacomb]

Could use GitHub topics? Or just add to the readme

On Fri, 18 Oct 2019 at 15:24, Robert Sandell  wrote:

> And how do I mark a plugin as up for adoption without the wiki labels?
>
> /B
>
> Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick :
>
>> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  wrote:
>> > I propose that we restore write access for plugin maintainers at least
>> for a time, to allow them to clear out wiki pages after migrating the
>> content elsewhere.
>>
>> Makes sense, but is there some plan to notify maintainers of plugins
>> who have not done this? There are a couple thousand pages out there,
>> and many people will not see mailing list notifications reliably.
>>
>> --
>> 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/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com
>> .
>>
>
>
> --
> *Robert Sandell*
> Software Engineer
> CloudBees, Inc.
> [image: CloudBees-Logo.png] 
> E: rsand...@cloudbees.com
> Twitter: robert_sandell
>
> --
> 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/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicsFkKUJQJb6bdBDK-L2AGmTFKo6oNo_eRwigu1da7%2BTw%40mail.gmail.com.

Re: 2019 Elections: voting is delayed

[Marky Jackson]

Sitting here with Oleg and just found out that I am included in the board 
member elections, I withdraw my nomination for the board position.
I would like to continue forth on the infra officer nomination.


{ 
"regards" : {
 "name" : “marky”,
 "phone" : "+1 (408) 464 2965”,
 "email" : “marky.r.jack...@gmail.com",
 "team" : “jackson5“,
 “role” : “software engineer"
 }
 }

> On Oct 15, 2019, at 3:02 PM, Kohsuke Kawaguchi  wrote:
> 
> 
> The proposed time table that we published earlier had Oct 14th as the start 
> of voting, but due to a logistical challenge of running a vote with this many 
> people, we need a bit more time to sort this out.
> 
> So the start of voting will be delayed. I currently do not have an ETA, but 
> hopefully it shouldn't take too long.
> 
> -- 
> Kohsuke Kawaguchi
> -- 
> 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/CAN4CQ4zGX0zaavFELOovrbtr%3DoefOXrTEKDan-Mu2Z4TMTOYcA%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2A7682DC-F9FB-4B40-801A-3F6910FC4899%40gmail.com.

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

[Robert Sandell]

And how do I mark a plugin as up for adoption without the wiki labels?

/B

Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick :

> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  wrote:
> > I propose that we restore write access for plugin maintainers at least
> for a time, to allow them to clear out wiki pages after migrating the
> content elsewhere.
>
> Makes sense, but is there some plan to notify maintainers of plugins
> who have not done this? There are a couple thousand pages out there,
> and many people will not see mailing list notifications reliably.
>
> --
> 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/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] 
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com.

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

[Jesse Glick]

On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  wrote:
> I propose that we restore write access for plugin maintainers at least for a 
> time, to allow them to clear out wiki pages after migrating the content 
> elsewhere.

Makes sense, but is there some plan to notify maintainers of plugins
who have not done this? There are a couple thousand pages out there,
and many people will not see mailing list notifications reliably.

-- 
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/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com.

Re: Request to be made maintainer of PowerShell Plugin

[Oleg Nenashev]

Hi Filippe,

Thanks for stepping up!

Could you please create a pull request to 
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-powershell.yml
 ?
Approval from Chris in this pull request will be enough to do the transfer.

Best regards,
Oleg


On Friday, October 18, 2019 at 12:07:12 PM UTC+2, Filipe Roque wrote:
>
> Hi, 
>
> The current maintener https://github.com/damienfinck doesn't seem active. 
>
> He is no longer the for the keyboard-shortcuts-plugin due to inactivity 
> and not responding:
>
> https://groups.google.com/forum/#!msg/jenkinsci-dev/OQRDRC8ZBH4/ug1OwT_CAgAJ
>
> There is another maintener https://github.com/chrisalbrecht, but he is 
> not able to develop with java and maven at the moment. 
>
> See:  
> 
> https://github.com/jenkinsci/powershell-plugin/pull/7#issuecomment-537015437
>
> github.com username: froque
> jenkins.io account: froque
>
> Thanks,
> Filipe Roque
>

-- 
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/5bd1a5ea-c0d4-49c4-a4f1-86181250a1a3%40googlegroups.com.

ANN - DevOps World - Jenkins World: Hackfest on December 02

[Oleg Nenashev]

Hi all,

There are many Jenkins contributors who are going to DevOps World - Jenkins 
World Lisbon  on December 
03-05. As it was previously announced, there will be Jenkins and Jenkins X 
contributor summits on Dec 03 (meetup page 
). In addition to 
that, on Dec 02 Advocacy and Outreach SIG will be organizing a 
hackathon/workshop for those who arrive early. It will be a full day even, 
the exact schedule will be announced later.

We invite Jenkins developers and users to join us and to work together on 
improving Jenkins, topics are to be discussed and selected by the 
participants. Your current experience with Jenkins does not matter, 
newcomers are welcome to join us and to do their first contributions! We 
will have experienced Jenkins maintainers at the event, and they will be 
happy to provide advice and ad-hoc knowledge transfer sessions.

If you are interested to participate, please sign up in this Google Doc 
.
 
Also, please feel free to propose your topics or to vote for existing ones.

Best regards,
Oleg Nenashev

P.S: All event participants are eligible for a 30% discount for the 
conference. And thanks to CloudBees for sponsoring the hackathon! 


-- 
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/e0be0c73-3f20-416f-9762-59d6c46541a4%40googlegroups.com.

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

[Daniel Beck]

> On 17. Oct 2019, at 17:05, Olblak  wrote:
> 
>> Don't we have a feature in Confluence to add a big warning in top of pages, 
>> for people logged in, to point them to this thread or so? 
> 
> I added that warning message 

It shows for everyone, but that way it prepares everyone for the eventual (I 
guess?) shutdown of the wiki.

> 
>> I am all for migrating content from Confluence to GitHub
>> (`jenkins-infra/
>> jenkins.io
>> `, `jenkinsci/*-plugin`, etc.), but we would
>> still need write access to Confluence at a minimum to delete the
>> content from a page and replace it with a note saying where the new
>> content lives!
>> 
> 
> Can we just add that information on top of every page, something like "The 
> content of this page is deprecated in favor of plugins.jenkins.io/ id>"
> 

I propose that we restore write access for plugin maintainers at least for a 
time, to allow them to clear out wiki pages after migrating the content 
elsewhere. The script for that basically exists at 
https://github.com/jenkins-infra/wiki-maintainers-updater -- grant write access 
only to that group and you're basically done.

Combined with the giant notice on top (perhaps slightly reworded) it should be 
clear that this is temporary, and the expectation is for the content to be 
moved, rather than just edited.

-- 
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/F195BE53-AE9A-42F9-94D1-EE87D5A22943%40beckweb.net.

Request to be made maintainer of PowerShell Plugin

['Filipe Roque' via Jenkins Developers]

Hi,

The current maintener https://github.com/damienfinck doesn't seem active.

He is no longer the for the keyboard-shortcuts-plugin due to inactivity and not 
responding:
https://groups.google.com/forum/#!msg/jenkinsci-dev/OQRDRC8ZBH4/ug1OwT_CAgAJ

There is another maintener https://github.com/chrisalbrecht, but he is not able 
to develop with java and maven at the moment.

See: 
 
https://github.com/jenkinsci/powershell-plugin/pull/7#issuecomment-537015437

github.com username: froque
jenkins.io account: froque

Thanks,
Filipe Roque

-- 
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/21185a58f8f1f3a82966b5d235b64261e6ff9632.camel%40premium-minds.com.

Re: Query on Jenkins pipeline Stash/Unstash

[Ullrich Hafner]

Please use the users mailing list for such questions.

> Am 18.10.2019 um 04:23 schrieb alok kumar :
> 
> Hello everyone,
> Can someone please let me know where do the files get stored when we stash 
> them in Jenkins pipeline?
> 
> Thanks
> Alok
> 
> -- 
> 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/CAOqqq4SLSxjY%3DeC9qzUonBOcokExkqAq4B67Ho6rn-8UPUn64g%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/066AE74A-8655-4047-A0CF-429530C3934E%40gmail.com.

Re: how to check build command result like pipeline.

[Ullrich Hafner]

Please use the users mailing list for such questions.

> Am 18.10.2019 um 04:09 schrieb jonghoon,jeon :
> 
> Hi, 
> 
> I want to check build command result like pipeline.
> 
> Now, I don't use pipeline job. I only have Freestyle projects.
> 
> But I saw pipeline project, and I could see the results for every stage on 
> project's summary page.
> 
> I cant use many plugin in pipeline project.
> 
> I want to see the results for every build command on current project's 
> summary page.
> 
> Is there this plugin like pipeline plugin?
> 
> 
> <캡처.JPG>
> 
> 
> 
> -- 
> 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/193c2c85-f9f1-4e9b-bfcc-cd9a7ed6317f%40googlegroups.com
>  
> .
> <캡처.JPG>

-- 
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/4EFAC8D9-B7B0-4D4F-9E44-379018BE11F9%40gmail.com.