Repository: jenkins-infra/contributor-spotlight
Pull request #306: Contributor Spotlight for Yaroslav Afenkin
Author: login: kmartens27
Created: 2025-03-18T17:35:05Z | Merged: 2025-03-24T14:22:08Z

This PR is to add the spotlight page for Yaroslav Afenkin. It includes his avatar image and changes the feature flag on the previous spotlight to false. It also includes some updates that were made during the local build.

Pending review from Yaroslav, it would be great to have this published this week, but if it is not ready until next week, that is fine. I have not put a publication date in the title for this reason.

cc: @yaroslavafenkin for review and feedback.


Diff:
diff --git a/src/pages/contributors/kohsuke-kawaguchi.adoc b/src/pages/contributors/kohsuke-kawaguchi.adoc
index a26a82c8..9a1f8616 100644
--- a/src/pages/contributors/kohsuke-kawaguchi.adoc
+++ b/src/pages/contributors/kohsuke-kawaguchi.adoc
@@ -9,7 +9,7 @@
 :page-location: San Jose, California, United States
 :page-firstcommit: 2004
 :page-datepublished: 2025-02-10
-:page-featured: true
+:page-featured: false
 :page-intro: Originally from Tokyo, Japan, and now residing in San Jose, California, Kohsuke Kawaguchi is the creator of Jenkins. After getting his first taste for technology thanks to his mother, Kohsuke soon turned this interest into a profession. Despite starting in high school, he followed through on this passion in college and eventually landed a job that brought him to Silicon Valley. This journey became even more high-stakes when he decided to get married and move to the United States, all in one sweeping change. Born from a time when Kohsuke would often be the only person at night still working, Jenkins started out as just another project. Over the years, Kohsuke has seen numerous changes to the project, the community, the technological world that we exist in, and the possibilities that Jenkins is capable of.
 
 == What is your background prior to creating Jenkins?
diff --git a/src/pages/contributors/yaroslav-afenkin.adoc b/src/pages/contributors/yaroslav-afenkin.adoc
new file mode 100644
index 00000000..e3eb0836
--- /dev/null
+++ b/src/pages/contributors/yaroslav-afenkin.adoc
@@ -0,0 +1,98 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2021
+:page-datepublished: 2025-03-24
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had up to seven hours of English a week.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine to study Computer Science, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using software called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result, I landed on a project with a heavy Java stack, using Java 8, Spring, Hibernate on the back end, and AngularJS and Angular on the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and JavaScript skills.
+I worked there for three years while I finished university, staying in Poland.
+Then Covid happened and for personal reasons, I eventually moved back to Ukraine.
+I had to leave my job since they did not offer remote work, but I found a new one at CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go, and I had a preference for security.
+This is how I ended up in the Jenkins security team at CloudBees, and that's how I gained most of the Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2025/01/16/jenkins-csp-project-update/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We only had CI at the time, as we were using Gerrit for code review and Jenkins for builds.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for software that we were building.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspect of Jenkins that interested you when you got started or that you found more useful?
+
+At the time, there was one colleague who is also a member of the community, Damian Szczepanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks for our project.
+I was interested, but I wasn't necessarily "allowed" to enter that area because I had other things to work on.
+It was still attractive to me, but I didn't get to work on Jenkins while I was working at my original company.
+However, when I was changing jobs I had an opportunity to interview with someone who explained that the work would be for Jenkins, and specifically security, which instantly sold me on the job.
+I was never a big fan of enterprise businesses like insurance or banking, it's always been a little boring for me.
+I'm more a fan of heavier technical things like Jenkins and other more developer-focused work.
+So, it was easy for me to get excited when I heard they're hiring for a Jenkins project.
+
+== What problems have you worked on in Jenkins?
+
+The CSP work was fairly narrow as it was focused on enhancing the Jenkins CSP.
+There are several archetypes of issues and I was familiar with how you approach a certain problem or how you solve it because we had some initiatives when I was originally working in the Jenkins security team.
+We were working on CSP stuff in Jenkins core, so we weren't touching plugins, but most of the issues that I have faced during the CSP project I was already familiar with how to approach them.
+When it comes to the Jenkins security team, the work that I was doing was part of the overall responsibilities of the team such as code review, fixing vulnerabilities in Jenkins core, and security advisories just to name a few.
+
+In regards to the challenges of the CSP project, it was not due to Jenkins or CSP, but JavaScript being JavaScript.
+There were some subtle, but very technical JavaScript caveats that needed to be addressed.
+Those problems were partially due to users not willing to leverage what Jenkins already has.
+For instance, it has the Jelly engine for views and people were trying to add JavaScript frameworks, such as React or Angular to that.
+The custom implementations contributed to some issues in their own way because those implementations were not fitting into the archetypes of issues that we were already familiar with and knew how to solve.
+So we had to figure out the framework first and see if there was a mechanism that allows you to enforce CSP.
+Then we had to try using it and depending on how old the technology was, the mechanism could exist or not exist.
+From there, you had to cook up something different to come up with a solution.
+
+==  Is there any part of Jenkins that you've found especially interesting?
+
+I think extensibility is the real power of Jenkins.
+If something doesn't exist, you can either look at the plugin ecosystem or in the worst case, you can just write it yourself.
+It's great because you can basically use Jenkins for whatever task you can come up with.
+Taking it one step further, if you want to automate the task you can most likely do it in Jenkins if you spend enough time.
+For instance, performance tests are not a very regular use case as far as I'm concerned, as most people use it to build software or publish, but in my first job we implemented performance tests.
+This is an example of a quirky way to use Jenkins.
+
+While fixing CSP issues, we would also fix any core vulnerabilities that are out there.
+For example, some vulnerabilities are caused by incorrect usage of JavaScript (due to developers cutting corners or being unaware).
+This could be something like usage of `eval` or using inline scripts on HTML elements.
+These incorrect usages create XSS sinks if unsanitized user input is supplied to them.
+If CSP is set with a policy that is strict enough, those vulnerabilities wouldn't exist because the scripts wouldn't run.
+
+== Any advice for new developers or new users looking to join the open-source community or Jenkins project?
+
+Read a lot of code and try to really understand what the code is doing.
+If you want to add some functionality or change an existing functionality, just read a lot.
+Really try to understand how it may impact extensibility.
+This understanding is crucial when contributing to a project because there is lots of history behind the code.
diff --git a/static/avatar/yaroslav-afenkin.jpg b/static/avatar/yaroslav-afenkin.jpg
new file mode 100644
index 00000000..1b012f34
Binary files /dev/null and b/static/avatar/yaroslav-afenkin.jpg differ
diff --git a/styles/index.css b/styles/index.css
index e7b0312f..0b5b0db8 100644
--- a/styles/index.css
+++ b/styles/index.css
@@ -5,10 +5,11 @@
 }
 html,
 body {
-    font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', 'Roboto',
-        'Roboto Light', 'Oxygen', 'Ubuntu', 'Cantarell', 'Fira Sans',
-        'Droid Sans', 'Helvetica Neue', sans-serif, 'Apple Color Emoji',
-        'Segoe UI Emoji', 'Segoe UI Symbol';
+    font-family:
+        -apple-system, BlinkMacSystemFont, 'Segoe UI', 'Roboto', 'Roboto Light',
+        'Oxygen', 'Ubuntu', 'Cantarell', 'Fira Sans', 'Droid Sans',
+        'Helvetica Neue', sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji',
+        'Segoe UI Symbol';
     font-size: 16px;
 }
 
diff --git a/updatecli/updatecli.d/nodejs.yaml b/updatecli/updatecli.d/nodejs.yaml
index 461fd143..49dc5d71 100644
--- a/updatecli/updatecli.d/nodejs.yaml
+++ b/updatecli/updatecli.d/nodejs.yaml
@@ -2,52 +2,52 @@
 name: Bump `nodejs` version according to packer-images
 
 scms:
-  default:
-    kind: github
-    spec:
-      user: "{{ .github.user }}"
-      email: "{{ .github.email }}"
-      owner: "{{ .github.owner }}"
-      repository: "{{ .github.repository }}"
-      token: "{{ requiredEnv .github.token }}"
-      username: "{{ .github.username }}"
-      branch: "{{ .github.branch }}"
+    default:
+        kind: github
+        spec:
+            user: '{{ .github.user }}'
+            email: '{{ .github.email }}'
+            owner: '{{ .github.owner }}'
+            repository: '{{ .github.repository }}'
+            token: '{{ requiredEnv .github.token }}'
+            username: '{{ .github.username }}'
+            branch: '{{ .github.branch }}'
 
 sources:
-  ciJenkinsIoPackerImageVersion:
-    kind: yaml
-    name: Get the packer-image version deployed on ci.jenkins.io agents
-    spec:
-      file: https://raw.githubusercontent.com/jenkins-infra/jenkins-infra/production/hieradata/common.yaml
-      key: $.profile::jenkinscontroller::jcasc.agent_images.azure_vms_gallery_image.version
-  packerImageNodeVersion:
-    kind: yaml
-    name: Get  the `nodejs_linux_version` set in the deployed packer-image
-    dependson:
-      - ciJenkinsIoPackerImageVersion
-    spec:
-      file: https://raw.githubusercontent.com/jenkins-infra/packer-images/{{ source "ciJenkinsIoPackerImageVersion" }}/provisioning/tools-versions.yml
-      key: $.nodejs_linux_version
+    ciJenkinsIoPackerImageVersion:
+        kind: yaml
+        name: Get the packer-image version deployed on ci.jenkins.io agents
+        spec:
+            file: https://raw.githubusercontent.com/jenkins-infra/jenkins-infra/production/hieradata/common.yaml
+            key: $.profile::jenkinscontroller::jcasc.agent_images.azure_vms_gallery_image.version
+    packerImageNodeVersion:
+        kind: yaml
+        name: Get  the `nodejs_linux_version` set in the deployed packer-image
+        dependson:
+            - ciJenkinsIoPackerImageVersion
+        spec:
+            file: https://raw.githubusercontent.com/jenkins-infra/packer-images/{{ source "ciJenkinsIoPackerImageVersion" }}/provisioning/tools-versions.yml
+            key: $.nodejs_linux_version
 
 targets:
-  updateToolVersions:
-    name: bump `nodejs` version to {{ source "packerImageNodeVersion" }} in .tool-versions
-    sourceid: packerImageNodeVersion
-    kind: file
-    spec:
-      file: .tool-versions
-      matchpattern: >
-        nodejs (.*)
-      replacepattern: >
-        nodejs {{ source "packerImageNodeVersion" }}
-    scmid: default
+    updateToolVersions:
+        name: bump `nodejs` version to {{ source "packerImageNodeVersion" }} in .tool-versions
+        sourceid: packerImageNodeVersion
+        kind: file
+        spec:
+            file: .tool-versions
+            matchpattern: >
+                nodejs (.*)
+            replacepattern: >
+                nodejs {{ source "packerImageNodeVersion" }}
+        scmid: default
 
 actions:
-  default:
-    kind: github/pullrequest
-    title: Bump `nodejs` version to {{ source "packerImageNodeVersion" }}
-    scmid: default
-    spec:
-      labels:
-        - dependencies
-        - nodejs
+    default:
+        kind: github/pullrequest
+        title: Bump `nodejs` version to {{ source "packerImageNodeVersion" }}
+        scmid: default
+        spec:
+            labels:
+                - dependencies
+                - nodejs
diff --git a/updatecli/values.yaml b/updatecli/values.yaml
index b8a2bd10..16d72fc4 100644
--- a/updatecli/values.yaml
+++ b/updatecli/values.yaml
@@ -1,8 +1,8 @@
 github:
-  user: "Jenkins Infra Bot (updatecli)"
-  email: "60776566+jenkins-infra-bot@users.noreply.github.com"
-  username: "jenkins-infra-bot"
-  token: "UPDATECLI_GITHUB_TOKEN"
-  branch: "main"
-  owner: "jenkins-infra"
-  repository: "contributor-spotlight"
+    user: 'Jenkins Infra Bot (updatecli)'
+    email: '60776566+jenkins-infra-bot@users.noreply.github.com'
+    username: 'jenkins-infra-bot'
+    token: 'UPDATECLI_GITHUB_TOKEN'
+    branch: 'main'
+    owner: 'jenkins-infra'
+    repository: 'contributor-spotlight'


Reviews:
user: login: gounthar
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-18T17:46:25Z
user: login: liamfield
body: Lgtm! 

A couple of typos, and I can't help but copy edit as I go 😅 

Feel free to ignore any of the stylistic changes if you disagree, or want to retain the less formal tone of Yaroslav's words.
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T08:40:27Z
user: login: yaroslavafenkin
state: COMMENTED
author_association: NONE
submitted_at: 2025-03-19T10:41:43Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T14:10:29Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T14:14:51Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T14:17:44Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T14:19:53Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T14:21:06Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T15:40:20Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T15:40:43Z
user: login: yaroslavafenkin
state: COMMENTED
author_association: NONE
submitted_at: 2025-03-19T17:03:32Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T18:23:06Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T18:24:22Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-19T18:25:23Z
user: login: yaroslavafenkin
body: The rest looks good to me
state: COMMENTED
author_association: NONE
submitted_at: 2025-03-20T10:21:13Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-20T12:51:56Z
user: login: kmartens27
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-20T14:47:02Z
user: login: krisstern
body: LGTM
state: DISMISSED
author_association: MEMBER
submitted_at: 2025-03-20T19:48:51Z
user: login: yaroslavafenkin
body: LGTM
state: APPROVED
author_association: NONE
submitted_at: 2025-03-24T08:50:24Z
user: login: gounthar
body: Everything looks great now! Thanks so much for your hard work, everyone! 🙏
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-03-24T14:11:23Z

Review comments:
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed my most of my Java and Javascript skills.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: gounthar
body: ```suggestion
That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
```
created_at: 2025-03-18T17:42:45Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed my most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks.
+I was interested, but I wasn't necessarily "allowed" to enter that area because I had other things to work on.
+It was still attractive to me, but I didn't get to work on Jenkins while I was working at my original company.
+However, when I was changing jobs I had an opportunity to interview with someone and heard the word Jenkins which instantly got me invested and wanting to participate in the interview.
+I was never a big fan of enterprise businesses like insurance or banking, it's always been a little boring for me.
+I'm more a fan of heavier technical things like Jenkins and other more developer-focused work.
+So, it was easy for me to get excited when I heard they're hiring for a Jenkins project.
+
+== what problems have you worked on in Jenkins
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: gounthar
body: ```suggestion
== What problems have you worked on in Jenkins
```
created_at: 2025-03-18T17:45:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: liamfield
body: ```suggestion
:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
```
created_at: 2025-03-19T08:24:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: liamfield
body: ```suggestion
I went to school in Ukraine and it was heavy on English, so I had up to seven hours of English a day.
```
created_at: 2025-03-19T08:26:58Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: liamfield
body: ```suggestion
They were using software called Guidewire.
```
created_at: 2025-03-19T08:28:14Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: liamfield
body: ```suggestion
As a result, I landed on a project with a heavy Java stack, using Java Spring and Angular on the front end.
```
created_at: 2025-03-19T08:30:26Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: liamfield
body: ```suggestion
I worked there for three years while I finished university, staying in Poland.
```
created_at: 2025-03-19T08:31:26Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: liamfield
body: ```suggestion
This meant that I had to leave my job, but I found a new one at CloudBees.
```
created_at: 2025-03-19T08:32:14Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: liamfield
body: ```suggestion
As my project was coming to an end, we were asked where we wanted to go, and I had a preference for security.
```
created_at: 2025-03-19T08:32:31Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: liamfield
body: ```suggestion
This is how I ended up in the Jenkins security team at CloudBees, and that's how I gained most of the Jenkins skills that I have right now.
```
created_at: 2025-03-19T08:32:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: liamfield
body: ```suggestion
But there were some micro projects where I had to do performance tests for software that we were using.
```
created_at: 2025-03-19T08:33:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks.
+I was interested, but I wasn't necessarily "allowed" to enter that area because I had other things to work on.
+It was still attractive to me, but I didn't get to work on Jenkins while I was working at my original company.
+However, when I was changing jobs I had an opportunity to interview with someone and heard the word Jenkins which instantly got me invested and wanting to participate in the interview.
+I was never a big fan of enterprise businesses like insurance or banking, it's always been a little boring for me.
+I'm more a fan of heavier technical things like Jenkins and other more developer-focused work.
+So, it was easy for me to get excited when I heard they're hiring for a Jenkins project.
+
+== What problems have you worked on in Jenkins
+
+The CSP work was fairly narrow as it was focused on enhancing the Jenkins CSP.
+There are several archetypes of issues and I was familiar with how you approach a certain problem or how you solve it because we had some initiatives when I was originally working in the Jenkins security team.
+We were working on CSP stuff in Jenkins core, so we weren't touching plugins, but most of the issues that I have faced during the CSP project I was already familiar with how to approach them.
+When it comes to the Jenkins security team, the work that I was doing was part of the overall responsibilities of the team such as code review, fixing vulnerabilities in Jenkins core, and security advisories just to name a few.
+
+In regards to the challenges of the CSP project, it was not due to Jenkins or CSP, but JavaScript being Javascript.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: liamfield
body: ```suggestion
In regards to the challenges of the CSP project, it was not due to Jenkins or CSP, but JavaScript being JavaScript.
```
created_at: 2025-03-19T08:36:41Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks.
+I was interested, but I wasn't necessarily "allowed" to enter that area because I had other things to work on.
+It was still attractive to me, but I didn't get to work on Jenkins while I was working at my original company.
+However, when I was changing jobs I had an opportunity to interview with someone and heard the word Jenkins which instantly got me invested and wanting to participate in the interview.
+I was never a big fan of enterprise businesses like insurance or banking, it's always been a little boring for me.
+I'm more a fan of heavier technical things like Jenkins and other more developer-focused work.
+So, it was easy for me to get excited when I heard they're hiring for a Jenkins project.
+
+== What problems have you worked on in Jenkins
+
+The CSP work was fairly narrow as it was focused on enhancing the Jenkins CSP.
+There are several archetypes of issues and I was familiar with how you approach a certain problem or how you solve it because we had some initiatives when I was originally working in the Jenkins security team.
+We were working on CSP stuff in Jenkins core, so we weren't touching plugins, but most of the issues that I have faced during the CSP project I was already familiar with how to approach them.
+When it comes to the Jenkins security team, the work that I was doing was part of the overall responsibilities of the team such as code review, fixing vulnerabilities in Jenkins core, and security advisories just to name a few.
+
+In regards to the challenges of the CSP project, it was not due to Jenkins or CSP, but JavaScript being Javascript.
+There were some subtle, but very technical JavaScript caveats that needed to be addressed.
+Those problems were partially due to users not willing to leverage what Jenkins already has.
+For instance, it has the Jelly engine for views and people were trying to add JavaScript frameworks, such as React or Angular to that.
+The custom implementations contributed to some issues in their own way because those implementations were not fitting into the archetypes of issues that we were already familiar with and knew how to solve.
+So we had to figure out the framework first and see if there is a mechanism that allows you to enforce CSP.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: liamfield
body: ```suggestion
So we had to figure out the framework first and see if there was a mechanism that allows you to enforce CSP.
```
created_at: 2025-03-19T08:37:28Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: This gives an impression I've moved back because of covid, though it's not really the case :P
I think we can say I've moved back to Ukraine for personal reasons. The company I was working in didn't have remote work option, so I had to move further.
created_at: 2025-03-19T10:01:16Z
author_association: NONE
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: ```suggestion
There was one guy who is also a member of the community, Damian Szczepanik.
```

I guess we can call him a colleague who was working on the same project as me. Right now it feels like he's a random person :D
created_at: 2025-03-19T10:08:38Z
author_association: NONE
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks.
+I was interested, but I wasn't necessarily "allowed" to enter that area because I had other things to work on.
+It was still attractive to me, but I didn't get to work on Jenkins while I was working at my original company.
+However, when I was changing jobs I had an opportunity to interview with someone and heard the word Jenkins which instantly got me invested and wanting to participate in the interview.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: Not that I heard the word :P
It was communicated very directly that they're looking for a person to work on Jenkins (and around the security stuff if I remember correctly) so I was immediately sold 😁
created_at: 2025-03-19T10:12:20Z
author_association: NONE
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: FWIW
```suggestion
He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks for our project.
```

(we still had de jure admins who were doing admin work on the rest of the instance, as there were other projects, teams, etc.)
created_at: 2025-03-19T10:17:07Z
author_association: NONE
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks.
+I was interested, but I wasn't necessarily "allowed" to enter that area because I had other things to work on.
+It was still attractive to me, but I didn't get to work on Jenkins while I was working at my original company.
+However, when I was changing jobs I had an opportunity to interview with someone and heard the word Jenkins which instantly got me invested and wanting to participate in the interview.
+I was never a big fan of enterprise businesses like insurance or banking, it's always been a little boring for me.
+I'm more a fan of heavier technical things like Jenkins and other more developer-focused work.
+So, it was easy for me to get excited when I heard they're hiring for a Jenkins project.
+
+== What problems have you worked on in Jenkins
+
+The CSP work was fairly narrow as it was focused on enhancing the Jenkins CSP.
+There are several archetypes of issues and I was familiar with how you approach a certain problem or how you solve it because we had some initiatives when I was originally working in the Jenkins security team.
+We were working on CSP stuff in Jenkins core, so we weren't touching plugins, but most of the issues that I have faced during the CSP project I was already familiar with how to approach them.
+When it comes to the Jenkins security team, the work that I was doing was part of the overall responsibilities of the team such as code review, fixing vulnerabilities in Jenkins core, and security advisories just to name a few.
+
+In regards to the challenges of the CSP project, it was not due to Jenkins or CSP, but JavaScript being Javascript.
+There were some subtle, but very technical JavaScript caveats that needed to be addressed.
+Those problems were partially due to users not willing to leverage what Jenkins already has.
+For instance, it has the Jelly engine for views and people were trying to add JavaScript frameworks, such as React or Angular to that.
+The custom implementations contributed to some issues in their own way because those implementations were not fitting into the archetypes of issues that we were already familiar with and knew how to solve.
+So we had to figure out the framework first and see if there is a mechanism that allows you to enforce CSP.
+Then we had to try using it and depending on how old the technology was, the mechanism could exist or not exist.
+From there, you had to cook up something different to come up with a solution.
+
+==  Is there any part of Jenkins that you've taken a special liking to or found especially interesting?
+
+I think extensibility is the real power of Jenkins.
+If something doesn't exist, you can either look at the plugin ecosystem or in the worst case, you can just write it yourself.
+It's great because you can basically use Jenkins for whatever task you can come up with.
+Taking it one step further, if you want to automate the task you can most likely do it in Jenkins if you spend enough time.
+For instance, performance tests are not a very regular use case as far as I'm concerned, as most people use it to build software or publish, but in my first job we implemented performance tests.
+This is an example of a quirky way to use Jenkins.
+
+While fixing CSP issues, at the same time we would fix vulnerabilities that are out there.
+Security vulnerabilities like Severance or XSS, which have high impact on CVSS scores, so those are the kind of vulnerabilities that need to be addressed.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: Not entirely sure what's meant here, I'll try to rephrase.

It's that some vulnerabilities are caused by incorrect usage of JavaScript (due to developers cutting corners or being unaware), like e.g. usage of `eval` or using inline scripts on HTML elements. These create XSS sinks if unsanitized user input is supplied to them. If CSP is set with a policy that is strict enough then those vulnerabilities wouldn't exist, as scripts won't run.
created_at: 2025-03-19T10:31:48Z
author_association: NONE
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks.
+I was interested, but I wasn't necessarily "allowed" to enter that area because I had other things to work on.
+It was still attractive to me, but I didn't get to work on Jenkins while I was working at my original company.
+However, when I was changing jobs I had an opportunity to interview with someone and heard the word Jenkins which instantly got me invested and wanting to participate in the interview.
+I was never a big fan of enterprise businesses like insurance or banking, it's always been a little boring for me.
+I'm more a fan of heavier technical things like Jenkins and other more developer-focused work.
+So, it was easy for me to get excited when I heard they're hiring for a Jenkins project.
+
+== What problems have you worked on in Jenkins
+
+The CSP work was fairly narrow as it was focused on enhancing the Jenkins CSP.
+There are several archetypes of issues and I was familiar with how you approach a certain problem or how you solve it because we had some initiatives when I was originally working in the Jenkins security team.
+We were working on CSP stuff in Jenkins core, so we weren't touching plugins, but most of the issues that I have faced during the CSP project I was already familiar with how to approach them.
+When it comes to the Jenkins security team, the work that I was doing was part of the overall responsibilities of the team such as code review, fixing vulnerabilities in Jenkins core, and security advisories just to name a few.
+
+In regards to the challenges of the CSP project, it was not due to Jenkins or CSP, but JavaScript being Javascript.
+There were some subtle, but very technical JavaScript caveats that needed to be addressed.
+Those problems were partially due to users not willing to leverage what Jenkins already has.
+For instance, it has the Jelly engine for views and people were trying to add JavaScript frameworks, such as React or Angular to that.
+The custom implementations contributed to some issues in their own way because those implementations were not fitting into the archetypes of issues that we were already familiar with and knew how to solve.
+So we had to figure out the framework first and see if there is a mechanism that allows you to enforce CSP.
+Then we had to try using it and depending on how old the technology was, the mechanism could exist or not exist.
+From there, you had to cook up something different to come up with a solution.
+
+==  Is there any part of Jenkins that you've taken a special liking to or found especially interesting?
+
+I think extensibility is the real power of Jenkins.
+If something doesn't exist, you can either look at the plugin ecosystem or in the worst case, you can just write it yourself.
+It's great because you can basically use Jenkins for whatever task you can come up with.
+Taking it one step further, if you want to automate the task you can most likely do it in Jenkins if you spend enough time.
+For instance, performance tests are not a very regular use case as far as I'm concerned, as most people use it to build software or publish, but in my first job we implemented performance tests.
+This is an example of a quirky way to use Jenkins.
+
+While fixing CSP issues, at the same time we would fix vulnerabilities that are out there.
+Security vulnerabilities like Severance or XSS, which have high impact on CVSS scores, so those are the kind of vulnerabilities that need to be addressed.
+While on the Jenkins security team, fixing core security vulnerabilities was of course part of the typical work.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: While it is part of the work, I'd say it was rather rare, compared to other typical tasks. Core doesn't have that many holes :)
created_at: 2025-03-19T10:33:54Z
author_association: NONE
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: Is this first commit ever, or first commit to Jenkins? :o
created_at: 2025-03-19T10:35:34Z
author_association: NONE
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: ```suggestion
I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a week.
```
created_at: 2025-03-19T10:37:18Z
author_association: NONE
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: FWIW was studying Computer Science both in Ukraine and in Poland.
created_at: 2025-03-19T10:39:01Z
author_association: NONE
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: It would be the first commit to Jenkins. I tried to base it off the timeline we had during our conversation, as I forgot to ask about it directly.
created_at: 2025-03-19T14:10:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: Thanks very much for the clarification, I was trying to be careful about not sharing unwanted details but if that changes the actual events, then I've got that updated.
created_at: 2025-03-19T14:14:51Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: Thanks for the correction on the spelling here, I was trying to find him to confirm the spelling but was not close with the last name.
created_at: 2025-03-19T14:17:44Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks.
+I was interested, but I wasn't necessarily "allowed" to enter that area because I had other things to work on.
+It was still attractive to me, but I didn't get to work on Jenkins while I was working at my original company.
+However, when I was changing jobs I had an opportunity to interview with someone and heard the word Jenkins which instantly got me invested and wanting to participate in the interview.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: Awesome, thanks for the clarification here as well!
created_at: 2025-03-19T14:19:53Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: Ah, okay that makes sense. Thanks very much!
created_at: 2025-03-19T14:21:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks.
+I was interested, but I wasn't necessarily "allowed" to enter that area because I had other things to work on.
+It was still attractive to me, but I didn't get to work on Jenkins while I was working at my original company.
+However, when I was changing jobs I had an opportunity to interview with someone and heard the word Jenkins which instantly got me invested and wanting to participate in the interview.
+I was never a big fan of enterprise businesses like insurance or banking, it's always been a little boring for me.
+I'm more a fan of heavier technical things like Jenkins and other more developer-focused work.
+So, it was easy for me to get excited when I heard they're hiring for a Jenkins project.
+
+== What problems have you worked on in Jenkins
+
+The CSP work was fairly narrow as it was focused on enhancing the Jenkins CSP.
+There are several archetypes of issues and I was familiar with how you approach a certain problem or how you solve it because we had some initiatives when I was originally working in the Jenkins security team.
+We were working on CSP stuff in Jenkins core, so we weren't touching plugins, but most of the issues that I have faced during the CSP project I was already familiar with how to approach them.
+When it comes to the Jenkins security team, the work that I was doing was part of the overall responsibilities of the team such as code review, fixing vulnerabilities in Jenkins core, and security advisories just to name a few.
+
+In regards to the challenges of the CSP project, it was not due to Jenkins or CSP, but JavaScript being Javascript.
+There were some subtle, but very technical JavaScript caveats that needed to be addressed.
+Those problems were partially due to users not willing to leverage what Jenkins already has.
+For instance, it has the Jelly engine for views and people were trying to add JavaScript frameworks, such as React or Angular to that.
+The custom implementations contributed to some issues in their own way because those implementations were not fitting into the archetypes of issues that we were already familiar with and knew how to solve.
+So we had to figure out the framework first and see if there is a mechanism that allows you to enforce CSP.
+Then we had to try using it and depending on how old the technology was, the mechanism could exist or not exist.
+From there, you had to cook up something different to come up with a solution.
+
+==  Is there any part of Jenkins that you've taken a special liking to or found especially interesting?
+
+I think extensibility is the real power of Jenkins.
+If something doesn't exist, you can either look at the plugin ecosystem or in the worst case, you can just write it yourself.
+It's great because you can basically use Jenkins for whatever task you can come up with.
+Taking it one step further, if you want to automate the task you can most likely do it in Jenkins if you spend enough time.
+For instance, performance tests are not a very regular use case as far as I'm concerned, as most people use it to build software or publish, but in my first job we implemented performance tests.
+This is an example of a quirky way to use Jenkins.
+
+While fixing CSP issues, at the same time we would fix vulnerabilities that are out there.
+Security vulnerabilities like Severance or XSS, which have high impact on CVSS scores, so those are the kind of vulnerabilities that need to be addressed.
+While on the Jenkins security team, fixing core security vulnerabilities was of course part of the typical work.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: Thanks for the clarification @yaroslavafenkin 
created_at: 2025-03-19T15:40:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based out of Odesa, Ukraine and has been involved with the Jenkins project in multiple instances throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had about five to seven hours of English a day.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using a suite was called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result of this, I landed on a project with a very heavy Java stack, Java Spring, and Angular in the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I ended up working there for three years while I finished university and stayed in Poland.
+Then Covid happened and for various reasons, I eventually moved back to Ukraine.
+This meant that I had to leave my job, but I found a new job and ended up in CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go and I had a preference for security.
+This is how I ended up in the Jenkins security team in CloudBees and that's how I gained most of my Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for a software that we were using.
+I used Jenkins for it, despite not being sure it was optimal for my purposes, but that's one notable thing I can think of. 
+
+Other than that, I wasn't necessarily a heavy user of Jenkins.
+Most of my work has been done on Jenkins instead of through Jenkins.
+It's not like I need Jenkins during my daily life outside of the job.
+I'm trying to keep the balance between spending time in front of a PC doing work stuff and my spare time.
+So, I'm just trying to relax a bit in my spare time and keep work at work.
+
+== Was there any other aspects of Jenkins that interested you when you got started with it or that you found a little bit more useful?
+
+There was one guy who is also a member of the community, Damien Strapanik.
+He sat right behind me and he was our de-facto admin since he was doing most of the admin tasks.
+I was interested, but I wasn't necessarily "allowed" to enter that area because I had other things to work on.
+It was still attractive to me, but I didn't get to work on Jenkins while I was working at my original company.
+However, when I was changing jobs I had an opportunity to interview with someone and heard the word Jenkins which instantly got me invested and wanting to participate in the interview.
+I was never a big fan of enterprise businesses like insurance or banking, it's always been a little boring for me.
+I'm more a fan of heavier technical things like Jenkins and other more developer-focused work.
+So, it was easy for me to get excited when I heard they're hiring for a Jenkins project.
+
+== What problems have you worked on in Jenkins
+
+The CSP work was fairly narrow as it was focused on enhancing the Jenkins CSP.
+There are several archetypes of issues and I was familiar with how you approach a certain problem or how you solve it because we had some initiatives when I was originally working in the Jenkins security team.
+We were working on CSP stuff in Jenkins core, so we weren't touching plugins, but most of the issues that I have faced during the CSP project I was already familiar with how to approach them.
+When it comes to the Jenkins security team, the work that I was doing was part of the overall responsibilities of the team such as code review, fixing vulnerabilities in Jenkins core, and security advisories just to name a few.
+
+In regards to the challenges of the CSP project, it was not due to Jenkins or CSP, but JavaScript being Javascript.
+There were some subtle, but very technical JavaScript caveats that needed to be addressed.
+Those problems were partially due to users not willing to leverage what Jenkins already has.
+For instance, it has the Jelly engine for views and people were trying to add JavaScript frameworks, such as React or Angular to that.
+The custom implementations contributed to some issues in their own way because those implementations were not fitting into the archetypes of issues that we were already familiar with and knew how to solve.
+So we had to figure out the framework first and see if there is a mechanism that allows you to enforce CSP.
+Then we had to try using it and depending on how old the technology was, the mechanism could exist or not exist.
+From there, you had to cook up something different to come up with a solution.
+
+==  Is there any part of Jenkins that you've taken a special liking to or found especially interesting?
+
+I think extensibility is the real power of Jenkins.
+If something doesn't exist, you can either look at the plugin ecosystem or in the worst case, you can just write it yourself.
+It's great because you can basically use Jenkins for whatever task you can come up with.
+Taking it one step further, if you want to automate the task you can most likely do it in Jenkins if you spend enough time.
+For instance, performance tests are not a very regular use case as far as I'm concerned, as most people use it to build software or publish, but in my first job we implemented performance tests.
+This is an example of a quirky way to use Jenkins.
+
+While fixing CSP issues, at the same time we would fix vulnerabilities that are out there.
+Security vulnerabilities like Severance or XSS, which have high impact on CVSS scores, so those are the kind of vulnerabilities that need to be addressed.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: That helps a lot, thanks for the expanded explanation and examples, I'll be sure to update this accordingly.
created_at: 2025-03-19T15:40:42Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: Oh, got it. It must be 2021 then, after I joined CloudBees.
created_at: 2025-03-19T16:48:53Z
author_association: NONE
diff_hunk: @@ -0,0 +1,98 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had up to to seven hours of English a week.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: ```suggestion
I went to school in Ukraine and it was heavy on English, so I had up to seven hours of English a week.
```
created_at: 2025-03-19T16:49:34Z
author_association: NONE
diff_hunk: @@ -0,0 +1,98 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had up to to seven hours of English a week.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine to study Computer Science, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using software called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result, I landed on a project with a heavy Java stack, using Java Spring and Angular on the front end.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: Not sure if it's supposed to be enumeration here with "Java Spring" or a specification.
I'd put it this way:

```suggestion
As a result, I landed on a project with a heavy Java stack, using Java 8, Spring, Hibernate on the back end and AngularJS and Angular on the front end.
```
created_at: 2025-03-19T16:55:04Z
author_association: NONE
diff_hunk: @@ -0,0 +1,98 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had up to to seven hours of English a week.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine to study Computer Science, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using software called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result, I landed on a project with a heavy Java stack, using Java Spring and Angular on the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: ```suggestion
That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and JavaScript skills.
```
created_at: 2025-03-19T16:55:35Z
author_association: NONE
diff_hunk: @@ -0,0 +1,98 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had up to to seven hours of English a week.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine to study Computer Science, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using software called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result, I landed on a project with a heavy Java stack, using Java Spring and Angular on the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I worked there for three years while I finished university, staying in Poland.
+Then Covid happened and for personal reasons, I eventually moved back to Ukraine.
+I had to leave my job since they did not offer remote work, but I found a new one at CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go, and I had a preference for security.
+This is how I ended up in the Jenkins security team at CloudBees, and that's how I gained most of the Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: Either I didn't publish my comment or this slipped 😋

We had no CD, releases were manual. For CI it was Gerrit (https://www.gerritcodereview.com/) for code review, and Jenkins for builds.
created_at: 2025-03-19T16:59:11Z
author_association: NONE
diff_hunk: @@ -0,0 +1,98 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had up to to seven hours of English a week.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine to study Computer Science, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using software called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result, I landed on a project with a heavy Java stack, using Java Spring and Angular on the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I worked there for three years while I finished university, staying in Poland.
+Then Covid happened and for personal reasons, I eventually moved back to Ukraine.
+I had to leave my job since they did not offer remote work, but I found a new one at CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go, and I had a preference for security.
+This is how I ended up in the Jenkins security team at CloudBees, and that's how I gained most of the Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
+I was just a basic user checking build logs and performing more basic actions.
+But there were some micro projects where I had to do performance tests for software that we were using.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: ```suggestion
But there were some micro projects where I had to do performance tests for software that we were building.
```
created_at: 2025-03-19T16:59:29Z
author_association: NONE
diff_hunk: @@ -0,0 +1,96 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: Okay great, I'll update that then. Thanks very much
created_at: 2025-03-19T18:23:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,98 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had up to to seven hours of English a week.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine to study Computer Science, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using software called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result, I landed on a project with a heavy Java stack, using Java Spring and Angular on the front end.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: Thanks for the clarification on this @yaroslavafenkin, I want to make sure everything is accurate.
created_at: 2025-03-19T18:24:22Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,98 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2018
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had up to to seven hours of English a week.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine to study Computer Science, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using software called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result, I landed on a project with a heavy Java stack, using Java Spring and Angular on the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and Javascript skills.
+I worked there for three years while I finished university, staying in Poland.
+Then Covid happened and for personal reasons, I eventually moved back to Ukraine.
+I had to leave my job since they did not offer remote work, but I found a new one at CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go, and I had a preference for security.
+This is how I ended up in the Jenkins security team at CloudBees, and that's how I gained most of the Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2024/10/04/content-security-policy-grant/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI/CD and no code review stack, so we were using Garrett and Jenkins.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: No worries, thanks for clarifying this point as well. I'll make sure this is updated properly.
created_at: 2025-03-19T18:25:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,98 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2021
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had up to seven hours of English a week.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine to study Computer Science, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using software called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result, I landed on a project with a heavy Java stack, using Java 8, Spring, Hibernate on the back end, and AngularJS and Angular on the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and JavaScript skills.
+I worked there for three years while I finished university, staying in Poland.
+Then Covid happened and for personal reasons, I eventually moved back to Ukraine.
+I had to leave my job since they did not offer remote work, but I found a new one at CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go, and I had a preference for security.
+This is how I ended up in the Jenkins security team at CloudBees, and that's how I gained most of the Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2025/01/16/jenkins-csp-project-update/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI and no code review stack, so we were using Gerrit for code review and Jenkins for builds.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: yaroslavafenkin
body: "No code review stack" doesn't fit here anymore, does it? :)
created_at: 2025-03-20T10:18:08Z
author_association: NONE
diff_hunk: @@ -0,0 +1,98 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2021
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had up to seven hours of English a week.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine to study Computer Science, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using software called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result, I landed on a project with a heavy Java stack, using Java 8, Spring, Hibernate on the back end, and AngularJS and Angular on the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and JavaScript skills.
+I worked there for three years while I finished university, staying in Poland.
+Then Covid happened and for personal reasons, I eventually moved back to Ukraine.
+I had to leave my job since they did not offer remote work, but I found a new one at CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go, and I had a preference for security.
+This is how I ended up in the Jenkins security team at CloudBees, and that's how I gained most of the Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2025/01/16/jenkins-csp-project-update/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI and no code review stack, so we were using Gerrit for code review and Jenkins for builds.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: ```suggestion
We only had CI at the time, as we were using Gerrit for code review and Jenkins for builds.
```
created_at: 2025-03-20T12:51:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,98 @@
+= Yaroslav Afenkin
+:page-name: Yaroslav Afenkin
+:page-linkedin: yaroslavafenkin
+:page-twitter:
+:page-github: yaroslavafenkin
+:page-email:
+:page-image: avatar/yaroslav-afenkin.jpg
+:page-pronouns: He/Him/His
+:page-location: Odesa, Ukraine
+:page-firstcommit: 2021
+:page-datepublished: 2025-03-25
+:page-featured: true
+:page-intro: Yaroslav Afenkin is a software engineer based in Odesa, Ukraine, and has been involved with the Jenkins project on multiple occasions throughout his career. Whether it was during his first job as a junior engineer, his time working on the Jenkins security team, or his return to contribute to the Jenkins Content Security Policy (CSP) project, Yaroslav has always been intrigued with the abilities of Jenkins. While not necessarily a Jenkins user, his work on securing Jenkins and fixing vulnerabilities has helped the entire community. Thankfully, Yaroslav makes sure to balance his work life with his personal life by finding time to relax and enjoy his free time when he's not deep in the code.
+
+== What is your background prior to contributing to Jenkins?
+
+I went to school in Ukraine and it was heavy on English, so I had up to seven hours of English a week.
+By the time I finished school, I got to a pretty decent level, which helps a lot in the industry that I'm working in.
+I then entered university in Ukraine to study Computer Science, but after studying here for two years, it wasn't as good as I had hoped.
+I decided to move to Warsaw, Poland and continued my studies there.
+With one year left to study, I found a job working as a junior software engineer.
+Initially, I was hired to work on some insurance stuff.
+They were using software called Guidewire.
+However, I was lucky enough that there was no Guidewire project for me.
+
+As a result, I landed on a project with a heavy Java stack, using Java 8, Spring, Hibernate on the back end, and AngularJS and Angular on the front end.
+That really helped a lot and I feel like I won a lottery there because that's how I developed most of my Java and JavaScript skills.
+I worked there for three years while I finished university, staying in Poland.
+Then Covid happened and for personal reasons, I eventually moved back to Ukraine.
+I had to leave my job since they did not offer remote work, but I found a new one at CloudBees.
+Initially there was this little project where we were cleaning up some security technical debt with some other folks.
+As my project was coming to an end, we were asked where we wanted to go, and I had a preference for security.
+This is how I ended up in the Jenkins security team at CloudBees, and that's how I gained most of the Jenkins skills that I have right now.
+This also helped a lot when working on the recent link:https://www.jenkins.io/blog/2025/01/16/jenkins-csp-project-update/[CSP project in Jenkins].
+
+== How long have you been working on Jenkins?
+
+It's probably worth mentioning that I used Jenkins in my first job.
+That was my initial exposure to Jenkins, despite not using it too heavily.
+We basically had CI and no code review stack, so we were using Gerrit for code review and Jenkins for builds.
path: src/pages/contributors/yaroslav-afenkin.adoc
user: login: kmartens27
body: That's very true, thanks for catching it! I've made sure to update this appropriately.
created_at: 2025-03-20T14:47:02Z
author_association: CONTRIBUTOR

PR comments:
user: login: kmartens27
created_at: 2025-03-18T17:40:18Z
body: deploy preview link: https://deploy-preview-306--contributor-spotlight.netlify.app/pages/contributors/yaroslav-afenkin/
author_association: CONTRIBUTOR
user: login: gounthar
created_at: 2025-03-18T17:41:04Z
body: Oh, nice! 😍 
author_association: CONTRIBUTOR
user: login: kmartens27
created_at: 2025-03-18T19:03:42Z
body: Thanks very much @gounthar 
author_association: CONTRIBUTOR
user: login: kmartens27
created_at: 2025-03-19T15:44:44Z
body: Hi @yaroslavafenkin, thanks very much for all of your feedback and clarification. I've updated the content accordingly, and was hoping to get your review or any feedback on what's been changed. Thanks very much!
author_association: CONTRIBUTOR
user: login: kmartens27
created_at: 2025-03-24T14:00:47Z
body: Thanks very much @yaroslavafenkin for all your help and approval, it's greatly appreciated!
author_association: CONTRIBUTOR