Hi all,
I can currently get some information for the changeSet of a job using:
http:///job///api/json
However this is not the entire set of change information (such as the edit
type (add, edit, delete), and the perforce revision of the file).
There is additional information provided by:
run once for each checkin
> and provide the single associated changelist to sync to. I think this will
> give you a one-to-one job execution
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Brent Scriver
> *Sent:*
For reference I'm on Jenkins 1.601 with Perforce Plugin v1.3.27.
I have a polling interval set for H/5 * ... for Perforce SCM changes on a
Job in Jenkins. I also have enabled concurrent builds for the job.
If multiple checkins occur during the polling interval then multiple
instances of the J
;
>> He mentioned in his email that he has the ANSI color plugin installed.
>>
>> On Mon, Mar 2, 2015 at 10:15 AM Baptiste Mathus > > wrote:
>>
>>> Try the ANSI color plugin? (Supposing .Net is emitting standard codes).
>>> Le 2 mars 2015 17:25, "
I have the ansi color plugin installed and verified it works, however .NET
or C++ applications setting console colors and emitting text does not
appear colored in the log. Is there a configuration setting to enable it?
The .net code is pretty simple:
static void Main(string[] args)
hive the artifacts” and then have C
> and D “Copy the artifacts” into their workspace and run the tests.
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Brent Scriver
> *Sent:* Tuesday, February 17, 2015 9:16 AM
&g
be the Block build when downstream project is
> building under advanced project options will work. I have used the first
> but not the second.
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Brent Scriver
> *Sent:
trigger using the Trigger Parameterized Build
> plugin. This will run before A completes but not cause A to wait. Then an
> executor will become available as A terminates
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Bren
I'm looking for some help/direction at resolving an odd problem. We
currently only have one node (still in the midst of setting up/configuring
hardware), and we encountered a scenario where we have just a couple
executors that can run on the machine at once (say 2). If I start jobs A &
B whi
