This isn't a jenkins issue, anyway for your scenario, it looks like oyu
need to add the taskdef for Ant contrib which defines the tasks for if
conditions.
http://ant-contrib.sourceforge.net/ and
http://ant-contrib.sourceforge.net/tasks/tasks/if.html
On Thu, Feb 6, 2014 at 1:35 PM, vinil narayan
You need to pass the parameterized value into ant like this:
-DDBName=${DBName}
Or handle it like an environment variable by adding this inside the project tag:
property environment=env/
And then use ${env.DBName} wherever you need to access it.
Cheers,
Ben
On Thu, Feb 6, 2014 at 12:05 AM,
ETA for a release that will include the change?
--
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,
I found the solution. Just downloaded Regression Report Plugin and modified
it.
--
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
Op woensdag 5 februari 2014 23:22:25 UTC+1 schreef JonathanRRogers:
On Wednesday, February 5, 2014 5:53:59 AM UTC-5, metalmo...@gmail.comwrote:
I had the same isssues as you did. Couldn't find a proper example of the
Junit XML file. Finally made it work. Maybe XML example below might help
Hi
I have just upgraded from Subversion 1.54 plugin to v.2.00. Launching a job
that does a clean checkout on a Windows slave now repeatedly fails with this
exception:
Checking out https:// my trunk at revision '2014-02-06T13:42:30.165 +'
ERROR: Failed to check out https:// my trunk
Did the credentials get migrated correctly?
On 6 February 2014 13:55, David Aldrich david.aldr...@emea.nec.com wrote:
Hi
I have just upgraded from Subversion 1.54 plugin to v.2.00. Launching a
job that does a clean checkout on a Windows slave now repeatedly fails with
this exception:
How would I check that?
I have just downgraded to 1.54. Now, on the configuration page of the failing
project, Jenkins is asking me for credentials:
Unable to access https://mytrunk : svn: E200015: OPTIONS
/subversion/zodiac/trunk failed (show
If you go to the job configuration screen (when using subversion 2.0) there
should be a credentials drop-down under the SVN URL. if that is empty, then
likely the credentials for that specific job were not migrated. You should
be able to select the credentials, or worst case add them again.
On 6
Hi Stephen
I upgraded to svn plugin 2.0 again. In the job configuration screen the
credentials drop-down read 'none' as you expected. I then selected the correct
credentials from the dropdown and was taken to:
https://myhttps://%3cmy url/jenkins/job/my job/configSubmit
which was a blank
There was always the possibility that there was some crazy state that a job
could get itself into with regards to where it was sourcing its credentials
from (using the pre-2.0 credentials model).
I was rather confident that I had covered all the crazy ways that the
credentials could be stashed.
Hi Stephen
Thanks, I am using the latest plugins.
Our Jenkins instance uses 'user' 'hudsonuser' for svn access but we have to
have separate credentials for that user for linux and Windows slaves (they have
different passwords). The linux jobs got the correct credentials but the
Windows jobs
yeah I certainly was not expecting anything that esoteric ;-)
On 6 February 2014 16:02, David Aldrich david.aldr...@emea.nec.com wrote:
Hi Stephen
Thanks, I am using the latest plugins.
Our Jenkins instance uses 'user' 'hudsonuser' for svn access but we have
to have separate
Hi Jenkins users,
I'm really confused with Downstream builds information on a build page. I
have an upstream job and a downstream job. Downstream job is a deployment
job and upstream job is a job that pulls source code and then archive .zip
file. The zip file gets copied from upstream job to
Hi Eric,
Thank you for your reply. I will try it out
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/How-to-have-downstream-job-scheduled-tp4688112p4688580.html
Sent from the Jenkins users mailing list archive at Nabble.com.
--
You received this message because you
The easiest way with Ant is to use the Jenkins global configuration to
configure an Ant installation, and have it download that Ant installation
from Apache. Then you define the job to use the specific Ant version you
configured, and it will be downloaded and used for that build.
That keeps your
On Thu, Feb 6, 2014 at 3:11 PM, Mark Waite mark.earl.wa...@gmail.com wrote:
The easiest way with Ant is to use the Jenkins global configuration to
configure an Ant installation, and have it download that Ant installation
from Apache. Then you define the job to use the specific Ant version you
Hi,
I am wirting a maven 2/3 project in jenkins. I am seeing following error in
build stage:
[INFO]
[ERROR]
BUILD ERROR[INFO]
[INFO] Fatal error
18 matches
Mail list logo
