See
<
https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.com/job/...
Changes:
------------------------------------------
Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on rhel7-releng-253 (rhel7-devstudio-releng rhel7-releng) in workspace
<
https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.com/job/...
The recommended git tool is: NONE
using credential devstudio-release
Cloning the remote Git repository
Cloning repository git@github.com:jbosstools/jiralint
Fetching upstream changes from git@github.com:jbosstools/jiralint
git --version # timeout=10
git --version # 'git version 1.8.3.1'
using GIT_SSH to set credentials key
used to push commits and tags via devstudio-release user to jbosstools repos
[INFO] Currently running in a labeled security context
[INFO] Currently SELinux is 'enforcing' on the host
Verifying host key using manually-configured host key entries
git fetch --tags --progress git@github.com:jbosstools/jiralint
+refs/heads/*:refs/remotes/origin/* # timeout=10
git config remote.origin.url git@github.com:jbosstools/jiralint # timeout=10
git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
git rev-parse origin/main^{commit} # timeout=10
Checking out
Revision fd48b4e3179c538caf3637be4b48f74c82f209ca (origin/main)
git config core.sparsecheckout # timeout=10
git checkout -f fd48b4e3179c538caf3637be4b48f74c82f209ca # timeout=10
Commit
message: "prepare for 4.26 (#19)"
git rev-list --no-walk fd48b4e3179c538caf3637be4b48f74c82f209ca #
timeout=10
[jbosstools-jiralint-daily] $ /bin/bash +x
/tmp/jenkins16371387587001016021.sh
fetch console log parsing rules
[jbosstools-jiralint-daily] $ /bin/bash +x /tmp/jenkins6179047840630271043.sh
Python 2.7.5
Loading constants from constants.json
after versionmatch: 2->4.26.0.AM1, 4.26.0.Final
jbide_next_master_versions->
after versionmatch: 12->3.1.x, 3.2.x, 3.3.x, 4.0.x, 4.1.x, 4.2.x, 4.3.x, 4.4.x, 4.5.x,
4.27.x, LATER, 4.26.x
jbide_bucket_versions->3.1.x, 3.2.x, 3.3.x, 4.0.x, 4.1.x, 4.2.x, 4.3.x, 4.4.x, 4.5.x,
4.27.x, LATER, 4.26.x
after versionmatch: 3->4.26.0.AM1, 4.26.0.Final, 4.26.x
jbide_maint_versions->4.26.0.AM1, 4.26.0.Final, 4.26.x
after versionmatch: 2->4.26.0.AM1, 4.26.0.Final
jbide_master_versions->4.26.0.AM1, 4.26.0.Final
after versionmatch: 85->4.3.0.Alpha1, 4.3.0.Alpha2, 4.3.0.Beta1, 4.3.0.Beta2,
4.3.0.CR1, 4.3.0.CR2, 4.3.0.Final, 4.3.1.Beta1, 4.3.1.Beta2, 4.3.1.CR1, 4.3.1.Final,
4.3.2.Final, 4.3.x, 4.4.0.Alpha1, 4.4.0.Alpha2, 4.4.0.Final, 4.4.1.AM1, 4.4.1.AM2,
4.4.1.AM3, 4.4.1.Final, 4.4.2.AM1, 4.4.2.AM2, 4.4.2.AM3, 4.4.2.Final, 4.4.3.AM1,
4.4.3.AM2, 4.4.3.Final, 4.4.4.AM1, 4.4.4.AM2, 4.4.4.AM3, 4.4.4.Final, 4.4.5.AM1, 4.4.x,
4.5.0.AM1, 4.5.0.AM2, 4.5.0.Final, 4.5.1.AM1, 4.5.1.AM2, 4.5.1.AM3, 4.5.1.Final,
4.5.2.AM1, 4.5.2.AM2, 4.5.2.AM3, 4.5.2.Final, 4.5.3.AM1, 4.5.3.AM2, 4.5.3.AM3,
4.5.3.Final, 4.5.x, 4.6.0.AM1, 4.6.0.AM2, 4.6.0.AM3, 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3,
4.11.0.AM1, 4.6.0.Final, 4.9.0.Final, 4.11.0.Final, 4.12.0.AM1, 4.12.0.Final, 4.13.0.AM1,
4.13.0.Final, 4.14.0.AM1, 4.14.0.Final, 4.15.0.AM1, 4.15.0.Final, 4.16.0.AM1,
4.16.0.Final, 4.17.0.AM1, 4.17.0.Final, 4.18.0.AM1, 4.18.0.Final, 4.19.0.AM1,
4.19.0.Final, 4.19.1.AM1, 4.19.1.Final, 4.21.0.AM1, 4.21.0.Final, 4.21.2.AM1,
4.21.3.Final, 4.23.0.AM1, 4.23.0.Final, 4.24.0.AM1, 4.24.0.Final
jbide_latest_freeze_versions->4.9.0.Final
after versionmatch: 85->4.3.0.Alpha1, 4.3.0.Alpha2, 4.3.0.Beta1, 4.3.0.Beta2,
4.3.0.CR1, 4.3.0.CR2, 4.3.0.Final, 4.3.1.Beta1, 4.3.1.Beta2, 4.3.1.CR1, 4.3.1.Final,
4.3.2.Final, 4.3.x, 4.4.0.Alpha1, 4.4.0.Alpha2, 4.4.0.Final, 4.4.1.AM1, 4.4.1.AM2,
4.4.1.AM3, 4.4.1.Final, 4.4.2.AM1, 4.4.2.AM2, 4.4.2.AM3, 4.4.2.Final, 4.4.3.AM1,
4.4.3.AM2, 4.4.3.Final, 4.4.4.AM1, 4.4.4.AM2, 4.4.4.AM3, 4.4.4.Final, 4.4.5.AM1, 4.4.x,
4.5.0.AM1, 4.5.0.AM2, 4.5.0.Final, 4.5.1.AM1, 4.5.1.AM2, 4.5.1.AM3, 4.5.1.Final,
4.5.2.AM1, 4.5.2.AM2, 4.5.2.AM3, 4.5.2.Final, 4.5.3.AM1, 4.5.3.AM2, 4.5.3.AM3,
4.5.3.Final, 4.5.x, 4.6.0.AM1, 4.6.0.AM2, 4.6.0.AM3, 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3,
4.11.0.AM1, 4.6.0.Final, 4.9.0.Final, 4.11.0.Final, 4.12.0.AM1, 4.12.0.Final, 4.13.0.AM1,
4.13.0.Final, 4.14.0.AM1, 4.14.0.Final, 4.15.0.AM1, 4.15.0.Final, 4.16.0.AM1,
4.16.0.Final, 4.17.0.AM1, 4.17.0.Final, 4.18.0.AM1, 4.18.0.Final, 4.19.0.AM1,
4.19.0.Final, 4.19.1.AM1, 4.19.1.Final, 4.21.0.AM1, 4.21.0.Final, 4.21.2.AM1,
4.21.3.Final, 4.23.0.AM1, 4.23.0.Final, 4.24.0.AM1, 4.24.0.Final
jbide_freeze_versions->4.3.0.Alpha1, 4.3.0.Alpha2, 4.3.0.Beta1, 4.3.0.Beta2, 4.3.0.CR1,
4.3.0.CR2, 4.3.0.Final, 4.3.1.Beta1, 4.3.1.Beta2, 4.3.1.CR1, 4.3.1.Final, 4.4.0.Alpha1,
4.4.0.Alpha2, 4.4.0.Final, 4.4.1.AM1, 4.4.1.AM2, 4.4.1.AM3, 4.4.1.Final, 4.4.2.AM1,
4.4.2.AM2, 4.4.2.AM3, 4.4.2.Final, 4.4.3.AM1, 4.4.3.AM2, 4.4.3.Final, 4.4.4.AM1,
4.4.4.AM2, 4.4.4.AM3, 4.4.4.Final, 4.5.0.AM1, 4.5.0.AM2, 4.5.0.Final, 4.5.1.AM1,
4.5.1.AM2, 4.5.1.AM3, 4.5.1.Final, 4.5.2.AM1, 4.5.2.AM2, 4.5.2.AM3, 4.5.2.Final,
4.5.3.AM1, 4.5.3.AM2, 4.5.3.AM3, 4.5.3.Final, 4.6.0.AM1, 4.6.0.AM2, 4.6.0.AM3, 4.9.0.AM1,
4.9.0.AM2, 4.9.0.AM3, 4.6.0.Final, 4.9.0.Final
after versionmatch: 2->4.26.0.AM1, 4.26.0.Final
jbide_next_maint_versions->
Processing filters found in filters.json
filter ds_needpmack
updating filter ds_needpmack->'Target Release' is not EMPTY AND 'CDW
pm_ack' = '?' AND resolution = Unresolved
filter ds_next_maint
updating filter ds_next_maint->project = JBIDE AND fixVersion in ( )
('Http Error:', HTTPError('400 Client Error: Bad Request',))
Traceback (most recent call last):
File "setup_filters.py", line 183, in <module>
fields['id'] = shared.jiraupdate(options, "/rest/api/latest/filter/"
+ fields['id'], data)['id']
File
"<https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.com/job/Studio/job/Engineering/job/releng/job/jbosstools-jiralint-daily/ws/common/shared.py",>
line 77, in jiraupdate
raise(e)
requests.exceptions.HTTPError: 400 Client Error: Bad Request
Using reports defined in reports-daily.json
Check for 'illegal fix version'
0 issues found with 'illegal fix version'
Write to illegalfixversion-test.xml
Check for 'no component'
0 issues found with 'no component'
Write to nocomponent-test.xml
Build step 'Console output (build log) parsing' changed build result to FAILURE
Recording test results
[Checks API] No suitable checks publisher found.