Re: Log file for script trigger plugin
On Wednesday, 30 October 2013 21:18:45 UTC+5:30, Srinivasa TN wrote: > > On Wednesday, 30 October 2013 18:32:03 UTC+5:30, maciej wrote: >> >> Srinivasa TN (2013-10-30 13:34): >> >> Hi All, >>I am using Jenkins 1.514 and scripttrigger plugin 0.31 on RHEL 6.3. I >> have written bash script in the plugin configuration to trigger the build >> whenever exit status is XXX. I have put "set -x" in the script. But where >> is the output going? Is there any log file I can check to find what is >> happening? >> >> >> If you want a log file then use: >> echo "some stuff" >> my.log >> >> After build you can archive "my.log" as build artifact. >> >> If you don't want a log file then just use echo it whoulsd be visible in >> the standard build log. >> > I don't want a log file but just wanted to know what is happening. I have > scheduled the job every two hour, so the script in plugin executes every > two hours and upon required exit status, the job should proceed.. but > nothing is happening. So I wanted to check are the steps in script are > being executed or not. > > It was my foolishness.. At the front page of job configuration itself I can see an link to scripttrigger.log. But it stores the log for only one run, how can I make it to have the logs of all the runs? Regards, Seenu. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Log file for script trigger plugin
On Wednesday, 30 October 2013 18:32:03 UTC+5:30, maciej wrote: > > Srinivasa TN (2013-10-30 13:34): > > Hi All, >I am using Jenkins 1.514 and scripttrigger plugin 0.31 on RHEL 6.3. I > have written bash script in the plugin configuration to trigger the build > whenever exit status is XXX. I have put "set -x" in the script. But where > is the output going? Is there any log file I can check to find what is > happening? > > > If you want a log file then use: > echo "some stuff" >> my.log > > After build you can archive "my.log" as build artifact. > > If you don't want a log file then just use echo it whoulsd be visible in > the standard build log. > I don't want a log file but just wanted to know what is happening. I have scheduled the job every two hour, so the script in plugin executes every two hours and upon required exit status, the job should proceed.. but nothing is happening. So I wanted to check are the steps in script are being executed or not. Regards, Seenu. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Log file for script trigger plugin
Hi All, I am using Jenkins 1.514 and scripttrigger plugin 0.31 on RHEL 6.3. I have written bash script in the plugin configuration to trigger the build whenever exit status is XXX. I have put "set -x" in the script. But where is the output going? Is there any log file I can check to find what is happening? Regards, Seenu. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Current build artifact
I had followed your step 3 (ls -ltr | tail -1) but just wanted
to know any other options.
I will explore your suggestion mentioned in step 2, thanks for it.
Regards,
Seenu.
On Monday, 8 July 2013 22:33:36 UTC+5:30, Eric Pyle wrote:
>
> Some thoughts:
>
> 1) If I understand correctly, in your step 1 you run a Maven snapshot
> build, which creates some artifacts. Assuming you are using a Nexus
> repository, you can have step 2 download the required artifact from Nexus.
> You can find an example bash script to do that at [1].
>
> 2) You could also copy that just-built artifact to a known directory
> during step 1. See [2] for an example.
>
> 3) You could write shell script code to look for the latest timestamp
> directory. Something like this:
> ts_dir=`ls -d
> /var/lib/jenkins/jobs/myjob/modules/org.opendaylight.controller$distribution.opendaylight/builds/2*|sort|tail
>
> -1`
>
> Eric
>
>
> [1]
> http://blog.sonatype.com/people/2011/01/downloading-artifacts-from-nexus-with-bash/
> [2]
> http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-artifacts.html
>
>
> On 7/8/2013 4:56 AM, Srinivasa TN wrote:
>
> Sorry for not being clear in articulating my requirement if my first mail:
>
> 1) In step 1 of my build plan, I have maven generate the following file:
>
> /var/lib/jenkins/jobs/myjob/modules/org.opendaylight.controller$distribution.opendaylight/builds/2013-07-05_19-01-16/archive/org.opendaylight.controller/distribution.opendaylight/0.1.0-SNAPSHOT/*.zip
>
> 2) In step 2 of my build plan (execute shell), I need to refer the above
> file. So, I use ${BUILD_ID} to refer
> -
> /var/lib/jenkins/jobs/myjob/modules/org.opendaylight.controller$distribution.opendaylight/builds/${BUILD_ID}/archive/org.opendaylight.controller/distribution.opendaylight/0.1.0-SNAPSHOT/*.zip
>
> 3) But BUILD_ID contains the time in which build started, i.e., it has
> value 2013-07-05_19-00-56.
>
> So now my question is how do I refer the above file in my exec shell?
> (I can't use lastSuccessfullBuild or something like that as my present job
> is still running).
>
> Regards,
> Seenu.
>
> On Monday, 8 July 2013 14:09:20 UTC+5:30, blaz wrote:
>>
>> All tasks within same job execution start in same directory. In such case
>> there should not be any problems with finding build artifacts. This case is
>> not really Jenkins specific.
>> If you want to use artifacts of job A in job B (triggered by job A) you
>> should use Copy Artifact
>> Plugin<http://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin>
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-use...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Current build artifact
Sorry for not being clear in articulating my requirement if my first mail:
1) In step 1 of my build plan, I have maven generate the following file:
/var/lib/jenkins/jobs/myjob/modules/org.opendaylight.controller$distribution.opendaylight/builds/2013-07-05_19-01-16/archive/org.opendaylight.controller/distribution.opendaylight/0.1.0-SNAPSHOT/*.zip
2) In step 2 of my build plan (execute shell), I need to refer the above
file. So, I use ${BUILD_ID} to refer
-
/var/lib/jenkins/jobs/myjob/modules/org.opendaylight.controller$distribution.opendaylight/builds/${BUILD_ID}/archive/org.opendaylight.controller/distribution.opendaylight/0.1.0-SNAPSHOT/*.zip
3) But BUILD_ID contains the time in which build started, i.e., it has
value 2013-07-05_19-00-56.
So now my question is how do I refer the above file in my exec shell?
(I can't use lastSuccessfullBuild or something like that as my present job
is still running).
Regards,
Seenu.
On Monday, 8 July 2013 14:09:20 UTC+5:30, blaz wrote:
>
> All tasks within same job execution start in same directory. In such case
> there should not be any problems with finding build artifacts. This case is
> not really Jenkins specific.
> If you want to use artifacts of job A in job B (triggered by job A) you
> should use Copy Artifact
> Plugin
> .
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Current build artifact
Hi All, My build plan consists of both which compiles and later do some operations on those artifacts using shell commads (using Execute Shell). But I am not finding how to reliable refer to the artifacts of the current build (I tried using BUILD_ID environment variable in the path when accessing the files related to project but it is not reliable - there may be some difference in the time build starts and the file creation and hence both will not have the same value). Any ideas? Regards, Seenu. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Refer a particular version of file in git repo
Hi Mark, My git repo contains mvn repo files as well as some shell scripts which need to be executed during the build. For maven files, I am accessing git the way you have mentioned. Now as part of the same build, I want to execute the shell scripts that are there in the git. So, my question was how to refer to the latest version of the script files that are in the repo that jenkins has already cloned? Regards, Seenu. On Thursday, 4 July 2013 19:03:38 UTC+5:30, Mark Waite wrote: > > That's not the typical way to execute some commands on the current version > of files from a git repo in Jenkins. > > Typically, you'd install the "Git Plugin", then configure a job to use the > Git plugin. In the Git plugin configuration section of that job, you'll > list the Git repository location and the branch or branches to be > monitored. For your initial projects, you'll probably configure the plugin > to poll the Git repository. > > As you get more and more jobs, you'll probably eventually switch from > polling the git repository to using a commit hook. Both techniques work, > and they do very well. > > Mark Waite > > -- > *From:* Srinivasa TN > > *To:* jenkins...@googlegroups.com > *Sent:* Thursday, July 4, 2013 6:48 AM > *Subject:* Refer a particular version of file in git repo > > Hi All, >I am using jenkins 1.514 on Ubuntu 12.10 with git as scm. As part of > my build plan, I want to execute some commands on the current version of > those files in the git repo. For this I did an execute shell where I have > the following commands > > git checkout master > git merge origin/master > > > Is it the right way to do it? > > Regards, > Seenu. > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-use...@googlegroups.com . > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Refer a particular version of file in git repo
Hi All, I am using jenkins 1.514 on Ubuntu 12.10 with git as scm. As part of my build plan, I want to execute some commands on the current version of those files in the git repo. For this I did an execute shell where I have the following commands git checkout master git merge origin/master Is it the right way to do it? Regards, Seenu. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Configuring build name and build id
The plugin "versionnumber" exactly meets my requirement. Thanks to jenkins
team and its plugin writers.
Regards,
Seenu.
On Wednesday, January 30, 2013 8:22:59 PM UTC+5:30, Srinivasa TN wrote:
>
> Hi,
>I am using Jenkins 1.499 on RHEL 6.3. At present, the build id/name is
> just an number or formed out of the build date and time. But I want to
> have the build name as 0.0.0.1 or 0.0.0.1-MMDD-${BUILD_NUMBER} (That is,
> build number in that particular day). The build-name-setter plugin just
> allows to set the display name and that too static. How can I achieve the
> above stuff?
>
> Regards,
> Seenu.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Base Clearcase Plugin Usage
Hi All, I am using Jenkins 1.500 and Base Clearcase Plugin. Is there any link which points to the page which describes the different fields I should configure along with example? Regards, Seenu. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Configuring build name and build id
Hi,
I am using Jenkins 1.499 on RHEL 6.3. At present, the build id/name is
just an number or formed out of the build date and time. But I want to
have the build name as 0.0.0.1 or 0.0.0.1-MMDD-${BUILD_NUMBER} (That is,
build number in that particular day). The build-name-setter plugin just
allows to set the display name and that too static. How can I achieve the
above stuff?
Regards,
Seenu.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
