[FOLIO-2979] Make FOLIO reference build logs available to devs Created: 25/Jan/21  Updated: 20/Mar/21  Resolved: 19/Mar/21

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: devops-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps Sprint 109, DevOps Sprint 110
Development Team: FOLIO DevOps

 Description   

We get a lot of dev requests to retrieve FOLIO log files from reference builds. Perhaps we should just make these logs available in an S3 bucket so that they can be easily retrieved.

Will consult with David Crossley on where to document how to access logs.

Update: see https://dev.folio.org/faqs/how-to-obtain-refenv-logs/



 Comments   
Comment by John Malconian [ 19/Mar/21 ]

There is a Jenkins job that will collect logs from specified reference environment and modules - https://jenkins-aws.indexdata.com/job/Automation/job/collect-reference-env-logs/

All members of folio-org are configured to run this job. The job creates a tar file containing the specified logs and uploads them to an S3 bucket. A URL to fetch the logs is returned
via a Slack notification.

I've even added a custom Slackbot response that will reply with a message containing a link to the jenkins job based on certain phrases. Unfortunately, the response will only be triggered by some very specific messages. I'm not able to cast a wider net because there is no way to narrow the scope of custom Slackbot responses to a specific set of channels.

Generated at Thu Feb 08 23:24:41 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.