You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(build): MONGOSH-122: upload linux packages to barque (#286)
- Introduces `curator` as a tool to upload packaged assets to barque,
MongoDB's PPA service.
- Uses an already bundled and packaged mongosh binary that was already
uploaded to Evergreen's S3 bucket to send to barque.
- Adds additional environmental variables to the build process:
`BARQUE_USERNAME`, `BARQUE_API_KEY`, `NOTARY_TOKEN`,
`NOTARY_KEY_NAME`. These are then used by `curator`.
- Adds `repo-config.yml` that is necessary for a barque upload. The
config specifies uploads for 3 different distros: `debian10`,
`ubuntu1804`, `rhel80`.
- We only upload the package to `org` MongoDB repository.
- We only upload along with `4.4.0` MongoDB version.
- These artifacts are only sent to `barque` when we do a public release
(`shouldDoPublicRelease`), i.e. a tagged commit and on main branch.
- We fetch the latest curator tarball before proceeding to upload to
barque.
Co-authored-by: Anna Henningsen <[email protected]>
Copy file name to clipboardExpand all lines: packages/build/README.md
+27-19Lines changed: 27 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,25 +10,33 @@ root of the project.
10
10
11
11
Current build and release flow is as follows:
12
12
13
-
- `npm run evergreen-release package
14
-
- A commit triggers an evergreen build based on currently available build
15
-
variants: MacOS, Windows, Linux, Debian, and RedHat.
16
-
- MacOS, Linux and Windows run three tasks: check, test, and release. Debian and
17
-
Redhat run two tasks: check and release. Debian and Redhat also depend on
18
-
tests to pass on Linux.
19
-
- Identical bundle and binary are built on all five variants.
20
-
- Each variant creates its own tarball (`.zip`, `.tgz`, `.deb`, `.rpm`). Type of
21
-
tarball is determined by the current build variant.
22
-
- Each variant uploads its own tarball to Evergreen’s AWS.
23
-
- MacOS build variant uploads config file with information about the new version
24
-
for each platform to Downloads Centre. This only happens on a tagged commit.
25
-
- MacOS build variant creates a github release. This only happens on a tagged
26
-
commit.
27
-
- The five build variants run in parallel.
28
-
-`npm run evergreen-release publish`
29
-
- All the previous build steps succeeded.
30
-
- A separate MacOS build variant (darwin_publish_release) uploads config file with information about the new version for each platform to Downloads Centre. This only happens on a tagged commit.
31
-
- A separate MacOS build variant (darwin_publish_release) promotes the draft github release to public. This only happens on a tagged commit.
13
+
### `npm run evergreen-release package`
14
+
- A commit triggers an evergreen build based on currently available build
15
+
variants: MacOS, Windows, Linux, Debian, and RedHat.
16
+
- MacOS, Linux and Windows run three tasks: check, test, and release. Debian and
17
+
Redhat run two tasks: check and release. Debian and Redhat also depend on
18
+
tests to pass on Linux.
19
+
- Identical bundle and binary are built on all five variants.
20
+
- Each variant creates its own tarball (`.zip`, `.tgz`, `.deb`, `.rpm`). Type of
21
+
tarball is determined by the current build variant.
22
+
- Each variant uploads its own tarball to Evergreen’s AWS.
23
+
- Linux build variants upload their artifacts to `barque` using
24
+
[`curator`](https://github.com/mongodb/curator) to be used with MongoDB's PPA. The uploaded packages can be found under the following URLs:
0 commit comments