This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/16/45716/1 in repository toolchain/jenkins-scripts.
discards f2bd8dd39 round-robin-bisect.sh (print_interesting_commit): Re-enable v [...] discards 9f17f9ccc round-robin-bisect.sh (exit_0): Ensure we have permissions to [...] discards 89876ce78 round-robin-notify.sh (update_jira_card): Improve handling of [...] discards f51ae4d13 round-robin-notify.sh (jira cards): Do not update closed cards discards e764a676c round-robin-notify.sh (gnu_print_result): Add links to useful logs discards 60d3d8798 round-robin-notify.sh (gnu_print_result): Improve --long version discards 17d36081f round-robin-notify.sh (print_mail_body): Add more ways to con [...] discards 03877dae5 jenkins-helpers.sh (describe_sha1): Improve describes for bin [...] adds e498d7bff jenkins-helpers.sh (describe_sha1): Improve describes for bin [...]
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference 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 (f2bd8dd39) \ N -- N -- N refs/changes/16/45716/1 (e498d7bff)
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 "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes: round-robin-baseline.sh | 524 -------------- round-robin-bisect.sh | 681 ------------------ round-robin-notify.sh | 1789 ----------------------------------------------- 3 files changed, 2994 deletions(-) delete mode 100755 round-robin-baseline.sh delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh