there is no POM in this directory

Hi I have configure the maven with jenkins. I am using git for source code. but when I run the build I am getting this error. [ERROR] The goal you specified requires a project to execute but there is no POM in this directory (/var/lib/jenkins/workspace/case1). Please verify you invoked Maven

Re: Jenkins REST API

https://stackoverflow.com/questions/25661362/where-can-i-find-jenkins-restful-api-reference https://wiki.jenkins.io/display/JENKINS/Remote+access+API Mark Waite On Tue, Jan 23, 2018 at 8:26 PM wrote: > Jenkins Experts - > > I want to target the Jenkins REST API for some automation. Is there a

Jenkins REST API

Jenkins Experts - I want to target the Jenkins REST API for some automation. Is there a site that lists ALL API's? Example: Get - http:///job//lastBuild/api/json Post - http:///job//build Cheers -- You received this message because you are subscribed to the Google Groups "Jenkins Users" gr

Use 'input' in a non-blocking way

Hi, I am trying to setup a cd pipeline with Jenkins recently, and 'input' is used for manual approval in the pipeline, but it seems that 'input' blocks the executor and won't free the executor util the build is manually approved or cancelled, the pipeline is something like this: pipeline {

Re: A recent change (or bug) in either Docker and/or Jenkins is breaking most tutorials in the Jenkins User Documentation.

Hi everyone, Just a quick follow-up ... It's possible that this issue may have resulted from recent changes in Docker behavior (i.e. in recent Docker versions) which were no longer being handled correctly by the Jenkins Docker Pipeline plugin. Once this PR (https://github.com/jenkinsci/docker-

Re: A recent change (or bug) in either Docker and/or Jenkins is breaking most tutorials in the Jenkins User Documentation.

Thanks so much for all the sleuthing work Damien - you've hit the nail on the head with this one. Cheers, Giles. On 24 January 2018 at 00:43, Damien Duportal wrote: > This issue is related to the "Docker Pipeline" plugin ("docker-workflow") > which has an issue when trying to determine if the e

Re: specifying branches to build for a multi-branch pipeline

Wildcard branches filter trait is the basic way... You probably want https://wiki.jenkins.io/display/JENKINS/SCM+Filter+Branch+PR+Plugin though (assumes your SCMSource has implemented trait support) On Tue 23 Jan 2018 at 19:49, ziffusion wrote: > Hi > > Is there a way get the multi-branch pipel

Re: SSH key forwarding into docker container pipeline

I've tried modifying the Jenkinsfile to the following: pipeline { agent { dockerfile true } stages { stage('Build'){ steps { sshagent(['d288a45e-5b02-4aac-839b-d87cc3a854d0']) { sh 'make' } } }

Re: SSH key forwarding into docker container pipeline

I've tried modifying the Jenkinsfile to the following: pipeline { agent { dockerfile true } stages { stage('Build'){ steps { sshagent(['d288a45e-5b02-4aac-839b-d87cc3a854d0']) { sh 'make debian' } }

SSH key forwarding into docker container pipeline

Hello I'm trying to build a project which Makefile pulls modules from a private repository. How should I forward the SSH key from Jenkins to the docker container? The pipeline which creates the build is pretty very basic but it fails on checkout: pipeline { agent { dockerfile true }

Re: How to change default permissions of created jobs in Jenkins file system

Mark is on the spot, but to specify, it's the user running Tomcat and the environment Tomcat is running under that you want to make sure the umask is set properly on, in your case umask 0002 (to get 775 or -rwrwxr-x). Take care! On Tuesday, 23 January 2018 04:20:28 UTC+1, 黄涛 wrote: > > Hi all,

How do I get access to environment variables in my post block?

At the top of my pipeline (not inside a specific stage) I define an env: environment { MYVA = 'sdkfjlsjflsjflsd'} Now I want to use it in a function call in my post block. I had to do this to get it to work: post { success { script { def MYVA = MYVA

Jenkins .Exe build issue

I am building 7 exes for my project out of which 5 are getting build and the other two are giving error -Source: File Name: light blue.bmp [exec] Position: 0 Error

Re: A recent change (or bug) in either Docker and/or Jenkins is breaking most tutorials in the Jenkins User Documentation.

This issue is related to the "Docker Pipeline" plugin ("docker-workflow") which has an issue when trying to determine if the executor (master or agent) is running inside a container. See issue/PR #120 of "docker-workflow-plugin", in particular https://github.com/jenkinsci/docker-workflow-plugin