On Thu, Oct 3, 2013 at 11:27 AM, Stephen Connolly
<[email protected]> wrote:
> Of course with literate builds you get a much easier way:
>
> Here's the markdown you'd have
>
> # Environments
>
> * `debian`
> * `i386`
> * `x64`
> * `redhat`
> * `i386`
> * `x64`
> * `windows`
>
> # Build
>
> * `debian`
>
> whatever command you use to make the deb
>
> * `redhat`
>
> rpmbuild blah blah blah
>
> * `windows`
>
> whatever command you use to make the exe
>
Sooo... Why didn't Jenkins do it that way from the start (at least
allowing the job definition to be stored/versioned as part of the
project)?
--
Les Mikesell
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
