-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure reporting #1337
Failure reporting #1337
Conversation
…rmPom` to HPI plugin `overrideWar`
interesting test failures 🤔 Complains about Jenkins.instance is missing inside jcasc methods 😓 Makes no sense? 🤔
|
Ah the one in
and |
Seems that with |
interesting see joda-time upperbound warnings. We really ought to have it removed... Use java 8 time libraries 😅 |
pct.sh
Outdated
@@ -40,7 +40,8 @@ MAVEN_PROPERTIES+=":jenkins.version=${JENKINS_VERSION}:overrideWar=$(pwd)/megawa | |||
# TODO When all plugins in the managed set are using a plugin parent POM with HPI Plugin 3.29 or | |||
# later (i.e., plugin parent POM 4.44 or later), this can be deleted. | |||
# | |||
MAVEN_PROPERTIES+=:hpi-plugin.version=3.30 | |||
# TODO https://github.com/jenkinsci/maven-hpi-plugin/pull/368 | |||
MAVEN_PROPERTIES+=:hpi-plugin.version=3.31-rc1289.8ccff91f4e1a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
huh pretty useful being able to force HPI higher, not sure this is even a hack at this point. Especially when we need to fix a potential bug.
This reverts commit 39615e5.
Bumps [theme-manager](https://github.com/jenkinsci/theme-manager-plugin) from 1.4 to 1.5. - [Release notes](https://github.com/jenkinsci/theme-manager-plugin/releases) - [Commits](jenkinsci/theme-manager-plugin@theme-manager-1.4...theme-manager-1.5) --- updated-dependencies: - dependency-name: io.jenkins.plugins:theme-manager dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
OK, I figured out the compatibility problem between Git and Subversion:
I was able to chase away the problem with this patch to Subversion:
|
Git/Subversion issue fixed in jenkinsci/subversion-plugin#273, hacked in 503c1e6 |
Bumps `subversion-plugin.version` from 2.15.5 to 2.16.0. Updates `subversion` from 2.15.5 to 2.16.0 - [Release notes](https://github.com/jenkinsci/subversion-plugin/releases) - [Changelog](https://github.com/jenkinsci/subversion-plugin/blob/master/docs/old-changelog.md) - [Commits](jenkinsci/subversion-plugin@subversion-2.15.5...subversion-2.16.0) Updates `subversion` from 2.15.5 to 2.16.0 - [Release notes](https://github.com/jenkinsci/subversion-plugin/releases) - [Changelog](https://github.com/jenkinsci/subversion-plugin/blob/master/docs/old-changelog.md) - [Commits](jenkinsci/subversion-plugin@subversion-2.15.5...subversion-2.16.0) --- updated-dependencies: - dependency-name: org.jenkins-ci.plugins:subversion dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: org.jenkins-ci.plugins:subversion:tests dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Checking to see how close we are to resolving #895.