Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed plugin builds due to missing Windows configuration file #3424

Closed
MarkEWaite opened this issue Mar 6, 2023 · 5 comments
Closed

Failed plugin builds due to missing Windows configuration file #3424

MarkEWaite opened this issue Mar 6, 2023 · 5 comments

Comments

@MarkEWaite
Copy link

Service(s)

ci.jenkins.io

Summary

Multiple plugin builds failed on the Windows agents of ci.jenkins.io due to a missing system configuration file.

https://ci.jenkins.io/job/Plugins/job/apache-httpcomponents-client-4-api-plugin/job/PR-127/1/ is one example.

Reproduction steps

  1. Run a pull request build on ci.jenkins.io of a plugin that includes Windows in its Jenkinsfile configuration
  2. Confirm that the build fails due to a missing settings file with the name null
@MarkEWaite MarkEWaite added the triage Incoming issues that need review label Mar 6, 2023
@dduportal
Copy link
Contributor

The error in the build you linked is java.io.FileNotFoundException: The specified user settings file does not exist: C:\Jenkins\workspace\nents-client-4-api-plugin_PR-127\null.

This path does not look to be a missing file, but an issue in the pipeline code.

More precisely: the mvn command is mvn --batch-mode --show-version --errors --no-transfer-progress -s null --update-snapshots -Dmaven.repo.local=C:/Jenkins/workspace/nents-client-4-api-plugin_PR-127@tmp/m2repo -Dmaven.test.failure.ignore -Dspotbugs.failOnError=false -Dcheckstyle.failOnViolation=false -Dcheckstyle.failsOnError=false -Dset.changelist clean install

=> the -s null is clearly the source of the problem, which looks like a jenkins-infra/pipeline-library problem.

cc @lemeurherve

@dduportal
Copy link
Contributor

Might be related to #3422

@lemeurherve
Copy link
Member

The issue here was that the Windows build ran from an agent in Azure, and since it was unavailable (cf #3425), the health check failed, but as there was a bug in infra.runMaven, the null settings.xml was added to Maven options.

jenkins-infra/pipeline-library#611 should fix it.

@dduportal
Copy link
Contributor

Triggered a new build #2: https://ci.jenkins.io/job/Plugins/job/apache-httpcomponents-client-4-api-plugin/job/PR-127/2/ now that jenkins-infra/pipeline-library#611 is merged (and applied following a pipeline-library cache clear)

@dduportal
Copy link
Contributor

Last build (#2) ran succesfully the windows-11 on Azure and used the Azure ACP as per the logs: I'm closing the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants