Skip to content

Conversation

@timja
Copy link
Member

@timja timja commented Dec 7, 2019

Description

Add permissions for new test-harness for configuration-as-code-plugin: jenkinsci/configuration-as-code-plugin#1215

And update @Casz to be security contact for snakeyaml component (he's the contact for all other configuration-as-code component's, this one was missed in the update.

Submitter checklist for changing permissions

Always

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

For a new permissions file only

Copy link
Contributor

@jetersen jetersen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jenkinsadmin
Copy link

Build failed; the context from the latest run is:

Expand to view
[2019-12-07T18:16:40.807Z] Updating references
[2019-12-07T18:16:41.606Z] Merge succeeded, producing 99099d3c9e845f8f6feec389823f9c8883072479
[2019-12-07T18:16:41.606Z] Checking out Revision 99099d3c9e845f8f6feec389823f9c8883072479 (PR-1359)
[2019-12-07T18:16:41.791Z] Commit message: "Add upload permissions for configuration-as-code-test-harness"
[2019-12-07T18:16:41.791Z] First time build. Skipping changelog.
[2019-12-07T18:16:43.616Z] [Pipeline] }
[2019-12-07T18:16:43.644Z] [Pipeline] // stage
[2019-12-07T18:16:43.736Z] [Pipeline] stage
[2019-12-07T18:16:43.748Z] [Pipeline] { (Build)
[2019-12-07T18:16:43.816Z] [Pipeline] tool
[2019-12-07T18:16:43.864Z] [Pipeline] tool
[2019-12-07T18:16:43.921Z] [Pipeline] sh
[2019-12-07T18:16:44.209Z] + /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/mvn/bin/mvn -U clean verify
[2019-12-07T18:16:45.582Z] [INFO] Scanning for projects...
[2019-12-07T18:16:45.839Z] Downloading from repo.jenkins-ci.org: https://repo.jenkins-ci.org/public/org/jenkins-ci/jenkins/1.36/jenkins-1.36.pom
[2019-12-07T18:19:52.298Z] Downloading from central: https://repo.maven.apache.org/maven2/org/jenkins-ci/jenkins/1.36/jenkins-1.36.pom
[2019-12-07T18:19:52.298Z] [ERROR] [ERROR] Some problems were encountered while processing the POMs:
[2019-12-07T18:19:52.298Z] [FATAL] Non-resolvable parent POM for io.jenkins.infra:repository-permissions-updater:1.0-SNAPSHOT: Could not transfer artifact org.jenkins-ci:jenkins:pom:1.36 from/to repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/): Failed to transfer file: https://repo.jenkins-ci.org/public/org/jenkins-ci/jenkins/1.36/jenkins-1.36.pom. Return code is: 502 , ReasonPhrase:Bad Gateway. and 'parent.relativePath' points at wrong local POM @ line 3, column 13
[2019-12-07T18:19:52.298Z]  @ 
[2019-12-07T18:19:52.298Z] [ERROR] The build could not read 1 project -> [Help 1]
[2019-12-07T18:19:52.298Z] [ERROR]   
[2019-12-07T18:19:52.298Z] [ERROR]   The project io.jenkins.infra:repository-permissions-updater:1.0-SNAPSHOT (/home/jenkins/workspace/tory-permissions-updater_PR-1359/pom.xml) has 1 error
[2019-12-07T18:19:52.298Z] [ERROR]     Non-resolvable parent POM for io.jenkins.infra:repository-permissions-updater:1.0-SNAPSHOT: Could not transfer artifact org.jenkins-ci:jenkins:pom:1.36 from/to repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/): Failed to transfer file: https://repo.jenkins-ci.org/public/org/jenkins-ci/jenkins/1.36/jenkins-1.36.pom. Return code is: 502 , ReasonPhrase:Bad Gateway. and 'parent.relativePath' points at wrong local POM @ line 3, column 13 -> [Help 2]
[2019-12-07T18:19:52.298Z] [ERROR] 
[2019-12-07T18:19:52.298Z] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[2019-12-07T18:19:52.298Z] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[2019-12-07T18:19:52.298Z] [ERROR] 
[2019-12-07T18:19:52.298Z] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[2019-12-07T18:19:52.298Z] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[2019-12-07T18:19:52.298Z] [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
[2019-12-07T18:19:52.332Z] [Pipeline] }
[2019-12-07T18:19:52.371Z] [Pipeline] // stage
[2019-12-07T18:19:52.467Z] [Pipeline] stage
[2019-12-07T18:19:52.502Z] [Pipeline] { (Archive)
[2019-12-07T18:19:52.625Z] [Pipeline] archiveArtifacts
[2019-12-07T18:19:52.641Z] Archiving artifacts
[2019-12-07T18:19:53.404Z] [Pipeline] archiveArtifacts
[2019-12-07T18:19:53.421Z] Archiving artifacts
[2019-12-07T18:19:53.470Z] ‘json/*.json’ doesn’t match anything: even ‘json’ doesn’t exist
[2019-12-07T18:19:53.493Z] [Pipeline] }
[2019-12-07T18:19:53.561Z] [Pipeline] // stage
[2019-12-07T18:19:53.593Z] [Pipeline] }
[2019-12-07T18:19:53.730Z] [Pipeline] // node
[2019-12-07T18:19:53.811Z] [Pipeline] End of Pipeline
[2019-12-07T18:19:55.542Z] 
[2019-12-07T18:19:55.542Z] GitHub has been notified of this commit’s build result
[2019-12-07T18:19:55.542Z] 
[2019-12-07T18:19:55.542Z] ERROR: No artifacts found that match the file pattern "json/*.json". Configuration error?
[2019-12-07T18:19:55.542Z] Finished: FAILURE

Powered by the Comment Logger

@timja
Copy link
Member Author

timja commented Dec 7, 2019

[2019-12-07T18:19:52.298Z] [ERROR] Non-resolvable parent POM for io.jenkins.infra:repository-permissions-updater:1.0-SNAPSHOT: Could not transfer artifact org.jenkins-ci:jenkins:pom:1.36 from/to repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/): Failed to transfer file: https://repo.jenkins-ci.org/public/org/jenkins-ci/jenkins/1.36/jenkins-1.36.pom. Return code is: 502 , ReasonPhrase:Bad Gateway. and 'parent.relativePath' points at wrong local POM @ line 3, column 13 -> [Help 2]

@slide
Copy link
Contributor

slide commented Dec 9, 2019

Needs auth from @ewelinawilkosz for the change to the component yaml.

@timja
Copy link
Member Author

timja commented Dec 9, 2019

Needs auth from @ewelinawilkosz for the change to the component yaml.

It was authorised here:
#1180

One was missed

@slide slide merged commit 980776d into jenkins-infra:master Dec 9, 2019
@timja timja deleted the add-test-harness branch December 9, 2019 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants