Jenkins Continuous Integration Server
Go to file
R. Tyler Croy 998f3db818
Refactor the flip() function to use an event argument
This makes the flip() function for all the tabs, available and other, consistent.
2018-08-23 17:44:20 -07:00
.github Address comment from @daniel-beck 2017-06-22 09:16:38 +02:00
.mvn Update parent POM. 2018-07-30 14:38:04 -04:00
cli [maven-release-plugin] prepare for next development iteration 2018-08-13 09:09:55 -07:00
core Refactor the flip() function to use an event argument 2018-08-23 17:44:20 -07:00
src [JENKINS-36717] - Remove FindBugs priority filters since they do not actually impact the build 2016-08-01 19:55:58 +03:00
test Merge pull request #3527 from ericyu2018/JENKINS-52181 2018-08-19 15:37:54 +02:00
war [maven-release-plugin] prepare for next development iteration 2018-08-13 09:09:55 -07:00
.gitattributes Add .gitattributes to embed standard IN the repo 2016-10-04 11:34:32 +02:00
.gitignore Picking up https://github.com/jenkinsci/pom/pull/25. 2018-05-14 14:35:17 -04:00
.jenkins
BUILDING.TXT Remove not existed build variable 2017-01-06 19:48:46 +03:00
CONTRIBUTING.md Update CONTRIBUTING.md 2018-07-17 01:36:06 +02:00
Jenkinsfile Avoid CI failures pending reincrementalifization. 2018-05-07 09:39:26 -04:00
LICENSE.txt
README.md Reference redirectors and jenkins.io as much as possible (#2756) 2017-02-25 19:56:01 +01:00
assembly-src.xml Revisit the source bundle creation 2014-08-18 20:58:45 -07:00
changelog.html Remove changelog from jenkinsci/jenkins repository (#2757) 2017-02-19 21:06:25 +01:00
dummy.keystore
essentials.yml [JENKINS-50585] Explicitly declared core builds against ATH smoke tests only 2018-04-06 10:19:46 +02:00
licenseCompleter.groovy Reference redirectors and jenkins.io as much as possible (#2756) 2017-02-25 19:56:01 +01:00
packaging-ref.txt Capture the corresponding branch/tag in jenkinsci/packaging to be used. 2018-05-10 08:55:05 +12:00
pom.xml [maven-release-plugin] prepare for next development iteration 2018-08-13 09:09:55 -07:00
settings-azure.xml [INFRA-1176] Using repo.azure.jenkins.io as a mirror for CI builds. 2017-05-18 17:28:25 -04:00
show-pom-version.rb
translation-tool.pl Fix translation tool entered newlines 2017-03-06 18:36:29 +01:00

README.md

About

In a nutshell, Jenkins is the leading open-source automation server. Built with Java, it provides over 1000 plugins to support automating virtually anything, so that humans can actually 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

Non-source downloads such as WAR files and several Linux packages can be found on our Mirrors.

Source

Our latest and greatest source of Jenkins can be found on GitHub. Fork us!

Contributing to Jenkins

Follow contributing file.

News and Website

All information about Jenkins can be found on our website. Follow us on Twitter @jenkinsci.

License

Jenkins is licensed under the MIT License. The terms of the license are as follows:

The MIT License (MIT)

Copyright (c) 2004 Kohsuke Kawaguchi, Sun Microsystems Inc., and a number of other contributors. 

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.