date:20141110
















































Mark Waite
 closed  JENKINS-10434 as Fixed


Git plugin 1.1.10 fails to parse author information
















Fix released in git plugin 2.3 10 Nov 2014





Change By:


Mark Waite
(11/Nov/14 5:47 AM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-25313) Deleting repository or branch from Git settings also prevents future addition
















































Mark Waite
 closed  JENKINS-25313 as Fixed


Deleting repository or branch from Git settings also prevents future addition
















Fix released in git plugin 2.3 10 Nov 2014





Change By:


Mark Waite
(11/Nov/14 5:45 AM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-20531) Retry count not working in Git plugin 2.0
















































Mark Waite
 closed  JENKINS-20531 as Fixed


Retry count not working in Git plugin 2.0
















Change By:


Mark Waite
(11/Nov/14 5:45 AM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github-plugin] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
















































Mark Waite
 closed  JENKINS-23641 as Fixed


Builds are failing due to GitHubCommitNotifier exception
















Change By:


Mark Waite
(11/Nov/14 5:46 AM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-25191) Git plugin does not correctly record built revision on failed merge
















































Mark Waite
 closed  JENKINS-25191 as Fixed


Git plugin does not correctly record built revision on failed merge
















Fix released in git plugin 2.3 10 Nov 2014





Change By:


Mark Waite
(11/Nov/14 5:46 AM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github-plugin] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
















































Mark Waite
 resolved  JENKINS-23641 as Fixed


Builds are failing due to GitHubCommitNotifier exception
















Fix released in git plugin 2.3 10 Nov 2014





Change By:


Mark Waite
(11/Nov/14 5:46 AM)




Status:


In Progress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-16737) java.lang.RuntimeException: No author in changeset null
















































Mark Waite
 closed  JENKINS-16737 as Fixed


java.lang.RuntimeException: No author in changeset null
















Fix released in git plugin 2.3 10 Nov 2014





Change By:


Mark Waite
(11/Nov/14 5:46 AM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-plugin] (JENKINS-20531) Retry count not working in Git plugin 2.0
















































Mark Waite
 resolved  JENKINS-20531 as Fixed


Retry count not working in Git plugin 2.0
















Fix released in git plugin 2.3 10 Nov 2014





Change By:


Mark Waite
(11/Nov/14 5:45 AM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

2014-11-10 Thread ariste...@java.net (JIRA)















































aristedes
 commented on  JENKINS-18935


Make Subversion plugin support Subversion 1.8















I upgraded to "2.5-SNAPSHOT (private-11/08/2014 10:24-jenkins)" and it installed fine. However despite changing the preference to "1.8" it did not upgrade any checked out repository. Other than that it worked fine.

Will we need to manually destroy all workspaces in order to get them upgraded to 1.8?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cli] (JENKINS-18627) NullPointerException in Jenkins CLI

2014-11-10 Thread o.v.nenas...@gmail.com (JIRA)















































Oleg Nenashev
 commented on  JENKINS-18627


NullPointerException in Jenkins CLI















GitHub browser lists all versions including 1.540. I just have not bothered to expand "..." mark (which wasn't very visible BTW)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [claim-plugin] (JENKINS-25530) Claiming a broken test for a matrix build should claim all instances of the same test across the matrix

2014-11-10 Thread trej...@java.net (JIRA)















































trejkaz
 created  JENKINS-25530


Claiming a broken test for a matrix build should claim all instances of the same test across the matrix















Issue Type:


Improvement



Assignee:


Christian Åkerström



Components:


claim-plugin



Created:


11/Nov/14 1:31 AM



Description:


We have a matrix build to run the same tests across multiple platforms.

For many tests, when they fail on one platform, they fail on all platforms at once. It is inconvenient to have to claim all 5 failures separately when the odds are that fixing it once will fix it for all platforms, so it would be nice if claiming it for one would automatically claim it for all other instances of the same test failure.




Project:


Jenkins



Priority:


Minor



Reporter:


trejkaz

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [script-security-plugin] (JENKINS-25524) SandboxInterceptorTest "templates" test failure blocking compilation

2014-11-10 Thread jtklin...@yahoo.com (JIRA)















































James Klinect
 commented on  JENKINS-25524


SandboxInterceptorTest "templates" test failure blocking compilation















Saw this earlier, the total turnaround time (filing-to-fixed) is incredible.  Remarkable.  Astonishing?  I can't decide which word does it the most justice.  Pulling in the fix allowed me to build the plugin successfully.  Thanks for patching this!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher

2014-11-10 Thread unclet...@java.net (JIRA)















































uncletall
 commented on  JENKINS-25180


Unable to authenticate using LDAP after upgrading to 1.576 or higher















I am not so sure how to do that. But I have just tested 1.589 and the problem is still present in this version. I can't find the tag in GitHub and the latest link still points to the 1.588 on the web site so I don't know if the 1.589 is officially released. But as JENKINS-25144 is marked as fixed I would have expected this issue to be fixed as well.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-flow-plugin] (JENKINS-25529) Build Flow does not always run multiple jobs in parallel: requires parameters to be passed, and "Execute concurrent" in downstream job

2014-11-10 Thread kb...@imprivata.com (JIRA)















































Ken Beal
 created  JENKINS-25529


Build Flow does not always run multiple jobs in parallel: requires parameters to be passed, and "Execute concurrent" in downstream job















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


build-flow-plugin



Created:


10/Nov/14 11:56 PM



Description:


I created two jobs, flowA and flowB.  flowA is a "Build Flow" job; flowB is just a regular job ("Freestyle project") that does nothing.

I used this for the Groovy code in flowA:

=
parallel (
{ build("flowB" ) },
{ build("flowB" ) },
{ build("flowB" ) }
)
=

The console output from running this job was:

=
Started by user Ken Beal
parallel {
Schedule job flowB
Schedule job flowB
Schedule job flowB
Build flowB #1 started
Build flowB #1 started
Build flowB #1 started
flowB #1 completed 
flowB #1 completed 
flowB #1 completed 
}
Notifying upstream projects of job completion
Finished: SUCCESS
=

Then I thought, perhaps it needs parameters?  So I added a string parameter named "string" with default "ABC" to flowB, then updated flowA's Groovy code to:

=
parallel (
{ build("flowB", string: 1 ) },
{ build("flowB", string: 2 ) },
{ build("flowB", string: 3 ) }
)
=

I rebuilt, and got the same result.  I almost submitted the bug report at this stage, where I'm blocked, but I found out how to unblock myself so I'll report that as well (and, this might be why this set of bugs hasn't been reported yet – perhaps most people start with jobs that have parameters).  I then checked flowB's "Execute concurrently builds if necessary", and re-ran it; this time, the output looked better:

=
Started by user Ken Beal
parallel {
Schedule job flowB
Schedule job flowB
Schedule job flowB
Build flowB #3 started
Build flowB #4 started
flowB #3 completed 
Build flowB #5 started
flowB #4 completed 
flowB #5 completed 
}
Notifying upstream projects of job completion
Finished: SUCCESS
=

Then I did a final check, as I wanted to know which was required, the "concurrent" checkbox, or the parameter passing?  I removed the parameter passing from the Groovy in flowA, but left flowB alone, and re-ran; then I got the same results that I originally got – proving that BOTH are necessary.

So, with the current state of the code, in order to run a downstream job in parallel, that job needs to be configured to run in parallel (the "duh" part), and also, the calling job needs to pass parameters down (not at all obvious).

I synced to the latest available Jenkins (1.589) and Build Flow plugin (0.16), before reproducing and reporting this today.




Project:


Jenkins



Priority:


Major



Reporter:


Ken Beal

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-25528) Reboot dialog displayed during MSI installation when upgrading

2014-11-10 Thread malliina...@gmail.com (JIRA)

Michael Skogberg
created JENKINS-25528

Reboot dialog displayed during MSI installation when upgrading

Issue Type:

Improvement

Assignee:

Unassigned

Components:

core

Created:

10/Nov/14 11:16 PM

Description:

Upgrading Jenkins using an MSI package while a previous version of Jenkins is running will open a dialog saying "... a reboot will be required to complete the setup." To reproduce, double-click jenkins-1.587.msi and complete the installation, then double-click jenkins-1.589.msi to upgrade.

I do not believe a reboot should actually be necessary. The dialog is not displayed if the user manually stops the service before running the newer MSI, but that workaround is not user-friendly. If the MSI installer would stop the service early on during the upgrade, I suspect the dialog would not be shown.

I'm not sure if the ServiceControl element defined in https://github.com/jenkinsci/jenkins/blob/master/msi/jenkins.wxs is supposed to stop the service during upgrades. I also don't know if this is a problem with the WiX definition or a winsw issue. Another app I know of also uses winsw and WiX and has the same issue.

Environment:

Windows 8.1, JDK8, Jenkins 1.589

Project:

Jenkins

Labels:

jenkins
service
windows
winsw

Priority:

Minor

Reporter:

Michael Skogberg

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

2014-11-10 Thread schristo...@gmail.com (JIRA)















































Steven Christou
 commented on  JENKINS-18935


Make Subversion plugin support Subversion 1.8















I completed PR-103 to work with subversion 1.8. While this worked locally I would like to make sure that this works for other users before performing a new release. Could I get a few volunteers to test this plugin before I perform a release. You can download the subversion.hpi file and install it in the Advanced tab in the Plugin Management page. Please install this in a CONTROLLED TEST ENVIRONMENT as this is still in a pull request and it is not final yet.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-14174) Publisher hudson.plugins.jabber.im.transport.JabberPublisher aborted due to exception
















































kutzi
 assigned  JENKINS-14174 to kutzi



Publisher hudson.plugins.jabber.im.transport.JabberPublisher aborted due to exception
















Change By:


kutzi
(10/Nov/14 10:27 PM)




Assignee:


kutzi



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-14174) Publisher hudson.plugins.jabber.im.transport.JabberPublisher aborted due to exception















































kutzi
 updated  JENKINS-14174


Publisher hudson.plugins.jabber.im.transport.JabberPublisher aborted due to exception
















Sorry, don't know how this could escape my attention for so long.

Is this still a problem for you?





Change By:


kutzi
(10/Nov/14 10:27 PM)




Component/s:


notification-plugin



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-25505) After Upgrade jenkins to 1.587 cannot send message with jabber















































kutzi
 commented on  JENKINS-25505


After Upgrade jenkins to 1.587 cannot send message with jabber















Smack issue tracked in https://igniterealtime.org/issues/browse/SMACK-616



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github-plugin] (JENKINS-18298) Jenkins (Github Plugin) post-commit hook fails to build with ssh config aliases

2014-11-10 Thread alex.eh...@gmail.com (JIRA)















































Alex Ehlke
 commented on  JENKINS-18298


Jenkins (Github Plugin) post-commit hook fails to build with ssh config aliases















My fork is here: https://github.com/tophatmonocle/github-plugin/tree/github-1.10-SNAPSHOT-NOHOSTS



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-25515) Jabber can not send message















































kutzi
 commented on  JENKINS-25515


Jabber can not send message















Regarding the session problem: if you have more info (e.g. thread dumps) please open an issue for this and I'll look at it. Low prio, since it doesn't seem to break anything.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-25515) Jabber can not send message















































kutzi
 commented on  JENKINS-25515


Jabber can not send message















Fixed in jabber-plugin 1.29



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-25515) Jabber can not send message
















































kutzi
 resolved  JENKINS-25515 as Fixed


Jabber can not send message
















Change By:


kutzi
(10/Nov/14 10:15 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-25515) Jabber can not send message















































SCM/JIRA link daemon
 commented on  JENKINS-25515


Jabber can not send message















Code changed in jenkins
User: Christoph Kutzinski
Path:
 src/main/java/hudson/plugins/jabber/im/transport/JabberIMConnection.java
http://jenkins-ci.org/commit/jabber-plugin/87f188e7e7199e256c170008797b903f4c929f5a
Log:
  JENKINS-25515 workaround for VCard parsing problem





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github-plugin] (JENKINS-18298) Jenkins (Github Plugin) post-commit hook fails to build with ssh config aliases

2014-11-10 Thread alex.eh...@gmail.com (JIRA)















































Alex Ehlke
 commented on  JENKINS-18298


Jenkins (Github Plugin) post-commit hook fails to build with ssh config aliases















I too ran into this issue. I'm making a temporary fix in my own fork that just ignores hostname when checking whether a repo matches another given repo, since for us this does not matter.

I think a proper fix has to somehow resolve the hostname to its actual hostname - I looked into this and the only way I can see to do it would be to parse the SSH config file, but that is awful (and there are several files that could set this). There must be a better way, but at this point I'm out of my depth on the solution.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [groovy-plugin] (JENKINS-12988) Improve Groovy help file
















































SCM/JIRA link daemon
 resolved  JENKINS-12988 as Fixed


Improve Groovy help file
















Change By:


SCM/JIRA link daemon
(10/Nov/14 8:50 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [groovy-plugin] (JENKINS-12988) Improve Groovy help file















































SCM/JIRA link daemon
 commented on  JENKINS-12988


Improve Groovy help file















Code changed in jenkins
User: Vojtech Juranek
Path:
 src/main/resources/hudson/plugins/groovy/Groovy/config.jelly
 src/main/webapp/groovy-version.html
http://jenkins-ci.org/commit/groovy-plugin/25ee88b770471217dde2d39669a701f6823cc0b1
Log:
  [FIXED JENKINS-12988] Improve Groovy version help file





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-25455) Code input field is too small















































SCM/JIRA link daemon
 commented on  JENKINS-25455


Code input field is too small















Code changed in jenkins
User: Vojtech Juranek
Path:
 src/main/resources/hudson/plugins/groovy/SystemGroovy/config.jelly
http://jenkins-ci.org/commit/groovy-plugin/dc6c57f9137f1b0e8590d1b90471d41b1ee7a559
Log:
  JENKINS-25455 Use StringScriptSource as default also for System Groovy script





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cli] (JENKINS-18627) NullPointerException in Jenkins CLI















































Jesse Glick
 commented on  JENKINS-18627


NullPointerException in Jenkins CLI
















jenkins$ git describe --contains b2730f3d31da93a45c7321962141c6f1bc360937
jenkins-1.540~39




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [xunit-plugin] (JENKINS-25527) xUnit reports yield duplicated "Test Result Trend" charts















































Watertight Door
 commented on  JENKINS-25527


xUnit reports yield duplicated "Test Result Trend" charts















Sorry – meant to add that this looked different than JENKINS-24608 as that issue seemed to be directly related to the Matrix Project plugin.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [xunit-plugin] (JENKINS-25527) xUnit reports yield duplicated "Test Result Trend" charts

Watertight Door
created JENKINS-25527

xUnit reports yield duplicated "Test Result Trend" charts

Issue Type:

Bug

Assignee:

Gregory Boissinot

Components:

xunit-plugin

Created:

10/Nov/14 8:50 PM

Description:

When using xUnit to interpret Boost Test XML log files in a Freestyle Project, Jenkins serves up duplicated "Test Result Trend" charts on the project page.

Interesting behavior of note that made it seem like an xUnit issue to me:

if I turn on the xUnit post-build reporting and perform a build, I get two identical "Test Result Trend" charts pointing to the same link.
If then configure the project by deleting the xUnit post-build action and refresh the browser before rebuilding I only see one "Test Result Trend" chart, even if I navigate away from the project page and then back.
If I then rebuild in the "no reporting" state, then as expected I get no charts.

The resulting junitResult.xml file in my builds looks like:

/var/lib/jenkins/jobs/host_common/workspace/generatedJUnitFiles/BoostTest/TEST-682740763.xml
MergedTestSuite
0.0

0.0
testHostCommon./var/lib/jenkins/jobs/host_common/workspace/erTools/src/test/testPack
testPack
false

[Info] - check 1 == 1 passed
== [File] - /var/lib/jenkins/jobs/host_common/workspace/erTools/src/test/testPack.cpp
== [Line] - 8
0

0.0
true

Environment:

Ubuntu 12.04, I'm using Jenkins 1.588 and xUnit 1.92. Using xUnit to interface with output from Boost Test.

Project:

Jenkins

Priority:

Minor

Reporter:

Watertight Door

[JIRA] [cli] (JENKINS-18627) NullPointerException in Jenkins CLI

2014-11-10 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-18627


NullPointerException in Jenkins CLI















Jesse Glick: My guess: Because the 1.565.1-rc1 tag name is (again) inconsistent with all the others, it's more difficult to tell at a glance the first version it was added.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ssh-slaves-plugin] (JENKINS-25522) Cannot launch slave with user different than jenkins user after upgrading to Jenkins 1.589
















































Alan Yang
 resolved  JENKINS-25522 as Not A Defect


Cannot launch slave with user different than jenkins user after upgrading to Jenkins 1.589
















I resolved my issue.

I had a couple of issues that culminated in the authentication exception:
1) The credential ID in credentials.xml did not match the one Jenkins was trying to use. I resolved this by configuring the slave node and just hitting save. This refreshed the ID
2) I am confused about this resolution, but the private key credential was previously using the user@slave's private key directly entered. This was invalid as it should be jenkin@master's private key. Somehow, the former input was working prior to update.





Change By:


Alan Yang
(10/Nov/14 8:48 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cli] (JENKINS-18627) NullPointerException in Jenkins CLI















































Jesse Glick
 commented on  JENKINS-18627


NullPointerException in Jenkins CLI















Rather, in 1.540.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [matrix-project-plugin] (JENKINS-24608) Test result link displays twice on matrix project page

2014-11-10 Thread kelsey.steinb...@libertymutual.com (JIRA)













































  
Watertight Door
 edited a comment on  JENKINS-24608


Test result link displays twice on matrix project page
















I'm seeing this occur, too.  FWIW, I'm using Jenkins 1.588, xUnit 1.92, and the Matrix Plugin 1.4
Actually, I commented on this issue without correctly reading it first.  My issue is NOT related to the matrix project plug-in – I am seeing this with a free-style project. Sorry ...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [promoted-builds-plugin] (JENKINS-25526) Add mask password feature to the promotion plugin















































Kelsey Steinbeck
 created  JENKINS-25526


Add mask password feature to the promotion plugin















Issue Type:


Improvement



Assignee:


Unassigned


Components:


promoted-builds-plugin



Created:


10/Nov/14 8:22 PM



Description:


It would be nice to run a cmd during the promoted build step that included credentials but there is no way to mask passwords. It would be nice if you could mask password in the promotion step.




Project:


Jenkins



Priority:


Minor



Reporter:


Kelsey Steinbeck

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure

2014-11-10 Thread vjura...@java.net (JIRA)















































vjuranek
 commented on  JENKINS-25392


Post Build Steps still running regardless of Pre Step Groovy Script failure















Hi,
groovy plugin preserves the contract of BuildStep#perform method, see groovy.java L117. I'm afraind there won't be any update unless you provide more details why you think this is a bug in groovy plugin or move it to the right component.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-publisher-plugin] (JENKINS-2786) ClassCastException when posting external job results

2014-11-10 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-2786


ClassCastException when posting external job results















Integrated in  jenkins_main_trunk #3811
 JENKINS-2786 Makes no sense for Computer.currentComputer to return MasterComputer when not on an executor thread. (Revision 0b0b868805e43d5b7bcafbdf22a59960a3baeeb0)

 Result = SUCCESS
jesse glick : 0b0b868805e43d5b7bcafbdf22a59960a3baeeb0
Files : 

	core/src/main/java/hudson/model/Computer.java





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [script-security-plugin] (JENKINS-25524) SandboxInterceptorTest "templates" test failure blocking compilation















































SCM/JIRA link daemon
 commented on  JENKINS-25524


SandboxInterceptorTest "templates" test failure blocking compilation















Code changed in jenkins
User: Jesse Glick
Path:
 src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovyCallSiteSelector.java
 src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovyCallSiteSelectorTest.java
 src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java
http://jenkins-ci.org/commit/script-security-plugin/a2c56252ec334d07e59f0c998e9c61324ad6baad
Log:
  [FIXED JENKINS-25524] Wrong overload of PrintWriter.print was sometimes being selected, at random.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [script-security-plugin] (JENKINS-25524) SandboxInterceptorTest "templates" test failure blocking compilation
















































SCM/JIRA link daemon
 resolved  JENKINS-25524 as Fixed


SandboxInterceptorTest "templates" test failure blocking compilation
















Change By:


SCM/JIRA link daemon
(10/Nov/14 8:15 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-25515) Jabber can not send message

2014-11-10 Thread benoit.donne...@gmail.com (JIRA)















































Benoit Donneaux
 commented on  JENKINS-25515


Jabber can not send message















Works like a charm on our test build server.
Thumbs up: this plugin is awesome.

This been said, you might have a closer look to what might happen when an error like this one is blocking.
Because it looks like a new connection is opened for each reconnect.
After a while, we've seen jenkins online with 6 sessions, even if we can't interact with any of them.
But I guess it could/should be another issue... Or not at all.

Thanks anyway.
Anything else to be tested before the next release?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-25525) Add support for the git clone timeout option

2014-11-10 Thread nico.mommae...@gmail.com (JIRA)















































Nico Mommaerts
 started work on  JENKINS-25525


Add support for the git clone timeout option
















Change By:


Nico Mommaerts
(10/Nov/14 7:48 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-dsl-plugin] (JENKINS-25525) Add support for the git clone timeout option

2014-11-10 Thread nico.mommae...@gmail.com (JIRA)















































Nico Mommaerts
 created  JENKINS-25525


Add support for the git clone timeout option















Issue Type:


Bug



Assignee:


Nico Mommaerts



Components:


job-dsl-plugin



Created:


10/Nov/14 7:48 PM



Description:


Xml should look like 


true
20
blah






Project:


Jenkins



Priority:


Minor



Reporter:


Nico Mommaerts

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [script-security-plugin] (JENKINS-25524) SandboxInterceptorTest "templates" test failure blocking compilation















































Jesse Glick
 started work on  JENKINS-25524


SandboxInterceptorTest "templates" test failure blocking compilation
















Change By:


Jesse Glick
(10/Nov/14 7:39 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [script-security-plugin] (JENKINS-25524) SandboxInterceptorTest "templates" test failure blocking compilation















































Jesse Glick
 commented on  JENKINS-25524


SandboxInterceptorTest "templates" test failure blocking compilation















This is working fine for me under

Linux jglick-t520 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux  java version "1.7.0_67"  Java(TM) SE Runtime Environment (build 1.7.0_67-b0  Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

I believe GroovyCallSiteSelector.staticMethod is failing to deterministically pick the most specific overload.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables

2014-11-10 Thread jstarb...@scisolutions.com (JIRA)















































Jon Starbird
 commented on  JENKINS-25501


Results not being propagated to ENV variables















You can use Batch or Powershell or pretty much anything that can access Environment variables.
For example if you put his into a Windows batch script and run it you'll get the values for all the WARNINGS variables.

SET WARNINGS

That will list them out in Jenkins console for the build.

Or you can use the Jenkins tokens in a build Email and email them to yourself. 
To test I just used both, ${WARNINGS_COUNT}  and ${ENV,var="WARNING_COUNT"}  with a text tag before each one and then just waited for an email. 
Of course you also need something to have Warnings in it. 

I used a previous build log that had MSBuild warnings in it. Then set the Warnings scanner to use the file instead of the workspace.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multiple-scms-plugin] (JENKINS-25523) Multiple SCMs Plugin doesn't work with Mercurial since 1.588

2014-11-10 Thread sergeygri...@mail.ru (JIRA)















































Sergey Grinev
 updated  JENKINS-25523


Multiple SCMs Plugin doesn't work with Mercurial since 1.588
















Change By:


Sergey Grinev
(10/Nov/14 7:31 PM)




Description:


I've upgraded from jenkins 1.
576
585
 and all jobs with Multiple SCM plugin fails with next exception:FATAL: org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState cannot be cast to hudson.plugins.mercurial.MercurialTagActionjava.lang.ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState cannot be cast to hudson.plugins.mercurial.MercurialTagAction	at hudson.plugins.mercurial.MercurialSCM.determineChanges(MercurialSCM.java:603)	at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:552)	at hudson.scm.SCM.checkout(SCM.java:484)	at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118)	at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)	at hudson.model.Run.execute(Run.java:1759)	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)	at hudson.model.ResourceController.execute(ResourceController.java:89)	at hudson.model.Executor.run(Executor.java:240)N.b.:* New job with Multiple SCM plugin fails same way.* Mercurial plugin works correctly



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cvs-plugin] (JENKINS-23234) cvs update hang when recursive symlink in directory















































SCM/JIRA link daemon
 commented on  JENKINS-23234


cvs update hang when recursive symlink in directory















Code changed in jenkins
User: James Coleman
Path:
 src/main/java/hudson/scm/AbstractCvs.java
http://jenkins-ci.org/commit/cvs-plugin/8574c853d2399f325bb58a767e6a7bfc606cb5ac
Log:
  cvs-plugin part of fix for JENKINS-23234: jenkins cvs update hang when recursive symlink in directory. use logger not print to stderr





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cvs-plugin] (JENKINS-23234) cvs update hang when recursive symlink in directory















































SCM/JIRA link daemon
 commented on  JENKINS-23234


cvs update hang when recursive symlink in directory















Code changed in jenkins
User: James Coleman
Path:
 src/main/java/hudson/scm/AbstractCvs.java
http://jenkins-ci.org/commit/cvs-plugin/60209053457903e23458d6170ac1b4409104a5d6
Log:
  cvs-plugin part of fix for JENKINS-23234: jenkins cvs update hang when recursive symlink in directory. ignore symlinks like the major cvs clients.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cvs-plugin] (JENKINS-23234) cvs update hang when recursive symlink in directory















































SCM/JIRA link daemon
 commented on  JENKINS-23234


cvs update hang when recursive symlink in directory















Code changed in jenkins
User: James Coleman
Path:
 src/main/java/hudson/scm/AbstractCvs.java
http://jenkins-ci.org/commit/cvs-plugin/273ee9b71512492d50fe192659c546ad4ac964e1
Log:
  cvs-plugin part of fix for JENKINS-23234: update after review: add curlies for if, simplify and remove references to issue in log output and comments, use listener.error in case of exception when checking for symlink.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cvs-plugin] (JENKINS-23234) cvs update hang when recursive symlink in directory















































SCM/JIRA link daemon
 commented on  JENKINS-23234


cvs update hang when recursive symlink in directory















Code changed in jenkins
User: Michael Clarke
Path:
 src/main/java/hudson/scm/AbstractCvs.java
http://jenkins-ci.org/commit/cvs-plugin/496b0f23fc85e4941be8bc5c46b88d7728d32700
Log:
  Merge pull request #31 from Gaoithe/fix-jenkins-23234_ignore_symlinks

JENKINS-23234 Prevent infinite recursion on symlink resolution during CVS checkout


Compare: https://github.com/jenkinsci/cvs-plugin/compare/7c5f8e917274...496b0f23fc85




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [groovy-plugin] (JENKINS-9130) Add a dynamic parser to colorize and indent groovy textareas

2014-11-10 Thread vjura...@java.net (JIRA)
















































vjuranek
 resolved  JENKINS-9130 as Fixed


Add a dynamic parser to colorize and indent groovy textareas
















Closing as syntax highlighting is already present in groovy plugin (actually for pretty long time, since rel. 1.15)





Change By:


vjuranek
(10/Nov/14 7:23 PM)




Status:


Open
Resolved





Assignee:


Lucie Votypkova
vjuranek





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-publisher-plugin] (JENKINS-2786) ClassCastException when posting external job results















































SCM/JIRA link daemon
 commented on  JENKINS-2786


ClassCastException when posting external job results















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/Computer.java
http://jenkins-ci.org/commit/jenkins/0b0b868805e43d5b7bcafbdf22a59960a3baeeb0
Log:
  JENKINS-2786 Makes no sense for Computer.currentComputer to return MasterComputer when not on an executor thread.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [junit-plugin] (JENKINS-24006) Customize number of Junit test failures that affect weather















































Jesse Glick
 commented on  JENKINS-24006


Customize number of Junit test failures that affect weather















Mark Sinclair I would suggest you file a separate bug and mark it blocking this one using a JIRA link. I know nothing about the intended behavior of healthScaleFactory. I was merely fixing the problem in its configuration form.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-25505) After Upgrade jenkins to 1.587 cannot send message with jabber















































kutzi
 commented on  JENKINS-25505


After Upgrade jenkins to 1.587 cannot send message with jabber















Also possible that Smack API 4.x broke something which was working previously...
Does maybe your Jabber server use the older _jabber._tcp. name?
This seems to be broken in Smack 4.x. See https://github.com/igniterealtime/Smack/commit/2eb13f48d2a72af9f0e88c5b2d8a9881a655fa1b#commitcomment-8506196



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Kindly reply to the below email

2014-11-10 Thread Andrew Norris

Hi,

 

We would like to have a discussion with you to explore opportunities to work
with FuGenX on the Mobile application development, please do suggest a
suitable time slot to meet.  

 

If your primary goal is to generate revenue with your mobile app then
Contact us for a free quote.

 

"Winner of Deloitte Technology Fast 500 Asia Pacific 2012 & 2013"

Regards,

Andrew Norris | Technical Consultant

FuGenX Technologies Pvt. Ltd.

California | Dubai | London | Bangalore

USA (1) 213.995.8091 | 

E:   and...@ny.fugenx.com | W:
 www.fugenx.com |Skype Andrew. Norris1

Winner of Deloitte Technology Fast 50 India 2012 & 2013 | Winner of Deloitte
Technology Fast 500 Asia Pacific 2012 | ISO 9001:2008 Certified Company

 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [script-security-plugin] (JENKINS-25524) SandboxInterceptorTest "templates" test failure blocking compilation

2014-11-10 Thread jtklin...@yahoo.com (JIRA)















































James Klinect
 created  JENKINS-25524


SandboxInterceptorTest "templates" test failure blocking compilation















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


script-security-plugin



Created:


10/Nov/14 7:03 PM



Description:


When running "mvn install" on the latest tagged release version (script-security-1.9) from the GitHub repo, I get the listed error:

```
Tests in error:
  templates(org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptorTest): Scripts not permitted to use method java.io.PrintWriter print java.lang.String

Tests run: 46, Failures: 0, Errors: 1, Skipped: 2
```

Same result when building the trunk/master branch (I assume the dev version).

Please advise how to proceed, we are blocked on building this.  Something is amiss.




Environment:


Failed in the following two environments:



$ mvn -v

Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T06:51:42-07:00)

Maven home: /usr/local/Cellar/maven/3.2.2/libexec

Java version: 1.6.0_65, vendor: Apple Inc.

Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home

Default locale: en_US, platform encoding: MacRoman

OS name: "mac os x", version: "10.9.4", arch: "x86_64", family: "mac"



$ mvn -v

/home/y/libexec/maven/bin/mvn -v

Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)

Java version: 1.7.0_13

Java home: /home/y/libexec64/jdk1.7.0/jre

Default locale: en_US, platform encoding: UTF-8

OS name: "linux" version: "2.6.18-164.el5" arch: "amd64" Family: "unix"




Project:


Jenkins



Priority:


Blocker



Reporter:


James Klinect

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [multiple-scms-plugin] (JENKINS-25523) Multiple SCMs Plugin doesn't work with Mercurial since 1.588

2014-11-10 Thread sergeygri...@mail.ru (JIRA)















































Sergey Grinev
 created  JENKINS-25523


Multiple SCMs Plugin doesn't work with Mercurial since 1.588















Issue Type:


Bug



Assignee:


Kevin Bell



Components:


multiple-scms-plugin



Created:


10/Nov/14 7:00 PM



Description:


I've upgraded from jenkins 1.576 and all jobs with Multiple SCM plugin fails with next exception:

FATAL: org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState cannot be cast to hudson.plugins.mercurial.MercurialTagAction
java.lang.ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState cannot be cast to hudson.plugins.mercurial.MercurialTagAction
	at hudson.plugins.mercurial.MercurialSCM.determineChanges(MercurialSCM.java:603)
	at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:552)
	at hudson.scm.SCM.checkout(SCM.java:484)
	at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
	at hudson.model.Run.execute(Run.java:1759)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)

N.b.:

	New job with Multiple SCM plugin fails same way.
	Mercurial plugin works correctly






Environment:


jenkins 1.588

Mercurial plugin 1.51

Multiple SCM plugin 0.3




Project:


Jenkins



Priority:


Major



Reporter:


Sergey Grinev

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [icon-shim-plugin] (JENKINS-25498) Inappropriate use of GString

2014-11-10 Thread dan...@beckweb.net (JIRA)













































  
Daniel Beck
 edited a comment on  JENKINS-25498


Inappropriate use of GString
















Tom: I have a chatlog around somewhere where I asked you about that, maybe that has more detail.

Update: Unfortunately not. [2014-08-30T01:19:33+0200] <+danielbeck> https://github.com/jenkinsci/icon-shim-plugin/blob/master/icon-set/src/main/java/org/jenkins/ui/icon/IconSet.java#L88 GString?
[2014-08-30T01:20:25+0200] <+danielbeck> What do you need Groovy strings for?
[2014-08-30T01:20:40+0200]  danielbeck: trying to remember
[2014-08-30T01:21:01+0200]  danielbeck: oh I think it was wrt jexl
[2014-08-30T01:21:38+0200]  danielbeck: forget exactly but it's needed sometimes... otherwise not resolved



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [icon-shim-plugin] (JENKINS-25498) Inappropriate use of GString

2014-11-10 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-25498


Inappropriate use of GString















Tom: I have a chatlog around somewhere where I asked you about that, maybe that has more detail.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables

2014-11-10 Thread ullrich.haf...@gmail.com (JIRA)















































Ulli Hafner
 commented on  JENKINS-25501


Results not being propagated to ENV variables















Ok thanks. I'll first try to add a test case to our acceptance test suite https://github.com/jenkinsci/acceptance-test-harness. 
What would be the best way to verify that the tokens are correctly set? How can one access these tokens, (I never consumed them yet)? 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-12097) Using Jabber Plugin with Google Talk logs VCARD Exception















































kutzi
 updated  JENKINS-12097


Using Jabber Plugin with Google Talk logs VCARD Exception
















Change By:


kutzi
(10/Nov/14 6:42 PM)




Summary:


Trying to Use
Using
 Jabber Plugin
 for
 with
 Google Talk
 Throws
 logs
 VCARD Exception



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-25515) Jabber can not send message















































kutzi
 commented on  JENKINS-25515


Jabber can not send message















This looks like a bug in the Smack library parsing VCards, which is also reported elsewhere:
http://stackoverflow.com/questions/26752285/android-asmack-vcard-classcastexception-while-calling-vcard-loadconn


I added a workaround to just ignore the error, so that the connection works at least. Would you be willing to test it?

https://dl.dropboxusercontent.com/u/25863594/jabber.hpi



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [junit-plugin] (JENKINS-24006) Customize number of Junit test failures that affect weather

2014-11-10 Thread msincl...@juniper.net (JIRA)















































Mark Sinclair
 commented on  JENKINS-24006


Customize number of Junit test failures that affect weather















It appears I'm not getting an accurate health report out of Junit.

I am running Junit version 1.2 (the health amplification factor fix is in).

The problem I am seeing is I don't see the weather report changing, it is always reporting 100% from Junit.  I tried different settings the amplification factor, but get the same result, always 100% health.  I created a job with only 1 test in it, Junit reports the test as failing, and it shows up in my trend graph.  Everything else with Junit seems to be working.

The weather is reported sunny with 1 test failing out of a total of 1 test 100% health.  The build is reported as unstable, but the weather is sunny.  I expect the health/weather to be 0% from Junit because 100% of the tests are failing.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes















































SCM/JIRA link daemon
 commented on  JENKINS-25241


svn+ssh checkout fails on remote nodes















Code changed in jenkins
User: Jesse Glick
Path:
 pom.xml
http://jenkins-ci.org/commit/subversion-plugin/38af37043e4a587bc2f6d57b44abd18be7cd6427
Log:
  Merge pull request #102 from daniel-beck/JENKINS-25241

[FIXED JENKINS-25241] Sync trilead SSH with core
(cherry picked from commit 98210443ba3b8ac337df2be4357d34fa2ec9eb4c)





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ssh-slaves-plugin] (JENKINS-25522) Cannot launch slave with user different than jenkins user after upgrading to Jenkins 1.589















































Alan Yang
 updated  JENKINS-25522


Cannot launch slave with user different than jenkins user after upgrading to Jenkins 1.589
















Change By:


Alan Yang
(10/Nov/14 6:10 PM)




Description:


The slaves on our project using credentials with a username different than the Jenkins user receive the following error:[11/10/14 11:25:16] [SSH] Opening SSH connection to hostname.com:22.ERROR: Server rejected the 1 private key(s) for builder (credentialId:21cdf000-1ffd-49d3-8984-e664cc3cf2cd/method:publickey)[11/10/14 11:25:16] [SSH] Authentication failed.hudson.AbortException: Authentication failed.	at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1178)	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:701)	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696)	at java.util.concurrent.FutureTask.run(FutureTask.java:262)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)	at java.lang.Thread.run(Thread.java:744)[11/10/14 11:25:16] Launch failed - cleaning up connection[11/10/14 11:25:16] [SSH] Connection closed.
This began occurring after upgrading jenkins with "yum upgrade jenkins." The configuration of slaves and credentials worked prior to upgrade.
I have tried downgrading Jenkins as well as each of the plugins, but
 there was no change
 continue to receive the error
.Here are the things I have tried/verified:* SSHing as jenkins user to slave as user@slave works from command line* Recreating credentials and slaves* Was able to reproduce on a different slave as a different user



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ssh-slaves-plugin] (JENKINS-25522) Cannot launch slave with user different than jenkins user after upgrading to Jenkins 1.589















































Alan Yang
 updated  JENKINS-25522


Cannot launch slave with user different than jenkins user after upgrading to Jenkins 1.589
















Change By:


Alan Yang
(10/Nov/14 6:08 PM)




Description:


The slaves on our project using credentials with a username different than the Jenkins user receive the following error:[11/10/14 11:25:16] [SSH] Opening SSH connection to hostname.com:22.ERROR: Server rejected the 1 private key(s) for builder (credentialId:21cdf000-1ffd-49d3-8984-e664cc3cf2cd/method:publickey)[11/10/14 11:25:16] [SSH] Authentication failed.hudson.AbortException: Authentication failed.	at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1178)	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:701)	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696)	at java.util.concurrent.FutureTask.run(FutureTask.java:262)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)	at java.lang.Thread.run(Thread.java:744)[11/10/14 11:25:16] Launch failed - cleaning up connection[11/10/14 11:25:16] [SSH] Connection closed.I have tried downgrading Jenkins as well as each of the plugins, but there was no change.
Here are the things I have tried/verified:* SSHing as jenkins user to slave as user@slave works from command line* Recreating credentials and slaves* Was able to reproduce on a different slave as a different user



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings-plugin] (JENKINS-25501) Results not being propagated to ENV variables

2014-11-10 Thread jstarb...@scisolutions.com (JIRA)















































Jon Starbird
 commented on  JENKINS-25501


Results not being propagated to ENV variables















I tried the ENV method and without it. Neither works.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ssh-slaves-plugin] (JENKINS-25522) Cannot launch slave with user different than jenkins user after upgrading to Jenkins 1.589















































Alan Yang
 created  JENKINS-25522


Cannot launch slave with user different than jenkins user after upgrading to Jenkins 1.589















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


ssh-slaves-plugin



Created:


10/Nov/14 6:04 PM



Description:


The slaves on our project using credentials with a username different than the Jenkins user receive the following error:

[11/10/14 11:25:16] [SSH] Opening SSH connection to hostname.com:22.
ERROR: Server rejected the 1 private key(s) for builder (credentialId:21cdf000-1ffd-49d3-8984-e664cc3cf2cd/method:publickey)
[11/10/14 11:25:16] [SSH] Authentication failed.
hudson.AbortException: Authentication failed.
	at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1178)
	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:701)
	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)
[11/10/14 11:25:16] Launch failed - cleaning up connection
[11/10/14 11:25:16] [SSH] Connection closed.

I have tried downgrading Jenkins as well as each of the plugins, but there was no change.




Environment:


Versions



Jenkins: 1.589

Credentials Plugin: 1.18

SSH Agent Plugin: 1.5

SSH Credentials Plugin: 1.10

SSH Plugin: 1.9



Jenkins slave OS: CentOS 5.8 (required for build environment)

Jenkins master OS: CentOS 6.5




Project:


Jenkins



Priority:


Major



Reporter:


Alan Yang

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [junit-plugin] (JENKINS-9980) Add the "Publish JUnit test result report" option to maven job configuration page

2014-11-10 Thread lorelei.mccol...@gmail.com (JIRA)















































Lorelei McCollum
 commented on  JENKINS-9980


Add the "Publish JUnit test result report" option to maven job configuration page















Any update here, sounds like a pretty simple thing to add
We could use this too

the xunit plugin is allowed here, but that plugin has lots of log errors



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes















































SCM/JIRA link daemon
 commented on  JENKINS-25241


svn+ssh checkout fails on remote nodes















Code changed in jenkins
User: Jesse Glick
Path:
 pom.xml
http://jenkins-ci.org/commit/subversion-plugin/98210443ba3b8ac337df2be4357d34fa2ec9eb4c
Log:
  Merge pull request #102 from daniel-beck/JENKINS-25241

[FIXED JENKINS-25241] Sync trilead SSH with core


Compare: https://github.com/jenkinsci/subversion-plugin/compare/25c5faff774f...98210443ba3b




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes















































SCM/JIRA link daemon
 commented on  JENKINS-25241


svn+ssh checkout fails on remote nodes















Code changed in jenkins
User: Daniel Beck
Path:
 pom.xml
http://jenkins-ci.org/commit/subversion-plugin/ba9aa68eb310274a7309a544c6fddffbf28d2339
Log:
  [FIXED JENKINS-25241] Sync trilead SSH with core





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes
















































SCM/JIRA link daemon
 resolved  JENKINS-25241 as Fixed


svn+ssh checkout fails on remote nodes
















Change By:


SCM/JIRA link daemon
(10/Nov/14 5:55 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [icon-shim-plugin] (JENKINS-25498) Inappropriate use of GString















































Jesse Glick
 commented on  JENKINS-25498


Inappropriate use of GString















Yes please dig up the original justification for this because it seems wrong. It also sounds like KK’s warning anticipated JENKINS-25499 exactly.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext-plugin] (JENKINS-25521) How to fix 'stapler-class is deprecated' warning?

2014-11-10 Thread davida2...@java.net (JIRA)















































davida2009
 created  JENKINS-25521


How to fix 'stapler-class is deprecated' warning?















Issue Type:


Bug



Assignee:


Alex Earl



Components:


email-ext-plugin



Created:


10/Nov/14 5:48 PM



Description:


I am running Jenkins 1.588. My system log shows many warnings of this type:


Nov 10, 2014 3:02:21 PM WARNING org.kohsuke.stapler.RequestImpl$TypePair convertJSON
'stapler-class' is deprecated: hudson.plugins.emailext.plugins.trigger.FixedTrigger

Nov 10, 2014 3:02:21 PM WARNING org.kohsuke.stapler.RequestImpl$TypePair convertJSON
'stapler-class' is deprecated: hudson.plugins.emailext.plugins.recipients.DevelopersRecipientProvider

Nov 10, 2014 3:02:21 PM WARNING org.kohsuke.stapler.RequestImpl$TypePair convertJSON
'stapler-class' is deprecated: hudson.plugins.emailext.plugins.recipients.CulpritsRecipientProvider

Nov 10, 2014 3:02:21 PM WARNING org.kohsuke.stapler.RequestImpl$TypePair convertJSON
'stapler-class' is deprecated: hudson.plugins.emailext.plugins.recipients.ListRecipientProvider


How can I fix this please?




Project:


Jenkins



Priority:


Minor



Reporter:


davida2009

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch

2014-11-10 Thread rmundkow...@ets.org (JIRA)













































  
robert mundkowsky
 edited a comment on  JENKINS-25172


GIT_SSH not always used for git fetch
















I agree, JENKINS-20941 is closer match for the error I am seeing. I would note, that I thought they had fixed JENKINS-20941 since there was a Pull Request, but after reading the Pull Request, seems the fix was not complete.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch

2014-11-10 Thread rmundkow...@ets.org (JIRA)















































robert mundkowsky
 commented on  JENKINS-25172


GIT_SSH not always used for git fetch















I agree, JENKINS-20941 is closer match for the error I am seeing. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [matrix-project-plugin] (JENKINS-24608) Test result link displays twice on matrix project page















































Watertight Door
 commented on  JENKINS-24608


Test result link displays twice on matrix project page















I'm seeing this occur, too.  FWIW, I'm using Jenkins 1.588, xUnit 1.92, and the Matrix Plugin 1.4



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option

2014-11-10 Thread pal...@perforce.com (JIRA)















































Paul Allen
 commented on  JENKINS-25341


Improve reconcile by using -m option















The latest stable build is here:

https://jenkins.ci.cloudbees.com/job/plugins/job/p4-plugin/77/org.jenkins-ci.plugins$p4/

You could download the '.hpi' file and install it manually.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [scripttrigger-plugin] (JENKINS-25520) Polling error sometimes (needs reboot)

2014-11-10 Thread blaineyo...@ge.com (JIRA)

Blaine Young
created JENKINS-25520

Polling error sometimes (needs reboot)

Issue Type:

Bug

Assignee:

Gregory Boissinot

Components:

scripttrigger-plugin

Created:

10/Nov/14 5:16 PM

Description:

We get the following error at the bottom of the scripttrigger log:

[ERROR] - Polling error...

With no evidence that it tried to run the script. The Polling error happens every time afterwards until Jenkins is restarted. I haven't seen any logs describing what the error is or why it's happening.

We've rebooted our server so that we can continue working. This problem is not reproducible. It has happened 3 times in the past 6 months (the last 2 times were within the last two weeks). When you're ready to work on it, we will keep the problem around when it happens again for debugging purposes.

Environment:

Scripttrigger v. 0.31

Envinject v. 1.89

Jenkins ver. 1.554.2

Arch: x86_64

Scientific Linux version 6.3.1

Java version: 1.7.0_25

OpenJDK Runtime: rhel-2.3.10.3.el6_4-x86_64

Only a master node with other machines that are used via ssh to execute tests (not Jenkins slaves, just ssh).

Project:

Jenkins

Priority:

Major

Reporter:

Blaine Young

[JIRA] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option

2014-11-10 Thread morne.joub...@u-blox.com (JIRA)















































Morne Joubert
 commented on  JENKINS-25341


Improve reconcile by using -m option















how do i grab the fix ?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch













































  
Mark Waite
 edited a comment on  JENKINS-25172


GIT_SSH not always used for git fetch
















robert mundkowsky I think your case is more like JENKINS-20941. I interpreted this bug report as not involving submodules, and failing sometimes when it passed at other times. The case you're describing is that submodules never use credentials to perform their update. That is described in JENKINS-20941 (and as far as I know, is still a bug or a known limitation).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jobconfighistory-plugin] (JENKINS-25456) POSTing to existing job config.xml results in 'java.io.IOException: Failed to persist config.xml'

2014-11-10 Thread j_carl...@apple.com (JIRA)

Jake Carlson
commented on JENKINS-25456

POSTing to existing job config.xml results in 'java.io.IOException: Failed to persist config.xml'

We've finally resolved the issue. TL;DR: Include a value in the 'name' node when POSTing config.xml to update a job. Not including it when creating the job will work just fine.

Here's what was happening:

We weren't setting a value for the 'name' node in the config.xml on initial job creation or job update. The job name is passed in via a GET parameter on job creation, and presumably Jenkins uses that parameter to set the name of the job (make sense). However, when updating the config.xml for a job, the absence of the 'name' node value in the config.xml caused Jenkins to rename the job to 'jobs'.

We have quite a few jobs and so the job being silently renamed was not noticed. When we rebooted Jenkins, we noticed that the renamed jobs magically appeared. I started following some discussions about job configs not being loaded back into memory without issuing a 'reload' command. Sure enough, issuing the reload command 'restored' (or so we thought at the time) the job's config in memory. (What appears really to have been happening is that Jenkins was silently autocorrecting the job names based the directory name and ignoring the blank 'name' node in the job's config.xml.)

We did a clean install of Jenkins without all the existing jobs and POSTed an update to a job config.xml directly in cURL and were finally able to notice that Jenkins was actually renaming the job to 'jobs.' That put us on to the trail of troubleshooting the 'name' node and on a hunch we included a value even though creating a job worked fine in its absence. And the update worked just fine.

So this is not a bug per se with Jenkins but IMO the error checking could definitely be improved upon. IMO POSTing an updated config.xml should throw an error if the 'name' node doesn't exist OR if the 'name' node doesn't match the actual path to the config.xml being POSTed to. And renaming the job to 'jobs' kind of came out of left field (not sure WTF that is about).

[JIRA] [jobconfighistory-plugin] (JENKINS-25456) POSTing to existing job config.xml results in 'java.io.IOException: Failed to persist config.xml'

2014-11-10 Thread j_carl...@apple.com (JIRA)
















































Jake Carlson
 resolved  JENKINS-25456 as Fixed


POSTing to existing job config.xml results in 'java.io.IOException: Failed to persist config.xml'
















Change By:


Jake Carlson
(10/Nov/14 5:04 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch















































Mark Waite
 commented on  JENKINS-25172


GIT_SSH not always used for git fetch















robert mundkowsky I think your case is more line JENKINS-20941. I interpreted this bug report as not involving submodules, and failing sometimes when it passed at other times. The case you're describing is that submodules never use credentials to perform their update. That is described in JENKINS-20941 (and as far as I know, is still a bug or a known limitation).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [workflow-plugin] (JENKINS-25519) Rethrown NumberFormatException from exitStatus can cause DurableTaskStep.Execution.check to retry indefinitely















































Jesse Glick
 created  JENKINS-25519


Rethrown NumberFormatException from exitStatus can cause DurableTaskStep.Execution.check to retry indefinitely















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


workflow-plugin



Created:


10/Nov/14 4:57 PM



Description:


https://jenkins.ci.cloudbees.com/job/plugins/job/workflow-plugin/org.jenkins-ci.plugins.workflow$workflow-aggregator/572/testReport/junit/org.jenkinsci.plugins.workflow.steps/TimeoutStepTest/basic/ showed repeated warnings:


... org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution check
FINE: could not check .../workspace/p
java.io.IOException: corrupted content in .../workspace/p/.a883d971/jenkins-result.txt: java.lang.NumberFormatException: For input string: ""
	at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.exitStatus(FileMonitoringTask.java:136)
	at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.exitStatus(BourneShellScript.java:123)
	at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:188)
	at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:151)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NumberFormatException: For input string: ""
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	at java.lang.Integer.parseInt(Integer.java:504)
	at java.lang.Integer.parseInt(Integer.java:527)
	at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.exitStatus(FileMonitoringTask.java:134)
	... 10 more


Unclear what caused jenkins-result.txt to be empty rather than contain a number, but at any rate there is a problem in DurableTaskStep that it continued to recheck the workspace every 15s and never gave up. FileMonitoringController could perhaps mark this exception as "fatal" rather than "transient", but that leaves it open to a race condition if the exit status is still being checked while written. So it is probably the responsibility of the caller (check) to give up and mark the step failed if exitStatus repeatedly throws an exception. (As distinct from getWorkspace repeatedly being null, which is normal enough if the slave stays offline for a while.)




Project:


Jenkins



Labels:


robustness




Priority:


Minor



Reporter:


Jesse Glick

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch

2014-11-10 Thread rmundkow...@ets.org (JIRA)















































robert mundkowsky
 commented on  JENKINS-25172


GIT_SSH not always used for git fetch















I seem to have a similar problem.  The plugin seems to fail to use GIT_SSH when a "Recursively update submodules" is used. So basically, the parent module is checked out correctly then I get the following failure for for submodule checkout. Note I can use hte plugin to directly check the submodule out (hence the crednetials are correct) : 
> /usr/bin/git submodule update --init --recursive
FATAL: Command "/usr/bin/git submodule update --init --recursive" returned status code 1:
stdout: Initialized empty Git repository in /export/Apps/srater_recognizer.15.1/SRaterHome/SRater/ASR_Files/files/ELTeach/expunct/.git/

...
stderr: Permission denied (publickey).
fatal: The remote end hung up unexpectedly
Clone of 'ssh://git@xxx:7999/foo/bar.git' into submodule path 'Foo/bar' failed

hudson.plugins.git.GitException: Command "/usr/bin/git submodule update --init --recursive" returned status code 1:
stdout: Initialized empty Git repository in /somewhere/.git/

stderr: Permission denied (publickey).
fatal: The remote end hung up unexpectedly
Clone of 'ssh://git@xxx:7999/foo/bar.git' into submodule path 'Foo/bar' failed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure

2014-11-10 Thread omar.ahmad...@googlemail.com (JIRA)















































Omar Ahmad
 commented on  JENKINS-25392


Post Build Steps still running regardless of Pre Step Groovy Script failure















Hi, any updates around this?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jabber-plugin] (JENKINS-25505) After Upgrade jenkins to 1.587 cannot send message with jabber















































kutzi
 commented on  JENKINS-25505


After Upgrade jenkins to 1.587 cannot send message with jabber















I'd suspect that the DNS SRV setup for your XMPP server might not be correct. Check e.g. http://blog.teemu.im/2008/12/14/setting-your-srv-records-straight-for-xmpp/

Have you ruled out that nothing else in the infrastructure has changed?
Can you connect with a different XMPP client from the Jenkins host?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option