Re: Programmatically searching the artifacts from multiple jobs

Thanks Martin. That looks like the most programmatic solution of all. On Mon, Aug 19, 2019 at 3:58 PM Martin d'Anjou wrote: > You can get the artifacts from Jenkins using curl: > curl -X GET "http://localhost:8080/job/p1/2/artifact/t2.txt"; -o t2.txt > > You can also get all the artifacts: > cur

Re: Programmatically searching the artifacts from multiple jobs

You can get the artifacts from Jenkins using curl: curl -X GET "http://localhost:8080/job/p1/2/artifact/t2.txt"; -o t2.txt You can also get all the artifacts: curl -X GET "http://localhost:8080/job/p1/2/artifact/*zip*/archive.zip"; -o a.zip For more see: https://stackoverflow.com/questions/35920

Re: Programmatically searching the artifacts from multiple jobs

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,

Re: Programmatically searching the artifacts from multiple jobs

Could the run selector plugin help? https://github.com/jenkinsci/run-selector-plugin Martin -- 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+uns

Re: Programmatically searching the artifacts from multiple jobs

If I can get the admin to install this, I'll give it a try thanks On Monday, August 12, 2019 at 2:30:32 PM UTC-7, Ullrich Hafner wrote: > > 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

Re: Programmatically searching the artifacts from multiple jobs

>>If you had access to the Jenkins server you could copy t I do have access to the server I'd write a script to go parse the artifact logs, if I only knew where they were. I don't know if that requires root access or not, I dont have root access. On Monday, August 12, 2019 at 9:23:56 PM UTC-7, M

Re: Programmatically searching the artifacts from multiple jobs

If you had access to the Jenkins server you could copy the files locally via scp or similar and run your script. You could also configure your job to save them somewhere in the file system with a date stamp in the name to allow you to search historically results. You could also set up a downstream

Re: Programmatically searching the artifacts from multiple jobs

Thanks, I may have to resort to that. I was hoping to find a way to get access to the artifact files, outside of Jenkins though. Then I could write my own script to run independently of Jenkins On Mon, Aug 12, 2019 at 2:30 PM Ullrich Hafner wrote: > > Or you can use the https://wiki.jenkins.io/d

Re: Programmatically searching the artifacts from multiple jobs

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 Us

Re: Programmatically searching the artifacts from multiple jobs

Thanks On Sunday, August 11, 2019 at 9:49:38 PM UTC-7, Björn Pedersen wrote: > > 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 Fai

Re: Programmatically searching the artifacts from multiple jobs

Thanks On Sunday, August 11, 2019 at 8:47:27 PM UTC-7, ok999 wrote: > > 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 > > wrote: > >> Hi, >> >> I've been using Jenkins at work, for j

Re: Programmatically searching the artifacts from multiple jobs

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.

Re: Programmatically searching the artifacts from multiple jobs

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 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 us