Re: Moving From Parameterized Trigger Plugin to Pipelines

Hello, To load a properties file, you can install this plugin : https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Utility+Steps+Plugin Then, you will have access to *readProperties* utility step. See https://github.com/jenkinsci/pipeline-utility-steps-plugin/blob/master/docs/STEPS.md for usage

Moving From Parameterized Trigger Plugin to Pipelines

Hello, I am trying to move towards Pipelines instead of our Build Flow / Parameterized Trigger plugin setup. It is mostly making sense, but there is one thing that seems very cumbersome / maybe even impossible under Pipelines which I can do with ease via the Parameterized Trigger plugin (see

MSTest plugin poll

Hello everyone, I have implemented a couple of blueprints (i.e. modification requests) of the MSTest plugin for Jenkins. Since I haven't any other way to contact my users, I will try to use this mailing list to describe the changes and have your opinion. First, the possibility to use the MSTest

Still trying to fix "It appears that your reverse proxy set up is broken" with IIS 8.5

We still have no solution for this. See https://groups.google.com/d/msg/jenkinsci-users/wmhprlRiVmI/7q4Il_xRBgAJ for more details. Does anyone have a working IIS 8.5 web.config that doesn't give "your reverse proxy set up is broken"? Terry -- You received this message because you are

Re: Kubernetes Plugin

I've seen it reported before. Check your pod logs, events and exit codes On Thu, Aug 24, 2017 at 6:35 PM, Pedro Januário wrote: > Hi, > > I am using Jenkins Pipeline with Kubernetes Plugin and doing something > really simple just to build a container and run the

Kubernetes Plugin

Hi, I am using Jenkins Pipeline with Kubernetes Plugin and doing something really simple just to build a container and run the container to execute the tests on it. While doing it I got a error that shows exit -2 without another information, currently I am just doing a echo. *Example (just

Re: Upgrade Jenkins, or not ?

I went through a similar situation. We had an older version of Jenkins (1.534) on a standalone configuration. I took the approach of standing up a new instance of Jenkins, this time with a master/slave configuration. First I took inventory of all the plugins that were used on the old Jenkins

Re: P4 Plugin - Jenkins Poll not triggering builds despite finding changes

Marley. do you want Perforce to checkout those files and perform some kind of build? if so, then I think $class: 'CheckOnlyImpl' is not what you want. I doubt its a bug (it could be) but the Perforce support in Jenkins is pretty robust and has been around for years. On Wed, Aug 23, 2017 at 5:19

Re: Multijob out of memory issues

The best to start here would be to try instructions on this page and analyze the resulting heapdump. 2017-08-24 8:08 GMT+02:00 Shashank Bhargav : > Hi All, > > We are facing serious out of memory

Re: Ansible role for installing and configuring Jenkins 2

Karl, this was extremely helpful. THanks very much. -- 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. To view this

readJSON file in new titandb with same vertexIds in writeJSON file

graph=TitanFactory.open('titan.properties') graph.io(IoCore.graphson()).writeGraph("titan-graph.json"); one sample row from titan-graph.json:(with vertexID: 49280)

Re: Jenkins crashes with "Illegal character 0x0 for HttpChannelOverHttp" - Why?

(replies inline) On Fri, 10 Feb 2017, daniel.seeba...@gmail.com wrote: > Hi, > > - Ubuntu 16.04.1 > - Jenkins 2.32.2 > > Since a few days I see crashes on Jenkins: (/var/log/jenkins/jenkins.log*)* > > Feb 10, 2017 12:15:09 AM hudson.security.csrf.CrumbFilter doFilter > WARNING: No valid crumb

Multijob out of memory issues

Hi All, We are facing serious out of memory errors with Multi job project. Configuration contains the following : 1. Parameterized build 2. Multi job Phase 3. Inject passwords to the build as environment variables 4. Set Jenkins user build variables 5. Editable Email notification All of these