[SERVER-34043] Publish embedded build artifacts to a 'latest' bucket Created: 15/Mar/18  Updated: 29/Oct/23  Resolved: 22/Mar/18

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Andrew Morrow (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Platforms 2018-03-26
Participants:

 Description   

Downstream developers should have a permalink to the latest green build of embedded.



 Comments   
Comment by Githook User [ 22/Mar/18 ]

Author:

{'email': 'acm@mongodb.com', 'name': 'Andrew Morrow', 'username': 'acmorrow'}

Message: SERVER-34043 Also upload SDK builds to s3 as -latest
Branch: master
https://github.com/mongodb/mongo/commit/f2d2013bdd11ca3b648cbb5ac38b2830da288122

Comment by Andrew Morrow (Inactive) [ 21/Mar/18 ]

Will it overwrite if I put the same filename, so that -latest gets updated?

Comment by Sam Kleinman (Inactive) [ 21/Mar/18 ]

The method that the releases use is the s3 copy operation, to very similar effect.

Comment by Andrew Morrow (Inactive) [ 21/Mar/18 ]

Oh neat. I should have thought to look at how the drivers were doing things. I'll see if I can make that work.

Comment by A. Jesse Jiryu Davis [ 21/Mar/18 ]

Can you do this in the Evergreen scripts without Build Team help? In the C Driver's config.yml we have something similar:

  "upload release":
    - command: shell.exec
      params:
        script: |
           [ -f mongoc/mongo*gz ] && mv mongoc/mongo*gz mongoc.tar.gz
    - command: s3.put
      params:
        aws_key: ${aws_key}
        aws_secret: ${aws_secret}
        local_file: mongoc.tar.gz
        remote_file: mongo-c-driver/${branch_name}/mongo-c-driver-${CURRENT_VERSION}.tar.gz
        bucket: mciuploads
        permissions: public-read
        content_type: ${content_type|application/x-gzip}

If you replaced CURRENT_VERSION with "latest" and made sure the task only runs after success that might do the trick.

Generated at Thu Feb 08 04:35:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.