Re: Issue in pipeline step of jenkinsfile

You need to add an intermediate var in your first loop and use this in the sh step sprat...@gmail.com schrieb am Dienstag, 11. Mai 2021 um 14:59:56 UTC+2: > Hey Devin, > Sorry for the late reply , I was down with covid for some time. > the code that you have given i tried and it works , but how

Re: Issue in pipeline step of jenkinsfile

Hey Devin, Sorry for the late reply , I was down with covid for some time. the code that you have given i tried and it works , but how to handle the string parameters ? some string parameters which I am assigning they are also interfering with each other On Fri, Apr 16, 2021 at 9:07 PM Devin

Re: Issue in pipeline step of jenkinsfile

This is a classic issue that a lot of people run into in various programming languages. https://groovyconsole.appspot.com/script/5078409050849280 shows the same problem and one way to fix it (click "edit in console" and then you can

Issue in pipeline step of jenkinsfile

registeries = [1,2,3,4] Map tasks = [:] for (j=0;j<=registeries.size();j++) { tasks["Code ${j}"] = { -> sh "touch ${j}" } } parallel(tasks) sh "ls -lrt" Above code should create files 0,1,2,3,4,5 but the last line ls -lrt only prints 5 which means it is only taking the last

Re: GitHub webhook push CI issue with pipeline projects

I hope you got the solution, If you could suggest me the best practice it will be helpful for me. On Friday, 11 November 2016 09:18:12 UTC+5:30, Cory Grubbs wrote: > > Okstill doesn't solve the problem of having to have two separate > Jenkins projects for every build which is not efficient

Re: Git plugin issue in pipeline

Thanks @Mark. I switched to using refspecs and it seems to have addressed the issue. On Tuesday, June 27, 2017 at 5:53:07 PM UTC-4, Abhijith Reddy wrote: > > Whenever i specify a branch with GitSCM i see the following issue > Couldn't find any revision to build. Verify the repository and branch

Re: Git plugin issue in pipeline

Can you try with something like that inside your Jenkinsfile : node { deleteDir() checkout scm } Jenkins seems to be already able to retrieve your Jenkinsfile, so you don't need to give all SCM details inside it, see

Re: Git plugin issue in pipeline

On Tuesday, June 27, 2017 at 5:01:46 PM UTC-6, Mark Waite wrote: > > I suspect you're encountering a conflict between the git plugin > maintaining compatibility with old behavior, and the desire to support > branch names which contain slashes. > > Refer to the online help in the git plugin for

Re: Git plugin issue in pipeline

I suspect you're encountering a conflict between the git plugin maintaining compatibility with old behavior, and the desire to support branch names which contain slashes. Refer to the online help in the git plugin for alternate ways to define a branch name. The format "word/word" is

Git plugin issue in pipeline

Whenever i specify a branch with GitSCM i see the following issue Couldn't find any revision to build. Verify the repository and branch configuration for this job. Here's my Jenkinsfile node { deleteDir() checkout([$class: 'GitSCM', branches: [[name: 'feature/my-branch]],

Re: Issue with pipeline

Folks, At this point, I am so confused. My Jenkins file is kept at the root of Git directory. I am doing this in branches where I want to do Jenkins build. I am using multibranch pipeline plug-in to define the build on Jenkins server. As I am doing only mock set-up for now, the pipeline job

Re: Issue with pipeline

the {workspace}@script is done during the initial fetch for the Jenkinsfile. Normally the pipeline checkout config. This first checkout is not transfer to the real workspace when you start the script 1. the jenkinsfile checkout inside {workspace}@script. I strongly suggest you get a

Re: Issue with pipeline

> On 09.02.2017, at 03:17, Sharan Basappa wrote: > > But I would like to understand the reason behind having files in > {workspace}@script rather than {workspace} ... The Jenkinsfile is checked out to @script so it's not in the actual workspace (duh), and you can

Re: Issue with pipeline

folks, I was able to resolve this by using {workspace}@script to access the files in the workspace. But I would like to understand the reason behind having files in {workspace}@script rather than {workspace} ... On Wednesday, 8 February 2017 15:51:09 UTC+5:30, Sharan Basappa wrote: > Some

Re: Issue with pipeline

Some updates from the experiments I tried out. I directly logged into the Linux machine where Jenkins is installed. I cd'ed into the workspace and listed the files. My scripts are not listed. I also found additional directories with @scripts suffix to the directories. There the files are listed.

Re: Issue with pipeline

If you see the sequence of commands, you will notice that I have used pwd. Let me list files and see if I can find anything On Wednesday, 8 February 2017 02:09:54 UTC+5:30, David Karr wrote: > On Tuesday, February 7, 2017 at 10:15:06 AM UTC-8, Sharan Basappa wrote: >> >> Hi All, >> >> I am

Re: Issue with pipeline

On Tuesday, February 7, 2017 at 10:15:06 AM UTC-8, Sharan Basappa wrote: > > Hi All, > > I am having some trouble executing basic shell commands (highlighted in > red). I cant figure out the issue. Need some help. This is what I get: > > Branch indexing > > > git rev-parse --is-inside-work-tree #

Re: Issue with pipeline

t 10:15 AM To: Jenkins Users <jenkinsci-users@googlegroups.com> Subject: Issue with pipeline Hi All, I am having some trouble executing basic shell commands (highlighted in red). I cant figure out the issue. Need some help. This is what I get: Branch indexing > git rev-parse --is-inside-w

Issue with pipeline

Hi All, I am having some trouble executing basic shell commands (highlighted in red). I cant figure out the issue. Need some help. This is what I get: Branch indexing > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to git@hd1:testing > git config remote.origin.url

Re: GitHub webhook push CI issue with pipeline projects

The purpose of Github project field In the Jenkins Job configuration is just to make Github available in the Jenkins left-nav. On 11/10/16, 7:48 PM, "jenkinsci-users@googlegroups.com on behalf of Cory Grubbs" wrote:

Re: GitHub webhook push CI issue with pipeline projects

Okstill doesn't solve the problem of having to have two separate Jenkins projects for every build which is not efficient nor scalable to the level I need it to be. I find it hard to believe you can't configure a webhook on a github repo to kick off a specific Jenkins job that isn't

Re: GitHub webhook push CI issue with pipeline projects

The 1st job does not need poll. If you have Github plugin and have configured and installed github-webhook on the source git repository on GitHub, you enable it to trigger with Github build trigger ³Build when a change is pushed to GitHub². You can only associate the pipeline with the source

Re: GitHub webhook push CI issue with pipeline projects

The whole objective is to get away from poll based CI as it places unnecessary and unsustainable load on both the source control system and Jenkins when you have thousands of projects continuously polling. In addition this is not a scalable/efficient solution in that you would have to create 2

Re: GitHub webhook push CI issue with pipeline projects

You can create a job that polls for the commit/push to the application source repository. This job will then simply trigger the pipeline job. On 11/10/16, 9:55 AM, "jenkinsci-users@googlegroups.com on behalf of Cory Grubbs"

Re: GitHub webhook push CI issue with pipeline projects

As a managed service which utilizes Jenkins for CI builds, I have created a generic pipeline script which is used by all projects to build. The script reads in application specific property files which drives what gets executed within the pipeline. The generic pipeline script and the