Unittest xml file not valid

2022-12-06 Thread Fabian Cenedese 
Hello

I'm using pytest for testing and have it generate a unittest
xml file that can be read by Jenkins. This has worked fine
for other jobs but now I have a new job where Jenkins doesn't
like the file:

01:12:52  org.jenkinsci.plugins.xunit.service.TransformerException: The result 
file 'C:\Jenkins\workspace\applicationtest\applicationtest\unittest.xml' for 
the metric 'CppUnit' is not valid. The result file has been skipped.

However the file exists and XmlLint doesn't see a problem with it.
No un-escaped special chars or < > etc. There's a 
tag and it just looks like other files from other jobs that work.



Is there a way to see what exactly it is that Jenkins doesn't like
about this file?

Thanks

bye  Fabi

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/770c9b9f82cede0ddb2e83a818ba0f09%40indel.ch.

Re: Running Jenkins as a Service in RHEL 8

2022-12-06 Thread eric....@gmail.com 
Requesting this conversation to be deleted because I accidentally let a 
machine name in without scrubbing it.  Thanks!

On Monday, December 5, 2022 at 8:54:21 AM UTC-7 eric@gmail.com wrote:

> Not sure changing the home directory is the answer.  I think the true 
> answer resides in how to allow the jenkins service to run in SELINUX...
>
> On Monday, December 5, 2022 at 8:45:42 AM UTC-7 slide wrote:
>
>> Jenkins switched to systemd "recently" check this page for how to change 
>> env variables and such 
>> https://www.jenkins.io/doc/book/system-administration/systemd-services/ 
>>
>> On Mon, Dec 5, 2022 at 8:40 AM eric@gmail.com  
>> wrote:
>>
>>> Changing the JENKINS_HOME directory in that config file didn't work.  I 
>>> got the same error some it's using that link somewhere else...
>>>
>>> Thanks,
>>> Eric
>>>
>>> On Monday, December 5, 2022 at 8:09:31 AM UTC-7 eric@gmail.com 
>>> wrote:
>>>
 Hi All,

 I'm running into an issue running Jenkins as a service in RHEL 8 with 
 SELINUX running (I don't have a choice).  It seems since /var/lib/jenkins 
 is a symbolic link to /opt/jenkins, SELINUX doesn't want to allow running 
 the service from there.  Would it be acceptable to just change the value 
 for JENKINS_HOME to /opt/jenkins in /etc/sysconfig/jenkins?  Thanks!


 ]# journalctl -xe

You can generate a 
 local policy module to allow this access.

Do

allow this access 
 for now by executing:

# ausearch -c 
 '(jenkins)' --raw | audit2allow -M my-jenkins

# semodule -X 300 -i 
 my-jenkins.pp



 Dec 02 10:45:03 nd655bd001 setroubleshoot[144816]: AnalyzeThread.run(): 
 Set alarm timeout to 10

 Dec 02 10:45:03 nd655bd001 setroubleshoot[144816]: AnalyzeThread.run(): 
 Cancel pending alarm

 Dec 02 10:45:07 nd655bd001 setroubleshoot[144816]: SELinux is 
 preventing /usr/lib/systemd/systemd from read access on the lnk_file 
 /var/lib/jenkins. For com>

 Dec 02 10:45:07 nd655bd001 setroubleshoot[144816]: SELinux is 
 preventing /usr/lib/systemd/systemd from read access on the lnk_file 
 /var/lib/jenkins.



*  Plugin 
 catchall_labels (83.8 confidence) suggests   ***



If you want to allow 
 systemd to have read access on the jenkins lnk_file

Then you need to 
 change the label on /var/lib/jenkins

Do

# semanage fcontext 
 -a -t FILE_TYPE '/var/lib/jenkins'

where FILE_TYPE is 
 one of the following: NetworkManager_etc_rw_t, NetworkManager_etc_t, 
 NetworkManager_un>

Then execute:

restorecon -v 
 '/var/lib/jenkins'





*  Plugin 
 catchall (17.1 confidence) suggests   **



If you believe that 
 systemd should be allowed read access on the jenkins lnk_file by default.

Then you should 
 report this as a bug.

You can generate a 
 local policy module to allow this access.

Do

allow this access 
 for now by executing:

# ausearch -c 
 '(jenkins)' --raw | audit2allow -M my-jenkins

# semodule -X 300 -i 
 my-jenkins.pp



 Dec 02 10:45:07 nd655bd001 setroubleshoot[144816]: AnalyzeThread.run(): 
 Set alarm timeout to 10

 Dec 02 10:45:18 nd655bd001 systemd[1]: setroubleshootd.service: 
 Succeeded.

 --

Re: *** buffer overflow detected ***: java terminated

2022-12-06 Thread M.Madhusudana Reddy 
I think I spoke too early.

Even with the newer version of Tomcat, I am seeing the issue.

Thanks
M.Madhu


On Tue, Dec 6, 2022 at 12:29 AM 'Dirk Heinrichs' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Am Montag, dem 05.12.2022 um 11:28 -0600 schrieb M.Madhusudana Reddy:
>
> My java version was jdk-11.0.16+8 and I updated this to the latest one in
> JAVA 11 this morning which is jdk-11.0.17+8 and I still see the same error.
>
> Tomcat is of version 9.0.0.0
>
>
> Ah, I see. We have different conditions, then. We're not running Jenkins
> in Tomcat here. And I checked again what our problem was with Java 11.0.16.
> It was a memory leak which led to Jenkins (or better: its JVM) being
> OOM-killed by the Linux kernel. THAT was fixed with 11.0.17.
>
> Bye...
>
> Dirk
>
> --
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhein...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/dba5491ad09b0ca4eb8ba76c80ecf6dcb663316d.camel%40opentext.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAN%2BS7NrLc3naAWOpc2VpyvStXfNLdP5GKrW1dq22zRq36DBS-Q%40mail.gmail.com.