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

Inject environment variables for a Job

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      As developer I would like to get the enviroment variables when I'm working with a Job. For that, we have the getEnvironment method, designed for:

      Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job.

      Use case
      1. I'm using a Subversion repository
      2. My repository URL is parametized, for example: https://server/project1/$MODULE
      3. I want to do polling
      Use case
      1. Validate Subversion repositories when its URL is parametized.

      This bug would be solved with this improvement.

        Attachments

          Issue Links

            Activity

            recena Manuel Recena Soto created issue -
            recena Manuel Recena Soto made changes -
            Field Original Value New Value
            Description As developer I would like to get the enviroment variables when I'm working with a {{Job}} and use the {{getEnvironment}} mehtod. This method is designed for:

            bq. Creates an environment variable override for launching processes for this project.
            bq. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job.
            As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for:

            bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job.

            h5. Use case

            # I'm using a Subversion repository
            # My repository URL is parametized, for example: https://server/project1/${BRANCH}
            # I want to do polling



            recena Manuel Recena Soto made changes -
            Description As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for:

            bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job.

            h5. Use case

            # I'm using a Subversion repository
            # My repository URL is parametized, for example: https://server/project1/${BRANCH}
            # I want to do polling



            As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for:

            bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job.

            h5. Use case

            # I'm using a Subversion repository
            # My repository URL is parametized, for example: {{https://server/project1/$MODULE}}
            # I want to do polling



            recena Manuel Recena Soto made changes -
            Summary Injects environment variables for a Job Inject environment variables for a Job
            recena Manuel Recena Soto made changes -
            Description As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for:

            bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job.

            h5. Use case

            # I'm using a Subversion repository
            # My repository URL is parametized, for example: {{https://server/project1/$MODULE}}
            # I want to do polling



            As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for:

            bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job.

            h5. Use case

            # I'm using a Subversion repository
            # My repository URL is parametized, for example: {{https://server/project1/$MODULE}}
            # I want to do polling

            This [bug|https://issues.jenkins-ci.org/browse/JENKINS-29340] would be solved with this improvement.



            recena Manuel Recena Soto made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jglick Jesse Glick made changes -
            Link This issue duplicates JENKINS-29340 [ JENKINS-29340 ]
            recena Manuel Recena Soto made changes -
            Description As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for:

            bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job.

            h5. Use case

            # I'm using a Subversion repository
            # My repository URL is parametized, for example: {{https://server/project1/$MODULE}}
            # I want to do polling

            This [bug|https://issues.jenkins-ci.org/browse/JENKINS-29340] would be solved with this improvement.



            As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for:

            bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job.

            h5. Use case

            # I'm using a Subversion repository
            # My repository URL is parametized, for example: {{https://server/project1/$MODULE}}
            # I want to do polling

            h5. Use case

            # Validate Subversion repositories when its URL is parametized.

            This [bug|https://issues.jenkins-ci.org/browse/JENKINS-29340] would be solved with this improvement.



            recena Manuel Recena Soto made changes -
            Link This issue duplicates JENKINS-29340 [ JENKINS-29340 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is related to JENKINS-29340 [ JENKINS-29340 ]
            recena Manuel Recena Soto made changes -
            Status In Progress [ 3 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 164894 ] JNJira + In-Review [ 197575 ]

              People

              • Assignee:
                recena Manuel Recena Soto
                Reporter:
                recena Manuel Recena Soto
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: