11:13 p.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #266
11:15 p.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #267
11:13 p.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #268
11:12 p.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #269
11:13 p.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #270
11:15 p.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #271
11:17 p.m.
New subject: Build failed in Jenkins: jbosstools-jiralint-weekly #272
See
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on rhel7-x64-51750 (nvm x64 rhel upshift mem8G nodejs rhel7 docker) in
workspace
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
Cloning the remote Git repository
Cloning repository git://github.com/jbosstools/jiralint.git
git init
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
# timeout=10
Fetching upstream changes from
git://github.com/jbosstools/jiralint.git
Fetching upstream changes from git://github.com/jbosstools/jiralint.git
Checking out
Revision 9686f435cc3caf6f531c65504c87ec30253a64fd (refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 9686f435cc3caf6f531c65504c87ec30253a64fd
Commit message: "Add
scripts to deal with filter permissions (#9)"
[jbosstools-jiralint-weekly] $ /bin/sh -xe /tmp/jenkins7979704971304383661.sh
+ export JIRA_USER=jiralint
+ JIRA_USER=jiralint
+ export JIRA_PWD=mart-milt-sedative
+ JIRA_PWD=mart-milt-sedative
+ python -V
Python 2.7.5
+ python render-testcase.py -u jiralint -p mart-milt-sedative -s https://issues.redhat.com
-r reports-weekly.json -f jmaury(a)redhat.com -n jbosstools-dev(a)lists.jboss.org -m
smtp.corp.redhat.com
Using reports defined in reports-weekly.json
Check for 'illegal fix version for resolved issue'
75 issues found with 'illegal fix version for resolved issue'
Write to illegalfixversionforresolvedissue-test.xml
Send email with 4 issue(s) to: dxu(a)redhat.com
* https://issues.redhat.com/browse/JBIDE-4807
* https://issues.redhat.com/browse/JBIDE-2889
* https://issues.redhat.com/browse/JBIDE-5495
* https://issues.redhat.com/browse/JBIDE-2738
Traceback (most recent call last):
File "render-testcase.py", line 290, 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 235, in render
options)
File "render-testcase.py", line 61, in mailsend
server.sendmail(from_email, recipients_list, msg)
File "/usr/lib64/python2.7/smtplib.py", line 746, in sendmail
raise SMTPRecipientsRefused(senderrs)
smtplib.SMTPRecipientsRefused: {'dennyxu <dxu(a)redhat.com>': (550, '5.1.1
<dxu(a)redhat.com>: Recipient address rejected: User unknown in local recipient
table')}
Build step 'Execute shell' marked build as failure
Recording test results
11:17 p.m.
New subject: Build failed in Jenkins: jbosstools-jiralint-weekly #273
See
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on rhel7-x64-53026 (nvm x64 rhel upshift mem8G nodejs rhel7 docker) in
workspace
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
Cloning the remote Git repository
Cloning repository git://github.com/jbosstools/jiralint.git
git init
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
# timeout=10
Fetching upstream changes from
git://github.com/jbosstools/jiralint.git
Fetching upstream changes from git://github.com/jbosstools/jiralint.git
Checking out
Revision 9686f435cc3caf6f531c65504c87ec30253a64fd (refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 9686f435cc3caf6f531c65504c87ec30253a64fd
Commit message: "Add
scripts to deal with filter permissions (#9)"
[jbosstools-jiralint-weekly] $ /bin/sh -xe /tmp/jenkins1587224968380642163.sh
+ export JIRA_USER=jiralint
+ JIRA_USER=jiralint
+ export JIRA_PWD=mart-milt-sedative
+ JIRA_PWD=mart-milt-sedative
+ python -V
Python 2.7.5
+ python render-testcase.py -u jiralint -p mart-milt-sedative -s https://issues.redhat.com
-r reports-weekly.json -f jmaury(a)redhat.com -n jbosstools-dev(a)lists.jboss.org -m
smtp.corp.redhat.com
Using reports defined in reports-weekly.json
Check for 'illegal fix version for resolved issue'
192 issues found with 'illegal fix version for resolved issue'
Write to illegalfixversionforresolvedissue-test.xml
Send email with 29 issue(s) to: rob.stryker(a)jboss.com
* https://issues.redhat.com/browse/JBIDE-1447
* https://issues.redhat.com/browse/JBIDE-2268
* https://issues.redhat.com/browse/JBIDE-2908
* https://issues.redhat.com/browse/JBIDE-478
* https://issues.redhat.com/browse/JBIDE-494
* https://issues.redhat.com/browse/JBIDE-636
* https://issues.redhat.com/browse/JBIDE-2799
* https://issues.redhat.com/browse/JBIDE-490
* https://issues.redhat.com/browse/JBIDE-633
* https://issues.redhat.com/browse/JBIDE-5167
* https://issues.redhat.com/browse/JBIDE-4673
* https://issues.redhat.com/browse/JBIDE-477
* https://issues.redhat.com/browse/JBIDE-6332
* https://issues.redhat.com/browse/JBIDE-3156
* https://issues.redhat.com/browse/JBIDE-767
* https://issues.redhat.com/browse/JBIDE-568
* https://issues.redhat.com/browse/JBIDE-1735
* https://issues.redhat.com/browse/JBIDE-1934
* https://issues.redhat.com/browse/JBIDE-5242
* https://issues.redhat.com/browse/JBIDE-486
* https://issues.redhat.com/browse/JBIDE-829
* https://issues.redhat.com/browse/JBIDE-5576
* https://issues.redhat.com/browse/JBIDE-485
* https://issues.redhat.com/browse/JBIDE-482
* https://issues.redhat.com/browse/JBIDE-480
* https://issues.redhat.com/browse/JBIDE-481
* https://issues.redhat.com/browse/JBIDE-648
* https://issues.redhat.com/browse/JBIDE-1071
* https://issues.redhat.com/browse/JBIDE-2224
Send email with 20 issue(s) to: snjezana.peco(a)redhat.com
* https://issues.redhat.com/browse/JBIDE-2803
* https://issues.redhat.com/browse/JBIDE-2811
* https://issues.redhat.com/browse/JBIDE-2128
* https://issues.redhat.com/browse/JBIDE-2804
* https://issues.redhat.com/browse/JBIDE-2609
* https://issues.redhat.com/browse/JBDS-3972
* https://issues.redhat.com/browse/JBIDE-4972
* https://issues.redhat.com/browse/JBIDE-3031
* https://issues.redhat.com/browse/JBIDE-2292
* https://issues.redhat.com/browse/JBIDE-2907
* https://issues.redhat.com/browse/JBIDE-2997
* https://issues.redhat.com/browse/JBDS-1410
* https://issues.redhat.com/browse/JBIDE-2588
* https://issues.redhat.com/browse/JBIDE-2620
* https://issues.redhat.com/browse/JBIDE-1481
* https://issues.redhat.com/browse/JBIDE-2225
* https://issues.redhat.com/browse/JBIDE-2293
* https://issues.redhat.com/browse/JBIDE-2271
* https://issues.redhat.com/browse/JBIDE-2853
* https://issues.redhat.com/browse/JBIDE-2084
Send email with 2 issue(s) to: alkazako+osio(a)redhat.com
* https://issues.redhat.com/browse/JBIDE-5181
* https://issues.redhat.com/browse/JBIDE-794
Send email with 1 issue(s) to: ldimaggi(a)redhat.com
* https://issues.redhat.com/browse/JBDS-3122
Send email with 2 issue(s) to: dpeng(a)redhat.com
* https://issues.redhat.com/browse/JBIDE-4171
* https://issues.redhat.com/browse/JBIDE-2365
Send email with 3 issue(s) to: achabatar(a)exadel.com
* https://issues.redhat.com/browse/JBIDE-1415
* https://issues.redhat.com/browse/JBIDE-1411
* https://issues.redhat.com/browse/JBIDE-874
Send email with 6 issue(s) to: vrubezhny(a)redhat.com
* https://issues.redhat.com/browse/JBDS-98
* https://issues.redhat.com/browse/JBDS-18
* https://issues.redhat.com/browse/JBDS-81
* https://issues.redhat.com/browse/JBIDE-1771
* https://issues.redhat.com/browse/JBIDE-635
* https://issues.redhat.com/browse/JBIDE-1061
Send email with 1 issue(s) to: mareshkau(a)exadel.com
* https://issues.redhat.com/browse/JBIDE-4554
Send email with 1 issue(s) to: anis(a)exadel.com
* https://issues.redhat.com/browse/JBIDE-1972
Send email with 1 issue(s) to: fbricon(a)redhat.com
* https://issues.redhat.com/browse/JBDS-2422
Send email with 4 issue(s) to: ascherbovich(a)exadel.com
* https://issues.redhat.com/browse/JBIDE-1398
* https://issues.redhat.com/browse/JBIDE-2029
* https://issues.redhat.com/browse/JBIDE-2085
* https://issues.redhat.com/browse/JBIDE-2033
Send email with 1 issue(s) to: ochikvina(a)exadel.com
* https://issues.redhat.com/browse/JBIDE-5708
Send email with 3 issue(s) to: dgeraskov(a)exadel.com
* https://issues.redhat.com/browse/JBIDE-1416
* https://issues.redhat.com/browse/JBIDE-1665
* https://issues.redhat.com/browse/JBIDE-1412
Send email with 2 issue(s) to: dmaliarevich(a)exadel.com
* https://issues.redhat.com/browse/JBIDE-6479
* https://issues.redhat.com/browse/JBIDE-6645
Send email with 24 issue(s) to: oggle(a)yandex.ru
* https://issues.redhat.com/browse/JBIDE-4802
* https://issues.redhat.com/browse/JBIDE-804
* https://issues.redhat.com/browse/JBIDE-948
* https://issues.redhat.com/browse/JBIDE-785
* https://issues.redhat.com/browse/JBIDE-579
* https://issues.redhat.com/browse/JBIDE-532
* https://issues.redhat.com/browse/JBIDE-2802
* https://issues.redhat.com/browse/JBIDE-593
* https://issues.redhat.com/browse/JBIDE-595
* https://issues.redhat.com/browse/JBIDE-671
* https://issues.redhat.com/browse/JBIDE-644
* https://issues.redhat.com/browse/JBIDE-677
* https://issues.redhat.com/browse/JBIDE-861
* https://issues.redhat.com/browse/JBIDE-898
* https://issues.redhat.com/browse/JBIDE-686
* https://issues.redhat.com/browse/JBIDE-547
* https://issues.redhat.com/browse/JBIDE-545
* https://issues.redhat.com/browse/JBIDE-565
* https://issues.redhat.com/browse/JBIDE-890
* https://issues.redhat.com/browse/JBIDE-12933
* https://issues.redhat.com/browse/JBIDE-668
* https://issues.redhat.com/browse/JBIDE-622
* https://issues.redhat.com/browse/JBIDE-2408
* https://issues.redhat.com/browse/JBIDE-584
Send email with 2 issue(s) to: smukhina(a)exadel.com
* https://issues.redhat.com/browse/JBDS-57
* https://issues.redhat.com/browse/JBDS-1080
Send email with 1 issue(s) to: vyemialyanchyk(a)gmail.com
* https://issues.redhat.com/browse/JBIDE-6070
Send email with 1 issue(s) to: kaers(a)redhat.com
* https://issues.redhat.com/browse/JBIDE-2823
Send email with 4 issue(s) to: dxu(a)redhat.com
* https://issues.redhat.com/browse/JBIDE-4807
* https://issues.redhat.com/browse/JBIDE-2889
* https://issues.redhat.com/browse/JBIDE-5495
* https://issues.redhat.com/browse/JBIDE-2738
Traceback (most recent call last):
File "render-testcase.py", line 290, 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 235, in render
options)
File "render-testcase.py", line 61, in mailsend
server.sendmail(from_email, recipients_list, msg)
File "/usr/lib64/python2.7/smtplib.py", line 746, in sendmail
raise SMTPRecipientsRefused(senderrs)
smtplib.SMTPRecipientsRefused: {'dennyxu <dxu(a)redhat.com>': (550, '5.1.1
<dxu(a)redhat.com>: Recipient address rejected: User unknown in local recipient
table')}
Build step 'Execute shell' marked build as failure
Recording test results
11:14 p.m.
New subject: Jenkins build is unstable: jbosstools-jiralint-weekly #274
11:14 p.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #275
11:15 p.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #276
11:17 p.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #277
11:14 p.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #278
11:14 p.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #279
12:14 a.m.
New subject: Jenkins build is still unstable: jbosstools-jiralint-weekly #280
12:14 a.m.
New subject: Build failed in Jenkins: jbosstools-jiralint-weekly #281
See
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on rhel7-x64-1146 (nvm x64 rhel upshift mem8G nodejs rhel7 docker) in
workspace
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
Cloning the remote Git repository
Cloning repository git://github.com/jbosstools/jiralint.git
git init
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
# timeout=10
Fetching upstream changes from
git://github.com/jbosstools/jiralint.git
Fetching upstream changes from git://github.com/jbosstools/jiralint.git
Checking out
Revision 9686f435cc3caf6f531c65504c87ec30253a64fd (refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 9686f435cc3caf6f531c65504c87ec30253a64fd
Commit message: "Add
scripts to deal with filter permissions (#9)"
[jbosstools-jiralint-weekly] $ /bin/sh -xe /tmp/jenkins2691789313516889345.sh
+ export JIRA_USER=jiralint
+ JIRA_USER=jiralint
+ export JIRA_PWD=mart-milt-sedative
+ JIRA_PWD=mart-milt-sedative
+ python -V
Python 2.7.5
+ python render-testcase.py -u jiralint -p mart-milt-sedative -s https://issues.redhat.com
-r reports-weekly.json -f jmaury(a)redhat.com -n jbosstools-dev(a)lists.jboss.org -m
smtp.corp.redhat.com
Using reports defined in reports-weekly.json
Check for 'illegal fix version for resolved issue'
0 issues found with 'illegal fix version for resolved issue'
Write to illegalfixversionforresolvedissue-test.xml
Check for 'no fix version'
12 issues found with 'no fix version'
Traceback (most recent call last):
File "render-testcase.py", line 290, 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 = installer on issue JBDS-4923.
[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
12:13 a.m.
New subject: Build failed in Jenkins: jbosstools-jiralint-weekly #282
See
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on rhel7-x64-1365 (nvm x64 rhel upshift mem8G nodejs rhel7 docker) in
workspace
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
Cloning the remote Git repository
Cloning repository git://github.com/jbosstools/jiralint.git
git init
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
# timeout=10
Fetching upstream changes from
git://github.com/jbosstools/jiralint.git
Fetching upstream changes from git://github.com/jbosstools/jiralint.git
Checking out
Revision 9686f435cc3caf6f531c65504c87ec30253a64fd (refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 9686f435cc3caf6f531c65504c87ec30253a64fd
Commit message: "Add
scripts to deal with filter permissions (#9)"
[jbosstools-jiralint-weekly] $ /bin/sh -xe /tmp/jenkins2047753072483423989.sh
+ export JIRA_USER=jiralint
+ JIRA_USER=jiralint
+ export JIRA_PWD=mart-milt-sedative
+ JIRA_PWD=mart-milt-sedative
+ python -V
Python 2.7.5
+ python render-testcase.py -u jiralint -p mart-milt-sedative -s https://issues.redhat.com
-r reports-weekly.json -f jmaury(a)redhat.com -n jbosstools-dev(a)lists.jboss.org -m
smtp.corp.redhat.com
Using reports defined in reports-weekly.json
Check for 'illegal fix version for resolved issue'
0 issues found with 'illegal fix version for resolved issue'
Write to illegalfixversionforresolvedissue-test.xml
Check for 'no fix version'
14 issues found with 'no fix version'
Traceback (most recent call last):
File "render-testcase.py", line 290, 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 = cdk on issue JBIDE-27727.
[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
1:54 a.m.
New subject: Build failed in Jenkins: jbosstools-jiralint-weekly #283
See
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on rhel7-x64-3429 (nvm x64 rhel upshift mem8G nodejs rhel7 docker) in
workspace
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
Cloning the remote Git repository
Cloning repository git://github.com/jbosstools/jiralint.git
git init
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
# timeout=10
Fetching upstream changes from
git://github.com/jbosstools/jiralint.git
Fetching upstream changes from git://github.com/jbosstools/jiralint.git
Checking out
Revision 9686f435cc3caf6f531c65504c87ec30253a64fd (refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 9686f435cc3caf6f531c65504c87ec30253a64fd
Commit message: "Add
scripts to deal with filter permissions (#9)"
[jbosstools-jiralint-weekly] $ /bin/sh -xe /tmp/jenkins98552632140456437.sh
+ export JIRA_USER=jiralint
+ JIRA_USER=jiralint
+ export JIRA_PWD=mart-milt-sedative
+ JIRA_PWD=mart-milt-sedative
+ python -V
Python 2.7.5
+ python render-testcase.py -u jiralint -p mart-milt-sedative -s https://issues.redhat.com
-r reports-weekly.json -f jmaury(a)redhat.com -n jbosstools-dev(a)lists.jboss.org -m
smtp.corp.redhat.com
Using reports defined in reports-weekly.json
Check for 'illegal fix version for resolved issue'
1 issues found with 'illegal fix version for resolved issue'
Traceback (most recent call last):
File "render-testcase.py", line 290, 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 = cdk on issue JBIDE-27727.
[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
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found.
Configuration error?
3:15 a.m.
New subject: Build failed in Jenkins: jbosstools-jiralint-weekly #284
See
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on rhel7-x64-3711 (nvm x64 rhel upshift mem8G nodejs rhel7 docker) in
workspace
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
Cloning the remote Git repository
Cloning repository git://github.com/jbosstools/jiralint.git
git init
<https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
# timeout=10
Fetching upstream changes from
git://github.com/jbosstools/jiralint.git
Fetching upstream changes from git://github.com/jbosstools/jiralint.git
Checking out
Revision 9686f435cc3caf6f531c65504c87ec30253a64fd (refs/remotes/origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f 9686f435cc3caf6f531c65504c87ec30253a64fd
Commit message: "Add
scripts to deal with filter permissions (#9)"
[jbosstools-jiralint-weekly] $ /bin/sh -xe /tmp/jenkins4634600091899250875.sh
+ export JIRA_USER=jiralint
+ JIRA_USER=jiralint
+ export JIRA_PWD=mart-milt-sedative
+ JIRA_PWD=mart-milt-sedative
+ python -V
Python 2.7.5
+ python render-testcase.py -u jiralint -p mart-milt-sedative -s https://issues.redhat.com
-r reports-weekly.json -f jmaury(a)redhat.com -n jbosstools-dev(a)lists.jboss.org -m
smtp.corp.redhat.com
Using reports defined in reports-weekly.json
Check for 'illegal fix version for resolved issue'
0 issues found with 'illegal fix version for resolved issue'
Write to illegalfixversionforresolvedissue-test.xml
Check for 'no fix version'
20 issues found with 'no fix version'
Traceback (most recent call last):
File "render-testcase.py", line 290, 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 = foundation on issue JBIDE-27777.
[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
12:17 a.m.
New subject: Jenkins build is unstable: jbosstools-jiralint-weekly #285
1432
days inactive
1572
days old
jbosstools-builds@lists.jboss.org
20 comments
1 participants
participants (1)
-
dev-platform-jenkins＠redhat.com