Re: Jenkins build says successful but no output is seen

2017-02-24 Thread Sharan Basappa
David, I will remove everything and start with just pwd. I will update how it goes. Maybe it is not related but one thing I changed recently was the native shell. I changed from sh to csh On Friday, 24 February 2017 17:39:07 UTC+5:30, Daniel Beck wrote: > > > On 21.02.2017, at 19:0

Re: Jenkins build says successful but no output is seen

2017-02-23 Thread Sharan Basappa
Hi David, Is there any other forum where I can get help? I haven't got much inputs on this forum On Fri, Feb 24, 2017 at 12:08 AM, David Karr <davidmichaelk...@gmail.com> wrote: > On Wed, Feb 22, 2017 at 9:36 AM, Sharan Basappa > <sharan.basa...@gmail.com> wrote: > > f

build successful but nothing happens

2017-02-23 Thread Sharan Basappa
** opening a new post as no one responded to my original post. I just need some direction. That's all ** My Jenkins build job indicates success but none of the scripts I am executing seem to do anything. I put a simple "pwd" command to echo current working directory but nothing happens. All

Re: Jenkins build says successful but no output is seen

2017-02-22 Thread Sharan Basappa
folks, need some guidance here ... thanks On Tuesday, 21 February 2017 23:39:43 UTC+5:30, Sharan Basappa wrote: > > My Jenkins build job indicates success but none of the scripts I am > executing seem to do anything. I put a simple "pwd" command to echo current > working

Jenkins build says successful but no output is seen

2017-02-21 Thread Sharan Basappa
My Jenkins build job indicates success but none of the scripts I am executing seem to do anything. I put a simple "pwd" command to echo current working directory but nothing happens. All Jenkins reports is "Running shell script" and then nothing is seen. Snippet of Jenkins log: First time

Re: environment variables not getting set

2017-02-15 Thread Sharan Basappa
; > On Wed, Feb 15, 2017 at 10:59 AM Sharan Basappa <sharan@gmail.com > > wrote: > >> In my pipeline script, I am running another script that compiles and runs >> tests. >> The script runs some jobs on sungrid. When the build is run, I see that >

environment variables not getting set

2017-02-15 Thread Sharan Basappa
In my pipeline script, I am running another script that compiles and runs tests. The script runs some jobs on sungrid. When the build is run, I see that qrsh (which is the command to launch job on sungrid) was not found. I went back and executed env to check the path and as expected the path to

Re: Pipeline documentation jenkins-book vs realty?

2017-02-13 Thread Sharan Basappa
Tyler, I have a few questions for which I could not find answers after going through the documentation. Unfortunately, understanding of these are necessary for anyone to create a decent build jobs. 1) Jenkins seems to be executing from a directory named @tmp (and some other names). The files

Re: Multibranch pipeline - source code present but .git file missing

2017-02-12 Thread Sharan Basappa
e syntax of "checkout scm", you can use the "Pipeline > Syntax" hyperlink on the left of pipeline job pages. > > Mark Waite > > On Sat, Feb 11, 2017 at 7:08 AM Sharan Basappa <sharan@gmail.com > > wrote: > >> Daniel, >> >> Don't t

Re: Multibranch pipeline - source code present but .git file missing

2017-02-11 Thread Sharan Basappa
have seen this issue only when I started using multibranch pipeline and not with pipeline or other build job types. Also, in this case alone, I am using Jenkinsfile driven build steps On Saturday, 11 February 2017 15:16:23 UTC+5:30, Daniel Beck wrote: > > > On 11.02.2017, at 05:0

Multibranch pipeline - source code present but .git file missing

2017-02-10 Thread Sharan Basappa
I am using multi-branch pipeline and I find that source code is present under {workspace}@script directory but .git files are missing in any of the directories. So, when I try to stash so that I can move to another branch, I get error saying that, "it does not appear to be a git repository"

Re: Issue with pipeline

2017-02-10 Thread Sharan Basappa
Pipeline ERROR: script returned exit code 128 *Finished* <http://stacktrace.jenkins-ci.org/search?query=Finished>: FAILURE On Tuesday, 7 February 2017 23:45:06 UTC+5:30, Sharan Basappa wrote: > Hi All, > > I am having some trouble executing basic shell commands (highlighted

Re: Pipeline - merge and push

2017-02-08 Thread Sharan Basappa
> wrote: > I would recommend that you include these files in a .gitignore so they are > ignored by git. > > > > -Indra > > > > *From: *<jenkinsci-users@googlegroups.com> on behalf of Sharan Basappa < > sharan.basa...@gmail.com> > *Reply-To: *"j

Pipeline - merge and push

2017-02-08 Thread Sharan Basappa
I have created a pipeline script. The pipeline script runs in a 'topic' branch (e.g. my_feature). Once test stage is successful, I would like to merge this into the master branch and then push the changes to remote. However, I have some doubts. My test stage creates many intermediate files

pipeline steps

2017-02-08 Thread Sharan Basappa
I would like to know if I have multiple steps in my pipeline script and if any one of the steps fails then subsequent steps would not be executed and build would terminate. Is my understanding correct? -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Issue with pipeline

2017-02-08 Thread Sharan Basappa
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: > S

Re: Issue with pipeline

2017-02-08 Thread Sharan Basappa
[root@hd1 workspace]# ls an_example_test-JXUTXQYEXLBFTQ57MDSHQEWRX4WVYMTOO7GTJHX5PXY7SUM2PYKA\@script/ Jenkinsfile Just_Checking simple.csh temp On Wednesday, 8 February 2017 07:54:45 UTC+5:30, Sharan Basappa wrote: > If you see the sequence of commands, you will notice that I have used

Re: Issue with pipeline

2017-02-07 Thread Sharan Basappa
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

Issue with pipeline

2017-02-07 Thread Sharan Basappa
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: Pipeline: wildcard for branch name

2017-01-28 Thread Sharan Basappa
hat's where you ultimately > want to go. > > Mark Waite > > On Sat, Jan 28, 2017 at 5:29 AM Sharan Basappa <sharan@gmail.com > > wrote: > >> Hi Mark, Indra, >> >> If I use wildcard as a branch specifier then what would happen if there >> are mul

Re: Pipeline: wildcard for branch name

2017-01-28 Thread Sharan Basappa
> > checkout scm: [$class: 'GitSCM', branches: [[name: '*/test*']], > userRemoteConfigs: [[url: 'git@hd1:testing']]] > > > > > > *From: *<jenkins...@googlegroups.com > on behalf of Sharan > Basappa <sharan@gmail.com > > *Reply-To: *"jenkins

Re: Pipeline & Git branch

2017-01-28 Thread Sharan Basappa
ary 27, 2017 at 9:12:38 PM UTC-7, Sharan Basappa wrote: >> >> >> I would like to list out all branches in Git with a specific naming >> convention (feature_*) and then start a build process (compile, test and >> publish) for each of those branches. >&

Pipeline & Git branch

2017-01-27 Thread Sharan Basappa
I would like to list out all branches in Git with a specific naming convention (feature_*) and then start a build process (compile, test and publish) for each of those branches. Can someone, please, give me some directions on this? Thanks -- You received this message because you are

Re: Pipeline - stage, node

2017-01-26 Thread Sharan Basappa
I would just like to point out a note from pipeline paper I am reading. It is as follows, Stages are usually the top most element of Pipeline syntax. Stages allow you to group your build step into its component parts. By default, multiple builds of the same pipeline can run concurrently. The

Re: Pipeline - stage, node

2017-01-26 Thread Sharan Basappa
can anyone be kind enough to respond to the query below of mine? It would help me a lot On Saturday, 21 January 2017 23:54:15 UTC+5:30, Sharan Basappa wrote: > Hello, > > I am trying to adapt pipeline as a part of my project. I am starting with > a simple example, thoug

Re: Pipeline: wildcard for branch name

2017-01-26 Thread Sharan Basappa
ary 23, 2017 at 9:37:01 AM UTC-8, Sharan Basappa wrote: >> >> Hi, >> >> I am trying to create pipeline script such that it only a certain >> branches following a naming style are built. >> However, pipeline bails out when I use the wildcard. >> >

Re: Pipeline: wildcard for branch name

2017-01-24 Thread Sharan Basappa
://jenkins.io/doc/pipeline/steps/git/#git-git > -- branch is a string therefore you need to quote it otherwise it seems > it's recognised as a property > > You can also try with the* generic scm step*, explained also in the same > page > > Cheers > > On Monday, 23 Janu

Jenkins: master/slave & distributed builds

2017-01-23 Thread Sharan Basappa
Hi All, I understand that Jenkins has a way to distribute build process. I would like to know how is it different from having one master node in Jenkins and then using that to launch the regular unix based jobs using a grid engine (like Sungrid etc.). I assume I can achieve the same thing. In

Pipeline: wildcard for branch name

2017-01-23 Thread Sharan Basappa
Hi, I am trying to create pipeline script such that it only a certain branches following a naming style are built. However, pipeline bails out when I use the wildcard. The code snippet is below: stage 'build' node { git url: 'git@hd1:testing', branch: test* sh "pwd" sh "cat simple.csh" sh

Pipeline - stage, node

2017-01-21 Thread Sharan Basappa
Hello, I am trying to adapt pipeline as a part of my project. I am starting with a simple example, though, to get my understanding correct. However, after reading several white papers and even after being able to write simple examples, I am stuck with conceptual understanding of pipeline. My