Errors while using Credential manager to store P4 password

[Shobha Dashottar]

I used the Credential manager plugin to store the perforce credentials. I 
have filled in the details as required on the Jenkins -> Credentials - > 
Global Credentials page  like the p4 port, ssl connection, fingerprint , 
username and password. but on clicking on "test Connection" I get the 
following error

Unable to connect to: p4javassl://perforce.xxx.com:1666
Unable to determine client host name: Jenkinshostname: Jenkinshostname

Where Jenkinshostname is the hostname of the Linux machine( RHEL 6 x64)  
with Jenkins installed.

Am I missing something?

Thanks
Shobha

-- 
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: Git Publish breaking build and un-deletable

[Mark Waite]

On Wed, Sep 24, 2014 at 9:06 AM,  wrote:

> More info
>
> Git Client Plugin
> 
> Shared library plugin for other Git related Jenkins plugins.
> 1.10.21.0.7
> Git Parameter Plugin
> 
> This plugin allows you to choose between Git tags or sha1 of your SCM
> repository so Git Plugin installed is required.
> Warning: This plugin is built for Jenkins 1.554.1 or newer. It may or may
> not work in your Jenkins.
> 0.3.20.2
> Git Plugin 
> This plugin allows use of Git  as a build SCM. A
> recent Git runtime is required (1.7.9 minimum, 1.8.x recommended). Plugin
> is only tested on official git client . Use exotic
> installations at your own risks.
> 2.2.61.4.0
>
>
If I am guessing correctly, that table hints that you upgraded from git
client plugin 1.0.7 to git client plugin 1.10.2 and from git plugin 1.4.0
to git plugin 2.2.6.  That is a long jump.  The git plugin transition from
version 1 to version 2 was a major transition.

You're also running a Jenkins version which is not a long term support
version but is over a year old.

For the specific problem you're seeing, you might try saving the job
definition from the user interface, then loading it again.  There may be
some gaps in the upgrade process from a plugin version that old to the
current plugin version.

You could also attempt to remove the git publisher section from the
config.xml file of the job (keep a backup copy of the working job
definition just in case), then attempt to add the git publisher section
again.

You could also update to a more recent Jenkins version, preferably a long
term support version (like 1.565.2) to see if that resolves the problem
you're seeing.

The git plugin and the git client plugin are intended to work with the
Jenkins version you're using.  They are dependent on the long term support
version 1.509.  However, that is a long time ago and there probably are not
many people still running 1.517.

Thanks,
Mark Waite


> On Wednesday, September 24, 2014 11:04:33 AM UTC-4, blaze...@gmail.com
> wrote:
>>
>> I added the Git Publish post build action to a project and there's no
>> delete. This is a problem instead of an annoyance because all it does by
>> default is "Build step 'Git Publisher' marked build as failure"
>> How do I remove the action?
>>
>>
>> Jenkins ver. 1.517 
>>
>  --
> 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.
>



-- 
Thanks!
Mark Waite

-- 
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: Building a specific commit with Gerrit

[Chanda Unmack]

On Mon, Sep 22, 2014 at 4:51 PM, Michael Vincent  wrote:

> I need to build every commit that gets submitted into a Gerrit repo
> (preferably in order).
>
> I have all the latest git/Gerrit plugins on the latest Jenkins 1.565.2
> LTS. Jenkins master is running on Linux and slave nodes are running on
> Windows 7 with msysgit-1.8.3. The Gerrit server is running 2.9.1.
>
> I've set up a job and set the Gerrit Trigger "Trigger on" field to "Ref
> Updated". The git plugin "Refspec" field is set to "$GERRIT_REFSPEC", the
> "Branches to build" field is set to "$GERRIT_NEWREV", and the "Choosing
> strategy" is set to "Gerrit Trigger".
>
> This works fine until multiple instances of this job get queued up, at
> which point it continues to just build the tip revision of the branch. This
> is particularly apparent if an older job is retriggered. Here's an example.
>
> The tip of "origin/master" is currently at 4d5f54f, but this job should
> be building 0af0a0f. Here are some of the Gerrit environment variables
> defined for the job:
>
> GERRIT_EVENT_TYPE ref-updated
> GERRIT_NEWREV 0af0a0fd5c533f258a18ea3bf72add14a3d43a3c
> GERRIT_OLDREV 57672ba6daa5674a561911706551e66b70a5c01a
> GERRIT_REFSPECrefs/heads/master
>
> and the log output:
>
> Fetching changes from the remote Git repository
>  > C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.url 
> ssh://gerrit/repo
> # timeout=10
> Fetching upstream changes from ssh://gerrit/repo
>  > C:\Program Files (x86)\Git\cmd\git.exe --version # timeout=10
> using GIT_SSH to set credentials id_dsa
>  > C:\Program Files (x86)\Git\cmd\git.exe fetch --tags --progress 
> ssh://gerrit/repo
> refs/heads/master
>
> *> C:\Program Files (x86)\Git\cmd\git.exe rev-parse "FETCH_HEAD^{commit}"
> # timeout=10Checking out Revision 4d5f54fe49ad4adbe8b494a9da3408f4206193a2
> (0af0a0fd5c533f258a18ea3bf72add14a3d43a3c)*
>  > C:\Program Files (x86)\Git\cmd\git.exe config core.sparsecheckout #
> timeout=10
>  *> C:\Program Files (x86)\Git\cmd\git.exe checkout -f
> 4d5f54fe49ad4adbe8b494a9da3408f4206193a2*
>  > C:\Program Files (x86)\Git\cmd\git.exe rev-parse "FETCH_HEAD^{commit}" #
> timeout=10
>  > C:\Program Files (x86)\Git\cmd\git.exe rev-list
> 0af0a0fd5c533f258a18ea3bf72add14a3d43a3c # timeout=10
>  > C:\Program Files (x86)\Git\cmd\git.exe remote # timeout=10
>  > C:\Program Files (x86)\Git\cmd\git.exe submodule init # timeout=10
>  > C:\Program Files (x86)\Git\cmd\git.exe submodule sync # timeout=10
>  > C:\Program Files (x86)\Git\cmd\git.exe config --get remote.origin.url #
> timeout=10
>  > C:\Program Files (x86)\Git\cmd\git.exe submodule update --init --
> recursive
>
> It looks like the Gerrit Trigger choosing strategy is checking out
> FETCH_HEAD even though I told it to check out "$GERRIT_NEWREV". I can
> work around this fairly easily by adding a "git checkout --force
> $GERRIT_NEWREV" command to the beginning of the build script, but it
> would be nice for the git/Gerrit plugins to handle this case. Is there
> something I should change in the job configuration or is this currently a
> plugin limitation?
>
> --
> 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.
>

Haven't had much of an issue with our setup in that regard, but we use
$GERRIT_BRANCH for the Branch Specifier. Haven't tried $GERRIT_NEWREV yet
(no time to experiment at the moment) so can't speak to the difference
there.

ymmv
chanda

-- 
*C**onfidentiality Notice:* This e-mail, including all attachments, is
confidential information of Lytro, Inc. If the reader of this e-mail is not
the intended recipient or its authorized agent, the reader is hereby
notified that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

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

Loadrunner Integration

[Connor Gilbert]

Hey Jenkins Users,

Currently I'm tasked with integrating our Loadrunner set up with Jenkins. 
Fair warning, I have no prior knowledge of Jenkins.

I found the HP Automation Tool 
 
which 
seems to be a rather simple solution into integrating Loadrunner.

The requirements of the tool state: 

   1. ALM/Quality Center client installed the machine that will run the 
   tests. To check if you have a client installed, follow the instructions on 
   this page:   http://:8080/qcbin/TDConnectivity_index.html


I'm not sure if I have ALM/Quality Center (Does it come with a Loadrunner 
install?).  Also I have zero idea how to begin installing this tool.

*Does anyone here have prior experience with this HP Automation Tool for 
Jenkins?*

As you can tell I'm a bit lost here. Any advice would be appreciated,

-Connor

-- 
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: Git Publish breaking build and un-deletable

[blaze . mkiv]

More info

Git Client Plugin 

Shared library plugin for other Git related Jenkins plugins.
1.10.21.0.7
Git Parameter Plugin 

This plugin allows you to choose between Git tags or sha1 of your SCM 
repository so Git Plugin installed is required.
Warning: This plugin is built for Jenkins 1.554.1 or newer. It may or may 
not work in your Jenkins.
0.3.20.2
Git Plugin 
This plugin allows use of Git  as a build SCM. A 
recent Git runtime is required (1.7.9 minimum, 1.8.x recommended). Plugin 
is only tested on official git client . Use exotic 
installations at your own risks.
2.2.61.4.0
On Wednesday, September 24, 2014 11:04:33 AM UTC-4, blaze...@gmail.com 
wrote:
>
> I added the Git Publish post build action to a project and there's no 
> delete. This is a problem instead of an annoyance because all it does by 
> default is "Build step 'Git Publisher' marked build as failure"
> How do I remove the action? 
>
>
> Jenkins ver. 1.517 
>

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

Git Publish breaking build and un-deletable

[blaze . mkiv]

I added the Git Publish post build action to a project and there's no 
delete. This is a problem instead of an annoyance because all it does by 
default is "Build step 'Git Publisher' marked build as failure"
How do I remove the action? 


Jenkins ver. 1.517 

-- 
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: locked out of Jenkins

[Ginga, Dick]

Well, I did recover. Our jenkins is on a windows machine and evidently there 
was another Jenkins process running that was not the service (??) don't know 
how that happens. There was also a second Java/Jenkins process issuing a cli 
command. Perhaps that kept the service process from terminating.

Anyway, I am back.

From: Ginga, Dick
Sent: Wednesday, September 24, 2014 9:28 AM
To: 'jenkinsci-users@googlegroups.com'
Subject: locked out of Jenkins
Importance: High

OK, I did it. I hit the wrong key and now everyone is locked out of jenkins, 
including me, I tried the below but it did not work.

Why would I "try renaming or deleting config,xml"? Won't I lose everything?



  1.  Stop Jenkins (the easiest way to do this is to kill the servlet 
container.)
  2.  Go to $JENKINS_HOME in the file system and find config.xml file.
  3.  Open this file in the editor.
  4.  Look for the true element in this file.
  5.  Replace true with false
  6.  Remove the elements authorizationStrategy and securityRealm
  7.  Start Jenkins
When Jenkins comes back, it's in the unsecured mode where everyone gets full 
access to the system.
If this is still not working, trying renaming or deleting config.xml.

Dick Ginga, Informatics R&D
PerkinElmer Inc. | For the Better
HUMAN HEALTH | ENVIRONMENTAL HEALTH
940 Winter Street, Waltham MA 02451

dick.gi...@perkinelmer.com
Mobile - 508-847-1434
Office - 781-663-6947

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

locked out of Jenkins

[Ginga, Dick]

OK, I did it. I hit the wrong key and now everyone is locked out of jenkins, 
including me, I tried the below but it did not work.

Why would I "try renaming or deleting config,xml"? Won't I lose everything?



  1.  Stop Jenkins (the easiest way to do this is to kill the servlet 
container.)
  2.  Go to $JENKINS_HOME in the file system and find config.xml file.
  3.  Open this file in the editor.
  4.  Look for the true element in this file.
  5.  Replace true with false
  6.  Remove the elements authorizationStrategy and securityRealm
  7.  Start Jenkins
When Jenkins comes back, it's in the unsecured mode where everyone gets full 
access to the system.
If this is still not working, trying renaming or deleting config.xml.

Dick Ginga, Informatics R&D
PerkinElmer Inc. | For the Better
HUMAN HEALTH | ENVIRONMENTAL HEALTH
940 Winter Street, Waltham MA 02451

dick.gi...@perkinelmer.com
Mobile - 508-847-1434
Office - 781-663-6947


-- 
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: how to propagate build number from parent job to child job ?

[Ginga, Dick]

I don’t think you can change the actual build number of a job programmatically 
but what I do is set the Display name of the later jobs. Pass into the later 
jobs the ${BUILD_NUMBER} of the first. There are a number of ways to set a 
builds display number: use the Version Number plugin, in a Build flow job, use 
setDisplayName on the build object, there is a CLI.,,,

You can manually set the build number “higher” with the Next Build Number 
plugin.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of mpc8250
Sent: Tuesday, September 23, 2014 6:11 PM
To: jenkinsci-users@googlegroups.com
Subject: how to propagate build number from parent job to child job ?

Hi All

We have 3 jobs chained linearly.
We like all 3 jobs to use the same build number using the topmost build number.
However right now, if any of the latter jobs fail and restarted the next time, 
they use their own build number in the job and not the topmost build number.

How do we accomplish that ?


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

-- 
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: Unable to determine where the build failed

[Kiro jnr]

Hi cchen,

Did you managed to resolve this issue. I am currently experiencing same 
issue.

Regards 

Ahmed

On Thursday, June 28, 2012 10:16:28 PM UTC+1, cchen wrote:
>
> Hey folks,
>
> Using jenkins to build a scala project via maven, and I am having trouble 
> to determine how builds are failing at times.  Sometimes, there is no 
> compile error, no test failure and everything seemed to succeed, but 
> jenkins says it failed.
>
> So I am hoping to understand how Jenkins determine a build has failed, as 
> well as the best practices that you use.
>
> Thanks,
>
> 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.