Re: Which release of Jenkins can I safely use? -- problem now solved, I hope

[Slide]

Your messages are getting through, sometimes it can take more than a
day to get a response.

Thanks,

slide

On Thu, Jul 19, 2012 at 10:54 PM, Sarah Woodall
 wrote:
> I've just looked again at the Jenkins website, and I find that there is now
> a release candidate available. I have downloaded the jenkins.war and
> installed it, and my multi-configuration jobs do now load from disk,
> apparently correctly. So I can use it!
>
> This version is:
> "Jenkins ver. 1.475-SNAPSHOT (rc-07/11/2012 15:57 GMT-kohsuke)"
>
> I didn't see any replies to my message yesterday. I hope my messages are
> getting through to the list. Could someone please let me know they've seen
> this, just to set my mind at rest about that? Thanks.
>
> --
> Sarah Woodall
> Code Red Technologies



-- 
Website: http://earl-of-code.com

Which release of Jenkins can I safely use? -- problem now solved, I hope

[Sarah Woodall]

I've just looked again at the Jenkins website, and I find that there is 
now a release candidate available. I have downloaded the jenkins.war and 
installed it, and my multi-configuration jobs do now load from disk, 
apparently correctly. So I can use it!


This version is:
"Jenkins ver. 1.475-SNAPSHOT (rc-07/11/2012 15:57 GMT-kohsuke)"

I didn't see any replies to my message yesterday. I hope my messages are 
getting through to the list. Could someone please let me know they've 
seen this, just to set my mind at rest about that? Thanks.


--
Sarah Woodall
Code Red Technologies

Re: Problems with E-mail notification: Recipient host is svn uuid instead of Default user e-mail suffix

[Slide]

Someone filed something on this as JENKINS-13715, did you ever come up
with a resolution?

slide

On Tue, May 17, 2011 at 6:44 AM, Thomas Ferris Nicolaisen
 wrote:
> Well, I did find the cause of this problem in the end.
>
> The list of people in jenkins/people/ is populated by parsing the
> changelog.xml's (see the method View.People.getUserInfo(...)).
>
> Now, in addition to our SVN repository, we also have some Git repositories.
> Some of these are git-svn clones, where the author meta looks like this
> (it's the default behavior for git-svn to generate this email address):
>
> author t.nicolaisen 
> 1302777659 +
>
> So, in the end the problem is that we have changelogs with bogus e-mail
> addresses in the author tags.
>
> One solution could be to do git-svn with authormaps, and rewrite our git-svn
> clones to have proper e-mail addresses that will also work in Jenkins.
> However, this will be a big load of work for something that isn't really
> useful for our git-svn repositories anyway.
>
> At the same time, I think it is weird that an e-mail address that is found
> in the changelog of a Git repository, is used for notification in a build
> that is only using SVN, just because the usernames are the same in both
> repositories.
>
> Also, when I manually change the email-address in the People configure page,
> it reverts to the bogus email from the git-svn repository upon the next time
> I load the people list. I think that if I specify an email address manually,
> it should have precendence over whatever is parsed out of some changelog.
>
> Then again, I doubt anyone else are affected by this problem. Oh well, at
> least it's google-able now ;)



-- 
Website: http://earl-of-code.com

RE: groovy script error No such property: manager for class

[Alex Earl]

Just check the javadocs, you can use pretty much everything from there.

Sent from my Windows Phone
--
From: Kamal Ahmed
Sent: 7/20/2012 9:25 AM
To: jenkinsci-users@googlegroups.com
Subject: groovy script error  No such property: manager for class

Hi,
Is there a working example of groovy script for jenkins that i can use, so
i know what methods are available for use
I used:

def matcher = manager.getLogMatcher(".*Total time:
(.*)\$")if(matcher?.matches()) {
manager.addShortText(matcher.group(1), "grey", "white", "0px", "white")
}


in the Groovy Command text box, and got the following error:


Started by user anonymous 
Building in workspace /var/lib/jenkins/jobs/CM-MOCK-TEST1/workspace
[workspace] $ groovy
/var/lib/jenkins/jobs/CM-MOCK-TEST1/workspace/hudson1529437829169554915.groovy
Caught: groovy.lang.MissingPropertyException: No such property:
manager for class: hudson1529437829169554915
at hudson1529437829169554915.run(hudson1529437829169554915.groovy:1)
Build step 'Execute Groovy script' marked build as failure
Notifying upstream projects of job completion
Finished: FAILURE


Thanks,
-Kamal.

Re: How do I ignore mDNS?

[xipmox]

> On Wednesday, July 18, 2012 9:47:53 PM UTC+10, Jesse Farinacci wrote:
>>
>>
>>  Is it possible to make jenkins ignore mDNS? 
>>
>>
>> https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties
>>  
>>
>> hudson.DNSMultiCast.disabled 
>>
>  
I've given this a spin for a day or so and it doesn't seem to have the 
desired effect.

The process looks like this to 'ps' (ie I think I got the syntax right - 
did I?)
jenkins435   433  2 Jul19 ?00:30:15 /usr/bin/java -jar 
/usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war 
--httpPort=8080 --ajp13Port=-1 -Dhudson.DNSMultiCast.disabled=true

but lsof shows it is still listening on 5353.
java435 jenkins  244u  IPv4   94661685   UDP *:5353 

I looked at the code and it seems 
like core/src/main/java/hudson/DNSMultiCast.java should be doing the right 
thing.
But I have trouble understanding what 
core/src/main/java/jenkins/model/Jenkins.java is doing.
Is it unconditionally setting up an mdns listener?

groovy script error No such property: manager for class

[Kamal Ahmed]

Hi,
Is there a working example of groovy script for jenkins that i can use, so i 
know what methods are available for use
I used:

def matcher = manager.getLogMatcher(".*Total time: (.*)\$") 
if(matcher?.matches()) { manager.addShortText(matcher.group(1), "grey", 
"white", "0px", "white")
}

in the Groovy Command text box, and got the following error:

Started by user anonymous Building in workspace 
/var/lib/jenkins/jobs/CM-MOCK-TEST1/workspace
[workspace] $ groovy 
/var/lib/jenkins/jobs/CM-MOCK-TEST1/workspace/hudson1529437829169554915.groovy
Caught: groovy.lang.MissingPropertyException: No such property: manager for 
class: hudson1529437829169554915 at 
hudson1529437829169554915.run(hudson1529437829169554915.groovy:1)
Build step 'Execute Groovy script' marked build as failure
Notifying upstream projects of job completion
Finished: FAILURE

Thanks,
-Kamal.

run 2 maven cmds?

[BillR]

I'd like to run 2 mvn cmds in the same test - the 2nd one retries failure 
cases from files left by the 1st:

   mvn [params]
   mvn [params] -Dretry-=failed

Is there any way to do this?

Thanks,
Bill

Which release of Jenkins can I safely use?

[Sarah Woodall]

Could someone please advise me? I am setting up a new Windows 7 machine 
as our new Jenkins server. We have lots of jobs already defined, which 
we ran successfully on an old machine (also Windows 7) using Jenkins 1.441.


I need to know which release of Jenkins I can install on the new machine 
and safely use.


Here are my problems:

1. I know I can't use the latest release (Jenkins 1.474), because I need 
to use multi-configuration jobs. So the bug that I found and reported a 
couple of days ago (Jenkins JIRA issue 14474) rules this out.


2. I know I must not go back to the old release we were using on our old 
machine (Jenkins 1.441), even though our jobs do work on it, because of 
the security advisory that was issued in March:

This affects all the releases of Jenkins to date (main line releases up
to 1.452 and LTS up to 1.424.3.) Please upgrade to the new releases at
your earliest convenience


So ideally I need to know when bug 14474 was introduced, and go back to 
the release just before that (assuming it is later than 1.452). If it 
was before 1.452, though, then that isn't an option.


Or, alternatively, can anyone advise me when a fix for 14474 is likely 
to appear? According to the comment by Matthew Cooper in the JIRA 
report, something that sounds like the same bug is already fixed on the 
trunk. I thought perhaps I could download the latest release candidate 
and try it out, but there isn't one available. Clicking on the "RC" link 
on the Jenkins downloads page leads me to:

The requested URL /pub/jenkins/war-rc/1.475/jenkins.war was not found on this 
server.


If I knew there was only a short time to wait before I had a fix for 
that bug, I'd probably wait.


Or is there anything I can do to help? Perhaps I could test the fix, if 
indeed it has already been fixed?


Thanks for listening! I'd be so grateful for good advice over this problem.
--
Sarah Woodall
Code Red Technologies

Re: Question about working copy format used by Jenkins Subversion plugin 1.42

[Sarah Woodall]

On 19/07/2012 21:03, Carlton Brown wrote:

Apparently the Jenkins Subversion Plugin 1.42 has problems updating a
manually checked out 1.7 workspace with externals if that configuration
setting does not specify a 1.7 format.


Ah, is _that_ the way to work round the bug? I have lost so much time 
over this problem! See Jenkins JIRA issue 13790. Are you telling me that 
all I need to do is change this setting in the configuration and my 
problems will be over?



Apparently this setting defaults to an SVN 1.4 working copy format, at
least that's what I observe in Jenkins 1.474.


Yes, I had seen that it defaulted to 1.4. I did wonder why. I _thought_ 
I had changed it to 1.7 and that I still saw the problem, but perhaps I 
am confused.


--
Sarah Woodall
Code Red Technologies

Re: Question about working copy format used by Jenkins Subversion plugin 1.42

[Carlton Brown]

Answering my own question... apparently there exists a config property in
Jenkins called "Subversion Workspace Version"  (under
http://server/jenkins/configure) that governs this setting.

Apparently the Jenkins Subversion Plugin 1.42 has problems updating a
manually checked out 1.7 workspace with externals if that configuration
setting does not specify a 1.7 format.

Apparently this setting defaults to an SVN 1.4 working copy format, at
least that's what I observe in Jenkins 1.474.

On Thu, Jul 19, 2012 at 12:36 PM, Carlton Brown wrote:

> Is it expected behavior that the Subversion Plugin 1.42 is not compatible
> with SVN 1.7 working copies?   Also, is it expected that Jenkins will check
> out new working copies in the SVN 1.4 format?
>
> When I manually check out using svn 1.7, and direct Jenkins to use that
> working copy, Jenkins fails to update.   It happens regardless of whether
> the protocol is http or svn.   This is the error:
>
> AssertionError: appears to be using unpatched svnkit at 
> jar:file:/usr/share/tomcat6/.jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.7.4-jenkins-3.jar!/org/tmatesoft/svn/core/wc/SVNEvent.class
>
>
> I thought after all that recent work, the plugin would be compatible with
> 1.7 working copies.  Is that not true?
>
> Additionally,  a project checked out as a clean workspace shows a value of
> '8' in .svn/format which signifies that the Subversion 1.4 working copy
> format.   In fact those .svn metadata folders are found in every
> subdirectory, recursively.   I hoped we'd be done with all those droppings
> after updating to the Subversion 1.42 plugin.
>
> This is on Jenkins 1.474 on Linux.
>
>
>
>

Problem with lighttpd reverse proxy and Jenkins

[Lars Nordin]

I realize that this is better directed to a lighttpd forum but just a quick 
shout-out if someone else has set this up before.

I'm moving to an upgraded version of Jenkins and have some sort of mistake with 
my lighttpd reverse proxy that handles https and proxies it to Jenkins on 
non-ssl localhost:8080. If anyone has configuration tips that would be great.

Re: New vs. fixed PMD warnings detection

[abunetta]

I've opened "PMD Plugin reporting existing warnings as new"
https://issues.jenkins-ci.org/browse/JENKINS-14509

- David

On Thursday, July 19, 2012 4:58:45 PM UTC+3, Ulli Hafner wrote:
>
>  Seems that the context hash code is not computed. Are the filenames 
> correct? Is this a maven or freestyle job? 
>
> Can you please file an issue so we can discuss this problem in Jira?
>
> Ulli
>
> On 07/19/2012 01:35 PM, abune...@gmail.com wrote:
>  
> Which file plug-in file created file do you need exactly? 
> jenkins\jobs\job-name\builds\2012-07-19_13-38-36\pmd-warnings.xml?
>
> Would it be enough for me to find the equivalent entries in the 
> pmd.xml/pmd-warnings.xml files?
>
> For example:
>
> pmd.xml:
>  rule="LoggerIsNotStaticFinal" ruleset="Java Logging" 
> package="com.dbconfig.app" class="BackupDatabase" variable="logger" 
> externalInfoUrl=
> "http://pmd.sourceforge.net/rules/java/logging-java.html#LoggerIsNotStaticFinal";priority="2">
> The Logger variable declaration does not contain the static and final 
> modifiers
> 
>
> pmd-warnings.xml:
>   
> The Logger variable declaration does not contain the static 
> and final modifiers.
> HIGH
> 3660
> 
>   
> 29
> 29
>   
> 
> 29
> 
> /home/jenkins/slave-root/workspace/job-name/db-config/src/main/java/com/dbconfig/app/BackupDatabase.java
> 
> 
> Java Logging
> LoggerIsNotStaticFinal
> 3661
> pmd
> db-config/src/main/java/com/dbconfig/app
> 31
> 84
> 
>   
>
>
> - David
>
> On Thursday, July 19, 2012 12:31:15 PM UTC+3, Ulli Hafner wrote:
>
> Can you please file a bug report and attach the pmd warnings files 
> that are created by my plug-in (in the build folder) so I can compare these 
> two files...?
>
> Ulli
>
> On 07/19/2012 10:51 AM, abune...@gmail.com wrote:
> > Yes, definitely the same PMD version. Before the PMD upgrade there 
> were no PMD warnings.
> >
> > The amount of warnings that are detected as new or existing seems 
> almost random. It usually shows all warnings as new, but it sometimes 
> detects some 10's or 100's as existing.
> >
> > - David
> >
> > On Thursday, July 19, 2012 11:29:16 AM UTC+3, Ulli Hafner wrote:
> >
> > Is the current and reference build using the same PMD version? 
> Maybe the
> > IDs of the rules changed in PMD5...
> >
> > Ulli
> >
> > On 07/19/2012 09:59 AM, abune...@gmail.com wrote:
> > > Hi,
> > >
> > > I'm using the PMD plugin to detect and monitor PMD warnings 
> that are
> > > found in my builds. I recently upgraded to PMD 5.0 and added a 
> number
> > > of new PMD rules to my report.
> > >
> > > My problem is that the PMD plugin seems to be almost completely
> > > incapable of differentiating between new and previously found 
> PMD
> > > warnings.
> > >
> > > For example, I got this from a recent build:
> > > PMD: 1,306 warnings from one analysis.
> > >
> > > 1,304 new warnings
> > > 1,305 fixed warnings
> > >
> > > Other types of warnings analyses (e.g. findbugs, checkstyle) 
> get it
> > > right and are able to differentiate between new and old 
> warnings.
> > >
> > > Is this a known issue related to PMD 5? Any workarounds?
> > >
> > > Thanks,
> > > David
> > >
> > > Jenkins 1.474
> > > Jenkins Violations Plugin 0.7.10
> > > PMD Plugin 3.29
> > > Static analysis utilities 1.43
> > > Static analysis collector plugin 1.29
> >
>
>  
>  

Re: conditional buildstep multiple not working for version 1.474

[domi]

there is already a ticket for this: 
https://issues.jenkins-ci.org/browse/JENKINS-14465
its probably caused by the JavaScript split in the core - not sure when I find 
time to look at this...
/Domi

On 19.07.2012, at 10:37, Varghese Renny wrote:

> 
> 
> Can somebody check it's the fault of me or some issues with conditional build 
> step plugin on jenkins version 1.474?
> It was working fine on 1.447.1.
> 
> Someone please check?
> 
> 
> 
> Thanks in Advance
> varghese

Re: Problem with the wiki

[Kohsuke Kawaguchi]

Just restarted Apache and that fixed the problem.

On 07/19/2012 09:12 AM, Larry Shatzer, Jr. wrote:

I think this is due to the caching plugin that kohsuke wrote.

On Thu, Jul 19, 2012 at 9:56 AM, David Weintraub mailto:qazw...@gmail.com>> wrote:

Who's responsible for the Wiki? They need to reindex Confluence.

--
David Weintraub
qazw...@gmail.com 





--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

Question about working copy format used by Jenkins Subversion plugin 1.42

[Carlton Brown]

Is it expected behavior that the Subversion Plugin 1.42 is not compatible
with SVN 1.7 working copies?   Also, is it expected that Jenkins will check
out new working copies in the SVN 1.4 format?

When I manually check out using svn 1.7, and direct Jenkins to use that
working copy, Jenkins fails to update.   It happens regardless of whether
the protocol is http or svn.   This is the error:

AssertionError: appears to be using unpatched svnkit at
jar:file:/usr/share/tomcat6/.jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.7.4-jenkins-3.jar!/org/tmatesoft/svn/core/wc/SVNEvent.class


I thought after all that recent work, the plugin would be compatible with
1.7 working copies.  Is that not true?

Additionally,  a project checked out as a clean workspace shows a value of
'8' in .svn/format which signifies that the Subversion 1.4 working copy
format.   In fact those .svn metadata folders are found in every
subdirectory, recursively.   I hoped we'd be done with all those droppings
after updating to the Subversion 1.42 plugin.

This is on Jenkins 1.474 on Linux.

Re: Problem with the wiki

[Larry Shatzer, Jr.]

I think this is due to the caching plugin that kohsuke wrote.

On Thu, Jul 19, 2012 at 9:56 AM, David Weintraub  wrote:

> Who's responsible for the Wiki? They need to reindex Confluence.
>
> --
> David Weintraub
> qazw...@gmail.com
>

Re: Regarding Email Notification while trigger another job

[Varghese Renny]

> My company has blocked that site. Can somebody give some brief description 
> about fingerprinting and email-ext plugin use for downstream job?
>
My ultimate aim to send mail for job A commiter after successful completion 
of job B? 

>
>
>
>
> Thanks in Advance,
> varghese
>

Re: Problem with the wiki

[David Weintraub]

Who's responsible for the Wiki? They need to reindex Confluence.

-- 
David Weintraub
qazw...@gmail.com

Re: Problem with the wiki

[Matt Casto]

Yes, that workaround worked great for me. Thanks!

< Matt


On Thu, Jul 19, 2012 at 11:50 AM, Mikhail Kalkov
wrote:

> I was about to post a "me too" reply, when I noticed that somebody on
> #jenkins channel suggested to add random query to the end of the address
> string to defeat broken caching, i.e.
> https://wiki.jenkins-ci.org/display/JENKINS/Use+Jenkins?foobar
>
> /Mikhail
>

Displaying Graphml Type Files in Jenkins

[David Weintraub]

Since the Wiki is broken, and I can't seem to find the info on Google:
Is there a plugin that can display a graphml type file (Graphics
Markup Language)? This file was generated by the Ivy Ant task
.

-- 
David Weintraub
qazw...@gmail.com

Re: Problem with the wiki

[Mikhail Kalkov]

I was about to post a "me too" reply, when I noticed that somebody on 
#jenkins channel suggested to add random query to the end of the address 
string to defeat broken caching, i.e. 
https://wiki.jenkins-ci.org/display/JENKINS/Use+Jenkins?foobar

/Mikhail

Re: Problem with the wiki

[Matt Casto]

I was just about to post about this very same problem. I've seen it several
times this morning. Most recently this
https://wiki.jenkins-ci.org/display/JENKINS/Fogbugz+Plugin is instead
showing the Github plugin page.

< Matt


On Thu, Jul 19, 2012 at 10:48 AM, mpapo - Michaël Pailloncy <
mpapo@gmail.com> wrote:

> Hi,
>
> The wiki has a strange behavior for 30 minutes.
> When I go to
> https://wiki.jenkins-ci.org/display/JENKINS/Jelly+form+controls, the wiki
> show me random page (plugin github, cobertura, PMD Plugin, Virtual Box
> plugin ...).
> Each refresh show me a different plugin.
>
> Someone else has the problem?
>

Problem with the wiki

[mpapo - Michaël Pailloncy]

Hi,

The wiki has a strange behavior for 30 minutes.
When I go 
to https://wiki.jenkins-ci.org/display/JENKINS/Jelly+form+controls, the 
wiki show me random page (plugin github, cobertura, PMD Plugin, Virtual Box 
plugin ...).
Each refresh show me a different plugin.

Someone else has the problem?

Re: New vs. fixed PMD warnings detection

[Ullrich Hafner]

Seems that the context hash code is not computed. Are the filenames
correct? Is this a maven or freestyle job?

Can you please file an issue so we can discuss this problem in Jira?

Ulli

On 07/19/2012 01:35 PM, abune...@gmail.com wrote:
> Which file plug-in file created file do you need exactly?
> jenkins\jobs\job-name\builds\2012-07-19_13-38-36\pmd-warnings.xml?
>
> Would it be enough for me to find the equivalent entries in the
> pmd.xml/pmd-warnings.xml files?
>
> For example:
>
> pmd.xml:
>  rule="LoggerIsNotStaticFinal" ruleset="Java Logging"
> package="com.dbconfig.app" class="BackupDatabase" variable="logger"
> externalInfoUrl="http://pmd.sourceforge.net/rules/java/logging-java.html#LoggerIsNotStaticFinal";
> priority="2">
> The Logger variable declaration does not contain the static and final
> modifiers
> 
>
> pmd-warnings.xml:
>   
> The Logger variable declaration does not contain the
> static and final modifiers.
> HIGH
> 3660
> 
>   
> 29
> 29
>   
> 
> 29
>
> /home/jenkins/slave-root/workspace/job-name/db-config/src/main/java/com/dbconfig/app/BackupDatabase.java
> 
> 
> Java Logging
> LoggerIsNotStaticFinal
> 3661
> pmd
> db-config/src/main/java/com/dbconfig/app
> 31
> 84
> 
>   
>
>
> - David
>
> On Thursday, July 19, 2012 12:31:15 PM UTC+3, Ulli Hafner wrote:
>
> Can you please file a bug report and attach the pmd warnings files
> that are created by my plug-in (in the build folder) so I can compare
> these two files...?
>
> Ulli
>
> On 07/19/2012 10:51 AM, abune...@gmail.com wrote:
> > Yes, definitely the same PMD version. Before the PMD upgrade
> there were no PMD warnings.
> >
> > The amount of warnings that are detected as new or existing
> seems almost random. It usually shows all warnings as new, but it
> sometimes detects some 10's or 100's as existing.
> >
> > - David
> >
> > On Thursday, July 19, 2012 11:29:16 AM UTC+3, Ulli Hafner wrote:
> >
> > Is the current and reference build using the same PMD
> version? Maybe the
> > IDs of the rules changed in PMD5...
> >
> > Ulli
> >
> > On 07/19/2012 09:59 AM, abune...@gmail.com wrote:
> > > Hi,
> > >
> > > I'm using the PMD plugin to detect and monitor PMD
> warnings that are
> > > found in my builds. I recently upgraded to PMD 5.0 and
> added a number
> > > of new PMD rules to my report.
> > >
> > > My problem is that the PMD plugin seems to be almost
> completely
> > > incapable of differentiating between new and previously
> found PMD
> > > warnings.
> > >
> > > For example, I got this from a recent build:
> > > PMD: 1,306 warnings from one analysis.
> > >
> > > 1,304 new warnings
> > > 1,305 fixed warnings
> > >
> > > Other types of warnings analyses (e.g. findbugs,
> checkstyle) get it
> > > right and are able to differentiate between new and old
> warnings.
> > >
> > > Is this a known issue related to PMD 5? Any workarounds?
> > >
> > > Thanks,
> > > David
> > >
> > > Jenkins 1.474
> > > Jenkins Violations Plugin 0.7.10
> > > PMD Plugin 3.29
> > > Static analysis utilities 1.43
> > > Static analysis collector plugin 1.29
> >
>

Re: Regarding Email Notification while trigger another job

[Sami Tikka]

http://thingsyoudidntknowaboutjenkins.tumblr.com/post/24737092433/fingerprinting

-- Sami

Varghese Renny kirjoitti 19.7.2012 kello 7.47:

> 
> How can i done fingerprinting?
> Whether i only needed to put $SCRIPT tag in the content box of recipient in 
> second job which has been triggered by first?
> 
> Please share me a link which provide information regarding this?
> 
> 
> 
> Thanks in Advance 
> Varghese

Re: trigger builds remotely from one jenkins to another jenkins

[Sami Tikka]

Check 
https://wiki.jenkins-ci.org/display/JENKINS/Text+Finder+Run+Condition+Plugin 
for checking the console log.

Triggerin a job on another Jenkins can be done in one of two ways:

1. Somehow make a HTTP GET request (e.g. use curl) to 
http://OTHERJENKINS/job/JOBNAME/build

or 

2. Use Jenkins command-line-interface. See http://OTHERJENKINS/cli for more 
details.

-- Sami

Kamal Ahmed kirjoitti 19.7.2012 kello 15.09:

> Is there a way to trigger a remote jenkins "Build" based on if there is 
> "SUCCESS" String in the result 
> Thanks,
> -Kamal.

trigger builds remotely from one jenkins to another jenkins

[Kamal Ahmed]

Is there a way to trigger a remote jenkins "Build" based on if there is 
"SUCCESS" String in the result 
Thanks,
-Kamal.

Re: New vs. fixed PMD warnings detection

[abunetta]

Which file plug-in file created file do you need exactly? 
jenkins\jobs\job-name\builds\2012-07-19_13-38-36\pmd-warnings.xml?

Would it be enough for me to find the equivalent entries in the 
pmd.xml/pmd-warnings.xml files?

For example:

pmd.xml:
http://pmd.sourceforge.net/rules/java/logging-java.html#LoggerIsNotStaticFinal";
 
priority="2">
The Logger variable declaration does not contain the static and final 
modifiers


pmd-warnings.xml:
  
The Logger variable declaration does not contain the static 
and final modifiers.
HIGH
3660

  
29
29
  

29

/home/jenkins/slave-root/workspace/job-name/db-config/src/main/java/com/dbconfig/app/BackupDatabase.java


Java Logging
LoggerIsNotStaticFinal
3661
pmd
db-config/src/main/java/com/dbconfig/app
31
84

  


- David

On Thursday, July 19, 2012 12:31:15 PM UTC+3, Ulli Hafner wrote:

Can you please file a bug report and attach the pmd warnings files that 
are created by my plug-in (in the build folder) so I can compare these two 
files...?

Ulli

On 07/19/2012 10:51 AM, abune...@gmail.com wrote:
> Yes, definitely the same PMD version. Before the PMD upgrade there 
were no PMD warnings.
>
> The amount of warnings that are detected as new or existing seems 
almost random. It usually shows all warnings as new, but it sometimes 
detects some 10's or 100's as existing.
>
> - David
>
> On Thursday, July 19, 2012 11:29:16 AM UTC+3, Ulli Hafner wrote:
>
> Is the current and reference build using the same PMD version? 
Maybe the
> IDs of the rules changed in PMD5...
>
> Ulli
>
> On 07/19/2012 09:59 AM, abune...@gmail.com wrote:
> > Hi,
> >
> > I'm using the PMD plugin to detect and monitor PMD warnings 
that are
> > found in my builds. I recently upgraded to PMD 5.0 and added a 
number
> > of new PMD rules to my report.
> >
> > My problem is that the PMD plugin seems to be almost completely
> > incapable of differentiating between new and previously found 
PMD
> > warnings.
> >
> > For example, I got this from a recent build:
> > PMD: 1,306 warnings from one analysis.
> >
> > 1,304 new warnings
> > 1,305 fixed warnings
> >
> > Other types of warnings analyses (e.g. findbugs, checkstyle) 
get it
> > right and are able to differentiate between new and old 
warnings.
> >
> > Is this a known issue related to PMD 5? Any workarounds?
> >
> > Thanks,
> > David
> >
> > Jenkins 1.474
> > Jenkins Violations Plugin 0.7.10
> > PMD Plugin 3.29
> > Static analysis utilities 1.43
> > Static analysis collector plugin 1.29
>

Javascript in Project Description stopped working

[Kamal Ahmed]

Hi,
I am using Jenkins 1.471 and Cannot use/preview Javascript in Project 
Description. Anyone know how to get it to work ?
Thanks,
-Kamal.

RE: email-ext plugin sends two emails

[Matthew.Webber]

I opened change request https://issues.jenkins-ci.org/browse/JENKINS-14500
Thanks

> -Original Message-
> From: jenkinsci-users@googlegroups.com 
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
> Sent: 19 July 2012 11:30
> To: jenkinsci-users@googlegroups.com
> Subject: Re: email-ext plugin sends two emails
> 
> You'd have to open a change request.
> 
> On Thu, Jul 19, 2012 at 3:28 AM,   wrote:
> > I am using the very useful email-ext plugin, and I have it configured to 
> > send emails for:
> > Improvement - An email will be sent any time there is an improvement. A 
> > build is considered to have
> improved whenever it has fewer failures than the previous build.
> > Fixed - An email will be sent when the build status changes from "Failure" 
> > or "Unstable" to
> "Successful".
> >
> > Unfortunately, when a job previously had tests failing, and then they are 
> > fixed, I get two emails -
> one for "Improvement", and then another for "Fixed". I only want the "Fixed" 
> email.
> >
> > It would be more useful if the Improvement email was sent only when the 
> > number of failing tests
> decreased, but was still no-zero (so there is no overlap with the "Fixed" 
> case).
> >
> > Is this something I can achieve by changing my configuration, or should I 
> > open a change request, or
> is there a good reason for it working as it does?
> >
> > Thanks
> > Matthew
> >


--
This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

Re: email-ext plugin sends two emails

[Slide]

Or you could do it with a pre-send script...

On Thu, Jul 19, 2012 at 3:28 AM,   wrote:
> I am using the very useful email-ext plugin, and I have it configured to send 
> emails for:
> Improvement - An email will be sent any time there is an improvement. A build 
> is considered to have improved whenever it has fewer failures than the 
> previous build.
> Fixed - An email will be sent when the build status changes from "Failure" or 
> "Unstable" to "Successful".
>
> Unfortunately, when a job previously had tests failing, and then they are 
> fixed, I get two emails - one for "Improvement", and then another for 
> "Fixed". I only want the "Fixed" email.
>
> It would be more useful if the Improvement email was sent only when the 
> number of failing tests decreased, but was still no-zero (so there is no 
> overlap with the "Fixed" case).
>
> Is this something I can achieve by changing my configuration, or should I 
> open a change request, or is there a good reason for it working as it does?
>
> Thanks
> Matthew
>
>
> --
> This e-mail and any attachments may contain confidential, copyright and or 
> privileged material, and are for the use of the intended addressee only. If 
> you are not the intended addressee or an authorised recipient of the 
> addressee please notify us of receipt by returning the e-mail and do not use, 
> copy, retain, distribute or disclose the information in or attached to the 
> e-mail.
> Any opinions expressed within this e-mail are those of the individual and not 
> necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
> attachments are free from viruses and we cannot accept liability for any 
> damage which you may sustain as a result of software viruses which may be 
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England and 
> Wales with its registered office at Diamond House, Harwell Science and 
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>
>
>
>



-- 
Website: http://earl-of-code.com

Re: email-ext plugin sends two emails

[Slide]

You'd have to open a change request.

On Thu, Jul 19, 2012 at 3:28 AM,   wrote:
> I am using the very useful email-ext plugin, and I have it configured to send 
> emails for:
> Improvement - An email will be sent any time there is an improvement. A build 
> is considered to have improved whenever it has fewer failures than the 
> previous build.
> Fixed - An email will be sent when the build status changes from "Failure" or 
> "Unstable" to "Successful".
>
> Unfortunately, when a job previously had tests failing, and then they are 
> fixed, I get two emails - one for "Improvement", and then another for 
> "Fixed". I only want the "Fixed" email.
>
> It would be more useful if the Improvement email was sent only when the 
> number of failing tests decreased, but was still no-zero (so there is no 
> overlap with the "Fixed" case).
>
> Is this something I can achieve by changing my configuration, or should I 
> open a change request, or is there a good reason for it working as it does?
>
> Thanks
> Matthew
>
>
> --
> This e-mail and any attachments may contain confidential, copyright and or 
> privileged material, and are for the use of the intended addressee only. If 
> you are not the intended addressee or an authorised recipient of the 
> addressee please notify us of receipt by returning the e-mail and do not use, 
> copy, retain, distribute or disclose the information in or attached to the 
> e-mail.
> Any opinions expressed within this e-mail are those of the individual and not 
> necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
> attachments are free from viruses and we cannot accept liability for any 
> damage which you may sustain as a result of software viruses which may be 
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England and 
> Wales with its registered office at Diamond House, Harwell Science and 
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>
>
>
>



-- 
Website: http://earl-of-code.com

email-ext plugin sends two emails

[Matthew.Webber]

I am using the very useful email-ext plugin, and I have it configured to send 
emails for:
Improvement - An email will be sent any time there is an improvement. A build 
is considered to have improved whenever it has fewer failures than the previous 
build. 
Fixed - An email will be sent when the build status changes from "Failure" or 
"Unstable" to "Successful".

Unfortunately, when a job previously had tests failing, and then they are 
fixed, I get two emails - one for "Improvement", and then another for "Fixed". 
I only want the "Fixed" email.

It would be more useful if the Improvement email was sent only when the number 
of failing tests decreased, but was still no-zero (so there is no overlap with 
the "Fixed" case).

Is this something I can achieve by changing my configuration, or should I open 
a change request, or is there a good reason for it working as it does?

Thanks
Matthew


--
This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

Re: New vs. fixed PMD warnings detection

[Ullrich Hafner]

Can you please file a bug report and attach the pmd warnings files that
are created by my plug-in (in the build folder) so I can compare these
two files...?

Ulli

On 07/19/2012 10:51 AM, abune...@gmail.com wrote:
> Yes, definitely the same PMD version. Before the PMD upgrade there
> were no PMD warnings.
>
> The amount of warnings that are detected as new or existing seems
> almost random. It usually shows all warnings as new, but it sometimes
> detects some 10's or 100's as existing.
>
> - David
>
> On Thursday, July 19, 2012 11:29:16 AM UTC+3, Ulli Hafner wrote:
>
> Is the current and reference build using the same PMD version?
> Maybe the
> IDs of the rules changed in PMD5...
>
> Ulli
>
> On 07/19/2012 09:59 AM, abune...@gmail.com
>  wrote:
> > Hi,
> >
> > I'm using the PMD plugin to detect and monitor PMD warnings that
> are
> > found in my builds. I recently upgraded to PMD 5.0 and added a
> number
> > of new PMD rules to my report.
> >
> > My problem is that the PMD plugin seems to be almost completely
> > incapable of differentiating between new and previously found PMD
> > warnings.
> >
> > For example, I got this from a recent build:
> > PMD: 1,306 warnings from one analysis.
> >
> > 1,304 new warnings
> > 1,305 fixed warnings
> >
> > Other types of warnings analyses (e.g. findbugs, checkstyle) get it
> > right and are able to differentiate between new and old warnings.
> >
> > Is this a known issue related to PMD 5? Any workarounds?
> >
> > Thanks,
> > David
> >
> > Jenkins 1.474
> > Jenkins Violations Plugin 0.7.10
> > PMD Plugin 3.29
> > Static analysis utilities 1.43
> > Static analysis collector plugin 1.29
>

Re: New vs. fixed PMD warnings detection

[abunetta]

Yes, definitely the same PMD version. Before the PMD upgrade there were no 
PMD warnings.

The amount of warnings that are detected as new or existing seems almost 
random. It usually shows all warnings as new, but it sometimes detects some 
10's or 100's as existing.

- David

On Thursday, July 19, 2012 11:29:16 AM UTC+3, Ulli Hafner wrote:
>
> Is the current and reference build using the same PMD version? Maybe the 
> IDs of the rules changed in PMD5... 
>
> Ulli 
>
> On 07/19/2012 09:59 AM, abune...@gmail.com wrote: 
> > Hi, 
> > 
> > I'm using the PMD plugin to detect and monitor PMD warnings that are 
> > found in my builds. I recently upgraded to PMD 5.0 and added a number 
> > of new PMD rules to my report. 
> > 
> > My problem is that the PMD plugin seems to be almost completely 
> > incapable of differentiating between new and previously found PMD 
> > warnings. 
> > 
> > For example, I got this from a recent build: 
> > PMD: 1,306 warnings from one analysis. 
> > 
> > 1,304 new warnings 
> > 1,305 fixed warnings 
> > 
> > Other types of warnings analyses (e.g. findbugs, checkstyle) get it 
> > right and are able to differentiate between new and old warnings. 
> > 
> > Is this a known issue related to PMD 5? Any workarounds? 
> > 
> > Thanks, 
> > David 
> > 
> > Jenkins 1.474 
> > Jenkins Violations Plugin 0.7.10 
> > PMD Plugin 3.29 
> > Static analysis utilities 1.43 
> > Static analysis collector plugin 1.29 
>
>

Jenkins newbie... Running sequentially job tasks on several environments for different projects using Jenkins

[ridan]

Hi,

I'm new to Jenkins. I'm trying to implement a specific scenario to build 
mobile applications using Jenkins. For each project I want to launch 
several tasks sequentially. Each task will use previous task output:


   - Task 1: It is a batch script that will run on windows. It Uses source 
   code from SCM (SVN)
   - Task 2: Another batch script running on windows. It will use task 1 
   output
   - Task 3: A shell script running on OSX. It will use task 2 input
   

I want to use this configuration for several projects. How can I 
efficiently organize my jobs/tasks so that it will be easy to create new 
project + do I need additionnal plugins ?

Thanks in advance,

conditional buildstep multiple not working for version 1.474

[Varghese Renny]

Can somebody check it's the fault of me or some issues with conditional 
build step plugin on jenkins version 1.474?
It was working fine on 1.447.1.

Someone please check?



Thanks in Advance
varghese

Re: New vs. fixed PMD warnings detection

[Ullrich Hafner]

Is the current and reference build using the same PMD version? Maybe the
IDs of the rules changed in PMD5...

Ulli

On 07/19/2012 09:59 AM, abune...@gmail.com wrote:
> Hi,
>
> I'm using the PMD plugin to detect and monitor PMD warnings that are
> found in my builds. I recently upgraded to PMD 5.0 and added a number
> of new PMD rules to my report.
>
> My problem is that the PMD plugin seems to be almost completely
> incapable of differentiating between new and previously found PMD
> warnings.
>
> For example, I got this from a recent build:
> PMD: 1,306 warnings from one analysis.
>
> 1,304 new warnings
> 1,305 fixed warnings
>
> Other types of warnings analyses (e.g. findbugs, checkstyle) get it
> right and are able to differentiate between new and old warnings.
>
> Is this a known issue related to PMD 5? Any workarounds?
>
> Thanks,
> David
>
> Jenkins 1.474
> Jenkins Violations Plugin 0.7.10
> PMD Plugin 3.29
> Static analysis utilities 1.43
> Static analysis collector plugin 1.29 

Re: psexec from a windows script works but doesn't return

[Eyal]

I'm having the same problem? Any suggestions?

On Wednesday, January 11, 2012 10:42:42 PM UTC+2, had4 wrote:
>
> I am running a Jenkins build on windows that calls a script from the 
> workspace which uses psexec.exe to remotely run an installation on 
> another server. I have the -accepteula option so it doesn't hang 
> waiting for that. It actually runs the job on the remote server but 
> when the remote script exits the Jenkins build doesn't get the message 
> and hangs (until I kill the psexec service process on the remote 
> server or the psexec process on the Jenkins server. Has anyone tried 
> this successfully? Below is the output from the end of the jenkins job 
> where it is running the script. 
>
> Is this something I should be using a Jenkins slave for? I suppose I 
> should look into that. 
>
> Thanks. 
>
>
> [workspace] $ cmd /c call D:\tomcat6\temp 
> \hudson7618064618623105909.bat 
>
> d:\opt\hudson\jobs\Deploy XXX to Dev\workspace>installdevportal.bat 
>
> d:\opt\hudson\jobs\Deploy XXX to Dev\workspace>set SERVER=10.99.99.56 
>
> d:\opt\hudson\jobs\Deploy XXX to Dev\workspace>copy target\portal.war \ 
> \10.217.6.56\D$\temp 
> 1 file(s) copied. 
>
> d:\opt\hudson\jobs\Deploy XXX to Dev\workspace>tools\psexec.exe - 
> accepteula \\10.99.99.56 -u techboss -p PASSWORD -w d:\temp d:\temp 
> \installportal.bat 10.99.99.56 weblogic 
>
> PsExec v1.98 - Execute processes remotely 
> Copyright (C) 2001-2010 Mark Russinovich 
> Sysinternals - www.sysinternals.com 
>
>  HANGS HERE UNTIL I KILL PROCESSES, NO OUTPUT RETURNED FROM REMOTE 
> SCRIPT 
>
> Build was aborted 
> Aborted by hal.deadman 
> Finished: ABORTED 
>

reorganizing Use+Jenkins - protocol?

[xipmox]

Hi

I keep reading https://wiki.jenkins-ci.org/display/JENKINS/Use+Jenkins and 
keep having ideas about how the contents could be reorganized (maybe a 
little, maybe a lot). But I don't want to 'break' the page for other people 
who are used to finding things in particular places. What is the 
protocol/process here?

Thanks

New vs. fixed PMD warnings detection

[abunetta]

Hi,

I'm using the PMD plugin to detect and monitor PMD warnings that are found 
in my builds. I recently upgraded to PMD 5.0 and added a number of new PMD 
rules to my report.

My problem is that the PMD plugin seems to be almost completely incapable 
of differentiating between new and previously found PMD warnings.

For example, I got this from a recent build:
PMD: 1,306 warnings from one analysis.

1,304 new warnings
1,305 fixed warnings

Other types of warnings analyses (e.g. findbugs, checkstyle) get it right 
and are able to differentiate between new and old warnings.

Is this a known issue related to PMD 5? Any workarounds?

Thanks,
David

Jenkins 1.474
Jenkins Violations Plugin 0.7.10
PMD Plugin 3.29
Static analysis utilities 1.43
Static analysis collector plugin 1.29

Re: How do I ignore mDNS?

[xipmox]

On Wednesday, July 18, 2012 9:47:53 PM UTC+10, Jesse Farinacci wrote:
>
>
>  Is it possible to make jenkins ignore mDNS? 
>
>
> https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties
>  
>
> hudson.DNSMultiCast.disabled 
>
>
Thank you for that, I did poke around the wiki but that link did not look 
relevant to me.