Re: Maintainer of copy-editors group on GitHub?

[Oleg Nenashev]

FTR I cannot merge the permissions there, somebody else needs to grant the 
permissions

On Friday, April 17, 2020 at 5:42:23 PM UTC+2, Oleg Nenashev wrote:
>
> +1
>
> On Friday, April 17, 2020 at 4:13:29 PM UTC+2, Tim Jacomb wrote:
>>
>> +1
>>
>> You should have it due to your role as documentation officer imo
>>
>> On Fri, 17 Apr 2020 at 15:10, Mark Waite  wrote:
>>
>>> I'd like to be assigned as a maintainer of the copy-editors team on the 
>>> Jenkins CI GitHub account.
>>>
>>> Are there specific steps that I should take to be granted maintainer 
>>> permission to https://github.com/orgs/jenkins-infra/teams/copy-editors ?
>>>
>>> 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 jenkin...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/963caf2a-f552-493e-b21a-d22d7813608d%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/d6eccbd6-5c25-4b3e-b116-c64e195b3527%40googlegroups.com.

Re: Maintainer of copy-editors group on GitHub?

[Oleg Nenashev]

+1

On Friday, April 17, 2020 at 4:13:29 PM UTC+2, Tim Jacomb wrote:
>
> +1
>
> You should have it due to your role as documentation officer imo
>
> On Fri, 17 Apr 2020 at 15:10, Mark Waite  > wrote:
>
>> I'd like to be assigned as a maintainer of the copy-editors team on the 
>> Jenkins CI GitHub account.
>>
>> Are there specific steps that I should take to be granted maintainer 
>> permission to https://github.com/orgs/jenkins-infra/teams/copy-editors ?
>>
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/963caf2a-f552-493e-b21a-d22d7813608d%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/e4c10644-1d79-4105-bf8a-0adcd927c017%40googlegroups.com.

Re: Maintainer of copy-editors group on GitHub?

[Marky Jackson]

+1

> On Apr 17, 2020, at 7:13 AM, Tim Jacomb  wrote:
> 
> +1
> 
> You should have it due to your role as documentation officer imo
> 
> On Fri, 17 Apr 2020 at 15:10, Mark Waite  > wrote:
> I'd like to be assigned as a maintainer of the copy-editors team on the 
> Jenkins CI GitHub account.
> 
> Are there specific steps that I should take to be granted maintainer 
> permission to https://github.com/orgs/jenkins-infra/teams/copy-editors 
>  ?
> 
> 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/963caf2a-f552-493e-b21a-d22d7813608d%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/CAH-3Bid8Syvi1gGt8kUfJwoTCXY_EBQDhvn4qsMVkrbdm1%2BX0A%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/8BA98CA2-519B-4E3E-8AA8-39DC953E0449%40gmail.com.


signature.asc
Description: Message signed with OpenPGP

Re: Maintainer of copy-editors group on GitHub?

[Tim Jacomb]

+1

You should have it due to your role as documentation officer imo

On Fri, 17 Apr 2020 at 15:10, Mark Waite  wrote:

> I'd like to be assigned as a maintainer of the copy-editors team on the
> Jenkins CI GitHub account.
>
> Are there specific steps that I should take to be granted maintainer
> permission to https://github.com/orgs/jenkins-infra/teams/copy-editors ?
>
> 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/963caf2a-f552-493e-b21a-d22d7813608d%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/CAH-3Bid8Syvi1gGt8kUfJwoTCXY_EBQDhvn4qsMVkrbdm1%2BX0A%40mail.gmail.com.

Maintainer of copy-editors group on GitHub?

[Mark Waite]

I'd like to be assigned as a maintainer of the copy-editors team on the 
Jenkins CI GitHub account.

Are there specific steps that I should take to be granted maintainer 
permission to https://github.com/orgs/jenkins-infra/teams/copy-editors ?

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/963caf2a-f552-493e-b21a-d22d7813608d%40googlegroups.com.

Re: [jenkins-infra] Jenkins Core Release automation

[Kohsuke Kawaguchi]

Wow, congratulations!!

After 15 years and ~900 releases, this process has finally left my hands...


On Fri, Apr 17, 2020 at 2:32 AM Olblak  wrote:

> Hi Everybody
>
> Yesterday we released a weekly version from the new release environment
> and while we managed to ship our weekly version, we also faced unplanned
> issues that we had to solve so here a quick retro.
>
> The process was done in two stages the release and then the packaging
>
> Stage 1, Release:
>
> The release part, was the easiest one. We only add two issues.
> The first issue was due to the password used to authenticate on Maven
> repository, containing special characters that couldn't be parsed by Maven
> release plugin. We just changed the password.
> The second problem was a permission issue on repo.jenkins-ci.org which
> was easily fixed.
> In the result of this stage, as expected every artifact was pushed to
> repo.jenkins-ci.org
>
> Stage 2, Package:
>
> Well, this stage was more tricky as we heavily refactored that part while
> also heavily relying on existing service. We discovered multiple side cases
> that we didn't catch during the testing period and I will describe here the
> most important ones.
>
> *  GPG: While this was something that we discussed a long time ago we
> forgot to communicate in advance but the GPG key used to sign releases
> changed for weekly release in order to not use Kohsuke gpg key. In a result
> of this, people who use RedHat/Debian/Suse repository need to reimport the
> new key. Remark: this is something that will also have to be done for Lts
> once we also release Lts with the current process
>
> New
> Key:
> pub   rsa4096 2020-03-30 [SC] [expires: 2023-03-30]
>   62A9756BFD780C377CF24BA8FCEF32E745F2C3D5
> uid   Jenkins Project 
> sub   rsa4096 2020-03-30 [E] [expires: 2023-03-30].
>
> Old Key:
> pub   dsa1024 2009-02-01 [SC]
>   150FDE3F7787E7D11EF4E12A9B7D32F2D50582E6
> uid   Kohsuke Kawaguchi 
> uid   [jpeg image of size 3704]
> uid   Kohsuke Kawaguchi 
> uid   Kohsuke Kawaguchi 
> uid   Kohsuke Kawaguchi 
> sub   elg2048 2009-02-01 [E]
> sub   rsa4096 2016-11-01 [S]
>
> * mirror.jenkins-ci.org: This service has now additional Html files
> `HEADER.html` and `FOOTER.html` per directory. Those two files are used by
> apache directory listing to prepend and append Html information to the
> directory listing. The main advantage of this is to provide information
> from mirrors about how to install those packages from your operating system
> from every mirror. At least apache with the correct configuration, an
> example of this is
>
> http://mirrors.jenkins-ci.org/debian/ or
> http://archives.jenkins-ci.org/debian/
>
> Please note that the instruction to configure os package manager is
> referencing the wrong URL and it should be pkg.jenkins.io. A fix needs to
> be provided, other remark CSS needs to align with other Jenkins website if
> someone is willing to work on this, feel free to do, it's defined here
> https://github.com/jenkinsci/packaging/blob/INFRA-910-core-release-automation/templates/base.html
>
> * pkg.jenkins.io: this service is used by RedHat/Debian/Suse package
> manager to know which version can be installed, previously a list of
> packages that could be download from pkg.jenkins.io was generated for
> each release, this won't be the case anymore instead a link to mirrors
> should be provided. As a result of this, the latest weekly version is not
> listed even though you can easily craft an URL.
>
> We still have improvement coming and the next release can only be smoother.
>
> Thanks to Tim Jacob, Marky Jackson, Oleg Nenashev, Alex Earl, Mark Wait,
> Daniel Beck, Kohsuke, Oliver Ogondza who helped me to ship this first
> release yesterday but also to all the people who helped me, over the last
> two years to make this project a thing.
>
> Have a good day,
>
> Cheers
>
> On Wed, Apr 15, 2020, at 10:53 PM, Olblak wrote:
>
> After some discussion with the people involved in the process, I'll start
> at 11AM UTC instead of 3PM UTC, so we have more time to fix any unplanned
> issues.
>
> On Wed, Apr 15, 2020, at 9:51 AM, Oleg Nenashev wrote:
>
> I confirm my availability for tomorrow. Will also spend some time today to
> merge changes into the Jenkins core so that the release includes some real
> enhancements and fixes for Jenkins users.
>
> Regarding the schedule, it would be great to start the release process a
> bit earlier so that we have more time to fix issues if any. E.g. we could
> start the release Pipeline early so that artifacts are ready to packaging
> when US wakes up.
>
> Best regards,
> Oleg
>
>
>
> On Tuesday, April 14, 2020 at 9:04:03 PM UTC+2, Olblak wrote:
>
> Today, during the infra meeting, we discussed creating a new weekly
> release from the new process this Thursday the 16th at 3PM UTC.
> While there won't be major features, the purpose of this release is to
> validate that everything is working as expected in a 

Re: Read a file on jenkins slave workspace

[Mathieu Delrocq]

Thank you Jesse !! It is working now :)

Le vendredi 17 avril 2020 14:22:10 UTC+2, Jesse Glick a écrit :
>
> This code could not work because you were trying to read a local file 
> with a pathname that only exists on the agent. You cannot use 
> `java.io.File` nor `java.nio.file`, only methods on `FilePath`, e.g.: 
>
> String text = workspace.child(step.filePath).readToString(); 
>

-- 
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/bd8053eb-869f-4307-b526-d3259ddd40b1%40googlegroups.com.

RE: Plugin: Liquibase Runner

[Robert Reeves]

Thanks, Daniel!

Sounds like adoption is the way to go:

Link to a plugin you want to adopt: 
https://github.com/jenkinsci/liquibase-runner-plugin
Link(s) to pull requests you want to deliver, if applicable: 
https://github.com/jenkinsci/liquibase-runner-plugin/pull/16 and more to come 
after we get access to the security tracker
Your GitHub username/id: https://github.com/r2datical & 
https://github.com/nvoxland
Your Jenkins infrastructure account id. Create your account if you don’t have 
one: r2datical & nvoxland

Keith has been great and has stated he's open to getting some help on this the 
Liquibase team. We are indebted to him.

Thanks!

Robert


Robert Reeves
CTO | Datical


Mobile: 512 422 2443
Email: r...@datical.com
Website: www.datical.com












-Original Message-
From: Daniel Beck  
Sent: Friday, April 17, 2020 3:58 AM
To: Jenkins Developers 
Cc: Keith Collison ; Nathan Voxland ; 
Robert Reeves 
Subject: Re: Plugin: Liquibase Runner



> On 16. Apr 2020, at 20:16, Robert Reeves  wrote:
> 
> Just to follow up…we’re trying to get this security issue resolved but have 
> not been able to get access to SECURITY-519. How can we view that so we can 
> fix the issue?

As I wrote in a previous response, Keith's account has access to the issue. 
Since you're working with him per your first email in this thread, ask him for 
the details.

>From a Jenkins project POV, Keith is the only maintainer of the plugin, and 
>the only one entitled to view the security issue information for his plugin. 
>(While we can add additional users to the private issue, that requires consent 
>by the current maintainer.)

The only option that doesn't require active involvement from a current 
maintainer is to request a transfer of maintainership of the plugin per 
https://jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/

-- 
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/BN7PR06MB63706B8897B81CDD62B749FD83D90%40BN7PR06MB6370.namprd06.prod.outlook.com.

Re: Read a file on jenkins slave workspace

[Jesse Glick]

This code could not work because you were trying to read a local file
with a pathname that only exists on the agent. You cannot use
`java.io.File` nor `java.nio.file`, only methods on `FilePath`, e.g.:

String text = workspace.child(step.filePath).readToString();

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

Re: Addition to Copy Editors team

[Oleg Nenashev]

Thanks for your interest Sladyn! It is much appreciated.

Regarding the process, maybe we could introduce a 2-stage ladder for 
reviewers, similarly to what we did for Jenkins core.
Opinions?

Best regards,
Oleg

On Friday, April 17, 2020 at 1:16:30 PM UTC+2, Sladyn Nunes wrote:
>
> Hello everyone, 
> With respect to the email sent by Mark 
> https://groups.google.com/d/msg/jenkinsci-docs/aunhIJbOvbc/VKLH8VQTAQAJ. 
> I would like to help out the docs  team by being added to the copy editors 
> team,
> I have submitted a PR for my ICLA 
> https://github.com/jenkinsci/infra-cla/pull/88
> Thanks and Cheers
>

-- 
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/f9e3e7af-964c-443a-b2c7-6641daff26f8%40googlegroups.com.

Read a file on jenkins slave workspace

[Mathieu Delrocq]

Hello,

I develop a new Jenkins plugin for a mobile security app.
I have to read a file on the workspace of the build but I always got 
FileNotFoundException.

The build is executed on a docker container with docker-plugin.

I get the file with :


FilePath workspace = this.context.get(FilePath)
File file = new File(String.valueOf(workspace) + step.filePath)

byte[] filebytes = Files.readAllBytes(app.toPath())  < 
FileNotFoundException here



It is like my code is searching the file on my local machine but not on the 
docker container.

Do you know how to get a file on a Jenkins agent?

Thanks.

Mathieu DELROCQ


-- 
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/d3dd7e0a-cfa7-4ad0-b021-093b81cb23f5%40googlegroups.com.

Addition to Copy Editors team

[Sladyn Nunes]

Hello everyone, 
With respect to the email sent by Mark 
https://groups.google.com/d/msg/jenkinsci-docs/aunhIJbOvbc/VKLH8VQTAQAJ. I 
would like to help out the docs  team by being added to the copy editors 
team,
I have submitted a PR for my ICLA 
https://github.com/jenkinsci/infra-cla/pull/88
Thanks and Cheers

-- 
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/87f7a458-1112-4f72-a80c-61b7590bd037%40googlegroups.com.

Re: [jenkins-infra] Jenkins Core Release automation

[Olblak]

Hi Everybody

Yesterday we released a weekly version from the new release environment and 
while we managed to ship our weekly version, we also faced unplanned issues 
that we had to solve so here a quick retro.

The process was done in two stages the release and then the packaging

Stage 1, Release:

The release part, was the easiest one. We only add two issues.
The first issue was due to the password used to authenticate on Maven 
repository, containing special characters that couldn't be parsed by Maven 
release plugin. We just changed the password.
The second problem was a permission issue on repo.jenkins-ci.org which was 
easily fixed.
In the result of this stage, as expected every artifact was pushed to 
repo.jenkins-ci.org

Stage 2, Package:

Well, this stage was more tricky as we heavily refactored that part while also 
heavily relying on existing service. We discovered multiple side cases that we 
didn't catch during the testing period and I will describe here the most 
important ones.

* GPG: While this was something that we discussed a long time ago we forgot to 
communicate in advance but the GPG key used to sign releases changed for weekly 
release in order to not use Kohsuke gpg key. In a result of this, people who 
use RedHat/Debian/Suse repository need to reimport the new key. Remark: this is 
something that will also have to be done for Lts once we also release Lts with 
the current process

New Key: 
pub rsa4096 2020-03-30 [SC] [expires: 2023-03-30]
 62A9756BFD780C377CF24BA8FCEF32E745F2C3D5
uid Jenkins Project 
sub rsa4096 2020-03-30 [E] [expires: 2023-03-30].

Old Key:
pub dsa1024 2009-02-01 [SC]
 150FDE3F7787E7D11EF4E12A9B7D32F2D50582E6
uid Kohsuke Kawaguchi 
uid [jpeg image of size 3704]
uid Kohsuke Kawaguchi 
uid Kohsuke Kawaguchi 
uid Kohsuke Kawaguchi 
sub elg2048 2009-02-01 [E]
sub rsa4096 2016-11-01 [S]

* mirror.jenkins-ci.org: This service has now additional Html files 
`HEADER.html` and `FOOTER.html` per directory. Those two files are used by 
apache directory listing to prepend and append Html information to the 
directory listing. The main advantage of this is to provide information from 
mirrors about how to install those packages from your operating system from 
every mirror. At least apache with the correct configuration, an example of 
this is

http://mirrors.jenkins-ci.org/debian/ or http://archives.jenkins-ci.org/debian/

Please note that the instruction to configure os package manager is referencing 
the wrong URL and it should be pkg.jenkins.io. A fix needs to be provided, 
other remark CSS needs to align with other Jenkins website if someone is 
willing to work on this, feel free to do, it's defined here 
https://github.com/jenkinsci/packaging/blob/INFRA-910-core-release-automation/templates/base.html

* pkg.jenkins.io: this service is used by RedHat/Debian/Suse package manager to 
know which version can be installed, previously a list of packages that could 
be download from pkg.jenkins.io was generated for each release, this won't be 
the case anymore instead a link to mirrors should be provided. As a result of 
this, the latest weekly version is not listed even though you can easily craft 
an URL.

We still have improvement coming and the next release can only be smoother.

Thanks to Tim Jacob, Marky Jackson, Oleg Nenashev, Alex Earl, Mark Wait, Daniel 
Beck, Kohsuke, Oliver Ogondza who helped me to ship this first release 
yesterday but also to all the people who helped me, over the last two years to 
make this project a thing.

Have a good day,

Cheers

On Wed, Apr 15, 2020, at 10:53 PM, Olblak wrote:
> After some discussion with the people involved in the process, I'll start at 
> 11AM UTC instead of 3PM UTC, so we have more time to fix any unplanned issues.
> 
> On Wed, Apr 15, 2020, at 9:51 AM, Oleg Nenashev wrote:
>> I confirm my availability for tomorrow. Will also spend some time today to 
>> merge changes into the Jenkins core so that the release includes some real 
>> enhancements and fixes for Jenkins users.
>> 
>> Regarding the schedule, it would be great to start the release process a bit 
>> earlier so that we have more time to fix issues if any. E.g. we could start 
>> the release Pipeline early so that artifacts are ready to packaging when US 
>> wakes up.
>> 
>> Best regards,
>> Oleg
>> 
>> 
>> 
>> On Tuesday, April 14, 2020 at 9:04:03 PM UTC+2, Olblak wrote:
>>> Today, during the infra meeting, we discussed creating a new weekly release 
>>> from the new process this Thursday the 16th at 3PM UTC.
>>> While there won't be major features, the purpose of this release is to 
>>> validate that everything is working as expected in a real scenario.
>>> 
>>> 
>>> I am proposing the following agenda
>>> 
>>> 
>>> * 3PM(UTC), I start the release job and we release directly to the master 
>>> branch and directly on repo.jenkins-ci.org/releases.
>>> Currently the release job take approximatively 1h30
>>> 
>>> 
>>> * 4:30PM(UTC), or early if ready, I start 

Re: Plugin: Liquibase Runner

[Daniel Beck]

> On 16. Apr 2020, at 20:16, Robert Reeves  wrote:
> 
> Just to follow up…we’re trying to get this security issue resolved but have 
> not been able to get access to SECURITY-519. How can we view that so we can 
> fix the issue?

As I wrote in a previous response, Keith's account has access to the issue. 
Since you're working with him per your first email in this thread, ask him for 
the details.

>From a Jenkins project POV, Keith is the only maintainer of the plugin, and 
>the only one entitled to view the security issue information for his plugin. 
>(While we can add additional users to the private issue, that requires consent 
>by the current maintainer.)

The only option that doesn't require active involvement from a current 
maintainer is to request a transfer of maintainership of the plugin per 
https://jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/

-- 
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/6C7D5AFB-2AF8-4BD8-8C76-5A07E3CC279B%40beckweb.net.

Addition to copy editors team

[Vlad Silverman]

Hello,

I would like to be added to the copy editors team.
Please see below several of my recent pull requests:

https://github.com/jenkinsci/infra-cla/pull/87 


https://github.com/jenkins-infra/jenkins.io/pull/3069 


https://github.com/jenkins-infra/jenkins.io/pull/3061 


https://github.com/vsilverman/jenkins-ci/pull/3 


https://github.com/vsilverman/jenkins-ci/pull/4 


https://github.com/vsilverman/jenkins-ci/pull/5 


Thx, Vlad
https://vsilverman.github.io/jenkins-ci/ 


-- 
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/F1857606-EDF8-4A97-8515-B804D6832846%40gmail.com.