Answers: <p><a href="https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-Deployingacustombuildofacoreplugin" rel="noreferrer">This section</a> of the official <a href="https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial" rel="noreferrer">Jenkins Plugin Tutorial</a> will probably be of use.</p>
  
  <p>According to the writers of that documentation, you need to copy your .hpi file to <code>$JENKINS_HOME/plugins</code>, remove the plugin's development directory, and finally create an empty file called .hpi.pinned for maven to use. Then you should be ready to restart Jenkins and use your custom build of a core plugin.</p>
  
  <p>They also suggest running <code>mvn clean</code> when you're ready to update Jenkins to remove old files (after changing core plugins, old .jar files might still be around after updating).</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-03-02T01:50:55.253Z
Answers: 2017-03-02T01:50:55.253Z
Answers: Peter G
Body: <p>How to deploy a custom build of a core plugin bundled in Jenkins?</p>
  
Comments: CC BY-SA 3.0
Comments: 2017-02-28T17:00:52.467Z
Comments: What do you mean by "deploy a custom field"? If you've customized/forked a core plugin, you can probably just plop the hpi file in there and override the built-in one (disclaimer: haven't tried this, but worth looking in to).
Comments: Assaf Lavie
Comments: CC BY-SA 3.0
Comments: 2017-03-05T14:05:44.427Z
Comments: @AssafLavie edited the question to properly ask about `build`, not `field`.
Comments: Evgeny Zislis
Comments: CC BY-SA 3.0
Comments: 2017-03-05T14:47:38.787Z
Comments: Please demonstrate more research into the question. Especially since we are still in private beta.
Comments: avi
Tags: <jenkins><jenkins-plugins>
Title: How to deploy a custom build of a Jenkins core plugin?
UserDisplayName: kenorb
ThreadText: # How to deploy a custom build of a Jenkins core plugin?
  
  (Asked by: username_0 on 2017-02-28)
  
  How to deploy a custom build of a core plugin bundled in Jenkins?
  
  **Tags:** jenkins, jenkins-plugins
  
  > **Comments:**
  > **username_1**: What do you mean by "deploy a custom field"? If you've customized/forked a core plugin, you can probably just plop the hpi file in there and override the built-in one (disclaimer: haven't tried this, but worth looking in to).  
  > **username_2**: @username_1 edited the question to properly ask about `build`, not `field`.  
  > **username_3**: Please demonstrate more research into the question. Especially since we are still in private beta.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_4 on 2017-03-02. Score: 8 | Accepted answer
  
  [This section](https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-Deployingacustombuildofacoreplugin) of the official [Jenkins Plugin Tutorial](https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial) will probably be of use.
  
  According to the writers of that documentation, you need to copy your .hpi file to `$JENKINS_HOME/plugins`, remove the plugin's development directory, and finally create an empty file called .hpi.pinned for maven to use. Then you should be ready to restart Jenkins and use your custom build of a core plugin.
  
  They also suggest running `mvn clean` when you're ready to update Jenkins to remove old files (after changing core plugins, old .jar files might still be around after updating).
  
  
  ---
  
  