starred/dotnet-packaging
1
0
Fork 0
mirror of https://github.com/quamotion/dotnet-packaging.git synced 2026-02-17 05:45:08 +00:00
Code Issues 207 Packages Projects Releases Wiki Activity

[PR #130] [MERGED] Add support for framework-dependent deployments #248

New Issue
Closed
opened 2026-01-29 16:31:35 +00:00 by claunia · 0 comments
claunia commented 2026-01-29 16:31:35 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/quamotion/dotnet-packaging/pull/130
Author: @qmfrederik
Created: 11/23/2019
Status: ✅ Merged
Merged: 11/25/2019
Merged by: @qmfrederik

Base: master ← Head: features/molecule-framework-dependent

📝 Commits (5)

  • c152cb0 Add Molecule tests for framework dependent apps
  • 8e230c8 Add default dependencies for framework-dependnet apps
  • 0061066 Architecture-independent is "noarch" for RPM, "all" for deb
  • 1311176 Run both self-contained and framework-dependent tests
  • 80be46e [molecule] linting

📊 Changes

17 files changed (+268 additions, -22 deletions)

View changed files

📝 .azure-pipelines.yml (+15 -8)
📝 Packaging.Targets.Tests/Deb/DebTaskTests.cs (+3 -3)
📝 Packaging.Targets.Tests/Rpm/RpmTaskTests.cs (+7 -7)
📝 Packaging.Targets/DebTask.cs (+1 -1)
📝 Packaging.Targets/RpmTask.cs (+1 -1)
📝 Packaging.Targets/build/Packaging.Targets.targets (+26 -2)
➕ molecule/framework-dependent/.yamllint (+13 -0)
➕ molecule/framework-dependent/framework-dependent-app/Program.cs (+12 -0)
➕ molecule/framework-dependent/framework-dependent-app/framework-dependent-app.csproj (+9 -0)
➕ molecule/framework-dependent/meta/main.yml (+14 -0)
➕ molecule/framework-dependent/molecule/default/Dockerfile.j2 (+18 -0)
➕ molecule/framework-dependent/molecule/default/molecule.yml (+50 -0)
➕ molecule/framework-dependent/molecule/default/playbook.yml (+5 -0)
➕ molecule/framework-dependent/molecule/default/tests/test_default.py (+10 -0)
➕ molecule/framework-dependent/tasks/deb.yml (+34 -0)
➕ molecule/framework-dependent/tasks/main.yml (+13 -0)
➕ molecule/framework-dependent/tasks/rpm.yml (+37 -0)

📄 Description

This PR adds support for framework-dependent deployments.

If you run dotnet deb or dotnet rpm and no RuntimeIdentifier is set, the resulting .deb and .rpm file will be architecture-independent and have a generic dependency on the .NET Core framework.

Includes Molecule tests for deploying to most Linux OSes supported by .NET Core:

  • Ubuntu: 16.04, 18.04, 19.04
  • Debian: 9, 10
  • CentOS: 7
  • Fedora: 29, 30
  • OpenSUSE: 15

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/quamotion/dotnet-packaging/pull/130 **Author:** [@qmfrederik](https://github.com/qmfrederik) **Created:** 11/23/2019 **Status:** ✅ Merged **Merged:** 11/25/2019 **Merged by:** [@qmfrederik](https://github.com/qmfrederik) **Base:** `master` ← **Head:** `features/molecule-framework-dependent` --- ### 📝 Commits (5) - [`c152cb0`](https://github.com/quamotion/dotnet-packaging/commit/c152cb02d3f75c00ecb572f9791da721f524d9d0) Add Molecule tests for framework dependent apps - [`8e230c8`](https://github.com/quamotion/dotnet-packaging/commit/8e230c808134356b11677dbe0a78b6ad6076b78c) Add default dependencies for framework-dependnet apps - [`0061066`](https://github.com/quamotion/dotnet-packaging/commit/00610664e99ad99f9d46c1bd7e3645a6a1fa0c32) Architecture-independent is "noarch" for RPM, "all" for deb - [`1311176`](https://github.com/quamotion/dotnet-packaging/commit/1311176d0b02135be2f16c4962b7465c8148cb8e) Run both self-contained and framework-dependent tests - [`80be46e`](https://github.com/quamotion/dotnet-packaging/commit/80be46e77d734d3f2104f0b684f3249c0dc470ef) [molecule] linting ### 📊 Changes **17 files changed** (+268 additions, -22 deletions) <details> <summary>View changed files</summary> 📝 `.azure-pipelines.yml` (+15 -8) 📝 `Packaging.Targets.Tests/Deb/DebTaskTests.cs` (+3 -3) 📝 `Packaging.Targets.Tests/Rpm/RpmTaskTests.cs` (+7 -7) 📝 `Packaging.Targets/DebTask.cs` (+1 -1) 📝 `Packaging.Targets/RpmTask.cs` (+1 -1) 📝 `Packaging.Targets/build/Packaging.Targets.targets` (+26 -2) ➕ `molecule/framework-dependent/.yamllint` (+13 -0) ➕ `molecule/framework-dependent/framework-dependent-app/Program.cs` (+12 -0) ➕ `molecule/framework-dependent/framework-dependent-app/framework-dependent-app.csproj` (+9 -0) ➕ `molecule/framework-dependent/meta/main.yml` (+14 -0) ➕ `molecule/framework-dependent/molecule/default/Dockerfile.j2` (+18 -0) ➕ `molecule/framework-dependent/molecule/default/molecule.yml` (+50 -0) ➕ `molecule/framework-dependent/molecule/default/playbook.yml` (+5 -0) ➕ `molecule/framework-dependent/molecule/default/tests/test_default.py` (+10 -0) ➕ `molecule/framework-dependent/tasks/deb.yml` (+34 -0) ➕ `molecule/framework-dependent/tasks/main.yml` (+13 -0) ➕ `molecule/framework-dependent/tasks/rpm.yml` (+37 -0) </details> ### 📄 Description This PR adds support for framework-dependent deployments. If you run `dotnet deb` or `dotnet rpm` and no `RuntimeIdentifier` is set, the resulting `.deb` and `.rpm` file will be architecture-independent and have a generic dependency on the .NET Core framework. Includes Molecule tests for deploying to most Linux OSes supported by .NET Core: * Ubuntu: 16.04, 18.04, 19.04 * Debian: 9, 10 * CentOS: 7 * Fedora: 29, 30 * OpenSUSE: 15 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-29 16:31:35 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pending-validation
pull-request
Mirrored from GitHub Pull Request
 up-for-grabs
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dotnet-packaging#248
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?