remove JenkinsFile and associated jjbb jobs

.ci/ci.csproj

@@ -9,9 +9,4 @@
     <AppendRuntimeIdentifierToOutputPath>false</AppendRuntimeIdentifierToOutputPath>
     <IntermediateOutputPath>$(ProjectDir)</IntermediateOutputPath>
   </PropertyGroup>
-  <ItemGroup>
-    <None Include="../Jenkinsfile" />
-
-  </ItemGroup>
-
 </Project>

.editorconfig

@@ -202,14 +202,6 @@ resharper_csharp_accessor_owner_body=expression_body
 resharper_redundant_case_label_highlighting=do_not_show
 resharper_redundant_argument_default_value_highlighting=do_not_show
 
-[Jenkinsfile]
-indent_style = space
-indent_size = 2
-end_of_line = lf
-charset = utf-8
-trim_trailing_whitespace = true
-insert_final_newline = true
-
 [*.{sh,bat,ps1}]
 trim_trailing_whitespace=true
 insert_final_newline=true

RELEASING.md

@@ -50,7 +50,7 @@ After the new changelog and version have been merged to main, the only thing rem
  git push upstream v<major>.<minor>.<bug>(-<suffix>)?
  ```
 
-The above commands will push the GitHub tag and will trigger the corresponding [CI Build pipeline](Jenkinsfile) which will run all the required stages to satisfy the release is in a good shape, then at the very end of the pipeline there will be an input approval waiting for an UI interaction to release to the NuGet repo. This particular input approval step will notify by email, to the owners of this repo, regarding the expected action to be done for doing the release.
+The above commands will push the GitHub tag and will trigger the corresponding [Github Action](.github/workflows/release-main.yml) which will run all the required stages to satisfy the release is in a good shape, then at the very end of the pipeline there will be an input approval waiting for an UI interaction to release to the NuGet repo. This particular input approval step will notify by email, to the owners of this repo, regarding the expected action to be done for doing the release.
 
 Tag names should start with a `v` prefix.