a problem occurred while processing the request.

Hi Team, All of the sudden I have started getting below message when I am launching my current Jenkins setup: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already r

Re: locks vs stage w/concurrency

This is the idiom to get what you are looking for: https://github.com/jenkinsci/workflow-aggregator-plugin/blob/master/demo/repo/Jenkinsfile#L22-L36 On Wed, Sep 28, 2016 at 12:49 AM, James Nord wrote: > The new way to do this is with a milestone. > > https://wiki.jenkins-ci.org/display/JENKINS/P

Re: Multiple pipelines in Jenkinsfile

Did you finish your implementation? Groovy is far from being my native language and it would be really helpful if you could share a snippet that is doing the subdirectory Jenkinsfile discovery and loading. On Thursday, July 21, 2016 at 1:43:18 AM UTC+1, slide wrote: > > The way I am planning on

Master restart when two users access 'manage jenkins'

Hi - I've noticed a hard to catch error triggered only when two users, on different computers, access the 'Manage Jenkins' page: it immediately crashes, with no obvious hints in the log, and the Docker container we're running it in is restarted (it's watched by Marathon). Has anyone else encoun

Re: Pipeline Issue

1 - The master agent needs to identify which branches contain a Jenkinsfile and match the branch selection criteria you provided. In order to do that, the master agent clones the repository and uses that clone for the work on the master agent 3 - I've found no way to change the name of the job wh

Deploy plugin

Hi, Because it now accepts build parameters in tomcat URL, I would like to install jenkins deploy plugin 1.12, which is not available. I tried to build it from the source code, and get a lot of ArrayIndexOutOfExceptions in most unit tests. I tried to switch to tag 1.10, which is the last relea

$WORKSPACE Changing

Not sure what's going on. My workspace seems to be changing mid-build. At the beginning of the build I see: Building in workspace /var/lib/jenkins/workspace/MyApp Then I check out to the same location and everything is cool so far. Next my ant task runs which looks like this: $WORKSPACE/MyP

Re: $WORKSPACE Changing

OK, figured it out. /var/lib/jenkins is a symbolic link to /opt/jenkins, so nm, this is fine... The builds just choose to tell it one way in one place and another way in another place. On Monday, October 3, 2016 at 7:43:59 AM UTC-6, Eric Fetzer wrote: > Not sure what's going on. My workspa

'Parameters from properties file' not working in 2.7.3

Hello, Several of my jobs use 'Parameters from properties file' to pass settings to downstream jobs. The configuration I used in Jenkins 1.625.3 does not appear to work with 2.7.3 I wrote two very simple jobs; one to create a parameter file that was used with 'Trigger parameterized build on ot

Re: 'Parameters from properties file' not working in 2.7.3

Most likely this is because of changes made to address Jenkins issue SECURITY-170 (see Security Advisory ). A job is no longer allowed to accept parameters not explicitly defined in the downstream job. Eric O

using multibranch artifacts in subsequent pipeline

I have a multi-branch pipeline project set up to build some libraries. I want to use the generated artifacts from this pipeline in a subsequent project which is also a multi-branch pipeline. However, in the second project, I would like to copy the artifacts from the first project where the br

Multi-platform binaries in a single job

*Current system* To better understand my requirements, I need to first give an overview of our current CI build system, and why it is too cumbersome. Our company has its own legacy build environments for our core products, which has worked for over 30 years, and we do not have the resources to

Re: 'Parameters from properties file' not working in 2.7.3

Eric, I think you're right. My problem is caused by the new security policies. I have not found the right combination of settings to make things work as before. I tried starting Jenkins with -Dhudson.model.ParametersActon.keepUndefinedParameters=true, but that did not solve the problem. Have y

Re: 'Parameters from properties file' not working in 2.7.3

We just upgraded our Jenkins from 1.642.3 to 2.7.4 and with that issue in mind, we did add the keepUndefinedParameters=true. We haven't seen any problems. We do have some jobs that trigger a downstream job with parameters from a properties file. Is that what you're doing? Or are you using "Inje

Re: 'Parameters from properties file' not working in 2.7.3

Yes. we're using parameters from a properties file. > > > > > > -- 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.

[Coverity Plugin for Jenkins] Question regarding open issue JENKINS-20670 and closed issue BZ 60322 (defect limit)

All, I am currently operating in the following environment: Jenkins version: 2.10 Coverity Plugin for Jenkins: 1.80 (same behavior in version 1.7.3 as well) Coverity Server Version: 7.7.0 I have a single Coverity Project / Stream which contains approx. 6200 defects (most of which are now

Re: Multi-platform binaries in a single job

> On 03.10.2016, at 18:08, Marcus MacWilliam > wrote: > > I am completely new to Jenkins, so do not know how to set this up, and would > appreciate any > pointers on how to do this. Looks like the optimal use case for Pipeline. More: https://jenkins.io/doc/pipeline/ -- You received this m

Shell and Path variable

I created a sample job in Jenkins2.0 to get the SHELL and PATH variables. Here is the console output: Started by user admin Building in workspace /var/lib/jenkins/workspace/path [path] $ /usr/bin/zsh -xe /tmp/hudson7499585998548354807.sh +/tmp/hudson7499585998548354807.sh:2> echo /bin/bash /bin/b

Re: Shell and Path variable

Have you tried putting #!/usr/bin/zsh at the top of your little jenkins build script? I imagine the default shell for your jenkins is defined by the settings associated with the user that owns the jenkins process running on your unix system and the duplicate java entries may also be the result

Re: 'Parameters from properties file' not working in 2.7.3

Just noticed, there is a typo in the property name below (Acton vs. Action). Could that be the problem? On 10/3/2016 1:15 PM, Steve K wrote: Eric, I think you're right. My problem is caused by the new security policies. I have not found the right combination of settings to make things work

Re: 'Parameters from properties file' not working in 2.7.3

Thanks for noticing the typo Eric. I *think *I had it correct when I added it to the Jenkins startup script. I can't verify, because I have since removed it. There was another thread on this topic (see: https://groups.google.com/d/msg/jenkinsci-users/sUs7NOiLKQ0/lrP-leh3OgAJ) where, basicall

multiple git + git publisher - how?

I would like to configure jenkins to do the following: 1. checkout from a list of git repos 2. sub jobs build for 3 targets 3. test the build 4. publish the results back to multiple git repos I have the system checking out and building successfully right now. it looks like there is a plugin call

Creating groovy script to configure slave node properties >> "Restrict jobs execution at node"

Hi All, I am trying to automate the process of creating a slave node on jenkins server , creating users and then and also allow certain users to access only certain slave nodes. The automation is to be achieved via a groovy script. Here's my script thus far import jenkins.model.* import huds

Re: Pipeline Issue

Hi Mark,Thanks for your reply.1- I have not configured anything for my master node and still it creates on master. So does that mean it will be running the same way on master node.3- actually my GIT branch structu