| Age | Commit message (Collapse) | Author |
|---|
|
Also use the GERRITHOST variable instead of magic text.
Change-Id: I3314be81017f64fca8aa756cca1715081ad01641
Reviewed-on: https://gerrit.libreoffice.org/41988
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Meeks <michael.meeks@collabora.com>
Tested-by: Michael Meeks <michael.meeks@collabora.com>
|
|
Change shebang to bash since -p option is used in read command,
use $(..) instead of `..`,
double quote to prevent word splitting,
handle cd failure.
Change-Id: I2ae00bbd21754136610504f2ff6818b8d3695cc4
Reviewed-on: https://gerrit.libreoffice.org/33089
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: jan iversen <jani@documentfoundation.org>
|
|
Recently some new developers accidentally used "resubmit", intending to
upload a new revision of their change, but it actually always creates a
new gerrit change.
4e15809a78ea3c6062e20e439cf8df3d06cd8569 claims that "resubmit creates a
new Change-Id for the current change and thus allow to submit changes for
review on release branches that were already reviewed on master", but
that is not actually required with gerrit versions that were in use in
the recent years, gerrit is capable of tracking Change-Id per branch.
Change-Id: I66eda4dbc6f4ff1e235105b3f55041cda88a6b60
|
|
- ./logerrit testfeature will trigger a testbuild of the
current feature branch as it is on gerrit
- ./logerrit testfeature $BRANCH will do the same for $BRANCH
- cloning to a tempdir and rm -rf'ing around isnt ideal, so
consider this as a template for your own scripting
Change-Id: I50a3c80748af82d855522f245ddbff227c8adab2
|
|
Change-Id: Ic8196ebfeef64270fcd42b44e485a2618472f184
Reviewed-on: https://gerrit.libreoffice.org/11788
Reviewed-by: Samuel Mehrbrodt <s.mehrbrodt@gmail.com>
Tested-by: Samuel Mehrbrodt <s.mehrbrodt@gmail.com>
|
