Log Parser Plugin Parser Rules Questions

[Bubunia Patra]

Hi ,

I want to use Log Parser Plugin with the following regular expression to be 
matched in the Jenkins console log.


Test case [id] failed
Test case [id] failed
Test case [id] failed


Finished all tests. Executed [id], pass [id], fail [id]

One more thing is I want to get the contents of Error/Info etc in to a 
table and send across via email? Can I access through groovy script?

 Can anyone help me in this regard?

Regards
Pradeep

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2554efff-53c9-49b2-ab84-d07206735b01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Monitoring network folder using FSTrigger plugin

[Ram D]

Hi Mark,

Thanks, I realized it soon enough. But thought mounting is was just a
workaround for this query.
Your answer showed me that is just the only solution available.

Regards,
Ramesh


On Sat, Oct 15, 2016 at 5:18 PM, Mark Waite 
wrote:

> http://superuser.com/questions/344775/passing-unc-
> username-and-password-within-a-unc-path suggests that there is no syntax
> which will allow you to embed the username and password in the network
> path.  You might need to assure that network path is already mounted on
> your Windows agents.  You could attach a label to Windows agents which have
> it mounted, then restrict the job to only run on those labels.
>
> Mark Waite
>
> On Sat, Oct 15, 2016 at 4:32 AM Ram D  wrote:
>
>> Anyone 
>> Is it at-least possible???
>>
>> On Fri, Oct 14, 2016 at 7:06 PM, Ram D  wrote:
>>
>> Hi All,
>>
>> Greetings!
>> Use case: I have to monitor (polling folder) a network folder for build
>> artifacts (.zip files). When ever there is new .zip file I have to copy it
>> and trigger downstream builds.
>>
>> Solution: FSTrigger plugin - seems to do the work of polling folder and
>> and if changes present in target, build is triggered.
>>
>> Question: How do I provide a network path for polling which requires
>> username and password to access it. e.g.
>> *\\100.1.1.1\abc\pqr\xyz\pqr\*.zip*
>>
>> If I open this in file system explorer it asks for username (with domain)
>> and password in order to open it. How to pass such parameters in
>> FSTrigger plugin.
>>
>> More info: https://wiki.jenkins-ci.org/display/JENKINS/FSTrigger+Plugin
>>
>> Any help or suggestions appreciated.
>>
>> Regards,
>> Ramesh
>>
>>
>> --
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/jenkinsci-users/CAAyu-G66gDG6QwjwXbMaTfO9OV5d0PibDeU
>> bhtWZYWaktEgEXQ%40mail.gmail.com
>> 
>> .
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/CAO49JtGQvUDLrgs8PnwWXXs-
> oy0Tjp%3DEqNTUoPwNcQDc7i7kGA%40mail.gmail.com
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAAyu-G6sJ%2BGAw4dzNMBzw-sVySYS6JxG21cKhzpCBs5bmWH8GA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - groovy - file paths on windows?

[Jonathan Hodgson]

Rachel and Martina,

Thanks for trying to help me on this, I've started a new thread now that 
I've realized the issue isn't to do with windows or paths, but rather to do 
with slaves and masters.

On Monday, October 17, 2016 at 11:27:08 PM UTC+1, Jonathan Hodgson wrote:
>
> Well I can confirm that it has nothing to do with it being windows, just 
> tried FileNameFinder on my OSX slave and it also looks on the master
>
> On Monday, October 17, 2016 at 9:44:03 PM UTC+1, Jonathan Hodgson wrote:
>>
>> But I don't want to restrict where the job runs, just where the node runs.
>>
>> I have code that needs to run on the master, and code that needs to run 
>> on the slaves.
>>
>> The code is running in the correct places, I can for example do a 
>> mercurial checkout on the slaves, I can also run batch files on the slaves, 
>> and visual studio (or I could, that bit's disabled as I'm working on this, 
>> but it worked before).
>>
>> Buildsteps do what they should, on the slave
>>
>> but groovy file commands don't.
>>
>> On Monday, October 17, 2016 at 9:19:45 PM UTC+1, Rachel wrote:
>>>
>>> Hi Jonathan,
>>>
>>> According to master and slave systems you have, I think you might use 
>>> the option:
>>>
>>>- "*Restrict where this project can be run*"
>>>
>>> in your job configuration (located in General Configuration), in order *to 
>>> force job execution on slave*.
>>>
>>> I hope be useful.
>>>
>>> Best regards,
>>> Rachel
>>>
>>>
>>> El lunes, 17 de octubre de 2016, 22:07:09 (UTC+2), Jonathan Hodgson 
>>> escribió:



 On Monday, October 17, 2016 at 8:36:55 PM UTC+1, Martina wrote:
>
> So you solved the issue of it running on the wrong system, right?
>

 No, I haven't solved the issue.

 I thought perhaps it was running on the wrong system because it didn't 
 have an absolute path that it recognized as such, so I was trying to see 
 if 
 there was a path syntax which made it look locally, so far, no luck

 Well, all the "does not exist" messages have a leading /.
> Not sure where that comes from, but I'm pretty sure that that is what 
> it is complaining about. Also, looking at FileNameFinder, all examples 
> are 
> it finding files, not directories, but examples are clearly using 
> c:/path/path syntax.
> I'm thinking you may want to try changing up your wildcard to 
> something like '**/*.xml' or '**/*.txt', whatever you actually have on 
> that 
> file system.
>
> FilenameFinder works as expected on the master, but not on the slave. 
 It doesn't matter what my wildcard is, it always looks on the master. The 
 same goes for File... which seems to be the complete opposite of what the 
 documentation on File and FilePath says. If I understand that correctly, 
 File is always supposed to look on the current machine (i.e. the one that 
 node is running on) and so to access stuff on the master you have to use 
 FilePath




-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/453dd417-9f6d-487f-9ff0-c0140bcdee28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline : Confused about file access on slaves

[Jonathan Hodgson]

Hi,

I've touched on this stuff in a previous thread where I thought it was 
about running on Windows, in turns out it's the same for any slave

So I'm starting a new thread now I'm clearer what the issue is

I have code that basically works like this

node('master') {  // Master is running Linus
SET_STUFF_UP
}   
platform_builders ["Mac"] = {
node ("XCode")
{
BUILD_STUFF_ON_OSX
}
}
platform_builders ["Windows"] = { 
node ("VS2013")
{
BUILD_STUFF_ON_WINDOWS
}
}
parallel(platform_builders)


So, pretty standard.

Now what I don't understand is what I get when I try to access files.

In SET_STUFF_UP jenkins Buildsteps that access files (checkouts, DeleteDir, 
etc) operate on the master (as expected) and Groovy's standard file 
handling classes (File, FileNameFinder etc) also act on the master... so 
that's all fine

but in BUILD_STUFF_IN_OSX and BUILD_STUFF_IN_WINDOWS buildsteps operate on 
files on the slaves (as expected) while Groovy standard classes operate on 
the master.

1) Is this expected? The documentation says that File operates on "the 
current machine", which I took to mean the one actually running the code at 
that moment, which is the slave. But that isn't hwat is happening

2) How do I get around it? Buildsteps just don't provide the functionality 
I need, and doing stuff in shell scripts and batch files (which works as 
expected) is really clunky.

 

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f314bd0d-7fea-469e-8616-8ad60ce1885f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - groovy - file paths on windows?

[Jonathan Hodgson]

Well I can confirm that it has nothing to do with it being windows, just 
tried FileNameFinder on my OSX slave and it also looks on the master

On Monday, October 17, 2016 at 9:44:03 PM UTC+1, Jonathan Hodgson wrote:
>
> But I don't want to restrict where the job runs, just where the node runs.
>
> I have code that needs to run on the master, and code that needs to run on 
> the slaves.
>
> The code is running in the correct places, I can for example do a 
> mercurial checkout on the slaves, I can also run batch files on the slaves, 
> and visual studio (or I could, that bit's disabled as I'm working on this, 
> but it worked before).
>
> Buildsteps do what they should, on the slave
>
> but groovy file commands don't.
>
> On Monday, October 17, 2016 at 9:19:45 PM UTC+1, Rachel wrote:
>>
>> Hi Jonathan,
>>
>> According to master and slave systems you have, I think you might use the 
>> option:
>>
>>- "*Restrict where this project can be run*"
>>
>> in your job configuration (located in General Configuration), in order *to 
>> force job execution on slave*.
>>
>> I hope be useful.
>>
>> Best regards,
>> Rachel
>>
>>
>> El lunes, 17 de octubre de 2016, 22:07:09 (UTC+2), Jonathan Hodgson 
>> escribió:
>>>
>>>
>>>
>>> On Monday, October 17, 2016 at 8:36:55 PM UTC+1, Martina wrote:

 So you solved the issue of it running on the wrong system, right?

>>>
>>> No, I haven't solved the issue.
>>>
>>> I thought perhaps it was running on the wrong system because it didn't 
>>> have an absolute path that it recognized as such, so I was trying to see if 
>>> there was a path syntax which made it look locally, so far, no luck
>>>
>>> Well, all the "does not exist" messages have a leading /.
 Not sure where that comes from, but I'm pretty sure that that is what 
 it is complaining about. Also, looking at FileNameFinder, all examples are 
 it finding files, not directories, but examples are clearly using 
 c:/path/path syntax.
 I'm thinking you may want to try changing up your wildcard to something 
 like '**/*.xml' or '**/*.txt', whatever you actually have on that file 
 system.

 FilenameFinder works as expected on the master, but not on the slave. 
>>> It doesn't matter what my wildcard is, it always looks on the master. The 
>>> same goes for File... which seems to be the complete opposite of what the 
>>> documentation on File and FilePath says. If I understand that correctly, 
>>> File is always supposed to look on the current machine (i.e. the one that 
>>> node is running on) and so to access stuff on the master you have to use 
>>> FilePath
>>>
>>>
>>>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3bb3377a-dfbe-44b6-b33d-29329515b5f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - groovy - file paths on windows?

[Jonathan Hodgson]

But I don't want to restrict where the job runs, just where the node runs.

I have code that needs to run on the master, and code that needs to run on 
the slaves.

The code is running in the correct places, I can for example do a mercurial 
checkout on the slaves, I can also run batch files on the slaves, and 
visual studio (or I could, that bit's disabled as I'm working on this, but 
it worked before).

Buildsteps do what they should, on the slave

but groovy file commands don't.

On Monday, October 17, 2016 at 9:19:45 PM UTC+1, Rachel wrote:
>
> Hi Jonathan,
>
> According to master and slave systems you have, I think you might use the 
> option:
>
>- "*Restrict where this project can be run*"
>
> in your job configuration (located in General Configuration), in order *to 
> force job execution on slave*.
>
> I hope be useful.
>
> Best regards,
> Rachel
>
>
> El lunes, 17 de octubre de 2016, 22:07:09 (UTC+2), Jonathan Hodgson 
> escribió:
>>
>>
>>
>> On Monday, October 17, 2016 at 8:36:55 PM UTC+1, Martina wrote:
>>>
>>> So you solved the issue of it running on the wrong system, right?
>>>
>>
>> No, I haven't solved the issue.
>>
>> I thought perhaps it was running on the wrong system because it didn't 
>> have an absolute path that it recognized as such, so I was trying to see if 
>> there was a path syntax which made it look locally, so far, no luck
>>
>> Well, all the "does not exist" messages have a leading /.
>>> Not sure where that comes from, but I'm pretty sure that that is what it 
>>> is complaining about. Also, looking at FileNameFinder, all examples are it 
>>> finding files, not directories, but examples are clearly using c:/path/path 
>>> syntax.
>>> I'm thinking you may want to try changing up your wildcard to something 
>>> like '**/*.xml' or '**/*.txt', whatever you actually have on that file 
>>> system.
>>>
>>> FilenameFinder works as expected on the master, but not on the slave. It 
>> doesn't matter what my wildcard is, it always looks on the master. The same 
>> goes for File... which seems to be the complete opposite of what the 
>> documentation on File and FilePath says. If I understand that correctly, 
>> File is always supposed to look on the current machine (i.e. the one that 
>> node is running on) and so to access stuff on the master you have to use 
>> FilePath
>>
>>
>>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/22e776a8-7c2a-44a4-98a9-5b5883889e01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Master Goes to 100% (at random?)

[Eric Crahen]

Hi,

  We're running Jenkins master with a bunch of slaves. Typical load on the
master is around 5-10% which is not very much. Several times now, we've
gotten into spikes where the CPU goes to 100% and stays there until we
restart it, and this usually only helps a little.

  We dump the stack, and typically we find a whole bunch of threads sitting
there marshaling XML aggressively. Usually, we can connect this to a plugin
via the stack trace, and we'll uninstall that plugin, and that tends to
help.

  So far, the plugins I can remember include:

* audit-trail
* build-timer
* log-parser

  That's just the most recent ones that I can remember. We must be going on
the 5th or 6th plugin now. I'm afraid it's starting to shake peoples
confidence in Jenkins, I'd rather not have to replace it with a different
build system because it generally works, but when it doesn't - it's bad. We
actually keep a CircleCI system around because we haven't been able to
build enough confidence in Jenkins.

  I have a couple general questions:

  1) We're on Jenkins 2.18 - so, why does this keep happening? We've seen
other bugs about threads getting stuck hammering the CPU. Seems like the
issues were marked as resolved, but we end up having to uninstall these
plugins all together.

  2) Is there a list of known "bad" plugins?

  3) Why not cache more and guard against this? It's easy to blame the
plugins as the thing triggering this, but why not make Jenkins core more
resilient to this, and assume people can't/won't write perfect plugins?
Getting to be a fool me once type of situation here


-- 
- Eric

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPyj2qEQ8Ych%2B6%3DDd71QVwR%2B0nkPY%3D3t9r%3DyKWE6YeUVUd9Y8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - groovy - file paths on windows?

[Rachel]

Hi Jonathan,

According to master and slave systems you have, I think you might use the 
option:

   - "*Restrict where this project can be run*"

in your job configuration (located in General Configuration), in order *to 
force job execution on slave*.

I hope be useful.

Best regards,
Rachel


El lunes, 17 de octubre de 2016, 22:07:09 (UTC+2), Jonathan Hodgson 
escribió:
>
>
>
> On Monday, October 17, 2016 at 8:36:55 PM UTC+1, Martina wrote:
>>
>> So you solved the issue of it running on the wrong system, right?
>>
>
> No, I haven't solved the issue.
>
> I thought perhaps it was running on the wrong system because it didn't 
> have an absolute path that it recognized as such, so I was trying to see if 
> there was a path syntax which made it look locally, so far, no luck
>
> Well, all the "does not exist" messages have a leading /.
>> Not sure where that comes from, but I'm pretty sure that that is what it 
>> is complaining about. Also, looking at FileNameFinder, all examples are it 
>> finding files, not directories, but examples are clearly using c:/path/path 
>> syntax.
>> I'm thinking you may want to try changing up your wildcard to something 
>> like '**/*.xml' or '**/*.txt', whatever you actually have on that file 
>> system.
>>
>> FilenameFinder works as expected on the master, but not on the slave. It 
> doesn't matter what my wildcard is, it always looks on the master. The same 
> goes for File... which seems to be the complete opposite of what the 
> documentation on File and FilePath says. If I understand that correctly, 
> File is always supposed to look on the current machine (i.e. the one that 
> node is running on) and so to access stuff on the master you have to use 
> FilePath
>
>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/41b4d9df-3fef-4c44-a880-309b6c13d2c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins automate tests and send mail with the version of application

[Sam K]

Can you use curl to get the version info, store it into a variable and pass 
it to the jenkins job?

On Monday, October 17, 2016 at 12:45:15 PM UTC-7, Rafael Silva wrote:
>
>
> Hi !
>
> I use Jenkins to automate my tests and send me an email with the report 
> and it's fine.
>
> But my website has a number of new version by week, and I want send this 
> information with the email
>
>
> My site has the version on the footer
>
> e.g.
>
> Test Version: 0.1 - Automation 
>
>
> How I take this number?
> It is is very important for my control. 
>
>
> Thank u
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/666c2be5-1bcf-40cf-8602-cf784a40db1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - groovy - file paths on windows?

[Jonathan Hodgson]

On Monday, October 17, 2016 at 8:36:55 PM UTC+1, Martina wrote:
>
> So you solved the issue of it running on the wrong system, right?
>

No, I haven't solved the issue.

I thought perhaps it was running on the wrong system because it didn't have 
an absolute path that it recognized as such, so I was trying to see if 
there was a path syntax which made it look locally, so far, no luck

Well, all the "does not exist" messages have a leading /.
> Not sure where that comes from, but I'm pretty sure that that is what it 
> is complaining about. Also, looking at FileNameFinder, all examples are it 
> finding files, not directories, but examples are clearly using c:/path/path 
> syntax.
> I'm thinking you may want to try changing up your wildcard to something 
> like '**/*.xml' or '**/*.txt', whatever you actually have on that file 
> system.
>
> FilenameFinder works as expected on the master, but not on the slave. It 
doesn't matter what my wildcard is, it always looks on the master. The same 
goes for File... which seems to be the complete opposite of what the 
documentation on File and FilePath says. If I understand that correctly, 
File is always supposed to look on the current machine (i.e. the one that 
node is running on) and so to access stuff on the master you have to use 
FilePath


-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/66009643-6192-4d88-b472-8a594bceebe7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins automate tests and send mail with the version of application

[Rafael Silva]

Hi !

I use Jenkins to automate my tests and send me an email with the report and 
it's fine.

But my website has a number of new version by week, and I want send this 
information with the email


My site has the version on the footer

e.g.

Test Version: 0.1 - Automation 


How I take this number?
It is is very important for my control. 


Thank u

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f7a67da6-aaa6-4b78-ad12-65d9a696906f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Accessing jenkins.model.Jenkins class from Custom Jars in Jenkins env.

[ZT]

Hello,

I have written some custom groovy scripts (bundled as Jars) which need to 
access the class jenkins.model.Jenkins

I have my custom JARS installed into Jenkins and they are loaded properly 
(verified through the Jenkins Script Console). However, When my script 
imports jenkins.model.Jenkins, it fails with a NoClassDef error.

I can see the jenkins core jar in /var/jenkins_home/war/WEB-INF/lib but 
they do not seem to be visible to my scripts. 

I am guessing this is either a classloader or a security restriction. 

Any pointers to resolve this would be appreciated.

Regards,
Rahul

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/52c1baf1-e1fe-4583-ab6a-2a0307e9f37c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - groovy - file paths on windows?

[Martina]

So you solved the issue of it running on the wrong system, right?
Well, all the "does not exist" messages have a leading /.
Not sure where that comes from, but I'm pretty sure that that is what it is 
complaining about. Also, looking at FileNameFinder, all examples are it 
finding files, not directories, but examples are clearly using c:/path/path 
syntax.
I'm thinking you may want to try changing up your wildcard to something 
like '**/*.xml' or '**/*.txt', whatever you actually have on that file 
system.

hth
Martina

On Monday, October 17, 2016 at 12:36:54 PM UTC-6, Jonathan Hodgson wrote:
>
> I've tried every path variation I can think of
>
> def paths = [
> "c:",
> "c:\\",
> "c:\\Jenkins",
> "c:\\Jenkins\\workspace\\",
> "c:\\Jenkins\\workspace\\WPF-TryBuild",
>"c:/",
> "c:/Jenkins",
> "c:/Jenkins/workspace/",
> "c:/Jenkins/workspace/WPF-TryBuild",
> "C:\\",
> "C:\\Jenkins",
> "C:\\Jenkins\\workspace\\",
> "C:\\Jenkins\\workspace\\WPF-TryBuild",
> "C:/",
> "C:/Jenkins",
> "C:/Jenkins/workspace/",
> "C:/Jenkins/workspace/WPF-TryBuild"
> ]
> for (path in paths)
> {
> try {
> def hg_folders = new FileNameFinder().getFileNames(path, '*')
> echo "SUCCESS!! Found $path"
> }
> catch(Exception err) {
> echo "There was a problem finding $path"
> echo err.getMessage()
> }
> }
>
>
> The result is this
>
> [Windows] There was a problem finding c:
> [Windows] /c: does not exist.
>
> [Windows] There was a problem finding c:\
> [Windows] /c: does not exist.
>
> [Windows] There was a problem finding c:\Jenkins
> [Windows] /c:/Jenkins does not exist.
>
> [Windows] There was a problem finding c:\Jenkins\workspace\
> [Windows] /c:/Jenkins/workspace does not exist.
>
> [Windows] There was a problem finding c:\Jenkins\workspace\WPF-TryBuild
> [Windows] /c:/Jenkins/workspace/WPF-TryBuild does not exist.
>
> [Windows] There was a problem finding c:/
> [Windows] /c: does not exist.
>
> [Windows] There was a problem finding c:/Jenkins
> [Windows] /c:/Jenkins does not exist.
>
> [Windows] There was a problem finding c:/Jenkins/workspace/
> [Windows] /c:/Jenkins/workspace does not exist.
>
> [Windows] There was a problem finding c:/Jenkins/workspace/WPF-TryBuild
> [Windows] /c:/Jenkins/workspace/WPF-TryBuild does not exist.
>
> [Windows] There was a problem finding C:\
> [Windows] /C: does not exist.
>
> [Windows] There was a problem finding C:\Jenkins
> [Windows] /C:/Jenkins does not exist.
>
> [Windows] There was a problem finding C:\Jenkins\workspace\
> [Windows] /C:/Jenkins/workspace does not exist.
>
> [Windows] There was a problem finding C:\Jenkins\workspace\WPF-TryBuild
> [Windows] /C:/Jenkins/workspace/WPF-TryBuild does not exist.
>
> [Windows] There was a problem finding C:/
> [Windows] /C: does not exist.
>
> [Windows] There was a problem finding C:/Jenkins
> [Windows] /C:/Jenkins does not exist.
>
> [Windows] There was a problem finding C:/Jenkins/workspace/
> [Windows] /C:/Jenkins/workspace does not exist.
>
> [Windows] There was a problem finding C:/Jenkins/workspace/WPF-TryBuild
> [Windows] /C:/Jenkins/workspace/WPF-TryBuild does not exist.
>
>
> Those paths most certainly do exist, 
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4c3fafce-30a0-4d41-9253-fcdaee3bd84e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - groovy - file paths on windows?

[Jonathan Hodgson]

I've tried every path variation I can think of

def paths = [
"c:",
"c:\\",
"c:\\Jenkins",
"c:\\Jenkins\\workspace\\",
"c:\\Jenkins\\workspace\\WPF-TryBuild",
   "c:/",
"c:/Jenkins",
"c:/Jenkins/workspace/",
"c:/Jenkins/workspace/WPF-TryBuild",
"C:\\",
"C:\\Jenkins",
"C:\\Jenkins\\workspace\\",
"C:\\Jenkins\\workspace\\WPF-TryBuild",
"C:/",
"C:/Jenkins",
"C:/Jenkins/workspace/",
"C:/Jenkins/workspace/WPF-TryBuild"
]
for (path in paths)
{
try {
def hg_folders = new FileNameFinder().getFileNames(path, '*')
echo "SUCCESS!! Found $path"
}
catch(Exception err) {
echo "There was a problem finding $path"
echo err.getMessage()
}
}


The result is this

[Windows] There was a problem finding c:
[Windows] /c: does not exist.

[Windows] There was a problem finding c:\
[Windows] /c: does not exist.

[Windows] There was a problem finding c:\Jenkins
[Windows] /c:/Jenkins does not exist.

[Windows] There was a problem finding c:\Jenkins\workspace\
[Windows] /c:/Jenkins/workspace does not exist.

[Windows] There was a problem finding c:\Jenkins\workspace\WPF-TryBuild
[Windows] /c:/Jenkins/workspace/WPF-TryBuild does not exist.

[Windows] There was a problem finding c:/
[Windows] /c: does not exist.

[Windows] There was a problem finding c:/Jenkins
[Windows] /c:/Jenkins does not exist.

[Windows] There was a problem finding c:/Jenkins/workspace/
[Windows] /c:/Jenkins/workspace does not exist.

[Windows] There was a problem finding c:/Jenkins/workspace/WPF-TryBuild
[Windows] /c:/Jenkins/workspace/WPF-TryBuild does not exist.

[Windows] There was a problem finding C:\
[Windows] /C: does not exist.

[Windows] There was a problem finding C:\Jenkins
[Windows] /C:/Jenkins does not exist.

[Windows] There was a problem finding C:\Jenkins\workspace\
[Windows] /C:/Jenkins/workspace does not exist.

[Windows] There was a problem finding C:\Jenkins\workspace\WPF-TryBuild
[Windows] /C:/Jenkins/workspace/WPF-TryBuild does not exist.

[Windows] There was a problem finding C:/
[Windows] /C: does not exist.

[Windows] There was a problem finding C:/Jenkins
[Windows] /C:/Jenkins does not exist.

[Windows] There was a problem finding C:/Jenkins/workspace/
[Windows] /C:/Jenkins/workspace does not exist.

[Windows] There was a problem finding C:/Jenkins/workspace/WPF-TryBuild
[Windows] /C:/Jenkins/workspace/WPF-TryBuild does not exist.


Those paths most certainly do exist, 

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ba5de980-98e7-4b38-89d5-5bb5bc3a0e82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

concurrency parameter no longer accepted for stage block?

[Kyle Flavin]

I posted this in the wrong place previously - hope this is correct.

Does the concurrency parameter no longer apply to the stage block?  This 
post is in reference to: https://issues.jenkins-ci.org/browse/JENKINS-26107

I have some legacy code, and I'm converting "stage" to use the new block 
format. We have a lot of stuff that looks like this: 


stage name: 's1: do something', concurrency: 1
 ...

stage name: 's2: do something else', concurrency: 1
 ...



I'm not entirely sure what "concurrency" is doing, or if it's even 
necessary to preserve in this case.  I can't find much reference to the new 
form in the docs.  Is it safe to just ignore the parameter?  Is it handled 
in some other way now?:


stage("s1: do something") {
...

}

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8a158100-1eba-4575-92c0-0aa9bbf48cb8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline jobs - Custom build names?

[Sam K]

Is there a way (yet) to name the pipeline build jobs like this using the 
build name setter plugin




instead of what is now currently showing like this:



-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8c7ed46d-5c9d-4a5d-9d68-f62935e8e604%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to write log file error I am getting in Jenkins for build.xml

[chinmoy padhi]

Hi All,

I have resolved the above error with some trial and error but not sure 
whether this is 100% work for others or not, but what I did I am sharing my 
experience.

Steps
--

   1. *service jenkins stop *or *sudo /etc/init.d/jenkins stop*
   2. Make sure all services are stopped. Even u should not be able to 
   access the jenkins url from browser.
   3. check the *rpm -qa|grep jenkins*. It will show your jenkins rpm 
   package.
   4. Run the find / -name jenkins to check where and all jenkins is used.
   
   [root@localhost]# *find / -name "jenkins"*
   /etc/rc.d/init.d/jenkins
   /etc/logrotate.d/jenkins
   /etc/sysconfig/jenkins
   /usr/lib/jenkins
   /var/lib/jenkins
   /var/cache/jenkins
   /var/cache/yum/jenkins
   /var/log/jenkins
   [root@localhost]#
   5. Take backup of */var/lib/jenkins/* folders to */var/lib/jenkins.old* 
   6. 
   
   Now run the *"rpm -e --nodeps jenkins-1.651.3-1.1"* to remove the 
   package.
   7. Repeat Step 4 again and make sure */var/cache/jenkins* and 
   */var/cache/yum/jenkins* are the two directories which remains
   8. Now run *"rpm -ivh /etc/yum.repos.d/jenkins-1.651.3-1.1.noarch.rpm" *to 
   install the jenkins package
   9. Run *"service jenkins start"* so that it will listen on port *8080*
   10. Open the jenkins url with IP and Port.
   11. Create a free-style project with some name and make sure the project 
   should be created in */var/lib/jenkins/jobs*
   12. Configure the necessary steps such as JDK Installation, Ant 
   installations etc., in manage jenkins options.
   13. Now run the build for your project without configuring *build.xml* 
   path, so that it will create a workspace folder in 
*/var/lib/jenkins/workspace/*
   14. Now copy the *build.xml* file from existing project and put the file 
   in */var/lib/jenkins/workspace/*
   15. Build project from Jenkins.
   16. Try to resolve script label errors such as it will complain for lib, 
   src folders not found and copy/create those folders to resolve the 
   compilation errors.
   17. Once done with all errors try to run the build again so that you 
   will get Build Successful.
   18. Make sure you copy/create src and lib folder and don't copy/create 
   the target folder.
   19. Make sure target folder must be created automatically by Jenkins 
   with jenkins ownership and jenkins file permission. Rest all may be root 
   owner and root file permission.
   20. Now configure the junit report and email notifications to get the 
   build reports in email.


On Wednesday, 12 October 2016 18:23:59 UTC+5:30, chinmoy padhi wrote:
>
> Hi Google Users,
>
> Need a help on the mentioned subject line.
> I have installed the jenkins using *"rpm -ivh"* command 
> Currently I am running the Jenkins on
> 1. Linux RHEL 5.8 (32-bit)
> 2. java version "1.7.0_79"
> 3. Master mode only
> 4. Jenkins Version 1.651.3
>
> Steps to Execute
> --
> 1. I am trying to run the junit test cases from *build.xml* using 
> Ant(Apache Ant(TM) version 1.9.7 compiled on April 9 2016)
> 2. Same project I am running from Windows 7 for easy debugging using 
> Eclipse for build.xml and other class files.
> 3. I copied the Windows project to Linux path and created a job and 
> workspace in* /var/lib/jenkins/*
> 4. Run the build from Jenkins which required desired configuration and it 
> run perfectly.
> 5. Later I compiled the AllTest.java file from Windows and copied the 
> .java and .class file from windows and copied the respective files to* 
> /var/lib/jenkins/workspace/project/src *folder and .class file to* 
> /var/lib/jenkins/workspace/project/target/class* folder.
> 6. When I build the project again from Jenkins it started to throw error 
> after all my test cases got executed.
> 7. Every time its pointing to Junit task in the build.xml file, I tried to 
> google but didn't get the exact answers.
> 8. When I didn't find any resolution I have removed the jenkins rpm using 
> *"rpm 
> -e"* command. But it didn't removed the jenkins folder from* 
> /var/lib/jenkins *
> 9. Re-installed the same rpm and freshly created new freestyle project but 
> it didn't resolve the same error and again after running all the test cases 
> it throws the error.
>
> Appreciate your help. Please find the attached build.xml
>
> Thanks,
> Chinmoy
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/71def122-c1de-497b-ba55-02c046e56e7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Email ext to send html body in Pipeline

[Slide]

rooturl and build are variables that are put into the binding for the Jelly
and Groovy templating. They can't be used directly.

On Mon, Oct 17, 2016 at 6:34 AM  wrote:

> Hi, Sam I was just wondering if the FILE type could use the token
> replacement like the follwoing:
>
> Jenkins project
>
> into the email body. I tested it on my side just out of curiosity and it
> does not make the token replacement as of writting this.
>
> For those who need it:
> '${JELLY_SCRIPT,template="/tmp/test.jelly"}'  for Jelly template
> or
> '${SCRIPT,template="/tmp/test.template"}'  for groovy template
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/6c33bdf1-5f89-48fe-8fec-64297e85fd65%40googlegroups.com
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVcayMP0JEJryEzDEy%2B_2sxR98Z%2B7jnf%3DP_3-XfcM3QrHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - groovy - file paths on windows?

[Jonathan Hodgson]

I've just done some experimentation, and 

testfile = new File("/tmp/CheckOnServer.txt")
if (testfile.exists())
{
echo "It's looking on the master"
}
else
{
echo "It's not looking on the master"
}



gives

[Pipeline] [Windows] echo[Windows] It's looking on the master



Now [Windows] is my slave (the master is a linux machine), but, as the 
message says, that file it is finding is on the master.

Paths seem to be failing because it's starting in the wrong place.


On Monday, October 17, 2016 at 3:44:39 PM UTC+1, Martina wrote:
>
> What exactly is the value of ${source_folder_name} that is in the message?
> C:/some-dir/some-other-name should definitely work.
>
> Martina
>>
>>   
>>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/61d38fe8-e800-44cf-a2e4-3560997c196e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

emailext jelly template access changetSet

[jerome]

Hi,
I have use the Jelly template to re enable most of our email content, 
except 2 things I still cannot do, the revision change set and the warnings 
counts (the later is not too bad, we are moving to warnings as errors 
anyway).

Any body have a way to access the scm changeSet into the pipeline emailext 
template?

I tried without any luck:

   - ${build.changeSet}
   - ${build.changeSets}
   - ${currentBuild.changeSets}
   - ${manager.build.changeSets}
   - ${manager.build.changeSet}
   
the console log are accessible with ${build.getLog()}
the artifacts are with ${build.artifacts}

The warning were:
${WARNINGS_RESULT()}
${WARNINGS_COUNT()}
${WARNINGS_NEW()}
${WARNINGS_FIXED()}

but now if used they generate a jelly parsing error.

if any body have any tips or info on this I would be glad,
Thanks
Jerome

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/05c11b76-e9a9-4fe7-ab19-94410a2d0708%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - groovy - file paths on windows?

[Martina]

What exactly is the value of ${source_folder_name} that is in the message?
C:/some-dir/some-other-name should definitely work.

Martina
>
>   
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4a99a741-43c8-41d7-983c-424f1d514f58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Collecting Workflow Run Info in Pipeline

[Zack Sampson]

Hey,

I'm trying to write a Pipeline job to generate a daily summary of my 
pipeline runs from the preceding day. I've figured out that in a 
non-sandboxed, non-CPS block I can get at the hudson instance and from 
there find the jobs/runs, but I can't find out how to get to the "stage X 
took Y minutes" data.

Has anyone done this before? Do you know where that data lives within 
WorkflowRun?

Thanks,
- Zack

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2f5dec60-89d9-4008-874f-95773aef2e29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: moving hotfixes along a parallel SDLC

[Guy Matz]

Yeah, sorry, I'm not actually suggesting bumping version #s is the way to
go . . .  I was hoping that maybe I was approaching the problem the wrong
way, and that someone had a better idea.  Thanks!!

On Mon, Oct 17, 2016 at 10:00 AM, 'Björn Pedersen' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Hi,
>
> It could be done, but think about using  a better versioning scheme.
> Using build numbers  from different jobs seems like a way to ask for
> trouble.
>
> Take a look at:
>   https://wiki.jenkins-ci.org/display/JENKINS/Version+Number+Plugin
>   https://wiki.jenkins-ci.org/display/JENKINS/semantic-versioning-plugin
>   https://wiki.jenkins-ci.org/display/JENKINS/Next+Build+Number+Plugin
>
> Björn
>
>
> Am Montag, 17. Oktober 2016 15:44:25 UTC+2 schrieb Guy Matz:
>>
>> Hello!  I need to be able to bump version numbers between two different
>> jobs, meaning that if job A runs, it should have a build number higher that
>> job B, and if job B runs, it should have a build # higher than job A . . .
>>  for example, job A may run 10 ten times and have a build number of 10.
>> Then job B will run and needs a build # of 11.  Job A wight run after than
>> and needs a build # of 12.
>>
>> Anyone know how to do this?  I *think* I need this because I am going to
>> have parallel tracks in my SDLC:  my usual develop -> master and a new
>> hotfix -> master SDLC being build by a separate job.  Do I need this?  Any
>> better ideas out there?  This seems like a common enough problem that it's
>> already been solved six ways to sunday . . .
>>
>> Thanks a lot,
>> Guy
>>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/ff35676e-c537-493d-ab45-62a5ce42ca8f%40googlegroups.
> com
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CABnTgtWcTbM%2B4UKXifEmAo1TWDZr8jWny9W%2BgJ817iFpgvhg3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - groovy - file paths on windows?

[Jonathan Hodgson]

On Saturday, October 15, 2016 at 6:05:45 PM UTC+1, Rachel wrote:
>
> Hi Jonathan,
>
> You might check:
>
>- When it's said "Source folder  does not exist", check that 
> really exists and it's right.
>- Jenkins process on slave has permissions on that path.
>
> I hope be useful.
>
> Best regards,
> Rachel
>
>
>>
Hi Rachel,

It certainly does exist.

Looking at the documentation, it seems that paths like "C:" should work, 
but they don't seem to.

Perhaps there is some subtlety about the path syntac that I'm missing?

  

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cb050e62-f21e-47d9-8d03-3de4af540d65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: moving hotfixes along a parallel SDLC

['Björn Pedersen' via Jenkins Users]

Hi,

It could be done, but think about using  a better versioning scheme.  Using 
build numbers  from different jobs seems like a way to ask for trouble.

Take a look at:
  https://wiki.jenkins-ci.org/display/JENKINS/Version+Number+Plugin
  https://wiki.jenkins-ci.org/display/JENKINS/semantic-versioning-plugin
  https://wiki.jenkins-ci.org/display/JENKINS/Next+Build+Number+Plugin

Björn

Am Montag, 17. Oktober 2016 15:44:25 UTC+2 schrieb Guy Matz:
>
> Hello!  I need to be able to bump version numbers between two different 
> jobs, meaning that if job A runs, it should have a build number higher that 
> job B, and if job B runs, it should have a build # higher than job A . . . 
>  for example, job A may run 10 ten times and have a build number of 10.  
> Then job B will run and needs a build # of 11.  Job A wight run after than 
> and needs a build # of 12.
>
> Anyone know how to do this?  I *think* I need this because I am going to 
> have parallel tracks in my SDLC:  my usual develop -> master and a new 
> hotfix -> master SDLC being build by a separate job.  Do I need this?  Any 
> better ideas out there?  This seems like a common enough problem that it's 
> already been solved six ways to sunday . . .
>
> Thanks a lot,
> Guy
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ff35676e-c537-493d-ab45-62a5ce42ca8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

moving hotfixes along a parallel SDLC

[Guy Matz]

Hello!  I need to be able to bump version numbers between two different
jobs, meaning that if job A runs, it should have a build number higher that
job B, and if job B runs, it should have a build # higher than job A . . .
 for example, job A may run 10 ten times and have a build number of 10.
Then job B will run and needs a build # of 11.  Job A wight run after than
and needs a build # of 12.

Anyone know how to do this?  I *think* I need this because I am going to
have parallel tracks in my SDLC:  my usual develop -> master and a new
hotfix -> master SDLC being build by a separate job.  Do I need this?  Any
better ideas out there?  This seems like a common enough problem that it's
already been solved six ways to sunday . . .

Thanks a lot,
Guy

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CABnTgtW%2B5xy_TrSsT4-W8vu3wEeCYgAww_LhuTCXCXS9Bs8nWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Email ext to send html body in Pipeline

[jerome]

Hi, Sam I was just wondering if the FILE type could use the token 
replacement like the follwoing:

Jenkins project

into the email body. I tested it on my side just out of curiosity and it 
does not make the token replacement as of writting this.

For those who need it:
'${JELLY_SCRIPT,template="/tmp/test.jelly"}'  for Jelly template
or
'${SCRIPT,template="/tmp/test.template"}'  for groovy template

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6c33bdf1-5f89-48fe-8fec-64297e85fd65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UI is not visible during execution when running jobs from Jenkins as service

[Victor Martinez]

If you Google a bit you can find the below answer:  
http://stackoverflow.com/questions/10177708/jenkins-on-windows-and-gui-tests-without-rdc/20295828#20295828

Using jnlp might help too

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/508c10dc-471d-47d1-be0f-db59e4d530b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - keep build forever

[roman . pickl]

created https://issues.jenkins-ci.org/browse/JENKINS-39028

please update as you see fit.
best,
Roman

Am Montag, 17. Oktober 2016 09:12:18 UTC+2 schrieb Baptiste Mathus:
>
> Hey,
>
> You need to have an account on the Jenkins infra.
> You can create one going on accounts.jenkins.io
>
> Then create a Jira issue in issues.jenkins-ci.org
>
> Cheers!
>
> Le 16 oct. 2016 9:42 PM,  a écrit :
>
>> works.
>>
>> How to file an RFE?
>>
>> best,
>> Roman
>>
>> Am Freitag, 14. Oktober 2016 07:59:54 UTC+2 schrieb Daniel Beck:
>>>
>>>
>>> > On 13.10.2016, at 13:18, roman...@fluidtime.com wrote: 
>>> > 
>>> > Is there any possibility to keep a build forever programmatically 
>>> after submitting an input approval step? 
>>>
>>> currentBuild.rawBuild.keepLog(true) should do this. 
>>>
>>> This requires sandbox script approval. 
>>>
>>> Should probably be exposed for 'currentBuild' and allowed in the 
>>> sandbox, so please file an RFE. 
>>>
>>> -- 
>> 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 jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/85a87a4c-e5e6-4056-ba80-36ed1470cfae%40googlegroups.com
>>  
>> 
>> .
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1e179ff2-8a7c-412b-911c-64bfc8df0d76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Pipeline with custom class does hang forever

[thomas . lehmann]

Yeah ... found out that too ... "Thread dumps" link in Jenkins job has 
shown the multiplle calls.
Wasn't aware of the property cabability.

Thank you

On Monday, October 17, 2016 at 10:50:39 AM UTC+2, Daniel Beck wrote:
>
> > def setMessage(String message) { 
> > this.message = message 
> > } 
>
> This looks like a potential infinite loop, because Groovy allows calling 
> setters by just setting the property. Probably something getting messed up 
> in one of the Groovy transformations (because this is supposed to only 
> happen for fields without access modifier, and only outside the class[1]). 
>
> Try this: 
>
> > this.@message = message 
>
> Or just skip the getters/setters while you don't need them. 
>
> 1: http://groovy-lang.org/objectorientation.html#properties 
>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/358437a9-d3e0-4814-935c-6a028809b96a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Pipeline with custom class does hang forever

[thomas . lehmann]

Hi,

I were trying to write custom class in Jenkinsfile.

With following example the JOb does hang after the line "echo hi:2". I have 
to click to abort the build and then click twice
on provided links in the Jenkins Console to fully cancel it. On our server 
- even after kill - Jenkins remains 200 and more percentage of CPU.
We were forced to shutdown the Service and to restart. Locally I'm running 
Jenkins inside a Docker container. No CPU problems there.
I'm using a 2.8 and on our server we have a 2.23.

The Console output looks like this:

hi:2
Aborted by Thomas Lehmann 

Click here to forcibly terminate running steps 


Terminating node

Click here to forcibly kill entire build 


Hard kill!
Finished: ABORTED


And ideas?

Kind Regards,
Thomas

class Project implements Serializable {
static final serialVersionUID = 1L

private String message = ""

def setMessage(String message) {
this.message = message
}

def getMessage() {
return this.message
}
}

node {
echo "hi:1"
def project = new Project()

stage("Using a class") {
echo "hi:2"
project.setMessage("some message")
echo "hi:3"
echo project.getMessage()
echo "hi:4"
}
}



-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/48fca903-6d35-4852-ade9-38688f2663f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UI is not visible during execution when running jobs from Jenkins as service

[Ranjit kumar Kundu]

Hi Victor,

The problem I an  facing is I have configure my selenium project with 
Jenkins which is installed as a service in my remote server . The execution 
is running fine. But I cant see any browser opening. everything  is running 
headless. 

OS -  Windows server 2012 R2 Standard 

Jenkins - 1.658



On Saturday, 15 October 2016 15:27:57 UTC+5:30, Victor Martinez wrote:
>
> If you need help it is worth provide more details otherwise the community 
> won't be able to understand your question/issue.
>
> The Jenkins mailing list page (https://jenkins.io/content/mailing-lists/) 
> suggests the below reference:
>
> http://www.catb.org/esr/faqs/smart-questions.html
>
> Besides of that, an initial suggested starting point is to review those 
> log output files:
>
> https://wiki.jenkins-ci.org/display/JENKINS/Logging
>
> Cheers
>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/82c0fd6d-50ae-43f3-b7cc-81db3795895f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline - keep build forever

[Baptiste Mathus]

Hey,

You need to have an account on the Jenkins infra.
You can create one going on accounts.jenkins.io

Then create a Jira issue in issues.jenkins-ci.org

Cheers!

Le 16 oct. 2016 9:42 PM,  a écrit :

> works.
>
> How to file an RFE?
>
> best,
> Roman
>
> Am Freitag, 14. Oktober 2016 07:59:54 UTC+2 schrieb Daniel Beck:
>>
>>
>> > On 13.10.2016, at 13:18, roman...@fluidtime.com wrote:
>> >
>> > Is there any possibility to keep a build forever programmatically after
>> submitting an input approval step?
>>
>> currentBuild.rawBuild.keepLog(true) should do this.
>>
>> This requires sandbox script approval.
>>
>> Should probably be exposed for 'currentBuild' and allowed in the sandbox,
>> so please file an RFE.
>>
>> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/85a87a4c-e5e6-4056-ba80-36ed1470cfae%40googlegroups.
> com
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS53TkE6mUrR5KJR17LQ4ty0Swine0TvL6d%2B5x-Dbem_Vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.