Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Jenkins integration
-
Hi,
I'm having problems uploading packages from Jenkins.We have a paremeterized master build for packages that is called from different builds.
The build takes care of modifying the assemblyinfo.cs with the versions passed as parameterers to the build, and After the msbuild succeeds, we are calling nuget pack
The line is:
nuget pack ${env:Project}${env:PropertiesSubDirectory}$env:{ProjectName}.csproj -Build -Symbols -Prop Configuration=Releasewhich generates a package like this:
XXX.YYY.1.2.19-dev.nupkgThe problem is that when I use those variables into the "Files to package" parameter of the upload task it always complain it can't find that file.
I used the powershell and jenkins variable format ($env: and $) with no success.
If I replaced the Files to package with a hardcoded name that already exists it works; however this is not possible since version tag changes for each build.
Is there any way to pass a variable to Files to package ?
Thanks,
FranciscoProduct: ProGet
Version: 4.1.3 -
I'm not sure if we'll be able to help here; this is basically Jenkins issuing a command to nuget.exe, so you may want to try on one of those support forums; if you do find the answer, please share here in case anyone stumbles across this post!
-
Hi Alana,
I don't think you understood my question.My problem is with the proget jenkins plugin.
The build has some environment variables to specify the version of the package, and when I use those variables in the "Files to package" parameter of the upload task of the plugin it always complain it can't find that file.
Francisco
-
Oh, see; so, you are using the Inedo ProGet Plugin after doing the msbuild, nupack, etc... and the field in the plug-in is not accepting a variable.
OK, that makes sense. We will investigate this.
-
Correct.
For example, if in the "Files to package" variable I enter a hardcoded value
eg. XXX.YYY.1.2.19-dev.nupkgIt works just fine. But if I use:
XXX.YYY.${MajorVersion}.${MinorVersion}.${BuildNumber}-devDoesn't. I verified the variables have the right values
Francisco
-
The Jenkins / ProGet Plugin has been updated to Version 0.3 with the following changes:
- Expand variable correctly
- Some basic validation on the version number
If you update, then it should work!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login