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

Source Code Management senction is not accepting String parameter

    XMLWordPrintable

Details

    Description

      Source Code Management senction is not accepting String parameter
      I am passing string parameter from Python script the value which is not substituting in the file path of the SCM section.
      ex: File Path: /mnt/test_dir/${PARAM}/

      I am able to see the value of the PRAM in the environment variables section. but the value is not substituting in the file path
       

       

      Attachments

        Issue Links

          Activity

            oleg_nenashev Oleg Nenashev added a comment -

            kkirangogula so what is your expectation here?

            oleg_nenashev Oleg Nenashev added a comment - kkirangogula so what is your expectation here?
            kkirangogula Kiran Gogula added a comment -

            As per the design view all plugin should have an access to environment variables that would be more generic. And I have seen the SCM source code, the build parameters are not injected to that. Please let me know that if you can able to make a small change on the same to make sure the build variables should be accessible in SCM section or plugin.

            Please let me know your thought on the above comment.

            kkirangogula Kiran Gogula added a comment - As per the design view all plugin should have an access to environment variables that would be more generic. And I have seen the SCM source code, the build parameters are not injected to that. Please let me know that if you can able to make a small change on the same to make sure the build variables should be accessible in SCM section or plugin. Please let me know your thought on the above comment.
            oleg_nenashev Oleg Nenashev added a comment -

            > As per the design view all plugin should have an access to environment variables that would be more generic.

            It is not a Jenkins design. Each plugin has its own choice whether to handle env vars or not. If you see it mentioned in documentation anywhere, please provide me a link, Then it will be a bug which we would need to fix.

            > And I have seen the SCM source code, the build parameters are not injected to that. Please let me know that if you can able to make a small change...

            As I mentioned above, this small change needs decisions about the behavior in cases when Environment variables do not exist. And it should be a non-breaking behavior (you can see how much fun I had with it in the Perforce plugin).

            You have not responded to my question about the desired behavior yet, in the current state I see no way to iterate on it.

             

             

            oleg_nenashev Oleg Nenashev added a comment - > As per the design view all plugin should have an access to environment variables that would be more generic. It is not a Jenkins design. Each plugin has its own choice whether to handle env vars or not. If you see it mentioned in documentation anywhere, please provide me a link, Then it will be a bug which we would need to fix. > And I have seen the SCM source code, the build parameters are not injected to that. Please let me know that if you can able to make a small change... As I mentioned above, this small change needs decisions about the behavior in cases when Environment variables do not exist. And it should be a non-breaking behavior (you can see how much fun I had with it in the Perforce plugin). You have not responded to my question about the desired behavior yet, in the current state I see no way to iterate on it.    
            kkirangogula Kiran Gogula added a comment -

            My expectation was I need to pass dynamic directory name as a parameter from the python script. And currently I am using the custom plugin so in that case I can not use the pipeline plug in to make my build success.

            kkirangogula Kiran Gogula added a comment - My expectation was I need to pass dynamic directory name as a parameter from the python script. And currently I am using the custom plugin so in that case I can not use the pipeline plug in to make my build success.
            oleg_nenashev Oleg Nenashev added a comment -

            Duplicates JENKINS-7133

            oleg_nenashev Oleg Nenashev added a comment - Duplicates JENKINS-7133

            People

              Unassigned Unassigned
              kkirangogula Kiran Gogula
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: