Since version 2.2 Scriptler also has a builder:
https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin#ScriptlerPlugin-Builder
With this one its possible to add Scriptler build steps to any job (if you'r
given the right permissions…).
I think the only thing missing is probably a direct vari
I'm trying to do something I think is pretty typical with the
promoted_builds plugin, but I'm running into problems. Here's what I want
to do-
1. Run a maven build
2. Preserve its pom.xml and target/*.jar
3. Create a promotion step where I push this jar to nexus.
I've tried two different approac
Nope, works for me too.
-- Sami
"Joshua J. Kugler" kirjoitti 26.3.2012 kello 9.26:
> For me, checking less than 10 minutes after your post, the site is up
> and running. Maybe Finland is having connection problems? :)
>
> j
>
> On Sunday, March 25, 2012, Sampo N. elucidated thus:
>> Hi,
>>
Hi,
Scriptler is not linked to any project (it's the convenient way of system
script )
What 's why this variable is empty.
I think this variable is only available when running from a build like with the
groovy script plugin.
BR
@vhardion
Le 26 mars 2012 à 20:15, "James Carr" a écrit :
>
Sorry, forgot to say, that the redirection on save button works. The
errors are only present in log file, no error messages on web pages, but
the objects are not saved.
On 25.03.2012 16:02, Grégory Boissinot wrote:
It should be fix with SharedObjects plugin 0.20.
On Fri, Mar 23, 2012 at 7:13
Thanks for this quick upgrade!
However I got exception in log file (complete stacktrace in attachment):
java.io.FileNotFoundException: /var/lib/jenkins/sharedObjects.xml (Is
a directory)
I tried to remove the directory sharedObjects.xml, but it was created
again when I pressed the save button.
Is there an easy way to setup scriptler so that it can modify files in
the the project workspace?
I kept trying System.getenv('WORKSPACE') but to no avail.
Thanks,
James
Yeah, the wiki is in dire need of an update...
I've slightly changed the behavior in 1.3.11 so that if there is no
perforce installation defined, it will use 'p4' by default.
On Wednesday, 21 March 2012 11:35:55 UTC-6, cjo wrote:
>
> You need to setup the perforce installations in the main confi
I've created issue JENKINS-13227 to track this.
On Friday, March 23, 2012 2:42:04 PM UTC-4, Spiff79 wrote:
>
> The 4 hour difference corresponds to GMT-adjusted time, so it looks like
> there's a mixup in time zones somewhere. Using CVS plugin 1.6 the cvs
> polling command looked like this (exec
Maybe this plugin helps, it lets you expose the different JDK HOMEs as
environment variables:
https://wiki.jenkins-ci.org/display/JENKINS/Tool+Environment+Plugin
/imod
On 26.03.2012, at 15:55, Andreas wrote:
> Hi,
>
> thanks for the feedback and the idea. Unfortunately I think, this will not
Hi,
thanks for the feedback and the idea. Unfortunately I think, this will not
work in my setup. I've several builds running in parallel, also I want to
have the JDKs auto installed by Jenkins.
Kind Regards, Andreas.
Am Montag, 26. März 2012 13:15:33 UTC+2 schrieb Didier Durand:
>
> Hi,
>
> T
Hi,
To my knowledge Jenkins launches a separate jvm for each step you configure
in the "Build" section of your job configuration
So, I would try to alternate your build steps under Ant with shell build
steps and use these shell steps to switch the jvm/jre as you want (via for
example. the lin
Hi,
I face the issue that I have to use different JDKs for different build
steps. Namely I need to invoke the compile step in ant with a 1.5 JDK and
run the sonar ant target with a 1.6 JDK. There is no easy way to split this
job, so a multi job setup is no solution here. Also I do not want to
Hi Vladimir,
actually is it the file jenkins.xml/respectively hudson.xml not
config.xml...
--- SNIP ---
java
-Dhudson.DNSMultiCast.disabled=true -Xrs -Xmx256m -
Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%
\jenkins.war" --httpPort=8080
--- SNAP ---
Question is here
14 matches
Mail list logo