Create Jenkins Pipeline for Internalizing, Converting, and Pushing Packages to Intune
- Dominant language
- MDX
- Stars
- 223
- Forks
- 248
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 4
Description
## What New Or Updated Would You Like To See?
Putting together a doc much like the [Automate Package Internalizer Doc](https://docs.chocolatey.org/en-us/guides/organizations/automate-package-internalization) we currently have. This one will cater more to guiding C4B trialists/users who have an existing Intune Environment. Because these users have Intune, they don't have the need for a repository solution as Intune acts as an app store much as a repository does as a package storage.
It will focus on using the functionality of the Intune integration and package internalizer to process the following workflow through a Jenkins pipeline.
- Internalize packages from the Chocolatey Community Repository(CCR)
- Convert those internalized packages to Intune win files.
- Then lastly push the generated *.intunewin files to the Intune tenant specified.
## Why Is It Needed?
Feel this addition would add value as the need for a doc like this came out of the discussion following the last Intune Webinar on March 30th, 2022.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.