| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Replace the current license header in files by
a SPDX-License-Identifier.
License files are organized under LICENSES directory.
Pick-to: master
Task-number: QTBUG-67283
Change-Id: I6ae743e055bbf1cf514abe604157068923fb03c6
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
- Remove unnecessary license files and license header templates
- Tools and test are licensed under GPL-EXCEPT nowdays, update correct
license header there
- Update test data to match current license headers
Change-Id: Ia25c9e0989be326e0edeb0325af399edc26f0054
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
|
|
|
|
|
|
|
|
|
| |
Qt copyrights are now in The Qt Company, so we could update the source
code headers accordingly. In the same go we should also fix the links to
point to qt.io.
Change-Id: I5999ee256134fe82ab13f6f06fcd1d0aa150b688
Reviewed-by: Sergio Ahumada <sahumada@texla.cl>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change was introduced by d2306fbb17c0f544e960d5cae4097c8e07dbf68f
not ok 136 - [monitor-jenkins-build http error] http url
# Failed test '[monitor-jenkins-build http error] http url'
# at /home/seahumad/GIT/Gerrit/codereview/qt/qtqa/scripts/jenkins/t/../../lib/perl5/QtQA/WWW/Util.pm line 79.
# got: 'http://jenkins.example.com/job/prjA/1234/api/json?depth=2&tree=building,number,url,result,fullDisplayName,timestamp,duration,runs[building,number,url,result,fullDisplayName,timestamp,duration]'
# expected: 'http://jenkins.example.com/job/prjA/1234/api/json?depth=2&tree=building,number,url,result,fullDisplayName,runs[building,number,url,result,fullDisplayName]'
Change-Id: I0f4b64559cd706d55c85d42f798d8b5778a0efb8
Reviewed-by: Simo Fält <simo.falt@digia.com>
Reviewed-by: Tony Sarajärvi <tony.sarajarvi@digia.com>
|
|
|
|
|
|
| |
Change-Id: I02eaa709ff91d158a3e34f4e719254f2adce873e
Reviewed-by: Simo Fält <simo.falt@digia.com>
Reviewed-by: Janne Anttila <janne.anttila@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The autotest is extended to cover all CI system states.
All possible state transitions are tested, but a few side-effects of
states aren't thoroughly tested; these are marked as TODO.
qt-jenkins-integrator.pl received a couple of trivial bug fixes and had
a few things made configurable/mockable for better testability.
Change-Id: Ia8469c8679678c4752c25c92d7e1340bf1ddcd60
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In an email, a line consisting only of '--' is triggered as the
signature delimiter in some clients. Avoid that.
A single '--' to delimit large blocks of preformatted text is also not
very visually distinct, so make it wider, somewhat like this:
Failure log for configuration 1
==========================================================
Failure log for configuration 2
Change-Id: I2c5a5813f245c70e6e2a1592504f1be27e3c9d41
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
Reviewed-by: Janne Anttila <janne.anttila@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This script implements a quality-gate workflow, using Gerrit as the
source of commits to be tested, and Jenkins as the testing tool.
Features / improvements over the earlier integrator include:
- a single process manages all projects, rather than one process per
project
- no polling required (where network architecture permits); uses
gerrit stream-events and jenkins post-build events
- no git checkouts required on the machine running the integrator
- warnings and errors are automatically buffered and sent as emails
- a read-only remote API is available to retrieve the CI state in JSON
format
This replaces the qt-jenkins-ci.pl script called from within Jenkins,
inverting the responsibility; Jenkins is contained within the CI
workflow rather than the CI workflow being contained within Jenkins.
Since the new integrator requires a lot of functionality in common with
other Jenkins-related scripts, some of this was extracted out into new
QtQA modules.
Change-Id: I8bf28ba9885b04935181b0c48ae2c35c211cce91
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
|
|
|
|
|
|
|
| |
Change copyrights and license headers from Nokia to Digia
Change-Id: I0122cd74f6246a5f20eee2b33ceb328df77a32db
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
|
|
|
|
|
|
|
| |
Test a few more cases, including one recently fixed crash.
Change-Id: I4f42fa4dae033bdc9bac2d1b68a6f16984d0fb2c
Reviewed-by: Sergio Ahumada <sergio.ahumada@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to the recent change introducing YAML support to
parse_build_log.pl, this change allows YAML output so that the caller
can unambiguously parse the output of this script.
Metadata from parse_build_log.pl is passed through unaltered; most
notably, whether or not the build should be retried.
Change-Id: I77f928e4dacc77117244fa551d0ba1956fb110cd
Reviewed-by: Sergio Ahumada <sergio.ahumada@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a human aborted a build in progress, it makes sense to simply report
the build as "ABORTED" (perhaps along with the name of the aborter).
If the CI system aborted a build because it saw that some build
configurations had already failed, it makes sense to ignore the
"ABORTED" status and report the failing configurations instead.
This commit adds a command-line option, --ignore-aborted, to toggle
between the two above behaviors.
Change-Id: I31fc984ea64ac586f0dd4d004a8602e5c14354d1
Reviewed-by: Sergio Ahumada <sergio.ahumada@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were running ln with the `-f' parameter with the intent of
overwriting existing links. However, if the link target was a directory,
ln would dereference the link and create a link inside the directory.
Therefore, for a new project, we'd create the first link:
latest -> build_00001
... as expected, but subsequent links would be created _inside_ of the
'latest' (actually build_00001) directory:
build_00001/build_00002 -> build_00002
build_00001/build_00003 -> build_00003
...
This is fixed by passing the -n / --no-dereference option to the ln
commands.
Change-Id: I1f188567d2580451236d5b90f86a737143860bb7
Reviewed-by: Kalle Lehtonen <kalle.ju.lehtonen@nokia.com>
|
|
|
|
|
|
|
|
|
| |
This option (to summarize-jenkins-build.pl) was renamed from --log-url
to --log-base-url during development, but a few uses of it still had the
old name.
Change-Id: I29733c32c5cfa9a67bc4b2e94d98b0bd6f54758b
Reviewed-by: Kalle Lehtonen <kalle.ju.lehtonen@nokia.com>
|
|
|
|
|
|
|
| |
Lists each tested change with a hyperlink.
Change-Id: I77fb19a9a1ce585d73321736f5f1d64c712f5dd3
Reviewed-by: Kalle Lehtonen <kalle.ju.lehtonen@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
When run with --pretend, the CI script does not actually create new
gerrit builds or pass/fail them, but rather triggers tests directly from
the staging branch and prints what the result would be. This can be
used to operate a development CI on a gerrit instance which tests
roughly the same content as a real CI.
Change-Id: I739daaff91b967b4e96b99f12ce44ec67c131186
Reviewed-by: Kalle Lehtonen <kalle.ju.lehtonen@nokia.com>
Reviewed-by: Toby Tomkins <toby.tomkins@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow qt-jenkins-ci.pl to put compressed logs on another host when a
build has completed, and allow summarize-jenkins-build.pl to generate
links referring to that host.
This supports a setup where the Jenkins build data may be deleted
without notice, or where the Jenkins server is not publicly accessible.
Change-Id: I48a66866ad56fa7df74b190927b192c9f4cb22df
Reviewed-by: Kalle Lehtonen <kalle.ju.lehtonen@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The qt-jenkins-ci.pl script implements the workflow used by the Qt
Project CI system from within Jenkins. Pre and post steps are used to
create and approve (pass or fail) gerrit builds. Meaningful failure
summaries are posted into gerrit as comments.
The qt-jenkins-ci.pl script contains documentation on how the script can
be set up within Jenkins.
Basic autotests are included; their coverage should be expanded.
Change-Id: I111ebc0f627ca26258bf4e07c6bd7806263dd539
Reviewed-by: Toby Tomkins <toby.tomkins@nokia.com>
|
|
summarize-jenkins-build.pl may be used to summarize the result of a
build in a form suitable for posting as a gerrit comment.
This script is primarily a glue between Jenkins' JSON API and the
existing parse_build_log.pl and does not itself contain any logic for
parsing logs.
Change-Id: I372eb5b75d1a41ceb6482af9f7443d6e66bb0423
Reviewed-by: Kalle Lehtonen <kalle.ju.lehtonen@nokia.com>
|