Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-11692

Build publisher does not work correctly when Build record path is changed

      • Create a Public and Private Jenkins instance, both with Build Publisher installed.
      • Check publishing from Private to Public works
      • Change the build record path in the Public Jenkins' configuration (copy/move the files if necessary)
      • Reload configuration on Public Jenkins or restart server.
      • Try publishing again from Private – the build will appear to be published but not appear on Public.
        • Examining the file system on Public, the latest published build is in, e.g.:
          C:\Jenkins\jobs\myjob\builds\published_build
          when it should be in
          D:\Jenkins_builds\myjob\builds\published_build

          [JENKINS-11692] Build publisher does not work correctly when Build record path is changed

          chris yate added a comment -

          Has anyone else been able to reproduce this problem?

          chris yate added a comment - Has anyone else been able to reproduce this problem?

          chris yate added a comment -

          Edit: I think this is a problem with Core; Build Publisher just pushes the builds at the "public" Jenkins via HTTP.

          chris yate added a comment - Edit: I think this is a problem with Core; Build Publisher just pushes the builds at the "public" Jenkins via HTTP.

          vjuranek added a comment -

          Hi, how do you change recoed path, by changing JENKINS_HOME? If you create new job on public jenkins, is it created correctly?

          vjuranek added a comment - Hi, how do you change recoed path, by changing JENKINS_HOME? If you create new job on public jenkins, is it created correctly?

          chris yate added a comment -

          server:8080/configure
          "Advanced" button just under the server name. Then you can configure Workspace root and Build record root directories.

          chris yate added a comment - server:8080/configure "Advanced" button just under the server name. Then you can configure Workspace root and Build record root directories.

          Code changed in jenkins
          User: Vojtech Juranek
          Path:
          src/main/java/hudson/plugins/build_publisher/ExternalProjectProperty.java
          http://jenkins-ci.org/commit/build-publisher-plugin/ffbcc7263834ba0b41e7d67b8e4095528ca2122d
          Log:
          [Fixed JENKINS-11692] publishig now takes into accnout custom builds directory

          Compare: https://github.com/jenkinsci/build-publisher-plugin/compare/2a27a8b...ffbcc72

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vojtech Juranek Path: src/main/java/hudson/plugins/build_publisher/ExternalProjectProperty.java http://jenkins-ci.org/commit/build-publisher-plugin/ffbcc7263834ba0b41e7d67b8e4095528ca2122d Log: [Fixed JENKINS-11692] publishig now takes into accnout custom builds directory Compare: https://github.com/jenkinsci/build-publisher-plugin/compare/2a27a8b...ffbcc72

          dogfood added a comment -

          Integrated in plugins_build-publisher #38
          [Fixed JENKINS-11692] publishig now takes into accnout custom builds directory (Revision ffbcc7263834ba0b41e7d67b8e4095528ca2122d)

          Result = SUCCESS
          Vojtech Juranek :
          Files :

          • src/main/java/hudson/plugins/build_publisher/ExternalProjectProperty.java

          dogfood added a comment - Integrated in plugins_build-publisher #38 [Fixed JENKINS-11692] publishig now takes into accnout custom builds directory (Revision ffbcc7263834ba0b41e7d67b8e4095528ca2122d) Result = SUCCESS Vojtech Juranek : Files : src/main/java/hudson/plugins/build_publisher/ExternalProjectProperty.java

          vjuranek added a comment -

          will be fixed in the next release

          vjuranek added a comment - will be fixed in the next release

            vjuranek vjuranek
            cjbrew chris yate
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: