date:20130115















































alexlombardi
 commented on  JENKINS-16346


Upgrade to Jenkins ver. 1.499 breaks master/slave connection















I was able to overcome this issue by giving the Anonymous user connection privilides in the Configure Global Security tab, then restarting the system. It's a terrible kludge, and I am hoping they find a way to make this unnecessary going forward.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16346) Upgrade to Jenkins ver. 1.499 breaks master/slave connection

2013-01-15 Thread s.sog...@gmail.com (JIRA)















































sogabe
 commented on  JENKINS-16346


Upgrade to Jenkins ver. 1.499 breaks master/slave connection















use -jnlpCredentials username:password option.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16319) Failure to delete old config files during rekeying on Windows

2013-01-15 Thread vasilena.tren...@softwareag.com (JIRA)

alexlombardi
commented on JENKINS-16319

Failure to delete old config files during rekeying on Windows

I am seeing an even bigger problem with this issue. I have Jenkins running on several 2k3 servers as window services. After my original upgrade to 1.499 (from 1.489), I was unable to get jenkins to recognize/start any of the slaves which all where running as windows services. There is a bug report already for this issue: https://issues.jenkins-ci.org/browse/JENKINS-16346.

I had unfortunately started the re-keying process already when it became necessary to revert to the older version of Jenkins to get things back up and running. The revert worked fine, and I was able to trouble shoot the issue on a different machine. The answer seemed to be to give Anonymous users conenction capability in the Global Security settings in the Project-based Matrix Authorization Strategy for a system using AD.

I re-upgraded my main system to 1.499, applied the security setting, got my slaves running, triggered the re-keying process, and was on my marry way. However, once that completed, any attempt to view the log created results in Jenkins crashing and the windows service it runs on being terminated. I manually looked at the log files and see many of the failed conversion steps as mentioned in this bug report.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16346) Upgrade to Jenkins ver. 1.499 breaks master/slave connection















































Vassilena Treneva
 commented on  JENKINS-16346


Upgrade to Jenkins ver. 1.499 breaks master/slave connection















I will try both options now but will hold off that version for the moment 

If I have to explicitly pass -jnlpCredentials username:password then I guess Jenkins needs to generate the proper command line when configuring the slaves. I mean  those:
Run from slave command line:

javaws http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp
Or if the slave is headless:

java -jar slave.jar -jnlpUrl http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp

We have quite a lot of slaves and it will take a while to go tru all of them for reconfiguration 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16319) Failure to delete old config files during rekeying on Windows

2013-01-15 Thread roman.harm...@gmail.com (JIRA)















































Roman Harmata
 commented on  JENKINS-16319


Failure to delete old config files during rekeying on Windows















It repeats same error all the time, even after granting RW rights for every standard user to whole folder Jenkins in "Program Files":
ERROR: Failed to rewrite C:\Program Files\Jenkins\jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml
java.io.IOException: Unable to delete C:\Program Files\Jenkins\jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml
	at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112)
	at hudson.util.SecretRewriter.rewrite(SecretRewriter.java:121)
	at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:170)
	at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:143)
	at jenkins.security.RekeySecretAdminMonitor$RekeyThread.run(RekeySecretAdminMonitor.java:182)

For me it seems, that this rekey is made to search for any XML file in jenkins subfolders. Is it problem if it tries to rekey this xml? I am thinking that it is maybe not necessary for some XMLs... And in this case I can probably assume, that rekey is successful. Can somebody confirm my assumption?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL

2013-01-15 Thread klaus.azesber...@gmail.com (JIRA)















































Klaus Azesberger
 commented on  JENKINS-10628


SCM build trigger not working correctly with variables in SVN URL















due to my automated formatting the change set caused a lot of conflicts and reduced visibility of the actually small change set, so my pull request got closed.
-> i rebased the changeset without the formatting-mess. it should be possible to integrate this fixes now.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16347) No images served to Anonymous users















































Dave Abrahams
 created  JENKINS-16347


No images served to Anonymous users















Issue Type:


Bug



Affects Versions:


current



Assignee:


Michael O'Cleirigh



Components:


github-oauth



Created:


15/Jan/13 2:54 PM



Description:


At http://jenkins.boost.org we have "Grant READ permissions for Anonymous Users" enabled, yet no images are served unless you're logged in.  See for yourself.




Environment:


Ubuntu 12.04




Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


Dave Abrahams

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification















































Sergey Grigoriev
 updated  JENKINS-16332


Leading and trailing underscores are added to commiters email address, unable to send build notification
















Change By:


Sergey Grigoriev
(15/Jan/13 2:58 PM)




Priority:


Blocker
Major



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification















































Sergey Grigoriev
 commented on  JENKINS-16332


Leading and trailing underscores are added to commiters email address, unable to send build notification















The problem has dissolved after  'sudo service jenkins restart'. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification













































  
Sergey Grigoriev
 edited a comment on  JENKINS-16332


Leading and trailing underscores are added to commiters email address, unable to send build notification
















The problem has gone after  'sudo service jenkins restart'. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16348) If SVN repository path has leading whitespace scm-sync-configration doesn't work and doesn't give errors

2013-01-15 Thread juha.syrj...@gmail.com (JIRA)















































Juha Syrjälä
 created  JENKINS-16348


If SVN repository path has leading whitespace scm-sync-configration doesn't work and doesn't give errors















Issue Type:


Bug



Assignee:


Frédéric Camblor



Components:


scm-sync-configuration



Created:


15/Jan/13 3:10 PM



Description:


If I configure SVN  repository path for scm-sync-configuration plugin with leading space, the plugin doesn't work or give any errors. UI validator for the field accepts this input.

The repo path is stored to scm-sync-configuration.xml as   scm:svn: http://my-server/svn/path.




Project:


Jenkins



Priority:


Minor



Reporter:


Juha Syrjälä

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16347) No images served to Anonymous users















































Dave Abrahams
 updated  JENKINS-16347


No images served to Anonymous users
















Change By:


Dave Abrahams
(15/Jan/13 3:19 PM)




Attachment:


noimage.png



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16349) People view aborts and returns nothing















































alexlombardi
 created  JENKINS-16349


People view aborts and returns nothing















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


Thread Dump 1-15-2013.doc



Components:


people-redirector



Created:


15/Jan/13 3:19 PM



Description:


Every attempt to bring up the people view results in an aborted process and nothing is returned.

Thread dump included.




Environment:


Running Jenkins on several 2k3 servers with master/slave setup using windows services. AD security setup matrix authorization.




Project:


Jenkins



Priority:


Major



Reporter:


alexlombardi

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16347) No images served to Anonymous users















































Dave Abrahams
 commented on  JENKINS-16347


No images served to Anonymous users















Actually I have to turn off that option so that my visitors don't get confused.  At least, with it off, they'll be redirected to GitHub for authentication.  I'll attach a screenshot



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16350) "logout" link doesn't work

2013-01-15 Thread hendrik.mill...@tu-clausthal.de (JIRA)















































Dave Abrahams
 created  JENKINS-16350


"logout" link doesn't work















Issue Type:


Bug



Affects Versions:


current



Assignee:


Michael O'Cleirigh



Components:


github-oauth



Created:


15/Jan/13 3:30 PM



Description:


When the plugin is configured to allow READ permission for Authenticated, but not Anonymous, users, clicking "logout" has no effect.  You actually have to go to GitHub and log out there.




Environment:


Ubuntu 12.04




Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


Dave Abrahams

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session















































Hendrik Millner
 started work on  JENKINS-16278


"Remember me on this computer" does not work, cookie is not accepted in new session
















Change By:


Hendrik Millner
(15/Jan/13 3:40 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16123) Valgrind plugin does not work when providing multiple Executable Arguments for run.

2013-01-15 Thread aschn...@cse.unl.edu (JIRA)















































Tony Schneider
 commented on  JENKINS-16123


Valgrind plugin does not work when providing multiple Executable Arguments for run.















Would love to have this fixed.  I'm trying to integrate valgrind (and this plugin) with a project that uses multiple command line parameters, and needs them to run.  Unfortunately the bug is preventing me from doing so. Is there any reason why the arguments were quoted in the first place?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session

2013-01-15 Thread hendrik.mill...@tu-clausthal.de (JIRA)















































Hendrik Millner
 commented on  JENKINS-16278


"Remember me on this computer" does not work, cookie is not accepted in new session















commit a9aff088 [SECURITY-49] introduced a change in signature generation for the remember me token in jenkins/core/src/main/java/hudson/security/TokenBasedRememberMeServices2.java:
String expectedTokenSignature = MAC.mac(userDetails.getUsername() + ":" + tokenExpiryTime + ":" + "N/A" + ":" + getKey());

This code is used to VERIFY a cookie sent to Jenkins. The new verification process seems fine, but the change in code is NOT reflected in org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.class . loginSuccess, where remember me cookies are created and sent to the user. Here, the old signature generation is still being used:
String signatureValue = DigestUtils.md5Hex(username + ":" + expiryTime + ":" + password + ":" + key);

I suggest either @Overriding TokenBasedRememberMeServices.loginSuccess in /jenkins-core/src/main/java/hudson/security/TokenBasedRememberMeServices2.java as well to rely on TokenBasedRememberMeServices2.makeTokenSignature, or revert to the old md5 signature.

Any comments?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14051) A PollingLog would be helpful in setting up dosTrigger

2013-01-15 Thread roger.my...@draeger.com (JIRA)
















































Roger Myung
 closed  JENKINS-14051 as Won't Fix


A PollingLog would be helpful in setting up dosTrigger 
















no maintainer of this plugin





Change By:


Roger Myung
(15/Jan/13 4:00 PM)




Status:


In Progress
Closed





Resolution:


Won't Fix



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14053) Being able to read environment variables in dos-trigger would be helpful

2013-01-15 Thread roger.my...@draeger.com (JIRA)
















































Roger Myung
 closed  JENKINS-14053 as Fixed


Being able to read environment variables in dos-trigger would be helpful
















Closing issue. No maintainer of this plugin.





Change By:


Roger Myung
(15/Jan/13 4:00 PM)




Status:


In Progress
Closed





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14053) Being able to read environment variables in dos-trigger would be helpful

2013-01-15 Thread roger.my...@draeger.com (JIRA)















































Roger Myung
 commented on  JENKINS-14053


Being able to read environment variables in dos-trigger would be helpful















Didn't mean to mark it fixed, sorry.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12927) Changes doesn't trigger a build - "unknown revision"

2013-01-15 Thread lew...@gmail.com (JIRA)















































Lewis Pollard
 commented on  JENKINS-12927


Changes doesn't trigger a build - "unknown revision"















Seems to get confused not just over revs but branches too - e.g. if I have repo A with branch 'dev' and repo B with branch 'staging' it tries to pull on repo B 'dev' branch. Shame that this appears not to be active any more as it would have been perfect.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15594) CopyArtifact plugin cannot always copy artifacts

2013-01-15 Thread haris_sha...@hotmail.com (JIRA)

Haris Shahid
commented on JENKINS-15594

CopyArtifact plugin cannot always copy artifacts

I would like to add that I have also been experiencing this issue and after doing some extensive tinkering I think it has to do something with permissions. At first I tried giving the job from which the artifacts were to be copied all types of access (anonymous, full access, authenticated group access) anything I read and could come up with on my own I tried. But, the copy artifac plugin would still fail intermittently.

The solution I figured out is this; if the copy artifact plugin starts to fail just go to the view that lists the job from which artifacts are to be copied as long as the logged in user sees the job listing, once, the copy artifact plugin will not fail (to copy artifacts) ever again from that job. You do not even have to click on the job just be able to see it in a list in one of your views. I know this sounds strange but I assure you this fixes the problem. Currently I have created a view where I list all of the jobs from which artifacts are to be copied and I have made it my default view. So, now as soon as a user logs-in or hits the Jenkins homepage the first thing they will see is the list of jobs. I have not had a failure since.

Can someone please fix this?

Thanks.

[JIRA] (JENKINS-12012) "Atomatic upgrade" link is no longer available on Manage Jenkins Page

2013-01-15 Thread esch...@sumtotalsystems.com (JIRA)















































Ernst Schepp
 commented on  JENKINS-12012


"Atomatic upgrade" link is no longer available on Manage Jenkins Page















To get around the issue I had to:

	do the "Downgrade" option (Restore the previous version of Jenkins).
	then use the Automatic Upgrade option to a newer version.
Now the "Or Upgrade Automatically" button is again available.



You could close this issue now.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15594) CopyArtifact plugin cannot always copy artifacts

2013-01-15 Thread haris_sha...@hotmail.com (JIRA)

Haris Shahid
edited a comment on JENKINS-15594

CopyArtifact plugin cannot always copy artifacts

The solution I figured out is this; if the copy artifact plugin starts to fail just go to the view that lists the job from which artifacts are to be copied as long as the logged in user sees the job listing, once, the copy artifact plugin will not fail (to copy artifacts) ever again. You do not even have to click on the job just be able to see it in a list in one of your views. I know this sounds strange but I assure you this fixes the problem. Currently I have created a view where I list all of the jobs from which artifacts are to be copied and I have made it my default view. So, now as soon as a user logs-in or hits the Jenkins homepage the first thing they will see is the list of jobs. I have not had a failure since and I implemented this fix about 1.5 - 2 months ago.

Can someone please fix this?

Thanks.

[JIRA] (JENKINS-15594) CopyArtifact plugin cannot always copy artifacts

2013-01-15 Thread haris_sha...@hotmail.com (JIRA)

Haris Shahid
edited a comment on JENKINS-15594

CopyArtifact plugin cannot always copy artifacts

The solution I figured out is this; if the copy artifact plugin starts to fail just go to the view that lists the job from which artifacts are to be copied as long as the logged in user sees the job listing, once, the copy artifact plugin will not fail (to copy artifacts) ever again for the current session. You do not even have to click on the job just be able to see it in a list in one of your views. I know this sounds strange but I assure you this fixes the problem. Currently I have created a view where I list all of the jobs from which artifacts are to be copied and I have made it my default view. So, now as soon as a user logs-in or hits the Jenkins homepage the first thing they will see is the list of jobs. I have not had a failure since and I implemented this fix about 1.5 - 2 months ago.

Can someone please fix this?

Thanks.

[JIRA] (JENKINS-15594) CopyArtifact plugin cannot always copy artifacts

2013-01-15 Thread jswa...@alohaoi.com (JIRA)















































Jason Swager
 commented on  JENKINS-15594


CopyArtifact plugin cannot always copy artifacts















I don't think this is a case of permissions.  I think this is a case of the job/build lazy-load not yet loading the build in question.  Similar issues have been happening with Build URLs.  You can paste the URL of a build into a browser and Jenkins responds with a 404.  But if you go into Jenkins, locate the job, then drill down to the build, it always works.  Then pasting the URL will work.  



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16351) Modification to build status balls to be less distracting

2013-01-15 Thread andrewcmar...@msn.com (JIRA)

Andrew Martin
created JENKINS-16351

Modification to build status balls to be less distracting

Issue Type:

Patch

Affects Versions:

current

Assignee:

asgeirn

Attachments:

blue_anime.gif, blue_anime_proposed.gif, green_anime.gif, green_anime_proposed.gif, grey_anime.gif, grey_anime_proposed.gif, red_anime.gif, red_anime_proposed.gif, yellow_anime.gif, yellow_anime_proposed.gif

Components:

greenballs, status-view

Created:

15/Jan/13 5:11 PM

Description:

I find the flashing / blinking build status balls to be somewhat distracting. To quote ESR on the related subject of blinking text:

Blinking text makes it nearly impossible to pay attention to anything else on the page. It reduces 87% of all surfers to a helpless state of fixated brain-lock, much like that of a rabbit caught in the headlights of an oncoming semi. This is not good. If you abuse the blink tag, you deserve to be shot. Clue: if you use the blink tag, you're abusing it.

I have modified the build status balls to animate using a more subtle “glow”. I have written a plugin to support this, but I thought I’d first offer it up as a modification to the trunk.

Here’s a comparison of the current versus proposed graphics:

Current

Proposed

I’ve issued a github pull request that updates raw SVGs, support scripts, and compiled gifs/pngs. The pull request eliminates the requirement for having inkscape to build the status balls. It also adjusts the balls to fix a minor horizontal misalignment.

I also have prepared modifications to the greenballs-plugin to be consistent with this change, should it be accepted.

Fix Versions:

current

Project:

Jenkins

Labels:

ball
balls
flashing
blinking

Priority:

Minor

Reporter:

Andrew Martin

[JIRA] (JENKINS-16352) Cron TimerTrigger with parameters

2013-01-15 Thread flozz...@gmail.com (JIRA)















































Florin Hillebrand
 created  JENKINS-16352


Cron TimerTrigger with parameters















Issue Type:


Improvement



Assignee:


Unassigned


Components:


core



Created:


15/Jan/13 5:12 PM



Description:


I was missing the possibility to pass a parameter to a crontab line, so that I can do different things on different days.

e.g. 
We have a linux that is built every day except Saturdays (~1h) and on Sundays we run a clean build (~10h), where Saturday is reserved for other projects that run a clean build.
The only way for me was to create a conditional build step. It blows up the job configuration and gets decoupled from the crontab:
So when someone changes the crontab from Sunday to Saturday for clean builds, he will also have to change the day in the conditional build step.

My proposal is to extend the crontab syntax by something like:

MIN HOUR DOM MONTH DOW % PARAM1=VALUE1,PARAM2=VALUE2

This would than schedule a build with the given parameters.

Would others be interested too?




Project:


Jenkins



Labels:


TimerTrigger,
Parameter




Priority:


Minor



Reporter:


Florin Hillebrand

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type















































eguess74
 commented on  JENKINS-15774


Add ability to specify custom ivy settings file in global configuration for ivy job type















We have the ivy settings file located on NFS, so from every host it is the same path /home/users/blahblah/path/to/ivysettings.xml So i believe this should work.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16352) Add ability to specify parameters in the crontab

2013-01-15 Thread flozz...@gmail.com (JIRA)















































Florin Hillebrand
 updated  JENKINS-16352


Add ability to specify parameters in the crontab
















Change By:


Florin Hillebrand
(15/Jan/13 5:17 PM)




Summary:


Cron TimerTrigger with
Add ability to specify
 parameters
 in the crontab



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16353) Create REST-based JobManagement















































Andrew Harmel-Law
 created  JENKINS-16353


Create REST-based JobManagement















Issue Type:


Bug



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 5:46 PM



Description:


On top of that should be a Gradle plugin, to call this from Gradle.




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16354) Wrap DSL Script execution failures so it is clear to a user that this is the root of the failure

Andrew Harmel-Law
created JENKINS-16354

Wrap DSL Script execution failures so it is clear to a user that this is the root of the failure

Issue Type:

New Feature

Assignee:

Justin Ryan

Components:

job-dsl-plugin

Created:

15/Jan/13 5:50 PM

Description:

The exceptions from Groovy are good, but we should wrap them so they are topped with a "your script has something wrong in it" message to focus remedial attention.

Comments from the original github issue:
andrewharmellaw commented 9 months ago
I need to figure out how to write to the Jenkins job output console directly. Then we can control what is written here.

andrewharmellaw commented 9 months ago
http://javadoc.jenkins-ci.org/hudson/model/TaskListener.html is the thing to use. It only has "error" and "fatalError" methods, but it does seem to do what we need (i.e. write useful messages to a user to the Jenkins Console output). I'll code this in and take a look.

andrewharmellaw commented 9 months ago
listener.getLogger().print(...) is my friend...

quidryan commented 8 months ago
@claymccoy pointed out that we should show the script when printing an error message. I think we could also look at the stack to see what line number the error was in, and we can show line number when printing it out.

andrewharmellaw commented 8 months ago
Totally agree. I have half worked on this (but not the line number bit) but not checked it in. I'll take a look at how far you're got in my absence and see what the priority is - finish this or something else.

Project:

Jenkins

Priority:

Minor

Reporter:

Andrew Harmel-Law

[JIRA] (JENKINS-16355) Allow job() to be assignable and chainable















































Andrew Harmel-Law
 created  JENKINS-16355


Allow job() to be assignable and chainable















Issue Type:


New Feature



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 5:51 PM



Description:


Jenkins has the notion of chaining jobs. A convenience method which accepts other jobs to construct "Build after projects are built" or a trigger for other jobs would be slick.




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16356) In each Project, show templates being used















































Andrew Harmel-Law
 created  JENKINS-16356


In each Project, show templates being used















Issue Type:


New Feature



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 5:53 PM



Description:


Comments from original Github issue
 andrewharmellaw commented 8 months ago 
This would be ideal.




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16357) In each Generated Project, show the seed job that created it.















































Andrew Harmel-Law
 created  JENKINS-16357


In each Generated Project, show the seed job that created it.















Issue Type:


New Feature



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 5:54 PM



Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16358) In configuration, control if generated jobs should be deleted or disabled















































Andrew Harmel-Law
 created  JENKINS-16358


In configuration, control if generated jobs should be deleted or disabled















Issue Type:


New Feature



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 5:55 PM



Description:


It's very likely that jobs will become unreferenced, from the Seed job. Since the seed job is "in charge" of these generated jobs we need to take action when this happens. The Seed job currently disables , but it could ignore this case or delete the jobs. We'd need some checkbox or such on the configuration page to determine the behavior.

Comments from original Github Issue
andrewharmellaw commented 8 months ago 
Sounds sensible. The checkbox sounds like a plan as otherwise our users will get correct, but possibly unexpected behaviour. A good help text on the item should help here too.




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16360) Print DSL formatted config.xml for an existing Job















































Andrew Harmel-Law
 created  JENKINS-16360


Print DSL formatted config.xml for an existing Job















Issue Type:


New Feature



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 5:57 PM



Description:


Reading and translating the config.xml of a desired project isn't exactly easy. It'd be pretty straightforward to print the config.xml for a job in the DSL format. I'm thinking a button on the left of a Job, which registers itself as a URL (common Jenkins practice).

Comments from original Github Issue
andrewharmellaw commented 8 months ago 
Simple and easy and expected is good, at least for a starter. I'd go with this as you propose for R1




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16359) Enable CodeMirror support on configuration page















































Andrew Harmel-Law
 created  JENKINS-16359


Enable CodeMirror support on configuration page















Issue Type:


New Feature



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 5:56 PM



Description:


In src/main/resources/javaposse/jobdsl/plugin/ExecuteDslScripts/config.groovy, I was unable to figure out to get CodeMirror support working. CodeMirror turns the textarea() into a mini-IDE, with syntax highlighting and line numbers. This should be a drop in feature, but I couldn't figure it out.

Comments from original Github Issue
 andrewharmellaw commented 8 months ago 
If you / we can, it'll mean we can edit /on the Jenkins box right? This is superb, and removes the need (at least initially) to have some IDE support for script writing.




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16361) @Grab Grape support















































Andrew Harmel-Law
 created  JENKINS-16361


@Grab Grape support















Issue Type:


New Feature



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 5:59 PM



Description:


It's very possible that someone will want to bring in an external library, which we're unfamiliar with or just don't include. If they could add an @Grab to get it, it's add up a lot of functionality.

Comments / References from Original Github Issue
andrewharmellaw referenced this issue 8 months ago
Closed
Issue #18: Facilitate DSL Extensions

 andrewharmellaw commented 8 months ago 
Sounds great. This is anther way of looking at the issue I created (#18). This is more idiomatic than mine though. I'll close it.




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16362) Use XmlUnit to compare configs before saving















































Andrew Harmel-Law
 created  JENKINS-16362


Use XmlUnit to compare configs before saving















Issue Type:


New Feature



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 6:00 PM



Description:


I've seen our version of the config to be slightly different than jenkin's version, specifically around empty tags. Jenkins perfers and our printing prefers . XmlUnit can tell the difference between these, and we could prevent a save.

Comments / References from Original Github Issue
 andrewharmellaw commented 8 months ago 
Superb. Shouldn;t be too difficult either - XML unit has a very configurable approach to testing compliance which we can build on.

 quidryan commented 6 months ago 
I think this is done. I'll confirm later.




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16364) Support Build Flow plugin dsl inside job dsl















































Andrew Harmel-Law
 created  JENKINS-16364


Support Build Flow plugin dsl inside job dsl















Issue Type:


New Feature



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 6:03 PM



Description:


There's some obvious overlap, but they can also work together. I don't know how to capture their dsl as a inline string so that it can then be injected back into the config.xml.

Comments / References from Original Github Issue




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16363) Allow selection of job type















































Andrew Harmel-Law
 created  JENKINS-16363


Allow selection of job type















Issue Type:


Bug



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 6:02 PM



Description:


We currently only support free-form projects, we will need to support maven projects soon. I'm thinking like an attribute on job, or a different name, like maven { } instead of job { }


  
  
  false
  

  
  true
  false
  false
  false
  (Default)
  
  false
  Maven 2.2.1
  true
  false
  true
  false
  false
  false
  false
  -1
  false
  
  
  
  
  
  
  
  
FAILURE
2
RED
  


Comments / References from Original Github Issue




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15720) Deploy Artifacts to Maven Repository only resolves Repository ID against POM, not settings.xml

2013-01-15 Thread i...@sven-amann.de (JIRA)















































Sven Amann
 commented on  JENKINS-15720


Deploy Artifacts to Maven Repository only resolves Repository ID against POM, not settings.xml















There is no deploy war/ear to container component... how is it called?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16365) allPermissions should try to load Jenkins's list of permissions















































Andrew Harmel-Law
 created  JENKINS-16365


allPermissions should try to load Jenkins's list of permissions















Issue Type:


New Feature



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 6:05 PM



Description:


Some plugins as permissions, which means we can't safely add an arbitrary list of Permissions, since they might not exist on the actual Jenkins service. It's generally safe to add extras, but it'd be best to avoid. Not sure what to do when running from Gradle/client-side.

Comments / References from Original Github Issue




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
















































Jesse Glick
 resolved  JENKINS-9679 as Fixed


NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
















The authentication issue is unrelated: JENKINS-16273





Change By:


Jesse Glick
(15/Jan/13 6:07 PM)




Status:


Reopened
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16366) Git config block doesn't work as given in examples















































Andrew Harmel-Law
 created  JENKINS-16366


Git config block doesn't work as given in examples















Issue Type:


Bug



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 6:07 PM



Description:


Git examples with no config block work as expected but those with config blocks fail with something like this:

FATAL: No signature of method: script13580273698081251596450.git() is applicable for argument types: (java.lang.String, script13580273698081251596450$_run_closure1_closure2_closure3) values: [git://github.com/JavaPosseRoundup/job-dsl-plugin, ...]
Possible solutions: wait(), run(), getJm(), run(), grep(), find()

Comments / References from Original Github Issue




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-3734) Can't launch Windows slave via JNLP when Hudson authentication enabled
















































Jesse Glick
 resolved  JENKINS-3734 as Duplicate


Can't launch Windows slave via JNLP when Hudson authentication enabled
















I guess this can be closed now.





Change By:


Jesse Glick
(15/Jan/13 6:08 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16346) Upgrade to Jenkins ver. 1.499 breaks master/slave connection
















































Jesse Glick
 resolved  JENKINS-16346 as Duplicate


Upgrade to Jenkins ver. 1.499 breaks master/slave connection
















Duplicate I think. You need appropriate authentication to connect a slave using JNLP.





Change By:


Jesse Glick
(15/Jan/13 6:11 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16319) Failure to delete old config files during rekeying on Windows















































Jesse Glick
 commented on  JENKINS-16319


Failure to delete old config files during rekeying on Windows















@alexlombardi keep discussion about authentication in JENKINS-16273. This is about rekeying only. And BTW giving anonymous users slave connect permissions is insecure (unless your network or servlet container adds independent security layers).

@romanhar Jenkins will only attempt to rewrite a file if it found some changes to make, meaning that the existing file contained insecurely encrypted passwords, so yes I think this is a problem.

I suspect that the root cause here is code in core or plugins which opens input streams on config files and fails to promptly close them in a finally block. On Windows, an open InputStream holds a mandatory file lock until it is garbage collected.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16367) Add "repository browser" support to the SCMContext.svn() method















































Andrew Harmel-Law
 created  JENKINS-16367


Add "repository browser" support to the SCMContext.svn() method















Issue Type:


Bug



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


15/Jan/13 6:17 PM



Description:


Git examples with no config block work as expected but those with config blocks fail with something like this:

FATAL: No signature of method: script13580273698081251596450.git() is applicable for argument types: (java.lang.String, script13580273698081251596450$_run_closure1_closure2_closure3) values: [git://github.com/JavaPosseRoundup/job-dsl-plugin, ...]
Possible solutions: wait(), run(), getJm(), run(), grep(), find()

Comments / References from Original Github Issue




Project:


Jenkins



Priority:


Minor



Reporter:


Andrew Harmel-Law

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16367) Add "repository browser" support to the SCMContext.svn() method















































Andrew Harmel-Law
 updated  JENKINS-16367


Add "repository browser" support to the SCMContext.svn() method
















Change By:


Andrew Harmel-Law
(15/Jan/13 6:19 PM)




Issue Type:


Bug
Task





Assignee:


Justin Ryan
Andrew Harmel-Law





Description:


Git examples with no config block work as expected but those with config blocks fail with something like this:FATAL: No signature of method: script13580273698081251596450.git() is applicable
The Subversion Source Code management plugin
 for
 argument types: (java
 Jenkins allows you to specify the tool you use to browse your SVN repository
.
lang
  This adds a  section to your config
.
String, script13580273698081251596450$_run_closure1_closure2_closure3) values: [git://github
xml file
.
com/JavaPosseRoundup/job-dsl-plugin, ...]Possible solutions: wait(), run(), getJm(), run(), grep(), find()h2. Comments / References from Original Github Issue



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type

2013-01-15 Thread johno.crawf...@gmail.com (JIRA)















































Johno Crawford
 commented on  JENKINS-15774


Add ability to specify custom ivy settings file in global configuration for ivy job type















I still think it is a bit strange to have slave specific configuration in system configuration so I will see about changing it to read the file from master.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification















































Jesse Glick
 commented on  JENKINS-16332


Leading and trailing underscores are added to commiters email address, unable to send build notification















Hmm if even @sgr cannot reproduce after restarting Jenkins then it is unlikely I will be able to reproduce either.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-9142) "Add Build Step" button broken in job configure page















































Jesse Glick
 commented on  JENKINS-9142


"Add Build Step" button broken in job configure page















Anyone affected should look in their browser’s _javascript_ console for errors, as well as enabling bound object logging as Kohsuke described earlier.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16341) Memory leak in createJavaScriptProxy















































Jesse Glick
 commented on  JENKINS-16341


Memory leak in createJavaScriptProxy















JENKINS-9142 describes how to enable logging in bound objects.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16368) Hardcoded protocol in some links

2013-01-15 Thread vjura...@java.net (JIRA)















































vjuranek
 created  JENKINS-16368


Hardcoded protocol in some links















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


15/Jan/13 7:03 PM



Description:


Some links (e.g. in console output lnks "Building remotely on slaveXYZ") don't preserve protocol and have hardcoded HTTP even if the page is opened via HTTPS. This can be considered as a security risk (e.g. user doesn't notice change of the protocol and later on can open another console output with sensitive data and the data would be sent over unsecure HTTP in this case)




Project:


Jenkins



Priority:


Major



Reporter:


vjuranek

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16319) Failure to delete old config files during rekeying on Windows

2013-01-15 Thread damien.finc...@online.fr (JIRA)















































Damien Finck
 commented on  JENKINS-16319


Failure to delete old config files during rekeying on Windows















Hello,

I have the same problem on my Server and on my personal computer.

  [...]
  ERROR: Failed to rewrite C:\PIC\Jenkins\hudson.scm.CVSSCM.xml
  [...]

How I can fix this problem ?


Instance Jenkins of my Server
OS : Windows 2008r2 64 bits
Jenkins : 1.498

Instance Jenkins of my Personnal Computer
OS : Windows 7 64 bits
Jenkins : 1.498 and after update 1.499



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16342) asynchPeople very slow when using Gravatar & Subversion plugins















































SCM/JIRA link daemon
 commented on  JENKINS-16342


asynchPeople very slow when using Gravatar & Subversion plugins















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/View.java
http://jenkins-ci.org/commit/jenkins/c757e65431ad1aec9a3bebe81ac919577e51ac58
Log:
  JENKINS-16342 Improving responsiveness of asynchPeople when Gravatar plugin is in use.
This change does not necessarily improve total performance, since the avatar is still computed.
But (1) the computation is correctly done in the work thread, not in the HTTP response thread;
(2) the computation is done just once for a given User, which could reduce load when many AJAX checks are done.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
















































Sergey Grigoriev
 closed  JENKINS-16332 as Cannot Reproduce


Leading and trailing underscores are added to commiters email address, unable to send build notification
















Change By:


Sergey Grigoriev
(15/Jan/13 7:46 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
















































Sergey Grigoriev
 resolved  JENKINS-16332 as Cannot Reproduce


Leading and trailing underscores are added to commiters email address, unable to send build notification
















Cannot reproduce





Change By:


Sergey Grigoriev
(15/Jan/13 7:46 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16368) Hardcoded protocol in some links

2013-01-15 Thread vjura...@java.net (JIRA)















































vjuranek
 commented on  JENKINS-16368


Hardcoded protocol in some links















Fixed in https://github.com/jenkinsci/jenkins/commit/460e508155187918e8c0f4fd0bb66a99cfe78527



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16368) Hardcoded protocol in some links

2013-01-15 Thread vjura...@java.net (JIRA)
















































vjuranek
 resolved  JENKINS-16368 as Fixed


Hardcoded protocol in some links
















Change By:


vjuranek
(15/Jan/13 7:50 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but no clear way to pass API token















































alexlombardi
 commented on  JENKINS-16273


Slaves forbidden to request JNLP anonymously but no clear way to pass API token















@Pei-Tang Huang: "I have configured all of my Windows slave launching method from "Launch slave agents via Java Web Start" to "Let Jenkins control this Windows slave as a Windows service" to avoid this issue"

I tried this but kept getting error:

Connecting to JenkinsSlave1
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins
java.net.UnknownHostException: JenkinsSlave1
	at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
	at java.net.InetAddress$1.lookupAllHostAddr(Unknown Source)
	at java.net.InetAddress.getAddressFromNameService(Unknown Source)
	at java.net.InetAddress.getAllByName0(Unknown Source)
	at java.net.InetAddress.getAllByName(Unknown Source)
	at java.net.InetAddress.getAllByName(Unknown Source)
	at java.net.InetAddress.getByName(Unknown Source)
	at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:202)
	at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:204)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

Even though I have verified that's the correct slave/service name.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but no clear way to pass API token















































alexlombardi
 commented on  JENKINS-16273


Slaves forbidden to request JNLP anonymously but no clear way to pass API token















Download the slave-agent.jnlp to the directory where the jenkins-slave.exe is

How are you accomplishing this? When I trigger the URl I do not get any option to do a download and the agent immediately launches.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but no clear way to pass API token













































  
alexlombardi
 edited a comment on  JENKINS-16273


Slaves forbidden to request JNLP anonymously but no clear way to pass API token
















Download the slave-agent.jnlp to the directory where the jenkins-slave.exe is

How are you accomplishing this? When I trigger the URL I do not get any option to do a download and the agent immediately launches.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15440) Emailing users at the end of a failed build very slow for big Jenkins instance using subversion















































SCM/JIRA link daemon
 commented on  JENKINS-15440


Emailing users at the end of a failed build very slow for big Jenkins instance using subversion















Code changed in jenkins
User: Jesse Glick
Path:
 src/main/resources/hudson/scm/SubversionMailAddressResolverImpl/global.jelly
http://jenkins-ci.org/commit/subversion-plugin/d5f9fb5a4a30aeebb379c3214508ecf80c387382
Log:
  JENKINS-15440 Warning about using mail resolver rules.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16342) asynchPeople very slow when using Gravatar & Subversion plugins

2013-01-15 Thread hendrik.mill...@tu-clausthal.de (JIRA)















































Jesse Glick
 commented on  JENKINS-16342


asynchPeople very slow when using Gravatar & Subversion plugins















Some things remain to be done to make UserAvatarResolver consistently quick:


	SubversionMailAddressResolverImpl should probably be rewritten to perform its calculations in a long-running process and cache them. Or maybe this should just be deleted and the problem solved in a different way.
	UserGravatarResolver should be rewritten to never block the API call waiting on an HTTP response; should initiate these asynchronously.



And until then, or even afterwards in case other plugins will reintroduce similar bugs:


	May be better for asynchPeople to list all users in a first pass, then go back and resolve avatars in a second pass.
	HudsonPrivateSecurityRealm/index.jelly and similar pages should avoid asking for the avatar synchronously in the HTTP handling thread. Can use ProgressiveRendering or perform the avatar calculation in the URL handler for the  rather than when producing the page.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session
















































Hendrik Millner
 assigned  JENKINS-16278 to Hendrik Millner



"Remember me on this computer" does not work, cookie is not accepted in new session
















Change By:


Hendrik Millner
(15/Jan/13 8:21 PM)




Assignee:


Hendrik Millner



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16278) "Remember me on this computer" does not work, cookie is not accepted in new session















































Jesse Glick
 commented on  JENKINS-16278


"Remember me on this computer" does not work, cookie is not accepted in new session















https://github.com/jenkinsci/jenkins/pull/673



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16342) asynchPeople very slow when using Gravatar & Subversion plugins

2013-01-15 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-16342


asynchPeople very slow when using Gravatar & Subversion plugins















Integrated in  jenkins_main_trunk #2191
 JENKINS-16342 Improving responsiveness of asynchPeople when Gravatar plugin is in use. (Revision c757e65431ad1aec9a3bebe81ac919577e51ac58)

 Result = SUCCESS
Jesse Glick : c757e65431ad1aec9a3bebe81ac919577e51ac58
Files : 

	core/src/main/java/hudson/model/View.java
	changelog.html





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type

2013-01-15 Thread johannes.ohlemac...@googlemail.com (JIRA)















































eguess74
 commented on  JENKINS-15774


Add ability to specify custom ivy settings file in global configuration for ivy job type















I have locally rebased global-ivy-settings branch on top of the ivy-descriptor-env-fix as in includes master and assembled the plugin . Now the global settings seems to be working as i was able to compile a project with it, without the job based ivy settings. I couldn't verify it works for slave due to Jenkins-15779. Global Ant OPS are also very nice to have!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16123) Valgrind plugin does not work when providing multiple Executable Arguments for run.















































Johannes Ohlemacher
 started work on  JENKINS-16123


Valgrind plugin does not work when providing multiple Executable Arguments for run.
















Change By:


Johannes Ohlemacher
(15/Jan/13 9:10 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL















































SCM/JIRA link daemon
 commented on  JENKINS-13726


Github plugin should work with Github enterprise by allowing for overriding the github URL















Code changed in jenkins
User: Johno Crawford
Path:
 pom.xml
 src/main/java/com/cloudbees/jenkins/Credential.java
 src/main/java/com/cloudbees/jenkins/GitHubWebHook.java
 src/main/resources/com/cloudbees/jenkins/Credential/config.jelly
 src/main/resources/com/cloudbees/jenkins/Credential/help-apiUrl.html
 src/main/resources/com/cloudbees/jenkins/Credential/help-password.html
 src/main/resources/com/cloudbees/jenkins/Credential/help-username.html
http://jenkins-ci.org/commit/github-plugin/947f6e29dd44a982603435ab58852794c43710a9
Log:
  JENKINS-13726: Support for GitHub Enterprise.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL
















































SCM/JIRA link daemon
 resolved  JENKINS-13726 as Fixed


Github plugin should work with Github enterprise by allowing for overriding the github URL
















Change By:


SCM/JIRA link daemon
(15/Jan/13 9:12 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL

2013-01-15 Thread johannes.ohlemac...@googlemail.com (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-13726


Github plugin should work with Github enterprise by allowing for overriding the github URL















Code changed in jenkins
User: Johno Crawford
Path:
 pom.xml
 src/main/java/com/cloudbees/jenkins/Credential.java
 src/main/java/com/cloudbees/jenkins/GitHubWebHook.java
 src/main/resources/com/cloudbees/jenkins/Credential/config.jelly
 src/main/resources/com/cloudbees/jenkins/Credential/help-apiUrl.html
 src/main/resources/com/cloudbees/jenkins/Credential/help-password.html
 src/main/resources/com/cloudbees/jenkins/Credential/help-username.html
http://jenkins-ci.org/commit/github-plugin/59fbb3e6a919e01c111dd0ec7d577488fa0a3803
Log:
  Merge pull request #22 from johnou/enterprise

[FIXED JENKINS-13726] Github plugin should work with Github enterprise by allowing for overriding the github URL.


Compare: https://github.com/jenkinsci/github-plugin/compare/a0255d82c5ff...59fbb3e6a919




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16123) Valgrind plugin does not work when providing multiple Executable Arguments for run.















































Johannes Ohlemacher
 commented on  JENKINS-16123


Valgrind plugin does not work when providing multiple Executable Arguments for run.















there is no special reason for quoting the argument string, its just a bug 
I already fixed it and i will release a new version soon!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-16123) Valgrind plugin does not work when providing multiple Executable Arguments for run.

2013-01-15 Thread aschn...@cse.unl.edu (JIRA)















































Tony Schneider
 commented on  JENKINS-16123


Valgrind plugin does not work when providing multiple Executable Arguments for run.















Wow!  Excellent.  Thanks much!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used















































eguess74
 commented on  JENKINS-15779


Parsing ivy descriptors step fails on a slave when custom ivy settings file is used















On the master the build works fine. On the slave it fails with the exception below. Same code, same project, same settings:


 
...
Parsing Ivy Descriptor Files
ERROR: Failed to parse ivy.xml files
java.io.IOException  : Remote call on  failed
at hudson.remoting.Channel.call(Channel.java:673)
at hudson.FilePath.act(FilePath.java:939)
at hudson.ivy.IvyModuleSetBuild$RunnerImpl.parseIvyDescriptorFiles(IvyModuleSetBuild.java:523)  
at hudson.ivy.IvyModuleSetBuild$RunnerImpl.doRun(IvyModuleSetBuild.java:365)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:589)
at hudson.model.Run.execute(Run.java:1516) 
at hudson.model.Run.run(Run.java:1462)  
at hudson.ivy.IvyModuleSetBuild.run(IvyModuleSetBuild.java:281)  
at hudson.model.ResourceController.execute(ResourceController.java:88)  
at hudson.model.Executor.run(Executor.java:236)  
Caused by:java.lang.ExceptionInInitializerError
 at hudson.ivy.IvyModuleSetBuild$IvyXmlParser.getIvySettingsFile(IvyModuleSetBuild.java:893)
at hudson.ivy.IvyModuleSetBuild$IvyXmlParser.getIvy(IvyModuleSetBuild.java:829)  
at hudson.ivy.IvyModuleSetBuild$IvyXmlParser.call(IvyModuleSetBuild.java:778) 
at hudson.ivy.IvyModuleSetBuild$IvyXmlParser.call(IvyModuleSetBuild.java:741) 
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326) 
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 
at java.util.concurrent.FutureTask.run(FutureTask.java:138) 
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
at java.lang.Thread.run(Thread.java:662) 
Caused by:java.lang.NullPointerException
 at hudson.model.Descriptor.getConfigFile(Descriptor.java:786)
at hudson.model.Descriptor.load(Descriptor.java:774)
at hudson.ivy.IvyModuleSet$DescriptorImpl.(IvyModuleSet.java:769)
at hudson.ivy.IvyModuleSet.(IvyModuleSet.java:757) 
... 13 more 

 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12012) "Atomatic upgrade" link is no longer available on Manage Jenkins Page

2013-01-15 Thread ever...@free.fr (JIRA)
















































evernat
 resolved  JENKINS-12012 as Fixed


"Atomatic upgrade" link is no longer available on Manage Jenkins Page
















ok, thanks





Change By:


evernat
(15/Jan/13 9:37 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used