Hello,
I pulled master of emial-ext on 3/6 and made some modifications. 50% of
the times, I see the following exception from one groovy email template
which is that different from our other templates. Any ideas? thanks!
[[ Exception while replacing SCRIPT. Please report this as a bug. ]] {{
Hi all,
I have a Jenkins parameterized build in our CI system, which takes in a few
parameters like PARAM_A (of type Choice), PARAM_B (of type String
parameter) at the beginning of the build.
After the build finished, I want to perform some post-build action, like
archiving artifacts, send
On Thu, Mar 14, 2013 at 4:39 PM, Martin Ba <0xcdcdc...@gmx.at> wrote:
>
> But "tying" a job to a certain node doesn't really sound like what happened.
>
> We have:
> * Node B says: "Leave this machine for tied jobs"
> * Job X says: I don't care where I'm run, just not on master (`!master`)
> * Job
On 14.03.2013 21:50, Les Mikesell wrote:
On Thu, Mar 14, 2013 at 3:30 PM, Martin Ba <0xcdcdc...@gmx.at> wrote:
I'd say this is not intended:
I have a node that has "Leave this machine for tied jobs only" set.
It started to run a Job that certainly did not explicitly set this node.
However, thi
On Thu, Mar 14, 2013 at 3:30 PM, Martin Ba <0xcdcdc...@gmx.at> wrote:
> I'd say this is not intended:
>
> I have a node that has "Leave this machine for tied jobs only" set.
>
> It started to run a Job that certainly did not explicitly set this node.
> However, this Job had "Restrict where this pro
I'd say this is not intended:
I have a node that has "Leave this machine for tied jobs only" set.
It started to run a Job that certainly did not explicitly set this node.
However, this Job had "Restrict where this project can be run" set to:
!master
So, yes, this expression includes this
Thanks. I think the users list (or perhaps the dev list) is probably the
best place to do this.
The plugin source code is at [1], but it looks like this plugin was
never released. I just did a minimal massaging and posted a release, so
hopefully in a day or so you'll see it in your update ce
Thanks for the info James, but looking at the job configuration page the job
itself is not listed as either upstream or downstream of itself. Furthermore,
tracing through the upstream and downstream relationships identified by
Jenkins, there is no cycle and therefore the job is not upstream of i
I have a proyect in Jenkins which throws "class not found exception" when
performing a built, while I can see that the class not found is actually in
the target of the proyect. Does anyone know why this could be happened?
thanks in advance
the proyect is built in maven1 while jenkins does not acc
This is just an observation, and I've not checked much further, however
When "prematurely" ending a job in Jenkins that is running on a slave (not
checked the master)
Jenkins registers the job as stopped
However, the process behind the job appears to continue to run, locking the
workspace unti
Presumably you have "Block build when upstream project is building" enabled.
If so the reason is that the project has itself marked as an upstream
project.
This could happen if you trigger the job to run itself again (e.g. you want
a continous loop).
Assuming you haven't done that then you need
Try to check the join plugin it can help
Em 13/03/2013 23:46, "Benjamin Wang" escreveu:
> Hi all,
>
> I have known some acknowledge about the distribute build.
>
> One common application of this practice is to run OS-specific functional
> tests.
>
> But I have a job, which is to test a great many
Thanks Shawn,
Your solution worked.
Cheers,
Prashant
On Monday, 28 November 2011 22:04:27 UTC+5:30, Shawn Goertzen wrote:
>
> Fix found.
>
> Windows Firewall service must be enabled and started. We had the service
> turned off and disabled, which causes the installer to fail out. Turning
Heureka!
Thank you very much, that was the solution. It works fine now.
Regards
Urs
--
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 jenkinsci-users+unsubscr
Thanks for the response. At the moment I'm in no great rush so I'll wait a
bit for a new version of the Git plugin(s) to be released.
Thanks
Petrik
On Thu, Mar 14, 2013 at 10:27 PM, Mark Waite wrote:
> I think you've found a bug in the Git publisher. I see the same behavior
> after updating
I think you've found a bug in the Git publisher. I see the same behavior after
updating to Git client plugin 1.4.0 and Git plugin 1.3.0.
Oddly, I think that the bug was not there in the Git plugin pre-release
snapshot of 1.3.0 which I built on 2 March 2013. That could indicate that the
issu
16 matches
Mail list logo