[JENKINS-71700] avoid stacktrace in artifactarchiver when no artifacts When the validateAntFileMask fails because there are too many files or it takes too long an exception is thrown that was intendend to be catched in the ArtifactArchiver. But when the build happens on an agent and not the built-in, this didn't work as the the exception is deeply wrapped in 2 other exceptions. As printing this information is of no real help, just catch all exceptions and print them to the jenkins log but not the build log. Any other message might just be misleading as one could get the impression that jenkins stopped after looking at 10000 files and only because of this no files where archived but this is not the case. At this place the ArtifactArchiver is just trying to give a hint why it didn't archive anything.
About
In a nutshell, Jenkins is the leading open-source automation server. Built with Java, it provides over 1,800 plugins to support automating virtually anything, so that humans can spend their time doing things machines cannot.
What to Use Jenkins for and When to Use It
Use Jenkins to automate your development workflow, so you can focus on work that matters most. Jenkins is commonly used for:
- Building projects
- Running tests to detect bugs and other issues as soon as they are introduced
- Static code analysis
- Deployment
Execute repetitive tasks, save time, and optimize your development process with Jenkins.
Downloads
The Jenkins project provides official distributions as WAR files, Docker images, native packages and installers for platforms including several Linux distributions and Windows. See the Downloads page for references.
For all distributions Jenkins offers two release lines:
- Weekly - Frequent releases which include all new features, improvements, and bug fixes.
- Long-Term Support (LTS) - Older release line which gets periodically updated via bug fix backports.
Source
Our latest and greatest source of Jenkins can be found on GitHub. Fork us!
Contributing to Jenkins
Follow the contributing guidelines if you want to propose a change in the Jenkins core. For more information about participating in the community and contributing to the Jenkins project, see this page.
Documentation for Jenkins core maintainers is in the maintainers guidelines.
News and Website
All information about Jenkins can be found on our website. Follow us on Twitter or LinkedIn.
Governance
See the Jenkins Governance Document for information about the project's open governance, our philosophy and values, and development practices. Jenkins Code of Conduct can be found here.
Adopters
Jenkins is used by millions of users and thousands of companies. See adopters for the list of Jenkins adopters and their success stories.
License
Jenkins is licensed under the MIT License.