Skip to content

[JENKINS-3942] Resolve job variables within Javadoc path location #18880

Closed

Description

@jenkins-infra-bot

Due to how clearcase works and our use of the plugin, we use a couple job
variables (NODE_NAME, JOB_NAME) to define the name of the clearcase view. This
value ends up as part of the filesystem. In order to make the build
relocatable, we have to be able to pass these variables to the post build
processors so that they can find all the build output.

This enhancement is to add the build variable processing to the javadoc plugin's
Javadoc directory setting. The code would then need to resolve this directory
at build time with the build parameters.


Originally reported by petehayes, imported from: Resolve job variables within Javadoc path location
  • status: Reopened
  • priority: Major
  • component(s): core
  • resolution: Unresolved
  • votes: 0
  • watchers: 0
  • imported: 2025-11-24
Raw content of original issue

Due to how clearcase works and our use of the plugin, we use a couple job variables (NODE_NAME, JOB_NAME) to define the name of the clearcase view. This value ends up as part of the filesystem. In order to make the build relocatable, we have to be able to pass these variables to the post build processors so that they can find all the build output.

This enhancement is to add the build variable processing to the javadoc plugin's Javadoc directory setting. The code would then need to resolve this directory at build time with the build parameters.

  • environment: Platform: All, OS: All

Activity

  1. jenkins-infra-bot commented on Sep 22, 2009

    @jenkins-infra-bot
    Author
    scm_issue_link:
    • Original comment link
    • Raw content of original comment:

      Code changed in hudson User: : kohsuke Path: trunk/hudson/main/core/src/main/java/hudson/tasks/JavadocArchiver.java trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=22031 Log: [FIXED JENKINS-3942] Fixed in 1.325. We probably need some kind of mechanical checks to make sure all the fields are variable expanded. Otherwise this is too error prone.

    Code changed in hudson
    User: : kohsuke
    Path:
    trunk/hudson/main/core/src/main/java/hudson/tasks/JavadocArchiver.java
    trunk/www/changelog.html
    http://fisheye4.cenqua.com/changelog/hudson/?cs=22031
    Log:
    [FIXED JENKINS-3942] Fixed in 1.325. We probably need some kind of mechanical checks to make sure all the fields are variable expanded. Otherwise this is too error prone.

  2. jenkins-infra-bot commented on Sep 1, 2011

    @jenkins-infra-bot
    Author
    salmira:
    • Original comment link
    • Raw content of original comment:

      "Publish Javadoc" section reports an error when variables are used for "Javadoc directory" value:

      No such directory: 'trunk/build/${SVN_REVISION}/docs /javadoc'

      Jenkins ver. 1.423 Ubuntu Server 10.04

    "Publish Javadoc" section reports an error when variables are used for "Javadoc directory" value:

    No such directory: 'trunk/build/${SVN_REVISION}/docs /javadoc'

    Jenkins ver. 1.423
    Ubuntu Server 10.04

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions