--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/97a539f0-1e12-4796-9692-23c662cbb340%40googlegroups.com.
Short answer, you need something like splunk or elastic search to parse the logs and check for specific strings.
On Sun, Aug 11, 2019 at 5:55 PM Tony C <capp...@gmail.com> wrote:
Hi,--I've been using Jenkins at work, for just over a year. I"m not the main architect of our groovy infrastructure. I'm just a userwho has several jobs which run each night.Each of those jobs saves a handful of artifacts (log files) from that job.I usually go into each job and look at a specific file (common to each job), for specific text that would indicate the job had a problem.Since there are so many jobs being run, this takes quite a bit of time. Every day.I would like to be able to search all of the jobs which ran on a certain date and scan the artifacts for specific text.I would probably do this outside of Jenkins, by writing a script to scan the artifact files.However, I don't know how to gain access to those jobs programmatically, let alone scanning the artifacts of each of those jobs.I've used the Python-Jenkins librarybut it doesn't have the ability to do what I want- scanning the artifacts of several builds (or a specific build).Thanks
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 jenkins...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/97a539f0-1e12-4796-9692-23c662cbb340%40googlegroups.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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ccdab323-3894-4635-a06f-5f7a74c3b3ec%40googlegroups.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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/97a539f0-1e12-4796-9692-23c662cbb340%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins...@googlegroups.com.
Or you can use the https://wiki.jenkins.io/display/JENKINS/Text-finder+Plugin
It provides already a way to grep files for a pattern and set the build status accordingly.
Am 12.08.2019 um 06:49 schrieb 'Björn Pedersen' via Jenkins Users <jenkins...@googlegroups.com>:
Hi,I think the best solution would be to use warnings-ng and set up suitable custom parser (I assume that none of the many available parsers fit your use-case). Possibly in combination with the Build Failure Analyzer plugin your jobs will show the correct status and where the errors happed.Björn--
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 jenkins...@googlegroups.com.
Perhaps. I'll have to give it a try to see what its limitations are.
When you have 5-10 artifacts per job, it takes a lot of time saving
them, so they can be attached to a Jira ticket.
Jenkins doesn't provide a way to save those files. You need to view
each one, copy it's contents into an editor, then save those files,
manually.
thanks
On Sun, Aug 18, 2019 at 10:49 AM Martin d'Anjou
<martin....@gmail.com> wrote:
>
> Could the run selector plugin help?
> https://github.com/jenkinsci/run-selector-plugin
>
> Martin
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/nNwRWXHOs5E/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to jenkins...@googlegroups.com.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/030c4641-e194-4562-aae0-ba7b2c6bc430%40googlegroups.com.