Closed donahuetrevor closed 6 years ago
So, first, a note. The xml section of the extension is actually not straight up ruby. You can use ruby in it, but the basic keywords are then translated into xml. That's where send comes in, the send function basically calls the method corresponding to the string passed. So, you will need to use send for any ruby keywords that you want to be xml nodes and not ruby or when you have periods in the xml node.
Without seeing the output I can't really diagnose what's wrong with those three. But, you can run the builder and have it write the files locally. The -d flag for debug might do it, but there's also the dump command (you'd use it instead of bootstrap). Once you have the xml it's writing you can compare it to the xml you are expecting to be there.
this is awesome! thank you @crimsonknave. I think I have everything I need to debug this.
First off, I want to say: amazing job! Great project! Definitely something I looked for a long time.
This is not really an issue, and sorry, I know this is for reporting legitimate issues. So feel free to close this if I'm intruding in some way. But please point me in the right direction.
I'm trying to write my extension for this jenkins plugin: https://github.com/jenkinsci/nodelabelparameter-plugin
Here's what I have so far:
My Ruby is not too strong, so I'm hopinh someone can just point me in the right direction. The 3 fields with comments on them don't work, the rest do. So:
defaultSlaves
andallowedSlaves
are of typeList<String>
. andnodeEligibility
is even harder - is of typeNodeEligibility
a custom type.From what I understand,
send
will send a signal to the current instance and return whatever that new class has?what am I doing wrong here?
Thank you in advance and apologies again!