feat: Add .NET Tutorial

[berviantoleo]

Part of

• Add .NET Quickstart jenkins-docs/quickstart-tutorials#1056
• feat: add dotnet agent jenkins-docs/quickstart-tutorials#1057

See https://deploy-preview-7977--jenkins-io-site-pr.netlify.app/doc/tutorials/build-a-dotnet-web-app-with-jenkins/ for the preview.

[kmartens27]

It appears that there are chunks of content here that are copied over from the Maven tutorial. For instance, there is a large section of "Create your initial Pipeline as a Jenkinsfile" which reads as though it was copied with only minimal changes made.

Additionally, when forking the sample repository a completely updated Jenkinsfile is included, defeating the purpose of the tutorial. I also don't see a build step in the pipeline overview despite it being included

This is after a clean fork of the original repository and running the Build (without making any changes to the completed jenkinsfile).

The screenshots are far too small to be readable by users and must be more focused so that the content is visible. Right now, I have to zoom in quite a bit to even read what is being displayed.

The capture here is also far too wide on the screen, as there is a ton of blank space to the right of the actual build status information, which is unnecessary.

There may be other changes needed, but these are my initial findings.

[berviantoleo]

Thank you. I'll revise the sample repository and the tutorial. I wonder how the better approach for capturing the screenshot.

[kmartens27]

Hi @berviantoleo, for the screenshots, I would recommend resizing the window to a smaller size so that there is not so much blank space on the page. Additionally, if you use a screenshot tool to capture just a section of the screen, instead of the full screen, it will help focus on the content that matters. For instance, the first-build-details screenshot could be more focused on the build details and captured closer to how the artifacts screenshot displays. The thing to keep in mind is that not everyone will be using the same size/resolution monitor and therefore screenshots can change very easily depending on the users hardware.

[kmartens27]

Thanks very much @berviantoleo for your work and updates on this. I've provided a couple further suggestions regarding the text/screenshots. Approving pending those updates.

[gounthar]

When this tutorial is nearly ready for merging, we should migrate the code repository to the jenkins-docs organization. It's important to ensure that we link to a repository that is part of the Jenkins project.

Thanks!

[kmartens27]

@gounthar should that happen prior to merge or after the merge has taken place? I want to be sure we make this as easy as possible since we've learned from last time.

[gounthar]

We can reference Bervianto's repository, but I would prefer to merge this PR after the repository has been migrated. This will ensure that we don't overlook the migration step.

[gounthar]

@berviantoleo could you please make me an admin/maintainer/co-author/anything that would allow me to migrate your repo to the jenkins-docs organization?
Thanks. 🙏

[berviantoleo]

@berviantoleo could you please make me an admin/maintainer/co-author/anything that would allow me to migrate your repo to the jenkins-docs organization? Thanks. 🙏

@gounthar
I think I should use a transfer repository for doing that. Adding a collaborator won't allow migrating the repo.

[gounthar]

Please go ahead this way, then.

[berviantoleo]

Please go ahead this way, then.

I've sent the transfer request.

[gounthar]

Thanks a lot, Bervianto.
Transfer finalized!