Re: Testopia jenkins integration

['Bruno P. Kinoshita' via Jenkins Developers]

Sorry Ankush, haven't had time to take a look yet. I still have a working 
Bugzilla/Testopia + Jenkins environment in my computer, so it mustn't be very 
hard to debug it later. My guess is that your key custom field is 
missing/wrong, or the unit result file generated is different than expected by 
the plug-in.
Could you please file an issue with the information you provided here in the 
mailing list, please? Feel free to ping me there if I take too long to take a 
look on it. Probably will do after holidays.
Thanks!Bruno
 
  From: Ankush Aggarwal 
 To: jenkinsci-dev@googlegroups.com 
 Sent: Monday, December 15, 2014 2:53 AM
 Subject: Re: Testopia jenkins integration
   
Hi Bruno,
Did you get a chance to check it.
Thanks,Ankush

On Thursday, 27 November 2014 16:23:12 UTC+5:30, Ankush Aggarwal wrote:
Hi All,
I am integrating Testopia with Jenkins, 
Download very simple java app from internet having test cases.Jenkins 
authentication with testopia is working fine.Created test Plan, test run, test 
case in TestopiaAttached both jenkins and testopia conf details.
jenkins is not able found test results and not able to update testopia.  Anyone 
please help me on this.
Testing.sh :-cd target/test-classes/usr/java/jdk1.7.0_71/bin/java -cp 
".:/var/lib/jenkins/jobs/App/ target/classes/*:/var/lib/ 
jenkins/jobs/App/junit-4.11. jar:/var/lib/jenkins/jobs/App/ 
hamcrest-core-1.3.jar"  org.junit.runner.JUnitCore com.mkyong.core.TestApp1


[INFO] -- -- 

[INFO] BUILD SUCCESS
[INFO] -- -- 

[INFO] Total time: 3.574 s
[INFO] Finished at: 2014-11-21T02:17:54-05:00
[INFO] Final Memory: 9M/57M
[INFO] -- -- 

Build step 'Invoke Maven 3' changed build result to SUCCESS
Connecting to Testopia to retrieve automated test cases
Preparing Testopia connection properties
Executing single build steps
[App] $ /bin/sh -xe /tmp/ hudson2693326793877533844.sh
+ ./testing.sh
JUnit version 4.11
.
Time: 0.007

OK (1 test)

Executing iterative build steps
Seeking test results
Found 0 test results
Finished: SUCCESS
-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/705c1916-5b69-4f6c-9ee2-90b8389da38c%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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1924379476.137250.1418692440244.JavaMail.yahoo%40jws10798.mail.gq1.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

How to set/reset a Build Environment section check box for every job programmatically ?

[Manoj Thakkar]

hi,

I am looking for a groovy/java way of making a checkbox true for every job 
 under Build Environments Section,

e.g  : For all jobs in my jenkins I want to mark the checkbox which says "Abort 
the build if it's stuck"  ,

I tried with getting environments or parameters looks like none of these 
have this 

Please advise of a good way of doing this ,

Thanks
Manoj

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8f4282a2-4378-4f2c-8d72-6ff200b49da9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Flyer 2015‏

[FredG]

Hi Jyrki,

A "What's new/Highlights" section would definitely be nice. As space is 
limited on the flyers, what should we get rid of? I guess, "Easy to extend" 
and "Jenkins hosting" are the most dispensable sections?!

@kohsuke/@rtyler: *Do we even need the flyers?* Most people at FOSDEM only 
want the stickers and would love to buy other merchandise (t-shirts, pins, 
etc.).

Regards,

Fred

On Wednesday, December 10, 2014 5:00:33 PM UTC+1, jyrki wrote:
>
> Hi,
>
> Some kind of "What's new/Highlights of the year/something" might be nice. 
> Jenkins is already pretty well known, and someone would even say old, so it 
> would be great to show that big things are still happening all the time.
>
> IMHO, the Workflow -plugin would be one of the "big things" that has 
> happened since last FOSDEM.
>
> - Jyrki
> ps.
> I'm reading those lists, just didn't have any ideas then.
>
> On Wed Dec 10 2014 at 5:26:53 PM FredG  > wrote:
>
>> Hi,
>>
>> Sorry for posting this here, but (once again) I did not get any replies
>> on the appropriate mailing lists (jenkins...@lists.jenkins-ci.org 
>> , eve...@lists.jenkins-ci.org ).
>> Does anyone actually still read those lists??
>>
>> -
>>
>> FOSDEM 2015 is only two months away and I won't have time to print the
>> flyers in January. Therefore I'd like to get the discussion started
>> about next year's flyer (see last year's flyer:
>> https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Flyer) so I can get
>> them printed before christmas.
>>  
>> What should be updated/changed/removed/left as is, etc?
>>  
>> I'm planning to (again) update the number of installations,
>> contributors, and plugins.
>> These are the numbers that I found:
>> -around 98000 installations (according to
>> http://stats.jenkins-ci.org/jenkins-stats/svg/total-jenkins.svg)
>> -638 Contributors (Members in https://github.com/jenkinsci)
>> -1000+ Plugins (according to
>> http://stats.jenkins-ci.org/jenkins-stats/jenkinsgraph.html)
>> Are these numbers reliable or did I miss anything?
>>  
>> How many flyers should I order?
>>  
>> Regards,
>>  
>> Fred
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/517d77bf-3b27-418b-bc1d-811c42be753a%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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/624a733d-6f77-426a-988c-dd93367c23bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

What is the name of download directory for config-file-provider plugin?

[Horton, Anne B]

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/966F9D10AEE55B4592FAD1487ABFF19A243271B1%40HVXDSP23.us.lmco.com.
For more options, visit https://groups.google.com/d/optout.

RE: Plugin only works when run from Maven

[Anthony DeMartini]

Just a gentle nudge, has anyone seen anything like this before?

From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of Anthony DeMartini
Sent: Wednesday, December 10, 2014 12:41 PM
To: jenkinsci-dev@googlegroups.com
Subject: RE: Plugin only works when run from Maven

I see the render HTTP request going out when adding the post build action but 
the response doesn’t have any data.  I do see all of the Jelly files in the 
packaged build, so I’m pretty stumped.

Is there some way of turning on an uber-logging mode to show what may be 
happening?

The only messages I see in the logs worth mentioning are the ones complaining 
about DNS errors shown below, but I still think these are not relevant.

Anthony

From: jenkinsci-dev@googlegroups.com 
[mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Anthony DeMartini
Sent: Tuesday, December 09, 2014 1:48 PM
To: jenkinsci-dev@googlegroups.com
Subject: RE: Plugin only works when run from Maven

Ryan,

Thanks for the response.  Yes, the HPI file does contain the config.jelly file 
for the publisher.  The only errors I see in the logs are related to DNS, such 
as this one:

Dec 09, 2014 1:39:57 PM javax.jmdns.impl.DNSIncoming readAnswer
WARNING: There was an OPT answer. Not currently handled. Option code: 65002 
data: 2DC591555FDEBD1A

Or this one:

SEVERE: bad domain name: possible circular name detected. Bad offset: 
0x at 0x1ab
Dec 09, 2014 10:16:47 AM javax.jmdns.impl.constants.DNSRecordType typeForIndex


I don’t believe these kinds of errors are related, since other plugins work 
fine.  This is the plugin:

https://github.com/jenkinsci/codedx-plugin

https://wiki.jenkins-ci.org/display/JENKINS/Code+Dx+Plugin


Kind Regards,

Anthony

From: jenkinsci-dev@googlegroups.com 
[mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Ryan Campbell
Sent: Tuesday, December 09, 2014 1:34 PM
To: jenkinsci-dev@googlegroups.com
Subject: Re: Plugin only works when run from Maven

What do the logs say? Does the hpi's jar contain the views. I've never seen 
this.
On Tue, Dec 9, 2014, 12:05 PM Anthony DeMartini 
mailto:anthony.demart...@avi.com>> wrote:
Hello,

We are having a strange issue with our Jenkins plugin.  In the development 
environment (running using mvn), the plugin works perfectly fine.  But when we 
install the plugin (using marketplace or hpi file) to seemingly any version of 
Jenkins, it is totally broken.  Our post-build action (publisher) registers but 
our configuration form is completely blank.  It only shows the delete button to 
remove the action.  What could be different about running from maven (hpi:run) 
vs installing from the marketplace or hpi file?

Kind Regards,

Anthony
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/DM2PR0801MB0794E5F5E26996B4D07CA8ACEB650%40DM2PR0801MB0794.namprd08.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANHK%3DJ1EsvcvPwMTKvESTRKicunzwjaiEhg63CEmm5OBHMSVdw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/DM2PR0801MB07943A95EA15C60053B5FB7CEB650%40DM2PR0801MB0794.namprd08.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
"Jen

Need some help dereferencing parameters in a buildstep-plugin.

[Dennis Jacobs]

Hi Guys,

I'm in bit of a jam.
I've written a plugin which takes in a string/xml-struct which contains 
variables. Like the following.
${BOARDNAME}${VERSIONHEAD}${FULLVERSION}

These variables are setup by the parameterized plugin, i've tested this by 
creating a shell script build-step which calls `echo $BOARDNAME`
And this works, the variables show the actual values!
However if I pass this string to my plugin, it seems that the variables 
aren't dereferenced.
I'm getting the same string as the one above, while i expected a string in 
the format like this.
board_name11.11.111.11.1-00100

So my question is how can I dereference these variables properly, without 
losing the generic-ness of the plugin.
Since i want the plugin to remain generic, in the sense that others can use 
other variables for their projects depending their needs.

Am i missing some vital part of the jenkins-framework, which is able to do 
this?
Or am i one of the first who could use/need this functionality?

With kind regards,
Jacobs Dennis.


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/87a02725-3cfb-4769-ab43-18c02d5fe022%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Thread issue

[ketan . mehta]

Hi,

I'm facing an issue while Jenkins.
I'm using Jenkins on windows 2008 server to bootstrap newly created VM via
Jenkins job. unfortunately it breaks after rendering, here is the bootstrap
command.

c:\opscode\chefdk\bin\knife.bat bootstrap windows winrm 10.166.144.44 -x
administrator -P password -N TestVm1 --bootstrap-version 11

Here is the output of the Jenkins.

Waiting for remote response before bootstrap.10.166.144.44 .
10.166.144.44 Response received.
Remote node responded after 0.03 minutes.
Bootstrapping Chef on 10.166.144.44
10.166.144.44 "Rendering "C:\Users\ADMINI~1\AppData\
Local\Temp\bootstrap-1224-1
418386804.bat" chunk 1"
10.166.144.44 "Rendering "C:\Users\ADMINI~1\AppData\
Local\Temp\bootstrap-1224-1
418386804.bat" chunk 2"
10.166.144.44 "Rendering "C:\Users\ADMINI~1\AppData\
Local\Temp\bootstrap-1224-1
418386804.bat" chunk 3"
10.166.144.44 "Rendering "C:\Users\ADMINI~1\AppData\
Local\Temp\bootstrap-1224-1
418386804.bat" chunk 4"
10.166.144.44 "Rendering "C:\Users\ADMINI~1\AppData\
Local\Temp\bootstrap-1224-1
418386804.bat" chunk 5"
ERROR: ThreadError: can't create Thread (22)
+ CategoryInfo  : NotSpecified: (ERROR: ThreadEr...ate Thread 
(22)
   :String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError

ERROR: The object you are looking for could not be found
Response: node 'TestVM1' not found
ERROR: The object you are looking for could not be found
Response: node 'TestVM1' not found

Same commands works fine if i run it on powershell command line.
It seems the jenkins is not allowing to create more than 5 threads.
Am i doing something wrong? Please advice.

Thanks,
Ketan

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a911e49f-f9a6-440a-b1c8-811cf244ee37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Credential description with Templates for Enterprise Jenkins

[pallen]

Hi,

I had an issue raised on the P4 plugin: 
https://issues.jenkins-ci.org/browse/JENKINS-25682

I don't know about Jenkins Enterprise or the Template plugin, but it seems 
that the Description is lost when listing Perforce Credentials (an 
extension of the Credential plugin).  It may be as simple as I just need to 
implement a getName() method or something, but I have no way of testing 
this.  

Any clues as to how I might fix this or test my changes?

Kind regards,
Paul

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2528aeb9-c6ca-46a4-adce-6634ac9abdba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automatic release and update of plugin documentation

[Daniel Spilker]

For the Job DSL Plugin [1] we use the Conflunce wiki page only for a 
summary and some basic information. For all other documentation we point to 
the GitHub wiki [2]. The wiki content is kept in the repo [3], so 
contributors can/must update the docs as part of a pull request. To update 
the wiki we use the ghpages Gradle plugin [4], which can be configured to 
update the wiki [5].

So far users seem to find the relevant docs and there have been no 
complaints. Merging/rebasing the docs has not been more or less painful 
than merging code.

Daniel

[1] https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin
[2] https://github.com/jenkinsci/job-dsl-plugin/wiki
[3] https://github.com/jenkinsci/job-dsl-plugin/tree/master/docs
[4] 
https://github.com/ajoberstar/gradle-git/wiki/org.ajoberstar.github-pages
[5] 
https://github.com/jenkinsci/job-dsl-plugin/blob/master/build.gradle#L139

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c97c4487-0e94-4ef2-bca9-2ee0c05456ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

xcode-plugin and re-locking keychains

[Jerome Lacoste]

Hello,

I am making a pass at the xcode-plugin these days. I am going through the 
pull requests and issues and trying to put a bit of order in the plugin.

One particular issue is the management of keychains, which can be done in 
different ways.

Right now we have:
1. global keychains
2. job keychains
3. developerProfile loading (into custom keychains)

I really like the developerProfile one. They fit well in the jenkins 
credentials mechanism.


One issue with keychains are that they need to be unlocked / relocked. 
Right now there are several pull requests 
(https://github.com/jenkinsci/xcode-plugin/pull/47, 
https://github.com/jenkinsci/xcode-plugin/pull/49) 
that want to provide a way for the user to specify a lock timeout (or 
remove it altogether). Which can be problematic if the user specifies a too 
short timeout.

A better way IMHO would be to relock automatically the keychain once not 
needed (at least for those we know aren't shared simultaneously by multiple 
jobs). That really sounds like a BuildWrapper to me.

Koshuke, is this what you had in mind when adding the:
* TODO: destroy identity in the end.
https://github.com/jenkinsci/xcode-plugin/blob/master/src/main/java/au/com/rayh/DeveloperProfileLoader.java#L33

Has anyone tip on how could this be implemented in a nice way ? (I looked a 
bit at the Lock and Latches plugin).



Another issue is that the global and job keychain mechanisms have several 
issues:
* they store passwords in plaintext. So that's not good.
* also their they require configuration to be done before hand on all 
machines. Not practical for slaves setup
* finally I suspect that the granularity of only having global or job 
keychains make them not very useful in the case of having servers with 
compartmented teams

And there are probably other problems I don't know of. I am almost in favor 
of deprecating this mechanism and not supporting them anymore and let 
people use custom scripts to extend this functionality instead. Any 
feedback on this idea ?


Thanks,

Jerome

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1b707e7b-5ec9-4a96-9f05-d2dc5985aa11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automatic release and update of plugin documentation

[Daniel Beck]

What's wrong with keeping an entry called 'Upcoming changes' or '2.4 
(unreleased)' up to date? It gives users an opportunity to review and provide 
feedback on upcoming changes since they're more visible. Then just switch the 
headline when you release, and you're good.

Putting the files in the repository has at least the problem that stable/bugfix 
branches (e.g. Subversion Plugin 2.4.x, Git Plugin 2.2.x, Maven Plugin 2.0.x), 
wouldn't work well with it AFAICT.


Damien Nozay, contributor to Promoted Builds, may be interested in this as 
well, as he implemented something related for that plugin as well. Discussion 
(much of which does not apply here though):
https://github.com/jenkinsci/promoted-builds-plugin/pull/54

On 15.12.2014, at 08:33, Bue Petersen  wrote:

> Hi
> 
> I have a suggestion or an idea
> 
> I'm tired of the situation where I'm releasing a plugin, and then have to 
> update the plugin wiki page  "just" after. There is always a bit of time-lack 
> where the new plugin release and the wiki isn't matching.
> Quite often it is not a big problem, as the plugin wiki page isn't changed 
> much - but stil...
> It would have been better to update it as we made decisions during 
> development and so on.
> 
> How do you do it?
> 
> I would like that we update the plugin wiki page during development (when 
> relevant), but first release it when the plugin is released.
> Further I would much rather maintain the wiki page in markdown than in 
> Confluence.
> 
> So my idea is to write the plugin wiki page in markdown (or maybe just 
> Confluence mark-up or what-ever), put this/these markdown files in the plugin 
> repository and upon release generate html/Confluence wiki mark-up and publish 
> it.
> Confluence have an API for posting pages, but I think it requires some kind 
> of configuration on the server?
> 
> Any thoughts on this? Are we the only one that would like this setup? I 
> couldn't find anything on this topic related to plugin development.
> 
> Best regards,
> Bue Petersen
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAJB%2BB4VWDzFNszUiVzdrfi1hpe%3D4iC%2B3tvikizmSyv2ZNRFK4Q%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CB57535B-07AF-417F-AEAE-01A99B25C34D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.