DYN-8030: PM artifact. (#16)

* DYN-8030: PM artifact.

* Remove package_version.

* Update artifacts pattern to TuneUp pattern.

* Merge conflicts.

* PM publish automated.

* Update versions.

* Solving comments.

---------

Co-authored-by: Alexis Erazo <alexis.erazo@autodesk.com>

Author: AlexisErazoGlobant

README.md

@@ -2,4 +2,13 @@
 
 Contains the DSIronPython package for using the legacy IronPython2 engine in Dynamo.
 Building this soluton will produce a dynamo package containing the python engine and an extension to load it.
-This repo is a WIP.
+This repo is a WIP.
+
+### How to publish a new version
+We currently can't use the release PR option when making releases on mirrored repositories. There is a propsed follow-up improvment filed that would allow CILibrary to create a PR against the public repository instead (DYN-8724). But until that is done, our release process will be:
+
+- Create a release branch on the internal repository
+- Build the branch to publish
+- Manually create a PR on the public repository with the changes introduced by the release branch (the updated version number in the pipeline file). 
+- Review and merge this PR
+- Delete the release branch on the internal repository

pipeline.yml

@@ -1,6 +1,6 @@
-version: 3.1.0
+version: 3.2.1
 env:
-  - JENKINS_NODE_WIN: "CDA-VS22-SVC"
+  - JENKINS_NODE_WIN: "CDA-VS22-DT"
   - SLACK_QUANTUM_BUILD_CHANNEL : "#dynamo-jenkinsbuild"
   - SLACK_QUANTUM_BUILD_CREDENTIAL_ID : "slack-notify-token"
   - MAIL_QUANTUM_BUILD_RECIPIENT : "dynamo.dev@autodesk.com"
@@ -54,9 +54,10 @@ deployment:
 
   -
     type: artifacts
-    allow_branches: master
-    publish_to_artifactory: false
     publish_to_jenkins: true
+    publish_to_artifactory: false
+    publish_to_package_manager: true
+    use_dev_pm: false
     scripts:
       - "pwsh.exe -ExecutionPolicy ByPass -Command Compress-Archive -Path .\\package_output\\DSIronPython -DestinationPath .\\DSIronPythonPackage.zip"
     outputs: