[SERVER-47171] non-release/push variants build packages Created: 29/Mar/20 Updated: 27/Oct/23 Resolved: 29/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sam Kleinman (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Participants: |
| Description |
|
A number of variants on master (and presumably 4.4) have "package" tasks even when they're non-releasing/non-pushing variants. We should remove packaging tasks |
| Comments |
| Comment by Max Hirschhorn [ 29/Mar/20 ] |
|
sam.kleinman, I had gotten confused about this myself, the package task is responsible for uploading the binaries, artifacts, and debug symbols to S3 for subsequent tasks to download, and the publish_packages and push tasks are responsible for releasing. The package task runs as part of the normal compile_all_run_unittests_TG task group. |