profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/slide/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.

jenkinsci/mailer-plugin 28

This plugin allows you to configure email notifications for build results

jenkins-infra/ircbot 23

Jenkins IRCbot

slide/jelly2groovy 12

Converts jelly views to groovy views

jenkinsci/cifs-plugin 4

Jenkins cifs plugin

jenkinsci/mailmap-resolver-plugin 0

Jenkins MailAddressResolver implementation which allows username to email mapping

PR closed jenkinsci/docker

Add dockerfile for ubuntu using hotspot jvm

<!-- Please describe your pull request here. -->

  • [x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • [x] Ensure that the pull request title represents the desired changelog entry
  • [x] Please describe what you did
  • [x] Link to relevant issues in GitHub or Jira
  • [x] Link to relevant pull requests, esp. upstream and downstream changes
  • [x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Added a dockerfile for jenkins using adoptopenjdk 11 hotspot on ubuntu focal. Also added the respective build command in the make file

I personally needed this for a project of mine which required a system level dependency, thought I would go ahead and PR this as others can benefit from an ubuntu jenkins image using hotspot instead of just openj8

+105 -0

0 comment

2 changed files

NovaFox161

pr closed time in 2 hours

PR opened jenkinsci/docker

Add dockerfile for ubuntu using hotspot jvm

<!-- Please describe your pull request here. -->

  • [x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • [x] Ensure that the pull request title represents the desired changelog entry
  • [x] Please describe what you did
  • [x] Link to relevant issues in GitHub or Jira
  • [x] Link to relevant pull requests, esp. upstream and downstream changes
  • [x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Added a dockerfile for jenkins using adoptopenjdk 11 hotspot on ubuntu focal. Also added the respective build command in the make file

I personally needed this for a project of mine which required a system level dependency, thought I would go ahead and PR this as others can benefit from an ubuntu jenkins image using hotspot instead of just openj8

+105 -0

0 comment

2 changed files

pr created time in 2 hours

push eventjenkins-infra/repository-permissions-updater

forgedhallpass

commit sha efc1e07e1af324ada0b823b9af1b401f73979008

Enable continuous delivery for the Nuclei plugin (#1999)

view details

push time in 12 hours

PR opened jenkins-infra/repository-permissions-updater

Enable continuous-delivery

Enabling continuous delivery for the nuclei plugin.

+2 -0

0 comment

1 changed file

pr created time in 12 hours

push eventjenkins-infra/repository-permissions-updater

jenkins-infra-bot

commit sha 80ffc8989205cc78000e3d6725cbaa41770a7713

Add upload permissions for nuclei-plugin (#1994)

view details

push time in 13 hours

delete branch jenkins-infra/repository-permissions-updater

delete branch : ircbot-nuclei-plugin-permissions

delete time in 13 hours

PR merged jenkins-infra/repository-permissions-updater

Add upload permissions for nuclei-plugin

Hello from your friendly Jenkins Hosting Bot!

This is an automatically created PR for:

  • https://issues.jenkins.io/browse/HOSTING-1112
  • https://github.com/jenkinsci/nuclei-plugin

The user(s) listed in the permissions file may not have logged in to Artifactory yet, check the PR status. To check again, hosting team members will retrigger the build using Checks area or by closing and reopening the PR.

cc @forgedhallpass, @ehsandeep, @Ice3man543, @ehrishirajsharma, @Mzack9999

+9 -0

1 comment

1 changed file

jenkins-infra-bot

pr closed time in 13 hours

pull request commentjenkins-infra/repository-permissions-updater

Add upload permissions for nuclei-plugin

I've logged in to Artifactory. Please re-trigger the checks/re-create the pull request.

jenkins-infra-bot

comment created time in 18 hours

pull request commentjenkinsci/docker

Introduce RHEL 8 support using UBI image

@saper

I got somewhat disappointed about how Red Hat Subscription Manager behaves once things get running on the UBI image...

Can you be more specific? What seems to be the issue?

olivergondza

comment created time in a day

push eventjenkins-infra/repository-permissions-updater

Lakshmi Narasimhan T V

commit sha 3a5bb2371a9a06d06b2d751bff33526e7857e3d3

Update plugin-teamconcert-git.yml (#1998)

view details

push time in a day

PR merged jenkins-infra/repository-permissions-updater

Update plugin-teamconcert-git.yml

Adding a new maintainer for Team Concert Git Plugin. GitHub URL https://github.com/susandip The maintainer has been given write access to the Team Concert plugin GitHub repository https://github.com/jenkinsci/teamconcert-git-plugin

<!-- This PR template only applies to permission changes. Ignore it for changes to the tool updating permissions in Artifactory -->

Description

<!-- fill in description here, this will at least be a link to a GitHub repository, and often also links to hosting request, and @mentioning other committers/maintainers as per the checklist below -->

Submitter checklist for adding or changing permissions

<!-- Make sure to implement all relevant entries (see section headers to when they apply) and mark them as checked (by replacing the space between brackets with an "x"). Remove sections that don't apply, e.g. the second and third when adding a new uploader to an existing permissions file. -->

Always

https://github.com/jenkinsci/teamconcert-git-plugin

  • [x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

  • [ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

When adding new uploaders (this includes newly created permissions files)

Reviewer checklist (not for requesters!)

  • [ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
  • [ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
  • [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
  • [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

+1 -0

1 comment

1 changed file

lvaikunt

pr closed time in a day

push eventjenkins-infra/repository-permissions-updater

Lakshmi Narasimhan T V

commit sha 2f8f1e525a9a4f7da8fc5ef0534eb37da80f7e3b

Update plugin-teamconcert.yml (#1997)

view details

push time in a day

PR merged jenkins-infra/repository-permissions-updater

Update plugin-teamconcert.yml

Adding a new maintainer for Team Concert Plugin. GitHub URL https://github.com/susandip The maintainer has been given write access to the Team Concert plugin GitHub repository https://github.com/jenkinsci/teamconcert-plugin

<!-- This PR template only applies to permission changes. Ignore it for changes to the tool updating permissions in Artifactory -->

Description

<!-- fill in description here, this will at least be a link to a GitHub repository, and often also links to hosting request, and @mentioning other committers/maintainers as per the checklist below -->

Submitter checklist for adding or changing permissions

<!-- Make sure to implement all relevant entries (see section headers to when they apply) and mark them as checked (by replacing the space between brackets with an "x"). Remove sections that don't apply, e.g. the second and third when adding a new uploader to an existing permissions file. -->

Always

https://github.com/jenkinsci/teamconcert-plugin

  • [x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

  • [ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

When adding new uploaders (this includes newly created permissions files)

Reviewer checklist (not for requesters!)

  • [ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
  • [ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
  • [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
  • [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

+1 -0

2 comments

1 changed file

lvaikunt

pr closed time in a day

pull request commentjenkins-infra/repository-permissions-updater

Update plugin-teamconcert.yml

Hi, I have joined the team that maintains the Team Concert Plugin

lvaikunt

comment created time in a day

pull request commentjenkins-infra/repository-permissions-updater

Update plugin-teamconcert.yml

Sandip has logged into artifactory but the checks have not run again.

lvaikunt

comment created time in a day

pull request commentjenkins-infra/repository-permissions-updater

Update plugin-teamconcert-git.yml

Hi, I have joined the team that maintains the Team Concert Git Plugin

lvaikunt

comment created time in a day

PR opened jenkins-infra/repository-permissions-updater

Update plugin-teamconcert-git.yml

Adding a new maintainer for Team Concert Git Plugin. GitHub URL https://github.com/susandip The maintainer has been given write access to the Team Concert plugin GitHub repository https://github.com/jenkinsci/teamconcert-git-plugin

<!-- This PR template only applies to permission changes. Ignore it for changes to the tool updating permissions in Artifactory -->

Description

<!-- fill in description here, this will at least be a link to a GitHub repository, and often also links to hosting request, and @mentioning other committers/maintainers as per the checklist below -->

Submitter checklist for adding or changing permissions

<!-- Make sure to implement all relevant entries (see section headers to when they apply) and mark them as checked (by replacing the space between brackets with an "x"). Remove sections that don't apply, e.g. the second and third when adding a new uploader to an existing permissions file. -->

Always

https://github.com/jenkinsci/teamconcert-git-plugin

  • [ ] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

  • [ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

When adding new uploaders (this includes newly created permissions files)

Reviewer checklist (not for requesters!)

  • [ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
  • [ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
  • [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
  • [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

+1 -0

0 comment

1 changed file

pr created time in a day

PR opened jenkins-infra/repository-permissions-updater

Update plugin-teamconcert.yml

Adding a new maintainer for Team Concert Plugin. GitHub URL https://github.com/susandip The maintainer has been given write access to the Team Concert plugin GitHub repository https://github.com/jenkinsci/teamconcert-plugin

<!-- This PR template only applies to permission changes. Ignore it for changes to the tool updating permissions in Artifactory -->

Description

<!-- fill in description here, this will at least be a link to a GitHub repository, and often also links to hosting request, and @mentioning other committers/maintainers as per the checklist below -->

Submitter checklist for adding or changing permissions

<!-- Make sure to implement all relevant entries (see section headers to when they apply) and mark them as checked (by replacing the space between brackets with an "x"). Remove sections that don't apply, e.g. the second and third when adding a new uploader to an existing permissions file. -->

Always

https://github.com/jenkinsci/teamconcert-plugin

  • [ ] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

  • [ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

When adding new uploaders (this includes newly created permissions files)

Reviewer checklist (not for requesters!)

  • [ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
  • [ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
  • [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
  • [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

+1 -0

0 comment

1 changed file

pr created time in a day

issue commentjenkinsci/docker

Using jmx in JAVA_OPTS make other java tools fail

We have a seed job on our Jenkins and the it has to run on Jenkins controller (Formerly known as master).

IuryAlves

comment created time in 2 days

push eventjenkins-infra/repository-permissions-updater

xwz123

commit sha d9e12601cadbb98746aa145fe09776152c84e69a

enable CD and add developers (#1996) Co-authored-by: xwzQmxx <1499273991@qq.com>

view details

push time in 2 days

PR merged jenkins-infra/repository-permissions-updater

Reviewers
enable CD and add developers

<!-- This PR template only applies to permission changes. Ignore it for changes to the tool updating permissions in Artifactory -->

Description

<!-- fill in description here, this will at least be a link to a GitHub repository, and often also links to hosting request, and @mentioning other committers/maintainers as per the checklist below -->

Submitter checklist for adding or changing permissions

<!-- Make sure to implement all relevant entries (see section headers to when they apply) and mark them as checked (by replacing the space between brackets with an "x"). Remove sections that don't apply, e.g. the second and third when adding a new uploader to an existing permissions file. -->

Always

  • [ ] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

  • [ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

When adding new uploaders (this includes newly created permissions files)

Reviewer checklist (not for requesters!)

  • [ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
  • [ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
  • [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
  • [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

+3 -0

4 comments

1 changed file

xwz123

pr closed time in 2 days

pull request commentjenkins-infra/repository-permissions-updater

enable CD and add developers

@timja Sorry, we have processed.

xwz123

comment created time in 2 days

pull request commentjenkins-infra/repository-permissions-updater

enable CD and add developers

@timja Done. Thanks!

xwz123

comment created time in 2 days

pull request commentjenkins-infra/repository-permissions-updater

enable CD and add developers

login

still failing currently

xwz123

comment created time in 2 days

pull request commentjenkins-infra/repository-permissions-updater

enable CD and add developers

login

xwz123

comment created time in 2 days

pull request commentjenkins-infra/repository-permissions-updater

enable CD and add developers

login

xwz123

comment created time in 2 days

PR opened jenkins-infra/repository-permissions-updater

enable CD and add developers

<!-- This PR template only applies to permission changes. Ignore it for changes to the tool updating permissions in Artifactory -->

Description

<!-- fill in description here, this will at least be a link to a GitHub repository, and often also links to hosting request, and @mentioning other committers/maintainers as per the checklist below -->

Submitter checklist for adding or changing permissions

<!-- Make sure to implement all relevant entries (see section headers to when they apply) and mark them as checked (by replacing the space between brackets with an "x"). Remove sections that don't apply, e.g. the second and third when adding a new uploader to an existing permissions file. -->

Always

  • [ ] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

  • [ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

When adding new uploaders (this includes newly created permissions files)

Reviewer checklist (not for requesters!)

  • [ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
  • [ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
  • [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
  • [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

+3 -0

0 comment

1 changed file

pr created time in 2 days

push eventjenkins-infra/repository-permissions-updater

jenkins-infra-bot

commit sha 833126c53424b4ec1947e71ce57e8997125f73a7

Adding upload permissions file for huaweicloud-ecs-plugin (#1993)

view details

push time in 2 days

PR merged jenkins-infra/repository-permissions-updater

Add upload permissions for huaweicloud-ecs-plugin

Hello from your friendly Jenkins Hosting Bot!

This is an automatically created PR for:

  • https://issues.jenkins.io/browse/HOSTING-1105
  • https://github.com/jenkinsci/huaweicloud-ecs-plugin

The user(s) listed in the permissions file may not have logged in to Artifactory yet, check the PR status. To check again, hosting team members will retrigger the build using Checks area or by closing and reopening the PR.

cc @xwz123, @zengchen1024

+9 -0

1 comment

1 changed file

jenkins-infra-bot

pr closed time in 2 days