This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git
omit d6ff979c14e Regen for commit 25f1cb6670989b39104b1340cfc5a3e1e0ad8f4e
add 9126bd631e0 Removing JenkinsFile for JDK 11 not needed on Camel 4.x
add 70faf693798 Jenkinsfile for S390x should use JDK 17
add 6aaeee2a19c Jenkinsfile for deployment should use JDK 17
add c2e0c754fa8 CAMEL-18879 - Remove Camel-Zipkin after deprecation -
Added migration notes
add 8e325d32525 Regen for commit c2e0c754fa86dc1e01e253ab60e5e224386da324
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d6ff979c14e)
\
N -- N -- N refs/heads/regen_bot (8e325d32525)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
Jenkinsfile.deploy | 2 +-
Jenkinsfile.jdk11 | 108 ---------------------
Jenkinsfile.s390x | 2 +-
.../ROOT/pages/camel-4-migration-guide.adoc | 4 +
4 files changed, 6 insertions(+), 110 deletions(-)
delete mode 100644 Jenkinsfile.jdk11
