profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/oleg-nenashev/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Oleg Nenashev oleg-nenashev @jenkinsci, @winsw, @cloudbees, @librecores Neuchatel, Switzerland @jenkinsci maintainer and board member. Engineer at @cloudbees. R&D and Automation engineer with HW/Embedded background, PhD.

hub4j/github-api 811

Java API for GitHub

jenkinsci/docker-inbound-agent 385

Docker image for a Jenkins agent which can connect to Jenkins using TCP or Websocket protocols

jenkinsci/docker-agent 178

Base Docker image for Jenkins Agents

jenkinsci/jenkinsfile-runner-github-actions 165

Jenkins single-shot master GitHub Action POC

jenkinsci/acceptance-test-harness 110

Acceptance tests cases for Jenkins and its plug-ins based on selenium and docker.

jenkinsci/docker-ssh-agent 99

Docker image for Jenkins agents connected over SSH

KostyaSha/github-integration-plugin 88

Jenkins GitHub Integration Plugin

kohsuke/winp 56

Windows process management library

jenkinsci/ci.jenkins.io-runner 36

An emulator of ci.jenkins.io instance, packaged as a single-shot Jenkinsfile Runner

librecores/librecores-ci-jenkins-server 35

LibreCores Continuous Integration

pull request commentjenkins-infra/jenkins.io

[fix] Use the project logo instead of the angry jenkins

Consider using https://twitter.com/oleg_nenashev/status/1408732675393966080 for inspiration :P

On Fri, Sep 24, 2021 at 3:19 PM Arnaud Heritier ***@***.***> wrote:

@darinpope https://github.com/darinpope do you have a profile ? I don't see one: https://github.com/jenkins-infra/jenkins.io/tree/master/content/_data/authors 2 years ago I did an opengraph but it is a bit crappy I find in term of design : https://github.com/jenkins-infra/jenkins.io/blob/master/content/blog/2019/11/2019-11-22-jenkins-health-advisor-by-cloudbees.adoc

— You are receiving this because your review was requested. Reply to this email directly, view it on GitHub https://github.com/jenkins-infra/jenkins.io/pull/4577#issuecomment-926618728, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAW4RICQIHN5WWOUCFIG4RTUDR3GNANCNFSM5EVUXAYQ .

aheritier

comment created time in 2 hours

pull request commentjenkinsci/jenkins

Renamed exclude file and set spotbugs default to medium

Will it require extending the excludes file before the merge? I'd guess so. There was huge work to cleanup the codebase (thanks to everyone!) but I'd guess there are still some unfixed issues

StefanSpieker

comment created time in 2 hours

push eventjenkins-infra/jenkins.io

James Nord

commit sha 13c471dda4506f1100a163a56f4189fb60de8d50

clarify backporting criteria and eligibility. note that the label can be applied to anything but only small well contained bug fixes are acceptable, along with a dependency bump should the library have a public CVE.

view details

James Nord

commit sha 51aec281fdc89dd846c5b0978fc955447f959fb5

Fix Typo identified in code review Co-authored-by: Tim Jacomb <21194782+timja@users.noreply.github.com>

view details

James Nord

commit sha b4b28c5f237363e941385486e98c9949f4a381a9

split sentence into two

view details

James Nord

commit sha a37e738fdf6a4ecd366ecff44bbfaa59b7323ddf

Update content/download/lts/index.adoc

view details

Oleg Nenashev

commit sha f73a294762b61e9efcad6c4828e80f32aba3addb

Merge pull request #4547 from jtnord/patch-9 clarify backporting criteria and eligibility.

view details

push time in 2 hours

PR merged jenkins-infra/jenkins.io

clarify backporting criteria and eligibility.

note that the label can be applied to anything but only small well contained bug fixes are acceptable, along with a dependency bump should the library have a public CVE.

+4 -2

1 comment

1 changed file

jtnord

pr closed time in 2 hours

pull request commentjenkins-infra/jenkins.io

clarify backporting criteria and eligibility.

No feedback from @jtnord w.r.t last suggestions. Will merge anyway, it is a reasonable update

jtnord

comment created time in 2 hours

PullRequestReviewEvent

pull request commentjenkins-infra/jenkins.io

[fix] Use the project logo instead of the angry jenkins

Is there opengraph for this post? Maybe you also want to add @darinpope to authors in the metadata

aheritier

comment created time in 2 hours

PullRequestReviewEvent

pull request commentjenkinsci/jenkins

💣 Remove powermock

We may merge it in 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process

timja

comment created time in a day

PullRequestReviewEvent

pull request commentjenkinsci/docker

Add java 17 preview image

@timja would it make sense to start a GitHub project for Java 17 related changes so that we could track the required changes?

timja

comment created time in a day

Pull request review commentjenkins-infra/jenkins.io

Proposing a french localization topic for hacktober fest 2021

 a| We are moving plugin documentation from https://wiki.jenkins.io/ to GitHub, link:https://issues.jenkins.io/issues/?jql=labels%20in%20(docs-sig%2C%20documentation)%20AND%20labels%20%3D%20newbie-friendly%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)[Jira newcomer-friendly issues], link:https://github.com/search?q=org%3Ajenkinsci+is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22+label%3Adocumentation&type=Issues[GitHub good first issues] +| French translation (maybe others languages)
| French translation
aHenryJard

comment created time in 2 days

Pull request review commentjenkins-infra/jenkins.io

Proposing a french localization topic for hacktober fest 2021

 a| We are moving plugin documentation from https://wiki.jenkins.io/ to GitHub, link:https://issues.jenkins.io/issues/?jql=labels%20in%20(docs-sig%2C%20documentation)%20AND%20labels%20%3D%20newbie-friendly%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)[Jira newcomer-friendly issues], link:https://github.com/search?q=org%3Ajenkinsci+is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22+label%3Adocumentation&type=Issues[GitHub good first issues] +| French translation (maybe others languages)+| Git, French, optional: Java developement tools to run Jenkins or plugins from sources locally.+a| Improve coverage of French localization of Jenkins.
a| Improve coverage of French localization of the Jenkins web interface, including the Jenkins core and plugins.
The same is possible for other languages, let us know if you are interested!
aHenryJard

comment created time in 2 days

Pull request review commentjenkins-infra/jenkins.io

Proposing a french localization topic for hacktober fest 2021

 a| We are moving plugin documentation from https://wiki.jenkins.io/ to GitHub, link:https://issues.jenkins.io/issues/?jql=labels%20in%20(docs-sig%2C%20documentation)%20AND%20labels%20%3D%20newbie-friendly%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)[Jira newcomer-friendly issues], link:https://github.com/search?q=org%3Ajenkinsci+is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22+label%3Adocumentation&type=Issues[GitHub good first issues] +| French translation (maybe others languages)+| Git, French, optional: Java developement tools to run Jenkins or plugins from sources locally.
| Git, French, Jenkins developer tools

Otherwise it will render badly

aHenryJard

comment created time in 2 days

PullRequestReviewEvent
PullRequestReviewEvent

startediterative/cml

started time in 2 days

PullRequestReviewEvent
PullRequestEvent

pull request commentjenkinsci/jenkins

Bump tyrus-standalone-client-jdk from 2.0.0 to 2.0.1

cloising as duplicate. No idea why Dependabot did not capture it

dependabot[bot]

comment created time in 5 days

PR closed jenkinsci/jenkins

Bump tyrus-standalone-client-jdk from 2.0.0 to 2.0.1 dependencies java

Bumps tyrus-standalone-client-jdk from 2.0.0 to 2.0.1.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

+1 -1

2 comments

1 changed file

dependabot[bot]

pr closed time in 5 days

pull request commentjenkinsci/jenkins

Bump tyrus-standalone-client-jdk from 2.0.0 to 2.0.1

cloising as duplicate. No idea why Dependabot did not capture it

dependabot[bot]

comment created time in 5 days

PullRequestReviewEvent
PullRequestReviewEvent

push eventjenkinsci/jenkins

James Nord

commit sha 124401d6cb7126e4e3dcd35846d6f09361a6b5f5

tidy up clicommand javadoc

view details

Oleg Nenashev

commit sha e580a420c32fe8aa77d27add9612bd57088106eb

Merge pull request #5728 from jtnord/cliCommand tidy up clicommand javadoc

view details

push time in 5 days

PR merged jenkinsci/jenkins

tidy up clicommand javadoc ready-for-merge skip-changelog

The javadoc for the return codes was a mess so not easy to parse.

Converted it to a table so it is easier to read. I tried using a definition list to more accuratly represent this but it looked worse and not easy to follow.

before:

image

after:

image

Proposed changelog entries

  • N/A

Proposed upgrade guidelines

N/A

Submitter checklist

  • [ ] (If applicable) Jira issue is well described
  • [ ] Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
    • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
  • [ ] Appropriate autotests or explanation to why this change has no tests
  • [ ] For dependency updates: links to external changelogs and, if possible, full diffs

<!-- For new API and extension points: Link to the reference implementation in open-source (or example in Javadoc) -->

Desired reviewers

<!-- Comment: If you need an accelerated review process by the community (e.g., for critical bugs), mention @jenkinsci/code-reviewers -->

Maintainer checklist

Before the changes are marked as ready-for-merge:

  • [ ] There are at least 2 approvals for the pull request and no outstanding requests for change
  • [ ] Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
  • [ ] Changelog entries in the PR title and/or Proposed changelog entries are correct
  • [ ] Proper changelog labels are set so that the changelog can be generated automatically
  • [ ] If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
  • [ ] If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).
+14 -15

1 comment

1 changed file

jtnord

pr closed time in 5 days

PullRequestReviewEvent

startedsmartvotedocs/votesmart2021

started time in 5 days

PullRequestReviewEvent

pull request commentjenkinsci/remoting

Remove setting of null security manager

We may merge it in 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process

timja

comment created time in 7 days