Run Jenkins under different Linux user

[mwpowellhtx]

Hello,

I've installed under Ubuntu Linux and have the service running as
"anonymous". I want it to run under a jenkins user, and set the home
to something other than /var/lib/path/to/workspace, more like /home/
jenkins/path/to/workspace.

I've identified the /etc/init.d/jenkins script. Is it here where we
set the JENKINS_USER, JENKINS_BASEDIR, and so on?

https://wiki.jenkins-ci.org/display/JENKINS/JenkinsLinuxStartupScript

I'm thinking probably so, but I wonder if anyone has done this before
and can witness.

Regards,

Michael

-- 
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: How to configure Linux Jenkins as not anonymous

[mwpowellhtx]

I am looking at my /etc/init.d/jenkins and it is a bash script. There is a 
JENKINS_USER there, but I don't see it set. I take it, I set it there 
and/or export the value? I'm new to this Linux thing, does that sound about 
right?

On Tuesday, February 26, 2013 11:40:32 AM UTC-6, mwpowellhtx wrote:
>
> Hello, I am sure this question has been asked in different forms before, 
> having some difficulty connecting the dots.
>
> I've got Jenkins more of the way installed, some owner and permissions 
> issues on a jenkins account better understood and resolved.
>
> I can now clone repositories on the command prompt using the jenkins 
> account. That's step one. Now I want to configure Jenkins service to run 
> not as the anonymous user but rather as the jenkins account.
>
> However, it's running as anonymous, trying to work with /var/lib, etc, 
> path to workspace. I want that workspace under the user's home directory 
> instead.
>
> I've been reading bits and pieces how to configure my jenkins start 
> command in a service environment, what configuration files to convey 
> running as the user name, but need a pointer to better understand and 
> resolve it.
>
> Regards,
>
> Michael
>

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

How to configure Linux Jenkins as not anonymous

[mwpowellhtx]

Hello, I am sure this question has been asked in different forms before, 
having some difficulty connecting the dots.

I've got Jenkins more of the way installed, some owner and permissions 
issues on a jenkins account better understood and resolved.

I can now clone repositories on the command prompt using the jenkins 
account. That's step one. Now I want to configure Jenkins service to run 
not as the anonymous user but rather as the jenkins account.

However, it's running as anonymous, trying to work with /var/lib, etc, path 
to workspace. I want that workspace under the user's home directory instead.

I've been reading bits and pieces how to configure my jenkins start command 
in a service environment, what configuration files to convey running as the 
user name, but need a pointer to better understand and resolve it.

Regards,

Michael

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

How to persuade Ubuntu Linux Jenkins to install Git

[mwpowellhtx]

Hello,

As the subject suggests, I am installing Jenkins CI on an Ubuntu Linux VM: 
Unbuntu 10.04 LTS.

I've got Jenkins itself up and running, and I've installed Git and it is 
running as it stands.

Now I want to persuade Jenkins to install Git. Supposedly I've got the Git 
client plugin installed. However, there doesn't appear to be a Git option 
under the job source control configuration.

I've done the very basic stuff at this point. Configured the Jenkins user 
with a home directory, the ITEM_ROOTDIR connected through .profile file in 
the home directory.

However the plugin itself doesn't seem to want to install.

Regards,

Michael

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

Guidance: setting up to build linux distribution

[mwpowellhtx]

Hello,

We've got a linux distribution we are customizing to target our
embedded device. I'd like to automate this process through a CI server
running on Ubuntu 10.04 so that we can capture distro updates,
versions, etc. If it's germane, also get some clue how to capture any
bootstrap processes as an outcome of the CI process: by capture I mean
making the tools available that make it possible to bootstrap and
install the OS and/or other services and apps in a production
environment.

Obviously, I am asking the question here because I'd like to do it
"simply" through something easier like a Jenkins. That's also more
familiar because I am running Jenkins already for other products only
from a Windows environment perspective, so accelerates time to market.

Thanks!

Regards,

Michael

-- 
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: MSBuild VC++ User settings

[mwpowellhtx]

Well, I sort of half answered my own question.

Configuration tends to land in the form: 
ProjectName.vcproj.COMPUTER.USER.user.

I need for it to land in a general manner that Jenkins CI can work with 
when MSBuild sees it.

i need that to pick up radiated output. I might look at other ways to 
capture that that aren't as settings specific.

On Wednesday, January 9, 2013 5:15:40 PM UTC-6, slide wrote:
>
> What configuration do you mean? 
>
> Sent from my Windows Phone
> ------
> From: mwpowellhtx
> Sent: 1/9/2013 4:05 PM
> To: jenkins...@googlegroups.com 
> Subject: MSBuild VC++ User settings
>
> Hello,
>
> Probably more a VS2008 and/or MSBuild question, but I'll ask here anyway
>
> I've got a VS2008 VC++ project that I want to build from Jenkins. The 
> trick is, VS2008 wants to store its configuration in a machine / user 
> specific USER file.
>
> Is there a way to include a global (any machine / any user) USER file?
>
> Regards,
>
> Michael
>

MSBuild VC++ User settings

[mwpowellhtx]

Hello,

Probably more a VS2008 and/or MSBuild question, but I'll ask here anyway

I've got a VS2008 VC++ project that I want to build from Jenkins. The trick 
is, VS2008 wants to store its configuration in a machine / user specific 
USER file.

Is there a way to include a global (any machine / any user) USER file?

Regards,

Michael

Re: How to publish Visual Studio VSTO automatically

[mwpowellhtx]

Mostly figured it out. Hopefully I don't need to repeat it because it
looks like an involved process:

I've got it building on my dev box in a separate workspace and
publishing to a drop area.

Something not unlike this article: 
http://msdn.microsoft.com/en-us/library/ff624126.aspx
(How to Build Visual Studio 2010 Office Development Projects with TFS
Team Build 2010), except for VS2012, Jenkins, and Office 2013 PIAs.

On Dec 27, 1:28 pm, mwpowellhtx  wrote:
> I should say: the latest PIAs: Office 2013 at the time of this post.
>
> On Dec 27, 1:27 pm, mwpowellhtx  wrote:
>
>
>
>
>
>
>
> > Hello,
>
> > I've got an Visual Studio Tools for Office Excel AddIn that I am
> > scheduling for build. I build the Debug and Release versions, and that
> > seems to be going well. I'd like to add a step that publishes to a
> > staging folder, possibly share for folks to demo, evaluate release
> > candidates, etc. Possibly ClickOnce style, if possible: trick being
> > it's built against Office PIAs. I searched the group and to my
> > surprise didn't find anything "publish". Does anyone know is this
> > possible? Is it a target we build or something like this? Thanks in
> > advance, and I'm going to dig into this a bit further myself
> > meanwhile.
>
> > Regards,
>
> > Michael

Re: How to publish Visual Studio VSTO automatically

[mwpowellhtx]

I should say: the latest PIAs: Office 2013 at the time of this post.

On Dec 27, 1:27 pm, mwpowellhtx  wrote:
> Hello,
>
> I've got an Visual Studio Tools for Office Excel AddIn that I am
> scheduling for build. I build the Debug and Release versions, and that
> seems to be going well. I'd like to add a step that publishes to a
> staging folder, possibly share for folks to demo, evaluate release
> candidates, etc. Possibly ClickOnce style, if possible: trick being
> it's built against Office PIAs. I searched the group and to my
> surprise didn't find anything "publish". Does anyone know is this
> possible? Is it a target we build or something like this? Thanks in
> advance, and I'm going to dig into this a bit further myself
> meanwhile.
>
> Regards,
>
> Michael

How to publish Visual Studio VSTO automatically

[mwpowellhtx]

Hello,

I've got an Visual Studio Tools for Office Excel AddIn that I am
scheduling for build. I build the Debug and Release versions, and that
seems to be going well. I'd like to add a step that publishes to a
staging folder, possibly share for folks to demo, evaluate release
candidates, etc. Possibly ClickOnce style, if possible: trick being
it's built against Office PIAs. I searched the group and to my
surprise didn't find anything "publish". Does anyone know is this
possible? Is it a target we build or something like this? Thanks in
advance, and I'm going to dig into this a bit further myself
meanwhile.

Regards,

Michael

Re: Jenkins Git suddenly stopped working

[mwpowellhtx]

The mystery still has me puzzled: Git Bash worked cloning, fetching, 
pulling. Yet Jenkins persistently failed even after repeated attempts 
restarting Jenkins Windows Service. It sounds plausible that Windows DNS 
Cache Service needed restarting, but then why did Git Bash work and Jenkins 
service did not? Are there any other services upon which Jenkins depends 
that might cause something like this? For now I've got an entry in my hosts 
file, but I still don't think I should have to do this, provided of course 
DNS is working right.

On Friday, December 14, 2012 6:09:41 AM UTC-6, mwpowellhtx wrote:
>
> I checked this, and Jenkins is running as a Windows Service logging in as 
> System. It doesn't get any more permissive than that. It is running as 
> "anonymous" during the job itself. Not sure how to set that other than null 
> or anonymous?
>
> On Thursday, December 13, 2012 8:25:36 PM UTC-6, SA Evans wrote:
>>
>> Not sure what OS you're running on, but could it be that the user that 
>> the Jenkins agent is running as might not have permissions to access 
>> network resources to do a DNS lookup?  Seems odd, but that's the only thing 
>> that comes to mind for this case.
>>
>> Scott
>>
>> On Thu, Dec 13, 2012 at 7:29 PM, mwpowellhtx  wrote:
>>
>>> Don't know what happened. Turns out it was a strange DNS issue (as folks 
>>> pointed out). What makes it strange is why it would fail for Jenkins and 
>>> still succeed for a command line Git Bash.
>>>
>>> To workaround I added an entry in my hosts file and that has "fixed" at 
>>> least my part of the issue. Still in question is whether whatever DNS 
>>> services are up and running properly.
>>>
>>> On Thursday, December 13, 2012 6:05:04 PM UTC-6, mwpowellhtx wrote:
>>>>
>>>> No, Jenkins is running on the same machine as my day to day 
>>>> development. Not the best of ideas I know.
>>>>
>>>> For the second part, yes, I can clone from a command line or Git Bash.
>>>>
>>>> On Thursday, December 13, 2012 5:44:40 PM UTC-6, Andrew Melo wrote:
>>>>>
>>>>> I mean, presumably the machine you work on day to day isn't the 
>>>>> machine your Jenkins slaves run on (since it seems like you have a larger 
>>>>> install)
>>>>>
>>>>> If you SSH to your Jenkins master/slaves, can you clone from them?
>>>>>
>>>>> 
>>>>> Andrew Melo
>>>>> Sent from my secret fortress.
>>>>>
>>>>> On Dec 14, 2012, at 0:17, mwpowellhtx  wrote:
>>>>>
>>>>> How do you mean, "connect to your slaves, clone manually"? From a 
>>>>> command line or Git Bash? Yes, I can clone manually with the same (copy 
>>>>> and 
>>>>> paste) SSH URI.
>>>>>
>>>>> On Thursday, December 13, 2012 4:33:12 PM UTC-6, Andrew Melo wrote:
>>>>>>
>>>>>> On Thu, Dec 13, 2012 at 11:24 PM, mwpowellhtx  
>>>>>> wrote: 
>>>>>> > And I can assure you it's not. I copy and paste the exact same 
>>>>>> address on 
>>>>>> > the command line, and I can clone from the command line. Only 
>>>>>> Jenkins is now 
>>>>>> > consistently failing across the board for jobs that were previously 
>>>>>> > succeeding. 
>>>>>> > 
>>>>>> > We're speculating whether repositoryhosting.com (our host) has 
>>>>>> some limits 
>>>>>> > set on SSH. 
>>>>>>
>>>>>> This seems to look like your DNS isnt resolving the host name right, 
>>>>>> it's not (necessarily) a matter of you fumbling the hostname... 
>>>>>>
>>>>>> stderr: ssh: : no address associated with name 
>>>>>> fatal: Could not read from remote repository. 
>>>>>>
>>>>>> If you connect to your slaves, can you do a git clone manually? 
>>>>>>
>>>>>> > 
>>>>>> > 
>>>>>> > On Thursday, December 13, 2012 3:59:42 PM UTC-6, SA Evans wrote: 
>>>>>> >> 
>>>>>> >> The error would indicate to me that it can't find the host where 
>>>>>> your repo 
>>>>>> >> is, whether a typo in that variable setting that's not gett

Re: Jenkins Git suddenly stopped working

[mwpowellhtx]

I checked this, and Jenkins is running as a Windows Service logging in as 
System. It doesn't get any more permissive than that. It is running as 
"anonymous" during the job itself. Not sure how to set that other than null 
or anonymous?

On Thursday, December 13, 2012 8:25:36 PM UTC-6, SA Evans wrote:
>
> Not sure what OS you're running on, but could it be that the user that the 
> Jenkins agent is running as might not have permissions to access network 
> resources to do a DNS lookup?  Seems odd, but that's the only thing that 
> comes to mind for this case.
>
> Scott
>
> On Thu, Dec 13, 2012 at 7:29 PM, mwpowellhtx 
> > wrote:
>
>> Don't know what happened. Turns out it was a strange DNS issue (as folks 
>> pointed out). What makes it strange is why it would fail for Jenkins and 
>> still succeed for a command line Git Bash.
>>
>> To workaround I added an entry in my hosts file and that has "fixed" at 
>> least my part of the issue. Still in question is whether whatever DNS 
>> services are up and running properly.
>>
>> On Thursday, December 13, 2012 6:05:04 PM UTC-6, mwpowellhtx wrote:
>>>
>>> No, Jenkins is running on the same machine as my day to day development. 
>>> Not the best of ideas I know.
>>>
>>> For the second part, yes, I can clone from a command line or Git Bash.
>>>
>>> On Thursday, December 13, 2012 5:44:40 PM UTC-6, Andrew Melo wrote:
>>>>
>>>> I mean, presumably the machine you work on day to day isn't the machine 
>>>> your Jenkins slaves run on (since it seems like you have a larger install)
>>>>
>>>> If you SSH to your Jenkins master/slaves, can you clone from them?
>>>>
>>>> 
>>>> Andrew Melo
>>>> Sent from my secret fortress.
>>>>
>>>> On Dec 14, 2012, at 0:17, mwpowellhtx  wrote:
>>>>
>>>> How do you mean, "connect to your slaves, clone manually"? From a 
>>>> command line or Git Bash? Yes, I can clone manually with the same (copy 
>>>> and 
>>>> paste) SSH URI.
>>>>
>>>> On Thursday, December 13, 2012 4:33:12 PM UTC-6, Andrew Melo wrote:
>>>>>
>>>>> On Thu, Dec 13, 2012 at 11:24 PM, mwpowellhtx  
>>>>> wrote: 
>>>>> > And I can assure you it's not. I copy and paste the exact same 
>>>>> address on 
>>>>> > the command line, and I can clone from the command line. Only 
>>>>> Jenkins is now 
>>>>> > consistently failing across the board for jobs that were previously 
>>>>> > succeeding. 
>>>>> > 
>>>>> > We're speculating whether repositoryhosting.com (our host) has some 
>>>>> limits 
>>>>> > set on SSH. 
>>>>>
>>>>> This seems to look like your DNS isnt resolving the host name right, 
>>>>> it's not (necessarily) a matter of you fumbling the hostname... 
>>>>>
>>>>> stderr: ssh: : no address associated with name 
>>>>> fatal: Could not read from remote repository. 
>>>>>
>>>>> If you connect to your slaves, can you do a git clone manually? 
>>>>>
>>>>> > 
>>>>> > 
>>>>> > On Thursday, December 13, 2012 3:59:42 PM UTC-6, SA Evans wrote: 
>>>>> >> 
>>>>> >> The error would indicate to me that it can't find the host where 
>>>>> your repo 
>>>>> >> is, whether a typo in that variable setting that's not getting 
>>>>> resolved 
>>>>> >> through your nameserver, or some sort of network issue, most 
>>>>> likely. 
>>>>> >> 
>>>>> >> 
>>>>> >> 
>>>>> >> On Thu, Dec 13, 2012 at 3:47 PM, mwpowellhtx  
>>>>> wrote: 
>>>>> >>> 
>>>>> >>> To clarify, I've edited the actual names out. The names are there, 
>>>>> it was 
>>>>> >>> working earlier. Now suddenly it has stopped working. 
>>>>> >>> 
>>>>> >>> A colleague of mine and I are wondering whether it's a SSH thing, 
>>>>> or 
>>>>> >>> perhaps there's a limit set by our host, or something. 
>>>>> >>> 
>>>>> >>> On Thursday, December 13, 2012 3:43:44 PM UTC-6, mwpowellhtx 
>>>>> wrote: 
>>>>> >>>> 
>>>>> >>>> I'm not sure what you mean. Can you be more specific? It's 
>>>>> possible 
>>>>> >>>> something got unset, but like I said, it was working all day 
>>>>> until just now. 
>>>>> >>>> 
>>>>> >>>> On Thursday, December 13, 2012 3:38:27 PM UTC-6, SA Evans wrote: 
>>>>> >>>>> 
>>>>> >>>>> Looks like you're missing an environment setting for repo-host 
>>>>> >>>>> 
>>>>> >>>>> Scott 
>>>>> >>>>> 
>>>>> >>>>> On Thu, Dec 13, 2012 at 3:35 PM, mwpowellhtx  
>>>>>
>>>>> >>>>> wrote: 
>>>>> >>>>>> 
>>>>> >>>>>> stderr: ssh: : no address associated with name 
>>>>> >>>>> 
>>>>> >>>>> 
>>>>> >> 
>>>>> > 
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> -- 
>>>>> Andrew Melo 
>>>>>
>>>>
>

Re: Jenkins Git suddenly stopped working

[mwpowellhtx]

Don't know what happened. Turns out it was a strange DNS issue (as folks 
pointed out). What makes it strange is why it would fail for Jenkins and 
still succeed for a command line Git Bash.

To workaround I added an entry in my hosts file and that has "fixed" at 
least my part of the issue. Still in question is whether whatever DNS 
services are up and running properly.

On Thursday, December 13, 2012 6:05:04 PM UTC-6, mwpowellhtx wrote:
>
> No, Jenkins is running on the same machine as my day to day development. 
> Not the best of ideas I know.
>
> For the second part, yes, I can clone from a command line or Git Bash.
>
> On Thursday, December 13, 2012 5:44:40 PM UTC-6, Andrew Melo wrote:
>>
>> I mean, presumably the machine you work on day to day isn't the machine 
>> your Jenkins slaves run on (since it seems like you have a larger install)
>>
>> If you SSH to your Jenkins master/slaves, can you clone from them?
>>
>> ----
>> Andrew Melo
>> Sent from my secret fortress.
>>
>> On Dec 14, 2012, at 0:17, mwpowellhtx  wrote:
>>
>> How do you mean, "connect to your slaves, clone manually"? From a command 
>> line or Git Bash? Yes, I can clone manually with the same (copy and paste) 
>> SSH URI.
>>
>> On Thursday, December 13, 2012 4:33:12 PM UTC-6, Andrew Melo wrote:
>>>
>>> On Thu, Dec 13, 2012 at 11:24 PM, mwpowellhtx  
>>> wrote: 
>>> > And I can assure you it's not. I copy and paste the exact same address 
>>> on 
>>> > the command line, and I can clone from the command line. Only Jenkins 
>>> is now 
>>> > consistently failing across the board for jobs that were previously 
>>> > succeeding. 
>>> > 
>>> > We're speculating whether repositoryhosting.com (our host) has some 
>>> limits 
>>> > set on SSH. 
>>>
>>> This seems to look like your DNS isnt resolving the host name right, 
>>> it's not (necessarily) a matter of you fumbling the hostname... 
>>>
>>> stderr: ssh: : no address associated with name 
>>> fatal: Could not read from remote repository. 
>>>
>>> If you connect to your slaves, can you do a git clone manually? 
>>>
>>> > 
>>> > 
>>> > On Thursday, December 13, 2012 3:59:42 PM UTC-6, SA Evans wrote: 
>>> >> 
>>> >> The error would indicate to me that it can't find the host where your 
>>> repo 
>>> >> is, whether a typo in that variable setting that's not getting 
>>> resolved 
>>> >> through your nameserver, or some sort of network issue, most likely. 
>>> >> 
>>> >> 
>>> >> 
>>> >> On Thu, Dec 13, 2012 at 3:47 PM, mwpowellhtx  
>>> wrote: 
>>> >>> 
>>> >>> To clarify, I've edited the actual names out. The names are there, 
>>> it was 
>>> >>> working earlier. Now suddenly it has stopped working. 
>>> >>> 
>>> >>> A colleague of mine and I are wondering whether it's a SSH thing, or 
>>> >>> perhaps there's a limit set by our host, or something. 
>>> >>> 
>>> >>> On Thursday, December 13, 2012 3:43:44 PM UTC-6, mwpowellhtx wrote: 
>>> >>>> 
>>> >>>> I'm not sure what you mean. Can you be more specific? It's possible 
>>> >>>> something got unset, but like I said, it was working all day until 
>>> just now. 
>>> >>>> 
>>> >>>> On Thursday, December 13, 2012 3:38:27 PM UTC-6, SA Evans wrote: 
>>> >>>>> 
>>> >>>>> Looks like you're missing an environment setting for repo-host 
>>> >>>>> 
>>> >>>>> Scott 
>>> >>>>> 
>>> >>>>> On Thu, Dec 13, 2012 at 3:35 PM, mwpowellhtx  
>>> >>>>> wrote: 
>>> >>>>>> 
>>> >>>>>> stderr: ssh: : no address associated with name 
>>> >>>>> 
>>> >>>>> 
>>> >> 
>>> > 
>>>
>>>
>>>
>>> -- 
>>> -- 
>>> Andrew Melo 
>>>
>>

Re: Jenkins Git suddenly stopped working

[mwpowellhtx]

No, Jenkins is running on the same machine as my day to day development. 
Not the best of ideas I know.

For the second part, yes, I can clone from a command line or Git Bash.

On Thursday, December 13, 2012 5:44:40 PM UTC-6, Andrew Melo wrote:
>
> I mean, presumably the machine you work on day to day isn't the machine 
> your Jenkins slaves run on (since it seems like you have a larger install)
>
> If you SSH to your Jenkins master/slaves, can you clone from them?
>
> 
> Andrew Melo
> Sent from my secret fortress.
>
> On Dec 14, 2012, at 0:17, mwpowellhtx > 
> wrote:
>
> How do you mean, "connect to your slaves, clone manually"? From a command 
> line or Git Bash? Yes, I can clone manually with the same (copy and paste) 
> SSH URI.
>
> On Thursday, December 13, 2012 4:33:12 PM UTC-6, Andrew Melo wrote:
>>
>> On Thu, Dec 13, 2012 at 11:24 PM, mwpowellhtx  
>> wrote: 
>> > And I can assure you it's not. I copy and paste the exact same address 
>> on 
>> > the command line, and I can clone from the command line. Only Jenkins 
>> is now 
>> > consistently failing across the board for jobs that were previously 
>> > succeeding. 
>> > 
>> > We're speculating whether repositoryhosting.com (our host) has some 
>> limits 
>> > set on SSH. 
>>
>> This seems to look like your DNS isnt resolving the host name right, 
>> it's not (necessarily) a matter of you fumbling the hostname... 
>>
>> stderr: ssh: : no address associated with name 
>> fatal: Could not read from remote repository. 
>>
>> If you connect to your slaves, can you do a git clone manually? 
>>
>> > 
>> > 
>> > On Thursday, December 13, 2012 3:59:42 PM UTC-6, SA Evans wrote: 
>> >> 
>> >> The error would indicate to me that it can't find the host where your 
>> repo 
>> >> is, whether a typo in that variable setting that's not getting 
>> resolved 
>> >> through your nameserver, or some sort of network issue, most likely. 
>> >> 
>> >> 
>> >> 
>> >> On Thu, Dec 13, 2012 at 3:47 PM, mwpowellhtx  
>> wrote: 
>> >>> 
>> >>> To clarify, I've edited the actual names out. The names are there, it 
>> was 
>> >>> working earlier. Now suddenly it has stopped working. 
>> >>> 
>> >>> A colleague of mine and I are wondering whether it's a SSH thing, or 
>> >>> perhaps there's a limit set by our host, or something. 
>> >>> 
>> >>> On Thursday, December 13, 2012 3:43:44 PM UTC-6, mwpowellhtx wrote: 
>> >>>> 
>> >>>> I'm not sure what you mean. Can you be more specific? It's possible 
>> >>>> something got unset, but like I said, it was working all day until 
>> just now. 
>> >>>> 
>> >>>> On Thursday, December 13, 2012 3:38:27 PM UTC-6, SA Evans wrote: 
>> >>>>> 
>> >>>>> Looks like you're missing an environment setting for repo-host 
>> >>>>> 
>> >>>>> Scott 
>> >>>>> 
>> >>>>> On Thu, Dec 13, 2012 at 3:35 PM, mwpowellhtx  
>> >>>>> wrote: 
>> >>>>>> 
>> >>>>>> stderr: ssh: : no address associated with name 
>> >>>>> 
>> >>>>> 
>> >> 
>> > 
>>
>>
>>
>> -- 
>> -- 
>> Andrew Melo 
>>
>

Re: Jenkins Git suddenly stopped working

[mwpowellhtx]

How do you mean, "connect to your slaves, clone manually"? From a command 
line or Git Bash? Yes, I can clone manually with the same (copy and paste) 
SSH URI.

On Thursday, December 13, 2012 4:33:12 PM UTC-6, Andrew Melo wrote:
>
> On Thu, Dec 13, 2012 at 11:24 PM, mwpowellhtx 
> > 
> wrote: 
> > And I can assure you it's not. I copy and paste the exact same address 
> on 
> > the command line, and I can clone from the command line. Only Jenkins is 
> now 
> > consistently failing across the board for jobs that were previously 
> > succeeding. 
> > 
> > We're speculating whether repositoryhosting.com (our host) has some 
> limits 
> > set on SSH. 
>
> This seems to look like your DNS isnt resolving the host name right, 
> it's not (necessarily) a matter of you fumbling the hostname... 
>
> stderr: ssh: : no address associated with name 
> fatal: Could not read from remote repository. 
>
> If you connect to your slaves, can you do a git clone manually? 
>
> > 
> > 
> > On Thursday, December 13, 2012 3:59:42 PM UTC-6, SA Evans wrote: 
> >> 
> >> The error would indicate to me that it can't find the host where your 
> repo 
> >> is, whether a typo in that variable setting that's not getting resolved 
> >> through your nameserver, or some sort of network issue, most likely. 
> >> 
> >> 
> >> 
> >> On Thu, Dec 13, 2012 at 3:47 PM, mwpowellhtx  
> wrote: 
> >>> 
> >>> To clarify, I've edited the actual names out. The names are there, it 
> was 
> >>> working earlier. Now suddenly it has stopped working. 
> >>> 
> >>> A colleague of mine and I are wondering whether it's a SSH thing, or 
> >>> perhaps there's a limit set by our host, or something. 
> >>> 
> >>> On Thursday, December 13, 2012 3:43:44 PM UTC-6, mwpowellhtx wrote: 
> >>>> 
> >>>> I'm not sure what you mean. Can you be more specific? It's possible 
> >>>> something got unset, but like I said, it was working all day until 
> just now. 
> >>>> 
> >>>> On Thursday, December 13, 2012 3:38:27 PM UTC-6, SA Evans wrote: 
> >>>>> 
> >>>>> Looks like you're missing an environment setting for repo-host 
> >>>>> 
> >>>>> Scott 
> >>>>> 
> >>>>> On Thu, Dec 13, 2012 at 3:35 PM, mwpowellhtx  
> >>>>> wrote: 
> >>>>>> 
> >>>>>> stderr: ssh: : no address associated with name 
> >>>>> 
> >>>>> 
> >> 
> > 
>
>
>
> -- 
> -- 
> Andrew Melo 
>

Re: Jenkins Git suddenly stopped working

[mwpowellhtx]

And I can assure you it's not. I copy and paste the exact same address on 
the command line, and I can clone from the command line. Only Jenkins is 
now consistently failing across the board for jobs that were previously 
succeeding.

We're speculating whether repositoryhosting.com (our host) has some limits 
set on SSH.

On Thursday, December 13, 2012 3:59:42 PM UTC-6, SA Evans wrote:
>
> The error would indicate to me that it can't find the host where your repo 
> is, whether a typo in that variable setting that's not getting resolved 
> through your nameserver, or some sort of network issue, most likely.
>
>
>
> On Thu, Dec 13, 2012 at 3:47 PM, mwpowellhtx 
> > wrote:
>
>> To clarify, I've edited the actual names out. The names are there, it was 
>> working earlier. Now suddenly it has stopped working.
>>
>> A colleague of mine and I are wondering whether it's a SSH thing, or 
>> perhaps there's a limit set by our host, or something.
>>
>> On Thursday, December 13, 2012 3:43:44 PM UTC-6, mwpowellhtx wrote:
>>>
>>> I'm not sure what you mean. Can you be more specific? It's possible 
>>> something got unset, but like I said, it was working all day until just now.
>>>
>>> On Thursday, December 13, 2012 3:38:27 PM UTC-6, SA Evans wrote:
>>>>
>>>> Looks like you're missing an environment setting for repo-host
>>>>
>>>> Scott
>>>>
>>>> On Thu, Dec 13, 2012 at 3:35 PM, mwpowellhtx wrote:
>>>>
>>>>> stderr: ssh: : no address associated with name
>>>>
>>>>
>>>>
>

Re: Jenkins Git suddenly stopped working

[mwpowellhtx]

To clarify, I've edited the actual names out. The names are there, it was 
working earlier. Now suddenly it has stopped working.

A colleague of mine and I are wondering whether it's a SSH thing, or 
perhaps there's a limit set by our host, or something.

On Thursday, December 13, 2012 3:43:44 PM UTC-6, mwpowellhtx wrote:
>
> I'm not sure what you mean. Can you be more specific? It's possible 
> something got unset, but like I said, it was working all day until just now.
>
> On Thursday, December 13, 2012 3:38:27 PM UTC-6, SA Evans wrote:
>>
>> Looks like you're missing an environment setting for repo-host
>>
>> Scott
>>
>> On Thu, Dec 13, 2012 at 3:35 PM, mwpowellhtx  wrote:
>>
>>> stderr: ssh: : no address associated with name
>>
>>
>>

Re: Jenkins Git suddenly stopped working

[mwpowellhtx]

I'm not sure what you mean. Can you be more specific? It's possible 
something got unset, but like I said, it was working all day until just now.

On Thursday, December 13, 2012 3:38:27 PM UTC-6, SA Evans wrote:
>
> Looks like you're missing an environment setting for repo-host
>
> Scott
>
> On Thu, Dec 13, 2012 at 3:35 PM, mwpowellhtx 
> > wrote:
>
>> stderr: ssh: : no address associated with name
>
>
>

Jenkins Git suddenly stopped working

[mwpowellhtx]

I am experiencing the following error(s).

I've been working on build jobs today in Jenkins and polling our online 
repository hosting frequently. It's been working most of today until 
recently the past hour or two. Now suddenly I am receiving the following 
error(s), for one job I am currently working on, and verified, a prior job 
I got working earlier is now breaking for the same reason.

I've also contacted our host thinking that perhaps the issue is with them. 
The strange part is that I can still clone from the command line, but 
Jenkins is consistently failing where Jenkins was working earlier.

Any suggestions?

Thank you...

Started by user anonymous 
[EnvInject] - Loading node environment variables.
Building in workspace 
Checkout:workspace /  - hudson.remoting.LocalChannel@18f57d2
Using strategy: Default
Last Built Revision: Revision  (origin/master)
Fetching changes from 1 remote Git repository
Fetching upstream changes from ssh://git@//.git
ERROR: Problem fetching from origin / origin - could be unavailable. Continuing 
anywayhudson.plugins.git.GitException 
:
 Command "git.exe fetch -t ssh://git@//.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: ssh: : no address associated with name
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:897)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:858)
at hudson.plugins.git.GitAPI.fetch(GitAPI.java:200)
at hudson.plugins.git.GitAPI.fetch(GitAPI.java:1105)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:813)
at hudson.plugins.git.GitSCM.access$100(GitSCM.java:72)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1018)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986)
at hudson.FilePath.act(FilePath.java:852)
at hudson.FilePath.act(FilePath.java:825)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:986)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1142)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1324)
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:1518)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
ERROR: Could not fetch from any repositoryFATAL 
: Could not fetch from any 
repositoryhudson.plugins.git.GitException 
:
 Could not fetch from any repository
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1025) 

at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) 

at hudson.FilePath.act(FilePath.java:852) 

at hudson.FilePath.act(FilePath.java:825) 

at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:986) 

at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1142) 

at hudson.model.AbstractProject.checkout(AbstractProject.java:1324) 

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:1518) 

Re: How to run PowerShell during job

[mwpowellhtx]

This is helpful: 
http://jenkins.361315.n4.nabble.com/PowerShell-plug-in-question-td1468725.html

After that it's the usual troubleshooting script issues from different 
runtime contexts.

On Thursday, December 13, 2012 1:06:13 PM UTC-6, mwpowellhtx wrote:
>
> Hello,
>
> We've got some Windows PowerShell scripts I would like to expose 
> throughout our jobs for natural house keeping steps.
>
> I've got the Set-ExecutionPolicy set appropriately and I can run scripts 
> apart from Jenkins through the command line, with PowerShell (i.e. context 
> menu), etc.
>
> Running through the PowerShell task doesn't work at all, it fails. I try 
> as a Windows Batch Command task, the command is nothing special.
>
> powershell.exe -File "" "" "" 
>
>
> However, when I run the Job I get the following error:
>
> File  cannot be loaded because the execution of 
> scripts is disabled on this system. Please see "get-help about_signing" for 
> more details.
>
>
> Now, is the Jenkins process somehow signing the wrappers it puts around 
> such scripts? We've got the execution policy set otherwise, which if it's a 
> conflict, then perhaps we abandon PowerShell altogether for something more 
> "conventional" like Batch or Command files.
>
> We've got the PowerShell scripts today, so obviously if I can get them to 
> work, I want to do that. But if I need to rewrite them as batch files, then 
> I'll do that instead.
>
> Thanks in advance..
>
> Regards,
>
> Michael
>

How to run PowerShell during job

[mwpowellhtx]

Hello,

We've got some Windows PowerShell scripts I would like to expose throughout 
our jobs for natural house keeping steps.

I've got the Set-ExecutionPolicy set appropriately and I can run scripts 
apart from Jenkins through the command line, with PowerShell (i.e. context 
menu), etc.

Running through the PowerShell task doesn't work at all, it fails. I try as 
a Windows Batch Command task, the command is nothing special.

powershell.exe -File "" "" "" 


However, when I run the Job I get the following error:

File  cannot be loaded because the execution of 
scripts is disabled on this system. Please see "get-help about_signing" for 
more details.


Now, is the Jenkins process somehow signing the wrappers it puts around 
such scripts? We've got the execution policy set otherwise, which if it's a 
conflict, then perhaps we abandon PowerShell altogether for something more 
"conventional" like Batch or Command files.

We've got the PowerShell scripts today, so obviously if I can get them to 
work, I want to do that. But if I need to rewrite them as batch files, then 
I'll do that instead.

Thanks in advance..

Regards,

Michael

Re: Really corrupt build history

[mwpowellhtx]

So the corruption is rooted in operator error: I misconfigured the Jenkins 
builds configuration. Did a little more reading and it seems that when you 
set the builds directory in the Jenkins configuration to 
${ITEM_ROOTDIR}/builds, this corrects the problem, is now job-specific. It 
would be better if we could possibly pull these aside from the Jenkins 
install location for easier backup and restore purposes, but this will work 
for now.

On Thursday, December 13, 2012 11:08:21 AM UTC-6, mwpowellhtx wrote:
>
> Hello,
>
> I have half a dozen or so jobs configured to run and I am finding that 
> Jenkins build history is becoming very corrupt. We're running 1.492 in a 
> Windows 7 Ultimate environment.
>
> Here's what I am experiencing:
>
>- From time to time my executor threads will just completely die. It 
>usually takes pulling the build history aside and letting Jenkins start 
>afresh to recover from this. One of the issues appears to be array 
>indexing, frequently thinking it has an invalid array index. Apparently 
>also a known issue for quite some time from other posts I've read.
>- I've started up the system once again and now I am finding that the 
>build history is apparently really confused. I have one disabled job and 
>all the others were building yesterday with valid history.
>
> How can any snafus like this be happening? I mean, did the designers of 
> these systems and subsystems consider that a build environment would have 
> use cases involving multiple independently scheduled jobs?
>
> The other option we can consider is to not keep a running build history at 
> all, particularly in a matrix build environment like we're got running. 
> History is nice and to show a healthy build history track record, but is 
> not as important as long as we can capture artifacts like generated 
> documents, NuGet packages, installers, and the like.
>
> I hate to say it, but if Jenkins is going to be this unstable, I wonder if 
> I don't give Hudson a try (again). Or even spend the energy to configure a 
> CruiseControl.NET. But the first thing I want to consider is 86'ing the 
> build history if it's going to cause that many problems.
>
> Any others with thoughts? Questions, concerns, suggestions?
>
> Regards,
>
> Michael
>

Really corrupt build history

[mwpowellhtx]

Hello,

I have half a dozen or so jobs configured to run and I am finding that 
Jenkins build history is becoming very corrupt. We're running 1.492 in a 
Windows 7 Ultimate environment.

Here's what I am experiencing:

   - From time to time my executor threads will just completely die. It 
   usually takes pulling the build history aside and letting Jenkins start 
   afresh to recover from this. One of the issues appears to be array 
   indexing, frequently thinking it has an invalid array index. Apparently 
   also a known issue for quite some time from other posts I've read.
   - I've started up the system once again and now I am finding that the 
   build history is apparently really confused. I have one disabled job and 
   all the others were building yesterday with valid history.
   
How can any snafus like this be happening? I mean, did the designers of 
these systems and subsystems consider that a build environment would have 
use cases involving multiple independently scheduled jobs?

The other option we can consider is to not keep a running build history at 
all, particularly in a matrix build environment like we're got running. 
History is nice and to show a healthy build history track record, but is 
not as important as long as we can capture artifacts like generated 
documents, NuGet packages, installers, and the like.

I hate to say it, but if Jenkins is going to be this unstable, I wonder if 
I don't give Hudson a try (again). Or even spend the energy to configure a 
CruiseControl.NET. But the first thing I want to consider is 86'ing the 
build history if it's going to cause that many problems.

Any others with thoughts? Questions, concerns, suggestions?

Regards,

Michael

Re: Confusion over build triggers

[mwpowellhtx]

Yessir, and re: a previous reply as well, this is what we ended up doing.

 Thanks for the speedy reply and happy CI! :-)

- Original Message -
From: Sami Tikka
Sent: 08/17/12 04:00 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Confusion over build triggers

 As far as I understand, the standard triggering of other projects from 
post-build actions does what you want. Go into A's configuration: Add 
post-build action -> Build other projects. Enter project name B, choose 
"Trigger only if build succeeds". If it doesn't, maybe you could be even more 
specific with your description? -- Sami mwpowellhtx  
kirjoitti 17.8.2012 kello 13.00: > Hello, > > In test and measurement verbiage, 
I think of a trigger as just that: see an event, respond to that event. > > Say 
we have two jobs: A and B. > > A runs when it sees SCM change and builds that 
environment. > > I'd like to schedule B when A has successfully completed a 
build and build the same environment but in a different configuration, possibly 
run some tests, etc. > > I don't want to look for the most recent build as it 
could be stale: hours, even days or weeks old. Only when A is actually running, 
and runs to completion. > > How to explain exactly? Hard to do so unless you're 
familiar with the pattern: trigger, particularly as I am accustomed to talking 
about it, i.e. T&M. > > Is there anything in the Jenkins plugin world that can 
do this? Or are we stuck with a chained build setup in A? > > Thanks in advance.



Best regards,

 Michael Powell
 Senior Software Developer

Re: Confusion over build triggers

[mwpowellhtx]

I'll just add, as others have suggested, an SCM trigger in B doesn't
quite do what we need it to do, because our build environment mucks
with configuration in the system, not just a Jenkins build workspace.
What we need is a timely, stateful trigger on B that responds to A
when it finds A successfully completed.

On Aug 17, 5:00 am, mwpowellhtx  wrote:
> Hello,
>
> In test and measurement verbiage, I think of a trigger as just that: see an
> event, respond to that event.
>
> Say we have two jobs: A and B.
>
> A runs when it sees SCM change and builds that environment.
>
> I'd like to schedule B when A has successfully completed a build and build
> the same environment but in a different configuration, possibly run some
> tests, etc.
>
> I don't want to look for the most recent build as it could be stale: hours,
> even days or weeks old. Only when A is actually running, and runs to
> completion.
>
> How to explain exactly? Hard to do so unless you're familiar with the
> pattern: trigger, particularly as I am accustomed to talking about it, i.e.
> T&M.
>
> Is there anything in the Jenkins plugin world that can do this? Or are we
> stuck with a chained build setup in A?
>
> Thanks in advance.

Confusion over build triggers

[mwpowellhtx]

Hello,

In test and measurement verbiage, I think of a trigger as just that: see an 
event, respond to that event.

Say we have two jobs: A and B.

A runs when it sees SCM change and builds that environment.

I'd like to schedule B when A has successfully completed a build and build 
the same environment but in a different configuration, possibly run some 
tests, etc.

I don't want to look for the most recent build as it could be stale: hours, 
even days or weeks old. Only when A is actually running, and runs to 
completion.

How to explain exactly? Hard to do so unless you're familiar with the 
pattern: trigger, particularly as I am accustomed to talking about it, i.e. 
T&M.

Is there anything in the Jenkins plugin world that can do this? Or are we 
stuck with a chained build setup in A?

Thanks in advance.