-
Notifications
You must be signed in to change notification settings - Fork 54
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
Bump groovy from 1.9 to 2.2 #174
Bump groovy from 1.9 to 2.2 #174
Conversation
Bumps [groovy](https://github.com/jenkinsci/groovy-plugin) from 1.9 to 2.2. - [Release notes](https://github.com/jenkinsci/groovy-plugin/releases) - [Changelog](https://github.com/jenkinsci/groovy-plugin/blob/master/CHANGELOG.md) - [Commits](jenkinsci/groovy-plugin@groovy-1.9...groovy-2.2) --- updated-dependencies: - dependency-name: org.jenkins-ci.plugins:groovy dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
I guess I will need some help with this one. |
Its faling on:
Its failing on this line:
I am not sure how to fix that. |
Neither am I. As far as I understand, |
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.
Thanks a lot for unblocking, Mark.
You found a new way of getting the list of installations that I could not find.
Bumps groovy from 1.9 to 2.2.
Changelog
Sourced from groovy's changelog.
... (truncated)
Commits
0ace219
[maven-release-plugin] prepare release groovy-2.240777c2
[SECURITY-1338] Prevent unsandboxed invocation of constructorsc536a7c
[maven-release-plugin] prepare for next development iteration60dbd79
[maven-release-plugin] prepare release groovy-2.1212e048
[SECURITY-1293] Secure the script check in StringScriptSourceda0739d
[maven-release-plugin] prepare for next development iterationad965ad
[maven-release-plugin] prepare release groovy-2.0fe1a3ee
Address not-actually-plausible FB errorfcdff05
Found that FileSystemScriptSource did not work. (This scenario apparently had...3adafe1
Strengthening test to assert OldDataMonitor behavior.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.