Hi,
Can anyone help me? everytime i am running my job on Jenkins its picking up
the ruby.framework version 2.0 and my job Gemfile specifies ruby 2.2.0 so
please i need help to force jenking (master) to use the rvm ruby-2.2.0 i
dont seem to get a way around it.
Jenkins version: 1.601
--
You
Hi ,
Greetings!!!
We have an excellent opportunity for “*Solution Architect “*for our client
in Atlanta, GA Eagan, MN.
*Position: Solution Architect*
*Locations: Atlanta, Georgia Eagan , Minnesota *
*Contract: Long Term*
If you have suitable candidates. Send their resumes to
AFAIK there's no plugins for such purpose.
The best way to do it in Jenkins w/o plugins would be...
1. Convert XML file to *.properties using XSLT conversion
2. Inject environment variables using EnvInject plugin
I think a dedicated plugin (or EnvInject extension) would find some
I have to use cases where I cant run my workflow due to errors thrown by
script-security-plugin. Both workflows are being served via SCM:
1 - org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException:
unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String
Have not found any code examples of how to set upstream projects. Neither
does it seems possible with the Jenkins API.
I tried to add directly in config.xml
upstreamProjectmyLib++/upstreamProject
upstreamProjectmyLib2++/upstreamProject
But it didn't take.
According to both JSON and XML schema
Hi everyone,
having upgraded from 1.580.3 to 1.596.1 just now I get an error about
not having the right Matrix Project Plugin (on top of the Manage
Jenkins page).
I guess this is because of the faulty release 1.4.1 of the Matrix
Project Plugin and should not concern me, correct?
Just wanted to
On 09.03.2015, at 16:26, Les Mikesell lesmikes...@gmail.com wrote:
It is something I'd want to know if I were considering installing the
latest LTS release with the idea that it would have fewer
regressions,..
The problem was that he _downgraded_ from latest weekly to latest LTS. LTS does
On Mon, Mar 9, 2015 at 10:58 AM, Daniel Beck m...@beckweb.net wrote:
It is something I'd want to know if I were considering installing the
latest LTS release with the idea that it would have fewer
regressions,..
The problem was that he _downgraded_ from latest weekly to latest LTS. LTS
Hi everyone,
I was wondering if anyone has experiences they are willing to share about
moving the user DB from the built-in Jenkins DB to an outside one like LDAP
or Google OpenID/Oauth (Google Oauth experience is more applicable to my
use case).
We have have 50-75 users with access now, and
I tend to disagree. People using LTS are somehow conservative and would be
at risk to get confused: so, in the end, is that LTS safe, or is it going
to screw up my data?.
We could indeed add information in the LTS changelog that is going to
change *in the future*, but I personally think it's just
I use an execute shell step with this at the top to force jenkins to
do what I want:
#!/bin/bash -x
source /usr/local/rvm/scripts/rvm
rvm use 1.8.7
On Mon, Mar 9, 2015 at 6:33 AM, seun are lummy...@gmail.com wrote:
Hi,
Can anyone help me? everytime i am running my job on Jenkins its picking up
Le 9 mars 2015 18:22, Les Mikesell lesmikes...@gmail.com a écrit :
On Mon, Mar 9, 2015 at 11:53 AM, Baptiste Mathus bmat...@batmat.net
wrote:
I tend to disagree. People using LTS are somehow conservative and would
be
at risk to get confused: so, in the end, is that LTS safe, or is it
going
On Mon, Mar 9, 2015 at 11:53 AM, Baptiste Mathus bmat...@batmat.net wrote:
I tend to disagree. People using LTS are somehow conservative and would be
at risk to get confused: so, in the end, is that LTS safe, or is it going
to screw up my data?.
Yes, when you know that LTS is going to screw up
Hello,
I started working with Jenkins a few months ago in an environment that
experiences occasional instability. I have hundreds of jobs running on
different servers and operating systems. When a job fails, I'd like to hook
it up to a Bugzilla entry that is tracking the issue, block the job
From the results is an instance of groovy.lang.Binding
http://groovy.codehaus.org/api/groovy/lang/Binding.html. Don't know if it
was supposed to be supported but as it works in out-of-sandox mode, here
comes the possible idea of it being a bug.
El lunes, 9 de marzo de 2015, 21:24:43 (UTC+1),
Anybody else get E200015 error on svn check-out? Any known solutions? Tried
deleting ~/.subversion directory and that did not make it go away.
E200015: ISVNAuthentication provider did not provide credentials; HTTP
authorization cancelled
1.596.1 LTS
Credentials Plugin 1.22
Subversion Plug-in
You need to specify 'Additional Credentials' for any externals.
On 09.03.2015, at 19:52, jesse_bic...@homedepot.com
jesse_bic...@homedepot.com wrote:
Anybody else get E200015 error on svn check-out? Any known solutions? Tried
deleting ~/.subversion directory and that did not make it go away.
On 09.03.2015, at 18:22, Les Mikesell lesmikes...@gmail.com wrote:
Yes, when you know that LTS is going to screw up data, it only seems
reasonable to post it in a visible place.
The data was screwed up by the regular weekly release, and that was mentioned:
- On the /manage page after the
On 09.03.2015, at 19:57, Les Mikesell lesmikes...@gmail.com wrote:
There is no issue affecting it. Again: You get the documentation on the
backwards-compatibility-breaking change to build layout when you upgrade.
It's not like there's a path to get into this situation where you're never
I think you must be right, my solution was to stop caring where the flow
runs, and focus on an alternative method of retrieving the report/log data.
I used the Build Flow Toolbox which lets you copy files with the flow:
job = build('downstream job')
toolbox.copyFiles(job.workspace,
On Mon, Mar 9, 2015 at 1:41 PM, Daniel Beck m...@beckweb.net wrote:
So when an issue affecting it becomes
known, the ideal thing would be to _fix_ the by-then-known problem,
but if that is too much to ask, warning about it would seem
appropriate.
There is no issue affecting it. Again: You
On Friday, March 6, 2015 at 9:51:08 AM UTC, Javier Delgado wrote:
node {
binding['MYVAR'] = myvalue
echo ${binding.getVariables()}
}
If ran on a non-sandboxed environment, the output is nice:
[steps:org.jenkinsci.plugins.workflow.cps.DSL@545c26e4, MYVAR:myvalue]
Surprising to me.
On Monday, March 9, 2015 at 3:45:07 PM UTC, Javier Delgado wrote:
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException:
unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String
java.lang.String[]
Probably a bug; please file with steps to reproduce in
This doesn't directly answer your question, but I would highly recommend
switching to using groovy views. It is SOO much easier to debug what is
going wrong compared to Jelly.
On Mon, Mar 9, 2015 at 4:28 PM Thom Ellis teh...@gmail.com wrote:
Alright, I've been staring at this one for a bit,
Alright, I've been staring at this one for a bit, and I must be missing
something obvious, and I'm just not seeing it, so hoping someone can point
out what it is :) I'm just trying to figure out how you get at variable
values that come from a nested class. What I have is a build result action
After upgrading to Jenkins LTS 1.596.1 and Subversion Plugin 2.4.5 Jenkins
is now ignoring post commit hook notifications - it replies with a 200
status but jobs using the repositories are not running.
I'm using Visual SVN Server with Active Directory authentication.
Note: I tried the
Hi,
This is a purely informative post for those who want to compile a Microsoft
Visual C++ 6 project with Jenkins.
- Get and unzip the Visual Studio SP6 (vs6sp6.exe).
- Unzip the file VS6sp61.cab
- In the resulting folder, copy the files Common\msdev98\bin\msdevP.exe
and
Looks like a big in the plugin you are using. I'm not aware of that plugin so
it may be DOA or some work in progress.
If you need a quick workaround why don't you run your tests like you would from
the command line with rake.
If you want to visualise the test results you can use one of the
I would suggest adding this link to the LTS page.
On 9 March 2015 at 09:14, Baptiste Mathus m...@batmat.net wrote:
https://wiki.jenkins-ci.org/display/JENKINS/JENKINS-24380+Migration
Cheers
Le 9 mars 2015 07:36, corneil.duples...@gmail.com
corneil.duples...@gmail.com a écrit :
We decided
https://wiki.jenkins-ci.org/display/JENKINS/JENKINS-24380+Migration
Cheers
Le 9 mars 2015 07:36, corneil.duples...@gmail.com
corneil.duples...@gmail.com a écrit :
We decided to move onto LTS after some of the recent instability.
We were on 1.599 and moved to 1.596.1
We stopped Jenkins,
We decided to move onto LTS after some of the recent instability.
We were on 1.599 and moved to 1.596.1
We stopped Jenkins, deleted the files in JENKINS_HOME/updates and replaced
the war.
When Jenkins came up again all the build history was missing. The build
directories are all empty.
None of
On 09.03.2015, at 08:54, corneil.duples...@gmail.com wrote:
I would suggest adding this link to the LTS page.
This has nothing to do with the LTS release line.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group
Hello,
Occasionally a build that runs every day (for few hours) is simply
disappearing. I can't see the build in Jenkins but I do see it on the file
system. Checking the build log there is no exception and it's looking like
the build was terminated at the middle.
I checked the Jenkins logs
33 matches
Mail list logo
