Thanks John, that sounds like a good idea. I'll see what I can do by
way of archiving artifacts. So far, I had been thinking of artifacts
in term of pure build output (files, libraries, whatever), not as
metadata.
On 23 Feb., 23:56, John Vacz
wrote:
> On 23.02.2012 08:36, Sason wrote:
>
>
>
>
>
>
2012/2/13 Grzegorz Ślusarek
> Bob Koertge gmail.com> writes:
>
> >
> > I cannot seem to get detailed infomration on my errors with JSLint and
> violations. Here is some screenshots http://screencast.com/t/Vu6vo2y9 ->
> I get
> the overall results, but clicking any of the .js file links leads to
Hi,
If you go to the plugins page and check the Build Triggers section,
you'll see that many plugins have the same intent as yours: FileFound
plugin, FST plugin, IRC plugin, URL change plugin.
So, you should definitely do it.
Btw, the plugins mentionned probably provide good source code
skeleton
So I have been using Jenkins for a couple of years to periodically run
some etl/batch jobs. Most of the jobs are simple enough that I just
need a groovy script or two to take care business. So anyway, I am
starting to get requests to start dealing with real time data from
JMS. The data processin
> Does the groovy plugin need anything special installed on the slaves?
there are two options, groovy script and system groovy script. First one
requires groovy installation on slaves (check global jenkins configuration,
auto-install can be used), second doesn't, however it's not executed on sla
svn export would take less disk space, but switching to another VCS alltogether
may be what you want for speed.
While I personally believe that svn forces you to get the governance of a code
base right, I think git dodges that entirely (thats why linux kernel developers
like it). However, git c
On 23.02.2012 08:36, Sason wrote:
Hi there,
I'd like to set up two dependent build projects for the same software
product as follows:
- have a "quick" build run every time a developer commits changes,
i.e. using the SCM polling trigger. This will only be an incremental
build, followed by unit te
Does the groovy plugin need anything special installed on the slaves?
I can run the example 'println System.getenv("PATH")' in the jenkins
script console for a slave but if I put the same thing in an 'execute
groovy script''s groovy command box and run a build I get:
[envtest] $ groovy e:\hudson\
Hello,
I am trying to configure Jenkins to build and archive an artifact when
I promote a build. This artifact is not built until the project is
promoted. So my promotion actions are:
1. Execute shell scripts that build package-name-[whatever].tar.gz
2. Archive the artifacts with path package-nam
FWIW: This request has been open for a few years:
https://issues.jenkins-ci.org/browse/JENKINS-1304
Your concerns is disk space, my concern is speed of checkout. Export can be
much faster on a very large tree. Like you I do clean checkouts so any of the
other concerns don't apply for me. May
On Thu, Feb 23, 2012 at 11:39 AM, Sami Tikka wrote:
>
> I know disk space is not cheap if the disk is inside an expensive and slow
> enterprise SAN. I know many teams that have gone rogue on their organization
> and set up their own CI server outside of IT department control and have been
> hap
It seems there aren't many people who have need for that feature. You can still
open a ticket with a feature request in the Jenkins issue tracker.
If no one steps up to the task, your only option is to implement it yourself or
hire someone to do it for you. There are also commercial versions of
On Thu, Feb 23, 2012 at 6:53 AM, Asmann, Roland wrote:
>
> As for tracing changes, I don't care about those on a build-server! The
> only purpose of a build-server is to check out the code, build it and
> report on that. If your build-server is making changes and checking
> those in, you are not u
On Thu, Feb 23, 2012 at 6:42 AM, Mandeville, Rob wrote:
> Another possibility would be to put Boost in a non-standard location where
> autoconf/configure would never find it, install various versions of Boost
> that you need into various directories, and then pass command-line arguments
> to autoc
Hi,
please, keep cool .
The reason for checkout rather than export is to track and obtain
changes in your big files from subversion to your jenkins server but
only when they've effectively changed not each time you run the build
as you will incurr with export. But, it seems you won't hear tha
Hi list, hi Thorsten,
First of all, thanks Thorsten for your work on the Crowd 2 plugin! I decided to
give it a try, but I noticed that pages were loading really really
slow when I was
logged in. So I took a look at the communication between Jenkins and Crowd:
# ngrep HTTP 'host crowd and port 80
Since we already use the clean checkout option, I don't see where the
performance can be gained.
As for tracing changes, I don't care about those on a build-server! The
only purpose of a build-server is to check out the code, build it and
report on that. If your build-server is making changes a
Another possibility would be to put Boost in a non-standard location where
autoconf/configure would never find it, install various versions of Boost that
you need into various directories, and then pass command-line arguments to
autoconf/configure specifying where to get your Boost library from.
Hi,
Even if checkout was possible, I don't think that it is a good idea
from a perf standpoint: if you export a file, it gets out of svn
control and the changes cannot be tracked.
So, next time your run the job, you have to do a full export again
even if the file didn't change inbetween: can take
Hi all,
Would it be possible to use 'svn export' instead of 'svn checkout'?
We have a couple of projects that contain very large files, which are
then obviously saved twice on the Server -- once as the actual file and
once as the bas-version for SVN.
Since we don't check-in stuff from Jenkins,
Hello,
I am working on AIX with the jenkins version 1.444 and the java
version 1.6.0
I have the following error on stdout after launching jenkins
application.
[Winstone 2012/02/23 12:05:45] - Winstone shutdown successfully
[Winstone 2012/02/23 12:05:45] - Container startup failed
java.io.IOExcep
What we have done is use maven to setup the environment with some calls to tar
etc.
We build boost and store it (versioned) in a maven repo (as tar.gz including
object headers etc).
Then what needs boost downloades it and unpacks it into a workspace relative
path.The make scrips are all configur
I finally changed it: UTC=false, but it made no difference, Jenkins keep
showing the time one hour ahead.. (strange..)
And now Maven shows one hour back.
So at the time of 10.00 (AM), jenkins shows 11:00 and Maven shows 9:00 in
the logging :(...
I am lost..
Ideas?
On Wed, Feb 15, 2012 at 8:14 AM,
That won’t work if you use a custom workspace for a job. The same probably
applies if, under the global configuration, you have (under "Advanced") changed
"Workspace Root Directory".
Matthew
> -Original Message-
> From: jenkinsci-users@googlegroups.com
> [mailto:jenkinsci-users@googlegr
Did you declare your JDK in Jenkins' global settings? If you have done so,
you should be able to select for each job the JDK that you want to use.
Vincent
2012/2/22 Sami Tikka
> I don't really use Maven that much but I do build Jenkins from time to
> time.
>
> Jenkins has at least two ways of
25 matches
Mail list logo
