Skip to end of metadata
Go to start of metadata

Plugin Information

View Nuget on the plugin site for more information.

A Jenkins plugin allowing to:

  • trigger a job when a NuGet dependency is updated.
  • publish packages to NuGet repositories
The path to the NuGet exe is configurable. NuGet.exe uses config file in %APPDATA%\Nuget\Nuget.config (location depends on user Jenkins is running as).
NuGet repositories can be configured in global configuration along with corresponding API keys. These repositories can then be used in jobs to publish packages.

Changelog

Release 0.7

Release 0.6

Release 0.5

  • Added publication to NuGet repositories.
  • Added French localization.

Release 0.4

  • Fixed NuGet polling on remote slave.

Release 0.3

  • Added support for Run Condition Plugin, so Nuget trigger can be an option in the Conditional BuildStep Plugin or Flexible Publish Plugin.

Release 0.2

  • Fixed issue where NuGet exe path wasn't loaded on Jenkins restart

Release 0.1

  • Initial release

8 Comments

  1. It would be great to be able to specify the location of NuGet.config.

  2. When I enable NUGet Trigger on my job and save, I get an error from the stapler, caused by a NullPointerException in NugetTrigger.getLogFile(NugetTrigger.java:36).  That's where it's trying to build a File for the polling log base doff the job's root directory.

    I found some similar bug reports against other plugins, e.g.: https://issues.jenkins-ci.org/browse/JENKINS-18667?focusedCommentId=181728&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-181728

  3. It would be great to be able to specify if Prereleases should be checked too,l when "nuget list" is called.

    Is this still in development?

  4. Thank you,

    Right now I am trying to use it with Jenkins 2.0 and an Multibranch Pipeline but I get an exception when I Save the configuration with the option "Build on Nuget Updates":

    java.lang.ClassCastException: org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject cannot be cast to hudson.model.AbstractProject

    Is it possible to use this with the new Jenkins 2.0 Pipeline?

  5. Is it possible to use environment variables in the path to the nuget.exe in the global configuration (e.g. ${NUGET_HOME}\nuget.exe) instead of absolute paths or a path relative to the workspace?

  6. Should it work with pipeline and multibranch pipeline projects and if not, are there any plans to support this?