Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add README for .NET #1420

Merged
merged 1 commit into from
Jul 25, 2024
Merged

Add README for .NET #1420

merged 1 commit into from
Jul 25, 2024

Conversation

alexandrevicenzi
Copy link
Member

This is related to #993.

dcermak pushed a commit that referenced this pull request Jul 16, 2024
dcermak pushed a commit that referenced this pull request Jul 16, 2024
Copy link

github-actions bot commented Jul 16, 2024

Created a staging project on OBS for Tumbleweed: home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1420
Changes pushed to branch Tumbleweed-1420 as commit a39c3234b946ad817c2a9b4f37d49477405b854e
Build succeeded ✅

Build Results

Repository images in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1420 for x86_64: current state: published
Build results:

package name status build log
kiwi-image ⛔ excluded live log

Repository images in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1420 for aarch64: current state: published
Build results:

package name status build log
kiwi-image ⛔ excluded live log

Repository containerfile in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1420 for x86_64: current state: published
Build results:

package name status build log
kiwi-image ✅ succeeded live log

Repository containerfile in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1420 for aarch64: current state: published
Build results:

package name status build log
kiwi-image ✅ succeeded live log

Build succeeded ✅

To run BCI-tests against this PR, use the following command:

OS_VERSION=tumbleweed TARGET=custom BASEURL=registry.opensuse.org/home/defolos/bci/staging/tumbleweed/tumbleweed-1420/ tox -- -n auto
The following images can be pulled from the staging project:
  • registry.opensuse.org/home/defolos/bci/staging/tumbleweed/tumbleweed-1420/containerfile/opensuse/bci/kiwi
⚠️⚠️ Project and Branch have been deleted ⚠️⚠️ ⚠️⚠️ Project and Branch have been deleted ⚠️⚠️ ⚠️⚠️ Project and Branch have been deleted ⚠️⚠️

@@ -393,7 +383,7 @@ def _is_latest_dotnet(version: _DOTNET_VERSION_T, os_version: OsVersion) -> bool
os_version=os_version,
version=ver,
name="dotnet-sdk",
pretty_name=f".Net {ver} SDK",
pretty_name=f".NET SDK {ver}",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

before anyone asks, these are the official names and case styling used by Microsoft.

Copy link

github-actions bot commented Jul 16, 2024

Created a staging project on OBS for 6: home:defolos:BCI:Staging:SLE-15-SP6:6-1420
Changes pushed to branch 6-1420 as commit 2821eb726767f995b5bbc9f41a6fce4c83db33b2
Build succeeded ✅

Build Results

Repository images in home:defolos:BCI:Staging:SLE-15-SP6:6-1420 for x86_64: current state: published
Build results:

package name status build log
aspnet-runtime-6.0 ⛔ excluded live log
aspnet-runtime-8.0 ⛔ excluded live log
dotnet-6.0 ⛔ excluded live log
dotnet-8.0 ⛔ excluded live log
dotnet-runtime-6.0 ⛔ excluded live log
dotnet-runtime-8.0 ⛔ excluded live log

Repository images in home:defolos:BCI:Staging:SLE-15-SP6:6-1420 for aarch64: current state: published
Build results:

package name status build log
aspnet-runtime-6.0 ⛔ excluded live log
aspnet-runtime-8.0 ⛔ excluded live log
dotnet-6.0 ⛔ excluded live log
dotnet-8.0 ⛔ excluded live log
dotnet-runtime-6.0 ⛔ excluded live log
dotnet-runtime-8.0 ⛔ excluded live log

Repository images in home:defolos:BCI:Staging:SLE-15-SP6:6-1420 for s390x: current state: published
Build results:

package name status build log
aspnet-runtime-6.0 ⛔ excluded live log
aspnet-runtime-8.0 ⛔ excluded live log
dotnet-6.0 ⛔ excluded live log
dotnet-8.0 ⛔ excluded live log
dotnet-runtime-6.0 ⛔ excluded live log
dotnet-runtime-8.0 ⛔ excluded live log

Repository images in home:defolos:BCI:Staging:SLE-15-SP6:6-1420 for ppc64le: current state: published
Build results:

package name status build log
aspnet-runtime-6.0 ⛔ excluded live log
aspnet-runtime-8.0 ⛔ excluded live log
dotnet-6.0 ⛔ excluded live log
dotnet-8.0 ⛔ excluded live log
dotnet-runtime-6.0 ⛔ excluded live log
dotnet-runtime-8.0 ⛔ excluded live log

Repository containerfile in home:defolos:BCI:Staging:SLE-15-SP6:6-1420 for x86_64: current state: published
Build results:

package name status build log
aspnet-runtime-6.0 ✅ succeeded live log
aspnet-runtime-8.0 ✅ succeeded live log
dotnet-6.0 ✅ succeeded live log
dotnet-8.0 ✅ succeeded live log
dotnet-runtime-6.0 ✅ succeeded live log
dotnet-runtime-8.0 ✅ succeeded live log

Repository containerfile in home:defolos:BCI:Staging:SLE-15-SP6:6-1420 for aarch64: current state: published
Build results:

package name status build log
aspnet-runtime-6.0 ⛔ excluded live log
aspnet-runtime-8.0 ⛔ excluded live log
dotnet-6.0 ⛔ excluded live log
dotnet-8.0 ⛔ excluded live log
dotnet-runtime-6.0 ⛔ excluded live log
dotnet-runtime-8.0 ⛔ excluded live log

Repository containerfile in home:defolos:BCI:Staging:SLE-15-SP6:6-1420 for s390x: current state: published
Build results:

package name status build log
aspnet-runtime-6.0 ⛔ excluded live log
aspnet-runtime-8.0 ⛔ excluded live log
dotnet-6.0 ⛔ excluded live log
dotnet-8.0 ⛔ excluded live log
dotnet-runtime-6.0 ⛔ excluded live log
dotnet-runtime-8.0 ⛔ excluded live log

Repository containerfile in home:defolos:BCI:Staging:SLE-15-SP6:6-1420 for ppc64le: current state: published
Build results:

package name status build log
aspnet-runtime-6.0 ⛔ excluded live log
aspnet-runtime-8.0 ⛔ excluded live log
dotnet-6.0 ⛔ excluded live log
dotnet-8.0 ⛔ excluded live log
dotnet-runtime-6.0 ⛔ excluded live log
dotnet-runtime-8.0 ⛔ excluded live log

Build succeeded ✅

To run BCI-tests against this PR, use the following command:

OS_VERSION=15.6 TARGET=custom BASEURL=registry.opensuse.org/home/defolos/bci/staging/sle-15-sp6/6-1420/ tox -- -n auto
The following images can be pulled from the staging project:
  • registry.opensuse.org/home/defolos/bci/staging/sle-15-sp6/6-1420/containerfile/bci/dotnet-aspnet
  • registry.opensuse.org/home/defolos/bci/staging/sle-15-sp6/6-1420/containerfile/bci/dotnet-runtime
  • registry.opensuse.org/home/defolos/bci/staging/sle-15-sp6/6-1420/containerfile/bci/dotnet-sdk

Copy link
Collaborator

@dcermak dcermak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The readme is missing the standard footer & header.

Also, would it make it sense to have separate templates for the images? The current template looks more like three templates with a bit of common content.

src/dotnet/README.md.j2 Outdated Show resolved Hide resolved
src/dotnet/README.md.j2 Outdated Show resolved Hide resolved
src/dotnet/README.md.j2 Outdated Show resolved Hide resolved
src/dotnet/README.md.j2 Outdated Show resolved Hide resolved
src/dotnet/README.md.j2 Outdated Show resolved Hide resolved
src/dotnet/README.md.j2 Outdated Show resolved Hide resolved
@@ -408,7 +398,7 @@ def _is_latest_dotnet(version: _DOTNET_VERSION_T, os_version: OsVersion) -> bool
version=ver,
name="dotnet-runtime",
is_sdk=False,
pretty_name=f".NET {ver} runtime",
pretty_name=f".NET Runtime {ver}",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we use sentence style capitalization here and "runtime" suffix is used elsewhere. why do we need to change this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these are the official names and case styling used by Microsoft.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dmpop or @lvicoun can you advise what is best here?

@@ -432,7 +422,7 @@ def _is_latest_dotnet(version: _DOTNET_VERSION_T, os_version: OsVersion) -> bool
os_version=os_version,
name="dotnet-aspnet",
is_sdk=False,
pretty_name=f"ASP.NET {ver} runtime",
pretty_name=f"ASP.NET Core Runtime {ver}",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we use sentence style capitalization here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these are the official names and case styling used by Microsoft.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See this for example https://dotnet.microsoft.com/en-us/download/dotnet/8.0

I don't see a reason to use lowercase on the package name, we don't call Apache tomcat, ASP.NET Core Runtime is the entire name, so the image would still be "ASP.NET Core Runtime container image".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dmpop or @lvicoun can you advise what is best here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Easy: follow the capitalization used in the official product name. 😄

To compile and deploy an application, copy the sources and build the binary:

```Dockerfile
FROM registry.suse.com/bci/dotnet-sdk:{{ image.version }} AS build
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we avoid hardcoding the registry reference here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, what is the best approach?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed to use the registry variable.

@alexandrevicenzi
Copy link
Member Author

The readme is missing the standard footer & header.

Yes, because .NET does not belong in bci_build. I have no way of reusing templates from there and I would need to duplicate it, create some hackery, or move .NET into bci_build as a package like others.

What do you suggest @dcermak @dirkmueller?

Also, would it make it sense to have separate templates for the images? The current template looks more like three templates with a bit of common content.

Yes, it could be split, but again, it needs a bit more hackery to get it working, unless it becomes a bci_build package.

@dcermak
Copy link
Collaborator

dcermak commented Jul 17, 2024

The readme is missing the standard footer & header.

Yes, because .NET does not belong in bci_build. I have no way of reusing templates from there and I would need to duplicate it, create some hackery, or move .NET into bci_build as a package like others.

What do you suggest @dcermak @dirkmueller?

I haven't tried this, but I think the following should work:

  • move the template to src/bci_build/package/dotnet-sdk/README.md.j2
  • symlink src/bci_build/package/dotnet-{runtime,aspnet}/README.md.j2 to the first template

then the standard readme reading code should pick it up and you should have access to additional footer & headers.

Also, would it make it sense to have separate templates for the images? The current template looks more like three templates with a bit of common content.

Yes, it could be split, but again, it needs a bit more hackery to get it working, unless it becomes a bci_build package.

I don't think that you need to have it in the bci_build package for the template reader to pick it up.

@alexandrevicenzi
Copy link
Member Author

@dcermak no hackery needed. It seems that the template is picked from the correct place. I also split into multiple templates and created a few partials to be imported where text was duplicated.

dcermak pushed a commit that referenced this pull request Jul 23, 2024
@dcermak dcermak dismissed their stale review July 24, 2024 10:32

changes were adressed

src/bci_build/package/dotnet-aspnet/README.md.j2 Outdated Show resolved Hide resolved
src/bci_build/package/dotnet-runtime/README.md.j2 Outdated Show resolved Hide resolved
src/bci_build/package/dotnet-sdk/README.md.j2 Outdated Show resolved Hide resolved
src/bci_build/package/dotnet-sdk/README.md.j2 Outdated Show resolved Hide resolved
src/bci_build/package/dotnet-sdk/README.md.j2 Outdated Show resolved Hide resolved
src/bci_build/package/templates/dotnet_globalization.j2 Outdated Show resolved Hide resolved
src/bci_build/package/templates/dotnet_notice.j2 Outdated Show resolved Hide resolved
src/bci_build/package/templates/dotnet_notice.j2 Outdated Show resolved Hide resolved
src/bci_build/package/templates/dotnet_notice.j2 Outdated Show resolved Hide resolved
@@ -432,7 +422,7 @@ def _is_latest_dotnet(version: _DOTNET_VERSION_T, os_version: OsVersion) -> bool
os_version=os_version,
name="dotnet-aspnet",
is_sdk=False,
pretty_name=f"ASP.NET {ver} runtime",
pretty_name=f"ASP.NET Core Runtime {ver}",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Easy: follow the capitalization used in the official product name. 😄

dcermak pushed a commit that referenced this pull request Jul 24, 2024
@dcermak dcermak merged commit e9d95a5 into main Jul 25, 2024
7 checks passed
@dcermak dcermak deleted the dotnet-readme branch July 25, 2024 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants