How to see a Pharo job configuration - getting null pointer error?
Hi guys - I am trying to understand how some of the CI jobs work (in particular pharo launcher) - however when I click on the âRead Only Job Configuarionâ link I just get an error screen with : java.lang.NullPointerException at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) Further down the stack it mentions acegisecurity - so Iâm assuming it might be related to some credential thing - but are we not allowed to see what scripts are run to create final images, or is something just misconfigured? Tim
I think you need an account to see the real config ... Please understand that we are all just users here, maintain/explaining jenkins/hudson is a PIA for all of us ;-) On 03 Sep 2014, at 17:26, Tim Mackinnon <tim@testit.works> wrote:
Hi guys - I am trying to understand how some of the CI jobs work (in particular pharo launcher) - however when I click on the âRead Only Job Configuarionâ link I just get an error screen with : java.lang.NullPointerException at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
Further down the stack it mentions acegisecurity - so Iâm assuming it might be related to some credential thing - but are we not allowed to see what scripts are run to create final images, or is something just misconfigured?
Tim
Believe me, I understand the PIA part of CI ;) You are right about the account though. I do have an account - so I tried logging in to ci.inria.fr - and I get a dashboard to navigate down to Pharo-contributions, but clicking the jenkins button for that project gives me the https://ci.inria.fr/pharo-contribution/? link Iâve been used to. I wonder if something is misconfigured (or maybe we just arenât allowed to see how a job is configured?). I wanted to know, because the images that PharoLauncher produces for end users seem different from the ones spit out of the normal jenkins CI. So I think there must be some script run at the very end, which I wanted to understand. Tim On 3 Sep 2014, at 16:33, Sven Van Caekenberghe <sven@stfx.eu> wrote:
I think you need an account to see the real config ...
Please understand that we are all just users here, maintain/explaining jenkins/hudson is a PIA for all of us ;-)
On 03 Sep 2014, at 17:26, Tim Mackinnon <tim@testit.works> wrote:
Hi guys - I am trying to understand how some of the CI jobs work (in particular pharo launcher) - however when I click on the âRead Only Job Configuarionâ link I just get an error screen with : java.lang.NullPointerException at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
Further down the stack it mentions acegisecurity - so Iâm assuming it might be related to some credential thing - but are we not allowed to see what scripts are run to create final images, or is something just misconfigured?
Tim
Le 3 sept. 2014 à 17:59, Tim Mackinnon a écrit :
Believe me, I understand the PIA part of CI ;)
You are right about the account though. I do have an account - so I tried logging in to ci.inria.fr - and I get a dashboard to navigate down to Pharo-contributions, but clicking the jenkins button for that project gives me the https://ci.inria.fr/pharo-contribution/? link Iâve been used to.
Pay attention that ci.inria.fr and ci.inria.fr/<aproject> don't point to the same web site / host. It means that even if you are logged in ci.inria.fr, you need to log in on ci.inria.fr/xxx to be able to manage jobs, see configurations, etc. It is a bit boring, but at least, it is the same user name / password.
participants (3)
-
Christophe Demarey -
Sven Van Caekenberghe -
Tim Mackinnon