[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Christian Galsterer
commented on JENKINS-17508
The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Upgraded to 1.516 and the problem seems to be still there.
Artifacts located in ${jenkins_home}/jobs/${jobname}/modules/${moduleName}/builds/${build_number}/archive are not deleted after a build has been executed.
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/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-16680) Downstream project being triggered twice since installing v0.11 version of plugin
Thomas Fields commented on JENKINS-16680 Downstream project being triggered twice since installing v0.11 version of plugin Hi vjuranek, Any chance you can have a look at fixing this issue? 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/groups/opt_out.
[JIRA] [testng] (JENKINS-16665) should not show +0 when nothing has changed
kutzi commented on JENKINS-16665 should not show +0 when nothing has changed Why? 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/groups/opt_out.
[JIRA] [testng] (JENKINS-18185) TestNG plugin should be able to capture and display stdout/stderr of tests
kutzi created JENKINS-18185 TestNG plugin should be able to capture and display stdout/stderr of tests Issue Type: Improvement Assignee: nalin_makar Components: testng Created: 04/Jun/13 7:59 AM Description: The build in test report displays the standard output and standard error of tests in the test details (BTW: this does even seem to work, when redirecting stdout to a file as you can do in the maven.surefire-plugin) The TestNG plugin should be able to do the same Project: Jenkins Priority: Critical Reporter: 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/groups/opt_out.
[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Per J. Lund
commented on JENKINS-17508
The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Just want to comment that in my environment it works fine. Got 250GB disk space back.
In my env. the path to the archive is:
${jenkins_home}/jobs/${jobname}/modules/${moduleName}/builds/${build_timestamp}/archive
Do you really have a 'build_number' or 'build_timestamp' in the path before '/archive' ?
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/groups/opt_out.
[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Christian Galsterer commented on JENKINS-17508 The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503. you are correct it is a "build_timestamp" not a "build_number" 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/groups/opt_out.
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Wolf Wolfswinkel commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows Verified to work for me in 1.517. Thanks. 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-14797) SVN_URL and SVN_REVISION environment variables are missing
kutzi resolved JENKINS-14797 as Fixed SVN_URL and SVN_REVISION environment variables are missing Change By: kutzi (04/Jun/13 8:22 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-9795) Long Subversion Revision Numbers don't display correctly on Changes page
kutzi commented on JENKINS-9795 Long Subversion Revision Numbers don't display correctly on Changes page Is this still an issue in current Jenkins versions? 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/groups/opt_out.
[JIRA] [maven2] (JENKINS-10700) Maven3 builder is swallowing exceptions in reporters
kutzi commented on JENKINS-10700 Maven3 builder is swallowing exceptions in reporters olamy: any news on this one? I still think that this is kind of critical 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/groups/opt_out.
[JIRA] [core] (JENKINS-11885) parallelLoad on startup uses twice as many executors as CPUs
kutzi resolved JENKINS-11885 as Not A Defect parallelLoad on startup uses twice as many executors as CPUs Maybe not a good idea Change By: kutzi (04/Jun/13 8:26 AM) 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/groups/opt_out.
[JIRA] [core] (JENKINS-18186) Make 'revisions' list on the build details page collapsable
kutzi created JENKINS-18186 Make 'revisions' list on the build details page collapsable Issue Type: Improvement Assignee: Unassigned Components: core Created: 04/Jun/13 8:34 AM Description: We have a lot of svn locations in a single job. Therefore you have to scroll down quite a lot past the revisions list to get to the 'useful' information - i.e. failed tests and changelog. Would be good to collapse the revisions if there are too many - e.g. more than 5 BTW: maybe it makes sense to think about the ordering in the details page anyway. IMHO the most important information should come first and that is IMO all information needed to fix a failed build - i.e. test failures and changelog Project: Jenkins Priority: Major Reporter: 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-9795) Long Subversion Revision Numbers don't display correctly on Changes page
teetoivo commented on JENKINS-9795 Long Subversion Revision Numbers don't display correctly on Changes page This issue is still visible in 1.514. I haven't tested with anything more recent. 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18187) scm-sync-configuration: Posibility to exclude files/directories from syncing
Wolfgang Hauser created JENKINS-18187 scm-sync-configuration: Posibility to exclude files/directories from syncing Issue Type: Improvement Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 04/Jun/13 8:54 AM Description: To reduce the scm "noise" it may be good to be able to exclude some files from syncing. e. g. In our environment, the file hudson.plugins.disk_usage.DiskUsageProjectActionFactory.xml was synced every day, the changes reflect the current disc usage only this might be not necessary. Environment: Jenkins 1.517 Debian lenny Fix Versions: current Project: Jenkins Priority: Minor Reporter: Wolfgang Hauser 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-9795) Long Subversion Revision Numbers don't display correctly on Changes page
kutzi commented on JENKINS-9795 Long Subversion Revision Numbers don't display correctly on Changes page I've also revision numbers > 100,000 but cannot reproduce the problem - not on IE and not on Chrome. You're talking about the job/jobName/buildNumber/changes page, aren't you? Maybe a screenshot would be helpful. 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/groups/opt_out.
[JIRA] [core] (JENKINS-17043) job run page crashed with java.lang.ArrayIndexOutOfBoundsException
Edward Hartwell Goose updated JENKINS-17043 job run page crashed with java.lang.ArrayIndexOutOfBoundsException Change By: Edward Hartwell Goose (04/Jun/13 9:03 AM) Attachment: jenkinsexception.txt Attachment: jenkinsexception2.txt Attachment: no build history anymore.PNG Attachment: some build history.png 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/groups/opt_out.
[JIRA] [core] (JENKINS-17043) job run page crashed with java.lang.ArrayIndexOutOfBoundsException
Edward Hartwell Goose commented on JENKINS-17043 job run page crashed with java.lang.ArrayIndexOutOfBoundsException I have a similar experience. We get the following stack trace and failure whenever a build fails. From that point forward, the job shows no available builds or history and any builds will cause the failures seen in JENKINS-17044 (all the executors are dead). A restart of Jenkins puts everything back to normal, but we lose all the history of the jobs in the sidebar for the job. I've got two stack traces which I'll attach, plus a screenshot showing no build history. If I restart Jenkins, the build history sort of comes back - but not really. Again, screenshot attached. I can still access build history for jobs which succeeded via their URL, but jobs that failed get this 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18187) scm-sync-configuration: Posibility to exclude files/directories from syncing
Frédéric Camblor commented on JENKINS-18187 scm-sync-configuration: Posibility to exclude files/directories from syncing Not really in favor to add excludes because, to my POV, it will complexify things I would rather be in favor to be more restrictive in the BasicPluginsConfigScmSyncStrategy default implementation (see here) WDYT ? 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/groups/opt_out.
[JIRA] [core] (JENKINS-17043) job run page crashed with java.lang.ArrayIndexOutOfBoundsException
Edward Hartwell Goose edited a comment on JENKINS-17043 job run page crashed with java.lang.ArrayIndexOutOfBoundsException I have a similar experience. We get the following stack trace and failure whenever a build fails. From that point forward, the job shows no available builds or history and any builds will cause the failures seen in JENKINS-17044 (all the executors are dead). A restart of Jenkins puts everything back to normal, but we lose almost all the history of the jobs in the sidebar for the job. I've got two stack traces which I'll attach, plus a screenshot showing no build history after a crash. If I restart Jenkins, the build history sort of comes back - but not really. Again, screenshot attached. I can still access build history for jobs which succeeded via their URL, but jobs that failed get this 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/groups/opt_out.
[JIRA] [testlink] (JENKINS-18188) When connecting to TestLink, finding error ClassCastException
astrob astrob created JENKINS-18188 When connecting to TestLink, finding error ClassCastException Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: configuration_jenkins.png, error.png, screenshot_testlink.png Components: testlink Created: 04/Jun/13 9:09 AM Description: Hi all, I get this error message. The test plan is active and public. Besides I think my configuration is ok (because if I enter a wrong project name, the system displays the message that the project does not exist) It seems linked to JENKINS-17442 but I have the plugin 3.4 Jenkins - 1.502 Testlink - 1.9.6 Plugin Testlink - 3.4 Thanks Environment: Jenkins - 1.502 Testlink - 1.9.6 Plugin Testlink - 3.4 Project: Jenkins Priority: Major Reporter: astrob astrob 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/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-9259) Include promotion status in the JSON/XML for a build
Hua Zhang edited a comment on JENKINS-9259 Include promotion status in the JSON/XML for a build One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine. I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks: job/[jobname]/promotion/latest/[PromotionName]/api/json and eventually information of every promoted build: job/[jobname]/[JobBuildNumber]/promotion/[PromotionName]/promotionBuild/num/api/json But the response does not contain any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get. It would be nice if the following information could be exposed through remote access api: a) promotion status for each build, and/or b) a summary/history of all promotion builds with reference to the being promoted build number. 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/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-9259) Include promotion status in the JSON/XML for a build
Hua Zhang
edited a comment on JENKINS-9259
Include promotion status in the JSON/XML for a build
One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine.
I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks:
{{ job/[jobname]/promotion/latest/[PromotionName]/api/json}}
and eventually information of every promoted build:
{{ job/[jobname]/[JobBuildNumber]/promotion/[PromotionName]/promotionBuild/[PromotionBuildNumber]/api/json}}
But the response does not contain any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get.
It would be nice if the following information could be exposed through remote access api:
a) promotion status for each build, and/or
b) a summary/history of all promotion builds with reference to the being promoted build number.
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/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-18189) disk-usage pluging: separate configuration and history serialization into different files
Wolfgang Hauser created JENKINS-18189 disk-usage pluging: separate configuration and history serialization into different files Issue Type: Improvement Affects Versions: current Assignee: vjuranek Components: disk-usage Created: 04/Jun/13 9:15 AM Description: To be able to store only the configuration using scm-sync-configuration plugin, it may be good to separate the plugin configuration and data storage into different files. At the time, the disk usage history is saved together with the configuration. This causes a periodical update of the configuration file which was synced to the scm. (see also JENKINS-18187) To fit scm-sync-configuration naming conventions, the history may be named "hudson.plugins.disk_usage.DiskUsageProjectActionFactory.history". (*.xml was the configuration file indication for scm-sync-configuration in jenkins base directory) Environment: Jenkins 1.517 Debian lenny Fix Versions: current Project: Jenkins Priority: Major Reporter: Wolfgang Hauser 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/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-9259) Include promotion status in the JSON/XML for a build
Hua Zhang
edited a comment on JENKINS-9259
Include promotion status in the JSON/XML for a build
One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine.
I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks:
{{job/[jobname]/promotion/latest/[PromotionName]/api/json}}
and eventually information of every promoted build:
{{job/[jobname]/[JobBuildNumber]/promotion/[PromotionName]/promotionBuild/[PromotionBuildNumber]/api/json}}
But the response does not contain any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get.
It would be nice if the following information could be exposed through remote access api:
a) promotion status for each build, and/or
b) a summary/history of all promotion builds with reference to the being promoted build number.
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/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-9259) Include promotion status in the JSON/XML for a build
Hua Zhang edited a comment on JENKINS-9259 Include promotion status in the JSON/XML for a build One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine. I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks: job//promotion/latest//api/json and eventually information of every promoted build: job///promotion//promotionBuild//api/json But the response does not contain any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get. It would be nice if the following information could be exposed through remote access api: a) promotion status for each build, and/or b) a summary/history of all promotion builds with reference to the being promoted build number. 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/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-18189) disk-usage pluging: separate configuration and history serialization into different files
Wolfgang Hauser updated JENKINS-18189 disk-usage pluging: separate configuration and history serialization into different files Change By: Wolfgang Hauser (04/Jun/13 9:17 AM) Priority: Major Trivial 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18187) scm-sync-configuration: Posibility to exclude files/directories from syncing
Wolfgang Hauser commented on JENKINS-18187 scm-sync-configuration: Posibility to exclude files/directories from syncing In our case, it was more an issue of the disk usage plugin which doesn't separate data from configuration. But as there was (as I know) no naming convention/location for files storing data, every plugin may provide some .xml files not necessarily have to be synced in scm. My personal opinion was to give the users the freedom to configure whatever was possible. This make the things flexible and reduces maintenance. 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/groups/opt_out.
[JIRA] [git] (JENKINS-17629) Regression: git < 1.6.2 not supported anymore (failing clone due to existing workspace dir)
Eberhard Leba commented on JENKINS-17629 Regression: git < 1.6.2 not supported anymore (failing clone due to existing workspace dir) Jenkins 1.3.3 , Git plugin 1.3.0 Got the same problem on one of three build systems running in a matrix project. Each build slave has a different linux distro (RHEL6, SLES11, debian squeeze) It is failing on SLES11 x86_64 and succeeds on the other two. The target directory (work space) exists and is empty (no .git directory in it). Workaround: remove target directory, do manual git clone into it and run the Jenkins build again. Wipe out is turned off 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/groups/opt_out.
[JIRA] [memory-map] (JENKINS-18190) Shouldn't publisher be skipped if build is failure?
Bue Petersen created JENKINS-18190 Shouldn't publisher be skipped if build is failure? Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: memory-map Created: 04/Jun/13 9:39 AM Description: Like checkstyle, and other plugins, shouldn't memory-map skip publisher step if build result is failure? It creates a graph anyway, thought the map-file may be old or with errors? Project: Jenkins Priority: Minor Reporter: Bue Petersen 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18187) scm-sync-configuration: Posibility to exclude files/directories from syncing
Frédéric Camblor edited a comment on JENKINS-18187 scm-sync-configuration: Posibility to exclude files/directories from syncing It would be the case if the BasicPluginsConfigScmSyncStrategy would only define a white list (more restricted as today) of sync'ed xml files. Then, users could play with manual includes feature to add their own files they want to sync. 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/groups/opt_out.
[JIRA] [git] (JENKINS-17763) Git plugin "clean workspace" blows away private maven repository
Mark Waite updated JENKINS-17763 Git plugin "clean workspace" blows away private maven repository Change By: Mark Waite (04/Jun/13 9:55 AM) Description: When you select "Clean repository workspace", this executes the equivalentof 'git clean -fdx' in $WORKSPACEIf you have 'local maven repository' selected, then there is a maven repoin $WORKSPACE/.repository.So this option deletes cleans the whole repo repository workspace , which is not what is wanted.I'm not sure what the most reasonable fix is, though.Clearly 'git clean -fdx -e .repository' will probably work, but it's a bit... 'magic' 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18187) scm-sync-configuration: Posibility to exclude files/directories from syncing
Frédéric Camblor commented on JENKINS-18187 scm-sync-configuration: Posibility to exclude files/directories from syncing It would be the case if the BasicPluginsConfigScmSyncStrategy would only define a white list of sync'ed xml files. Then, users could play with manual includes feature to add their own files they want to sync. 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/groups/opt_out.
[JIRA] [memory-map] (JENKINS-18190) Shouldn't publisher be skipped if build is failure? (Praqma case 9443)
Bue Petersen updated JENKINS-18190 Shouldn't publisher be skipped if build is failure? (Praqma case 9443) Change By: Bue Petersen (04/Jun/13 10:09 AM) Summary: Shouldn't publisher be skipped if build is failure? (Praqma case 9443) 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/groups/opt_out.
[JIRA] [git] (JENKINS-17763) Git plugin "clean workspace" blows away private maven repository
kutzi commented on JENKINS-17763 Git plugin "clean workspace" blows away private maven repository This is the same as e.g. the subversion-plugin does and letting them behave in the same way is IMO a good thing. If you don't want this you can either checkout the git repository not to the root of the Jenkins workspace or put the Maven repository somewhere else. 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/groups/opt_out.
[JIRA] [batch-task] (JENKINS-13647) Environment variables from EnvInject plugin are not inherited/parsed by batch tasks
basharimovvv reopened JENKINS-13647 Environment variables from EnvInject plugin are not inherited/parsed by batch tasks Jenkins ver. 1.515 Environment Injector Plugin 1.86 Jenkins batch task plugin 1.17 Build describes env vars on "Prepare an environment for the run". There is injectedEnvVars.txt and there is the env var there. But run of batch task does not load them. Change By: basharimovvv (04/Jun/13 10:29 AM) Resolution: Fixed Status: Resolved Reopened 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/groups/opt_out.
[JIRA] [timestamper] (JENKINS-16778) Timestamper makes the build fail if the slave if put offline during the build.
stevengbrown resolved JENKINS-16778 as Fixed Timestamper makes the build fail if the slave if put offline during the build. Back from holiday. Released Timestamper 1.5.4 with this fix. Change By: stevengbrown (04/Jun/13 11:05 AM) Status: Reopened 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/groups/opt_out.
[JIRA] [envinject] (JENKINS-17688) Environment variable UI in job and API (https://jenkins/job/ServerBuild/4323/injectedEnvVars/api/json?pretty=true)
basharimovvv commented on JENKINS-17688 Environment variable UI in job and API (https://jenkins/job/ServerBuild/4323/injectedEnvVars/api/json?pretty=true) The issue can be reproduced on Jenkins ver. 1.515, plugin 1.86 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/groups/opt_out.
[JIRA] [envinject] (JENKINS-17688) Environment variable UI in job and API (https://jenkins/job/ServerBuild/4323/injectedEnvVars/api/json?pretty=true)
Petre Ghita commented on JENKINS-17688 Environment variable UI in job and API (https://jenkins/job/ServerBuild/4323/injectedEnvVars/api/json?pretty=true) It is again reproducible on Jenkins 1.517 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/groups/opt_out.
[JIRA] [timestamper] (JENKINS-17697) Different timestamp between short and full console log on timeout
stevengbrown resolved JENKINS-17697 as Duplicate Different timestamp between short and full console log on timeout Change By: stevengbrown (04/Jun/13 11:22 AM) Status: Open Resolved Resolution: Duplicate 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/groups/opt_out.
[JIRA] [timestamper] (JENKINS-17779) Timestamps incorrect in .../console when truncated
stevengbrown commented on JENKINS-17779 Timestamps incorrect in .../console when truncated The difference can sometimes be larger, e.g. JENKINS-17697. 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/groups/opt_out.
[JIRA] [timestamper] (JENKINS-17312) Additional option for showing elapsed time per line in the execution log
stevengbrown assigned JENKINS-17312 to Unassigned Additional option for showing elapsed time per line in the execution log I'm OK with this feature being added. But if your aim is to parse the data with a script, I suggest adding an argument to the /timestamps URL instead. Change By: stevengbrown (04/Jun/13 11:30 AM) Assignee: stevengbrown 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/groups/opt_out.
[JIRA] [core] (JENKINS-18191) After upgrading to 1.517 fingerprinting seems to hang
Dirk Kuypers created JENKINS-18191 After upgrading to 1.517 fingerprinting seems to hang Issue Type: Bug Assignee: Marc Sanfacon Components: core, fingerprint Created: 04/Jun/13 11:31 AM Description: After upgrading to 1.517 I was hit by a problem with fingerprinting. I am not sure if it is core related please reassign if appropriate. I am fingerprinting a file in the upstream build process, pack several 100 files and assembles via scm clone workspace plugin and start about 50 unit test jobs on a bunch of slaves. After testing the downstream unit test project fingerprints the same file to be able to track the changes of the upstream project. With 1.517 now it happens that the fingerprinting seems to hang so that the workspace can not be cleaned up after testing: 17:35:31 Recording fingerprints 17:35:31 No emails were triggered. 17:35:31 17:35:31 Deleting project workspace... 17:35:49 Cannot delete workspace: java.nio.file.FileSystemException: C:\WS\SscuMimoVar13Tests\ContestContinuous\contest_sw\Bin\Debug\CommonTypes.dll: The process cannot access the file because it is being used by another process. 17:35:49 17:35:49 Option not to fail the build is turned on, so let's continue 17:35:49 Notifying upstream projects of job completion 17:35:49 Finished: SUCCESS Starting the next test some time later on the same machine leads to a failure because the old workspace can not be deleted because the file to fingerprint is still "in use by another process". Downgrading to 1.516 fixes the problem for me (but I had to restart all the slave Services). The problem also occured on my master, it was not related to slaves only. 17:36:11 Started by upstream project "ContestContinuous" build number 16910 17:36:11 originally caused by: 17:36:11 Started by an SCM change 17:36:11 [EnvInject] - Loading node environment variables. 17:36:11 Building remotely on 1SP1-SLAVE8 in workspace C:\WS\SscuMimoVar13Tests 17:36:11 hudson.util.IOException2: remote file operation failed: C:\WS\SscuMimoVar13Tests at hudson.remoting.Channel@191b66bf:1SP1-SLAVE8 17:36:11 at hudson.FilePath.act(FilePath.java:901) 17:36:11 at hudson.FilePath.act(FilePath.java:878) 17:36:11 at hudson.FilePath.deleteContents(FilePath.java:1050) 17:36:11 at hudson.plugins.cloneworkspace.CloneWorkspaceSCM.checkout(CloneWorkspaceSCM.java:145) 17:36:11 at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) 17:36:11 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) 17:36:11 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) 17:36:11 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) 17:36:11 at hudson.model.Run.execute(Run.java:1576) 17:36:11 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 17:36:11 at hudson.model.ResourceController.execute(ResourceController.java:88) 17:36:11 at hudson.model.Executor.run(Executor.java:241) 17:36:11 Caused by: java.nio.file.FileSystemException: C:\WS\SscuMimoVar13Tests\ContestContinuous\contest_sw\Bin\Debug\CommonTypes.dll: The process cannot access the file because it is being used by another process. 17:36:11 17:36:11 at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) 17:36:11 at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) 17:36:11 at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) 17:36:11 at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) 17:36:11 at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) 17:36:11 at java.nio.file.Files.delete(Unknown Source) 17:36:11 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 17:36:11 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 17:36:11 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 17:36:11 at java.lang.reflect.Method.invoke(Unknown Source) 17:36:11 at hudson.Util.deleteFile(Util.java:237) 17:36:11 at hudson.Util.deleteRecursive(Util.java:305) 17:36:11 at hudson.Util.deleteContentsRecursive(Util.java:202)
[JIRA] [core] (JENKINS-18191) After upgrading to 1.517 fingerprinting seems to hang
Dirk Kuypers updated JENKINS-18191 After upgrading to 1.517 fingerprinting seems to hang Change By: Dirk Kuypers (04/Jun/13 11:33 AM) Environment: Windows 7 64 Bit/Windows 2008 Server R2 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/groups/opt_out.
[JIRA] [timestamper] (JENKINS-17312) Additional option for showing elapsed time per line in the execution log
stevengbrown edited a comment on JENKINS-17312 Additional option for showing elapsed time per line in the execution log I'm OK with this feature being added. But if your aim is to parse the data with a script, I suggest adding an argument to the /timestamps URL for that. 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/groups/opt_out.
[JIRA] [build-failure-analyzer] (JENKINS-15926) Build Failure Analyzer with Timestamper output ugly.
stevengbrown closed JENKINS-15926 as Fixed Build Failure Analyzer with Timestamper output ugly. Change By: stevengbrown (04/Jun/13 11: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/groups/opt_out.
[JIRA] [core] (JENKINS-17590) Builds fail because of "slave went offline during the build"
stevengbrown closed JENKINS-17590 as Duplicate Builds fail because of "slave went offline during the build" Change By: stevengbrown (04/Jun/13 11: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/groups/opt_out.
[JIRA] [timestamper] (JENKINS-17697) Different timestamp between short and full console log on timeout
stevengbrown closed JENKINS-17697 as Duplicate Different timestamp between short and full console log on timeout Change By: stevengbrown (04/Jun/13 11:49 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/groups/opt_out.
[JIRA] [timestamper] (JENKINS-17312) Additional option for showing elapsed time per line in the execution log
Marc Günther commented on JENKINS-17312 Additional option for showing elapsed time per line in the execution log Hi Rob, I understand your intention, I had the same idea when I first saw those new radio buttons. My comment was just about which output format feels more natural. Lets say I have this script: echo "Building software" sleep 300 echo "Building software finished, uploading to Nexus" sleep 20 echo "Upload finished" I would expect this output: 0:00:00 Building software 0:05:00 Building software finished, uploading to Nexus 0:00:20 Upload finished I guess because this looks more similar to the other output modes. With your version: 0:05:00 Building software 0:00:20 Building software finished, uploading to Nexus 0:00:00 Upload finished the Console couldn't output the first line immediately, but would have to wait the whole 5mins. Or the output would have to be non linear, i.e. print the echo first, and later prepend the timestamp in the front. Both feel not very desireable. Your version might be easier to parse, though. It all depends on what and when you output in your echo's, I guess 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/groups/opt_out.
[JIRA] [core] (JENKINS-18192) global search box doesn't remember entered text
Marc Günther created JENKINS-18192 global search box doesn't remember entered text Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Jun/13 12:41 PM Description: When I enter something in the global search field, and press return, I get a new page with the search result, and the search field is empty again. Expected: the search field should remember the string I just searched for, so I can easily change it, without having to type it in all over again. Project: Jenkins Priority: Trivial Reporter: Marc Günther 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-17369) SVNKit 1.6.7 has authentication bugs
Andreas Panagiotidis commented on JENKINS-17369 SVNKit 1.6.7 has authentication bugs @kutzi What are the duplicates of this issue that you mention? Please reference them. 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-9795) Long Subversion Revision Numbers don't display correctly on Changes page
teetoivo updated JENKINS-9795 Long Subversion Revision Numbers don't display correctly on Changes page Attached image shows revision number not fully visible on /job/jobName/changes page using IE8 with Jenkins 1.514. Only 5 digits are visible when the revisions have 6 or more digits. Change By: teetoivo (04/Jun/13 1:23 PM) Attachment: changes.jpg 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/groups/opt_out.
[JIRA] [cloudtest] (JENKINS-17986) CloudTest plug-in does not work on Windows
Luis Cardozo commented on JENKINS-17986 CloudTest plug-in does not work on Windows Excellent, I will be waiting for the fix, thanks a lot. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18193) NPE from ConfidentialStore.get
Jesse Glick created JENKINS-18193 NPE from ConfidentialStore.get Issue Type: Bug Assignee: Jesse Glick Components: core Created: 04/Jun/13 1:50 PM Description: Reported in 1.509.1: ... winstone.Logger logInternal WARNING: Untrapped Error in Servlet java.lang.NullPointerException at jenkins.security.ConfidentialStore.get(ConfidentialStore.java:66) at jenkins.security.ConfidentialKey.load(ConfidentialKey.java:47) at jenkins.security.HMACConfidentialKey.getKey(HMACConfidentialKey.java:125) at jenkins.security.HMACConfidentialKey.createMac(HMACConfidentialKey.java:112) at jenkins.security.HMACConfidentialKey.mac(HMACConfidentialKey.java:69) at jenkins.security.HMACConfidentialKey.mac(HMACConfidentialKey.java:85) at hudson.security.TokenBasedRememberMeServices2.makeTokenSignature(TokenBasedRememberMeServices2.java:51) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.autoLogin(TokenBasedRememberMeServices.java:240) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) 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:722) Probably a race condition: attempt to load a web page during startup, when the security realm has been set (as indicated by the call stack location in HudsonFilter) yet Jenkins.INSTANCE is still null. Can probably just ignore the Lookup in this case. Project: Jenkins Labels: startup exception Priority: Minor
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: src/test/resources/setup-rootless.xml http://jenkins-ci.org/commit/config-rotator-plugin/a47eb87dcdc877a7864592070746f8d94af30e4d Log: JENKINS-17830 Adding test 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/JENKINS17830.java http://jenkins-ci.org/commit/config-rotator-plugin/b29d7bcbdcd3eca0ab0eafb03adec33d3f1fd340 Log: JENKINS-17830 Updated test 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/JENKINS17830.java http://jenkins-ci.org/commit/config-rotator-plugin/cfc873d57c54c4c56b975868b8b186f76e70c12a Log: JENKINS-17830 Updated test 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: src/test/resources/setup-rootless.xml http://jenkins-ci.org/commit/config-rotator-plugin/cd361b72f25a6d7ef13ae97adad9ec4b92f39d29 Log: JENKINS-17830 Adding test 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: pom.xml src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/JENKINS17830.java src/test/resources/setup-rootless.xml http://jenkins-ci.org/commit/config-rotator-plugin/916ef57f6e9de0b2f47a8259230a9ad7edb9cf75 Log: JENKINS-17830 Adding test 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-18194) Config Rotator triggers, but nothing new is found, case 9366
Christian Wolfgang resolved JENKINS-18194 as Fixed Config Rotator triggers, but nothing new is found, case 9366 Change By: Christian Wolfgang (04/Jun/13 1:56 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: pom.xml src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/PrepareWorkspace.java http://jenkins-ci.org/commit/config-rotator-plugin/6f8754e1f0d70c3ba4cbea58061dd88612df3acf Log: JENKINS-17830 Updated prepare 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/JENKINS17830.java http://jenkins-ci.org/commit/config-rotator-plugin/a0854f0a5d1c515fa256a806a2325f67977680f0 Log: JENKINS-17830 Updated test 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: src/test/resources/setup-rootless.xml http://jenkins-ci.org/commit/config-rotator-plugin/1978c5cd206573ffb7442256c80c53ebe0d7ae87 Log: JENKINS-17830 Updating test setup for rootless components 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/JENKINS17830.java http://jenkins-ci.org/commit/config-rotator-plugin/8388224dfe16f041d924d9f357b8f3ef5c5e76eb Log: JENKINS-17830 Adding test 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/JENKINS17830.java http://jenkins-ci.org/commit/config-rotator-plugin/9eaf2389677d7424bd94fc2dc79981ad6c365bcf Log: JENKINS-17830 Updating test setup for rootless components 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: src/test/resources/setup-rootless.xml http://jenkins-ci.org/commit/config-rotator-plugin/c109ef355f2608a328d3e494e875db22f9ac1eb8 Log: JENKINS-17830 Updating test setup for rootless components 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
SCM/JIRA link daemon commented on JENKINS-17830 Config spec for ClearCase UCM is not created correctly, case 9184 Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/FB8790.java http://jenkins-ci.org/commit/config-rotator-plugin/90de886ee5238f389670b35a900cd3607dfa53e9 Log: JENKINS-17830 Updated test 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17830) Config spec for ClearCase UCM is not created correctly, case 9184
Christian Wolfgang resolved JENKINS-17830 as Fixed Config spec for ClearCase UCM is not created correctly, case 9184 Change By: Christian Wolfgang (04/Jun/13 1:57 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-18194) Config Rotator triggers, but nothing new is found, case 9366
Christian Wolfgang created JENKINS-18194 Config Rotator triggers, but nothing new is found, case 9366 Issue Type: Bug Assignee: Praqma Support Components: config-rotator Created: 04/Jun/13 1:52 PM Project: Jenkins Priority: Critical Reporter: Christian Wolfgang 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/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-17992) Posted deliver baselines are not found, case 9299
SCM/JIRA link daemon commented on JENKINS-17992 Posted deliver baselines are not found, case 9299 Code changed in jenkins User: Christian Wolfgang Path: pom.xml http://jenkins-ci.org/commit/clearcase-ucm-plugin/839f3e52b75fc09a7cbc324a70a47411482fef2b Log: [fix for JENKINS-17992] Updating backend deps 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/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-17993) Wrongful error message on failed update, case 9239
Christian Wolfgang resolved JENKINS-17993 as Fixed Wrongful error message on failed update, case 9239 Change By: Christian Wolfgang (04/Jun/13 2:44 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/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-17992) Posted deliver baselines are not found, case 9299
Christian Wolfgang resolved JENKINS-17992 as Fixed Posted deliver baselines are not found, case 9299 Change By: Christian Wolfgang (04/Jun/13 2:45 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/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-18101) Iteratively finding view private files, case 9368
Christian Wolfgang resolved JENKINS-18101 as Fixed Iteratively finding view private files, case 9368 Change By: Christian Wolfgang (04/Jun/13 2:44 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/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-18026) Baseline not loaded when paramerized, case 9320
SCM/JIRA link daemon commented on JENKINS-18026 Baseline not loaded when paramerized, case 9320 Code changed in jenkins User: Christian Wolfgang Path: src/main/java/net/praqma/hudson/scm/CCUCMScm.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/c2c017f7564c0fe62e6affd30a6d84c4785dcf0b Log: [fix for JENKINS-18026] Using loaded information 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/groups/opt_out.
[JIRA] [core] (JENKINS-18195) Plugin Wiki Website BUGGY
cforce created JENKINS-18195 Plugin Wiki Website BUGGY Issue Type: Bug Assignee: Unassigned Attachments: Zwischenablage01.jpg Components: core Created: 04/Jun/13 3:19 PM Description: The plugin wiki site is buggy. Project: Jenkins Priority: Blocker Reporter: cforce 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/groups/opt_out.
[JIRA] [redmine] (JENKINS-11865) Ato guess parameters: Global redmine server url path and get redmine project name from job name
cforce commented on JENKINS-11865 Ato guess parameters: Global redmine server url path and get redmine project name from job name There is also a post build action "Aggregate Redmine ticket metrics" which needs a API Key on job level. It would be most useful to be able to define jenkins wide a global api key so i can create a redmine service user jenkins can use in this jobs. Anaywaxy i would give this user's api only read rights. It should be optional to defeine the api key on job level again (overrdie) or required if there is no global api key already existing. 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/groups/opt_out.
[JIRA] [jabber] (JENKINS-9233) Builds hang on jabber notification when XMPP server is not responding
kutzi assigned JENKINS-9233 to Unassigned Builds hang on jabber notification when XMPP server is not responding Change By: kutzi (04/Jun/13 4:23 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/groups/opt_out.
[JIRA] [core] (JENKINS-18196) With lazy-build loading estimated build duration may become expensive
kutzi commented on JENKINS-18196 With lazy-build loading estimated build duration may become expensive See https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Job.java#L876 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/groups/opt_out.
[JIRA] [core] (JENKINS-18196) With lazy-build loading estimated build duration may become expensive
kutzi created JENKINS-18196 With lazy-build loading estimated build duration may become expensive Issue Type: Bug Assignee: kutzi Components: core, maven2 Created: 04/Jun/13 4:30 PM Description: With lazy-build loading the computation for the estimated duration may become expensive: it searches of the last 3 unstable (or better) builds to compute the runtime. In the (not very probable, but still possible) that there are a lot of builds and less than 3 have been unstable, it can be very expensive to lookup the builds. Limit the number to build to go back in time and maybe also consider failed builds in the calculation Project: Jenkins Priority: Major Reporter: 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/groups/opt_out.
[JIRA] [plugin] (JENKINS-18197) Content Encoding Error when trying to click on the "integration-status" link (Subversion Merge Plugin)
Kamal Ahmed created JENKINS-18197 Content Encoding Error when trying to click on the "integration-status" link (Subversion Merge Plugin) Issue Type: Bug Assignee: Unassigned Components: plugin, subversion Created: 04/Jun/13 4:44 PM Description: I am using Jenkins ver. 1.516, installed on Centos 6.4 with subversion merge plugin = 1.48, and running the job on a CentOs 6.4 Slave Virtual Machine ( VMWare ) When i click on the link "Integration Status" i get an error in the Firefox (version 20, on ubuntu 12.04) browser: Content Encoding Error The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression. Please contact the website owners to inform them of this problem. Environment: Jenkins ver. 1.516 Jenkins Master installed on Centos 6.4 Jenkins Slave in stalled on Centos 6.4 SVN Merge Plugin version 1.48 Firefox Browser version 20 installed on Ubuntu 12.04 Project: Jenkins Priority: Major Reporter: Kamal Ahmed 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/groups/opt_out.
[JIRA] [cloudtest] (JENKINS-17986) CloudTest plug-in does not work on Windows
msolnit commented on JENKINS-17986 CloudTest plug-in does not work on Windows Fixed in git, revision ee99d0a8644aa851a3aa54d515bc967b3d96c041. I'll publish a new version of the plug-in later today. 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/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-16534) Copy existing Job - Status Code: 500 - NullPointerException
rakesh jain commented on JENKINS-16534 Copy existing Job - Status Code: 500 - NullPointerException I am having a similar issue when trying to copy an existing job. Any updates on when a fix will be made available? I am using jenkins 1.512 Below is the exception. Status Code: 500 Exception: jenkins/mvn/GlobalMavenConfig Stacktrace: javax.servlet.ServletException: jenkins/mvn/GlobalMavenConfig at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.jav
[JIRA] [cloudtest] (JENKINS-17986) CloudTest plug-in does not work on Windows
Luis Cardozo commented on JENKINS-17986 CloudTest plug-in does not work on Windows Awesome...!!! I will try again when the fix is published, thanks for your collaboration 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/groups/opt_out.
[JIRA] [concurrent-build] (JENKINS-18198) Concurrent Build completion is blocked by in-progress earlier Build # of same build.
4 4 created JENKINS-18198 Concurrent Build completion is blocked by in-progress earlier Build # of same build. Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: concurrent-build Created: 04/Jun/13 5:09 PM Description: Details: When running a single build concurrently : ie build 9 and 10. If 10 completes before 9, the Jenkins dashboard still indicates that 10 is in progress. However when examining Build 10's status page, it indicates it has completed. The console for Build 10 is constantly polling as well, instead of indicating it has completed. This holds up an executor, which is a waste of resources. Expected behavior Build 10 should indicate that it's complete and that the executor is free. Additional Info: Build 9 is running a lengthy external java process via bat/shell Due Date: 11/Jun/13 12:00 AM Project: Jenkins Priority: Major Reporter: 4 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/groups/opt_out.
[JIRA] [concurrent-build] (JENKINS-18198) Concurrent Build completion is blocked by in-progress earlier Build # of same build.
4 4 commented on JENKINS-18198 Concurrent Build completion is blocked by in-progress earlier Build # of same build. Similar to issue https://issues.jenkins-ci.org/browse/JENKINS-16220 But not the same. 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/groups/opt_out.
[JIRA] [concurrent-build] (JENKINS-16220) With Concurrent Builds enabled, faster builds won't fully complete until slower builds are done.
4 4 edited a comment on JENKINS-16220 With Concurrent Builds enabled, faster builds won't fully complete until slower builds are done. Similar issue: https://issues.jenkins-ci.org/browse/JENKINS-18198 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/groups/opt_out.
[JIRA] [concurrent-build] (JENKINS-16220) With Concurrent Builds enabled, faster builds won't fully complete until slower builds are done.
4 4 commented on JENKINS-16220 With Concurrent Builds enabled, faster builds won't fully complete until slower builds are done. Similar issue: https://issues.jenkins-ci.org/browse/JENKINS-16220 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/groups/opt_out.
[JIRA] [concurrent-build] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
4 4 commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Happening in 1.515 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-17939) Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesn't exist.
Steven Deal commented on JENKINS-17939 Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesn't exist. I experienced this as well, both with the current code base as well as going back to the 1.3.3 time frame with 34c17d66dc3fae5cdd52efb387e4ae1e97a040d2. However, I found that if I removed the old plugin folder and the build-pipeline-plugin.jpi file, copied the new build-pipeline-plugin.hpi to the plugins folder, renamed as a jpi file. It deployed successfully. I don't know which of these steps were 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-17939) Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesn't exist.
Steven Deal edited a comment on JENKINS-17939 Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesn't exist. I experienced this as well, both with the current code base as well as going back to the 1.3.3 time frame with 34c17d66dc3fae5cdd52efb387e4ae1e97a040d2. However, I found that if I removed the old plugin folder and the build-pipeline-plugin.jpi file, copied the new build-pipeline-plugin.hpi to the plugins folder, renamed as a jpi file. It deployed successfully. I don't know which of these steps were the 'fix'. Actually, this did not work for the current head. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18199) Deadlock during delete of upstream/downstream projects
Cees Bos created JENKINS-18199 Deadlock during delete of upstream/downstream projects Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Jun/13 6:39 PM Description: We had a number of linked projects which could be removed. I opened multiple projects in multiple tabpages and deleted them. I did not get reaction of the server (timeout). Later on all kind of changes to jobs failed. The cron thread was blocked as well, so no new jobs were started. I was able to create a thread dump. Most methods hang on hudson.model.Project.getPublishersList() this is synchronized method. The deadlock message: "Handling POST /jenkins/job/cws-is-junit-l/doDelete : RequestHandlerThread20": waiting to lock Monitor@0x0c447fa8 (Object@0x000747c7aaf0, a hudson/model/FreeStyleProject), which is held by "Handling POST /jenkins/job/prepare-for-is-regressions/doDelete : RequestHandlerThread15" "Handling POST /jenkins/job/prepare-for-is-regressions/doDelete : RequestHandlerThread15": waiting to lock Monitor@0x0b3e3c68 (Object@0x000747ec1378, a hudson/model/FreeStyleProject), which is held by "Handling POST /jenkins/job/cws-is-junit-l/doDelete : RequestHandlerThread20" The 2 jobs are up and downstream jobs of eachother. Project: Jenkins Priority: Critical Reporter: Cees Bos 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/groups/opt_out.
[JIRA] [core] (JENKINS-11872) UnsatisfiedLinkError when installing as Windows service
Brian Brooks commented on JENKINS-11872 UnsatisfiedLinkError when installing as Windows service I'm encountering this problem on Windows Server 2008 as well. Any tips on how to resolve/workaround it? I noticed the same error occurred when I started Jenkins from a console windows like java -jar jenkins.war 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-12076) m2 Release Plugin lock builds
teilo commented on JENKINS-12076 m2 Release Plugin lock builds See inline help, or comments above. If unclear please use the mailing list. 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-12076) m2 Release Plugin lock builds
teilo closed JENKINS-12076 as Fixed m2 Release Plugin lock builds Change By: teilo (04/Jun/13 6:48 PM) 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/groups/opt_out.
[JIRA] [core] (JENKINS-10661) Impossible to assign the permission release using project based matrix security
teilo closed JENKINS-10661 as Fixed Impossible to assign the permission release using project based matrix security Change By: teilo (04/Jun/13 6:50 PM) 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-4958) add switch for -DdryRun=true
teilo closed JENKINS-4958 as Fixed add switch for -DdryRun=true Change By: teilo (04/Jun/13 6:51 PM) 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
teilo closed JENKINS-17264 as Duplicate m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject Change By: teilo (04/Jun/13 6:50 PM) 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-12812) dryRun switch failes
teilo closed JENKINS-12812 as Fixed dryRun switch failes Change By: teilo (04/Jun/13 6:52 PM) 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-16087) "Number of successful release builds to keep" option does not work
teilo closed JENKINS-16087 as Duplicate "Number of successful release builds to keep" option does not work Change By: teilo (04/Jun/13 6:53 PM) 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-12991) unable to install m2release plugin 0.9.0 or 0.9.1 on Hudson 2.2.0
teilo closed JENKINS-12991 as Fixed unable to install m2release plugin 0.9.0 or 0.9.1 on Hudson 2.2.0 Change By: teilo (04/Jun/13 6:53 PM) 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
teilo closed JENKINS-13465 as Fixed Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 Change By: teilo (04/Jun/13 6:53 PM) 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/groups/opt_out.
