Setenv Plugin

Plugin Information

Plugin ID setenv
Latest Release 1.1
Latest Release Date Dec 28, 2009
Sources Subversion
Support Eclipse Hudson Forum
Issue Tracking Eclipse Bugzilla

Set environment variables for a project, to be referenced during build steps.

This plugin adds a section to job configuration pages for specifying key/value pairs of environment variables. These environment variables will be available to build steps in both freestyle and Maven projects, including the Ant, Maven, shell, and batch steps in freestyle projects.

Changelog

Version 1.1 (12/28/2009)
  • Fix help link
Version 1.0 (9/29/2009)
  • Initial release.

Labels:

tier3-hudson-plugin tier3-hudson-plugin Delete
plugin-buildwrapper plugin-buildwrapper Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
  1. Oct 12, 2009

    Stefan Bäumler says:

    Providing environment variables for a build is already realized by the (Hudson c...

    Providing environment variables for a build is already realized by the (Hudson core) job option "This build is parameterized" (see Parameterized Build). What is the difference between your plugin and the core functionality?

    1. Oct 23, 2009

      Stig Kleppe-Jørgensen says:

      If you want a build to start automatically, like from an SCM or a dependency cha...

      If you want a build to start automatically, like from an SCM or a dependency change, you cannot use parameterized builds. Then this plugin is very good to have. In my case, I have some GUI tests that need an X11 display. As I have a cluster, it is very nice to just set the X11 display env.var. with this plugin and not have to do this for every node.

  2. Oct 27, 2009

    Stephen Callaghan says:

    Is it possible to extend this to include "Post Build Actions" as well? Reason be...

    Is it possible to extend this to include "Post Build Actions" as well? Reason being is that we have clear case stream views that change everytime a new stream is created (about once a month). Currently i have to go into every single config area and update the new stream path , for example where the ant script is and in the Post Build in the Archive Area where I want to change where the artifacts will be.

  3. Dec 21, 2009

    Craig Erdmann says:

    I'm attempting to use the plugin to set variables based on other environmental v...

    I'm attempting to use the plugin to set variables based on other environmental variables. i.e.

    CONTAINER = $WORKSPACE\container

    TempHolder=$WORKSPACE\temp

    Artifacts=$TempHolder/artifacts

    How should I do this?

    Thanks

    1. Dec 22, 2009

      Craig Erdmann says:

      Figured it out: CONTAINER=${WORKSPACE}\\container TEMPHOLDER=${WORKSPACE}\\te...

      Figured it out:

      CONTAINER=${WORKSPACE}\\container
      TEMPHOLDER=${WORKSPACE}\\temp
      ARTIFACTS=${TEMPHOLDER}\\artifacts

      I was missing the braces and double backslash (I'm assuming this is escaped??)

      1. Jan 06, 2010

        Carl Quinn says:

        Try using forward slash instead of double backslash. That should work on Unix as...

        Try using forward slash instead of double backslash. That should work on Unix as well as Windows.
        CONTAINER=$

        Unknown macro: {WORKSPACE}

        /container
        ...

  4. Apr 22, 2010

    Jean-Luc Pinardon says:

    It seems that the plugin cannot be used to pass parameter from an upstream to a ...

    It seems that the plugin cannot be used to pass parameter from an upstream to a downstream job. I mean from a job which triggers another one when it successfully ends.
    Am I true, or have I missed something ?

  5. May 25, 2010

    Phillip Oldham says:

    Its also not possible to create "dynamic" vars - i.e. calculate them at the poin...

    Its also not possible to create "dynamic" vars - i.e. calculate them at the point of creation:

    TAG_ID=`date +%y.%m.%d.$SVN_REVISION`
    

    This would be a very handy feature.

  6. Jul 16, 2010

    Axel Heider says:

    What is the difference to the ToolEnvironment Plugin. It appears both do more or...

    What is the difference to the ToolEnvironment Plugin. It appears both do more or less the same.

  7. Dec 19, 2010

    tim jurik says:

    I am unable to successfully use the env vars I create in the subsequent email.&n...

    I am unable to successfully use the env vars I create in the subsequent email. 

    I try both $VARNAME and "$

    Unknown macro: {VARNAME}

    "

    and neither get substituted.  Am I out of luck with sending the emails?

    (I use this for a single place to set a version number and it works fine int he batch processes but no good in the emails)