Bump org.jenkins-ci:jenkins from 1.104 to 1.105 #529
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
|
@dduportal this looks like an interesting failure related to artifact caching. |
Currently checking the result with the current brownout (e.g. falling back to apache central) |
|
One of your CI runs failed on this pull request, so Dependabot won't merge it. Dependabot will still automatically merge this pull request if you amend it and your tests pass. |
|
The error also happens on the Currently trying to reproduce locally (e.g. outside ci.jenkins.io). I'm wondering if the |
|
GOTCHA @MarkEWaite : the culprit is Line 242 in 043e1e0 When jenkins-infra/jenkins-infra#2992 was deployed to ci.jenkins.io, it created the But none of these Line 242 in 043e1e0 Btw, the Artifactory brownout with "Apache Central" removal did not have any change on the error which is a positive thing! |
|
Note for maintainers: this PR has the same check failures as the principal branch: it is not related to the PR change itself. |
|
@dependabot recreate |
Bumps [org.jenkins-ci:jenkins](https://github.com/jenkinsci/pom) from 1.104 to 1.105. - [Release notes](https://github.com/jenkinsci/pom/releases) - [Changelog](https://github.com/jenkinsci/pom/blob/master/CHANGELOG-old.md) - [Commits](jenkinsci/pom@jenkins-1.104...jenkins-1.105) --- updated-dependencies: - dependency-name: org.jenkins-ci:jenkins dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/maven/org.jenkins-ci-jenkins-1.105
branch
from
920aab8
to
f73b1ac
Compare
dependabot
bot
deleted the
dependabot/maven/org.jenkins-ci-jenkins-1.105
branch
Bumps org.jenkins-ci:jenkins from 1.104 to 1.105.
Release notes
Sourced from org.jenkins-ci:jenkins's releases.
Commits
f201ef0[maven-release-plugin] prepare release jenkins-1.10539e6310Bump com.diffplug.spotless:spotless-maven-plugin from 2.38.0 to 2.39.0 (#476)a2473f4Make JUnit version a customizable property (#474)56c5c70Fix Hamcrest versioning (#475)2c77cf0Bump org.mockito:mockito-bom from 5.4.0 to 5.5.0 (#473)b620a93Bump org.apache.maven.plugins:maven-enforcer-plugin from 3.3.0 to 3.4.0 (#472)679c8e8[maven-release-plugin] prepare for next development iterationDependabot 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 will merge this PR once CI passes on it, as requested by @MarkEWaite.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)