Mark Waite
f59a5d4536
* Reduce inQueueTaskLookupByAPI flakiness https://app.launchableinc.com/organizations/jenkins/workspaces/jenkins/data/test-paths/class%3Dhudson.model.QueueTest%23%23%23testcase%3DinQueueTaskLookupByAPI?dateFilter=90d reports that inQueueTaskLookupByAPI has been flaky in th epast 90 days. The flakiness seems to be specific to Windows and seems to be related to the job not be in the queue quickly enough after the call toe schedule the build. If the job is not queued, sleep for 3 seonds to allow it time to queue. Testing done: Confirmed that the job queues consistently on my Linux computer, so the sleep statement is not executed. * Replace SCSS 1x with 1dppx to silence HTMLUnit warning Per https://developer.mozilla.org/en-US/docs/Web/CSS/resolution , `x` is an alias for `dppx`, so let's use `dppx` to avoid warnings from HTMLUnit. * Reduce flakiness of ComputerStateTest#testUiForConnected https://app.launchableinc.com/organizations/jenkins/workspaces/jenkins/data/test-paths/class%3Dhudson.cli.ComputerStateTest%23%23%23testcase%3DtestUiForConnected?dateFilter=90d reports that there have been multiple failures of ComputerStateTest#testUiForConnected in the last 90 days. The failures seem to be related to a race condition that the agent is not yet disconnected when the state of the agent is checked. Wait for 1 second to allow the agent to disconnect before checking agent status. The average time to run the test is 34 seconds. This will increase that average time by 1 second. Not a significant increase compared to the benefit of avoiding a flaky test. * Reduce preventXssInBadgeTooltip flakes with a 2 second sleep https://app.launchableinc.com/organizations/jenkins/workspaces/jenkins/data/test-paths/class%3Dhudson.model.RunTest%23%23%23testcase%3DpreventXssInBadgeTooltip?dateFilter=90d shows there have been random test failures of preventXssInBadgeTooltip in the last 90 days. Reeduce failures by sleeping before the key assertions in order to allow Jenkins to complete the initialization of the page.
About
In a nutshell, Jenkins is the leading open-source automation server. Built with Java, it provides over 2,000 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.
Latest releases:
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.