[FOLIO-3445] check why Okapi logs are not logged in the Jenkins Console Output Created: 14/Mar/22  Updated: 09/Jun/22  Resolved: 09/Jun/22

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

Type: Story Priority: P3
Reporter: Jakub Skoczen Assignee: John Malconian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps Sprint 135, DevOps Sprint 136, DevOps Sprint 137, DevOps Sprint 138, DevOps Sprint 139, DevOps Sprint 140, DevOps Sprint 141
Development Team: FOLIO DevOps
RCA Group: TBD

 Comments   
Comment by Jakub Skoczen [ 21/Mar/22 ]

Wayne Schneider confirm that Okapi errors are reported by Ansible

John Malconian will set the Jenkins job so that Okapi logs are retained.

Comment by Wayne Schneider [ 04/Apr/22 ]

I believe this is the relevant issue for the Jenkins Ansible plugin. It is addressed in this languishing PR.

There are a few possible workarounds; the simplest is to make sure that a little wait time is built into the Jenkinsfile post-processing to ensure that the final message from the build is logged, as we did in the reference build Jenkinsfile:

  post {
    always {
      sendNotifications currentBuild.result
    }
    cleanup {
      echo "Sleeping during cleanup to enable ansible error reporting."
      sleep 10
    }
  } // end post
Comment by Wayne Schneider [ 04/Apr/22 ]

PR is ready and awaiting review (John Malconian).

Comment by Wayne Schneider [ 07/Apr/22 ]

OTY, John Malconian, to attach Okapi container log to Jenkins job.

Comment by John Malconian [ 09/Jun/22 ]

Added a step to the build-platform-complete-snapshot job (https://jenkins-aws.indexdata.com/job/Automation/job/build-platform-complete-snapshot) that publishes the okapi log whenever the job fails.

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