For treeherder integration, we need a means to publish logs to S3. We already have S3 plugins installed on Jenkins via our puppet scripts. It appears that this should be easily accomplished w/ that plugin, as long as permissions are correct on Amazon, and a remote bucket profile is properly configured in Manage Jenkins. We'll be using something like: services-qa-jenkins-artifacts/test-logs/<job-name> The purpose of this bug is to outline steps needed to do this.
HOW TO PUBLISH LOGS TO S3 . Jenkins > Configuration > Amazon S3 Profiles . Add a profile name (can be anything you want) . click on checkbox: "Use IAM Role" NOTE: If ticked uses the instance IAM role to access S3 - so make sure to add S3 access to that role . Save . Create a new job . Add a build step that creates some artifact (i.e. dummy.log) . Add a post-build step: "Publish Artifacts to S3 bucket" . Save and run job . logs will be output to bucket in this format: <bucket-name>/jobs/<job-name>/<run-number>/<log-name> https://s3-us-west-1.amazonaws.com/services-qa-jenkins-artifacts/jobs/demo-s3/2/dummy.txt NOTE: These are the steps needed to publish to S3, but won't be needed by folks writing tests. These will eventually be baked into jobs by the Jenkins job generator, but can be added manually for now, if needed. Just documenting here for reference.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.