[SERVER-24423] Incorrect directory for fetching and putting artifacts in v2.6 branch of mongodb/mongo repo Created: 24/May/16  Updated: 31/Jan/18  Resolved: 13/Jun/16

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

Type: Bug Priority: Major - P3
Reporter: Zakhar Kleyman Assignee: Zakhar Kleyman
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Build 16 (06/24/16)
Participants:

 Description   

In the v2.6 branch of the mongodb/mongo repo, etc/evergreen.yml file has fetch and put artifacts functions using ${build_variant} var as the folder in the mciuploads bucket.
It should be using mongodb-mongo-v2.6 folder and ${build_variant} as a subfolder instead, like the rest of the branches.

    - command: s3.put
      params:
        aws_key: ${aws_key}
        aws_secret: ${aws_secret}
        local_file: target.tgz
        remote_file: ${build_variant}/${build_id}.tgz
        bucket: mciuploads
        permissions: public-read
        content_type: application/tar
        display_name: Artifacts

  "fetch artifacts" :
    command: s3.get
    params:
      aws_key: ${aws_key}
      aws_secret: ${aws_secret}
      remote_file: ${build_variant}/${build_id}.tgz
      bucket: mciuploads
      extract_to: src

It should be

remote_file: mongodb-mongo-v2.6/${build_variant}/${build_id}.tgz

in both cases.



 Comments   
Comment by Githook User [ 13/Jun/16 ]

Author:

{u'username': u'zakhark', u'name': u'Zakhar Kleyman', u'email': u'zakhar.kleyman@mongodb.com'}

Message: SERVER-24423: update artifact get/put path in evergreen.yml
Branch: v2.6
https://github.com/mongodb/mongo/commit/5342f8db9fe77c6f77c2df59f8e583fa23198231

Comment by Zakhar Kleyman [ 13/Jun/16 ]

I think that would only make sense since all other branches use this naming convention

Comment by Ernie Hershey [ 13/Jun/16 ]

Should 2.6 match them? i.e.

mongodb-mongo-v2.6/${build_variant}/${revision}/artifacts/${build_id}.tgz

Comment by Zakhar Kleyman [ 13/Jun/16 ]

master and v3.0 branches have fetch artifacts section as following

  "fetch artifacts" : &fetch_artifacts
    command: s3.get
    params:
      aws_key: ${aws_key}
      aws_secret: ${aws_secret}
      remote_file: mongodb-mongo-master/${build_variant}/${revision}/artifacts/${build_id}.tgz
      bucket: mciuploads
      extract_to: src

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