profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/batmat/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.
Baptiste Mathus batmat @CloudBees Toulouse, France http://batmat.net Software Tinkerer https://twitter.com/bmathus

batmat/artifactchecker-maven-plugin 6

Small plugin designed to check that your artifactId matches the project directory name, as recommended for example there: http://www.sonatype.com/people/2011/01/maven-tip-project-directories-and-artifact-ids/

batmat/asciidoctor-maven-site-demo 1

Demonstration of a maven site using asciidoctor syntax for its site pages

batmat/batmat.github.com 1

Github projects sWebsite

batmat/acceptance-test-harness 0

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

batmat/access-modifier 0

Enforce access restrictions to deprecated code

batmat/active-directory-plugin 0

Jenkins active-directory plugin

batmat/agiletour-forge-verifier-votre-machine 0

Repo pour tester le bon fonctionnement de sa machine avant l'atelier http://att2013.herokuapp.com/event/268

batmat/amazon-ecs-plugin 0

Amazon EC2 Container Service Plugin for Jenkins

push eventjenkins-infra/repository-permissions-updater

jasonopslevel

commit sha 61b6b88e257078f913744c1f0f97f9be31875758

Update plugin-opslevel.yml (#2001) Co-authored-by: jason-opslevel <74929492+jason-opslevel@users.noreply.github.com>

view details

push time in 7 hours

PR merged jenkins-infra/repository-permissions-updater

Update plugin-opslevel.yml

For the opslevel plugin: add developers, and add the ability to release through CD.

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

Description

Sorry for the fast-follow PR. We would like to add the ability to release the plugin through CD as well. Here is the link to the plugin: https://github.com/jenkinsci/opslevel-plugin

Thanks!

<!-- 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

jasonopslevel

pr closed time in 7 hours

PullRequestEvent

PR closed jenkins-infra/repository-permissions-updater

Update plugin-opslevel.yml

For the opslevel plugin: add developers, and add the ability to release through CD.

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

Description

Sorry for the fast-follow PR. We would like to add the ability to release the plugin through CD as well. Here is the link to the plugin: https://github.com/jenkinsci/opslevel-plugin

Thanks!

<!-- 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

+4 -0

0 comment

1 changed file

jasonopslevel

pr closed time in 8 hours

push eventjenkins-infra/repository-permissions-updater

bharatpandiri

commit sha 46e5e2da59099b8b3287fb7c4026394c5f5a0b41

Update plugin-leanix-microservice-intelligence.yml (#2000) Enable CD for leanix plugin

view details

push time in 8 hours

PR merged jenkins-infra/repository-permissions-updater

Update plugin-leanix-microservice-intelligence.yml

Enable CD for LeanIX MI 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

  • [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

+2 -0

0 comment

1 changed file

bharatpandiri

pr closed time in 8 hours

PullRequestEvent

PR closed jenkins-infra/repository-permissions-updater

Update plugin-opslevel.yml

For the opslevel plugin: add developers, and add the ability to release through CD.

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

Description

Sorry for the fast-follow PR. We would like to add the ability to release the plugin through CD as well. Here is the link to the plugin: https://github.com/jenkinsci/opslevel-plugin

Thanks!

<!-- 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

+4 -0

0 comment

1 changed file

jasonopslevel

pr closed time in 8 hours

PR opened jenkins-infra/repository-permissions-updater

Update plugin-opslevel.yml

For the opslevel plugin: add developers, and add the ability to release through CD.

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

Description

Sorry for the fast-follow PR. We would like to add the ability to release the plugin through CD as well.

Thanks!

<!-- 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

+4 -0

0 comment

1 changed file

pr created time in 9 hours

PR opened jenkins-infra/repository-permissions-updater

Update plugin-leanix-microservice-intelligence.yml

Enable CD for LeanIX MI 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

  • [ ] 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

+2 -0

0 comment

1 changed file

pr created time in 9 hours

push eventjenkins-infra/repository-permissions-updater

jenkins-infra-bot

commit sha df2e1f611a109f117e8944f2b82649f00826e71c

Add upload permissions for opslevel-plugin (#1990)

view details

push time in 12 hours

delete branch jenkins-infra/repository-permissions-updater

delete branch : ircbot-opslevel-plugin-permissions

delete time in 12 hours

PR merged jenkins-infra/repository-permissions-updater

Add upload permissions for opslevel-plugin

Hello from your friendly Jenkins Hosting Bot!

This is an automatically created PR for:

  • https://issues.jenkins.io/browse/HOSTING-1107
  • https://github.com/jenkinsci/opslevel-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 @jason-opslevel, @sergio-opslevel, @kenrose, @jlaban

+9 -0

2 comments

1 changed file

jenkins-infra-bot

pr closed time in 12 hours

pull request commentjenkins-infra/repository-permissions-updater

Add upload permissions for opslevel-plugin

No just the last 3 builds failed.

jenkins-infra-bot

comment created time in 12 hours

pull request commentjenkins-infra/repository-permissions-updater

Add upload permissions for opslevel-plugin

Hey @jenkins-infra/hosting, is there anything else we should do for this pull request?

Thanks for your time!

jenkins-infra-bot

comment created time in 12 hours

created repositoryserenity-dojo/string-calculator-challenge

created time in a day

created repositoryserenity-dojo/fruit-shop-challenge

created time in a day

push eventjenkins-infra/repository-permissions-updater

forgedhallpass

commit sha efc1e07e1af324ada0b823b9af1b401f73979008

Enable continuous delivery for the Nuclei plugin (#1999)

view details

push time in 3 days

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 3 days

push eventjenkins-infra/repository-permissions-updater

jenkins-infra-bot

commit sha 80ffc8989205cc78000e3d6725cbaa41770a7713

Add upload permissions for nuclei-plugin (#1994)

view details

push time in 3 days

delete branch jenkins-infra/repository-permissions-updater

delete branch : ircbot-nuclei-plugin-permissions

delete time in 3 days

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 3 days

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 3 days

push eventjenkins-infra/repository-permissions-updater

Lakshmi Narasimhan T V

commit sha 3a5bb2371a9a06d06b2d751bff33526e7857e3d3

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

view details

push time in 3 days

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 3 days

push eventjenkins-infra/repository-permissions-updater

Lakshmi Narasimhan T V

commit sha 2f8f1e525a9a4f7da8fc5ef0534eb37da80f7e3b

Update plugin-teamconcert.yml (#1997)

view details

push time in 3 days

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 3 days