Build pipe and manual build when unstable upstream

[Ruddy Gbaguidi]

Hi,

I have a build pipe.

I have a job A that has a "Manual trigger" for job B.

 

But when job A which has some unitests is unstable, there is no button to
trigger B.

 

But if the downstream link is automatic, I had an option to continue even if
job A is unstable

 

How can I fix 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.

RE: how can I monitor a repository without having to check out code into jekins workspace

[Ruddy Gbaguidi]

Maybe you can have an empty job that just execute a shell script.

That job can run periodically every X minutes.

Then your script will "manually" verify the repository and act if there is a
change.

So, don't let Jenkins do the check> Do it yourself in your script and let
Jenkins call your script periodically.

 

It should work.

 

 

From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Richard Bywater
Sent: March 26, 2014 11:48 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: how can I monitor a repository without having to check out code
into jekins workspace

 

Could a git hook do what you are trying to do?

 

Richard.

On Thursday, March 27, 2014,  wrote:

Hello-

 

I want to monitor a git repository and run a script where then is a change.
I've puzzled over it for a while now, and I cannot figure this out. If I use
"Source Code Management" and fill out my particulars about my git
repository, Jenkins tries to checkout the code into a local workspace. Is
there any way to monitor a repository and act on it without this inherent
checkout into a workspace? I'm sure there is a way to do it, but I don't see
it in the interface.

 

-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.

-- 
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.

Are pipeline sweetable for multi environement builds ?

[Ruddy Gbaguidi]

Hi All,

I have an application that I want to build for Ubuntu 32 bits, 64 bits.
There is a second application that needs to be build on Wndows.

 

So, I would like to know what is the best setup to do this.

Then the Mega-job starts:

1.   The 32 bits and 64 bits and windows slave machine pull from SVN
source control

2.   The two Ubuntu machines starts building simultaneously App1 while
the windows builds the windows App2 application

3.   Once those 3 jobs are completed, unit tests are run on each machine

4.   One everything is complete on all servers, produced binaries are
pulled and published on an FTP server for the public to download/

 

So, my question is : Should I use build pipeline ? Should I have multislaves
? Should I have 2 or 3 jobs ? How do I tell one job to go on one specific
host to build ?

 

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.