[JIRA] [core] (JENKINS-25533) "Restrict where this project can be run" removed/disabled after Save/Apply of Job Configuration
podskalsky created JENKINS-25533 "Restrict where this project can be run" removed/disabled after Save/Apply of Job Configuration Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Nov/14 7:34 AM Description: The host parameters for "Restrict where this project can be run" are disabled removed/disabled after Save/Apply of Job Configuration !!! The builds are running on any host not at the specified ones Environment: Jenkins ver. 1.589 Latest Plugins Solaris 10 Project: Jenkins Priority: Blocker Reporter: podskalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24581) tasks status icon not visible at overview of single task
podskalsky updated JENKINS-24581 tasks status icon not visible at overview of single task Change By: podskalsky (05/Sep/14 9:14 AM) Environment: jenkins 1.578 latest versions of core http://wiki.jenkins-ci.org/display/JENKINS/Batch + plugins Task+Plugin 1.17 latest chrome/firefox/ie8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24581) tasks status icon not visible at overview of single task
podskalsky commented on JENKINS-24581 tasks status icon not visible at overview of single task This is the plugin: http://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24581) tasks status icon not visible at overview of single task
podskalsky commented on JENKINS-24581 tasks status icon not visible at overview of single task jenkins 1.578 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24581) tasks status icon not visible at overview of single task
podskalsky updated JENKINS-24581 tasks status icon not visible at overview of single task Change By: podskalsky (05/Sep/14 6:13 AM) Environment: jenkins 1. 57 578 latest versions of core+pluginslatest chrome/firefox/ie8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24581) tasks status icon not visible at overview of single task
podskalsky created JENKINS-24581 tasks status icon not visible at overview of single task Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Attachments: 2014-09-04 14_01_07-tagging + release [Jenkins].png Components: core, tasks-plugin Created: 04/Sep/14 12:12 PM Description: The tasks status icon is not visible at overview of single task. I think before the big design updates they where visible. Environment: jenkins 1.57 latest versions of core+plugins latest chrome/firefox/ie8 Project: Jenkins Priority: Major Reporter: podskalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23921) new s layout doesn't work with IE8
podskalsky edited a comment on JENKINS-23921 new s layout doesn't work with IE8 21% of users in the world (June 2014) are still using IE8 http://en.wikipedia.org/wiki/Internet_Explorer_8#Adoption So I think IE8 support from Jenkins would be fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23921) new s layout doesn't work with IE8
podskalsky commented on JENKINS-23921 new s layout doesn't work with IE8 21% of users in the world (June 2014) are still using IE8 http://en.wikipedia.org/wiki/Internet_Explorer_8#Adoption This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23921) new s layout doesn't work with IE8
podskalsky commented on JENKINS-23921 new s layout doesn't work with IE8 Internet Explorer 8 is bound to the lifecycle of the Windows version it is installed on. IE8 for Windows7 it's still supported by Microsoft. (Many companies are still using this 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] [core] (JENKINS-23921) new s layout doesn't work with IE8
podskalsky created JENKINS-23921 new s layout doesn't work with IE8 Issue Type: Bug Assignee: Unassigned Components: core, gui Created: 22/Jul/14 9:44 AM Description: The new layout using s is not running at IE8. All boxes(menues,tables,...) are below each other and some fields are not visible. Project: Jenkins Priority: Critical Reporter: podskalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-22094) Promoted builds not picking up injected env settings as of 2.17 (2.15 is ok)
podskalsky commented on JENKINS-22094 Promoted builds not picking up injected env settings as of 2.17 (2.15 is ok) I would also need to have the defined environment variables from the https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin running he in the promoted additional build actions (shell). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [active-directory] (JENKINS-22669) login failed (timed out) after upgrade to 1.37 from 1.36
podskalsky commented on JENKINS-22669 login failed (timed out) after upgrade to 1.37 from 1.36 Same problem with newest active-directory-1.38 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
podskalsky edited a comment on JENKINS-22669 login failed after upgrade to 1.37 from 1.36 I have the same problem at my Solaris(sparc) system This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
podskalsky commented on JENKINS-22669 login failed after upgrade to 1.37 from 1.36 I have the same problem an my Solaris(sparc) system This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jiratestresultreporter] (JENKINS-22405) Error if the job has no testresults
podskalsky created JENKINS-22405 Error if the job has no testresults Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jiratestresultreporter Created: 28/Mar/14 10:40 AM Description: If there are no tests and test results (Maven project), than the configured Jira test result reporter has an error and the completed sucesfull build is marked as failed BUILD SUCCESSFUL Total time: 2 seconds [JiraTestResultReporter] [INFO] Examining test results... ERROR: Publisher JiraTestResultReporter.JiraReporter aborted due to exception java.lang.NullPointerException at JiraTestResultReporter.JiraReporter.perform(JiraReporter.java:106) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:742) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:714) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1030) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:663) at hudson.model.Run.execute(Run.java:1713) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Finished: FAILURE Environment: Solaris10 Project: Jenkins Priority: Major Reporter: podskalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky assigned JENKINS-21679 to Unassigned After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Change By: podskalsky (19/Feb/14 8:27 AM) Assignee: podskalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky assigned JENKINS-21679 to podskalsky After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Change By: podskalsky (19/Feb/14 8:27 AM) Assignee: podskalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky updated JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Change By: podskalsky (19/Feb/14 8:15 AM) Attachment: 2014-02-19 09_06_07-production_scripts Config [Jenkins].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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky commented on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Great 2.2 is now running Thanks for your quick support! But one more question ... look at attached new picture. I've still have the default "- none -" selection at Credentials field. All svn commands are running. Should I see here the used "old" Credentials, which are still in use and running? Do I have to change all the credentials in my 500 jobs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky edited a comment on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Here are some additional LOG messages ... it seems taht there is a problem with "Credentials" and "Role-based Authorization Strategy Plugin" ... where should I add "anonymous" (a default/alias User) at Credentials? Please look at pictures and Error.log at Attachments! Failed to instantiate Key[type=hudson.scm.SubversionSCM$DescriptorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, hudson.security.AccessDeniedException2: anonymous is missing the Credentials/ManageDomains permission at hudson.scm.SubversionSCM$DescriptorImpl.(Unknown Source) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky commented on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Also a test with 2.1 of that plugin faild This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky edited a comment on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Also a test with 2.1 of that plugin failed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky updated JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Change By: podskalsky (18/Feb/14 10:34 AM) Attachment: 2014-02-18 11_12_22-production_scripts Config [Jenkins].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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky updated JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Change By: podskalsky (18/Feb/14 10:34 AM) Attachment: 2014-02-18 11_25_06-Jenkins.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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky commented on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Here are some additional LOG messages ... it seems taht there is a problem with Credentials or Please look at pictures and Error.log at Attachments! Failed to instantiate Key[type=hudson.scm.SubversionSCM$DescriptorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, hudson.security.AccessDeniedException2: anonymous is missing the Credentials/ManageDomains permission at hudson.scm.SubversionSCM$DescriptorImpl.(Unknown Source) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky updated JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Change By: podskalsky (18/Feb/14 10:33 AM) Attachment: Error.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky created JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 06/Feb/14 8:03 AM Description: After update of svn-plugin to 2.0 all jobs lost Subversion Urls and it's not able to select Subversion at job config in chapter Source Code Management. All jobs are broken. Environment: Latest at Solaris Project: Jenkins Labels: subversion Priority: Blocker Reporter: podskalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18614) Config screen loading dialog permanently blocks config
podskalsky updated JENKINS-18614 Config screen loading dialog permanently blocks config Change By: podskalsky (04/Jul/13 6:39 AM) Priority: Major Blocker Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18614) Config screen loading dialog permanently blocks config
podskalsky updated JENKINS-18614 Config screen loading dialog permanently blocks config Change By: podskalsky (04/Jul/13 6:39 AM) Affects Version/s: current Environment: 1.521 - solaris 10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [gui] (JENKINS-18614) Config screen loading dialog permanently blocks config
podskalsky commented on JENKINS-18614 Config screen loading dialog permanently blocks config I have the same blocking point with the new 1.521 !!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-13682) Setenv Plugin and Batch Task Plugin no longer compatible?
podskalsky created JENKINS-13682: Summary: Setenv Plugin and Batch Task Plugin no longer compatible? Key: JENKINS-13682 URL: https://issues.jenkins-ci.org/browse/JENKINS-13682 Project: Jenkins Issue Type: Bug Components: batch-task Environment: Latest Jenkins + Latest Plugins + Batch Task Plugin 1.16 + Setenv Plugin 1.1 Reporter: podskalsky Assignee: Kohsuke Kawaguchi Priority: Blocker The variables configured at the Setenv Plugin are not existing at the Batch Task Plugin! Workaround: downgrade to the Batch Task Plugin 1.15 ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
