[JIRA] [pretested-integration] (JENKINS-24907) HTML formatting in build description ( our case 12074 )
Jens Brejner updated JENKINS-24907 HTML formatting in build description ( our case 12074 ) Change By: Jens Brejner (29/Sep/14 11:14 AM) Summary: HTMLformattinginbuilddescription (ourcase12074) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-24907) HTML formatting in build description ( our case 12074 )
Jens Brejner commented on JENKINS-24907 HTML formatting in build description ( our case 12074 ) Have you checked against this issue https://issues.jenkins-ci.org/browse/JENKINS-22028 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-24285) Improve commit message (our case 11772)
Jens Brejner updated JENKINS-24285 Improve commit message (our case 11772) Change By: Jens Brejner (18/Aug/14 5:55 AM) Summary: Improvecommitmessage (ourcase11772) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin (our case 11771)
Jens Brejner updated JENKINS-23901 Job SCM changes are not valid after running plugin (our case 11771) Change By: Jens Brejner (18/Aug/14 5:56 AM) Summary: JobSCMchangesarenotvalidafterrunningplugin (ourcase11771) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-24284) In the commit message - don't write origin (our case 11769)
Jens Brejner updated JENKINS-24284 In the commit message - dont write origin (our case 11769) Change By: Jens Brejner (18/Aug/14 5:57 AM) Summary: Inthecommitmessage-dontwriteorigin (ourcase11769) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-24286) Plugin tries to delete origin/master (our case 11770)
Jens Brejner updated JENKINS-24286 Plugin tries to delete origin/master (our case 11770) Change By: Jens Brejner (18/Aug/14 5:57 AM) Summary: Plugintriestodeleteorigin/master (ourcase11770) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Jens Brejner commented on JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed These are my installed plugins: saferestart Safe Restart Plugin 0.3 description-setter description setter plugin 1.9 jquery jQuery plugin 1.7.2-1 analysis-coreStatic Analysis Utilities 1.57 javadoc Javadoc Plugin 1.2 htmlpublisherHTML Publisher plugin 1.3 xunitxUnit plugin1.90 pam-auth PAM Authentication plugin 1.1 warnings Warnings Plug-in4.40 parameterized-triggerParameterized Trigger plugin2.25 ci-game Continuous Integration game 1.20 clover Clover plugin 4.4.0 antisamy-markup-formatterOWASP Markup Formatter Plugin 1.2 ant Ant Plugin 1.2 matrix-auth Matrix Authorization Strategy Plugin1.2 jobConfigHistory Job Configuration History Plugin2.8 github GitHub plugin 1.9.1 subversion Subversion Plug-in 2.4.1 token-macro Token Macro Plugin 1.10 external-monitor-job External Monitor Job Type Plugin1.2 ws-cleanup Workspace Cleanup Plugin0.22 matrix-project Matrix Project Plugin 1.3 cvs CVS Plug-in 2.12 covcomplplot Coverage/Complexity Scatter Plot PlugIn 1.1.1 disk-usage disk-usage plugin 0.24 log-parser Log Parser Plugin 1.0.8 git-client GIT client plugin 1.10.1 scm-api SCM API Plugin 0.2 build-keeper-plugin Build Keeper Plugin 1.3 checkstyle Checkstyle Plug-in 3.39 text-finder TextFinder plugin 1.10 windows-slaves Windows Slaves Plugin 1.0 maven-plugin Maven Integration plugin2.6 ssh-credentials SSH Credentials Plugin 1.8 nodelabelparameter Node and Label parameter plugin 1.5.1 mapdb-apiMapDB API Plugin1.0.1.0 git GIT plugin 2.2.4 github-api GitHub API Plugin 1.56 ssh-agentSSH Agent Plugin1.5 jsunit JSUnit plugin 1.5 logging Logging Plugin 0.2.8 ghprbGitHub Pull Request Builder 1.14 tasksTask Scanner Plug-in4.39 ssh-slaves SSH Slaves plugin 1.6 ansicolorAnsiColor 0.4.0 multiple-scmsMultiple SCMs plugin0.3 violations Violations plugin 0.7.11 ircbot IRC Plugin 2.25 ldap LDAP Plugin 1.10.2 run-conditionRun Condition Plugin1.0 translation Translation Assistance plugin 1.11 ssh SSH plugin 2.4 instant-messaginginstant-messaging plugin1.29 jslint Box UK - JSLint 0.8.2 credentials Credentials Plugin 1.16.1 violation-columnsViolation Columns(List View Columns)1.6 mailer Mailer Plugin 1.10 Parameterized-Remote-Trigger Parameterized Remote Trigger Plugin 2.1.3
[JIRA] [core] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Jens Brejner
commented on JENKINS-23442
Jenkins 1.568 can not start when monitoring plugin is installed
Hi magnayn.
Try stopping the Jenkins service, then cd into ${JENKINS_HOME}/plugins and remove the file monitoring.jpi as well as monitoring directory.
Then start Jenkins, and reinstall monitoring plugin.
Report back your findings, then evernat get's something to work with. If you can send him your Jenkins log, it may be usefull too.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Jens Brejner commented on JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed Reproduced on Ubuntu 14.04, Jenkins 1.574 + latest monitoring plugin After installing the monitoring plugin, Jenkins does not complete startup as described above. Removing the plugin fixes. I use Oracle java version 1.7.0_65-b17 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-reloaded] (JENKINS-24009) Incorrect result status after Matrix rebuild (our case 11639 )
Jens Brejner updated JENKINS-24009 Incorrect result status after Matrix rebuild (our case 11639 ) Change By: Jens Brejner (30/Jul/14 9:13 AM) Summary: IncorrectresultstatusafterMatrixrebuild (ourcase11639) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [memory-map] (JENKINS-23734) (our case 11569 )Memory map plugin does not allow to enter absolute or relative path
Jens Brejner updated JENKINS-23734 (our case 11569 )Memory map plugin does not allow to enter absolute or relative path Change By: Jens Brejner (30/Jul/14 9:32 AM) Summary: (ourcase11569) Memorymapplugindoesnotallowtoenterabsoluteorrelativepath This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [memory-map] (JENKINS-23734) (our case 11569 )Memory map plugin does not allow to enter absolute or relative path
Jens Brejner commented on JENKINS-23734 (our case 11569 )Memory map plugin does not allow to enter absolute or relative path I will work with Per on this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-23540) Post build step not run and difficult to know why
Jens Brejner updated JENKINS-23540 Post build step not run and difficult to know why Change By: Jens Brejner (02/Jul/14 8:48 AM) Summary: (ourcase11519) Postbuildstepnotrunanddifficulttoknowwhy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-23540) Post build step not run and difficult to know why
Jens Brejner commented on JENKINS-23540 Post build step not run and difficult to know why Removing pseudolink to Praqma's internal tracker. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Jens Brejner commented on JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed It was probably 1.50.0, I had to remove it to be able to work. But please resolve case if you can not reproduce with current Jenkins version and latest plugin version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jens Brejner commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Hi Jonathan. A) Try opening the configuration of your "sdk_dev_cfg00" and the "build" projects - and save again (Because I see "Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered") B) Wrt to your build step, it Is type Windows Batch file - am I right ? C) Try change in change the commands: Build Step1, type windows batch: echo %WORKSPACE% Build Step2, type windows batch: dir Be aware that for some post-build step plugins, they can be ordered, and sometimes (depends on the plugin), subsequent steps are aborted if one fails The above two is just to verify both build steps are executed and not failing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jens Brejner commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Hi Jonathan. Thats right - matrix builds can be a bit of a pain, I avoid the as much as I can. Anyway, I will change the component and assignee for this, as it is not related to the component "component" Br Jens This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jens Brejner updated JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Change By: Jens Brejner (26/Jun/14 12:57 PM) Assignee: PraqmaSupport KohsukeKawaguchi Component/s: matrix-project Component/s: component This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jens Brejner commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Hi Jonathan. We need the job's config.xml: On Jenkins master's filesystem, browse to jenkins install folder\jobs\JOBNAME\ and post the config.xml from there BR Jens This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jens Brejner updated JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Change By: Jens Brejner (24/Jun/14 6:21 AM) Summary: (ourcase11519) Postbuildstepnotrunanddifficulttoknowwhy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jens Brejner commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Hi Jonathan. I am not sure it is related to the component component. Please post the complete, failing build log and the configuration of the project (config.xml). BR Jens This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23442) Jenkins 1.1568 can not start when monitoring plugin is installed
Jens Brejner created JENKINS-23442 Jenkins 1.1568 can not start when monitoring plugin is installed Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, monitoring Created: 16/Jun/14 11:16 AM Description: After upgrading to Jenkins version 1.568 it can not start. The following is the last entry in the log file no matter how long I wait. Exception in thread "Thread-3" java.lang.ClassCircularityError: java/util/logging/LogRecord at net.bull.javamelody.LoggingHandler.publish(LoggingHandler.java:109) at java.util.logging.Logger.log(Logger.java:616) at java.util.logging.Logger.doLog(Logger.java:641) at java.util.logging.Logger.log(Logger.java:730) at winstone.Logger.logInternal(Logger.java:157) at winstone.Logger.log(Logger.java:165) Stopping Jenkins again and deleting file ./plugins/monitoring.jpi and folder ./plugins/monitoring/ allows me to get Jenkins running again, so that can work as a workaround Environment: Jenkins installed as native package on Ubuntu 14.04. Java version: java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.7.0_60-b19 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation Project: Jenkins Priority: Critical Reporter: Jens Brejner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Jens Brejner updated JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed Change By: Jens Brejner (16/Jun/14 11:17 AM) Summary: Jenkins1. 1568 568 cannotstartwhenmonitoringpluginisinstalled This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-reloaded] (JENKINS-22964) Additional configuration selectors ( our Case 11475 )
Jens Brejner updated JENKINS-22964 Additional configuration selectors ( our Case 11475 ) Change By: Jens Brejner (16/Jun/14 11:31 AM) Summary: Additionalconfigurationselectors (ourCase11475) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-reloaded] (JENKINS-22966) Combination filters are not handled well ( our case 11480 )
Jens Brejner updated JENKINS-22966 Combination filters are not handled well ( our case 11480 ) Change By: Jens Brejner (16/Jun/14 12:10 PM) Summary: Combinationfiltersarenothandledwell (ourcase11480) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-23122) Cross-Site-Scripting (XSS) Vulnarability: Github Titles rendered unescaped to build description
Jens Brejner commented on JENKINS-23122 Cross-Site-Scripting (XSS) Vulnarability: Github Titles rendered unescaped to build description I see this issue too. Jenkins version 1.567 and ghprb plugin version 1.12 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-23122) Cross-Site-Scripting (XSS) Vulnarability: Github Titles rendered unescaped to build description
Jens Brejner commented on JENKINS-23122 Cross-Site-Scripting (XSS) Vulnarability: Github Titles rendered unescaped to build description I just found https://issues.jenkins-ci.org/browse/JENKINS-22028. As described html is escaped if you select Raw HTML under Configure Global Security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)
Jens Brejner commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) You are right - the administrator should do 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/d/optout.
[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)
Jens Brejner commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) Yes, the PR is ready the maintainers says they have no more comments, so it should be merged very soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)
Jens Brejner commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) Unfortunately not, that is in the hands of the maintainers. Meanwhile you can use the "dummy node" workaround. Create a slave, which actually is on the master itself, then polling will work again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)
Jens Brejner commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) Hi. Yes, the key issue is the combination of "polling requires workspace" and "no slave exists". I have been tied to other tasks the last couple of days, but will write a fix now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Jens Brejner commented on JENKINS-21394 Avoid queuing request for workspace while node is offline @Eric - which Git Plugin version do you have ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Jens Brejner commented on JENKINS-21394 Avoid queuing request for workspace while node is offline @Brian, just use the standard jenkins log output, and define a new logger for that name space. @David, Thank you, very much, changing CanRoam in the job's config.xml is probably a useful workaround. I will test your suggested change later this week, but I am at a customer right now, so it will not be 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/d/optout.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Jens Brejner commented on JENKINS-21394 Avoid queuing request for workspace while node is offline @Eric, how long has the master been running ? You can get this message the first 10 minutes it runs, because we allow some time for slaves to come online - and I assume that your slaves are online ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Jens Brejner commented on JENKINS-21394 Avoid queuing request for workspace while node is offline Thank you. What are you polling ? ( I mean which kind of SCM ? Subversion, git, ?) Would you mind to enable logging and log on AbstractProject ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm] (JENKINS-13234) Option to specify the view storage location - our case 8516
Jens Brejner
commented on JENKINS-13234
Option to specify the view storage location - our case 8516
Hi Iosif.
The original idea behind this case was to offer the ability to specify a name which is different from view. This would be implemented as a global configuration option for snapshot view folder name. Today the option is not available, any view CCUCM creates are located in the a job's workspace as ${workspace}\view\ As said, we can make a global configuration option with default value 'view', but whichever string is in the global configuration, will be used by all CCUCM jobs.
Your need is a bit different and as I understand it, it has nothing to do with the use of string 'view' for the local data representation. You need an option, where we change our use of the mkview command so we use -vws UNC-path instead of -stgloc -auto.
Do you see this as a global configuration option or as a per job option ? From my point of view I think we should arrange an online meeting and talk this through.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm] (JENKINS-13234) Option to specify the view storage location - our case 8516
Jens Brejner commented on JENKINS-13234 Option to specify the view storage location - our case 8516 Ok, now I think I understand, I will get back to you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm] (JENKINS-13234) Option to specify the view storage location - our case 8516
Jens Brejner commented on JENKINS-13234 Option to specify the view storage location - our case 8516 Hi Iosif. I do not think this has been implemented. Do you agree that we are talking about which view-server storage location should be used, and not about where in the local filesystem, the snapshot view will be created ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm] (JENKINS-13234) Option to specify the view storage location - our case 8516
Jens Brejner commented on JENKINS-13234 Option to specify the view storage location - our case 8516 Do you allow clients to be view-servers ? Personally I think that is very inconvenient seen from a ClearCase administrative point of view - but is an absolutely valid use. But I am still a bit confused, would you like to be able to control (change) the folder name 'view' which we create in the workspace root, or do you need to be able to use a different UNC path, as opposed to the one ClearCase gives you with cleartool mkview option -stgloc -auto ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-reloaded] (JENKINS-22535) Matrix Reloaded plugin overwrites existing builds (our case 11118 )
Jens Brejner updated JENKINS-22535 Matrix Reloaded plugin overwrites existing builds (our case 8 ) Change By: Jens Brejner (08/Apr/14 2:57 PM) Summary: MatrixReloadedpluginoverwritesexistingbuilds (ourcase8) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Jens Brejner started work on JENKINS-21394 Avoid queuing request for workspace while node is offline Change By: Jens Brejner (18/Feb/14 10:04 AM) Status: Open InProgress 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-21394) Avoid queuing request for workspace while node is offline
Jens Brejner resolved JENKINS-21394 as Fixed Avoid queuing request for workspace while node is offline created pull request with fix Change By: Jens Brejner (18/Feb/14 10:06 AM) Status: InProgress 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] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Jens Brejner commented on JENKINS-21394 Avoid queuing request for workspace while node is offline Pull request 1092 ( https://github.com/jenkinsci/jenkins/pull/1092 ) created 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
Jens Brejner closed JENKINS-17993 as Fixed Wrongful error message on failed update, case 9239 Missing information... Don't know what to fix, closing Change By: Jens Brejner (18/Feb/14 12:27 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] [drmemory] (JENKINS-21628) Jenkins workspace environment variables are not expanded in command line passed to drmemory ( our case 21628)
Jens Brejner updated JENKINS-21628 Jenkins workspace environment variables are not expanded in command line passed to drmemory ( our case 21628) Change By: Jens Brejner (03/Feb/14 2:07 PM) Summary: Jenkinsworkspaceenvironmentvariablesarenotexpandedincommandlinepassedtodrmemory (ourcase21628) 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] [drmemory] (JENKINS-21628) Environment variables not expanded in command line passed to drmemory ( our case 21628)
Jens Brejner commented on JENKINS-21628 Environment variables not expanded in command line passed to drmemory ( our case 21628) Changed subject line 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] [drmemory] (JENKINS-21628) Environment variables not expanded in command line passed to drmemory ( our case 21628)
Jens Brejner updated JENKINS-21628 Environment variables not expanded in command line passed to drmemory ( our case 21628) Change By: Jens Brejner (03/Feb/14 2:11 PM) Summary: Jenkinsworkspaceenvironment Environment variables are notexpandedincommandlinepassedtodrmemory(ourcase21628) 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] [drmemory] (JENKINS-21628) ( our case 21628 ) Environment variables not expanded in command line passed to drmemory
Jens Brejner updated JENKINS-21628 ( our case 21628 ) Environment variables not expanded in command line passed to drmemory Change By: Jens Brejner (03/Feb/14 2:13 PM) Summary: (ourcase21628) Environmentvariablesnotexpandedincommandlinepassedtodrmemory (ourcase21628) 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] [prqa] (JENKINS-21588) PRQA plugin runs if previous build steps failed ( praqma case 10681 )
Jens Brejner updated JENKINS-21588 PRQA plugin runs if previous build steps failed ( praqma case 10681 ) Change By: Jens Brejner (31/Jan/14 9:23 AM) Summary: PRQApluginrunsifpreviousbuildstepsfailed (praqmacase10681) 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] [ec2] (JENKINS-19943) EC2 plugin cannot connect to slaves outside us-east-1 on new AWS accounts (using EC2-VPC)
Jens Brejner resolved JENKINS-19943 as Fixed EC2 plugin cannot connect to slaves outside us-east-1 on new AWS accounts (using EC2-VPC) Change By: Jens Brejner (31/Jan/14 10:36 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] [ec2] (JENKINS-21182) EC2 Plugin: EC2 instance starts but waits forever
Jens Brejner resolved JENKINS-21182 as Fixed EC2 Plugin: EC2 instance starts but waits forever fixed together with 19943 Change By: Jens Brejner (31/Jan/14 10:35 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] [core] (JENKINS-19026) Node log fails to update
Jens Brejner assigned JENKINS-19026 to Unassigned Node log fails to update Change By: Jens Brejner (01/Aug/13 12:48 PM) Assignee: PraqmaSupport 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-19026) Node log fails to update
Jens Brejner updated JENKINS-19026 Node log fails to update Change By: Jens Brejner (01/Aug/13 12:47 PM) Component/s: core Component/s: logging 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-18537) java.lang.ArrayIndexOutOfBoundsException when trying to save data
Jens Brejner updated JENKINS-18537 java.lang.ArrayIndexOutOfBoundsException when trying to save data Change By: Jens Brejner (01/Jul/13 7:39 AM) Assignee: PraqmaSupport Component/s: core Component/s: component This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18537) java.lang.ArrayIndexOutOfBoundsException when trying to save data
Jens Brejner commented on JENKINS-18537 java.lang.ArrayIndexOutOfBoundsException when trying to save data This case is not related to "component" because does not existk - or at least it should not exist, we are trying to get rid of it. 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-18507) some command can't exit in the execute windows batch command (praqma case 9630)
Jens Brejner commented on JENKINS-18507 some command cant exit in the execute windows batch command (praqma case 9630) try to break it into multiple commands: PSEXEC -accepteula GPS68 SCHTASKS /QUERY /TN "\GOPP\SDT" 21 "%TEMP%\FILE.TXT" findstr "Disabled" "%TEMP%\FILE.TXT" echo. ehco Here comes file contents: type "%TEMP%\FILE.TXT" 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-18507) some command can't exit in the execute windows batch command (praqma case 9630)
Jens Brejner commented on JENKINS-18507 some command cant exit in the execute windows batch command (praqma case 9630) Can you send me the job log ? And or contents of "%TEMP%\FILE.TXT" 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-18507) some command can't exit in the execute windows batch command (praqma case 9630)
Jens Brejner commented on JENKINS-18507 some command cant exit in the execute windows batch command (praqma case 9630) Hi dzy dzy. I do not think there is any bug in this, but either PSEXEC or SCHTASK is waiting for some input Is the jenkins job / service running with your credentials or does it run as LocalSystem ? I am also wondering if your job is the actual job or are you testing PSEXEC ? If it the real job, and you want you jenkins, to check - on a remote machine - if the remote machine's scheduled task named SDT is disabled, I would suggest 2 different approaches to you: A) Install a jenkins slave on the remote machine, and create a job tied to that slave, the job shall then do what you wanted to do in the scheduled task or B) use schtasks with it's /S parameter: Parameter List: /Ssystem Specifies the remote system to connect to. /Uusername Specifies the user context under which schtasks.exe should execute. /Ppassword Specifies the password for the given user context. Prompts for input if omitted. 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] [component] (JENKINS-18507) some command can't exit in the execute windows batch command (praqma case 9630)
Jens Brejner updated JENKINS-18507 some command cant exit in the execute windows batch command (praqma case 9630) Change By: Jens Brejner (26/Jun/13 9:31 AM) Summary: somecommandcantexitintheexecutewindowsbatchcommand (praqmacase9630) 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] [logging] (JENKINS-18456) Jenkins Job Current Log Status ( our case 9603)
Jens Brejner updated JENKINS-18456 Jenkins Job Current Log Status ( our case 9603) Pseudo linking to internal tracker Change By: Jens Brejner (23/Jun/13 11:47 AM) Summary: JenkinsJobCurrentLogStatus (ourcase9603) 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] [logging] (JENKINS-15153) Custom logging template
Jens Brejner assigned JENKINS-15153 to Praqma Support Custom logging template Change By: Jens Brejner (20/Jun/13 8:59 AM) Assignee: ChristianWolfgang PraqmaSupport 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] [logging] (JENKINS-15153) Custom logging template (our case 9584)
Jens Brejner updated JENKINS-15153 Custom logging template (our case 9584) pseudo linking to internal tracker Change By: Jens Brejner (20/Jun/13 9:11 AM) Summary: Customloggingtemplate (ourcase9584) 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] [matrix-reloaded] (JENKINS-16591) Matrix Reloaded plugin - our case 8520
Jens Brejner commented on JENKINS-16591 Matrix Reloaded plugin - our case 8520 Hi Klaus. Thank you, we will try to reproduce, it sounds like rebuilding the project may the issue ? Best regards Jens Brejner 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-18244) Passwords should not be stored as clear text in config.xml and should not be printed out to the log (praqma case 9463)
Jens Brejner updated JENKINS-18244 Passwords should not be stored as clear text in config.xml and should not be printed out to the log (praqma case 9463) Change By: Jens Brejner (07/Jun/13 7:04 AM) Summary: Passwordsshouldnotbestoredascleartextinconfig.xmlandshouldnotbeprintedouttothelog(praqmacase9463) ) 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-18107) Warning sent to wrong log
Jens Brejner created JENKINS-18107 Warning sent to wrong log Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm Created: 28/May/13 9:23 AM Description: A SCM polling job, polling ClearCase UCM, in "poll self" mode, with "Create baseline" enabled. The following warning: CCUCM You cannot create a baseline in this mode is infrequently sent to the polling log, so it is easy to miss. It should be send to the build log, for each execution Project: Jenkins Priority: Trivial Reporter: Jens Brejner 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-18107) Warning sent to wrong log (our Case 9374)
Jens Brejner updated JENKINS-18107 Warning sent to wrong log (our Case 9374) Change By: Jens Brejner (28/May/13 9:38 AM) Summary: Warningsenttowronglog (ourCase9374) 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] [matrix-reloaded] (JENKINS-17964) NPE if one of the upstream builds is not found (our case 9294)
Jens Brejner updated JENKINS-17964 NPE if one of the upstream builds is not found (our case 9294) Pseudo linking into our tracker Change By: Jens Brejner (16/May/13 7:37 AM) Summary: NPEifoneoftheupstreambuildsisnotfound (ourcase9294) 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-17847) Exception when getting component (our case 9199)
Jens Brejner updated JENKINS-17847 Exception when getting component (our case 9199) Change By: Jens Brejner (07/May/13 10:58 AM) Summary: Exceptionwhengettingcomponent (ourcase9199) 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] [matrix-reloaded] (JENKINS-17748) Bubble links on matrix reloaded action have incorect url (our Case 9155)
Jens Brejner updated JENKINS-17748 Bubble links on matrix reloaded action have incorect url (our Case 9155) Pseudo linking Change By: Jens Brejner (26/Apr/13 11:08 AM) Summary: Bubblelinksonmatrixreloadedactionhaveincorecturl (ourCase9155) 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-17396) When a technical issue arise in the plugin itself the baseline should be untouched (our case 8915)
Jens Brejner started work on JENKINS-17396 When a technical issue arise in the plugin itself the baseline should be untouched (our case 8915) Change By: Jens Brejner (10/Apr/13 12:49 PM) Status: Open InProgress 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-17396) When a technical issue arise in the plugin itself the baseline should be untouched (our case 8915)
Jens Brejner closed JENKINS-17396 as Not A Defect When a technical issue arise in the plugin itself the baseline should be untouched (our case 8915) Change By: Jens Brejner (10/Apr/13 12: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] [clearcase-ucm] (JENKINS-17396) When a technical issue arise in the plugin itself the baseline should be untouched (our case 8915)
Jens Brejner resolved JENKINS-17396 as Not A Defect When a technical issue arise in the plugin itself the baseline should be untouched (our case 8915) We can not get more information from reporter, and on the description it the behaviour we want. If a view update fails we want to fail the build, and let that information be persisted on the baseline. If the view update or rebase or what ever is failing because somebody accidently cuts the network cable or whatever, all it takes is to change the promotion level of baseline, then it will be picked up again. Change By: Jens Brejner (10/Apr/13 12:53 PM) Status: InProgress Resolved Fix Version/s: current Resolution: NotADefect 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-17466) Graph configuration not effective until after another build (our case 8955)
Jens Brejner updated JENKINS-17466 Graph configuration not effective until after another build (our case 8955) Linking to our internal tracker Change By: Jens Brejner (04/Apr/13 9:02 AM) Summary: Graphconfigurationnoteffectiveuntilafteranotherbuild (ourcase8955) 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-17465) Missing data from bar chart (our case 8954)
Jens Brejner updated JENKINS-17465 Missing data from bar chart (our case 8954) Linking to our internal tracker Change By: Jens Brejner (04/Apr/13 9:03 AM) Summary: Missingdatafrombarchart (ourcase8954) 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] (JENKINS-17396) When a technical issue arise in the plugin itself the baseline should be untouched (our case 8915)
Jens Brejner updated JENKINS-17396 When a technical issue arise in the plugin itself the baseline should be untouched (our case 8915) pseudo-linking Change By: Jens Brejner (30/Mar/13 3:40 PM) Summary: Whenatechnicalissueariseinthepluginitselfthebaselineshouldbeuntouched (ourcase8915) 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] (JENKINS-17396) When a technical issue arise in the plugin itself the baseline should be untouched (our case 8915)
Jens Brejner commented on JENKINS-17396 When a technical issue arise in the plugin itself the baseline should be untouched (our case 8915) Hello Jenkinsuserfrance. Please let me know which jenkins version and which version you are using Best regards Jens Brejner Praqma 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] (JENKINS-17372) Error looking up function 'CreateSymbolicLinkW'
Jens Brejner created JENKINS-17372 Error looking up function CreateSymbolicLinkW Issue Type: Bug Assignee: Praqma Support Components: prqa Created: 26/Mar/13 9:08 PM Description: Issue reported here: https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-users/lYjRlqulBNQ Hi, I’ve updated to PRQA 1.2.0, since that I got following message: FATAL: Error looking up function 'CreateSymbolicLinkW': The specified procedure could not be found. java.lang.UnsatisfiedLinkError: Error looking up function 'CreateSymbolicLinkW': The specified procedure could not be found. at com.sun.jna.Function.init(Function.java:179) at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:347) at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:327) at com.sun.jna.Library$Handler.invoke(Library.java:203) at $Proxy33.CreateSymbolicLinkW(Unknown Source) at hudson.util.jna.Kernel32Utils.createSymbolicLink(Kernel32Utils.java:85) at hudson.Util.createSymlink(Util.java:1048) at hudson.model.Run.execute(Run.java:1573) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Mit freundlichen Grüßen / with best regards Klaus Kuhnert (Ext.) System SW development coordination BU Vehicle Dynamics and Controls Product Center Vehicle Electronic Architecture and Drivers Assistance Systems WABCO Vehicle Control Systems Am Lindener Hafen 21 30453 Hannover Germany Phone: +49 511 922 - 2910 Mobile: +49 170 428 4229 Fax: +49 511 922 42910 Email: klaus.kuhn...@wabco-auto.com Web: www.wabco-auto.com Project: Jenkins Priority: Major Reporter: Jens Brejner 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] (JENKINS-17372) Error looking up function 'CreateSymbolicLinkW' (our case 8907)
Jens Brejner updated JENKINS-17372 Error looking up function CreateSymbolicLinkW (our case 8907) Change By: Jens Brejner (26/Mar/13 9:11 PM) Summary: ErrorlookingupfunctionCreateSymbolicLinkW (ourcase8907) 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] (JENKINS-17372) Error looking up function 'CreateSymbolicLinkW' (our case 8908)
Jens Brejner updated JENKINS-17372 Error looking up function CreateSymbolicLinkW (our case 8908) Change By: Jens Brejner (26/Mar/13 9:13 PM) Summary: ErrorlookingupfunctionCreateSymbolicLinkW(ourcase 8907 8908 ) 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] (JENKINS-17229) Config Rotator does not trig on new baseline (our case 8789)
Jens Brejner created JENKINS-17229 Config Rotator does not trig on new baseline (our case 8789) Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: config-rotator Created: 15/Mar/13 2:14 PM Description: We use Jenkins version 1.502 and Config Rotator version 1.0.2. If a job is configured: and the baseline baseline has promotion level TESTED then this job will not trig on new baselines of that component with promotion level INITIAL. But if changing the promotion level for baseline baseline then the job trigger on new baselines. So when searching for new baselines the promotion level for the current baseline must not be used! Project: Jenkins Priority: Major Reporter: Jens Brejner 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] (JENKINS-17230) Unload component from Config Rotator job does not work (our case 8790)
Jens Brejner created JENKINS-17230 Unload component from Config Rotator job does not work (our case 8790) Issue Type: Bug Assignee: Praqma Support Components: config-rotator Created: 15/Mar/13 2:16 PM Description: The following is a screenshot from the configure page of a config rotator job. It is possible to Add a new component or delete an existing. But if deleting an existing component the component is not unloaded when running the Jenkins job again. This is an error. Project: Jenkins Priority: Major Reporter: Jens Brejner 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] (JENKINS-17019) Incompatible prqa plugin with older Jenkins version (our case 8751)
Jens Brejner updated JENKINS-17019 Incompatible prqa plugin with older Jenkins version (our case 8751) pseudo-linking to internal tracker Change By: Jens Brejner (01/Mar/13 2:11 PM) Summary: IncompatibleprqapluginwitholderJenkinsversion (ourcase8751) 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] (JENKINS-16487) Promotion Level being set to INITIAL - our case 8471
Jens Brejner assigned JENKINS-16487 to Praqma Support Promotion Level being set to INITIAL - our case 8471 Change By: Jens Brejner (27/Feb/13 8:29 AM) Assignee: JensBrejner PraqmaSupport 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] (JENKINS-16938) Information lost when build is stopped by user (our case 8705)
Jens Brejner updated JENKINS-16938 Information lost when build is stopped by user (our case 8705) pseudo linking to our tracker Change By: Jens Brejner (27/Feb/13 7:44 AM) Summary: Informationlostwhenbuildisstoppedbyuser (ourcase8705) 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] (JENKINS-14746) Use nothing to build (grey builds) if there is no new baselines
Jens Brejner assigned JENKINS-14746 to Praqma Support Use nothing to build (grey builds) if there is no new baselines our case 6843 Change By: Jens Brejner (19/Feb/13 8:49 AM) Assignee: BuePetersen PraqmaSupport 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] (JENKINS-14746) Use nothing to build (grey builds) if there is no new baselines, our case 8676
Jens Brejner updated JENKINS-14746 Use nothing to build (grey builds) if there is no new baselines, our case 8676 pseudo-linking to our internal tracker Change By: Jens Brejner (19/Feb/13 8:52 AM) Summary: Usenothingtobuild(greybuilds)ifthereisnonewbaselines ,ourcase8676 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] (JENKINS-14746) Use nothing to build (grey builds) if there is no new baselines, our case 6843
Jens Brejner updated JENKINS-14746 Use nothing to build (grey builds) if there is no new baselines, our case 6843 Change By: Jens Brejner (19/Feb/13 8:55 AM) Summary: Usenothingtobuild(greybuilds)ifthereisnonewbaselines,ourcase 8676 6843 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] (JENKINS-16704) Wrong file delimiters - our case 8584
Jens Brejner updated JENKINS-16704 Wrong file delimiters - our case 8584 Change By: Jens Brejner (08/Feb/13 2:21 PM) Summary: Wrongfiledelimiters -ourcase8584 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] (JENKINS-16371) Allow non composite baselines in posted deliver - our case 8514
Jens Brejner updated JENKINS-16371 Allow non composite baselines in posted deliver - our case 8514 pseudo linking Change By: Jens Brejner (05/Feb/13 12:20 PM) Summary: Allownoncompositebaselinesinposteddeliver -ourcase8514 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] (JENKINS-16422) Enabling 'Poll for posted deliveres' breaks the poll self method for all jobs - our case 8423
Jens Brejner updated JENKINS-16422 Enabling Poll for posted deliveres breaks the poll self method for all jobs - our case 8423 Linking to FB Change By: Jens Brejner (05/Feb/13 12:25 PM) Summary: EnablingPollforposteddeliveresbreaksthepollselfmethodforalljobs -ourcase8423 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] (JENKINS-16271) The list of changed files should be shown in a table format - our case 7857
Jens Brejner updated JENKINS-16271 The list of changed files should be shown in a table format - our case 7857 Change By: Jens Brejner (05/Feb/13 12:31 PM) Summary: Thelistofchangedfilesshouldbeshowninatableformat -ourcase7857 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] (JENKINS-16591) Matrix Reloaded plugin - our case 8520
Jens Brejner updated JENKINS-16591 Matrix Reloaded plugin - our case 8520 Pseudo-linking to our internal tracker Change By: Jens Brejner (03/Feb/13 6:11 PM) Summary: MatrixReloadedplugin -ourcase8520 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] (JENKINS-16591) Matrix Reloaded plugin - our case 8520
Jens Brejner resolved JENKINS-16591 as Not A Defect Matrix Reloaded plugin - our case 8520 Change By: Jens Brejner (03/Feb/13 6:13 PM) Status: Open Resolved Resolution: NotADefect 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] (JENKINS-16447) Fix polling display: Show ANY instead of null - our case 8449
Jens Brejner updated JENKINS-16447 Fix polling display: Show ANY instead of null - our case 8449 Change By: Jens Brejner (03/Feb/13 6:22 PM) Summary: Fixpollingdisplay:ShowANYinsteadofnull -ourcase8449 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] (JENKINS-16487) Promotion Level being set to INITIAL - our case 8471
Jens Brejner commented on JENKINS-16487 Promotion Level being set to INITIAL - our case 8471 Hi Ronan. Think we got it. Do you want to test with a snapshot version of the plugin ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15676) Self-Polling Recommendation and Description
Jens Brejner assigned JENKINS-15676 to Praqma Support Self-Polling Recommendation and Description Change By: Jens Brejner (01/Feb/13 8:07 AM) Assignee: ChristianWolfgang PraqmaSupport 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] (JENKINS-13234) Option to specify the view storage location
Jens Brejner assigned JENKINS-13234 to Praqma Support Option to specify the view storage location Change By: Jens Brejner (01/Feb/13 8:08 AM) Assignee: PraqmaSupport 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] (JENKINS-12931) Let ClearCase UCM plugin be able to have a different checkout path than view
Jens Brejner assigned JENKINS-12931 to Praqma Support Let ClearCase UCM plugin be able to have a different checkout path than view Change By: Jens Brejner (01/Feb/13 8:09 AM) Assignee: ChristianWolfgang PraqmaSupport 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] (JENKINS-16597) Test interaction
Jens Brejner created JENKINS-16597 Test interaction Issue Type: Task Affects Versions: current Assignee: Praqma Support Components: clearcase-ucm Created: 01/Feb/13 1:29 PM Description: Sorry this is actually just a dummy case, I need to test the integration to another system Environment: Remote Case system Project: Jenkins Priority: Trivial Reporter: Jens Brejner 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] (JENKINS-16597) Test interaction - our case 8524
Jens Brejner updated JENKINS-16597 Test interaction - our case 8524 Change By: Jens Brejner (01/Feb/13 1:31 PM) Summary: Testinteraction -ourcase8524 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.
