Re: is Jenkins using the latest version from msysgit

2013-09-05 Thread Lee Ho Yeung
version 1.529,
now i got problem at this post
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/d4373df2-e9fd-4896-913c-f626e2cf03ed/got-many-errors-after-import-database-to-database-project-in-vs2012


On Wed, Sep 4, 2013 at 10:42 PM,  wrote:

>  What version are you using? I remember , I had difficulty using 1.528
> with Copy Artifact plugin.
>
> ** **
>
> You might want to check open issue related to Jenkins latest version.
>
> ** **
>
> Let us know whether this helped or not.
>
> ** **
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *nicolas de loof
> *Sent:* Wednesday, September 04, 2013 2:01 AM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: is Jenkins using the latest version from msysgit
>
> ** **
>
> right, and what's you issue then ?
>
> ** **
>
> 2013/9/4 Ho Yeung Lee 
>
> i set the command like this without environment variables such as
> %WORKSPACE%,
>
> ** **
>
> the path is using 
>
> ** **
>
> ** **
>
> ** **
>
> C:\Users\LAB-User2\Documents\GitHub\testing005
>
> C:\Users\LAB-User2\Documents\GitHub\testing005\.git
>
> C:\Users\LAB-User2\Documents\GitHub\testing005\Database3
>
> C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3.sln
>
> C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3\sp_insert_rpt_criteria.sql
>
>  ** **
>
> 1. Execute window batch
>
> ** **
>
> echo 'Copying Adventure Works Solution to Jenkins workspace...'
>
> xcopy /s /E /H /Y /R
> "C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3"
> "C:\Program Files (x86)\Jenkins\jobs\testing003\workspace" 
>
>  
>
> echo 'Deleting artifacts from previous builds...'
>
> del
> "C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3\*_publish.zip"
> /F /Q
>
> ** **
>
> ** **
>
> 2. MSBUILD
>
> ** **
>
> C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe
>
> ** **
>
> "C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3\Database3.sqlproj"
> /p:Configuration=Database3 /p:Platform=AnyCPU /t:Build;Publish
> /p:SqlPublishProfilePath='C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3\Database3.publish.xml'
> /p:UpdateDatabase=False
>
> --
> 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.
>
> ** **
>
> --
> 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.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/ejGpa1EMHtk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@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.


Plugin require for BTS

2013-09-05 Thread Gaurang shah
Hi Guys, 

I have my automation project configured on the Jenkins, Now everytime a 
test case fails management is interested in knowing the reason. 

Is it a bug in automation ? 
is it a product bug ?
is it a timing or network issue ? 

In all the above case if necessary bug Id. 

is there any plugin avaible which serves this puprose

I want something like below 





-- 
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: Run Job on Remote Slave node

2013-09-05 Thread Gaurang shah
Is there any other way apart from this. ??

If i go and change the Maven and JDK setting to download from the internet 
it works fine.

Is there any other thing i need to know about how Jenkins run program on 
slave node, one thing i came to know is it build project on slave node as 
well before running it. 

Gaurang SHah


On Thursday, 5 September 2013 19:24:19 UTC+5:30, Jes Struck wrote:
>
>
> Hello Gaurang,
>
> it would be a good ide to consider to split it into two jobs one for 
> building and one for the running of the program, you can easely share 
> reslult between job's either with an artifact manegement system like 
> artifactory or similar.
>
> Or you can use the archive function in jenkins that can actually also copy 
> between jobs.
>
> If you run into any problems just get back and ill bee happy to help ;)
>
>
> 2013/9/5 Gaurang shah >
>
>> Hi Guys, 
>>
>> I have an automation project on the Jenkins in which I want job run on 
>> Remote Slave Node, However it looks like when I bind my project with remote 
>> slave, it builds project on that slave as well. 
>>
>> In my Jenkins I have specified JDK and Maven Path locally rather then to 
>> install it from internet. 
>>
>> However the when i run the Job on remote node it tries to find the JDK 
>> and Maven in same directory, which is creating problem. Is there any way I 
>> can use the JDK and Maven installed on Jenkins Host machine to build the 
>> job but it run on remote node ??
>>
>> Gaurang Shah
>>
>> -- 
>> 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.
>>
>
>
>
> -- 
>
> [image: 
> ]
>  *Jes Struck, *
> Consultant
> j...@praqma.net 
> +45 31 42 09 00
> Skype:jes.struck *Praqma A/S*
> www.praqma.net
> Allerød Stationsvej 4
> DK-3450 Allerød
> +45 36 77 27 62  
> 
>
> 

-- 
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.


Got "no such job" when trigger a build with jenkins-cli 1.525 as an administrator permission after enable LDAP and role strategy security

2013-09-05 Thread viola lu
I have setup a jenkins server and enable LDAP and role strategy security. I 
can build jobs in UI as administrator account. But if i trigger builds via 
jenkins-cli , it failed, and reported an error" no such job ." 

icap@icap-build-linux-5:/icap/jazz_build/build/Core_Sonar/ant_build/lib$ 
java -jar jenkins-cli.jar -s http://9.111.211.30:8080/ version --username 
** --password **
1.525
icap@icap-build-linux-5:/icap/jazz_build/build/Core_Sonar/ant_build/lib$ 
java -jar jenkins-cli.jar -s http://9.111.211.30:8080/ list-jobs --username 
** --password **

Setup_Jenkins
test
testSlave1
Upload_Artifacts_and_Result

icap@icap-build-linux-5:/icap/jazz_build/build/Core_Sonar/ant_build/lib$ 
java -jar jenkins-cli.jar -s http://9.111.211.30:8080/ build test 
--username ** --password **

*No such job 'test'*

Is this a bug?

-- 
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: jenkins and clearcase plugin

2013-09-05 Thread Larry Brigman
Nope. Changing /etc/environment doesn't add the path into the java
instance.

In this case the user is just a placeholder without a login shell; a daemon
account.
Something in the init script or in the jenkins config file would need to add
the path for clearcase.


On Wed, Sep 4, 2013 at 2:37 PM, Richard Bywater  wrote:

> Does sticking the PATH statement in /etc/environment help? (I can't
> remember if that gets invoked in this particular case though)
>
> Richard.
>
>
> On Thu, Sep 5, 2013 at 7:25 AM, Larry Brigman wrote:
>
>> Finally got it.  Had to hack the init script to declare the PATH variable
>> on the invocation line
>> by pre-pending it to the JAVA_CMD.  runuser was wiping out the PATH
>> variable.
>> There probably should be a better way to do this.
>>
>> Here is my change in the init script to get clearcase to function
>> properly.
>> JAVA_CMD="umask 002;PATH=${PATH}:/usr/atria/bin; $JENKINS_JAVA_CMD
>> $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR"
>>
>>
>>
>> On Wed, Sep 4, 2013 at 11:52 AM, Larry Brigman 
>> wrote:
>>
>>> Ok.  I'm looking at the info from the config page->System Info and the
>>> path doesn't show
>>> /usr/atria/bin.  I added that to the path in the init script but it
>>> doesn't seem to get added to
>>> jenkins when I restart the service.
>>>
>>> The cleartool path is set as part of the config
>>> The path variable only shows
>>> /sbin:/usr/sbin:/bin:/usr/bin
>>>
>>>
>>>
>>> On Wed, Sep 4, 2013 at 10:40 AM, Larry Brigman 
>>> wrote:
>>>
 Updated the path to ensure that Path is there on service start.
 The executable is there.
 Same result.
 Backed the clearcase plugin down to 1.3.18. same result.

 I was able to run the command by hand and it created the needed view.



 On Tue, Sep 3, 2013 at 4:48 PM, Richard Bywater wrote:

> I'd check that the directory that cleartool is located at is on the
> PATH for the user than runs Jenkins.
>
> Richard
>
>
> On Wednesday, September 4, 2013, Larry Brigman wrote:
>
>>  I'm trying to use the jenkins clearcase plugin (1.3.19) in linux
>> from a machine
>> that functions in clearcase.
>> This machine is doing manual builds from the command line without
>> issue.
>> I'm using dynamic views to do these builds.
>>
>> Even with everything looking configured correctly it looks like
>> things are just wrong.
>> Here is the error output:
>>
>> Building in workspace /var/lib/jenkins/jobs/top_main/workspace
>> [WARNING] load rules are empty!
>> [workspace] $ cleartool lsview Jenkins_jenkins_master_top_main
>> [INFO] computeChangeLogBeforeCheckout = false
>> [INFO] computeChangeLogAfterCheckout  = true
>> [workspace] $ cleartool lsview Jenkins_jenkins_master_top_main
>> [workspace] $ cleartool mkview -tag Jenkins_jenkins_master_top_main 
>> -stgloc -auto
>> java.io.IOException: Cannot run program "cleartool" (in directory 
>> "/var/lib/jenkins/jobs/top_main/workspace"): java.io.IOException: 
>> error=2, No such file or directory
>>  at java.lang.ProcessBuilder.start(ProcessBuilder.java:470)
>>  at hudson.Proc$LocalProc.(Proc.java:244)
>>  at hudson.Proc$LocalProc.(Proc.java:216)
>>  at hudson.Launcher$LocalLauncher.launch(Launcher.java:773)
>>  at hudson.Launcher$ProcStarter.start(Launcher.java:353)
>>  at 
>> hudson.plugins.clearcase.HudsonClearToolLauncher.getLaunchedProc(HudsonClearToolLauncher.java:157)
>>  at 
>> hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:115)
>>  at hudson.plugins.clearcase.ClearToolExec.mkview(ClearToolExec.java:661)
>>  at 
>> hudson.plugins.clearcase.action.BaseDynamicCheckoutAction.createView(BaseDynamicCheckoutAction.java:129)
>>  at 
>> hudson.plugins.clearcase.action.BaseDynamicCheckoutAction.checkout(BaseDynamicCheckoutAction.java:72)
>>  at 
>> hudson.plugins.clearcase.AbstractClearCaseScm.checkout(AbstractClearCaseScm.java:666)
>>  at hudson.model.AbstractProject.checkout(AbstractProject.java:1408)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)
>>  at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)
>>  at hudson.model.Run.execute(Run.java:1603)
>>  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
>>  at hudson.model.ResourceController.execute(ResourceController.java:88)
>>  at hudson.model.Executor.run(Executor.java:247)
>> Caused by: java.io.IOException: java.io.IOException: error=2, No such 
>> file or directory
>>  at java.lang.UNIXProcess.(UNIXProcess.java:148)
>>  at java.lang.ProcessImpl.start(ProcessImpl.java:65)
>>  at java.lang.ProcessBuilder.start(ProcessBuilder.java:452)
>>
>>

Re: shell execution produces "couldn't flush stdout" error

2013-09-05 Thread John Russell
I find I have much better luck in "Execute shell" build steps if I put

#!/bin/bash at the top.

It tends to make the behavior much more consistent. YMMV

On Wednesday, September 4, 2013 4:30:04 AM UTC-4, Matthias wrote:
>
> Hello,
>
> when using pipes in shell scripts I often get the error mentioned in the 
> subject line.
>
> To reproduce the issue add an "execute shell" build step to a new job and 
> run the following:
>
> echo replace e by a | sed 's_e_a_g' | echo done
>
> This might not make much sense - but it generates the error "couldn't 
> flush stdout" while this does not happen when executing the same in a 
> terminal.
>
>
> The jenkins console output produces:
>
>
> [EnvInject] - Loading node environment variables.
> Building on master in workspace 
> /home/jenkins/build-server/jobs/test.sed/workspace
> [workspace] $ /bin/sh -xe /tmp/hudson7236481234921041257.sh
> + echo replace e by a
> + echo done
> done
> + sed s_e_a_g
> sed: couldn't flush stdout: Broken pipe
> Finished: SUCCESS
>
>
>
> best regards,
> Matthias
>

-- 
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: github plugin: commit status configuration/authentication?

2013-09-05 Thread William Soula
I don't know of any other github pull request plugins, but I am able to get the 
github pull request builder to work for our enterprise server, even with a 
funky security certificate.  The biggest distinction I see is the ability for 
it to work for enterprise and public at the same time.  That would be a good 
feature request for the github pull request builder, and one I just realized I 
might need soon :)

Will

On 09/05/13 10:40, Andy Freeland wrote:
Unlike all of the Git/Github related Jenkins plugins I tried, I could actually 
get it to work. :)

I could also point it at both GitHub for Enterprise and 
github.com repos on the same CI server, which is important 
to us, because we have projects on both.


On Thu, Sep 5, 2013 at 10:20 AM, William Soula 
mailto:william.so...@drillinginfo.com>> wrote:
Did you look at the github pull request builder?  If so, what benefits does 
leeroy have over it?

https://wiki.jenkins-ci.org/display/JENKINS/Github+pull+request+builder+plugin

Will

On 09/05/13 09:58, Andy Freeland wrote:
I now run Leeroy (https://github.com/litl/leeroy) on my Jenkins server. It 
listens for GitHub pull request notifications, triggers a Jenkins build, and 
sets the commit status based on the result of the build.

This has been working great for me for github.com and GitHub 
for Enterprise repos.


On Thu, Sep 5, 2013 at 9:50 AM, Aaron Cain 
mailto:aaron.c...@oncenter.com>> wrote:
Did you ever find an answer to get "Set build status on GitHub commit" 
configured?


On Thursday, March 7, 2013 3:11:39 PM UTC-6, Andy Freeland wrote:
I'm also not seeing any logs from the post-build actions, so I have no idea 
what it's doing.

On Thursday, March 7, 2013 4:05:14 PM UTC-5, Andy Freeland wrote:
I've been trying to use the commit status functionality from the latest version 
of the GitHub plugin (https://github.com/jenkinsci/github-plugin/pull/23). I 
built and installed the plugin, but I haven't found anywhere to configure 
authentication to actually post the commit statuses.

In my repository, I've tried setting the git url to 
https://oauth_to...@github.com/rouge8/jenkins-test.git, but I've also tried 
git://github.com/rouge8/jenkins-test.git
 with no luck.

I have the post-build action "Set build status on GitHub commit" activated, but 
I haven't found anywhere to configure the authentication.

Has anyone successfully configured the plugin?
--
You received this message because you are subscribed to a topic in the Google 
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-users/tDzto-wILeM/unsubscribe.

To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@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.

--
You received this message because you are subscribed to a topic in the Google 
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-users/tDzto-wILeM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@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.

-- 
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.


hudson.util.IOException2 - Jenkins - VSS error

2013-09-05 Thread natesh . shanmuga
My jenkins - vss configuration and mvn build and weblogic deployment works 
fine on a Windows 32 machine 
but failing on windows 64 machine and getting this exception in the first 
step - trying to connect to vss from jenkins.
hudson.util.IOException2: com4j.ComException: 80040154 CoCreateInstance 
failed : Class not registered : .\com4j.cpp:135

VSS will not work on 64bit OS or Jenkins -VSS combination doesnt work on 
 64 bit OS or otherwise ? Please advise.

Thanks.

-- 
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: Prevent incrementing build number on failures

2013-09-05 Thread Peter Soncek
Thanks for the information.  I will take a look at the plugin and see if we 
can take advantage of it somehow.  Otherwise, I will see if I can impose 
this change on my group without too much uproar.

Peter

On Thursday, September 5, 2013 9:25:57 AM UTC-5, Volodymyr Kostyrko wrote:
>
> 05.09.2013 16:36, peterman1002 wrote: 
> > Hello, 
> > 
> > I am new to Jenkins and trying to setup my build environment.  I have 
> > noticed that when a build fails, the build number is still incremented. 
> > How can I prevent Jenkins from doing this?  I'm not here to start a 
> > debate on whether that is the correct behavior or not.  I just want to 
> > know how I can do this for my environment here. 
>
> Well that's wrong as any failed build results in mailings and logs 
> tailed to them. You don't need them to be tied up to the next 
> successfull build, don't you? 
>
> If you need to count "good" build maybe you need to look at Version 
> Number Plug-In? 
> (https://wiki.jenkins-ci.org/display/JENKINS/Version+Number+Plugin) It 
> can create your own $VERSION based on how many successful builds were in 
> total, today or this month. 
>
> -- 
> Sphinx of black quartz, judge my vow. 
>
>

-- 
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: scriptler won't let "Trigger/call builds on other projects" block on build

2013-09-05 Thread John Russell
The initiating build logs eventually update with the result of the 
downstream build but the initiating build does not block while this happens.

On Thursday, September 5, 2013 2:37:01 PM UTC-4, John Russell wrote:
>
> I have a scriptler build step setting my build description just before I 
> call "Trigger/call builds on other projects" on a downstream job which 
> blocks waiting for that build.
>
> If I have the scriptler step there, the "Trigger..." step will not block 
> waiting for downstream. The build ends immediately with FAILURE. If I 
> remove the scriptler step it works fine. If I put the scriptler code into a 
> System Groovy Script build step in the same spot it also works fine and 
> blocks on the "Trigger..." step as I want.
>
> Is there something about scriptler that would make "Trigger..." not block 
> correctly? Any workarounds?  Thanks.
>
>

-- 
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.


scriptler won't let "Trigger/call builds on other projects" block on build

2013-09-05 Thread John Russell
I have a scriptler build step setting my build description just before I 
call "Trigger/call builds on other projects" on a downstream job which 
blocks waiting for that build.

If I have the scriptler step there, the "Trigger..." step will not block 
waiting for downstream. The build ends immediately with FAILURE. If I 
remove the scriptler step it works fine. If I put the scriptler code into a 
System Groovy Script build step in the same spot it also works fine and 
blocks on the "Trigger..." step as I want.

Is there something about scriptler that would make "Trigger..." not block 
correctly? Any workarounds?  Thanks.

-- 
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: github plugin: commit status configuration/authentication?

2013-09-05 Thread Aaron Cain
Did you ever find an answer to get "Set build status on GitHub commit" 
configured?

On Thursday, March 7, 2013 3:11:39 PM UTC-6, Andy Freeland wrote:
>
> I'm also not seeing any logs from the post-build actions, so I have no 
> idea what it's doing.
>
> On Thursday, March 7, 2013 4:05:14 PM UTC-5, Andy Freeland wrote:
>>
>> I've been trying to use the commit status functionality from the latest 
>> version of the GitHub plugin (
>> https://github.com/jenkinsci/github-plugin/pull/23). I built and 
>> installed the plugin, but I haven't found anywhere to configure 
>> authentication to actually post the commit statuses.
>>
>> In my repository, I've tried setting the git url to 
>> https://oauth_to...@github.com/rouge8/jenkins-test.git, but I've also 
>> tried git://github.com/rouge8/jenkins-test.git with no luck.
>>
>> I have the post-build action "Set build status on GitHub commit" 
>> activated, but I haven't found anywhere to configure the authentication.
>>
>> Has anyone successfully configured the 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.


Re: github plugin: commit status configuration/authentication?

2013-09-05 Thread Andy Freeland
I now run Leeroy (https://github.com/litl/leeroy) on my Jenkins server. It
listens for GitHub pull request notifications, triggers a Jenkins build,
and sets the commit status based on the result of the build.

This has been working great for me for github.com and GitHub for Enterprise
repos.


On Thu, Sep 5, 2013 at 9:50 AM, Aaron Cain  wrote:

> Did you ever find an answer to get "Set build status on GitHub commit"
> configured?
>
>
> On Thursday, March 7, 2013 3:11:39 PM UTC-6, Andy Freeland wrote:
>>
>> I'm also not seeing any logs from the post-build actions, so I have no
>> idea what it's doing.
>>
>> On Thursday, March 7, 2013 4:05:14 PM UTC-5, Andy Freeland wrote:
>>>
>>> I've been trying to use the commit status functionality from the latest
>>> version of the GitHub plugin (https://github.com/jenkinsci/**
>>> github-plugin/pull/23).
>>> I built and installed the plugin, but I haven't found anywhere to configure
>>> authentication to actually post the commit statuses.
>>>
>>> In my repository, I've tried setting the git url to
>>> https://OAUTH_TOKEN@github.**com/rouge8/jenkins-test.git,
>>> but I've also tried 
>>> git://github.com/rouge8/**jenkins-test.gitwith
>>>  no luck.
>>>
>>> I have the post-build action "Set build status on GitHub commit"
>>> activated, but I haven't found anywhere to configure the authentication.
>>>
>>> Has anyone successfully configured the plugin?
>>>
>>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/tDzto-wILeM/unsubscribe.
>
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@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: github plugin: commit status configuration/authentication?

2013-09-05 Thread Andy Freeland
Unlike all of the Git/Github related Jenkins plugins I tried, I could
actually get it to work. :)

I could also point it at both GitHub for Enterprise and github.com repos on
the same CI server, which is important to us, because we have projects on
both.


On Thu, Sep 5, 2013 at 10:20 AM, William Soula <
william.so...@drillinginfo.com> wrote:

>  Did you look at the github pull request builder?  If so, what benefits
> does leeroy have over it?
>
>
> https://wiki.jenkins-ci.org/display/JENKINS/Github+pull+request+builder+plugin
>
> Will
>
> On 09/05/13 09:58, Andy Freeland wrote:
>
> I now run Leeroy (https://github.com/litl/leeroy) on my Jenkins server.
> It listens for GitHub pull request notifications, triggers a Jenkins build,
> and sets the commit status based on the result of the build.
>
>  This has been working great for me for github.com and GitHub for
> Enterprise repos.
>
>
> On Thu, Sep 5, 2013 at 9:50 AM, Aaron Cain wrote:
>
>> Did you ever find an answer to get "Set build status on GitHub commit"
>> configured?
>>
>>
>> On Thursday, March 7, 2013 3:11:39 PM UTC-6, Andy Freeland wrote:
>>>
>>> I'm also not seeing any logs from the post-build actions, so I have no
>>> idea what it's doing.
>>>
>>> On Thursday, March 7, 2013 4:05:14 PM UTC-5, Andy Freeland wrote:

 I've been trying to use the commit status functionality from the latest
 version of the GitHub plugin (
 https://github.com/jenkinsci/github-plugin/pull/23). I built and
 installed the plugin, but I haven't found anywhere to configure
 authentication to actually post the commit statuses.

  In my repository, I've tried setting the git url to
 https://oauth_to...@github.com/rouge8/jenkins-test.git, but I've also
 tried git://github.com/rouge8/jenkins-test.git with no luck.

  I have the post-build action "Set build status on GitHub commit"
 activated, but I haven't found anywhere to configure the authentication.

  Has anyone successfully configured the plugin?

>>>   --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Users" group.
>>  To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-users/tDzto-wILeM/unsubscribe.
>>
>>
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-users+unsubscr...@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.
>
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/tDzto-wILeM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@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: Prevent incrementing build number on failures

2013-09-05 Thread Edwin Castro
On 9/5/13 7:25 AM, Volodymyr Kostyrko wrote:
> If you need to count "good" build maybe you need to look at Version
> Number Plug-In?
> (https://wiki.jenkins-ci.org/display/JENKINS/Version+Number+Plugin) It
> can create your own $VERSION based on how many successful builds were
> in total, today or this month.

+1 And it gives you the ability to not increment that version when
failed builds occur too.

--
Edwin G. Castro

-- 
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: github plugin: commit status configuration/authentication?

2013-09-05 Thread William Soula
Did you look at the github pull request builder?  If so, what benefits does 
leeroy have over it?

https://wiki.jenkins-ci.org/display/JENKINS/Github+pull+request+builder+plugin

Will
On 09/05/13 09:58, Andy Freeland wrote:
I now run Leeroy (https://github.com/litl/leeroy) on my Jenkins server. It 
listens for GitHub pull request notifications, triggers a Jenkins build, and 
sets the commit status based on the result of the build.

This has been working great for me for github.com and GitHub 
for Enterprise repos.


On Thu, Sep 5, 2013 at 9:50 AM, Aaron Cain 
mailto:aaron.c...@oncenter.com>> wrote:
Did you ever find an answer to get "Set build status on GitHub commit" 
configured?


On Thursday, March 7, 2013 3:11:39 PM UTC-6, Andy Freeland wrote:
I'm also not seeing any logs from the post-build actions, so I have no idea 
what it's doing.

On Thursday, March 7, 2013 4:05:14 PM UTC-5, Andy Freeland wrote:
I've been trying to use the commit status functionality from the latest version 
of the GitHub plugin (https://github.com/jenkinsci/github-plugin/pull/23). I 
built and installed the plugin, but I haven't found anywhere to configure 
authentication to actually post the commit statuses.

In my repository, I've tried setting the git url to 
https://oauth_to...@github.com/rouge8/jenkins-test.git, but I've also tried 
git://github.com/rouge8/jenkins-test.git
 with no luck.

I have the post-build action "Set build status on GitHub commit" activated, but 
I haven't found anywhere to configure the authentication.

Has anyone successfully configured the plugin?
--
You received this message because you are subscribed to a topic in the Google 
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-users/tDzto-wILeM/unsubscribe.

To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@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.

-- 
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: Prevent incrementing build number on failures

2013-09-05 Thread Volodymyr Kostyrko

05.09.2013 16:36, peterman1002 wrote:

Hello,

I am new to Jenkins and trying to setup my build environment.  I have
noticed that when a build fails, the build number is still incremented.
How can I prevent Jenkins from doing this?  I'm not here to start a
debate on whether that is the correct behavior or not.  I just want to
know how I can do this for my environment here.


Well that's wrong as any failed build results in mailings and logs 
tailed to them. You don't need them to be tied up to the next 
successfull build, don't you?


If you need to count "good" build maybe you need to look at Version 
Number Plug-In? 
(https://wiki.jenkins-ci.org/display/JENKINS/Version+Number+Plugin) It 
can create your own $VERSION based on how many successful builds were in 
total, today or this month.


--
Sphinx of black quartz, judge my vow.

--
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: Prevent incrementing build number on failures

2013-09-05 Thread Matthew.Webber
>> But if you really what to do this, i think it can be done by hacking the 
>> file placed
>> $hudson/jobs//nextBuildNumber in the end of you build if you now 
>> it failed,

Don’t do that. Jenkins code assumes that the number increases with each run 
(pass or fail). If you invalidate that assumption, you can break things in all 
sorts of unpredictable ways.


-- 
This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
 



-- 
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: Prevent incrementing build number on failures

2013-09-05 Thread Peter Soncek
I will see if I can convince my group that this behavior is intended and 
see if they can live with it.  I am just sick of the old Cruise Control 
application that hasn't been updated in like 5 years.

Peter

On Thursday, September 5, 2013 9:12:46 AM UTC-5, matthew...@diamond.ac.uk 
wrote:
>
> >> But if you really what to do this, i think it can be done by hacking 
> the file placed 
> >> $hudson/jobs//nextBuildNumber in the end of you build if you 
> now it failed, 
>
> Don’t do that. Jenkins code assumes that the number increases with each 
> run (pass or fail). If you invalidate that assumption, you can break things 
> in all sorts of unpredictable ways. 
>
>
> -- 
> This e-mail and any attachments may contain confidential, copyright and or 
> privileged material, and are for the use of the intended addressee only. If 
> you are not the intended addressee or an authorised recipient of the 
> addressee please notify us of receipt by returning the e-mail and do not 
> use, copy, retain, distribute or disclose the information in or attached to 
> the e-mail. 
> Any opinions expressed within this e-mail are those of the individual and 
> not necessarily of Diamond Light Source Ltd. 
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
> attachments are free from viruses and we cannot accept liability for any 
> damage which you may sustain as a result of software viruses which may be 
> transmitted in or with the message. 
> Diamond Light Source Limited (company no. 4375679). Registered in England 
> and Wales with its registered office at Diamond House, Harwell Science and 
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom 
>
>
>
>
>

-- 
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: Prevent incrementing build number on failures

2013-09-05 Thread Peter Soncek
Thank you for your replies.  We are trying to migrate from Cruise Control, 
so there a build failure did not receive a build number.  I am trying to 
mimic some Cruise Control behavior to help convince my group to migrate.  
If too many things are different, I don't think I will get approval.

Peter

On Thursday, September 5, 2013 9:04:38 AM UTC-5, Jes Struck wrote:
>
> I must claim that i think you are going in the wrong direction.
>
> But if you really what to do this, i think it can be done by hacking the 
> file placed $hudson/jobs//nextBuildNumber in the end of you build 
> if you now it failed, this would probably work best if implemented in 
> groovy where you have access to the model.
>
> or you might be able to do it directly from groovy or with a java plugin.
>
>
> Mark: 
> it's been a vile but i now that for at least a couple of years ago it was 
> possible it simply overwritten what ever was in the folder with the new 
> result.
>
>
>
>
> 2013/9/5 peterman1002 >
>
>> Hello,
>>
>> I am new to Jenkins and trying to setup my build environment.  I have 
>> noticed that when a build fails, the build number is still incremented.  
>> How can I prevent Jenkins from doing this?  I'm not here to start a debate 
>> on whether that is the correct behavior or not.  I just want to know how I 
>> can do this for my environment here.
>>
>> Thank you,
>> Peter
>>
>> -- 
>> 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.
>>
>
>
>
> -- 
>
> [image: 
> ]
>  *Jes Struck, *
> Consultant
> j...@praqma.net 
> +45 31 42 09 00
> Skype:jes.struck *Praqma A/S*
> www.praqma.net
> Allerød Stationsvej 4
> DK-3450 Allerød
> +45 36 77 27 62 
>  
>
> 

-- 
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: Prevent incrementing build number on failures

2013-09-05 Thread Jes Struck
I must claim that i think you are going in the wrong direction.

But if you really what to do this, i think it can be done by hacking the
file placed $hudson/jobs//nextBuildNumber in the end of you build
if you now it failed, this would probably work best if implemented in
groovy where you have access to the model.

or you might be able to do it directly from groovy or with a java plugin.


Mark:
it's been a vile but i now that for at least a couple of years ago it was
possible it simply overwritten what ever was in the folder with the new
result.




2013/9/5 peterman1002 

> Hello,
>
> I am new to Jenkins and trying to setup my build environment.  I have
> noticed that when a build fails, the build number is still incremented.
> How can I prevent Jenkins from doing this?  I'm not here to start a debate
> on whether that is the correct behavior or not.  I just want to know how I
> can do this for my environment here.
>
> Thank you,
> Peter
>
> --
> 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.
>



-- 

[image: 
]
*Jes Struck, *
Consultant
j...@praqma.net
+45 31 42 09 00
Skype:jes.struck *Praqma A/S*
www.praqma.net
Allerød Stationsvej 4
DK-3450 Allerød
+45 36 77 27 62


-- 
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: Prevent incrementing build number on failures

2013-09-05 Thread Mark Waite
You can't.  At least, you can't reuse the same job number for a later build 
because the job number uniquely identifies the results of that job and is 
used to store the results of that job in the file system.

If you want a monotonically increasing number which only increases when you 
successfully build, I think you'll need to implement that in your build 
scripts, since the build number / job number is not something you can use 
to count successful builds.

We did something like that by increasing the version number in a file 
controlled by the SCM system, then we only committed/pushed that change 
when the job was successful.

Mark Waite

On Thursday, September 5, 2013 7:36:29 AM UTC-6, Peter Soncek wrote:
>
> Hello,
>
> I am new to Jenkins and trying to setup my build environment.  I have 
> noticed that when a build fails, the build number is still incremented.  
> How can I prevent Jenkins from doing this?  I'm not here to start a debate 
> on whether that is the correct behavior or not.  I just want to know how I 
> can do this for my environment here.
>
> Thank you,
> Peter
>

-- 
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: Run Job on Remote Slave node

2013-09-05 Thread Jes Struck
Hello Gaurang,

it would be a good ide to consider to split it into two jobs one for
building and one for the running of the program, you can easely share
reslult between job's either with an artifact manegement system like
artifactory or similar.

Or you can use the archive function in jenkins that can actually also copy
between jobs.

If you run into any problems just get back and ill bee happy to help ;)


2013/9/5 Gaurang shah 

> Hi Guys,
>
> I have an automation project on the Jenkins in which I want job run on
> Remote Slave Node, However it looks like when I bind my project with remote
> slave, it builds project on that slave as well.
>
> In my Jenkins I have specified JDK and Maven Path locally rather then to
> install it from internet.
>
> However the when i run the Job on remote node it tries to find the JDK and
> Maven in same directory, which is creating problem. Is there any way I can
> use the JDK and Maven installed on Jenkins Host machine to build the job
> but it run on remote node ??
>
> Gaurang Shah
>
> --
> 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.
>



-- 

[image: 
]
*Jes Struck, *
Consultant
j...@praqma.net
+45 31 42 09 00
Skype:jes.struck *Praqma A/S*
www.praqma.net
Allerød Stationsvej 4
DK-3450 Allerød
+45 36 77 27 62


-- 
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: IRCbot plugin fails with ngricd

2013-09-05 Thread Seiji Sogabe
Hi,

If you can configure ngircd.conf, then set "MaxNickLength" to more than 11.
Its default value is 9, but Nickname of the plugin is "jenkins-bot" (11 chars).

2013/8/31 Alex O'Ree :
> Hi, I'm running a ngircd server in a private lan and wanted to get the
> Jenkins IRC bot setup with it. Are there any known issues with ngircd with
> the IRC bot? The log has a message like
> Could not log into the IRC server : :address 461 jenkins user "Syntax error
>
> The irc server just says connection closed
>
> --
> 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.



-- 
s.sogabe at gmail.com

-- 
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.


Prevent incrementing build number on failures

2013-09-05 Thread peterman1002
Hello,

I am new to Jenkins and trying to setup my build environment.  I have 
noticed that when a build fails, the build number is still incremented.  
How can I prevent Jenkins from doing this?  I'm not here to start a debate 
on whether that is the correct behavior or not.  I just want to know how I 
can do this for my environment here.

Thank you,
Peter

-- 
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.


Run Job on Remote Slave node

2013-09-05 Thread Gaurang shah
Hi Guys, 

I have an automation project on the Jenkins in which I want job run on 
Remote Slave Node, However it looks like when I bind my project with remote 
slave, it builds project on that slave as well. 

In my Jenkins I have specified JDK and Maven Path locally rather then to 
install it from internet. 

However the when i run the Job on remote node it tries to find the JDK and 
Maven in same directory, which is creating problem. Is there any way I can 
use the JDK and Maven installed on Jenkins Host machine to build the job 
but it run on remote node ??

Gaurang Shah

-- 
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: Git push back changes

2013-09-05 Thread David Karlsen
Yeah - I'm left with some BOFH operating Jenkins - and it's installed on an
ancient RHEL5 box which have no git binaries.
We can compile it by hand (in fact I have) - but that results in having to
configure the path for the native git differently on the different boxes
(we have a fair amount of slaves).
I'll do some hacks on the PATH so git shows up in path and see how that
goes.

Even though if I get this to work, we also have some more exotic slaves
running AIX, where it's not straightforward to get git in place (again
dependent on corporate BOFH).


2013/9/5 Mark Waite 

> I believe my testing of the Git plugin 2.0 beta confirmed that it was able
> to push back.  However, I think it will be better for you if you stay with
> the released plugin and use command line Git rather than JGit as your
> executable.  Is there a compelling reason you must use jgit?
>
> I recommend against Git plugin 2.0 beta for production work because it has
> other serious problems.  For example:
>
> https://issues.jenkins-ci.org/browse/JENKINS-19043 - hangs "Updating
> references" with large repos
> https://issues.jenkins-ci.org/browse/JENKINS-18988 - exception fails
> checkout sometimes
> https://issues.jenkins-ci.org/browse/JENKINS-18960 - cloning large repo
> is dramatically slower
> https://issues.jenkins-ci.org/browse/JENKINS-19108 - fails to checkout
> specific branch
> https://issues.jenkins-ci.org/browse/JENKINS-19305 - shallow clone
> doesn't work
> https://issues.jenkins-ci.org/browse/JENKINS-19037 - error dialog in
> preference edits
> https://issues.jenkins-ci.org/browse/JENKINS-19036 - serialization errors
> on slaves
> https://issues.jenkins-ci.org/browse/JENKINS-18957 - null pointer
> exception
>
> The git plugin 2.0 beta jgit implementation is a significant improvement
> over the jgit implementation in git plugin 1.5.0, but I don't think it is
> ready for production yet.
>
> Mark Waite
>
>   --
>  *From:* David Karlsen 
> *To:* jenkinsci-users@googlegroups.com
> *Sent:* Thursday, September 5, 2013 1:37 AM
>
> *Subject:* Re: Git push back changes
>
> Thanks! Would pushing work if I went for git-plugin 2.0 beta?
>
>
> 2013/9/5 Mark Waite 
>
> I think the key problem in that list is "using jgit executable".  The
> jgit implementation in the current released Git plugin is not able to push
> to a central repository, along with many other limitations.
>
> You'll need to use the command line git implementation if you want to push
> back to a central repository.
>
> There are several other bugs related to the jgit implementation, if you're
> interested in them.  Even the Git plugin beta 2.0 still seems to have a
> number of rough spots with the jgit implementation.
>
> Mark Waite
>
>   --
>  *From:* David Karlsen 
> *To:* jenkinsci-users@googlegroups.com
> *Sent:* Wednesday, September 4, 2013 8:24 AM
> *Subject:* Re: Git push back changes
>
> My config:
> Repository url:
> http://username:credenti...@test.fswiki.evry.com:7990/scm/tac/tac-jfr-server.git
> name: stash
> branches to build:
> stash/topic/**
> stash/dev
>
> under 2nd advanced I have:
>   Checkout/merge to local branch (optional): master (tried with and w/o
> value here)
> Config user.name Value: the userid
> Config user.email Value: the mail adr
>
> Merge options:
> merge before build is checked,
> name of repository: stash
> branch to merge to: master
>
> using jgit executable
>
> then under post build actions, I have, for the git publisher:
> Push Only If Build Succeed: checked
> merge results: checked
> branches:
> branch to push: master
> target remote name: stash
>
> from console log:
>
> Building on master in workspace /var/lib/jenkins/jobs/tac-jfr-srv/workspace
> Checkout:workspace / /var/lib/jenkins/jobs/tac-jfr-srv/workspace - 
> hudson.remoting.LocalChannel@1b8223f2
> Using strategy: Default
> Last Built Revision: Revision a8ea258e0efe1d514f31c2c4b5cc60ea6ed6b3c6 
> (stash/dev)
> Fetching changes from 1 remote Git repository
> Commencing build of Revision d5b0609fcb1061ee658d971ef5bffb06c1d40646 
> (stash/dev)
> Merging Revision d5b0609fcb1061ee658d971ef5bffb06c1d40646 (stash/dev) onto 
> master
>
> . ok building
>
> Skipping Sonar analysis
> Pushing HEAD to branch master of stash repository
> Opening connection
> Counting objects
> Finding sources
> Writing objects
> Pushing HEAD to branch master at repo stash
> Opening connection
> Counting objects
> Finding sources
> Writing objects
> No emails were triggered.
>
>
>
>
> 2013/9/2 Mark Waite 
>
> The bug you referenced is fixed in the current versions of the git client
> plugin and the git plugin.  I can confirm that Git plugin versions 1.4.0
> and 1.5.0 are able to publish changes when used with git client plugin
> 1.1.2.
>
> Unfortunately, that probably doesn't help you, since there is still some
> reason that your publish attempt is failing.  You'll need to do more
> investigating to understand why publish works for others and not in t

Help with Locale Plugin

2013-09-05 Thread Eduardo Dias
Hi All,

I am experiencing in Jenkins a language change even that the plugin is set
to a defined language and to ignore the browser (Jenkins change from
English to Portuguese). Beyond that I have included in java options the
parameters -Duser.language=en -Duser.country=US

Jenkins Release: 1.509.2
Locale Plugin: 1.2

Any help will be appreciated.

Regards,

Eduardo

-- 
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: Help needed with MsBuild plugin

2013-09-05 Thread Ginga, Dick
FWIW, We build for both VS 2008 and VS 2010. I have taken the contents of the 
vcvarsall.bat file and made it a Properties file on the master. Then I use 
"Prepare an environment for the run" and set the "Properties File Path" to 
$JENKINS_HOME\usercontent\vs2010env.properties and click "load script and 
properties file form the master" and the environment is all setup for using the 
MSBuild build step.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: Wednesday, September 04, 2013 9:45 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Help needed with MsBuild plugin

Isn't the message "error TRK0005: Failed to locate: "CL.exe". The system cannot 
find the file specified. " an indication that you may have failed to call 
vcvarsall.bat for your specific Visual Studio before starting the Jenkins slave 
agent on that machine?

I thought that Visual Studio used that technique to allow users to install 
multiple Visual Studio versions on a single machine, and then select which 
Visual Studio they want to use for a command line compile by invoking the 
corresponding vcvarsall.bat script for that Visual Studio version.

I don't think the MSBuild plugin is the right one to decide which Visual Studio 
version you want to run, though I guess it could be extended to have some form 
of list of alternative Visual Studio versions which it should attempt to 
configure before running the build.

Mark Waite


From: "dhrutiben.pa...@wellsfargo.com" 
mailto:dhrutiben.pa...@wellsfargo.com>>
To: jenkinsci-users@googlegroups.com
Sent: Wednesday, September 4, 2013 9:42 AM
Subject: RE: Help needed with MsBuild plugin

I set MSBuild.exe at configure system location and for my jobs , I just use the 
command 'Execute Batch Command" and write my query.
It works for me so far.


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich
Sent: Wednesday, September 04, 2013 8:23 AM
To: jenkinsci-users@googlegroups.com
Subject: RE: Help needed with MsBuild plugin

Do you use the MSBuild plugin or just specify a 'Windows batch command' build 
step?

Does your path variable on your slave include:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN;

?

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of 
dhrutiben.pa...@wellsfargo.com
Sent: 04 September 2013 16:14
To: jenkinsci-users@googlegroups.com
Subject: RE: Help needed with MsBuild plugin

Sorry David, but it is hard to understand your problem.

I am giving my code snippet so you can compare and check the difference.

Jenkins Job:

Execute windows batch command
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe 
/t:Rebuild /p:Configuration=%BuildType% /p:Platform="%BuildPlatform%" 
/verbosity:normal  %workspace%MyProj.sln


And check whether you have set up environment variables on your build server. 
E.g. C:\winodws\system32


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich
Sent: Wednesday, September 04, 2013 8:07 AM
To: jenkinsci-users@googlegroups.com
Subject: RE: Help needed with MsBuild plugin

I think there is not much to say.

The master configuration sets the MSBuild path to:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe

The build step is:

MS Build file: MSVC\MyProj.sln
Command line arguments: /p:Configuration=" release" /p:useenv=true 
/flp:logfile=MyOutput.log;verbosity=diagnostic

David

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of 
dhrutiben.pa...@wellsfargo.com
Sent: 04 September 2013 15:54
To: jenkinsci-users@googlegroups.com
Subject: RE: Help needed with MsBuild plugin

Can you provide configuration settings for your job , if possible?
And what are the steps you are adding for MSBuild?

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich
Sent: Wednesday, September 04, 2013 7:49 AM
To: jenkinsci-users@googlegroups.com
Subject: RE: Help needed with MsBuild plugin

Hi

Thanks for your reply.

Yes, I had already done that.

David


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of 
dhrutiben.pa...@wellsfargo.com

Re: Git push back changes

2013-09-05 Thread Mark Waite
I believe my testing of the Git plugin 2.0 beta confirmed that it was able to 
push back.  However, I think it will be better for you if you stay with the 
released plugin and use command line Git rather than JGit as your executable.  
Is there a compelling reason you must use jgit?

I recommend against Git plugin 2.0 beta for production work because it has 
other serious problems.  For example:

https://issues.jenkins-ci.org/browse/JENKINS-19043 - hangs "Updating 
references" with large repos

https://issues.jenkins-ci.org/browse/JENKINS-18988 - exception fails checkout 
sometimes

https://issues.jenkins-ci.org/browse/JENKINS-18960 - cloning large repo is 
dramatically slower

https://issues.jenkins-ci.org/browse/JENKINS-19108 - fails to checkout specific 
branch

https://issues.jenkins-ci.org/browse/JENKINS-19305 - shallow clone doesn't work

https://issues.jenkins-ci.org/browse/JENKINS-19037 - error dialog in preference 
edits

https://issues.jenkins-ci.org/browse/JENKINS-19036 - serialization errors on 
slaves

https://issues.jenkins-ci.org/browse/JENKINS-18957 - null pointer exception


The git plugin 2.0 beta jgit implementation is a significant improvement over 
the jgit implementation in git plugin 1.5.0, but I don't think it is ready for 
production yet.

Mark Waite



>
> From: David Karlsen 
>To: jenkinsci-users@googlegroups.com 
>Sent: Thursday, September 5, 2013 1:37 AM
>Subject: Re: Git push back changes
> 
>
>
>Thanks! Would pushing work if I went for git-plugin 2.0 beta?
>
>
>
>2013/9/5 Mark Waite 
>
>I think the key problem in that list is "using jgit executable".  The jgit 
>implementation in the current released Git plugin is not able to push to a 
>central repository, along with many other limitations.
>>
>>
>>You'll need to use the command line git implementation if you want to push 
>>back to a central repository.
>>
>>
>>There are several other bugs related to the jgit implementation, if you're 
>>interested in them.  Even the Git plugin beta 2.0 still seems to have a 
>>number of rough spots with the jgit implementation.
>>
>>
>>Mark Waite
>>
>>
>>
>>>
>>> From: David Karlsen 
>>>To: jenkinsci-users@googlegroups.com 
>>>Sent: Wednesday, September 4, 2013 8:24 AM
>>>Subject: Re: Git push back changes
>>> 
>>>
>>>
>>>My config:
>>>Repository url: 
>>>http://username:credenti...@test.fswiki.evry.com:7990/scm/tac/tac-jfr-server.git
>>>name: stash
>>>branches to build:
>>>stash/topic/**
>>>
>>>stash/dev
>>>
>>>
>>>
>>>under 2nd advanced I have:
>>>  Checkout/merge to local branch (optional): master (tried with and w/o 
>>>value here)
>>>Config user.name Value: the userid
>>>Config user.email Value: the mail adr
>>>
>>>Merge options:
>>>merge before build is checked, 
>>>name of repository: stash
>>>branch to merge to: master
>>>
>>>using jgit executable
>>>
>>>then under post build actions, I have, for the git publisher:
>>>Push Only If Build Succeed: checked
>>>merge results: checked
>>>branches: 
>>>branch to push: master
>>>target remote name: stash
>>>
>>>from console log:
>>>
>>>Building on master in workspace /var/lib/jenkins/jobs/tac-jfr-srv/workspace
Checkout:workspace / /var/lib/jenkins/jobs/tac-jfr-srv/workspace - 
hudson.remoting.LocalChannel@1b8223f2
Using strategy: Default
Last Built Revision: Revision a8ea258e0efe1d514f31c2c4b5cc60ea6ed6b3c6 
(stash/dev)
Fetching changes from 1 remote Git repository
Commencing build of Revision d5b0609fcb1061ee658d971ef5bffb06c1d40646 
(stash/dev)
Merging Revision d5b0609fcb1061ee658d971ef5bffb06c1d40646 (stash/dev) onto 
master
>>>. ok building
>>>Skipping Sonar analysis
Pushing HEAD to branch master of stash repository
Opening connection
Counting objects
Finding sources
Writing objects
Pushing HEAD to branch master at repo stash
Opening connection
Counting objects
Finding sources
Writing objects
No emails were triggered.
>>> 
>>>
>>>
>>>
>>>2013/9/2 Mark Waite 
>>>
>>>The bug you referenced is fixed in the current versions of the git client 
>>>plugin and the git plugin.  I can confirm that Git plugin versions 1.4.0 and 
>>>1.5.0 are able to publish changes when used with git client plugin 1.1.2.


Unfortunately, that probably doesn't help you, since there is still some 
reason that your publish attempt is failing.  You'll need to do more 
investigating to understand why publish works for others and not in the 
case you're testing.


Mark Waite



>
> From: David Karlsen 
>To: jenkinsci-users@googlegroups.com 
>Sent: Monday, September 2, 2013 2:53 AM
>Subject: Git push back changes
> 
>
>
>I'm having problems getting jenkins to push back the merged branch to 
>origin repo. (everything else works but the push back to the repository).
>
>
>Looks like this issue:
>http://jenkins-ci.361315.n4.nabble.com/Git-publisher-fails-to-push-td4659177.h

VSS Plugin - Workspace Folder Structure

2013-09-05 Thread Andre Greeff
Greetings all... (:

I'm somewhat new to CI servers in general so I was expecting a somewhat 
steep learning curve... Jenkins has made life so very easy though, I'm most 
of the way through my config and so far I've only had to do minimal 
Googling.

Right now though, I'm having a problem with the VSS plugin 
(link). 
Let me start with my current configuration... All projects in question are 
built using NetBeans 7, so all NB's baggage comes along with it 
unfortunately.

For Jenkins:

   - Jenkins home directory: C:\Jenkins
   - Launched with "java -jar C:\Jenkins\jenkins.war" to run as user
   - Active workspace: C:\Jenkins\workspace

VSS Plugin options for ProjectX

   - VSS Folder Path: "$/Andre - Test/ProjectX/"
  - This folder contains 'build.xml', 'lib', 'nbproject' (excl 
  'private') and 'src'.
   
Project Settings:

   - Name: ProjectX
   - Other than pointing Ant to local NB installation folder and 
   configuring VSS, everything else is default.


When pulling files from VSS, the plugin strips the '$' from the VSS folder 
path and recreates that structure inside the workspace folder. So for 
ProjectX as described above, Jenkins now has my source files in:

   - C:\Jenkins\jobs\ProjectX\workspace\Andre - Test\ProjectX\
  - This folder contains 'build.xml', 'lib', 'nbproject' (excl 
  'private') and 'src'.
   

In order to get Jenkins to build this, I now have to manually set the 
buildfile path for Ant to be "Andre - Test\ProjectX". Doing that works fine 
though, and it only needs to be done once, so it's not that bad I suppose. 
I'd still like to know if it's possible to get this olugin to stop 
recreating the project parent folder structure from SourceSafe inside my 
workspace. I'd like the plugin to instead do the following:

   - Pull source from VSS path ("$/Andre - Test/ProjectX/")
   - Place files into "C:\Jenkins\jobs\ProjectX\workspace
  - So this folder contains 'build.xml' [, ...]
   - Build project using standard project workspace folder


Looking at the VSS plugin source code, if line 233 of 
VSSSCM.java
 is changed from...
String localPath = file.getAbsolutePath() + "/" + vssPath.substring(2);
...to...
String localPath = file.getAbsolutePath() + "/";
...then I think it would achieve what I'm looking for. But surely there 
must be an easier way for a non-programmer to get this working...? I am, 
after all, only an enthusiastic and adventurous software tester. (:

Anybody have any bright ideas here?

-- 
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: Important Doubt - about how configurate jenkins with Django application in windows xp as server

2013-09-05 Thread JonathanRRogers
On Tuesday, September 3, 2013 4:50:15 PM UTC-4, Carlos Palomares Campos 
wrote:
>
> Hi everyboby,
>
> First I am sorry if this message or question is upset for you, but I dont 
> know where can I look for answers to this question. In my case I have been 
> working with hudson and java projects using ANT and MAVEN in linux systems 
> but currently I am working from 1 month ago in a new project with Python, 
> Django web framework, mysql and Subversion but in this case with a windows 
> xp as operative system, yeah I know that is very strange mix but in my case 
> the company where currently I am working prefers this technology with 
> windows and therefore I can not use some features or others tools 
> furthermore I am suffering the rules of a proxy, so... anyway my 
> question is if anyone know how can I build a jenkins project fro dwonalod a 
> project from subversion in windows and rebuild a project and restart an 
> apache using xampp.
>

> In the future my intentio is integrate everything with seleniun test and 
> sonar tool but I insist I always have been working with java and maven tool 
> or ant tool but now in this new environment I dont know how can I do it? Do 
> you know any tutorial for dummies about how to do it?
>
> Thanks in advance. 
>

The place to start learning Jenkins is:
https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins>

The place to start learning about Selenium is:
http://docs.seleniumhq.org/>

Without more specific questions, I doubt you'll be able to get much help on 
this list.

-- 
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.


Matrix projects and Git pulls

2013-09-05 Thread Paulo Matos
Hi,

I have two jobs, one configures and builds a piece of software and another 
is triggered to test the build and passes through the git sha of the build.
The test job is a matrix project with one axis (arch) and two variants 
(arm, intel).

However, the git repository is being pulled 3 times, one on the workspace 
root and again for each variant, so I end up with:
workspace/
  arch/intel/gcc
  arch/arm/gcc
  gcc

Why is my gcc repository showing up at the root of the workspace as well?

-- 
Paulo Matos

-- 
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: GUI testing on a linux slave

2013-09-05 Thread Trystan Louboutin
Normally this is done by the Xvnc plugin:
"The $DISPLAY environment variable is set for the build by the plugin." (
https://wiki.jenkins-ci.org/display/JENKINS/Xvnc+Plugin)

thank you anyway


2013/9/4 Richard Lavoie 

> Did you set the environment variable DISPLAY to redirect the display of
> your UI application to the VNC and/or XVFB display ?
>
>
> On Wed, Sep 4, 2013 at 12:44 PM, Trystan L.  wrote:
>
>> Hi,
>>
>> I use a master to build and test on two slaves:
>>
>>- Linux slave launched via ssh
>>- Win7 as a windows service
>>
>> I am performing some UI tests on both, no problem on Win7 slave but it
>> fails on linux one.
>>
>> I tried vnc plugin and start a session before the build but nothing
>> better, idem with Xvbf plugin.
>>
>> may be this is due to a specific needs of VTK library (based on OpenGL),
>> it causes the following error :
>>
>> vtkXOpenGLRenderWindow (0xc15b1b0): Could not find a decent visual
>>
>> vtkXOpenGLRenderWindow (0xc482be0): Cannot create GLX context.
>>
>>
>> I also tried setting LIBGL_ALWAYS_INDIRECT=y but still failed.
>>
>> anyone has a idea ?
>>
>> thanks for any help !
>>
>> Trystan
>>
>> --
>> 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.
>>
>
>
>
> --
> Richard Lavoie
> IT consultant / consultant en informatique
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/N04osvYUPzQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@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.


Build success however created stored procedure not exist in database

2013-09-05 Thread Ho Yeung Lee


VS2012, use Jenkins with Git and Msbuild

the database project i do not use import database as expect to use git to 
download source to local and use Jenkins to deploy

sp_insert_rpt_criteria already exist, then i create sp_insert_rpt_criteria2 
and copy code to database project

in Jenkins, build success,

however, stored procedure do not exist in database after search with 
SELECT OBJECT_NAME(id) 
FROM syscomments 
WHERE [text] LIKE '%sp_insert_rpt_criteria2%' 
AND OBJECTPROPERTY(id, 'IsProcedure') = 1 
GROUP BY OBJECT_NAME(id)


Started by user anonymous 
Building in workspace C:\Program Files (x86)\Jenkins\jobs\testing004\workspace
Checkout:workspace / C:\Program Files (x86)\Jenkins\jobs\testing004\workspace - 
hudson.remoting.LocalChannel@ee8538
Using strategy: Default
Last Built Revision: Revision cba51fdbcdee2a075d79de74143fc032b6cc5958 
(origin/HEAD, origin/master)
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
Seen branch in repository origin/HEAD
Seen branch in repository origin/master
Seen 2 remote branches
Commencing build of Revision cba51fdbcdee2a075d79de74143fc032b6cc5958 
(origin/HEAD, origin/master)
Checking out Revision cba51fdbcdee2a075d79de74143fc032b6cc5958 (origin/HEAD, 
origin/master)
Warning : There are multiple branch changesets here
Path To MSBuild.exe: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe
Executing the command cmd.exe /C 
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe 
C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3.sln && exit 
%%ERRORLEVEL%% from C:\Program Files (x86)\Jenkins\jobs\testing004\workspace
[workspace] $ cmd.exe /C 
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe 
C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3.sln && exit 
%%ERRORLEVEL%%
Microsoft (R) Build Engine version 4.0.30319.17929
[Microsoft .NET Framework, version 4.0.30319.18034]
Copyright (C) Microsoft Corporation. All rights reserved.

Building the projects in this solution one at a time. To enable parallel build, 
please add the "/m" switch.
Build started 9/5/2013 3:42:09 PM.
Project 
"C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3.sln" on 
node 1 (default targets).
ValidateSolutionConfiguration:
  Building solution configuration "Debug|Any CPU".
Project 
"C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3.sln" (1) is 
building 
"C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3\Database3.sqlproj"
 (2) on node 1 (default targets).
GenerateSqlTargetFrameworkMoniker:
Skipping target "GenerateSqlTargetFrameworkMoniker" because all output files 
are up-to-date with respect to the input files.
CoreCompile:
Skipping target "CoreCompile" because all output files are up-to-date with 
respect to the input files.
SqlBuild:
Skipping target "SqlBuild" because all output files are up-to-date with respect 
to the input files.
CopyFilesToOutputDirectory:
  Database3 -> 
C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3\bin\Debug\Database3.dll
SqlPrepareForRun:
  Database3 -> 
C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3\bin\Debug\Database3.dacpac
IncrementalClean:
  Deleting file 
"C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3\obj\Debug\Model.xml".
Done Building Project 
"C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3\Database3.sqlproj"
 (default targets).
Done Building Project 
"C:\Users\LAB-User2\Documents\GitHub\testing005\Database3\Database3.sln" 
(default targets).

Build succeeded.
0 Warning(s)
0 Error(s)

Time Elapsed 00:00:00.36
Finished: SUCCESS

-- 
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: Help needed with MsBuild plugin

2013-09-05 Thread David Aldrich
Hi Mark

Thanks for your reply.

I have found this issue:

https://issues.jenkins-ci.org/browse/JENKINS-16452

where you have also discussed this.

Given that we run Jenkins as a Windows service, and given that it is not 
possible to run vcvarsall.bat in conjunction with the MSBuild plugin from 
Jenkins, I think it is best for us to use a 'Windows batch command' build step 
in the Jenkins job and call vcvarsall.bat and MSBuild.exe explicitly there.

It seems to me that the MSBuild plugin is not very useful because of this.

BR

David

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: 05 September 2013 02:45
To: jenkinsci-users@googlegroups.com
Subject: Re: Help needed with MsBuild plugin

Isn't the message "error TRK0005: Failed to locate: "CL.exe". The system cannot 
find the file specified. " an indication that you may have failed to call 
vcvarsall.bat for your specific Visual Studio before starting the Jenkins slave 
agent on that machine?

I thought that Visual Studio used that technique to allow users to install 
multiple Visual Studio versions on a single machine, and then select which 
Visual Studio they want to use for a command line compile by invoking the 
corresponding vcvarsall.bat script for that Visual Studio version.

I don't think the MSBuild plugin is the right one to decide which Visual Studio 
version you want to run, though I guess it could be extended to have some form 
of list of alternative Visual Studio versions which it should attempt to 
configure before running the build.

Mark Waite


From: "dhrutiben.pa...@wellsfargo.com" 
mailto:dhrutiben.pa...@wellsfargo.com>>
To: jenkinsci-users@googlegroups.com
Sent: Wednesday, September 4, 2013 9:42 AM
Subject: RE: Help needed with MsBuild plugin

I set MSBuild.exe at configure system location and for my jobs , I just use the 
command 'Execute Batch Command" and write my query.
It works for me so far.


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich
Sent: Wednesday, September 04, 2013 8:23 AM
To: jenkinsci-users@googlegroups.com
Subject: RE: Help needed with MsBuild plugin

Do you use the MSBuild plugin or just specify a 'Windows batch command' build 
step?

Does your path variable on your slave include:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN;

?

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of 
dhrutiben.pa...@wellsfargo.com
Sent: 04 September 2013 16:14
To: jenkinsci-users@googlegroups.com
Subject: RE: Help needed with MsBuild plugin

Sorry David, but it is hard to understand your problem.

I am giving my code snippet so you can compare and check the difference.

Jenkins Job:

Execute windows batch command
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe 
/t:Rebuild /p:Configuration=%BuildType% /p:Platform="%BuildPlatform%" 
/verbosity:normal  %workspace%MyProj.sln


And check whether you have set up environment variables on your build server. 
E.g. C:\winodws\system32


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich
Sent: Wednesday, September 04, 2013 8:07 AM
To: jenkinsci-users@googlegroups.com
Subject: RE: Help needed with MsBuild plugin

I think there is not much to say.

The master configuration sets the MSBuild path to:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe

The build step is:

MS Build file: MSVC\MyProj.sln
Command line arguments: /p:Configuration=" release" /p:useenv=true 
/flp:logfile=MyOutput.log;verbosity=diagnostic

David

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of 
dhrutiben.pa...@wellsfargo.com
Sent: 04 September 2013 15:54
To: jenkinsci-users@googlegroups.com
Subject: RE: Help needed with MsBuild plugin

Can you provide configuration settings for your job , if possible?
And what are the steps you are adding for MSBuild?

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich
Sent: Wednesday, September 04, 2013 7:49 AM
To: jenkinsci-users@googlegroups.com
Subject: RE: Help needed with MsBuild plugin

Hi

Thanks for your reply.

Yes, I had already done that.

David


From: jenkinsci-users@googlegroups.com

Re: Git push back changes

2013-09-05 Thread David Karlsen
Thanks! Would pushing work if I went for git-plugin 2.0 beta?


2013/9/5 Mark Waite 

> I think the key problem in that list is "using jgit executable".  The
> jgit implementation in the current released Git plugin is not able to push
> to a central repository, along with many other limitations.
>
> You'll need to use the command line git implementation if you want to push
> back to a central repository.
>
> There are several other bugs related to the jgit implementation, if you're
> interested in them.  Even the Git plugin beta 2.0 still seems to have a
> number of rough spots with the jgit implementation.
>
> Mark Waite
>
>   --
>  *From:* David Karlsen 
> *To:* jenkinsci-users@googlegroups.com
> *Sent:* Wednesday, September 4, 2013 8:24 AM
> *Subject:* Re: Git push back changes
>
> My config:
> Repository url:
> http://username:credenti...@test.fswiki.evry.com:7990/scm/tac/tac-jfr-server.git
> name: stash
> branches to build:
> stash/topic/**
> stash/dev
>
> under 2nd advanced I have:
>   Checkout/merge to local branch (optional): master (tried with and w/o
> value here)
> Config user.name Value: the userid
> Config user.email Value: the mail adr
>
> Merge options:
> merge before build is checked,
> name of repository: stash
> branch to merge to: master
>
> using jgit executable
>
> then under post build actions, I have, for the git publisher:
> Push Only If Build Succeed: checked
> merge results: checked
> branches:
> branch to push: master
> target remote name: stash
>
> from console log:
>
> Building on master in workspace /var/lib/jenkins/jobs/tac-jfr-srv/workspace
> Checkout:workspace / /var/lib/jenkins/jobs/tac-jfr-srv/workspace - 
> hudson.remoting.LocalChannel@1b8223f2
> Using strategy: Default
> Last Built Revision: Revision a8ea258e0efe1d514f31c2c4b5cc60ea6ed6b3c6 
> (stash/dev)
> Fetching changes from 1 remote Git repository
> Commencing build of Revision d5b0609fcb1061ee658d971ef5bffb06c1d40646 
> (stash/dev)
> Merging Revision d5b0609fcb1061ee658d971ef5bffb06c1d40646 (stash/dev) onto 
> master
>
> . ok building
>
> Skipping Sonar analysis
> Pushing HEAD to branch master of stash repository
> Opening connection
> Counting objects
> Finding sources
> Writing objects
> Pushing HEAD to branch master at repo stash
> Opening connection
> Counting objects
> Finding sources
> Writing objects
> No emails were triggered.
>
>
>
>
> 2013/9/2 Mark Waite 
>
> The bug you referenced is fixed in the current versions of the git client
> plugin and the git plugin.  I can confirm that Git plugin versions 1.4.0
> and 1.5.0 are able to publish changes when used with git client plugin
> 1.1.2.
>
> Unfortunately, that probably doesn't help you, since there is still some
> reason that your publish attempt is failing.  You'll need to do more
> investigating to understand why publish works for others and not in the
> case you're testing.
>
> Mark Waite
>
>   --
>  *From:* David Karlsen 
> *To:* jenkinsci-users@googlegroups.com
> *Sent:* Monday, September 2, 2013 2:53 AM
> *Subject:* Git push back changes
>
> I'm having problems getting jenkins to push back the merged branch to
> origin repo. (everything else works but the push back to the repository).
>
> Looks like this issue:
>
> http://jenkins-ci.361315.n4.nabble.com/Git-publisher-fails-to-push-td4659177.html
>
> I'm running:
> -bash-3.2$ cat git-client/META-INF/MANIFEST.MF
> Manifest-Version: 1.0
> Archiver-Version: Plexus Archiver
> Created-By: Apache Maven
> Built-By: jglick
> Build-Jdk: 1.7.0_25
> Extension-Name: git-client
> Specification-Title: Utility plugin for Git support in Jenkins
> Implementation-Title: git-client
> Implementation-Version: 1.1.2
> Group-Id: org.jenkins-ci.plugins
> Short-Name: git-client
> Long-Name: Jenkins GIT client plugin
> Url: http://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin
> Plugin-Version: 1.1.2
> Hudson-Version: 1.480
> Jenkins-Version: 1.480
> Plugin-Dependencies: ssh-credentials:1.0
> Plugin-Developers: Nicolas De Loof:ndeloof:nicolas.del...@gmail.com
>
> -bash-3.2$ cat git/META-INF/MANIFEST.MF
> Manifest-Version: 1.0
> Archiver-Version: Plexus Archiver
> Created-By: Apache Maven
> Built-By: nicolas
> Build-Jdk: 1.6.0_31
> Extension-Name: git
> Specification-Title: Integrates Jenkins with GIT SCM
> Implementation-Title: git
> Implementation-Version: 1.4.0
> Group-Id: org.jenkins-ci.plugins
> Short-Name: git
> Long-Name: Jenkins GIT plugin
> Url: http://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin
> Plugin-Version: 1.4.0
> Hudson-Version: 1.448
> Jenkins-Version: 1.448
> Plugin-Dependencies: token-macro:1.5.1;resolution:=optional,multiple-s
>  cms:0.2;resolution:=optional,git-client:1.0.6,parameterized-trigger:2
>  .4;resolution:=optional
> Plugin-Developers: Kohsuke Kawaguchi:kohsuke:,Nicolas De Loof:ndeloof:
>  nicolas.del...@gmail.com
>
>
> on core 1.509.2
>
> are there any workarounds? AFAIK I'm running the latest git plugins for
> latest LTS.
>
>