and attributes
plus the tags and attributes allowed by all the plugins installed in that
particular Jenkins instance.
Mark Waite
>
> From: Ramith Jayasinghe
>To: Jenkins Users
>Sent: Monday, August 20, 2012 10:23 PM
>Subject: Re: Cre
The schema is dynamic based on the plugins installed and their
serialisation via xstream.
Backwards compatibility constrains should ensure that it is reasonably
stable, but you need to look at the backing classes to infer the purpose of
each field and what values it can take
On Tuesday, 21 August
Hi Mark,
Does this means we don't have a documentation explaining the tags &
attributes available?
regards
Ramith
LSF (www.opensource.lk)
On Aug 20, 6:49 pm, Mark Waite wrote:
> I've used your technique of creating a similar job from the GUI and passing
> that to the command line for multiple
I've used your technique of creating a similar job from the GUI and passing
that to the command line for multiple Jenkins releases. It works very well for
me. I prefer that technique because it also allows me to compare my "archived"
job definition (kept under source control for the project wh
