Re: Why does it running on another node?

If this node used "Only build jobs with label restrictions matching this node." option, so a job of don't restrict the job does it still picking up this node? 在 2018年12月17日星期一 UTC+8下午10:37:58，Eric Pyle写道： > > If you don't restrict the job, it will pick one of the available nodes > arbitrarily,

Re: Usage of Jenkins shared library in Job DSL

Hi tre..., I know this thread is getting old, but did you ever get an answer or figure out how to use a Jenkins Shared Library in the Job DSL script, or some workaround? Thanks Philip -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To

Re: Allow a build to be triggered only by a Pipeline

I’m not sure if there is a plugin that lets you do this... I see two solutions: 1. In your pipeline, check if the cause is an upstream job cause and abort if not (functionality will be correct, but run the risk of lots of aborted builds) 2. Write a plugin. Your plugin will need two parts: a

Re: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

You might check that the job definition was not changed recently. If that shows nothing of interest, you could login to the workspace last used for the clone and perform the same commands in that clone. That may help identify what is failing. On Mon, Dec 17, 2018 at 1:11 PM 'Yash Dabhi' via

Re: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

Hi Mark, Thanks for the reply. I tried cloning the branch in my local and it clones fine. Branch exists and able to commit as well. Not sure why it stopped working suddenly. Thanks, Yash On Monday, December 17, 2018 at 2:40:41 PM UTC-5, Mark Waite wrote: > > That seems to indicate that you

Re: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

That seems to indicate that you previously had a branch named '9' and now the branch named '9' no longer exists. Mark Waite On Mon, Dec 17, 2018 at 11:32 AM 'Yash Dabhi' via Jenkins Users < jenkinsci-users@googlegroups.com> wrote: > Hi all, > > when I am trying to run job getting below error.

Allow a build to be triggered only by a Pipeline

Is there a way to allow users to only build a job as part of an upstream / downstream dependency while disallowing direct execution? Thanks! -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving

ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

Hi all, when I am trying to run job getting below error. Getting this while checking out the source code. It happened all of sudden. I was working fine with the same configuration. Please advise what can be done. > git fetch --tags ssh://${git_url}.git CICD > git rev-parse

Re: Why does it running on another node?

If you don't restrict the job, it will pick one of the available nodes arbitrarily, and it doesn't matter whether it is the master or a slave/agent. Once the job has run on a particular node, it will remain there unless that node is unavailable at the time the job starts. This is done to take

Re: pipeline-maven-plugin stucks

Thanks Dan for the feedback. > Love to see Postgres support since all of our in house DB using Postgres We prefer to focus for the moment on MySQL and get it right before extending to other RDBMS (ie PostgreSQL). We picked MySQL because it was the most pervasive RDBMS we looked at. Cyrille

Why does it running on another node?

I have a job it's doesn't use "Restrict where this project can be run" option, why doesn't it running on a master node, but running on a slave node? Jenkins ver. 1.625.1 Could you help me to know? -- You received this message because you are subscribed to the Google Groups "Jenkins Users"