[jbosstools-builds] Build failed in Jenkins: Studio » Engineering » CodeReady Studio Release Engineering » jbosstools-jiralint-weekly #54
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-4 (rhel rhel7) in workspace
<https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.comjob/S...
The recommended git tool is: NONE
using credential devstudio-release
Cloning the remote Git repository
Cloning repository git@github.com:jbosstools/jiralint
git init
<https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.comjob/S...
# timeout=10
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 and jbdevstudio
repos
[INFO] Currently running in a labeled security context
[INFO] Currently SELinux is 'enforcing' on the host
/usr/bin/chcon --type=ssh_home_t
<https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.comjob/S...
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
Seen branch in repository origin/main
Seen 1 remote branch
git show-ref --tags -d # timeout=10
Checking out Revision
5d9a228584a47b99b8a0d928b27379cfa7450dc5 (origin/main)
git config core.sparsecheckout # timeout=10
git checkout -f 5d9a228584a47b99b8a0d928b27379cfa7450dc5 # timeout=10
Commit
message: "update versions after 4.21.3.Final/12.21.3.GA (#15)"
git rev-list --no-walk 5d9a228584a47b99b8a0d928b27379cfa7450dc5 #
timeout=10
[jbosstools-jiralint-weekly] $ /bin/bash +x
/tmp/jenkins1533131398979412.sh
fetch console log parsing rules
[jbosstools-jiralint-weekly] $ /bin/bash +x /tmp/jenkins953380251676192077.sh
Python 2.7.5
Using reports defined in reports-weekly.json
Check for 'illegal fix version for resolved issue'
4 issues found with 'illegal fix version for resolved issue'
Write to illegalfixversionforresolvedissue-test.xml
Send email with 2 issue(s) to: ldimaggi(a)redhat.com
* https://issues.redhat.com/browse/JBDS-2017
* https://issues.redhat.com/browse/JBDS-3469
Send email with 1 issue(s) to: sbouchet(a)redhat.com
* https://issues.redhat.com/browse/JBDS-5041
Send email with 1 issue(s) to: olkornii(a)redhat.com
* https://issues.redhat.com/browse/JBDS-5046
Check for 'no fix version'
44 issues found with 'no fix version'
Traceback (most recent call last):
File "render-testcase.py", line 291, in <module>
email_addresses = render(issue_type,
fields['description'].encode('utf8','replace'), data,
data['issues'], fields['jql'], options, email_addresses, components)
File "render-testcase.py", line 100, in render
'.\n\n[ERROR] Contact an administrator to update
https://issues.redhat.com/plugins/servlet/project-config/JBIDE/components...)
Exception: [ERROR] No component lead set for component = base on issue JBIDE-28330.
[ERROR] Contact an administrator to update
https://issues.redhat.com/plugins/servlet/project-config/JBIDE/components
Build step 'Execute shell' marked build as failure
Recording test results
[Checks API] No suitable checks publisher found.