This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/31/42331/1
in repository toolchain/jenkins-scripts.
discards a1803d1a2 dashboard-generate-squad.sh: Fix vs-first dashboard mode
new 6cb7295a3 dashboard-generate-squad.sh: Fix vs-first dashboard mode
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 (a1803d1a2)
\
N -- N -- N refs/changes/31/42331/1 (6cb7295a3)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/31/41931/2
in repository toolchain/jenkins-scripts.
discards 4c4b1ee61 jenkins-helpers.sh (clone_or_update_repo_no_checkout): Update
adds 79c215266 jenkins-helpers.sh (clone_or_update_repo_no_checkout): Update
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 (4c4b1ee61)
\
N -- N -- N refs/changes/31/41931/2 (79c215266)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/31/41931/1
in repository toolchain/jenkins-scripts.
discards 782d7160b jenkins-helpers.sh (clone_or_update_repo_no_checkout): Update
new 1fb1c69ad jenkins-helpers.sh (clone_or_update_repo_no_checkout): Update
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 (782d7160b)
\
N -- N -- N refs/changes/31/41931/1 (1fb1c69ad)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/31/41831/4
in repository toolchain/jenkins-scripts.
discards 90ca8ebf5 round-robin-bisect.sh: Trigger builds for last-good revisions
adds b6191e131 round-robin-bisect.sh: Trigger builds for last-good revisions
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 (90ca8ebf5)
\
N -- N -- N refs/changes/31/41831/4 (b6191e131)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/31/41831/3
in repository toolchain/jenkins-scripts.
discards 1e23e9a2c round-robin-bisect.sh: Trigger builds for last-good revisions
new e7b6a295f round-robin-bisect.sh: Trigger builds for last-good revisions
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 (1e23e9a2c)
\
N -- N -- N refs/changes/31/41831/3 (e7b6a295f)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/31/41831/2
in repository toolchain/jenkins-scripts.
discards f3f83a3a3 round-robin-bisect.sh: Trigger builds for last-good revisions
new e78b88d91 round-robin-bisect.sh: Trigger builds for last-good revisions
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 (f3f83a3a3)
\
N -- N -- N refs/changes/31/41831/2 (e78b88d91)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/31/41831/1
in repository toolchain/jenkins-scripts.
discards 20a51db7b round-robin-bisect.sh: Trigger builds for last-good revisions
discards 836b21266 round-robin.sh: Fix "git rev-parse" of short histories
adds d90fd211c round-robin.sh: Fix "git rev-parse" of short histories
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 (20a51db7b)
\
N -- N -- N refs/changes/31/41831/1 (d90fd211c)
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-bisect.sh | 870 --------------------------------------------------
1 file changed, 870 deletions(-)
delete mode 100755 round-robin-bisect.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/31/38531/3
in repository toolchain/jenkins-scripts.
discards acf08dc66 tcwg-start-container.sh: Handle starting QEMU-based containers
adds 7b15c9769 tcwg-start-container.sh: Handle starting QEMU-based containers
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 (acf08dc66)
\
N -- N -- N refs/changes/31/38531/3 (7b15c9769)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/31/38531/2
in repository toolchain/jenkins-scripts.
discards d1a209287 tcwg-start-container.sh: Handle starting QEMU-based containers
new 23f80cf0f tcwg-start-container.sh: Handle starting QEMU-based containers
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 (d1a209287)
\
N -- N -- N refs/changes/31/38531/2 (23f80cf0f)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/31/38531/1
in repository toolchain/jenkins-scripts.
discards b2b7fd7b2 tcwg-start-container.sh: Handle starting QEMU-based containers
new 8d5866e32 tcwg-start-container.sh: Handle starting QEMU-based containers
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 (b2b7fd7b2)
\
N -- N -- N refs/changes/31/38531/1 (8d5866e32)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.