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

Add "Project path" as exported environment variable

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • tfs-plugin
    • None
    • Platform: All, OS: All

      One thing I would like to do is to automatically label the source code in TFS
      for every Hudson build. It seems that right now the only way to do that is to
      add an Ant target to use the <tfslabel> Teamprise ant task
      (http://www.teamprise.com/products/ant/) to accomplish this. This works fine,
      except that I don’t see a way to get the Project path (e.g., $/Project/sub/sub),
      which is needed to apply the label correctly.

      Am I missing some way to get the project path inside my Ant script? If not, is
      there any way the project path could be added as an exported environment
      variable? (like you do for TFS_WORKSPACE and TFS_WORKFOLDER)

      At the same time, maybe it would make sense to make the other TFS-related
      configuration items available as environment variables: Server URL, Login name,
      Password (not sure about that one)...

      I do have a workaround for this...I can hard code the project path as an Ant
      property, but that means I have the project path defined in two places in the
      Hudson job config screen, which means when I create a new Hudson job for a
      branch I have to make the change in two places.

      Thanks,
      Jeff

            redsolo redsolo
            jeffolson jeffolson
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: