[JIRA] [terminal] (JENKINS-18057) Jenkins Plugin - Terminal Plugin - [JENKINS TERMINAL] ERROR: 405
kiy0taka closed JENKINS-18057 as Fixed Jenkins Plugin - Terminal Plugin - [JENKINS TERMINAL] ERROR: 405 Change By: kiy0taka (24/May/13 11:58 AM) Status: Resolved Closed Assignee: kiy0taka This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-16279) Parameter paths are not correctly calculated when master is running on Windows machine
kiy0taka resolved JENKINS-16279 as Fixed Parameter paths are not correctly calculated when master is running on Windows machine Change By: kiy0taka (10/Jan/13 10:07 PM) 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
[JIRA] (JENKINS-14345) Grails wrapper doesn't respect Project Base Directory
kiy0taka assigned JENKINS-14345 to kiy0taka Grails wrapper doesnt respect Project Base Directory Change By: kiy0taka (18/Jul/12 4:07 PM) Assignee: jeffg2one kiy0taka This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14345) Grails wrapper doesn't respect Project Base Directory
kiy0taka resolved JENKINS-14345 as Fixed Grails wrapper doesnt respect Project Base Directory Change By: kiy0taka (18/Jul/12 4:08 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
[JIRA] (JENKINS-13813) NullPointer after upgrading to 1.6
[
https://issues.jenkins-ci.org/browse/JENKINS-13813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kiy0taka reassigned JENKINS-13813:
--
Assignee: kiy0taka (was: jeffg2one)
NullPointer after upgrading to 1.6
--
Key: JENKINS-13813
URL: https://issues.jenkins-ci.org/browse/JENKINS-13813
Project: Jenkins
Issue Type: Bug
Components: grails
Reporter: lshatzer
Assignee: kiy0taka
Priority: Critical
After upgrading to 1.6, when my Grails jobs run, I get a NPE:
{code}
java.lang.NullPointerException
at com.g2one.hudson.grails.GrailsBuilder.perform(GrailsBuilder.java:155)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710)
at hudson.model.Build$RunnerImpl.build(Build.java:178)
at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
{code}
I save my job after opening it up and saving it without changing, it now
works. The config file now has an empty: useWrapper element. Your plugin
should probably handle it missing without having to resave all grails jobs.
--
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
[JIRA] (JENKINS-13813) NullPointer after upgrading to 1.6
[
https://issues.jenkins-ci.org/browse/JENKINS-13813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162904#comment-162904
]
kiy0taka commented on JENKINS-13813:
If you want to fix this problem now, please run script via Script Console
(http://yourjenkins/script).
{code}
import hudson.model.*
import com.g2one.hudson.grails.GrailsBuilder
Hudson.instance.items.each { item -
item.builders.findAll { it in GrailsBuilder it.useWrapper == null }
.each {
it.useWrapper = false
item.save()
}
}
{code}
NullPointer after upgrading to 1.6
--
Key: JENKINS-13813
URL: https://issues.jenkins-ci.org/browse/JENKINS-13813
Project: Jenkins
Issue Type: Bug
Components: grails
Reporter: lshatzer
Assignee: kiy0taka
Priority: Critical
After upgrading to 1.6, when my Grails jobs run, I get a NPE:
{code}
java.lang.NullPointerException
at com.g2one.hudson.grails.GrailsBuilder.perform(GrailsBuilder.java:155)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710)
at hudson.model.Build$RunnerImpl.build(Build.java:178)
at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
{code}
I save my job after opening it up and saving it without changing, it now
works. The config file now has an empty: useWrapper element. Your plugin
should probably handle it missing without having to resave all grails jobs.
--
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
[JIRA] (JENKINS-13813) NullPointer after upgrading to 1.6
[
https://issues.jenkins-ci.org/browse/JENKINS-13813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kiy0taka resolved JENKINS-13813.
Resolution: Fixed
NullPointer after upgrading to 1.6
--
Key: JENKINS-13813
URL: https://issues.jenkins-ci.org/browse/JENKINS-13813
Project: Jenkins
Issue Type: Bug
Components: grails
Reporter: lshatzer
Assignee: kiy0taka
Priority: Critical
After upgrading to 1.6, when my Grails jobs run, I get a NPE:
{code}
java.lang.NullPointerException
at com.g2one.hudson.grails.GrailsBuilder.perform(GrailsBuilder.java:155)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710)
at hudson.model.Build$RunnerImpl.build(Build.java:178)
at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
{code}
I save my job after opening it up and saving it without changing, it now
works. The config file now has an empty: useWrapper element. Your plugin
should probably handle it missing without having to resave all grails jobs.
--
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
[JIRA] (JENKINS-13549) Duplicate test results are shown for grails projectsgr
[ https://issues.jenkins-ci.org/browse/JENKINS-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162875#comment-162875 ] kiy0taka edited comment on JENKINS-13549 at 5/17/12 5:49 AM: - If you set 'target/test-reports/\*.xml' in 'Publish JUnit test report' configuration, please change to 'target/test-reports/TEST-*.xml'. was (Author: kiy0taka): If you set 'target/test-reports/*.xml' in 'Publish JUnit test report' configuration, please change to 'target/test-reports/TEST-*.xml'. Duplicate test results are shown for grails projectsgr -- Key: JENKINS-13549 URL: https://issues.jenkins-ci.org/browse/JENKINS-13549 Project: Jenkins Issue Type: Bug Components: core, grails Reporter: Ravi Teja Lokineni Assignee: jeffg2one Labels: grails Attachments: dup_tests.png, dup_tests_1.png, dup_tests_1.png This started happening recently. PFA the attached screenshots. Each failed testcase is printed twice. -- 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
