Please file an issue recap'ing as much as data we discussed here and
anything you have in mind that help reproduce it. I don't have a Windows
agent handy, so will have to do that later.

Thanks

2016-12-02 20:31 GMT+01:00 PJ <[email protected]>:

> Thanks for your response.
>
> 1. ALL CAPS did not work.
> 2. Tested with a Linux agent and it works fine.
> 3. I checked that page on a Linux agent and yes its as you mentioned.
>
> I still cannot get it to work on a windows agent though. Thanks again for
> your help with this.
>
> On Friday, December 2, 2016 at 3:28:32 AM UTC-8, Baptiste Mathus wrote:
>>
>> Hi,
>>
>> I've just given it a quick shot. Initially I thought this might be
>> something related to SECURITY-170
>> <https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170>,
>> but as the param is explicit, it shouldn't.
>>
>> Testing locally on a 2.19.3, it works fine with or without space after %.
>> So, as I'm testing with Linux, it may be something specific with Windows
>> (your use case).
>>
>> So, could you please see the following and get back with results here:
>>
>>    - check with ALL CAPS for you variable name, maybe something related
>>    to case insensitivity under Windows, wild guessing here
>>    - check if possible with a linux agent to see if you're able to make
>>    it work there. It will help triage if this is windows specific or not.
>>    - Also, please check the build page (http://yourinstance/job/YOURJ
>>    OB/9/ e.g.), you should see something like, if not, this is not even
>>    the plugin who triggered your job, so might also explain why the variable
>>    is absent:
>>
>> [image: Images intégrées 1]
>>
>> Thanks
>>
>> 2016-12-01 18:38 GMT+01:00 PJ <[email protected]>:
>>
>>> Thanks for getting back to me. I tried this by removing the default
>>> value of the Parameter. Attached is the full job, all I am doing is
>>> echo'ing the parameter. I added a space after the % like you mentioned but
>>> that did not fix it either.
>>> Am I missing something?
>>>
>>> On Wednesday, November 30, 2016 at 3:01:10 PM UTC-8, Baptiste Mathus
>>> wrote:
>>>>
>>>> (moving it to the users mailing list, please use this list for users
>>>> related question)
>>>>
>>>> Hi, I don't see the link between your first and second screenshot, not
>>>> the same parameter names. Also, please make sure there's a space after the
>>>> %. I didn't double check the code, but the documentation generally shows it
>>>> this way.
>>>>
>>>> If it's confirmed to be "only" this, BTW, I'll welcome you to file an
>>>> issue in the tracker since this seems a useless usability issue and I'd
>>>> happily improve it.
>>>>
>>>> Thanks
>>>>
>>>> 2016-11-30 23:46 GMT+01:00 PC <[email protected]>:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have installed this plugin and am trying to use it. This plugin is
>>>>> exactly what I need, as I need to to schedule multiple builds with
>>>>> different parameters at each build.
>>>>>
>>>>> For some reason, the build is not triggering at the scheduled periods.
>>>>> I tried various schedules. Attached are the screenshots from my sample 
>>>>> job.
>>>>>
>>>>> Thanks,
>>>>> Pragya
>>>>>
>>>>>
>>>>>
>>>>> On Thursday, November 19, 2015 at 2:31:41 PM UTC-8, Baptiste Mathus
>>>>> wrote:
>>>>>>
>>>>>> Plugin released, any feedback welcome: https://wiki.jenkins-
>>>>>> ci.org/display/JENKINS/Parameterized+Scheduler+Plugin
>>>>>>
>>>>>> 2015-11-18 6:22 GMT+01:00 Baptiste Mathus <[email protected]>:
>>>>>>
>>>>>>> OK, as we've tested it successfully, I'm going to fork it.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> 2015-11-17 11:14 GMT+01:00 Baptiste Mathus <[email protected]>:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Note: this is *not* a fork request.
>>>>>>>>
>>>>>>>> Just an email here to get potential feedback about that plugin [1].
>>>>>>>> I've already gotten some feedback from Daniel [2] and agreement from 
>>>>>>>> the
>>>>>>>> original author to take ownership [3].
>>>>>>>>
>>>>>>>> This plugin adds a new trigger field which basically lets you plan
>>>>>>>> simply many parameterized executions using the typical cron format + an
>>>>>>>> additional list of parameters values.
>>>>>>>>
>>>>>>>> Example :
>>>>>>>>
>>>>>>>> */10 * * * * % param=X
>>>>>>>> */15 * * * * % param=Y
>>>>>>>> H * * * * [here it will execute with default values]
>>>>>>>>
>>>>>>>>
>>>>>>>> If you think this plugin is interesting, or is actually a bad idea,
>>>>>>>> please say it here!
>>>>>>>>
>>>>>>>> Depending on the feedback, I may fork it quite soon, in the next
>>>>>>>> few days.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> [1] https://github.com/jwmach1/parameterized-scheduler
>>>>>>>> [2] https://issues.jenkins-ci.org/browse/JENKINS-16352
>>>>>>>> [3] https://github.com/jwmach1/parameterized-scheduler/issues/1
>>>>>>>>
>>>>>>>> --
>>>>>>>> Baptiste
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Baptiste <Batmat> MATHUS - http://batmat.net
>>>>>>> Sauvez un arbre,
>>>>>>> Mangez un castor !
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Baptiste <Batmat> MATHUS - http://batmat.net
>>>>>> Sauvez un arbre,
>>>>>> Mangez un castor !
>>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Jenkins Developers" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to [email protected].
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/db675dd5-e97
>>>>> 8-4a62-9c38-794ee90966e1%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/db675dd5-e978-4a62-9c38-794ee90966e1%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS79hwdY7HoV2X5FfwbmDCZmPgrvEBOna0s7C1gi-%2B096g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to