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 n
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 i
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 is
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 smal
> 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 e.g. deleteDir() to remove le
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 upda
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. P
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 having
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 #
Do you have the simple.csh file checked-in or not?
From: on behalf of Sharan Basappa
Reply-To: "jenkinsci-users@googlegroups.com"
Date: Tuesday, February 7, 2017 at 10:15 AM
To: Jenkins Users
Subject: Issue with pipeline
Hi All,
I am having some trouble executing basic shel
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 git@hd1:te
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:
>Okstill doesn't solve the problem of having to have two separate
>Jenkins
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 connect
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 repo
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 J
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" wrote:
>As a managed service which utilizes Jenkins for CI builds, I hav
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 applicati
17 matches
Mail list logo
