-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/03/2012 11:44 PM, Michael Pailloncy wrote:
[...]
> In the meantime, I found out that there's an issue for this in JIRA
> already:
> https://issues.jenkins-ci.org/browse/JENKINS-14157
> Unfortunately, it's still unassigned.
>
>
So you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/04/2012 12:00 AM, Qazwart wrote:
> I'm a bit confused by this. All Subversion 1.1 to 1.7 clients should work
> with all Subversion servers from 1.1 and up.
>
> Besides Jenkins doesn't use the command line clients. It uses SvnKit.
>
> Why is t
I'm a bit confused by this. All Subversion 1.1 to 1.7 clients should work with
all Subversion servers from 1.1 and up.
Besides Jenkins doesn't use the command line clients. It uses SvnKit.
Why is the version of the Subversion client so important? Are you shipping or
sharing working directories
Le 03/08/2012 22:44, Fritz Elfert a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Michael,
On 08/03/2012 10:00 PM, Michael Pailloncy wrote:
Le 03/08/2012 21:30, Fritz Elfert a écrit :
I can't find any way to select the workspace
version per slave
Hi,
I'm not sure to clearly unders
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Michael,
On 08/03/2012 10:00 PM, Michael Pailloncy wrote:
> Le 03/08/2012 21:30, Fritz Elfert a écrit :
>> I can't find any way to select the workspace
>> version per slave
> Hi,
> I'm not sure to clearly understand what you want.
> If you have sla
On Mon, 16 Jul 2012, Tisch wrote:
> Hi all,
>
> I have been looking at the jenkins ec2 plugin for jenkins. I've read the
> documentation for the plugin on the plugin page. I can't find a way to set
> an instance-ID
> (i-88e6xxx) instead of an AMI-ID to start slaves. I've seen the option to
> s
Le 03/08/2012 21:30, Fritz Elfert a écrit :
I can't find any way to select the workspace
version per slave
Hi,
I'm not sure to clearly understand what you want.
If you have slaves with SVN 1.7 and slaves with 1.6 natively, you can
add labels like "svn1-6" to nodes with 1.6 version and "svn1-7"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
In the global config, the SVN workspace version can be selected. However
I have a mix of older/newer slave where some use 1.7 natively and some
others use still 1.6. I can't find any way to select the workspace
version per slave - which is a prere
this is more of a maven question, I think.
Try turning -X on in the maven job to find out where it is looking.
At 2:10 PM -0400 8/3/12, wrote:
>I'm on an older Hudson server. One of my projects can't find it's parent pom,
>though other ones can. Doesn't seem like a nexus side issue since the
I'm on an older Hudson server. One of my projects can't find it's parent pom,
though other ones can. Doesn't seem like a nexus side issue since the other
projects are finding it okay. I have the -U flag turned on to prevent caching
of a failure response. I can't figure anything out.
What ca
The artefacts are not in the workspace, they are stored with the build
information,
so you can retrieve artifacts from all of the builds that have them stored,
from build#1 to latest if you keep them that long.
these are easily accessed from the webUI via
/job///artifact/
The default file pat
Install the "Workspace Cleanup Plugin"
-Original Message-
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of phil swenson
Sent: Friday, August 03, 2012 12:23 PM
To: jenkinsci-users
Subject: workspace deletion
Is there an easy way to delete all t
right but I have to do that on every node. I have 15 of them and have
needed to do this several times….
On Fri, Aug 3, 2012 at 10:39 AM, David Weintraub wrote:
> In Unix, you could do something like this:
>
> $ rm -rf $JENKIN_HOME/jobs/*/workspace/*
>
> Another possibility is:
>
> $ cd $JENKINS
In Unix, you could do something like this:
$ rm -rf $JENKIN_HOME/jobs/*/workspace/*
Another possibility is:
$ cd $JENKINS_HOME/jobs
$ find . -regex "\./[^/]+/workspace/[^/]+" -exec rm {} \;
On Fri, Aug 3, 2012 at 12:23 PM, phil swenson wrote:
> Is there an easy way to delete all the workspace
Have a look at the EnvInject Plugin[1], to see if you are able plug your
script into it and get the correct results.
look at "Prepare an environment for the run" section in the job config.
The "Evaluated Groovy script" item might override them correctly.
https://wiki.jenkins-ci.org/display/JENKI
On Fri, Aug 3, 2012 at 11:32 AM, cjo 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 done with the Copy Artifact Plugin[1] before your deploy
I
Is there an easy way to delete all the workspaces on all nodes?
I looked at the CLI - doesn't appear to help.
thanks
Hi,
I have a job that takes a number of parameters (version_number,
release_number, branch etc). This build can be built in a number of ways,
some need to get the values of these parameters from other locations. the
different modes are:
1) Manually - Take the passed in parameters
2) SCM Change
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, an
We are using Maven (actually Ant and Ivy, but I'm converting the
ivy.xml to a Maven pom.xm). I store the pom.xml and the jar/war/ear
I'm deploying as a "Build Artifact". I have figured out how to use the
Promotion Plugin to deploy the artifact into our Maven repository when
I press the button to p
bump.
On Monday, July 16, 2012 9:09:44 AM UTC+2, Tisch wrote:
>
> Hi all,
>
> I have been looking at the jenkins ec2 plugin for jenkins. I've read the
> documentation for the plugin on the plugin page. I can't find a way to set
> an instance-ID
> (i-88e6xxx) instead of an AMI-ID to start slaves.
First google link on "job changes history Jenkins"
https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin
Hope it helps.
On Aug 3, 2012, at 12:16 AM, Suri wrote:
> Hi
>
> How to identify job configuration user id details in Jenkins. I have created
> one job using my id.
> Anot
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
> create
if i change my master system to dns like demo.sigmainfo.in:8050
Where all i needed to change in
jenkins url: demo.sigmainfo.in:8050/jenkins
Advanced setting of slave : instead of HOST:PORT whether i needed to give
demo.sigmainfo.in:8050 or hostname of master:8050?
Thanks in Advance
vargh
Hi
How to identify job configuration user id details in Jenkins. I have
created one job using my id.
Another person modified my job without my knowledge.
That person also having id in Jenkins. How to track job configuration
history with user ids.
25 matches
Mail list logo
