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 8e325d32525 Regen for commit c2e0c754fa86dc1e01e253ab60e5e224386da324
add ab5400ec888 Remove Jenkinsfile for full pipeline
add 295d403fb46 CAMEL-18877 - camel-caffeine - Key should be string type -
Migration notes
add f22a53dc176 Regen for commit 295d403fb46c74b7954b24ead9414b20d6b20253
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 (8e325d32525)
\
N -- N -- N refs/heads/regen_bot (f22a53dc176)
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.full.pipeline | 69 ----------------------
.../ROOT/pages/camel-4-migration-guide.adoc | 4 ++
2 files changed, 4 insertions(+), 69 deletions(-)
delete mode 100644 Jenkinsfile.full.pipeline
