My fork is 91 commits behind master #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[JENKINS-38608] Report clearly if the Repo URL is empty
…rrect indentation Co-Authored-By: Raihaan Shouhell <raihaanhimself@gmail.com>
[JENKINS-57660] Addition of a doCheck validation method for invalid refSpec
Bumps [equalsverifier](https://github.com/jqno/equalsverifier) from 3.1.11 to 3.1.12. - [Release notes](https://github.com/jqno/equalsverifier/releases) - [Changelog](https://github.com/jqno/equalsverifier/blob/master/CHANGELOG.md) - [Commits](jqno/equalsverifier@equalsverifier-3.1.11...equalsverifier-3.1.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Add an additional behaviour that disables the multi candidate scheduling. The default behaviour of the git plugin is to check for new changes and trigger a new build for every tip of every branch. When working with big repositories, high build times and many independent branches, this behaviour leads to an unnecessary high resource consumption.
….java Co-Authored-By: Raihaan Shouhell <raihaanhimself@gmail.com>
….java Co-Authored-By: Raihaan Shouhell <raihaanhimself@gmail.com>
….java Co-Authored-By: Raihaan Shouhell <raihaanhimself@gmail.com>
….java Co-Authored-By: Mark Waite <mark.earl.waite@gmail.com>
Bumps [maven-checkstyle-plugin](https://github.com/apache/maven-checkstyle-plugin) from 3.1.0 to 3.1.1. - [Release notes](https://github.com/apache/maven-checkstyle-plugin/releases) - [Commits](apache/maven-checkstyle-plugin@maven-checkstyle-plugin-3.1.0...maven-checkstyle-plugin-3.1.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
I had to read very carefully to detect the syntactic errors in the URL. The comment helps me see more clearly.
Avoid undue load on any one server for this test.
The jsoup jar file is added to the hpi file as a transitive dependency of the configuration as code test harness. The git plugin does not deliver the configuration as code test harness and so it should not deliver the dependencies of that test harness either. We've had issues in the past where other plugins mistakenly depended on a jar file that the git plugin bundled (like joda-time). Better to avoid others from depending on a transitive test dependency by not including the transitive test dependency. The jsoup jar file was included in git plugin 4.1.0 and 4.1.1. Earlier versions did not include it. f3c65cb added the transitive dependency.
Exclude jsoup from git plugin jpi packaging
compile time errors corrected. This reverts commit 454397e.
JENKINS-59828: Expand support for the SCM API 2.0 to support tags
Includes tag support for SCM file system
Set next version to 4.2.0
Refspec expansion is handled in another pull request and should be evaluated separately.
[JENKINS-48625] Restore binding of doCheckUrl methods and add some initial checks
Bumps [plugin](https://github.com/jenkinsci/plugin-pom) from 3.56 to 3.57. - [Release notes](https://github.com/jenkinsci/plugin-pom/releases) - [Changelog](https://github.com/jenkinsci/plugin-pom/blob/master/CHANGELOG.md) - [Commits](jenkinsci/plugin-pom@plugin-3.56...plugin-3.57) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JENKINS-xxxxx - summarize pull request in one line
Describe the big picture of your changes here to explain to the maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, include a link to the issue.
Checklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. This is simply a reminder of what we are going to look for before merging your code. If a checkbox or line does not apply to this pull request, delete it. We prefer all checkboxes to be checked before a pull request is mergedTypes of changes
What types of changes does your code introduce? Put an
xin the boxes that apply. Delete the items in the list that do not applyFurther comments
If this is a relatively large or complex change, start the discussion by explaining why you chose the solution you did and what alternatives you considered.