From your two different solutions that you tried, the reasons for it not
triggering are as follows
Case 1 passing current build parameters, this only passes the parameters
when parametrized or those passed in.
So if no parameters are found in the build then downstream will no be
triggered
Exporting the variable in the shell buildstep will not add them Enviroment
variables list for later buildsteps/postbuild items,
If they are needed for later buildsteps write them to a properties files
and use the envinject plugin to make them available for later buildsteps.
If you just want
As I commented in your other thread, a Matrix job runs
the parametrized trigger on the parent job once only and not for each
configuration used.
This is not a bug but intended design.
Note that the value of $WORKSPACE is incorrect on master as well, (try
printing the variable out in a build
One way to do this is to trigger job A B from within a job using the
Build/Trigger other projects buildstep with the blocking mode enabled (wait
until triggered jobs finished). When using this there are Env variables
(see the help for the block item or the wiki) created indicating the
this, which has better error
checking for these cases.
Chris
On Monday, 4 March 2013 04:57:04 UTC, MDKF wrote:
Yes. The configuration shown in the first box Copy Artifact box of the
image works fine but the second one does not.
On Friday, March 1, 2013 6:38:34 AM UTC-5, cjo wrote:
Have you
March 2013 03:36:11 UTC, Kamal Ahmed wrote:
Hi cjo,
When i use the same URL as i do for Repo, i get error:
Server returned HTTP response code: 401 for URL:
--
*From:* cjo cjo.j...@gmail.com javascript:
*To:* jenkins...@googlegroups.com javascript:
*Cc
Have you enabled the build to be Parameterized and add a Copy Parameter
named Configuration which is used in the copy artifact buildstep.
As it seems that that is missing in your case.
Chris.
On Thursday, 28 February 2013 22:50:05 UTC, MDKF wrote:
I see my picture didn't make it the first
Do you have a trigger setup for the job, as stated in the wiki page you
need to have one even if it is a yearly one.
On Friday, 1 March 2013 17:57:24 UTC, Jeremy Jensen wrote:
Having an issue with the SVN Post Commit Hook triggering a build in
Jenkins. To test this concept out, I have a
These should be the values that you enter in the config of the job when you
select the Sventon2 browser for the SVN browser in the SCM config for a
job. (might be in the advanced section)
So from the code it would be the URL and Repository Instance.
Warning: Before you run that script make sure
Chris
Would your plugin work for Hudson too ?
We tried and it didnt work.
Thanks
On Monday, April 30, 2012 5:55:16 AM UTC-7, cjo wrote:
If you just want to remove the junction points between triggering a build
and the checkout from SCM,
You can use the pre-scm-buildstep plugin[1] which
*
http://jenkins-swcoe.india.ti.com/job/Child/*17:13:06* ERROR: Child
aborted.*17:13:06* Notifying upstream projects of job completion*17:13:06*
Finished: FAILURE
Thanks and Regards,
Manju
On Friday, February 8, 2013 5:06:20 PM UTC+5:30, cjo wrote:
There is a known issue if the child
There is a known issue if the child jobs have block if upstream is
running enabled as they see the triggering job as running,
which might be the issue that you are seeing.
If this is not the case, can you actually post the reasons that the pending
jobs are not running (from the tooltip when
I assume that you have the jobs set up as
every commit job - testjob
tagged commits - testjob
Try adding a dummy parameter that is passed from the tagged commits job,
that is unique for each build, as the ParametersAction will cause
a separate builds if there are different parameters passed
.
Hope this explains it a bit better.
Chris
On Friday, 8 February 2013 18:03:53 UTC, Chris Withers wrote:
On 08/02/2013 11:53, cjo wrote:
I assume that you have the jobs set up as
every commit job - testjob
tagged commits - testjob
Yep.
Try adding a dummy parameter
I think the reason for this is that the matrix jobs are designed to run
several configs and normally the labels indicate the what type of
machine/OS or other requirements the nodes have.
And the matrix configuration allows the job to run on different labels to
build on different Environments.
If you want to select different build steps dependant on node/axis try
looking at the Conditional BuildStep Plugin as that should let you use
whichever buildstep you like dependant on finding a condition you can check.
The AXIS items should be available as ENV for the conditions to check,
Just knocked up an extension to the parameterized trigger plugin that will
allow you to pass the inverse of what is build to a triggered job.
If this parameter is added to a Matrix build it will get the filter passed
into it and then inverts the filter (makes it !(original filter) )
before
This might be a workspace locking issue as the polling log you post seems
to indicate that the polling has started [1], but has not completed.
even though the concurrent is allowed.
Try adding a logger for hudson.slaves.WorkspaceList to the log page and see
if there is a log message
Some
Are you picking from a fixed set of projects?
If you are you could try the pull request I created to use the
run-condition plugin on the parameterized trigger plugin which would allow
the decision on if a particular projects is triggered to be calculated from
various options. Including files
Not sure as the maintainer seems to be AWOL for the last 9-10 months, will
ping the developer list to see if I can get someone to review the many Pull
requests.
On Friday, January 25, 2013 11:44:34 AM UTC, Chris Withers wrote:
On 25/01/2013 11:33, cjo wrote:
Are you picking from a fixed
You will also need to alter the canRoam element from true to false as this
controls whether project can be built on any node, or just ones matching
the labels.
canRoamtrue/canRoam --- use any nodes
canRoamfalse/canRoam --- use defined nodes/labels only
Chris
On Tuesday, January 22, 2013
Have a look at the copy to slave plugin, which should do what you want to
do.
https://wiki.jenkins-ci.org/display/JENKINS/Copy+To+Slave+Plugin
Chris
On Wednesday, January 16, 2013 9:25:22 AM UTC, Guillaume Membré wrote:
Hello,
first of all, thanks a lot for the work you have done on
What you need to do is pass the parameter for the SVN_REVISON that is
generated in the first job down to the chained jobs.
Simple solution using parameterized trigger plugin[1]
(assumes you don't want to start downstream jobs directly with parameters)
Start job, has REVISION string parameter,
Select the specific build option and set the build number to be the
variable $PROMOTED_NUMBER.
This will get resolved when the build step runs so you can then get the
artifacts from the correct build that is being promoted.
Chris
On Friday, December 7, 2012 11:02:48 AM UTC, Masariello wrote:
Why not just archive the artifacts that everyone can access, which are
then available via the artifacts link,
while the workspace is still locked to those who can access it.
Add this as a post build action.
Chris.
On Tuesday, December 4, 2012 6:05:11 PM UTC, zw wrote:
Hi
We currently are
You might also want to check what build steps and post build steps you have
enabled in the job, as some of them such as the warnings plugin require the
previous build to have completed.
As they declare that the step needs the previous build to complete, to
perform the correct actions.
they
Is this the same job being started with two sets of different parameters?
If so check that you have Allow Concurrent builds enabled (under advanced
options I think).
If this is not enabled only one build of that job can run at one time
regardless of the times triggered.
Chris
On Tuesday,
Assuming that the build step is a shell script, then the defaults when
started are /bin/sh -xe which causes it to return at the first error.
You can alter this following the answers in
https://groups.google.com/d/topic/jenkinsci-users/dyS1y4y32tc/discussion
Chris.
On Friday, November 16,
You can easily move the workspace of the jobs,
On slaves, this is just setting the Remote FS root for the slave, and the
workspaces will be created under that. (yourserver:port
/computer/slave/configure)
On Master you can configure workspace to use a different directory to that
of Jenkins
Have you enabled the block when upstream/downstream is running options in
the advanced section of the job config.
As this will normally keep multiple jobs in a chain, only allowing a single
job to be running at a time.
I have used these options to run a chain of 5-6 jobs run on multiple
Regarding the item
2. Use the Parameterized-Trigger plugin (
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin).
This plugin lets you trigger downstream-jobs based on certain triggers. The
triggers appear to be too restrictive though. They're all based on the
state of
Or you can go to
http://yourserver:port/pluginManager/advanced
and upload the hpi file via the Upload Plugin section.
On Monday, October 22, 2012 3:23:16 PM UTC+1, atef_101 wrote:
Hello,
You can put the file under $HUDSOM_HOME/plugins and restart jenkins.
Regards,
2012/10/22 ilikeflex
For the issue 1. Block build when downstream project is building allows
build in queue to be started ahead of downstream jobs in the queue.
We saw this a while back and raised an issue on it, JENKINS-14918 [1]
and there is a pending patch for it.[2]
Chris
[1]
on that or any other resource that you know might help??
Rgrds
bandy
On Monday, September 3, 2012 7:23:10 PM UTC+8, cjo wrote:
To run one or other of the downstream jobs, it currently not a simple
case as, but there are are several different ways of doing it.
Use a groovy post build script
To run one or other of the downstream jobs, it currently not a simple case
as, but there are are several different ways of doing it.
Use a groovy post build script to trigger one of the builds
You could use the Parametrized trigger [1] in combination with the
conditional build step plugin,[2]
anyway.
Thanks!
Ben
On Fri, Aug 31, 2012 at 4:42 AM, cjo cjo.j...@gmail.com javascript:
wrote:
Use the parameterized trigger plugin, as that has a parameter to pass
in
matrix subset to build, using that combination rather than the defined
one
in the project.
Added
to be
true in order that the job will run.
Thanks
David
On Thursday, August 23, 2012 1:27:33 PM UTC+3, cjo wrote:
You can set multiple triggers on a project,
So just set both the Build after other projects are built and the Build
periodically on the project.
Chris,
On Thursday, August 23
On project B check that you do not have the Block when upstream projects
are building under the Advanced Project Options section set, as this
will cause this behaviour.
Chris.
On Friday, August 24, 2012 2:08:10 PM UTC+1, marathiboy wrote:
Hello,
I have two projects say A and B. Both are
You can set multiple triggers on a project,
So just set both the Build after other projects are built and the Build
periodically on the project.
Chris,
On Thursday, August 23, 2012 10:02:46 AM UTC+1, David Gang wrote:
Hi all,
I have a job which i want to run on 2 specific days in a
I was running a small groovy script to do this, and then used the trigger
on start plugin to run the job when Jenkins is restarted, also gives you
the enabled and pinned states so that you can see if these have changed.
Script:
import hudson.model.*
println(plugin name, version, active,
If all of the builds are triggered by project 1, and you only want to run
one set of parameters at a time through the chain at a time.
You should be able to use the Block build when downstream project is
building and Block build when upstream project is building advanced
options on all of the
There were several issues linked to this problem and they all started in
1.474, where the javascript was separated out into separate files for each
of the components.
I investigated this under JENKINS-14495[1], which was linked to the main
issue JENKINS-14514 [2]
Jesse, added a fix on Friday
Use the job config history plugin,
https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin
which should cover your needs.
Chris
On Friday, August 3, 2012 8:16:21 AM UTC+1, Suri wrote:
Hi
How to identify job configuration user id details in Jenkins. I have
created one
As you have the deploying part already configured in the promotion,
All that you need to do is retrieve the artefacts from the build that you
need, in to the current workspace,
This is done with the Copy Artifact Plugin[1] before your deploy
You should set the project to $PROMOTED_JOB_NAME,
, 2012 5:23:15 PM UTC+1, qazwart wrote:
On Fri, Aug 3, 2012 at 11:32 AM, cjo cjo.john...@gmail.com wrote:
As you have the deploying part already configured in the promotion,
All that you need to do is retrieve the artefacts from the build that
you
need, in to the current workspace
This is normal for a fresh installation.
To enable the requirement to login you need to enable security.
Goto yourserver/configure
then tick the checkbox for Enable security
then select the Security Realm and Authorization that you require. see
the wiki for details on these.
What is your setup?
Does it have master + slaves?
The master and slave paths are different.
Did the jobs run on the same slave?
Have you updated the Jenkins version between those two builds?
Has anyone altered the path for the master workspace in
your_server/configure advanced item below the
There is no change that has occurred as the promotion is its own job, and
therefore has its own ${JOB_NAME}
which is parent_jobname/promotions/ promotion_name
So the behaviour is consistent when using the custom workspace option.
If you read the wiki page [1] for the plugin there is a warning
You could also try the flexible publish plugin[1], as a wrapper around the
email-ext post build step and have the conditions of NOT and buildcause ==
upstream.
if you don't want to have a groovy prestep.
Haven't tried this, it is just a suggestion of an alternative way.
[1]
Then in most probabilities the email ext plugin does not have the required
DataBoundConstructor needed for use with the Flexible publish plugin.
It is probably not a simple change to make as there are several different
options available for it.
and the groovy solution is probably better and
From your comments it looks like you want to perform some different actions
for the developer commits and the nightly builds.
If this is the case.
You want to look at the Conditional BuildStep Plugin if you want to perform
a different action based on how the build is started.
this will allow
This assumes that poll SCM and build periodically are set as the
triggers in the same job.
So you are seeing the config as in the image
https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin#ConditionalBuildStepPlugin-Conditionalstep%28single%29
or
Looks like you really want the parameterized-trigger with more conditions,
this is currently a pull request
which make the parameterized-trigger have all of the same conditions as the
conditional build step plugin.
If you want to try this it is request
Some things to check
Does the user that Jenkins have permissions to write to the mapped drive?
This user may vary depending on how Jenkins is started.
Windows service? is this mapped drive available for the service?
Linux
Can you login as the jenkins user and access/add files to that share?
There is also the conditional build step plugin which you can use which
will allow check the build cause and then run a single or multiple
buildstep(s).
https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin
You will need to have separate buildsteps in this case, for each of
You could try looking at the Multiple SCM plugin
https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+Plugin
I haven't used it myself, but it seems to allow you to do what you want.
Chris
On Friday, June 29, 2012 6:03:35 PM UTC+1, Chris Withers wrote:
Hi All,
I have one job where I
The Promote plugin is its own project and has its own configuration file.
which are stored under Jobs/Job_Name/promotion/Promotion_Name/config.xml
If you are copying jobs via the new job / copy from existing project,
please look and see if there is an issue relating to this, as I tested it
The behaviour is correct the default env variables that the promotion job
sees are the one for its own runs (as it a job/project in itself).
However it provides a different set of env variables, so that you can get
at job being promoted, these are
PROMOTED_URL - URL of the job being
Bill,
There is the NODE_NAME environment variable which gives you the name of the
node the job is running on, however this just gives you the name of the
node as defined in Jenkins, this may or may not match to your machine
hostname especially if you run multiple slaves on the same machine.
Hi,
The Log Parser plugin is used to highlight the console log, i.e. highlight
failure sections etc.
this requires that some global configuration is done see section Console
Output Parsing in the amin Jekins configuration page.
See https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin
Which version of Jenkins are you using?
As there was an issue fixed on this recently, which was included in 1.468.
https://issues.jenkins-ci.org/browse/JENKINS-13735
Is this the same issue?
Chris
On Tuesday, June 26, 2012 11:28:42 AM UTC+1, Sergey Irisov wrote:
Hello.
I'm using Jenkins
From the code, it looks like the build description is hard coded, you
cannot specify your own in this case.
The description set is
Build timed out (after {0} minutes). Marking the build as {1}.
where {0} is the time period it aborted at
and {1} is either aborted or failed depending on
The problem with the set build name plugin is that it is a build wrapper
and the promotion plugin does not support those and if it did it would
apply to the promotion job itself. As a promotion job is a job of its own
with a slimed down configuration.
If you have the groovy plugin installed
I've set up some thing like that,
Basically the first job in the chain asks all the questions about tasks to
builds, are artifacts required, etc via parameters.
Does some basic checking (tasks correct, do they exist) and creates a
summary of this information.
If this checking passes, it
Hi Dirk,
Looks like you need to use one of the LabelExpression which are the other
subclass of Label,
in your example case the LabelExpression.Or would be needed.
The code would be
job.setAssignedLabel(
new hudson.model.labels.LabelExpression.Or(
new
Antony,
In the Discard Old Builds section,
Where you set up the option to keep the builds for a length of time, or
maximum number of builds.
There is an advanced button that will let you set the same items for
the artifacts.
I believe the warning counts are stored separately to these
If you just want to remove the junction points between triggering a build
and the checkout from SCM,
You can use the pre-scm-buildstep plugin[1] which allows you to run most
build steps at this point, including windows batch scripts.
You could also use the post-build step, which should
This would have been better asked on the jenkinsci-dev list,
But have you modified your local ~/.m2/settings.xml file to include the
jenkins hosted repos.
*
*
See the Setting Up Environment section of
https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial
Chris
On Friday, 20 April 2012
You need to setup the perforce installations in the main configuration page,
goto http://yourserver:port/configure
and scroll to find the perforce section and then click the add perforce
button
enter the name of the installation and the path to the executable, of setup
the automatic
As I have some free time,
I have tested this out using the parametrized trigger plugin.
Warning I am not a SVN user so these are all from reading docs and testing
them out.
if Job A and Job B both checkout from the same URL,
using the parametrised trigger in job A, add Subversion parameters
From the error described, it looks like the errors are coming from another
script called from inside the shell command.
Are the sh: -c: line 0: ...
showing up in the build log in Jenkins?
Can you share more or the output log? (basically 15-20 lines before this is
seen)
As it looks more likely
71 matches
Mail list logo
