[JIRA] (JENKINS-14531) CAS1 and 'Trigger builds remotely' incompatibility

2012-07-27 Thread joao.antu...@tagus.ist.utl.pt (JIRA)














































João Antunes
 commented on  JENKINS-14531


CAS1 and Trigger builds remotely incompatibility















it's working now, https://github.com/joantune/cas1-plugin give it a spin, just 
git clone, mvn package, maybe remove the plugin on the hudson dir and then click on advanced and upload this version. I already made a pull request so that it can be integrated in the main code base.

Cheers,
João Antunes



























This message is automatically generated by JIRA.
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-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM

2012-07-25 Thread joao.antu...@tagus.ist.utl.pt (JIRA)














































João Antunes
 commented on  JENKINS-14154


Groovy script can not resolve import classes like hudson.scm.SubversionSCM 















the same happens with me, is this normal?



























This message is automatically generated by JIRA.
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-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM

2012-07-25 Thread joao.antu...@tagus.ist.utl.pt (JIRA)














































João Antunes
 commented on  JENKINS-14154


Groovy script can not resolve import classes like hudson.scm.SubversionSCM 















so, running the import on the ssh -p port localhost groovysh i get:

groovy:000 import hudson.scm.SubversionSCM
groovy:000 ERROR java.lang.IncompatibleClassChangeError:
the number of constructors during runtime and compile time for java.lang.Exception do not match. Expected 5 but got 4
at java_lang_Runnable$run.call (Unknown Source)
at hudson.cli.GroovyshCommand.main (GroovyshCommand.java:70)
at org.jenkinsci.main.modules.sshd.CLICommandAdapter$1.run (CLICommandAdapter.java:34)
at org.jenkinsci.main.modules.sshd.AsynchronousCommand$1.run (AsynchronousCommand.java:104)



























This message is automatically generated by JIRA.
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-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM

2012-07-25 Thread joao.antu...@tagus.ist.utl.pt (JIRA)














































João Antunes
 commented on  JENKINS-14154


Groovy script can not resolve import classes like hudson.scm.SubversionSCM 















actually, this also happens when I do just a purge:


fenix-ashes:~/JenkinsSVNScripts# ssh -p 1414 jenkins@localhost groovysh
Groovy Shell (1.8.5, JVM: 1.6.0_22)
Type 'help' or '\h' for help.
---
groovy:000 purge
groovy:000 ERROR java.lang.IncompatibleClassChangeError:
the number of constructors during runtime and compile time for java.lang.Exception do not match. Expected 5 but got 4
at java_lang_Runnable$run.call (Unknown Source)
at hudson.cli.GroovyshCommand.main (GroovyshCommand.java:70)
at org.jenkinsci.main.modules.sshd.CLICommandAdapter$1.run (CLICommandAdapter.java:34)
at org.jenkinsci.main.modules.sshd.AsynchronousCommand$1.run (AsynchronousCommand.java:104)




























This message is automatically generated by JIRA.
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-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM

2012-07-25 Thread joao.antu...@tagus.ist.utl.pt (JIRA)














































João Antunes
 commented on  JENKINS-14154


Groovy script can not resolve import classes like hudson.scm.SubversionSCM 















so, according to http://stackoverflow.com/questions/7826967/geb-incompatibleclasschangeerror  Java 7 seems to be the issue.. I'm thinking on recompilink jenkins with Java 7 



























This message is automatically generated by JIRA.
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-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM

2012-07-25 Thread joao.antu...@tagus.ist.utl.pt (JIRA)














































João Antunes
 commented on  JENKINS-14154


Groovy script can not resolve import classes like hudson.scm.SubversionSCM 















ok, so, I was running jenkins with Java 6, switched to run it with Java 7, and the purge now works, but the import gives me the error:


groovy:000 import jenkins.scm.SubversionSCM
ERROR org.codehaus.groovy.tools.shell.CommandException:
Invalid import definition: 'import jenkins.scm.SubversionSCM'; reason: startup failed:
script13432436404381481316699.groovy: 1: unable to resolve class jenkins.scm.SubversionSCM
 @ line 1, column 1.
   import jenkins.scm.SubversionSCM
   ^

1 error



























This message is automatically generated by JIRA.
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-14531) CAS1 and 'Trigger builds remotely' incompatibility

2012-07-24 Thread joao.antu...@tagus.ist.utl.pt (JIRA)














































João Antunes
 commented on  JENKINS-14531


CAS1 and Trigger builds remotely incompatibility















Submitted a pull request with the code to fix 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






[JIRA] (JENKINS-14531) CAS1 and 'Trigger builds remotely' incompatibility

2012-07-23 Thread joao.antu...@tagus.ist.utl.pt (JIRA)















































João Antunes
 assigned  JENKINS-14531 to João Antunes



CAS1 and Trigger builds remotely incompatibility
















Change By:


João Antunes
(23/Jul/12 2:38 PM)




Assignee:


JoãoAntunes



























This message is automatically generated by JIRA.
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-14531) CAS1 and 'Trigger builds remotely' incompatibility

2012-07-23 Thread joao.antu...@tagus.ist.utl.pt (JIRA)














































João Antunes
 created  JENKINS-14531


CAS1 and Trigger builds remotely incompatibility















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


cas1



Created:


23/Jul/12 2:37 PM



Description:


Basicly, if one wants to have scripts that actually trigger the build remotely, it must perform a CAS1 authentication, if the CAS1 plugin is activated.




Environment:


Jenkins with CAS1 and Jobs with Trigger build remotely




Project:


Jenkins



Priority:


Major



Reporter:


João Antunes

























This message is automatically generated by JIRA.
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-14531) CAS1 and 'Trigger builds remotely' incompatibility

2012-07-23 Thread joao.antu...@tagus.ist.utl.pt (JIRA)














































João Antunes
 started work on  JENKINS-14531


CAS1 and Trigger builds remotely incompatibility
















Change By:


João Antunes
(23/Jul/12 2:38 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