Topics created by MaxCascone

Thanks, yeah, that seems to work. I changed my pipeline code to not send any title metadata to ProGet, which returned that field in the UI to its original behavior. I also found that rebuilding an existing package, and sent to ProGet with the updated pipeline, has the same effect.

After futzing with the certs on the proget host vm, it looks like we've got full connectivity to the chocolatey.org feed as well as nuget.org. Can someone remind me/point me to docs around the difference between connector caching of packages vs. the "pull to proget" function? thanks!

It seems the package deployment endpoint is POST-only, but using the Native API you could use the Packages_GetPackageDeployments method. Down the line we can certainly consider adding GET method on the deployment api... if you can help us know what you/someone will use that info for ;)

@mcascone yep, that's a good way of putting it!

@mcascone do you happen to remember where you found that link? We are trying to be conservative about adding a ton of redirect rules... We are now running automated scans, so HOPEFULLY it's picking up bad links within the docs.

@mcascone I don't think it's new, but it's just used to specify the dependencies field in the manifest file; I'm thinking, perhaps, it might be similar/identical to the consumes field you added? https://docs.inedo.com/docs/upack-universal-packages-manifest The only thing Inedo tools use it for today is just displaying information in ProGet, on the dependencies tab. That may / may not be helpful.

Just thought I'd drop in and describe where we ended up with this. It works for us, YMMV. This is running in the context of a Jenkins deploy run, but the concepts should apply to most other use cases. There are a lot of env vars floating around in all of this; i know it's not ideal, but it's really the easiest way to move values around in Jenkins without going crazy with OO classes that are really hard to get working in the Jenkins context. I have recently come up with a pattern to store more complex objects in env vars as json strings, and convert them when needed. Happy to answer any questions from anyone interested in using this admittedly obscure functionality. // this is called from vars/deploy.groovy when appropriate clickOnceDeploy([clickAppName:env.clickOnceName, clickAppPath:env.clickOnceDir, targetEnv:targetMap.key]) // defined in vars/deploy.groovy def clickOnceDeploy(HashMap clickParms) { // find the zip in the download folder String dlFolder = "${WORKSPACE}/${env.packageDownloadDir}" String clickOncePackage = "${dlFolder}/${env.releasePath}/${clickParms.clickAppPath}.zip" String targetEnv = clickParms.targetEnv String zipFileName = "${clickOncePackage.replace('.zip', '')}-${targetEnv}.zip" // extract the zip - select the target env folder unzip zipFile: clickOncePackage, glob: "${targetEnv}/**", quiet: true // zip that folder up, use powershell to get the dir included pwsh "Compress-Archive -Path ${targetEnv} -DestinationPath ${zipFileName} -Force" // publish it to proget asset dir HashMap publishParams = [assetDir:"${clickParms.clickAppName}", zipFilePath:zipFileName] addToInfoMessages("Publishing ClickOnce App: ${clickParms.clickAppName}/${targetEnv}") publish.publishProGetAssetFromZip(publishParams) // defined in vars/publish.groovy def publishProGetAssetFromZip(HashMap publishParams) { // check for required params assert publishParams.assetDir != null assert publishParams.zipFilePath != null // sane defaults publishParams.get('progetBase', env.progetUrl) publishParams.get('overwrite', true) publishParams.get('format', 'zip') // build the api endpoint String progetAssetImportApi = "endpoints/${publishParams.assetDir}/import/?format=${publishParams.format}&overwrite=${publishParams.overwrite.toString()}" String assetUrl = "${publishParams.progetBase}/${progetAssetImportApi}" // need to pass the api token, so pull it from the jenkins cred store withCredentials([string(credentialsId: 'proget-api-key', variable: 'token')]) { retry(3) { httpRequest httpMode: 'POST', url: assetUrl, uploadFile: publishParams.zipFilePath, customHeaders: [[maskValue: true, name: 'X-APIKey', value: token]], ignoreSslErrors: true, responseHandle: 'NONE', contentType: 'APPLICATION_OCTETSTREAM', wrapAsMultipart: false, quiet: true } } addToInfoMessages("Published to ${publishParams.progetBase}/assets/${publishParams.assetDir}") }

Thanks for updating and letting us know the problem was related to a connection string!

Fantastic, looking forward to it! Sorry for the work, but i'm happy to contribute in some small way as well!

@mcascone_8142 said in breaking forward slash inserted in downloadprogetpackage jenkins plugin: I opened a bug on Jenkins' JIRA: https://issues.jenkins-ci.org/browse/JENKINS-61299