Re: Jenkins printing every remote branch on all builds [JENKINS-22794]

Hi have you set the option on both master and slaves? BR On Thursday, 25 July 2019 10:25:52 UTC+2, Jordan Sokolic wrote: > > We are experiencing an issue where Jenkins prints every remote branch in > our repository to the console in every build. Since we have several > thousand remote branches,

Create new item - Item name error 'Only alphanumerical characters allowed'

Hi everyone, Since the lastest releases of Jenkins we're having a problem when creating new items. We always get the 'Only alphanumerical characters allowed' error when trying to create a new item. We've tried from multiple browsers, changing our system language and the error persists. We don'

Re: Create new item - Item name error 'Only alphanumerical characters allowed'

Possibly the folder where you're creating those items has a character in its name that is outside the allowed set of characters? On Fri, Jul 26, 2019 at 5:55 AM Laura López Senderos < laurapeopl...@gmail.com> wrote: > Hi everyone, > > Since the lastest releases of Jenkins we're having a problem w

Re: Create new item - Item name error 'Only alphanumerical characters allowed'

Hi Mark, The folder where every jobs are created is '/var/lib/jenkins/jobs'. This is the default folder and we've been able to create items on it since now. Maybe some plugin update, or the jenkins instance update has broken something... We can't rename the jobs neither :/ It's like the regex t

Re: Create new item - Item name error 'Only alphanumerical characters allowed'

I've not seen any report of that issue from anyone other than you. When I asked if a folder containing the job included an unexpected character, I was thinking of a Jenkins folder more than a directory on the file system. The directory on the file system which represents that Jenkins folder would

Pipeline: Expected call wound up catching different method

I got a problem with my Pipeline which has worked fine up until recently. I don't quite understand what the problem is: expected to call Build.checkUpstream but wound up catching releaseUtility.getReleaseBranch; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/ expected to call Bu

Re: Build failure in Jenkins: DependencyCheckAnalyzer

We cleared the m2e cache and that resolved the problem. Thanks y'all for the other tips. Wanted to post this resolution in case ever helpful for anyone else. On Thursday, July 25, 2019 at 11:24:44 AM UTC-4, Mark Waite wrote: > > I suspect that someone removed the OWASP dependency check plugin f

Re: Pipeline: Expected call wound up catching different method

Your Pipeline should be working exactly as it did before, now you are just getting a log message (unless you are using jenkinsfile-runner, in which case an exception is thrown instead, see JENKINS-58407) warning that it has probably never worked correctly , although depending on exactly what the

Re: withDockerContainer in pipeline failing

Hi, did you find a solution ? I'm facing the same problem. How did you correct it ? Le mardi 25 juin 2019 23:52:51 UTC+2, NARASIMHAMURTHY G N a écrit : > > Hi All, > > i have also facing Jenkins Deployment issue. could you possible to help > me to this issue, this error is looks similar to ab