Jon,

THANK YOU! I got it to work! I appreciate your help very much! Cheers!!

On Monday, July 28, 2014 1:49:31 PM UTC-4, Andrew Pritykin wrote:
>
> So just to clarify, will I be creating a new foo.properties file for each 
> run or add a new value to YVALUE?
>
> On Monday, July 28, 2014 1:47:49 PM UTC-4, Jon Schewe wrote:
>>
>> That's how I use the plot plugin as well. Have your script write 
>> YVALUE=time into the file foo.properties, then configure the plugin to use 
>> the file just like I specified earlier. The plot plugin will keep track of 
>> all of the values for each build internally.
>>
>>
>> On Mon, Jul 28, 2014 at 11:38 AM, Andrew Pritykin <[email protected]> 
>> wrote:
>>
>>> How would I go about using the foo.properties files for what I need.
>>>
>>> Basically my script tests how long it takes to load the webpage, then 
>>> saves the time in a file. I plan to graph the load time for each build in a 
>>> single graph (so we can monitor webpage performance over time).
>>>
>>> I apologize as I am new to all of this and am trying to piece it all 
>>> together.
>>>
>>> On Monday, July 28, 2014 12:33:47 PM UTC-4, Jon Schewe wrote:
>>>
>>>> The "foo.properties" file is created for each build as part of my 
>>>> continuous integration script.
>>>>
>>>>
>>>> On Mon, Jul 28, 2014 at 10:23 AM, Andrew Pritykin <[email protected]> 
>>>> wrote:
>>>>
>>>>> Jon,
>>>>>
>>>>> Is the same file "foo.properties" used for multiple builds? Would I 
>>>>> just continue to add values to YVALUE or create a new file for each 
>>>>> build? 
>>>>> Is it difficult to write to the properties file in Javascript?
>>>>>
>>>>>
>>>>> On Monday, July 28, 2014 11:12:17 AM UTC-4, Jon Schewe wrote:
>>>>>
>>>>>> I have the plot plugin generating plots from some of my test scripts. 
>>>>>> I'm using the properties file format. So for each series that I want to 
>>>>>> graph I create a file that contains YVALUE=<value>. For instance I have 
>>>>>> a 
>>>>>> series named "foo" and I create a file named "foo.properties" that 
>>>>>> contains 
>>>>>> a single line "YVALUE=5". The name of the file and the name of the 
>>>>>> series 
>>>>>> do not need to match. 
>>>>>>
>>>>>> In my configuration I created a plot group "Plots" with a plot title 
>>>>>> "Foo" and a "Plot y-axis label "foo". Then the data configurationhas 
>>>>>> "Data 
>>>>>> series file" is "foo.properties" assuming that the file is at the top of 
>>>>>> my 
>>>>>> workspace. Paths are relative to the workspace directory. Then I check 
>>>>>> the 
>>>>>> radio button "Load data from properties file"
>>>>>>
>>>>>> Note that if you're using a matrix build you will likely have 
>>>>>> problems unless you build your own patched version of the plot plugin.
>>>>>>
>>>>>> An example of picking up my value for the properties file is here:
>>>>>>
>>>>>> cat rse-stats.txt | grep "RSE" | awk '{printf("YVALUE=%f",$1)}' > 
>>>>>> rse-ch0.properties
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 28, 2014 at 9:58 AM, Andrew Pritykin <[email protected]> 
>>>>>> wrote:
>>>>>>
>>>>>>>  Still looking for any help on this problem.
>>>>>>>
>>>>>>> On Wednesday, July 23, 2014 5:22:12 PM UTC-4, Andrew Pritykin wrote:
>>>>>>>>
>>>>>>>> So here is the deal folks,
>>>>>>>>
>>>>>>>> I have a PhantomJS script that simply measures the amount of time 
>>>>>>>> it takes to load a web page (in ms). My plan is to graph the result 
>>>>>>>> (time 
>>>>>>>> taken) on a graph for each build over time.
>>>>>>>>
>>>>>>>> I read about the Plot Plugin and how "easy" it is to plot data on a 
>>>>>>>> graph by using formats like .xml or .csv
>>>>>>>>
>>>>>>>> I currently am able to get my script to save the result (time taken 
>>>>>>>> to load page) to a external .csv file.
>>>>>>>>
>>>>>>>> For Example: 367,8042,567,
>>>>>>>>
>>>>>>>>
>>>>>>>> One of my builds that I am testing this with(using a github repo) 
>>>>>>>> saves the data in the .csv file but Plot Plugin does not seem to plot 
>>>>>>>> the 
>>>>>>>> data. Not sure if its the format of my data or the configuration of 
>>>>>>>> the 
>>>>>>>> plugin.
>>>>>>>>
>>>>>>>>
>>>>>>>> Lastly another way I thought to do this is without a Source Code 
>>>>>>>> Management and just move the script and the .csv file to the workspace 
>>>>>>>> for 
>>>>>>>> that project. The issue I am getting with this project is the script 
>>>>>>>> is 
>>>>>>>> unable to either open or write to the file (possible permission 
>>>>>>>> issues).
>>>>>>>>
>>>>>>>> I am quite desperate to get this "easy" build to work and display 
>>>>>>>> the data. Does anyone have experience doing this and/or help me out to 
>>>>>>>> get 
>>>>>>>> this working. I greatly appreciate it!
>>>>>>>>
>>>>>>>>
>>>>>>>> I will attach the script and a example .csv to this post for people 
>>>>>>>> to get a better understanding. 
>>>>>>>>
>>>>>>>>  
>>>>>>>>
>>>>>>>>  -- 
>>>>>>> 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].
>>>>>>>
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -- 
>>>>>> http://mtu.net/~jpschewe
>>>>>>
>>>>>>   -- 
>>>>> 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].
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>> http://mtu.net/~jpschewe
>>>>
>>>>   -- 
>>> 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].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> http://mtu.net/~jpschewe
>>
>>  

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to