Jenkins failed to record SCM polling

[hezjing]

Hi

I'm using Jenkins 1.489 and Mercurial plugin 1.41.

My Jenkins failed to poll Mercurial changes with the following error in the
polling log:

ERROR: Failed to record SCM polling for hudson.maven.MavenModuleSet@3c32fb80
[.]
java.lang.ArrayIndexOutOfBoundsException: 1
at hudson.Launcher$2.launch(Launcher.java:712)
at hudson.Launcher$ProcStarter.start(Launcher.java:346)
at
hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309)
at hudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303)
at
hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252)
at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
at hudson.scm.SCM.poll(SCM.java:373)
at hudson.model.AbstractProject._poll(AbstractProject.java:1471)
at hudson.model.AbstractProject.poll(AbstractProject.java:1404)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
at
hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)


Any idea?

-- 

Hez

Re: Jenkins failed to record SCM polling

[hezjing]

Hi

This problem is resolved by deleting the workspace directory.

It looks like the problem occurred after Jenkins is restarted after the
upgrade.


On Tue, Nov 6, 2012 at 11:08 AM, hezjing  wrote:

> Hi
>
> I'm using Jenkins 1.489 and Mercurial plugin 1.41.
>
> My Jenkins failed to poll Mercurial changes with the following error in
> the polling log:
>
> ERROR: Failed to record SCM polling for
> hudson.maven.MavenModuleSet@3c32fb80[.]
> java.lang.ArrayIndexOutOfBoundsException: 1
> at hudson.Launcher$2.launch(Launcher.java:712)
>  at hudson.Launcher$ProcStarter.start(Launcher.java:346)
> at
> hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309)
>  at hudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303)
> at
> hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252)
>  at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
> at hudson.scm.SCM.poll(SCM.java:373)
> at hudson.model.AbstractProject._poll(AbstractProject.java:1471)
>  at hudson.model.AbstractProject.poll(AbstractProject.java:1404)
> at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
>  at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
> at
> hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
>  at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
>
>
> Any idea?
>
> --
>
> Hez
>



-- 

Hez

Re: Jenkins failed to record SCM polling

[hezjing]

I made the conclusion too early, the problem is still there.

The mercurial plugin is able to poll the changes for the 1st time, e.g.
when the workspace directory is deleted. Then, it fails in the subsequent
polling, e.g. when the workspace directory is created.



On Tue, Nov 6, 2012 at 11:33 AM, hezjing  wrote:

> Hi
>
> This problem is resolved by deleting the workspace directory.
>
> It looks like the problem occurred after Jenkins is restarted after the
> upgrade.
>
>
> On Tue, Nov 6, 2012 at 11:08 AM, hezjing  wrote:
>
>> Hi
>>
>> I'm using Jenkins 1.489 and Mercurial plugin 1.41.
>>
>> My Jenkins failed to poll Mercurial changes with the following error in
>> the polling log:
>>
>> ERROR: Failed to record SCM polling for
>> hudson.maven.MavenModuleSet@3c32fb80[.]
>> java.lang.ArrayIndexOutOfBoundsException: 1
>> at hudson.Launcher$2.launch(Launcher.java:712)
>>  at hudson.Launcher$ProcStarter.start(Launcher.java:346)
>> at
>> hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309)
>>  at hudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303)
>> at
>> hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252)
>>  at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
>> at hudson.scm.SCM.poll(SCM.java:373)
>> at hudson.model.AbstractProject._poll(AbstractProject.java:1471)
>>  at hudson.model.AbstractProject.poll(AbstractProject.java:1404)
>> at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
>>  at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
>> at
>> hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
>>  at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>  at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>  at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>>
>>
>> Any idea?
>>
>> --
>>
>> Hez
>>
>
>
>
> --
>
> Hez
>



-- 

Hez

[no subject]

[hezjing]

Hi

I used to find the following options in the Jenkins's "Manage Jenkins" page?

1) System Log
2) System Information

But now they are not there any more in Jenkins 1.489, they have been
removed for some reasons???


-- 

Hez

Re: Jenkins failed to record SCM polling

[hezjing]

The problem gone away after I downgraded Jenkins to 1.488.


On Tue, Nov 6, 2012 at 5:20 PM, Dirk Kuypers  wrote:

> just vote for:
>
> https://issues.jenkins-ci.org/browse/JENKINS-15718
>
> BR
> Dirk
>
>
> 2012/11/6 hezjing 
>
>> I made the conclusion too early, the problem is still there.
>>
>> The mercurial plugin is able to poll the changes for the 1st time, e.g.
>> when the workspace directory is deleted. Then, it fails in the subsequent
>> polling, e.g. when the workspace directory is created.
>>
>>
>>
>> On Tue, Nov 6, 2012 at 11:33 AM, hezjing  wrote:
>>
>>> Hi
>>>
>>> This problem is resolved by deleting the workspace directory.
>>>
>>> It looks like the problem occurred after Jenkins is restarted after the
>>> upgrade.
>>>
>>>
>>> On Tue, Nov 6, 2012 at 11:08 AM, hezjing  wrote:
>>>
>>>> Hi
>>>>
>>>> I'm using Jenkins 1.489 and Mercurial plugin 1.41.
>>>>
>>>> My Jenkins failed to poll Mercurial changes with the following error in
>>>> the polling log:
>>>>
>>>>  ERROR: Failed to record SCM polling for
>>>> hudson.maven.MavenModuleSet@3c32fb80[.]
>>>> java.lang.ArrayIndexOutOfBoundsException: 1
>>>> at hudson.Launcher$2.launch(Launcher.java:712)
>>>>  at hudson.Launcher$ProcStarter.start(Launcher.java:346)
>>>> at
>>>> hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309)
>>>>  at hudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303)
>>>> at
>>>> hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252)
>>>>  at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
>>>> at hudson.scm.SCM.poll(SCM.java:373)
>>>> at hudson.model.AbstractProject._poll(AbstractProject.java:1471)
>>>>  at hudson.model.AbstractProject.poll(AbstractProject.java:1404)
>>>> at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
>>>>  at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
>>>> at
>>>> hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
>>>>  at
>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>>>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>  at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>  at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>> at java.lang.Thread.run(Thread.java:662)
>>>>
>>>>
>>>> Any idea?
>>>>
>>>> --
>>>>
>>>> Hez
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Hez
>>>
>>
>>
>>
>> --
>>
>> Hez
>>
>
>


-- 

Hez

Re: Jenkins failed to record SCM polling

[hezjing]

This problem is fixed in Jenkins 1.491 (issue
JENKINS-15733
).

My Mercurial is polling correctly now!

Thank you!


On Fri, Nov 9, 2012 at 2:48 AM, Mark Waite  wrote:

> You could consider switching to the long term support release.  It arrives
> about once every three months and remains stable for those three months.
>
> Mark Waite
>
>   --
> *From:* KP 
> *To:* jenkinsci-users@googlegroups.com
> *Sent:* Thursday, November 8, 2012 2:02 AM
> *Subject:* Re: Jenkins failed to record SCM polling
>
> Exactly the same issue, but with (old built-in 1.x) CVS plugin.
> Issue went away after revert tot 1.488.
>
> After the lazy loading problem made jenkins unusable, now this... It seems
> the stability of the jenkins updates is getting very bad lately. 2 bugs
> completely breaking jenkins, only in a couple of weeks :-(
>
>
>


-- 

Hez

How to keep Unix process alive after job is completed?

[hezjing]

Hi

I have a job which will be run in an Linux slave.

This job will execute a shell command to start a server process which will
run forever. Unfortunately this process is terminated when the job is
finished.

When I tested this using PuTTY, the server process is still alive after I
logged-in and out several times.

May I know how to keep a Unix process alive after the job is completed?


-- 

Hez

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to keep Unix process alive after job is completed?

[hezjing]

Thanks, it works by create a job parameter BUILD_ID=dontKillMe


On Fri, Apr 26, 2013 at 4:16 PM, Riccardo Foschia <
riccardo.fosc...@meta-level.de> wrote:

> Hi,
>
> Take a look at https://wiki.jenkins-ci.org/**display/JENKINS/**
> ProcessTreeKiller<https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller>section
>  "If your build wants to leave a daemon running behind..."
>
> Greetings,
> Riccardo
>
> Am 26.04.2013 10:08, schrieb hezjing:
>
>  Hi
>>
>> I have a job which will be run in an Linux slave.
>>
>> This job will execute a shell command to start a server process which will
>> run forever. Unfortunately this process is terminated when the job is
>> finished.
>>
>> When I tested this using PuTTY, the server process is still alive after I
>> logged-in and out several times.
>>
>> May I know how to keep a Unix process alive after the job is completed?
>>
>>
>>
> --
>
> META-LEVEL Software AG
> Saarbrücker Str. 51
> 66130 Saarbrücken
> Deutschland
> Tel: +49 - 681 / 99687-0
> Fax: +49 - 681 / 99687-99
> Mail: i...@meta-level.de
> Web: www.meta-level.de
>
> Rechtsform: Aktiengesellschaft
> Sitz: Saarbrücken
> HR B Nr. 13 380 Amtsgericht Saarbrücken
> USt-IdNr. DE 1 38 17
> Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
> Vorsitzender des Aufsichtsrats:  Reinhard Kuhn
>
> --
> 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+unsubscribe@**googlegroups.com
> .
> For more options, visit 
> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
> .
>
>
>


-- 

Hez

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Job parameters to specify slave's credential?

[hezjing]

Hi

Currently, we have to choose a pre-configured credential when creating a
Jenkins slave.

Is it possible that the user specifies the credential via the job
parameters instead of using the pre-configured credential? Imagine that I
have a job which allows the user to specify which user account on the slave
they want to install the software.


Any idea if this is do-able?


-- 

Hez

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to keep Unix process alive after job is completed?

[hezjing]

Hi Rakesh


On Mon, Apr 29, 2013 at 2:16 PM, rakesh menon  wrote:

> Hi hezjing,
>
> I have a same issue . Was adding the above parameter the only thing you
> did or do we do any other additional steps?
>
> Thanks
>
>
> On Mon, Apr 29, 2013 at 7:35 AM, hezjing  wrote:
>
>> Thanks, it works by create a job parameter BUILD_ID=dontKillMe
>>
>>
>> On Fri, Apr 26, 2013 at 4:16 PM, Riccardo Foschia <
>> riccardo.fosc...@meta-level.de> wrote:
>>
>>> Hi,
>>>
>>> Take a look at https://wiki.jenkins-ci.org/**display/JENKINS/**
>>> ProcessTreeKiller<https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller>section
>>>  "If your build wants to leave a daemon running behind..."
>>>
>>> Greetings,
>>> Riccardo
>>>
>>> Am 26.04.2013 10:08, schrieb hezjing:
>>>
>>>  Hi
>>>>
>>>> I have a job which will be run in an Linux slave.
>>>>
>>>> This job will execute a shell command to start a server process which
>>>> will
>>>> run forever. Unfortunately this process is terminated when the job is
>>>> finished.
>>>>
>>>> When I tested this using PuTTY, the server process is still alive after
>>>> I
>>>> logged-in and out several times.
>>>>
>>>> May I know how to keep a Unix process alive after the job is completed?
>>>>
>>>>
>>>>
>>> --
>>>
>>> META-LEVEL Software AG
>>> Saarbrücker Str. 51
>>> 66130 Saarbrücken
>>> Deutschland
>>> Tel: +49 - 681 / 99687-0
>>> Fax: +49 - 681 / 99687-99
>>> Mail: i...@meta-level.de
>>> Web: www.meta-level.de
>>>
>>> Rechtsform: Aktiengesellschaft
>>> Sitz: Saarbrücken
>>> HR B Nr. 13 380 Amtsgericht Saarbrücken
>>> USt-IdNr. DE 1 38 17
>>> Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
>>> Vorsitzender des Aufsichtsrats:  Reinhard Kuhn
>>>
>>> --
>>> 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+unsubscribe@**googlegroups.com
>>> .
>>> For more options, visit 
>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>> .
>>>
>>>
>>>
>>
>>
>> --
>>
>> Hez
>>
>> --
>> 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...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> 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...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 

Hez

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to keep Unix process alive after job is completed?

[hezjing]

Yes, Rakesh


On Mon, Apr 29, 2013 at 2:21 PM, hezjing  wrote:

> Hi Rakesh
>
>
> On Mon, Apr 29, 2013 at 2:16 PM, rakesh menon wrote:
>
>> Hi hezjing,
>>
>> I have a same issue . Was adding the above parameter the only thing you
>> did or do we do any other additional steps?
>>
>> Thanks
>>
>>
>> On Mon, Apr 29, 2013 at 7:35 AM, hezjing  wrote:
>>
>>> Thanks, it works by create a job parameter BUILD_ID=dontKillMe
>>>
>>>
>>> On Fri, Apr 26, 2013 at 4:16 PM, Riccardo Foschia <
>>> riccardo.fosc...@meta-level.de> wrote:
>>>
>>>> Hi,
>>>>
>>>> Take a look at https://wiki.jenkins-ci.org/**display/JENKINS/**
>>>> ProcessTreeKiller<https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller>section
>>>>  "If your build wants to leave a daemon running behind..."
>>>>
>>>> Greetings,
>>>> Riccardo
>>>>
>>>> Am 26.04.2013 10:08, schrieb hezjing:
>>>>
>>>>  Hi
>>>>>
>>>>> I have a job which will be run in an Linux slave.
>>>>>
>>>>> This job will execute a shell command to start a server process which
>>>>> will
>>>>> run forever. Unfortunately this process is terminated when the job is
>>>>> finished.
>>>>>
>>>>> When I tested this using PuTTY, the server process is still alive
>>>>> after I
>>>>> logged-in and out several times.
>>>>>
>>>>> May I know how to keep a Unix process alive after the job is completed?
>>>>>
>>>>>
>>>>>
>>>> --
>>>>
>>>> META-LEVEL Software AG
>>>> Saarbrücker Str. 51
>>>> 66130 Saarbrücken
>>>> Deutschland
>>>> Tel: +49 - 681 / 99687-0
>>>> Fax: +49 - 681 / 99687-99
>>>> Mail: i...@meta-level.de
>>>> Web: www.meta-level.de
>>>>
>>>> Rechtsform: Aktiengesellschaft
>>>> Sitz: Saarbrücken
>>>> HR B Nr. 13 380 Amtsgericht Saarbrücken
>>>> USt-IdNr. DE 1 38 17
>>>> Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
>>>> Vorsitzender des Aufsichtsrats:  Reinhard Kuhn
>>>>
>>>> --
>>>> 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+unsubscribe@**googlegroups.com
>>>> .
>>>> For more options, visit 
>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>>> .
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Hez
>>>
>>> --
>>> 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...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>>  --
>> 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...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
>
> --
>
> Hez
>



-- 

Hez

-- 
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...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

How to get artifact archived by upstream project

[hezjing]

Hi

I have a upstream project that create a file which will be processed by the
subsequent downstream projects.

May I know how to configure a project to retrieve the latest artifact
created by the upstream projects?


-- 

Hez

Email notification when built on different slaves

[hezjing]

Hi

I have configured the NodeLabel Parameter plugin to execute a job in slave
X, followed by slave Y.

When the job failed at slave X, an email notification was sent. Then, the
build continued in slave Y. When the job was built successfully in slave Y,
another email notification was triggered saying that the job is back to
normal. This is misleading because the job is still failing in slave X.

Can I somehow configure Jenkins to send email only when the job is built
successfully only slave X?


-- 

Hez

Re: Mercurial plugin NOT picking up merges back to the default branch

[hezjing]

I'm waiting for the fix too ... our team didn't realized that we actually
missed some builds because Jenkins ignored the merge changesets :-(


On Tue, Feb 21, 2012 at 4:05 AM, Maven User  wrote:

> Looking at this:
>
> https://issues.jenkins-ci.org/browse/JENKINS/component/15502
>
> Seems like it's a mix of released and unreleased bugs/tasks/etc...
>
> How does one vote for a release of a plugin explicitly?




-- 

Hez

Port allocator plugin to check port number specified during runtime

[hezjing]

Hi

I want to use the port allocator plugin to make sure that the ports are
free before executing the job.

It works perfectly if I entered the port number directly, e.g.
31080. However in my case, there is a job parameter called PORTBASE (e.g.
31000) and I want the port allocator plugin to check if the PORTBASE + 80
(31080) is free before executing the job.

How can I configure this in Jenkins?


-- 

Hez

Re: Email notification when built on different slaves

[hezjing]

Any workaround for this problem?

On Mon, Apr 16, 2012 at 9:21 PM, hezjing  wrote:

> Hi
>
> I have configured the NodeLabel Parameter plugin to execute a job in slave
> X, followed by slave Y.
>
> When the job failed at slave X, an email notification was sent. Then, the
> build continued in slave Y. When the job was built successfully in slave Y,
> another email notification was triggered saying that the job is back to
> normal. This is misleading because the job is still failing in slave X.
>
> Can I somehow configure Jenkins to send email only when the job is built
> successfully only slave X?
>
>
> --
>
> Hez
>



-- 

Hez

Re: Email notification when built on different slaves

[hezjing]

FYI, I have created a JIRA issue for this,
https://issues.jenkins-ci.org/browse/JENKINS-13921


On Wed, May 9, 2012 at 4:38 PM, hezjing  wrote:

> Any workaround for this problem?
>
>
> On Mon, Apr 16, 2012 at 9:21 PM, hezjing  wrote:
>
>> Hi
>>
>> I have configured the NodeLabel Parameter plugin to execute a job in
>> slave X, followed by slave Y.
>>
>> When the job failed at slave X, an email notification was sent. Then, the
>> build continued in slave Y. When the job was built successfully in slave Y,
>> another email notification was triggered saying that the job is back to
>> normal. This is misleading because the job is still failing in slave X.
>>
>> Can I somehow configure Jenkins to send email only when the job is built
>> successfully only slave X?
>>
>>
>> --
>>
>> Hez
>>
>
>
>
> --
>
> Hez
>



-- 

Hez

Re: Email notification when built on different slaves

[hezjing]

Hi Alex

I'm using built-in email.

I have also tested with email-ext, and it has the same problem.


On Sat, May 26, 2012 at 9:41 AM, Alex Earl  wrote:

> Are you using the built in emailed, or email-ext?
>
> Sent from my Windows Phone
> ------
> From: hezjing
> Sent: 5/25/2012 5:25 PM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: Email notification when built on different slaves
>
> FYI, I have created a JIRA issue for this,
> https://issues.jenkins-ci.org/browse/JENKINS-13921
>
>
> On Wed, May 9, 2012 at 4:38 PM, hezjing  wrote:
>
>> Any workaround for this problem?
>>
>>
>> On Mon, Apr 16, 2012 at 9:21 PM, hezjing  wrote:
>>
>>> Hi
>>>
>>> I have configured the NodeLabel Parameter plugin to execute a job in
>>> slave X, followed by slave Y.
>>>
>>> When the job failed at slave X, an email notification was sent. Then,
>>> the build continued in slave Y. When the job was built successfully in
>>> slave Y, another email notification was triggered saying that the job is
>>> back to normal. This is misleading because the job is still failing in
>>> slave X.
>>>
>>> Can I somehow configure Jenkins to send email only when the job is built
>>> successfully only slave X?
>>>
>>>
>>> --
>>>
>>> Hez
>>>
>>
>>
>>
>> --
>>
>> Hez
>>
>
>
>
> --
>
> Hez
>



-- 

Hez

Performing tasks in remote servers as slave or SSH?

[hezjing]

Hi

I want to create a job that will login to multiple remote servers (and with 
multiple user accounts) and install some products. How should I create this 
job?

One way is to create a slave node for every user in each of the remote 
servers, then trigger the job on that specific slave node.

Another way is use SSH plugin that login to the remote hosts and execute 
the commands.

What are the differences between these two ways? Any better idea?


-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/dab41abd-1598-4682-8204-44143af64cb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Maven repository server supports multiple upstream projects?

[hezjing]

Hi

It looks like the Maven repository server only allow us to configure one 
upstream project.

Imagine that I have a project C, which has dependency to project A and B.

How can configure the Maven repository server to take the last successful 
build from project A and B?

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2d1c5ed3-9bbc-49b9-a550-8d214a57d5ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.