maven build on ssh slave hangs at "Parsing POMs" (Jenkins 1.577)

[Aaron Molitor]

updated Jenkins to 1.577 last weekend, and now no builds work.  I have 
tried reverting back to 1.575 and back to 1.565.1 (LTS), default plugin 
versions included, and get same result.  I am struggling to find and answer 
after three solid days of digging.

I am now looking for a way to see what happens in my build after the git 
clone/checkout and before executing the maven build that corresponds with 
"Parsing 
POMs" log output with the little swirly thing. Trying to generate a thread 
dump at that point fails, it seems either the slave is hung or the ssh 
connection has dropped. 

The Systems are all Ubuntu 12.04 LTS running the debs from here: 
(http://pkg.jenkins-ci.org/debian binary/). There is one master and 12 
slaves all systems have only one executor. The plugins are at the latest 
revision (according to the plugin manager). The OS is up to date on all 
patches from Ubuntu. all process and builds in question are running in Java 
1.6.0_45. I am not convinced this is a Jenkins bug given the different 
Jenkins and version/plugin combinations I have tried.

Thus I am looking for any help I can get getting trace or debug level 
logging out of Jenkins. I am sure there is a logger I can setup, but I have 
not yet guessed the correct class (or it hangs so quickly that the logger 
doesn't output anything before hand). 


-- 
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/d/optout.

Re: Installing Jenkins into a specific directory on Windows using msiexec

[Luiz Esmiralha]

Hi Terrence,

Thanks for your answer, but I just "forgot" that I needed admin rights to 
install Jenkins on the Program Files (x86) folder. Problem detected between 
keyboard and chair. :)

Regards, 

Luiz

On Wednesday, August 27, 2014 11:42:40 AM UTC-3, Dunnigan, Terrence J wrote:
>
>  Hi Luiz,
>
>  
>
> Have you tried manually deleting or moving the existing C:\Program Files 
> (x86)\Jenkins directory and then installing?
>
>  
>
> Terry
>
>  
>  
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Dirk Kuypers
> *Sent:* Wednesday, August 27, 2014 1:05 AM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Re: Installing Jenkins into a specific directory on Windows 
> using msiexec
>  
>  
>  
> Hi Luiz,
>  
>  
>  
> sorry, for the maybe dumb question: Does the user installing the package 
> have admnistrative rights? From the log:
>  
>  
>   
> MSI (s) (C8:68) [14:47:01:951]: Product: Jenkins 1.577 -- Error 1303. The 
> installer has insufficient privileges to access this directory: C:\Program 
> Files (x86)\Jenkins.  The installation cannot continue.  Log on as 
> administrator or contact your system administrator.
>  
>  
>  
> Error 1303. The installer has insufficient privileges to access this 
> directory: C:\Program Files (x86)\Jenkins.  The installation cannot 
> continue.  Log on as administrator or contact your system administrator.
>   
>  
>  
> What's the command line you are using to install?
>  
>  
>  
> BR 
>  
> Dirk
>  
>  
>   
>  
>  
> 2014-08-26 20:13 GMT+02:00 Luiz Esmiralha 
> >:
>  
> Fails for me on 1.577. I attached the msiexec log file.
>  
>
>
>
>
> On Thursday, March 6, 2014 4:15:09 PM UTC-3, Tim Bradt wrote:
>  
> It works now as of 1.553 using the Windows native package.
>
> -- 
> 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-use...@googlegroups.com .
>  
> For more options, visit https://groups.google.com/d/optout.
>  
>  
>  
> -- 
> 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-use...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>  

-- 
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/d/optout.

Re: Installing Jenkins into a specific directory on Windows using msiexec

[Luiz Esmiralha]

Hi Dirk,

I'm the one who should be sorry for a dumb question! I was using AutoIt to 
perform the install, removed the #RequireAdmin flag from the script and 
forgot about it. 

Thank you, sir.



On Wednesday, August 27, 2014 3:04:48 AM UTC-3, Dirk Kuypers wrote:
>
> Hi Luiz,
>
> sorry, for the maybe dumb question: Does the user installing the package 
> have admnistrative rights? From the log:
>
> MSI (s) (C8:68) [14:47:01:951]: Product: Jenkins 1.577 -- Error 1303. The 
> installer has insufficient privileges to access this directory: C:\Program 
> Files (x86)\Jenkins.  The installation cannot continue.  Log on as 
> administrator or contact your system administrator.
>
> Error 1303. The installer has insufficient privileges to access this 
> directory: C:\Program Files (x86)\Jenkins.  The installation cannot 
> continue.  Log on as administrator or contact your system administrator.
>
> What's the command line you are using to install?
>
> BR 
> Dirk
>
>
>
> 2014-08-26 20:13 GMT+02:00 Luiz Esmiralha 
> >:
>
>> Fails for me on 1.577. I attached the msiexec log file.
>>
>>
>>
>>
>> On Thursday, March 6, 2014 4:15:09 PM UTC-3, Tim Bradt wrote:
>>>
>>> It works now as of 1.553 using the Windows native package.
>>>
>>  -- 
>> 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-use...@googlegroups.com .
>>  For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/d/optout.

Re: Trigger build on git merge

[Mark Waite]

I don't see a way to do that using hooks or polling.  As far as I can tell,
the git plugin assumes that a SHA1 only needs to be built once.

If the typical case is that you push the staging branch and staging and
develop are the same SHA1, could you add a build step to one of the
branches which runs the same job again with a parameter that is the value
of the other branch?  The build step would somehow need to be conditional
so that you don't always run the job twice on every commit to either branch.

Managing two jobs sounds simpler to me than trying to manage the subtle
challenges hiding in that configuration running two different
configurations from the same job.

Mark Waite


On Wed, Aug 27, 2014 at 8:31 AM, Nicolas Goy  wrote:

> I have two branches, develop and staging.
>
> When I push changes to the develop branch, a build is triggered and this
> works fine.
>
> Now, if I merge develop into staging and push the staging branch, jenkins
> git plugin says there is no change because the commit id of the staging
> branch matches the commit id of the develop branch.
>
> I'd am using the conditional plugin and I check for the branch name. I'd
> like to have one test suite for the develop branch and a slightly different
> suite for the staging branch.
>
> How can I do that without duplicating the project within jenkins?
>
> --
> 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/d/optout.
>



-- 
Thanks!
Mark Waite

-- 
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/d/optout.

Start Jenkins slave from Windows 7 while master is run with https protocol

[Grace Lee]

Has anyone successfully started Jenkins slave via ‘Launch slave agents via Java 
Web Start’ when master is running in https protocol?

We are running Jenkins 1.568 on Linux Centos 5.5.

Jenkins suggested the following command to run on slave machine, but I think 
it’s lack of the cert key. Has anyone successfully done this? Thanks.

->java -jar slave.jar -jnlpUrl https://:8080/hudson/computer//s
lave-agent.jnlp -secret 
9344091d1e0c6b2582d277761105f8380f799bc318cce577480c9aeaf31b0309
Exception in thread "main" javax.net.ssl.SSLHandshakeException: 
java.security.cert.CertificateException: No subject alternative names present
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source)
at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)
at sun.security.ssl.Handshaker.processLoop(Unknown Source)
at sun.security.ssl.Handshaker.process_record(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown 
Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown 
Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown 
Source)
at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:245)
at hudson.remoting.Launcher.run(Launcher.java:207)
at hudson.remoting.Launcher.main(Launcher.java:180)
Caused by: java.security.cert.CertificateException: No subject alternative 
names present
at sun.security.util.HostnameChecker.matchIP(Unknown Source)
at sun.security.util.HostnameChecker.match(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown 
Source)
... 14 more

-- 
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/d/optout.

Re: Question about git polling & "nonexisting_workspace"

[Mark Waite]

Vincent is correct.  A workspace is required in order to perform the
inclusion / exclusion analysis.  The plugin knows that dependency is
required, and implicitly requires a workspace for the polling.

Mark Waite


On Wed, Aug 27, 2014 at 9:02 AM, Vincent Latombe 
wrote:

> Hi Terry,
>
> I believe options such as "Polling ignores commits in certain paths
> (path/to/version/file)" require you to poll using workspace.
>
> Vincent
>
>
> 2014-08-27 16:42 GMT+02:00 Dunnigan, Terrence J <
> terrence.j.dunni...@boeing.com>:
>
>  Hi all,
>>
>>
>>
>> I have a job that polls for changes. When I wipe the workspace the
>> polling stops working and I see this message:
>>
>>
>>
>> Started on Aug 27, 2014 9:20:22 AM
>>
>> No workspace is available, so can’t check for updates.
>> (nonexisting_workspace)
>>
>> Done. Took 0.21 sec
>>
>> No changes
>>
>>
>>
>> For this job, “Force polling using workspace” is NOT enabled. Since
>> “Force polling using workspace” is not enabled, why does the polling
>> require a workspace?
>>
>>
>>
>>
>>
>> The job is configured as such:
>>
>> -Branches to build has a specific branch listed
>>
>> -Polling ignores commits in certain paths (path/to/version/file)
>>
>> -Check out to a sub-directory
>>
>> -Advanced sub-modules behaviors (recursively update submodules)
>>
>> -Prune stale remote-tracking branches
>>
>> -Check out to a specific local branch
>>
>> -Poll SCM every 10 minutes
>>
>>
>>
>>
>>
>> Here’s my system information:
>>
>>
>>
>> Jenkins LTS 1.554.3
>>
>> Git plugin 2.2.2
>>
>> Git client plugin 1.10.0
>>
>>
>>
>> I appreciate any help or insight that anyone may have.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Terry
>>
>>
>>
>>
>>
>> --
>> 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/d/optout.
>>
>
>  --
> 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/d/optout.
>



-- 
Thanks!
Mark Waite

-- 
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/d/optout.

NullPointer after upgrade to 1.577

[Christopher Helck]

After upgrading from a pretty old version (at least 30 revisions) a large 
number of jobs don't show up in the browser although the job directories 
still exist on the server. The log file has tons of errors similar to:

 

Aug 27, 2014 3:43:23 PM jenkins.InitReactorRunner$1 onTaskFailed

SEVERE: Failed Loading job RFQ.LPA.Common 1.0 java.lang.NullPointerException

at 
hudson.model.AbstractProject.getLastBuild(AbstractProject.java:970)

at 
hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:184)

at 
hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:463)

at 
hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:739)

at 
hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:459)

at hudson.model.AbstractProject.save(AbstractProject.java:303)

at 
hudson.plugins.disk_usage.DiskUsageProperty.setOwner(DiskUsageProperty.java:150)

at hudson.model.Job.onLoad(Job.java:214)

at hudson.model.AbstractProject.onLoad(AbstractProject.java:317)

at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:789)

at hudson.model.Items.load(Items.java:279)

at jenkins.model.Jenkins$18.run(Jenkins.java:2649)

at 
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)

at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)

at jenkins.model.Jenkins$7.runTask(Jenkins.java:885)

at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)

at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)

at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:724)

 

Any help would be greatly appreciated.

-Chris

-- 
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/d/optout.

Verify job config.xml is valid without actually creating a job

[Sean Last]

Does jenkins have any way to verify a configuration is valid other than
actually creating a job?

I've written a bunch of automation around jenkins that generates job
configurations and pushes them, and I'd like to add more and better unit
tests, but one of the things I don't know how to do is validate that the
config.xml being generated is considered valid by jenkins.

Is there a way to do this? 

-- 
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/d/optout.

Is jenkins needed in test?

[Abe Farhat]

We built jenkins and artifactory in Dev and we are currently using it there 
to build our code. We deployed the code to test and prod systems and 
everything works fine. Do we need to build the same 
environment for jenkins and artifactory in test system? what would that 
benefit us?  Thanks

-- 
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/d/optout.

Re: Question about git polling & "nonexisting_workspace"

[Vincent Latombe]

Hi Terry,

I believe options such as "Polling ignores commits in certain paths
(path/to/version/file)" require you to poll using workspace.

Vincent


2014-08-27 16:42 GMT+02:00 Dunnigan, Terrence J <
terrence.j.dunni...@boeing.com>:

>  Hi all,
>
>
>
> I have a job that polls for changes. When I wipe the workspace the polling
> stops working and I see this message:
>
>
>
> Started on Aug 27, 2014 9:20:22 AM
>
> No workspace is available, so can’t check for updates.
> (nonexisting_workspace)
>
> Done. Took 0.21 sec
>
> No changes
>
>
>
> For this job, “Force polling using workspace” is NOT enabled. Since “Force
> polling using workspace” is not enabled, why does the polling require a
> workspace?
>
>
>
>
>
> The job is configured as such:
>
> -Branches to build has a specific branch listed
>
> -Polling ignores commits in certain paths (path/to/version/file)
>
> -Check out to a sub-directory
>
> -Advanced sub-modules behaviors (recursively update submodules)
>
> -Prune stale remote-tracking branches
>
> -Check out to a specific local branch
>
> -Poll SCM every 10 minutes
>
>
>
>
>
> Here’s my system information:
>
>
>
> Jenkins LTS 1.554.3
>
> Git plugin 2.2.2
>
> Git client plugin 1.10.0
>
>
>
> I appreciate any help or insight that anyone may have.
>
>
>
> Thanks,
>
>
>
> Terry
>
>
>
>
>
> --
> 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/d/optout.
>

-- 
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/d/optout.

Question about git polling & "nonexisting_workspace"

[Dunnigan, Terrence J]

Hi all,

I have a job that polls for changes. When I wipe the workspace the polling 
stops working and I see this message:

Started on Aug 27, 2014 9:20:22 AM
No workspace is available, so can't check for updates. (nonexisting_workspace)
Done. Took 0.21 sec
No changes

For this job, "Force polling using workspace" is NOT enabled. Since "Force 
polling using workspace" is not enabled, why does the polling require a 
workspace?


The job is configured as such:
-Branches to build has a specific branch listed
-Polling ignores commits in certain paths (path/to/version/file)
-Check out to a sub-directory
-Advanced sub-modules behaviors (recursively update submodules)
-Prune stale remote-tracking branches
-Check out to a specific local branch
-Poll SCM every 10 minutes


Here's my system information:

Jenkins LTS 1.554.3
Git plugin 2.2.2
Git client plugin 1.10.0

I appreciate any help or insight that anyone may have.

Thanks,

Terry


-- 
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/d/optout.

RE: Installing Jenkins into a specific directory on Windows using msiexec

[Dunnigan, Terrence J]

Hi Luiz,

Have you tried manually deleting or moving the existing C:\Program Files 
(x86)\Jenkins directory and then installing?

Terry

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Dirk Kuypers
Sent: Wednesday, August 27, 2014 1:05 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Installing Jenkins into a specific directory on Windows using 
msiexec

Hi Luiz,

sorry, for the maybe dumb question: Does the user installing the package have 
admnistrative rights? From the log:

MSI (s) (C8:68) [14:47:01:951]: Product: Jenkins 1.577 -- Error 1303. The 
installer has insufficient privileges to access this directory: C:\Program 
Files (x86)\Jenkins.  The installation cannot continue.  Log on as 
administrator or contact your system administrator.

Error 1303. The installer has insufficient privileges to access this directory: 
C:\Program Files (x86)\Jenkins.  The installation cannot continue.  Log on as 
administrator or contact your system administrator.

What's the command line you are using to install?

BR
Dirk


2014-08-26 20:13 GMT+02:00 Luiz Esmiralha 
mailto:esmira...@gmail.com>>:
Fails for me on 1.577. I attached the msiexec log file.




On Thursday, March 6, 2014 4:15:09 PM UTC-3, Tim Bradt wrote:
It works now as of 1.553 using the Windows native package.
--
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/d/optout.

--
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/d/optout.

-- 
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/d/optout.

Trigger build on git merge

[Nicolas Goy]

I have two branches, develop and staging.

When I push changes to the develop branch, a build is triggered and this 
works fine.

Now, if I merge develop into staging and push the staging branch, jenkins 
git plugin says there is no change because the commit id of the staging 
branch matches the commit id of the develop branch.

I'd am using the conditional plugin and I check for the branch name. I'd 
like to have one test suite for the develop branch and a slightly different 
suite for the staging branch.

How can I do that without duplicating the project within jenkins?

-- 
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/d/optout.

Re: How to execute an action when build is submitted

[Baptiste Mathus]

Hi,

Never did it myself, but I think you should have a look at the
QueueListener:
https://wiki.jenkins-ci.org/display/JENKINS/Extension+points#Extensionpoints-hudson.model.queue.QueueListener

And If you're looking for real life example, the Priority Sorter Plugin is
certainly a candidate for finding tricks for handling the queue submission.

My 2 cents.

Cheers


2014-08-27 16:16 GMT+02:00 Martin d'Anjou :

>
> Hi,
>
> Is it possible to execute an action when the build is submitted, before it
> goes in the pending state.
>
> Martin
>
> --
> 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/d/optout.
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor ! nbsp;!

-- 
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/d/optout.

How to execute an action when build is submitted

[Martin d'Anjou]

Hi,

Is it possible to execute an action when the build is submitted, before it
goes in the pending state.

Martin

-- 
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/d/optout.