-
Improvement
-
Resolution: Unresolved
-
Trivial
-
None
We are using that Jenkins plugin in some of the customers so the IT team requests to add a license file.
Export - CSV (All fields)
Export - CSV (Current fields)
Search
- JENKINS-75025Add LICENSE file to GitHub repo of Build Timeout plugin
- JENKINS-69595ClassCastException-warning in case of a matrix-job (multi-configuration project)
- JENKINS-62956build timeout does not stop a multi-configuration project
- JENKINS-57476Build timeout should include only successful builds, not unstable builds
- JENKINS-57263Java java.lang.ClassNotFoundException on Jenkins Startup
- JENKINS-45174Time-out strategy Deadline for specific days
- JENKINS-41584Plugin functionality missing in pipeline API
- JENKINS-27396Elastic timeout in pipeline
- JENKINS-26778Build-timeout+Plugin global timeout setting
- JENKINS-26563BlockableBuildTrigger invokes build timeout
- JENKINS-23137Show a message in the console log when a build timeout occurs
- JENKINS-19883Thread dump when a build time out
- JENKINS-16875Builds do not timeout when job hangs in post build actions
- JENKINS-12744Execute a command before timeout
- JENKINS-11064Update ambiguous ABORTED message to "TIMED OUT" and fix raised InterruptedException
- JENKINS-9716allow timeouts to occur during pre-build
- JENKINS-2936Using build-timeout plugin to stop build but not force the build abort or failed
- JENKINS-789build-timeout — ver.1.3: should kill the all process tree.
1 of 18
Add LICENSE file to GitHub repo of Build Timeout plugin
-
Kohsuke Kawaguchi
-
vanashri
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated:
The license for the plugin is specified in its pom.xml. The Apache Maven build process stores the license in the plugin binary. The license information for all installed plugins can be displayed in Jenkins from the "Manage Jenkins" ==> "About Jenkins" page in the "License and dependency information for plugins" tab. License information for the plugin is already available for Jenkins users without adding a LICENSE file to the root directory of the source code repository.
If it is important to your organization that there also be a copy of the license in the root directory of the source code repository, you are welcome to submit a pull request that proposes the license text. Plugin maintainers can then decide if they want to merge your proposed pull request. If the plugin uses an MIT license, then you can refer to the Jenkins plugin archetype for the LICENSE.md file that is included in plugins created from the archetype.
I've downgraded this issue from Critical to Trivial because the requested improvement does not change the licensing of the plugin and does not help other users of the plugin.