Branch: refs/heads/master
Home: https://github.com/jenkinsci/git-client-plugin
Commit: c6e94fc334ffcb0c64a31d6b495d1bb38ca0edb8
https://github.com/jenkinsci/git-client-plugin/commit/c6e94fc334ffcb0c64a31d6b495d1bb38ca0edb8
Author: Jacob Keller <[email protected]>
Date: 2015-07-28 (Tue, 28 Jul 2015)
Changed paths:
M src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java
Log Message:
-----------
add Submodule Update test
Add a new test to the GitAPI test cases that initializes and update
submodules in order to add more coverage of submodules before making any
new changes.
Signed-off-by: Jacob Keller <[email protected]>
Commit: bee128b84a87e770af77ded1f7e2d056bd19a305
https://github.com/jenkinsci/git-client-plugin/commit/bee128b84a87e770af77ded1f7e2d056bd19a305
Author: Jacob Keller <[email protected]>
Date: 2015-07-29 (Wed, 29 Jul 2015)
Changed paths:
M src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java
A src/test/java/org/jenkinsci/plugins/gitclient/StringSharesPrefix.java
Log Message:
-----------
fix git describe test case for uneven commit abbreviation length
git describe will honor the "core.abbrev" setting from the gitconfig,
(thus CLI implementation will as well). This potentially breaks the JGit
test of git describe as implementations may not return the exact same
length for an abbreviated hash. Fix this by implementing
StringSharesPrefix matcher based on SubstringMatcher from hamcrest.
We can't use the startsWith matcher due to not knowing which particular
string will actually contain the shorter prefix. However, we want to
allow both cases as long as the total string continues to match up to
the end of either string.
This fixes a test failure if a user has customized their Git
configuration to provide a larger default abbreviation (such as for
working with incredibly large projects like the Linux kernel). We
shouldn't fail the test just because the JGit implementation returns
fewer characters.
Note that we will have to update StringSharesPrefix if we ever update
the hamcrest version requirement, as the upstream has changed.
Signed-off-by: Jacob Keller <[email protected]>
Commit: 986619f08a7774d37557cc61dbd09a78e2ed8aec
https://github.com/jenkinsci/git-client-plugin/commit/986619f08a7774d37557cc61dbd09a78e2ed8aec
Author: Jacob Keller <[email protected]>
Date: 2015-07-30 (Thu, 30 Jul 2015)
Changed paths:
M src/test/java/org/jenkinsci/plugins/gitclient/PushSimpleTest.java
Log Message:
-----------
rework tricky pushNoRefSpec test to be explicit
Do not test "no refspec" push behavior, as this is user configurable and
infact the default changed in Git 2.0 Despite this change, the new
default still functions with the supplied test, but we should not rely
on this behavior. Instead, re-write this test to be "pushCurrent" and
ensure we explicitly mention "HEAD" as the ref to push (rather than our
configured refspec). In this way, we can ensure this test succeeds even
if the CLI implementation has a different configured default push mode,
and we are actually testing what we think.
I considered removing the test altogether, however this breaks other
tests which depend on commits being pushed into the remote, which does
not have a 2nd commit until we complete this initial test. Due to this,
it is simpler to just redefine this test to work regardless of how the
user configured the default settings.
Signed-off-by: Jacob Keller <[email protected]>
Commit: ec0dfde6e43fb1bb747c6b58505b6b8dcdadab3e
https://github.com/jenkinsci/git-client-plugin/commit/ec0dfde6e43fb1bb747c6b58505b6b8dcdadab3e
Author: Mark Waite <[email protected]>
Date: 2015-07-31 (Fri, 31 Jul 2015)
Changed paths:
M src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java
M src/test/java/org/jenkinsci/plugins/gitclient/PushSimpleTest.java
A src/test/java/org/jenkinsci/plugins/gitclient/StringSharesPrefix.java
Log Message:
-----------
Merge pull request #178 from jacob-keller/jk-submodule-tests
add and fix tests
Compare:
https://github.com/jenkinsci/git-client-plugin/compare/ff9c21927753...ec0dfde6e43f
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
