Re: Jenkins on Windows Server w/ short-workspace-path-plugin (path too long error)

[Fred Davis]

Have you tried 'long path tool'?
it's very helpful for me.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ac6fe1c3-56bf-4e5b-9017-61634c14e620%40googlegroups.com.

Re: Jenkins: remote windows build slave

[Stephen Connolly]

If you use Cygwin as the ssh Server, yes.

If you use Microsoft’s port of OpenSSH, you would need to be a level 10
mage... i’ve heard rumours that it can be made to work using power shell as
the launch shell, but not command.com

But i’d recommend setting up a vpn, it’s easy with OpenVPN or similar and
much better for security.

On Wed 8 Nov 2017 at 07:35, Jeeva Chelladhurai  wrote:

> I have ssh port open, Is it possible to setup SSH slave on Windows?
>
> - Jeeva
>
> On Wed, Nov 8, 2017 at 12:44 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> If Jenkins is served over https and you only have jnlp4 protocol enabled,
>> and you
>> lock down security on the master, it should be.
>>
>> If somebody gets their hands on an agent secret, they can take over your
>> master...
>>
>> My masters have that port on vpn network only.
>>
>> On Wed 8 Nov 2017 at 06:31, Björn Rohlén  wrote:
>>
>>> Hello.
>>>
>>> No.
>>>
>>> Regards,
>>> -Björn
>>>
>>>
>>> On Wednesday, 8 November 2017 07:08:28 UTC+1, Jeeva Chelladhurai wrote:

 Hello all!

 I want to configure windows build slave which is accessed over a public
 internet.

 Is JNLP though port 50,000 safe in a public domain?

 What is your recommendation?

 Thanks,
 Jeeva

 --
 Jeeva K S Chelladhurai

 --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/470fb08b-ee4b-4c38-9b6d-69c35d01a8db%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> Sent from my phone
>>
>> --
>> 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.
>>
> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMyEJ24wyLtQnO__vdch4-ZRNjXTs5BqLW6RK_kJj4yXKA%40mail.gmail.com
>> 
>> .
>
>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Jeeva K S Chelladhurai
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAK5CbZXW9tB%2B%2BOZAG4g3xRGvj%3D%3Dn%3DH6FbzmAKydYBQ3S2pRY%3DA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from my phone

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMxy7PXcgXOXmhGN3NTUCi48Gc-PjKPmREsqU-nUknFR7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins: remote windows build slave

[Jeeva Chelladhurai]

I have ssh port open, Is it possible to setup SSH slave on Windows?

- Jeeva

On Wed, Nov 8, 2017 at 12:44 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> If Jenkins is served over https and you only have jnlp4 protocol enabled,
> and you
> lock down security on the master, it should be.
>
> If somebody gets their hands on an agent secret, they can take over your
> master...
>
> My masters have that port on vpn network only.
>
> On Wed 8 Nov 2017 at 06:31, Björn Rohlén  wrote:
>
>> Hello.
>>
>> No.
>>
>> Regards,
>> -Björn
>>
>>
>> On Wednesday, 8 November 2017 07:08:28 UTC+1, Jeeva Chelladhurai wrote:
>>>
>>> Hello all!
>>>
>>> I want to configure windows build slave which is accessed over a public
>>> internet.
>>>
>>> Is JNLP though port 50,000 safe in a public domain?
>>>
>>> What is your recommendation?
>>>
>>> Thanks,
>>> Jeeva
>>>
>>> --
>>> Jeeva K S Chelladhurai
>>>
>>> --
>> 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.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/jenkinsci-users/470fb08b-ee4b-4c38-9b6d-
>> 69c35d01a8db%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Sent from my phone
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/CA%2BnPnMyEJ24wyLtQnO__vdch4-
> ZRNjXTs5BqLW6RK_kJj4yXKA%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jeeva K S Chelladhurai

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAK5CbZXW9tB%2B%2BOZAG4g3xRGvj%3D%3Dn%3DH6FbzmAKydYBQ3S2pRY%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins: remote windows build slave

[Stephen Connolly]

If Jenkins is served over https and you only have jnlp4 protocol enabled,
and you
lock down security on the master, it should be.

If somebody gets their hands on an agent secret, they can take over your
master...

My masters have that port on vpn network only.

On Wed 8 Nov 2017 at 06:31, Björn Rohlén  wrote:

> Hello.
>
> No.
>
> Regards,
> -Björn
>
>
> On Wednesday, 8 November 2017 07:08:28 UTC+1, Jeeva Chelladhurai wrote:
>>
>> Hello all!
>>
>> I want to configure windows build slave which is accessed over a public
>> internet.
>>
>> Is JNLP though port 50,000 safe in a public domain?
>>
>> What is your recommendation?
>>
>> Thanks,
>> Jeeva
>>
>> --
>> Jeeva K S Chelladhurai
>>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/470fb08b-ee4b-4c38-9b6d-69c35d01a8db%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from my phone

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMyEJ24wyLtQnO__vdch4-ZRNjXTs5BqLW6RK_kJj4yXKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins: remote windows build slave

[Björn Rohlén]

Hello.

No.

Regards,
-Björn

On Wednesday, 8 November 2017 07:08:28 UTC+1, Jeeva Chelladhurai wrote:
>
> Hello all!
>
> I want to configure windows build slave which is accessed over a public 
> internet. 
>
> Is JNLP though port 50,000 safe in a public domain?
>
> What is your recommendation?
>
> Thanks,
> Jeeva
>
> -- 
> Jeeva K S Chelladhurai
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/470fb08b-ee4b-4c38-9b6d-69c35d01a8db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0RC windows Batch file fail

[Daniel Daugherty]

Issue created and band-aid pull request submitted.  As stated in the pull 
request while troubleshooting the issue reverting a change in how Jenkins 
logs batch command output back to older code allows code to function as 
expected.  I have the example job in the bug running one a min for 3+ hours 
now with no failure.  Revert back to 1.9 release of durable-task-plugin  I 
am lucky to get 10 strait working.  

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

https://github.com/jenkinsci/durable-task-plugin/pull/20

On Monday, April 11, 2016 at 1:59:10 PM UTC-4, Daniel Beck wrote:
>
>
> On 11.04.2016, at 19:11, Daniel Daugherty  > wrote: 
>
> > Taking the base install of JenkinsRC I get regular hanging batch 
> commands.  When I check running tasks the batch has finished but Jenkins is 
> still looking for the results.  After some investigation I found the batch 
> files being run by jenkins.  jenkins-main.bat and jenkins-wrap.bat  The 
> wrap calls main.  Once main is complete the wrap should write a the file 
> jenkins-result.txt into the job folder.  This file is not present when the 
> task hangs.  If is create a file with a 1 or 0 in it the task complete as 
> expected.  This failure is not every time but at least 2 out of 10 time it 
> will fail.   
> > 
> > example build 
> > 
> > node{ 
> >   echo 'test 123' 
> >   bat 'ping -r 10 127.0.0.1' 
> >   echo 'test done' 
> > } 
> > 
> > It will do the first echo and the ping completes but the eche 'test 
> done' never starts.  This make Jenkins pipeline unusable for us.   
> > 
>
> Could you file a bug against the 'workflow-plugin' component in JIRA, 
> ideally with steps to reproduce? As this may be environment dependent, 
> better include as much as you can. Are you running an antivirus tool that 
> scans the directory this file should be in? 
>
> https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue 
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5d755baa-6822-424d-b5c9-9f3109324c82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0RC windows Batch file fail

[Daniel Beck]

On 11.04.2016, at 19:11, Daniel Daugherty  wrote:

> Taking the base install of JenkinsRC I get regular hanging batch commands.  
> When I check running tasks the batch has finished but Jenkins is still 
> looking for the results.  After some investigation I found the batch files 
> being run by jenkins.  jenkins-main.bat and jenkins-wrap.bat  The wrap calls 
> main.  Once main is complete the wrap should write a the file 
> jenkins-result.txt into the job folder.  This file is not present when the 
> task hangs.  If is create a file with a 1 or 0 in it the task complete as 
> expected.  This failure is not every time but at least 2 out of 10 time it 
> will fail.  
> 
> example build
> 
> node{
>   echo 'test 123'
>   bat 'ping -r 10 127.0.0.1'
>   echo 'test done'
> }
> 
> It will do the first echo and the ping completes but the eche 'test done' 
> never starts.  This make Jenkins pipeline unusable for us.  
> 

Could you file a bug against the 'workflow-plugin' component in JIRA, ideally 
with steps to reproduce? As this may be environment dependent, better include 
as much as you can. Are you running an antivirus tool that scans the directory 
this file should be in?

https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/99F70B5A-6698-4A90-AA7E-2795CF312C2D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins on Windows Server w/ short-workspace-path-plugin (path too long error)

[geoffroy . jabouley]

Hi

For what i've read about the plugin your using "The plugin has currently no 
effect on master node and never places short workspaces out of slave's 
workspace root."

Does Jenkins supports windows ntfs 32k file path long names, like 
\\?\c:\dir\file" ? 
(https://serverfault.com/questions/163419/window-256-characters-path-name-limitation)
 
I've never tried it...
In the same serverfault thread, there are others possible solutions, like 
creating symlinks of your long path folders using mklink (which does not 
require root access like subst).

You can also start your jenkins with "JENKINS_HOME=c:\j" for example ;) but 
this is only a short term solution as your paths keep getting longer and 
longer.

Good luck

Le vendredi 29 janvier 2016 17:18:14 UTC+1, rginga a écrit :
>
> There are 2 ways to make the resultant workspace path shorter. The path is 
> made up of the workspace root and your source code structure.
>
>  
>
> 1.   Change the “Workspace Root Directory” under System Configuration. My 
> windows master workspace resolves to: C:\Program Files 
> (x86)\Jenkins\jobs\JOBNAME\workspace. But I do very, very little building on 
> the master.
>
>  
>
> 2.   In some SCM’s you can change the mapping to eliminate common root 
> folders. We use Perforce and I could map:
>
> //depot/aaa/bbb/ccc/ddd/eee/ProjA/… //workspace/ProjA/…
>
>  
>
>  
>
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Patrick Hummer
> *Sent:* Friday, January 29, 2016 11:06 AM
> *To:* Jenkins Users
> *Subject:* Jenkins on Windows Server w/ short-workspace-path-plugin (path 
> too long error)
>
>  
>
> Hi,
>
>  
>
> We currently are running Jenkins on a Windows Server box and a couple of 
> our projects are getting the "Path too long" error.  I realize this is a 
> limitation of Windows but from looking around there are a couple options to 
> get around this in Jenkins.
>
>  
>
> The one we are trying is the short-workspace-path-plugin 
> . 
>  By default the system property for BUILD_PATH_LENGTH in this plugin is set 
> to 512.  I was able to modify this property via the Jenkins.xml file and 
> have verified that the value is being set.  We set the value below the 
> Windows maximum path length however we are still receiving an error.
>
>  
>
> The error in our build we are seeing:
>
>  
>
> Error: The specified path, file name, or both are too long. The fully 
> qualified file name must be less than 260 characters, and the directory 
> name must be less than 248 characters.
>
>  
>
>  
>
> The system property value we are setting it is:
>
>  
>
> -Dorg.jenkinsci.plugins.shortwspath.BUILD_PATH_LENGTH=248
>
>  
>
> And as seen in the "System Information" section:
>
>
>
> 
>  
> 
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
> Any direction would be greatly appreciated.
>
>  
>
> Thank you,
>
> Patrick
>
> -- 
> 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 .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/6cbee678-9f67-49d1-9523-d270e0bf0555%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/160488be-f541-40bb-ac9b-5b5a8258b1ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Jenkins on Windows Server w/ short-workspace-path-plugin (path too long error)

[Ginga, Dick]

There are 2 ways to make the resultant workspace path shorter. The path is made 
up of the workspace root and your source code structure.


1.   Change the “Workspace Root Directory” under System Configuration. My 
windows master workspace resolves to: C:\Program Files 
(x86)\Jenkins\jobs\JOBNAME\workspace. But I do very, very little building on 
the master.



2.   In some SCM’s you can change the mapping to eliminate common root 
folders. We use Perforce and I could map:

//depot/aaa/bbb/ccc/ddd/eee/ProjA/… //workspace/ProjA/…



From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Patrick Hummer
Sent: Friday, January 29, 2016 11:06 AM
To: Jenkins Users
Subject: Jenkins on Windows Server w/ short-workspace-path-plugin (path too 
long error)

Hi,

We currently are running Jenkins on a Windows Server box and a couple of our 
projects are getting the "Path too long" error.  I realize this is a limitation 
of Windows but from looking around there are a couple options to get around 
this in Jenkins.

The one we are trying is the 
short-workspace-path-plugin.
  By default the system property for BUILD_PATH_LENGTH in this plugin is set to 
512.  I was able to modify this property via the Jenkins.xml file and have 
verified that the value is being set.  We set the value below the Windows 
maximum path length however we are still receiving an error.

The error in our build we are seeing:

Error: The specified path, file name, or both are too long. The fully qualified 
file name must be less than 260 characters, and the directory name must be less 
than 248 characters.


The system property value we are setting it is:

-Dorg.jenkinsci.plugins.shortwspath.BUILD_PATH_LENGTH=248

And as seen in the "System Information" section:

[https://lh3.googleusercontent.com/-lbG8WTJcUEo/VquM2HCMmFI/MfY/rze4X80ptw4/s1600/Screenshot_012916_110220_AM.jpg]











Any direction would be greatly appreciated.

Thank you,
Patrick
--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6cbee678-9f67-49d1-9523-d270e0bf0555%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D86BDB90%40AMERMBX02.PERKINELMER.NET.
For more options, visit https://groups.google.com/d/optout.

RE: Jenkins on Windows: BSoD and Fortify

[j.g.wessels]

Hello Chris,

Thanks for your reply. We have already seen the message in the Manage Jenkins 
main screen.

Also there seems to be a solution for the Jenkins Fortify plugin. HP has added 
the plugin in the latest version of Fortify: HP Fortify 4.21.

Regards,

Gerrit


-Oorspronkelijk bericht-
Van: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] 
Namens Christopher Orr
Verzonden: donderdag 30 oktober 2014 16:30
Aan: jenkinsci-users@googlegroups.com
Onderwerp: Re: Jenkins on Windows: BSoD and Fortify

On 28/10/14 16:56, j.g.wess...@rn.rabobank.nl wrote:
  From the Jenkins-ci.org website we understand that the BSoD problem 
 has been worked around in Jenkins version 1.580.x or higher. This 
 means that upgrading to one of the latest (non LTS) versions would be 
 a (temporary) solution for our problem. But, to solve BSoD’s is not the only 
 challenge.

FWIW, Jenkins LTS 1.580.1 was released yesterday (despite the website still 
saying 1.565.3).

Regards,
Chris

--
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/d/optout.
==
Rabobank disclaimer: http://www.rabobank.nl/disclaimer

-- 
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/d/optout.

Re: Jenkins on Windows: BSoD and Fortify

[Christopher Orr]

On 28/10/14 16:56, j.g.wess...@rn.rabobank.nl wrote:

 From the Jenkins-ci.org website we understand that the BSoD problem has
been worked around in Jenkins version 1.580.x or higher. This means that
upgrading to one of the latest (non LTS) versions would be a (temporary)
solution for our problem. But, to solve BSoD’s is not the only challenge.


FWIW, Jenkins LTS 1.580.1 was released yesterday (despite the website 
still saying 1.565.3).


Regards,
Chris

--
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/d/optout.

Re: Jenkins on Windows Server 2008 unable to connect to updates site

[Andrew Sumner]

Never mind, discovered the newer version of Jenkins and Subversion plugin 
have a property for exactly this scenario.  Thanks everyone who contributes 
to Jenkins - love the tool :-)

-- 
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 in windows

[Alex Earl]

Lance,

We run Jenkins on windows with no issues. Can you describe the issues you
are having in more detail?

Thanks,

Alex

Sent from my Windows Phone
--
From: lance.e.mead@mail.mil
Sent: 5/22/2013 9:57
To: jenkinsci-users@googlegroups.com
Subject: Jenkins in windows

I am a new user trying to get Jenkins working in a Windows 7 OS.  There
seems to be no support nor any help available for such a task.  Does anyone
know a) where to get answers to questions or b) a CI like Jenkins that has
a API that runs in Windows?

Lance

-- 
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: Jenkins in windows

[k . thieling]

What are you having trouble with? 



The windows installer can be downloaded here: http://jenkins-ci.org/ 



Click on Windows under the natvie package section.  It will run as a service. 





- Original Message -


From: lance e mead ctr lance.e.mead@mail.mil 
To: jenkinsci-users@googlegroups.com 
Sent: Wednesday, May 22, 2013 11:57:52 AM 
Subject: Jenkins in windows 

I am a new user trying to get Jenkins working in a Windows 7 OS.  There seems 
to be no support nor any help available for such a task.  Does anyone know a) 
where to get answers to questions or b) a CI like Jenkins that has a API that 
runs in Windows? 

Lance 


-- 
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: Jenkins in windows

[lance . e . mead . ctr]

We need to run the Python API, JenkinsAPI, but I can't find anything that 
will install the API.  The API is a .tar.gz file and after unzipping the 
setup file does not run with pip, a error.  I posted a message about 
getting the API to work but there was no response.

Thanks, Lance

On Wednesday, May 22, 2013 10:01:32 AM UTC-7, slide wrote:

 Lance,

 We run Jenkins on windows with no issues. Can you describe the issues you 
 are having in more detail?

 Thanks,

 Alex

 Sent from my Windows Phone
 --
 From: lance.e@mail.mil javascript:
 Sent: 5/22/2013 9:57
 To: jenkins...@googlegroups.com javascript:
 Subject: Jenkins in windows

 I am a new user trying to get Jenkins working in a Windows 7 OS.  There 
 seems to be no support nor any help available for such a task.  Does anyone 
 know a) where to get answers to questions or b) a CI like Jenkins that has 
 a API that runs in Windows?

 Lance

 -- 
 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 javascript:.
 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: Jenkins in windows

[lance . e . mead . ctr]

The Python API .


On Wednesday, May 22, 2013 9:57:52 AM UTC-7, lance.e@mail.mil wrote:

 I am a new user trying to get Jenkins working in a Windows 7 OS.  There 
 seems to be no support nor any help available for such a task.  Does anyone 
 know a) where to get answers to questions or b) a CI like Jenkins that has 
 a API that runs in Windows?

 Lance


-- 
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 + git + windows

[rakhee Kulkarni]

Hey Mark,

I am trying to configure my windows slave for Mingw. I have the slave up 
using jnlp. Can you please advise?

Thanks,
Rakhee

On Friday, April 8, 2011 5:43:50 AM UTC-7, Mark Waite wrote:

 We use msys git for our configuration.  We run many builds on many 
 machines with git as SCM.

 Mark Waite


 --
 *From:* Jon Schewe jpsc...@mtu.net javascript:
 *To:* Jenkins Users jenkins...@googlegroups.com javascript:
 *Sent:* Fri, April 8, 2011 6:40:26 AM
 *Subject:* Jenkins + git + windows

 I have 2 jobs that need to run on Windows. I currently have my Jenkins
 slave setup using ssh access via cygwin. However there appears to be a
 bug in ssh or git under cygwin such that clones keep failing with
 index-pack filed. There are reports that mingw works and msysgit work.
 What are others in the community using for such a setup?

 One of the jobs needs to run under cygwin, the other is a Qt build that
 I use mingw to build and then execute native windows executables.

 Jon



-- 
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, Git, Windows and Line Feeds

[Mark Waite]

Could you split your build into two parts, running the part which involves 
Linux components on a Linux machine, and the part which requires MSBuild (and 
Windows) on your Windows machine, with one of those jobs publishing its build 
results as an artifact which the next build takes and includes in the build?

The artifact should be transmitted in binary and would not require that you 
perform any line transformations.

Mark Waite






 From: David Brossard dbross...@gmail.com
To: jenkinsci-users@googlegroups.com 
Sent: Wednesday, March 27, 2013 12:24 PM
Subject: Jenkins, Git, Windows and Line Feeds
 

All,
This has been frustrating me for a while. I need to both build Windows code 
and publish Linux code during a single build. The only way I've been able to 
get this to build is to run completely on a Windows slave. If I try to run on 
a linux slave as well it always complains that MSBuild cannot be found. So I 
force it onto my windows slave and use GIT to check out the code, build with 
MSBuild, then push out to both Windows and Linux without error.
Now my issue is that the code pushed to my Linux box has been converted to 
Windows' CR/LF method so none of my executables work on Linux. Short of doing 
a dos2unix on every single file I push out, is there a way to fix this? I 
tried adding *   text=binary to my gitattributes but to no avail. I think it 
may be ignoring that attributes file because jgit is used instead of git?
Any and all help greatly appreciated.
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.
 
 




-- 
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, Git, Windows and Line Feeds

[William Soula]

I can't tell if you are talking about files created during the build or files 
checked out for the build but if it is files checked out for the build perhaps 
your git line endings are set wrong.  If the git repo is for windows and git 
then you need it set to use linux line endings.  Check out this page:
https://help.github.com/articles/dealing-with-line-endings

Will

From: jenkinsci-users@googlegroups.com [jenkinsci-users@googlegroups.com] on 
behalf of David Brossard [dbross...@gmail.com]
Sent: Wednesday, March 27, 2013 1:24 PM
To: jenkinsci-users@googlegroups.com
Subject: Jenkins, Git, Windows and Line Feeds

All,
This has been frustrating me for a while. I need to both build Windows code and 
publish Linux code during a single build. The only way I've been able to get 
this to build is to run completely on a Windows slave. If I try to run on a 
linux slave as well it always complains that MSBuild cannot be found. So I 
force it onto my windows slave and use GIT to check out the code, build with 
MSBuild, then push out to both Windows and Linux without error.
Now my issue is that the code pushed to my Linux box has been converted to 
Windows' CR/LF method so none of my executables work on Linux. Short of doing a 
dos2unix on every single file I push out, is there a way to fix this? I tried 
adding *   text=binary to my gitattributes but to no avail. I think it may be 
ignoring that attributes file because jgit is used instead of git?
Any and all help greatly appreciated.
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.


-- 
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, Git, Windows and Line Feeds

[David Brossard]

I found an answer to my own question.


   - Set the Jenkins Slave service to run as a specific user on the local 
   system.
   - login as that user and run in a command prompt git config --global  
   core.autocrlf input
   - Clear out the Jenkins workspace on that slave so it will do a full git 
   clone again

core.autocrlf input means don't monkey with the EOL stuff. If it was 
checked in as Linux EOL or Windows EOL it will keep it that way.

Thanks

On Wednesday, March 27, 2013 11:24:25 AM UTC-7, David Brossard wrote:

 All,
 This has been frustrating me for a while. I need to both build Windows 
 code and publish Linux code during a single build. The only way I've been 
 able to get this to build is to run completely on a Windows slave. If I try 
 to run on a linux slave as well it always complains that MSBuild cannot be 
 found. So I force it onto my windows slave and use GIT to check out the 
 code, build with MSBuild, then push out to both Windows and Linux without 
 error.
 Now my issue is that the code pushed to my Linux box has been converted to 
 Windows' CR/LF method so none of my executables work on Linux. Short of 
 doing a dos2unix on every single file I push out, is there a way to fix 
 this? I tried adding *   text=binary to my gitattributes but to no avail. 
 I think it may be ignoring that attributes file because jgit is used 
 instead of git?
 Any and all help greatly appreciated.
 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: Jenkins, Git, Windows and Line Feeds

[David Brossard]

William, just saw your post. That is exactly what I had to figure out.

Mark, I would definitely like to have different steps in my build run on 
different machines, however I still haven't solved the problem that if I 
have an MSBuild step anywhere in my config, it tries to find that on my 
linux slaves as well and fails. If you have any links to instructions on 
making that work I would love to see them. That was my original plan before 
forcing the entire job onto the Windows slave.

Thanks

On Wednesday, March 27, 2013 11:54:49 AM UTC-7, David Brossard wrote:

 I found an answer to my own question.


- Set the Jenkins Slave service to run as a specific user on the local 
system.
- login as that user and run in a command prompt git config --global  
core.autocrlf input
- Clear out the Jenkins workspace on that slave so it will do a full 
git clone again

 core.autocrlf input means don't monkey with the EOL stuff. If it was 
 checked in as Linux EOL or Windows EOL it will keep it that way.

 Thanks

 On Wednesday, March 27, 2013 11:24:25 AM UTC-7, David Brossard wrote:

 All,
 This has been frustrating me for a while. I need to both build Windows 
 code and publish Linux code during a single build. The only way I've been 
 able to get this to build is to run completely on a Windows slave. If I try 
 to run on a linux slave as well it always complains that MSBuild cannot be 
 found. So I force it onto my windows slave and use GIT to check out the 
 code, build with MSBuild, then push out to both Windows and Linux without 
 error.
 Now my issue is that the code pushed to my Linux box has been converted 
 to Windows' CR/LF method so none of my executables work on Linux. Short of 
 doing a dos2unix on every single file I push out, is there a way to fix 
 this? I tried adding *   text=binary to my gitattributes but to no avail. 
 I think it may be ignoring that attributes file because jgit is used 
 instead of git?
 Any and all help greatly appreciated.
 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: Jenkins, Git, Windows and Line Feeds

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

You need to assign labels ('windows', 'linux', etc.) to your slaves and then 
indicate in your jobs what labels are required for that job to run.


- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Mar 27 2013 15:07:36




William, just saw your post. That is exactly what I had to figure out.


Mark, I would definitely like to have different steps in my build run on 
different machines, however I still haven't solved the problem that if I 
have an MSBuild step anywhere in my config, it tries to find that on my 
linux slaves as well and fails. If you have any links to instructions on 
making that work I would love to see them. That was my original plan before 
forcing the entire job onto the Windows slave.


Thanks


On Wednesday, March 27, 2013 11:54:49 AM UTC-7, David Brossard wrote:

 I found an answer to my own question.


- Set the Jenkins Slave service to run as a specific user on the local 
system.
- login as that user and run in a command prompt git config --global  
core.autocrlf input
- Clear out the Jenkins workspace on that slave so it will do a full 
git clone again

 core.autocrlf input means don't monkey with the EOL stuff. If it was 
 checked in as Linux EOL or Windows EOL it will keep it that way.

 Thanks

 On Wednesday, March 27, 2013 11:24:25 AM UTC-7, David Brossard wrote:

 All,
 This has been frustrating me for a while. I need to both build Windows 
 code and publish Linux code during a single build. The only way I've been 
 able to get this to build is to run completely on a Windows slave. If I try 
 to run on a linux slave as well it always complains that MSBuild cannot be 
 found. So I force it onto my windows slave and use GIT to check out the 
 code, build with MSBuild, then push out to both Windows and Linux without 
 error.
 Now my issue is that the code pushed to my Linux box has been converted 
 to Windows' CR/LF method so none of my executables work on Linux. Short of 
 doing a dos2unix on every single file I push out, is there a way to fix 
 this? I tried adding *   text=binary to my gitattributes but to no avail. 
 I think it may be ignoring that attributes file because jgit is used 
 instead of git?
 Any and all help greatly appreciated.
 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.

-- 
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, Git, Windows and Line Feeds

[Mark Waite]

You would need to configure two different build jobs, with a different set of 
build steps in each job.  

The Linux build job would be configured to never call MSBuild.  The Windows 
build job would be configured to never call the Linux specific portions of the 
build.  

If the Windows job is the first job, then the Linux build job would be 
configured to copy the artifacts from the Windows build job and include those 
artifacts in the final build result.  

If the Linux job is the first job, then the Windows job would be configured to 
copy the artifacts from the Linux job and include those artifacts in the final 
build result.

Mark Waite




 From: David Brossard dbross...@gmail.com
To: jenkinsci-users@googlegroups.com 
Sent: Wednesday, March 27, 2013 1:06 PM
Subject: Re: Jenkins, Git, Windows and Line Feeds
 

William, just saw your post. That is exactly what I had to figure out.

Mark, I would definitely like to have different steps in my build run on 
different machines, however I still haven't solved the problem that if I have 
an MSBuild step anywhere in my config, it tries to find that on my linux 
slaves as well and fails. If you have any links to instructions on making that 
work I would love to see them. That was my original plan before forcing the 
entire job onto the Windows slave.

Thanks

On Wednesday, March 27, 2013 11:54:49 AM UTC-7, David Brossard wrote:
I found an answer to my own question.


  * Set the Jenkins Slave service to run as a specific user on the local 
 system.
  * login as that user and run in a command prompt git config --global  
 core.autocrlf input
  * Clear out the Jenkins workspace on that slave so it will do a full 
 git clone againcore.autocrlf input means don't monkey with the EOL stuff. 
 If it was checked in as Linux EOL or Windows EOL it will keep it that way.

Thanks

On Wednesday, March 27, 2013 11:24:25 AM UTC-7, David Brossard wrote:
All,
This has been frustrating me for a while. I need to both build Windows code 
and publish Linux code during a single build. The only way I've been able to 
get this to build is to run completely on a Windows slave. If I try to run 
on a linux slave as well it always complains that MSBuild cannot be found. 
So I force it onto my windows slave and use GIT to check out the code, build 
with MSBuild, then push out to both Windows and Linux without error.
Now my issue is that the code pushed to my Linux box has been converted to 
Windows' CR/LF method so none of my executables work on Linux. Short of 
doing a dos2unix on every single file I push out, is there a way to fix 
this? I tried adding *   text=binary to my gitattributes but to no avail. 
I think it may be ignoring that attributes file because jgit is used instead 
of git?
Any and all help greatly appreciated.
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.
 
 




-- 
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, Git, Windows and Line Feeds

[David Brossard]

We are getting off topic so I will start another one if I need to continue, 
but when I tried something similar to what you say previously, the Linux 
build had no clue about the windows build artifacts and vice-versa since 
they were separate jobs in separate workspaces and on different servers.

On Wednesday, March 27, 2013 3:35:34 PM UTC-7, Mark Waite wrote:

 You would need to configure two different build jobs, with a different set 
 of build steps in each job.  

 The Linux build job would be configured to never call MSBuild.  The 
 Windows build job would be configured to never call the Linux specific 
 portions of the build.  

 If the Windows job is the first job, then the Linux build job would be 
 configured to copy the artifacts from the Windows build job and include 
 those artifacts in the final build result.  

 If the Linux job is the first job, then the Windows job would be 
 configured to copy the artifacts from the Linux job and include those 
 artifacts in the final build result.

 Mark Waite

   --
 *From:* David Brossard dbro...@gmail.com javascript:
 *To:* jenkins...@googlegroups.com javascript: 
 *Sent:* Wednesday, March 27, 2013 1:06 PM
 *Subject:* Re: Jenkins, Git, Windows and Line Feeds
  
 William, just saw your post. That is exactly what I had to figure out.

 Mark, I would definitely like to have different steps in my build run on 
 different machines, however I still haven't solved the problem that if I 
 have an MSBuild step anywhere in my config, it tries to find that on my 
 linux slaves as well and fails. If you have any links to instructions on 
 making that work I would love to see them. That was my original plan before 
 forcing the entire job onto the Windows slave.

 Thanks

 On Wednesday, March 27, 2013 11:54:49 AM UTC-7, David Brossard wrote:

 I found an answer to my own question.


- Set the Jenkins Slave service to run as a specific user on the local 
system.
- login as that user and run in a command prompt git config --global  
core.autocrlf input
- Clear out the Jenkins workspace on that slave so it will do a full 
git clone again

 core.autocrlf input means don't monkey with the EOL stuff. If it was 
 checked in as Linux EOL or Windows EOL it will keep it that way.

 Thanks

 On Wednesday, March 27, 2013 11:24:25 AM UTC-7, David Brossard wrote:

 All,
 This has been frustrating me for a while. I need to both build Windows 
 code and publish Linux code during a single build. The only way I've been 
 able to get this to build is to run completely on a Windows slave. If I try 
 to run on a linux slave as well it always complains that MSBuild cannot be 
 found. So I force it onto my windows slave and use GIT to check out the 
 code, build with MSBuild, then push out to both Windows and Linux without 
 error.
 Now my issue is that the code pushed to my Linux box has been converted to 
 Windows' CR/LF method so none of my executables work on Linux. Short of 
 doing a dos2unix on every single file I push out, is there a way to fix 
 this? I tried adding *   text=binary to my gitattributes but to no avail. 
 I think it may be ignoring that attributes file because jgit is used 
 instead of git?
 Any and all help greatly appreciated.
 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-use...@googlegroups.com javascript:.
 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: Jenkins on Windows: Java + JRE (version) confusion

[Martin Ba]

On 15.03.2013 11:45, Martin Ba wrote:

I'll start with my questions:
-
* Should I run Jenkins on Windows with the included JRE (currentl
1.6_26) or should I run it with a more recent Java version?
* Should I make sure slaves run within the same java version (or at
least bit-ness)? (Slaves don't have an integrated JRE as far as I can
see.)
* When (and based on what) is the JRE contained in the Windows installer
updated? (after all, the latest JRE 6 release is Update 43 from 2013-03-04)

Thanks!
...


Added question on SF: 
http://serverfault.com/questions/488745/which-java-version-should-i-run-jenkins-with


cheers,
Martin

--
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 on Windows box

[cjo]

You might also want to check what build steps and post build steps you have 
enabled in the job, as some of them such as the warnings plugin require the 
previous build to have completed. 

As they declare that the step needs the previous build to complete, to 
perform the correct actions. 
they use the BuildStepMonitor as used in [1]. 
e.g. the warnings plugin needs the previous build to be complete so that it 
can calculate new / fixed warnings counts.

[1] 
http://javadoc.jenkins-ci.org/hudson/tasks/BuildStep.html#getRequiredMonitorService()

Chris.

On Wednesday, November 28, 2012 1:16:07 AM UTC, RobertK - Seattle wrote:

 Or… are you sure you didn’t configure it to only have on executor at a 
 time?  I manually configured my install to do that, so somewhat-related 
 build processes on my machine didn’t trip over each other.  

  

 *From:* jenkins...@googlegroups.com javascript: [mailto:
 jenkins...@googlegroups.com javascript:] *On Behalf Of *Mark Waite
 *Sent:* Tuesday, November 27, 2012 5:10 PM
 *To:* jenkins...@googlegroups.com javascript:
 *Subject:* Re: Jenkins on Windows box

  

 Are you sure it is not something in your build script (not in Jenkins) 
 which prevents multiple builds from running concurrently?  Jenkins is able 
 to run multiple builds concurrently in the tests I've run, without blocking 
 one job behind another.

 Mark Waite

  

  
 --

 *From:* Bill Wonch bill@gmail.com javascript:
 *To:* jenkins...@googlegroups.com javascript: 
 *Sent:* Tuesday, November 27, 2012 5:17 PM
 *Subject:* Jenkins on Windows box

  

 Hi everyone -

  

 Quick question, but it's causing some frustration for our developers. 
  Hope you can help!

  

 We have a deploy job that is configured to run concurrent builds, but when 
 I execute more than once, the second job will wait for the first to 
 complete before running the first step (it does send out build start 
 notifications before pausing).  Anyone seen anything like this before?  Any 
 idea what I can do to fix it?

  

 If it's helpful, I'm running jenkins.war from Tomcat 7 on a win XP machine.

  

 Thanks!

  

 Bill

  

Re: Jenkins on Windows box

[Bill Wonch]

Hi everyone -

Thanks for your quick responses!

This isn't for a build (at least in the sense that it generates an 
artifact) it's part of an automated deployment process that we have set up. 
 The first step calls a small batch script which verifies that the user is 
in a specific group if the ENVIRONMENT parameter is not dev (using the 
Conditional Build Step plugin).  It seems to get through the condition 
checking fine, then stalls when it hits the batch file.  Here is what the 
configuration looks like for the first step:

  concurrentBuildtrue/concurrentBuild
  builders

org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder
  condition class=org.jenkins_ci.plugins.run_condition.logic.Not
condition 
class=org.jenkins_ci.plugins.run_condition.core.StringsMatchCondition
  arg1${ENV,var=quot;ENVIRONMENTquot;}/arg1
  arg2dev/arg2
  ignoreCasefalse/ignoreCase
/condition
  /condition
  buildStep class=hudson.tasks.BatchFile
commandauthorization\environment_authorization.bat/command
  /buildStep
  runner 
class=org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail/

/org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder

As you can see, I've got it configured to run multiple builds concurrently, 
which seems to work - it definitely takes up two executors when I try to 
run two jobs at the same time, and makes it as far as checking the 
conditions specified in the step above.  It only stalls when it hits 
authorization\environment_authorization.bat. 

The contents of that batch script are:

@echo off
set i=0
set group=DTCA_APD_JENKINS_ADMI
set user=%BUILD_USER_ID%
echo Checking if %user% is member of %group%...
for /f %%f in ('net user %user% /domain | findstr /i %group%') do set /a 
i=%i%+1
if %i% gtr 0 (goto :member)
:nomember
echo FAILURE: Authentication check failed.  You are not authorized to 
deploy in this environment.
exit 1
:member
echo SUCCESS: Authentication check passed
exit 0
   
So ti really just requests a user's group info from the domain, and fails 
the build if the user is not in the correct group.  At first I thought it 
might be a file locking issue of some sort, but these are in two separate 
workspaces, each with their own copy of the script...

As far as post-build steps go, for this job I only have a small postbuild 
groovy step that publishes some audit information on the build page.  We 
use a similar pattern on a couple of other jobs, and all have this same 
problem.

If it woulld help I can post the config.xml file for the job?

Thanks again!

Bill

On Wednesday, November 28, 2012 4:49:40 AM UTC-7, cjo wrote:

 You might also want to check what build steps and post build steps you 
 have enabled in the job, as some of them such as the warnings plugin 
 require the previous build to have completed. 

 As they declare that the step needs the previous build to complete, to 
 perform the correct actions. 
 they use the BuildStepMonitor as used in [1]. 
 e.g. the warnings plugin needs the previous build to be complete so that 
 it can calculate new / fixed warnings counts.

 [1] 
 http://javadoc.jenkins-ci.org/hudson/tasks/BuildStep.html#getRequiredMonitorService()

 Chris.

 On Wednesday, November 28, 2012 1:16:07 AM UTC, RobertK - Seattle wrote:

 Or… are you sure you didn’t configure it to only have on executor at a 
 time?  I manually configured my install to do that, so somewhat-related 
 build processes on my machine didn’t trip over each other.  

  

 *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] 
 *On Behalf Of *Mark Waite
 *Sent:* Tuesday, November 27, 2012 5:10 PM
 *To:* jenkins...@googlegroups.com
 *Subject:* Re: Jenkins on Windows box

  

 Are you sure it is not something in your build script (not in Jenkins) 
 which prevents multiple builds from running concurrently?  Jenkins is able 
 to run multiple builds concurrently in the tests I've run, without blocking 
 one job behind another.

 Mark Waite

  

  
 --

 *From:* Bill Wonch bill@gmail.com
 *To:* jenkins...@googlegroups.com 
 *Sent:* Tuesday, November 27, 2012 5:17 PM
 *Subject:* Jenkins on Windows box

  

 Hi everyone -

  

 Quick question, but it's causing some frustration for our developers. 
  Hope you can help!

  

 We have a deploy job that is configured to run concurrent builds, but 
 when I execute more than once, the second job will wait for the first to 
 complete before running the first step (it does send out build start 
 notifications before pausing).  Anyone seen anything like this before?  Any 
 idea what I can do to fix it?

  

 If it's helpful, I'm running jenkins.war from Tomcat 7 on a win XP 
 machine.

  

 Thanks!

  

 Bill

  

Re: Jenkins on Windows box

[Bill Wonch]

I think I found the problem: 
 https://issues.jenkins-ci.org/browse/JENKINS-13871

It looks like a fix may have been committed.  I'm going to move my variable 
checking into the batch file until I see a fix on that issue.  Thanks 
everyone!

On Wednesday, November 28, 2012 8:28:42 AM UTC-7, Bill Wonch wrote:

 Hi everyone -

 Thanks for your quick responses!

 This isn't for a build (at least in the sense that it generates an 
 artifact) it's part of an automated deployment process that we have set up. 
  The first step calls a small batch script which verifies that the user is 
 in a specific group if the ENVIRONMENT parameter is not dev (using the 
 Conditional Build Step plugin).  It seems to get through the condition 
 checking fine, then stalls when it hits the batch file.  Here is what the 
 configuration looks like for the first step:

   concurrentBuildtrue/concurrentBuild
   builders
 
 org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder
   condition class=org.jenkins_ci.plugins.run_condition.logic.Not
 condition 
 class=org.jenkins_ci.plugins.run_condition.core.StringsMatchCondition
   arg1${ENV,var=quot;ENVIRONMENTquot;}/arg1
   arg2dev/arg2
   ignoreCasefalse/ignoreCase
 /condition
   /condition
   buildStep class=hudson.tasks.BatchFile
 commandauthorization\environment_authorization.bat/command
   /buildStep
   runner 
 class=org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail/
 
 /org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder

 As you can see, I've got it configured to run multiple builds 
 concurrently, which seems to work - it definitely takes up two executors 
 when I try to run two jobs at the same time, and makes it as far as 
 checking the conditions specified in the step above.  It only stalls when 
 it hits authorization\environment_authorization.bat. 

 The contents of that batch script are:

 @echo off
 set i=0
 set group=DTCA_APD_JENKINS_ADMI
 set user=%BUILD_USER_ID%
 echo Checking if %user% is member of %group%...
 for /f %%f in ('net user %user% /domain | findstr /i %group%') do set /a 
 i=%i%+1
 if %i% gtr 0 (goto :member)
 :nomember
 echo FAILURE: Authentication check failed.  You are not authorized to 
 deploy in this environment.
 exit 1
 :member
 echo SUCCESS: Authentication check passed
 exit 0

 So ti really just requests a user's group info from the domain, and fails 
 the build if the user is not in the correct group.  At first I thought it 
 might be a file locking issue of some sort, but these are in two separate 
 workspaces, each with their own copy of the script...

 As far as post-build steps go, for this job I only have a small postbuild 
 groovy step that publishes some audit information on the build page.  We 
 use a similar pattern on a couple of other jobs, and all have this same 
 problem.

 If it woulld help I can post the config.xml file for the job?

 Thanks again!

 Bill

 On Wednesday, November 28, 2012 4:49:40 AM UTC-7, cjo wrote:

 You might also want to check what build steps and post build steps you 
 have enabled in the job, as some of them such as the warnings plugin 
 require the previous build to have completed. 

 As they declare that the step needs the previous build to complete, to 
 perform the correct actions. 
 they use the BuildStepMonitor as used in [1]. 
 e.g. the warnings plugin needs the previous build to be complete so that 
 it can calculate new / fixed warnings counts.

 [1] 
 http://javadoc.jenkins-ci.org/hudson/tasks/BuildStep.html#getRequiredMonitorService()

 Chris.

 On Wednesday, November 28, 2012 1:16:07 AM UTC, RobertK - Seattle wrote:

 Or… are you sure you didn’t configure it to only have on executor at a 
 time?  I manually configured my install to do that, so somewhat-related 
 build processes on my machine didn’t trip over each other.  

  

 *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] 
 *On Behalf Of *Mark Waite
 *Sent:* Tuesday, November 27, 2012 5:10 PM
 *To:* jenkins...@googlegroups.com
 *Subject:* Re: Jenkins on Windows box

  

 Are you sure it is not something in your build script (not in Jenkins) 
 which prevents multiple builds from running concurrently?  Jenkins is able 
 to run multiple builds concurrently in the tests I've run, without blocking 
 one job behind another.

 Mark Waite

  

  
 --

 *From:* Bill Wonch bill@gmail.com
 *To:* jenkins...@googlegroups.com 
 *Sent:* Tuesday, November 27, 2012 5:17 PM
 *Subject:* Jenkins on Windows box

  

 Hi everyone -

  

 Quick question, but it's causing some frustration for our developers. 
  Hope you can help!

  

 We have a deploy job that is configured to run concurrent builds, but 
 when I execute more than once, the second job will wait for the first to 
 complete before running the first step (it does send out build start 
 notifications before

Re: Jenkins on Windows box

[Mark Waite]

Are you sure it is not something in your build script (not in Jenkins) which 
prevents multiple builds from running concurrently?  Jenkins is able to run 
multiple builds concurrently in the tests I've run, without blocking one job 
behind another.

Mark Waite






 From: Bill Wonch bill.wo...@gmail.com
To: jenkinsci-users@googlegroups.com 
Sent: Tuesday, November 27, 2012 5:17 PM
Subject: Jenkins on Windows box
 

Hi everyone -


Quick question, but it's causing some frustration for our developers.  Hope 
you can help!


We have a deploy job that is configured to run concurrent builds, but when I 
execute more than once, the second job will wait for the first to complete 
before running the first step (it does send out build start notifications 
before pausing).  Anyone seen anything like this before?  Any idea what I can 
do to fix it?


If it's helpful, I'm running jenkins.war from Tomcat 7 on a win XP machine.


Thanks!


Bill

RE: Jenkins on Windows box

[Robert]

Or. are you sure you didn't configure it to only have on executor at a
time?  I manually configured my install to do that, so somewhat-related
build processes on my machine didn't trip over each other.  

 

From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: Tuesday, November 27, 2012 5:10 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Jenkins on Windows box

 

Are you sure it is not something in your build script (not in Jenkins)
which prevents multiple builds from running concurrently?  Jenkins is able
to run multiple builds concurrently in the tests I've run, without
blocking one job behind another.

Mark Waite

 

 


  _  


From: Bill Wonch bill.wo...@gmail.com
To: jenkinsci-users@googlegroups.com 
Sent: Tuesday, November 27, 2012 5:17 PM
Subject: Jenkins on Windows box

 

Hi everyone -

 

Quick question, but it's causing some frustration for our developers.
Hope you can help!

 

We have a deploy job that is configured to run concurrent builds, but when
I execute more than once, the second job will wait for the first to
complete before running the first step (it does send out build start
notifications before pausing).  Anyone seen anything like this before?
Any idea what I can do to fix it?

 

If it's helpful, I'm running jenkins.war from Tomcat 7 on a win XP
machine.

 

Thanks!

 

Bill

 

Antwort: Re: Jenkins as Windows Service; Mercurial.ini

[Andreas Schilling]

Hi Jesse,

all of the described locations didn't work for our case. We wanted to use 
the registry key, but for whatever reason this didn't work either.
Finally we used HGRCPATH environment variable which worked for us.
Unfortunately this is a pretty harsh override, so we had to additionally 
create the .hg/hgrc files in the hg installations (with the hgrc file 
being simply the default config from the installation with another name).

Thanks alot for the help!
 
Andreas Schilling
CAE Processes  Data Management
---
Dipl. Inf. Andreas Schilling
Senior Software Architect

TWT GmbH
Science  Innovation
Bernhäuser Str. 40 - 42
73765 Neuhausen
 
Tel: +49 - 7158 - 17 15 - 673
E-Mail: andreas.schill...@twt-gmbh.de

www.twt-gmbh.de

Geschäftsführung: Dimitrios Vartziotis, Joachim Laicher (stv.)
Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778
Umsatzsteuer: ID-Nr.: DE147841145




Von:Jesse Glick jgl...@cloudbees.com
An: jenkinsci-users@googlegroups.com
Datum:  18.07.2012 00:12
Betreff:Re: Jenkins as Windows Service; Mercurial.ini
Gesendet von:   jenkinsci-users@googlegroups.com



On 07/17/2012 07:56 AM, Andreas Schilling wrote:
 our jenkins master is set up as windows service using the windows local 
system account.
 where are we supposed to put the mercurial.ini with the credentials for 
the https access?

hgrc(5) [1] gives a number of locations where Mercurial looks, or can be 
made to look, for config files.

You can also pass '--config section.key=value' as part of the Mercurial 
command, so defaults could be configured in the Mercurial installation 
your jobs use (see 
$jenkins/configure). Of course this is less secure than storing 
credentials in a local file location; for example, the values will 
probably appear in build logs.

By the way if you are trying to use client certificates, rather than just 
a username/password combo, and get it to work, please update JENKINS-7351 
[2] accordingly.

[1] http://www.selenic.com/mercurial/hgrc.5.html
[2] https://issues.jenkins-ci.org/browse/JENKINS-7351