Request to transfer my maintainer role for https://github.com/jenkinsci/fortify-on-demand-uploader-plugin

[Konstantin Voin]

Hello,

I need to transfer my maintainer role for https://github.com/jenkinsci/fortify-on-demand-uploader-plugin to https://github.com/ciuppinho. He also needs an invitation to join the organization.

·         Link to a plugin  - https://github.com/jenkinsci/fortify-on-demand-uploader-plugin

·         Link(s) to pull requests you want to deliver, if applicable -  Not Applicable

·         Your GitHub username/id  – makropod for https://github.com/makropod

Please help.

Thanks!

Konstantin Voin

[Alexander Brandes]

Heyo,

you can do that yourself by filing a pull request against the repository permission updater which updates your plugin's permission file. Once the pull request is merged, you are all set.

~ Alex

[Konstantin Voin]

Got it. What about inviting to the org?

[Gavin Mogan]

Those with permission to merge will take care of it

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0fb5efef-8afa-49e6-a217-32eb8af7eeccn%40googlegroups.com.

[Alexander Brandes]

That likely happens while processing your repository permission updater PR. The pull request template has a dedicated checklist, added users have to go through before the PR is ready to be merged.

[Konstantin Voin]

I have permissions to merge but didn't see Invite button to invite. Will see if repository permission updater PR does it.

Thanks!

[Konstantin Voin]

My PR  has been failing at the archiving step. Somebody else's PR is failing with the same error as well.

https://github.com/jenkins-infra/repository-permissions-updater/pull/2483

I called out a user that I saw merging another PR but no response yet.

How can I get help for that?

Thanks!

[Mark Waite]

On Fri, Apr 8, 2022 at 7:40 PM Konstantin Voin wrote:

My PR  has been failing at the archiving step. Somebody else's PR is failing with the same error as well.

https://github.com/jenkins-infra/repository-permissions-updater/pull/2483

I called out a user that I saw merging another PR but no response yet.

How can I get help for that?

The repository permissions updater build is failing on the master branch.  We'll need to fix that before any pull requests can be merged.  See https://ci.jenkins.io/job/Infra/job/repository-permissions-updater/job/master/

Not yet sure why the failures are happening on the master branch.  Will need more investigation.

Mark Waite

 

[Mark Waite]

The repository permissions updater downloads a JSON file from  https://reports.jenkins.io/artifactory-ldap-users-report.json that lists the known users of repo.jenkins-ci.org.  Unfortunately, the tool that generates that JSON file is writing content that is not valid JSON.  It is placing an additional string in the output.  That string is "jq-master-v3.15.0_alpha20210804-4073-gb39e1241e8".

The rest of the file appears to be valid JSON, but that version string at the start of the file is not valid.

Mark Waite

[Konstantin Voin]

Thanks for the quick response, Mark.

How would I find out when the issue is fixed?

[Mark Waite]

On Friday, April 8, 2022 at 8:45:11 PM UTC-6 Konstantin wrote:

Thanks for the quick response, Mark.

How would I find out when the issue is fixed?

The job on the master branch and your pull request build will likely both pass when the issue is fixed.  The job is scheduled to run once an hour.

The data file is generated on trusted.ci.jenkins.io based on the https://github.com/jenkins-infra/infra-reports/blob/main/Jenkinsfile .  When I look at the data files in that job on trusted.ci.jenkins.io (behind the Jenkins infra VPN), the data file is correct.  I'm not clear what has caused the data file stored on  reports.jenkins.io to be incorrect.  As far as I can tell, https://reports.jenkins.io/ was updated very recently, possibly because I interrupted a long running queue of jobs on trusted.ci.jenkins.io.  The data file at https://reports.jenkins.io/artifactory-ldap-users-report.json seems to now be valid JSON.

The master branch is now passing.  I've re-run the job for your pull request.  https://ci.jenkins.io/job/Infra/job/repository-permissions-updater/job/PR-2483/3/ 

Mark Waite

[Mark Waite]

Your job is also passing its checks.  Infrastructure issue seems to be resolved.

[Konstantin Voin]

Thanks Mark for the quick turnaround. Really appreciate it!

[Damien Duportal]

Additional note: the failures in reports and RPU are my fault, apologies for that. Please check https://github.com/jenkins-infra/plugin-site/pull/1150#issuecomment-1093986510 for more informations.

Apologies for this: it should be fixed in 3-4 hours.