[JIRA] [core] (JENKINS-23665) Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password

2014-09-09 Thread tschlab...@gmx.net (JIRA) 














































Torsten Schlabach
 commented on  JENKINS-23665


Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password















There were already some people asking on the dev mailing list for some attention on this, but no luck there either.
Any further hints welcome.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-24637) Git connection to Stash fails for ssh w/ publickey

2014-09-09 Thread andy.rudd...@rainydayz.org (JIRA) 














































Andy Ruddock
 created  JENKINS-24637


Git connection to Stash fails for ssh w/ publickey















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git



Created:


09/Sep/14 7:55 AM



Description:


Projects are stored in stash and accessed via ssh.

When editing the project I get red text ;
Failed to connect to repository : Command "git ls-remote -h ssh://g...@stash.rainydayz.org:7999/hi/helloworld.git HEAD" returned status code 128:
stdout:
stderr: Permission denied (publickey).
fatal: The remote end hung up unexpectedly

The selected user has password protected credentials added.

When I first created this project it worked fine, but there have been a number of updates over the past week or so during which time the project wasn't run. I know it worked on whatever version was in the repositories on 1st September.

Trying to build the project, I get the following :

Started by user Administrator
Building in workspace /var/lib/jenkins/jobs/HelloWorld/workspace
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url ssh://g...@stash.rainydayz.org:7999/hi/helloworld.git # timeout=10
Fetching upstream changes from ssh://g...@stash.rainydayz.org:7999/hi/helloworld.git
 > git --version # timeout=10
using GIT_SSH to set credentials jenkins
 > git fetch --tags --progress ssh://g...@stash.rainydayz.org:7999/hi/helloworld.git +refs/heads/:refs/remotes/origin/
FATAL: Failed to fetch from ssh://g...@stash.rainydayz.org:7999/hi/helloworld.git
hudson.plugins.git.GitException: Failed to fetch from ssh://g...@stash.rainydayz.org:7999/hi/helloworld.git
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:627)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:865)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:890)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1253)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
	at hudson.model.Run.execute(Run.java:1745)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://g...@stash.rainydayz.org:7999/hi/helloworld.git +refs/heads/:refs/remotes/origin/" returned status code 128:
stdout: 
stderr: Permission denied (publickey).
fatal: The remote end hung up unexpectedly

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1407)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1195)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:87)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:266)
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:625)
	... 10 more




Environment:


Debian (stable), installed via repositories.




Project:


Jenkins



Labels:


git




Priority:


Major



Reporter:


Andy Ruddock

























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:

[JIRA] [email-ext] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time

2014-09-09 Thread kures...@gmail.com (JIRA) 














































Kaupo Kuresson
 created  JENKINS-24638


No E-Mail sent when build of new branch fails for first time















Issue Type:


Bug



Affects Versions:


current



Assignee:


Alex Earl



Components:


email-ext



Created:


09/Sep/14 8:15 AM



Description:


Steps to reproduce my problem:

1. Using GIT for SCM and Jenkins is set up to trigger build on SCM change
2. Master branch is building fine and all tests are passing
3. Create new branch from master
4. Break something so build fails and push to the new branch
5. Build is triggered in Jenkins by SCM change (but it says "No changes")

Expected result is that email-ext plugin sends notification of build failure to the person who first pushed to the new branch. But actually no e-mail is sent and the log says:


Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
An attempt to send an e-mail to empty list of recipients, ignored.
Finished: FAILURE



The "Failure - Any" trigger has Developers and Culprits set under "Send To". When a second commit is made to the new branch by the same person, the trigger works fine - it finds the e-mail address of the culprit and sends the e-mail.




Environment:


Email-ext 2.38.1, Jenkins 1.575




Project:


Jenkins



Labels:


email-ext




Priority:


Major



Reporter:


Kaupo Kuresson

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [thinBackup] (JENKINS-22192) Wrong Error: SEVERE: Could not create backup directory. Backup cannot be performed

2014-09-09 Thread markdeb...@gmail.com (JIRA) 














































mark de bont
 commented on  JENKINS-22192


Wrong Error: SEVERE: Could not create backup directory. Backup cannot be performed















Moving the location to a local destination resolves the problem. Doesn't explain why another instance, same Jenkins and plugin version, is accepting an external UNC path successfully? 



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger

2014-09-09 Thread rinrin...@gmail.com (JIRA) 














































rin_ne
 commented on  JENKINS-19013


Gerrit Trigger: NPE on manual trigger















When you ran build, session for search query might have been already closed.

I will create new PR to check session status.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list

2014-09-09 Thread ullrich.haf...@gmail.com (JIRA) 














































Ulli Hafner
 commented on  JENKINS-24611


Warnings plugin, missing AntJavaParser in the parser selection list 















Seems that the parser already supports the Japanese words for warning, did these names change? 

In case 3, did you specify the correct encoding in the configuration screen? 



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger

2014-09-09 Thread rinrin...@gmail.com (JIRA) 














































rin_ne
 updated  JENKINS-19013


Gerrit Trigger: NPE on manual trigger
















Change By:


rin_ne
(09/Sep/14 8:36 AM)




URL:


https://github.com/jenkinsci/gerrit-trigger-plugin/pull/176



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ldap] (JENKINS-24623) LDAP AcceptSecurityContext error

2014-09-09 Thread 1990.a...@gmail.com (JIRA) 














































Alex Vesely
 commented on  JENKINS-24623


LDAP AcceptSecurityContext error















After analyzing my LDAP hierarchy, I devised the correct manager DN in the format described in your link:
  CN=My Full Name,OU=Workers,DC=abc,DC=corp,DC=company,DC=com

However, that did not change the behavior at all. 
The plugin prints no errors on the configuration, thus implying that the configuration is correct and that it can successfully login to the LDAP server. The Groovy script I posted above also confirms that: it can validate user names successfully.

But when I try to login to Jenkins, I see the following behavior:

	Logging in with a BAD username: login fails, Jenkins log is clean
	Logging in with a GOOD username: whether the password is good or bad, I get the same stacktrace in the Jenkins log.



In summary: the username is identified to be correct, the password is also correct (as it is the manager password), but login is still impossible.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-24611


Warnings plugin, missing AntJavaParser in the parser selection list 















Code changed in jenkins
User: Ulli Hafner
Path:
 src/test/java/hudson/plugins/warnings/parser/AntJavacParserTest.java
http://jenkins-ci.org/commit/warnings-plugin/387e9c5a2dd6c2dc07155be9c19131a204c35381
Log:
  JENKINS-24611 Added testcase.





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger

2014-09-09 Thread rinrin...@gmail.com (JIRA) 












































  
rin_ne
 edited a comment on  JENKINS-19013


Gerrit Trigger: NPE on manual trigger
















When you ran build, session for search query might have been already closed.

I will create new PR to check session status.


@eguess74, if you set "Gerrit Trigger" to choosing strategy in git plugin?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger

2014-09-09 Thread rinrin...@gmail.com (JIRA) 












































  
rin_ne
 edited a comment on  JENKINS-19013


Gerrit Trigger: NPE on manual trigger
















When you ran build, session for search query might have been already closed.

I will create new PR to check session status.


@eguess74, did you set "Gerrit Trigger" to choosing strategy in git plugin?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-21036) NullPointerException in StreamWatchdog when trying to stop/restart

2014-09-09 Thread rinrin...@gmail.com (JIRA) 















































rin_ne
 resolved  JENKINS-21036 as Fixed


NullPointerException in StreamWatchdog when trying to stop/restart
















Change By:


rin_ne
(09/Sep/14 8:47 AM)




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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [master-slave] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"

2014-09-09 Thread oldel...@java.net (JIRA) 














































Richard Mortimer
 commented on  JENKINS-23852


slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"















I have been seeing similar problems to this. In my situation one of my slaves is a Windows 7 desktop computer that is set to suspend after a period of inactivity. I've had this running for a few years without problem and the slave has always reconnected successfully when the desktop is woken up.

However since the NIO selector thread has been introduced the slaves have ended up being offline for prolonged periods of time and require a manual restart of the Jenkins slave service to bring them back online (see JENKINS-24272). One other symptom that I have observed during testing of this is the server rejecting connections similar to that reported here namely:


Jul 16, 2014 9:07:06 PM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: The server rejected the connection: XXX is already connected to this master. Rejecting this connection.
java.lang.Exception: The server rejected the connection: XXX is already connected to this master. Rejecting this connection.
at hudson.remoting.Engine.onConnectionRejected(Engine.java:304)
at hudson.remoting.Engine.run(Engine.java:276)



Having investigated I'm seeing that the slave has decided that the connection is broken and has tore down its TCP connection to the master but the master never sees the TCP RST for this so it continues to retry the TCP packets for 10 or so minutes until the TCP connection times out and then the master tears down the connection.

The really strange this is that this behaviour seems to be different between NIO and threaded methods on the master. With threaded the TCP RST is sent by W7 and kills the connection before the slave reconnects but in NIO no RST is ever sent. That happens down at the network packet level so it shouldn't really be affected by NIO but I wonder if it a slight different configuration in the network stack (non-blocking vs blocking) that causes the different behaviour.

I also suspect that this may be related to the change to re-start JNLP slaves using a new JVM rather than just restarting in the same process. It may be that the Windows TCP stack just immediately forgets the old TCP socket when the old JVM process exits and hence ignores retries rather than RSTing the connection.

I'm planning on waiting for the current crop of JNLP slave fixes to get integrated and will then experiment a bit further to see if I can work out what is stopping the NIO selector getting notified that the slave has closed the TCP connection.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-19013


Gerrit Trigger: NPE on manual trigger















Code changed in jenkins
User: rinrinne
Path:
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/actions/manual/ManualTriggerAction.java
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/Messages.properties
 src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/Messages_ja.properties
http://jenkins-ci.org/commit/gerrit-trigger-plugin/02c4d4febc31582d2d39c5955d3ae4dd40d8c01b
Log:
  Fix session management in manual trigger page

In ManualTriggerAction, session is always created if nothing.
It might be issue if session is closed before build.

This patch creates session once then reuse it.

Fix for JENKINS-19013

Task-Url: https://issues.jenkins-ci.org/browse/JENKINS-19013





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-pipeline] (JENKINS-14565) Please add support for Cloudbees folder structure

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-14565


Please add support for Cloudbees folder structure















Code changed in jenkins
User: Lance Johnston
Path:
 src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java
 src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/trigger/BuildPipelineTrigger.java
http://jenkins-ci.org/commit/build-pipeline-plugin/132e16a21e184e51331080fc9c501a6aba43be69
Log:
  JENKINS-14565 Cloudbees folder plugin support for manually triggered jobs.





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb

2014-09-09 Thread oldel...@java.net (JIRA) 














































Richard Mortimer
 commented on  JENKINS-11952


Emulator occasionally hangs indefinitely on startup, unable to connect adb















The bad_adb.log file does not look like what I expected at all. It seems to be logging socket level information but not adb or transport. It maybe that things operate differently on OS X but if you could check that you did capture the log at the correct level please. It might also be worth making /tmp/adb.log world writeable, chmod a+x /tmp/adb.log, just in case there is something else creating the log first. 



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [conditional-buildstep] (JENKINS-19802) Conditional Build Step for "Current build status" never triggers - or doesn't seem to

2014-09-09 Thread paolo.perso...@gmail.com (JIRA) 














































paolo mazzoni
 commented on  JENKINS-19802


Conditional Build Step for "Current build status" never triggers - or doesn't seem to















I agree with Dominik, it's very strange to watch the build status, but I find it useful when executing external programs or batches, for example sql scripts. With oracle it is possible to interrupt script execution with the clause 'WHENEVER SQL ERROR EXIT FAILURE', this immediately stops script execution and puts the build in failure status. In this case I would watch for the build status and flashback the whole instance (flashback supported since oracle 10.2 btw), but with the bug above mentioned it is long and complicated to manage and identify this situation.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cli] (JENKINS-24639) ExtendedChoiceParameter not supported in Jenkins CLI (ssh)

2014-09-09 Thread da...@orionrobots.co.uk (JIRA) 














































Danny Staple
 created  JENKINS-24639


ExtendedChoiceParameter not supported in Jenkins CLI (ssh)















Issue Type:


Bug



Assignee:


vimil



Components:


cli, extended-choice-parameter



Created:


09/Sep/14 10:27 AM



Description:


If I attempt to start a parameterized build via the Jenkins CLI via SSH with an extended choice parameter I get the following message:


CLI parameter submission is not supported for the class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition type. Please file a bug report for this


I am able to start them by clicking build, and via url with wget.

How I ran this:


ssh -o ServerAliveInterval=10 -p 9200 hudsonmaster1 build -s test_job -p URL="" -p FOR_CHECK_DEVEL=true -p PLATFORM=x86 -p TEST_SET=main_functional_set -p BRANCH=devel


The platform parameter is an extended choice param.




Environment:


Jenkins 1.554.1




Project:


Jenkins



Priority:


Major



Reporter:


Danny Staple

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-24637) Git connection to Stash fails for ssh w/ publickey

2014-09-09 Thread andy.rudd...@rainydayz.org (JIRA) 















































Andy Ruddock
 resolved  JENKINS-24637 as Not A Defect


Git connection to Stash fails for ssh w/ publickey
















Looks as though it was caused by disk corruption on the Stash server which was unable to correctly read the repository.





Change By:


Andy Ruddock
(09/Sep/14 10:56 AM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression

2014-09-09 Thread steffen.breitb...@1und1.de (JIRA) 














































Steffen Breitbach
 commented on  JENKINS-2


Label display wrong when using operators in _expression_















I'm super busy at the moment. I managed to install it but didn't have the time yet to restart Jenkins and have a closer look. Sorry.

I'll look at this as soon as possible.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [conditional-buildstep] (JENKINS-19802) Conditional Build Step for "Current build status" never triggers - or doesn't seem to

2014-09-09 Thread d...@fortysix.ch (JIRA) 














































Dominik Bartholdi
 commented on  JENKINS-19802


Conditional Build Step for "Current build status" never triggers - or doesn't seem to















sorry, maybe I was not clear enough...
The conditional-buildstep plugin is not able to fix this issue. Jenkins stops triggering any further buildsteps if the current build status is not SUCCESS - therefore conditional-buildstep is not able to validate the status either.
>From a conceptional point of view, everything depending on the buildstatus has to be solved/triggered in a post build action, so "Flexible publish" plugin is the one you have to use.
The condition "Current build status" should be removed in one of the next releases of the conditional buildstep plugin.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client] (JENKINS-24640) File modes are wrong after git checkout

2014-09-09 Thread gust...@cpqd.com.br (JIRA) 














































Gustavo Chaves
 created  JENKINS-24640


File modes are wrong after git checkout















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git-client



Created:


09/Sep/14 11:59 AM



Description:


After changing the "Git Installations" general configuration from Git to JGit whenever a new build is triggered in which a git-checkout is performed, the mode of the files changed in the workspace is wrong. In particular, files which should have mode rwxr-xr-x end up having mode rwxr-r-.

After the workspace is wiped out all files that should have the executable bit set end up having only the user-executable bit set, not the group-executable, and not the other-executable.

From an already checked out workspace (in which I have fixed the file modes by hand) if a new build is triggered and a git-fetch/git-checkout is performed by the plugin, all files that were changed end up with the group- and other-executable bits unset.

I've tried this on three different Jenkins slaves and two different Jenkins masters with the same results. Always creating a free-style job from scratch.

If I change the general "Git Installations" back to Git the problem disappears.

I've straced the java -jar slave.jar process during the build and found this sequence of syscalls which caused the problem:


15082 open("/n/code/bin/._server-report.pl8165876850559140433.tmp", O_RDWR|O_CREAT|O_EXCL, 0666) = 71
15082 fstat(71, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
15082 fcntl(71, F_GETFD)= 0
15082 fcntl(71, F_SETFD, FD_CLOEXEC)= 0
15082 close(71) = 0
15082 open("/n/code/bin/._server-report.pl8165876850559140433.tmp", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 71
15082 fstat(71, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
15082 fcntl(71, F_GETFD)= 0
15082 fcntl(71, F_SETFD, FD_CLOEXEC)= 0
15082 write(71, "#!/usr/bin/env perl\n\n# Copyright"..., 6388) = 6388
15082 close(71) = 0
15082 access("/n/code/bin/._server-report.pl8165876850559140433.tmp", X_OK) = -1 EACCES (Permission denied)
15082 stat("/n/code/bin/._server-report.pl8165876850559140433.tmp", {st_mode=S_IFREG|0644, st_size=6388, ...}) = 0
15082 chmod("/n/code/bin/._server-report.pl8165876850559140433.tmp", 0100744) = 0
15082 rename("/n/code/bin/._server-report.pl8165876850559140433.tmp", "/n/code/bin/server-report.pl") = 0
15082 stat("/n/code/bin/server-report.pl", {st_mode=S_IFREG|0744, st_size=6388, ...}) = 0



You can see that first the temporary file is created with mode 0666 and later its mode is changed (via chmod) to 0100744, clearing the executable bits.

I've checked the umask of the user running the slave and it's 0022. I've also checked the umask of the slave process and it's 0022 too.

I haven't found any other mention to this problem in this JIRA or Googling for it.




Environment:


* Red Hat Enterprise Linux 6.2

* Jenkins 1.565.1

* git-client-plugin 1.10.1

* git-plugin 2.2.5






Project:


Jenkins



Priority:


Major



Reporter:


Gustavo Chaves

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [label-linked-jobs] (JENKINS-24641) See what could be reused from better-labels-plugin

2014-09-09 Thread domi.br...@free.fr (JIRA) 














































Dominique Brice
 created  JENKINS-24641


See what could be reused from better-labels-plugin















Issue Type:


New Feature



Assignee:


Dominique Brice



Components:


label-linked-jobs



Created:


09/Sep/14 12:06 PM



Description:


See what could be reused (ideas and/or code) from Daniel's similar plugin.




Project:


Jenkins



Priority:


Major



Reporter:


Dominique Brice

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)

2014-09-09 Thread iwbb....@gmail.com (JIRA) 














































Craig Phillips
 commented on  JENKINS-24076


Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)















Hi Michal

It's been a difficult one to explain this one 

I understand that the data is dynamic.  I have had to use this approach to force delta generation between the last stable build and the current build, by deleting all the intermediate builds.  This issue I am having is that builds are churned out every ten minutes, which is faster than developers are able to fix the CPP check warnings that they have introduced.  So what happens is, you get this intermediate build that sits between the last stable build and the current build.  The current build shows no difference, so you can't use it to determine what new errors were introduced.  You have to go back to the intermediate build to identify the errors.

But at the same time, the current most build shows what errors have been resolved since the last stable build.  So they accumulate as errors are resolved across unstable builds.  This is also odd, because what is interesting to me and my development team, is what warnings did we fix since the last unstable build?  Also, how many errors are left from the warnings we introduced since the last stable build?  Does this make sense?

So if build 1 is stable and I introduce 5 cpp check warnings in build 2 and someone else introduces 3 warnings in build 3 and another build comes out with no additional warnings (build 4), the delta is zero.  If I delete build 3, the delta is 3, because it shows the warnings introduced between build 2 and 4.  If I delete build 2, then I see what I would expect to have seen, that being the total number of errors since the last stable build (build 1).  That said, without deleting any of the builds, if I fix one warning in build 5, it will continue to show 1 warning has been solved for all builds until the next stable build.  I would expect it to show specifically the delta between the build that had the error and the build that resolved it, but nothing outside the scope of this.

I don't necessarily think there is anything wrong with the cppcheck report, it all comes down to how the plugin represents the results between builds.  The simple solution for me, would be to swap the comparisons such that resolved errors are shown since the last build and new errors are since the last "stable" build, which is the inverse of what I am currently seeing.  The more complicated solution would be to have this as a configurable set of options, allowing the job to define what builds are used to represent the deltas.

I hope this clarifies my issue and what I am asking for?   If not, I will need to fork the plugin and make the changes and submit a pull request so I can demonstrate it to you.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-17116) gracefull job termination

2014-09-09 Thread martin.danjo...@gmail.com (JIRA) 














































Martin d'Anjou
 commented on  JENKINS-17116


gracefull job termination















This has gone from bad to worst. I have non-concurrent builds running back to back. When the first one is killed, it somehow keeps running in the background while the other one starts in the same workspace and fails when it should have passed.

Daniel Beck: how do I set the Log to FINER or higher on the process tree, and where do I look up the log? Give me urls please, I sometimes don't understand all the jargon.

This is the Java I am using:

/usr/java/jdk1.7/bin/java -version
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)



I run jenkins as "java -jar jenkins.war"



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-10582) slave connection breaks thru EXCEPTION_ACCESS_VIOLATION

2014-09-09 Thread sebastian.l...@googlemail.com (JIRA) 














































Sebastian Laag
 commented on  JENKINS-10582


slave connection breaks thru EXCEPTION_ACCESS_VIOLATION















I could resolve this problem by changing the version of JNA which is part of the jenkins installation. Now i use version 4.1.0. You can download this version via Maven Repo.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-17116) gracefull job termination

2014-09-09 Thread martin.danjo...@gmail.com (JIRA) 












































  
Martin d'Anjou
 edited a comment on  JENKINS-17116


gracefull job termination
















This has gone from bad to worst. I have non-concurrent builds running back to back. When the first one is killed, it somehow keeps running in the background while the other one starts in the same workspace and fails when it should have passed.

Daniel Beck: how do I set the Log to FINER or higher on the process tree, and where do I look up the log? Give me urls please, I sometimes don't understand all the jargon.

This is the Java I am using:

/usr/java/jdk1.7/bin/java -version
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)



I run jenkins as /usr/java/jdk1.7/bin/java -jar jenkins.war



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [publish-over-ftp] (JENKINS-21083) Connection timed out

2014-09-09 Thread giovannisantin...@yahoo.it (JIRA) 














































Giovanni Santini
 commented on  JENKINS-21083


Connection timed out















Same problem here; for a particular host I had to set it up to 5 hours (1800) as I need something like 1h30m of connections...
It's kinda weird though



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [conditional-buildstep] (JENKINS-19802) Conditional Build Step for "Current build status" never triggers - or doesn't seem to

2014-09-09 Thread paolo.perso...@gmail.com (JIRA) 














































paolo mazzoni
 commented on  JENKINS-19802


Conditional Build Step for "Current build status" never triggers - or doesn't seem to















Well the "Current build status" condition resulted confusing to me since I read it for the first time, so I'll write a post build action as suggested



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-parameter] (JENKINS-24502) Specify a local subdir to check the git repo

2014-09-09 Thread pierretlio...@gmail.com (JIRA) 














































Lionel Pierret
 updated  JENKINS-24502


Specify a local subdir to check the git repo
















Change By:


Lionel Pierret
(09/Sep/14 1:31 PM)




Description:


Could be possible to have a field to specify a local dir where the git repo is in the workspace ?Or even use the parameter from the Git plugin directly if possible ?
!



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sauce-ondemand] (JENKINS-24642) Latest Browsers on Sauce On Demand Plugin

2014-09-09 Thread ppal...@signiant.com (JIRA) 














































Prashanth Paleti
 created  JENKINS-24642


Latest Browsers on Sauce On Demand Plugin















Issue Type:


Task



Assignee:


Kohsuke Kawaguchi



Components:


sauce-ondemand



Created:


09/Sep/14 1:34 PM



Description:


Hi

We make use of the Sauce On Demand plugin in order to run over selenium tests on Sauce Labs.

Can someone tell us how we can be up to date with the latest OS/Browser combination ? Right now Sauce Labs has the support for the Chrome Version 37, but through Sauce On Demand plugin we are able to see the Chrome Version 36.

Is there a way how we can stay up to date with the OS/Browser versions supported on Sauce Labs ? Wonder if we have to be updating the plugin every time there is a new combination on Sauce Labs.

Any inputs on this are really appreciated.

Thanks
Prashanth




Project:


Jenkins



Labels:


plugin
jenkins




Priority:


Major



Reporter:


Prashanth Paleti

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials

2014-09-09 Thread alghe.glo...@gmail.com (JIRA) 














































Alexandru Gheorghe
 commented on  JENKINS-6610


RSS Feeds Ought to Accept Credentials















Daniel Beck:
Appears to be a client-side issue. I can get the feed from the command line using

curl --netrc http://jenkins/rssAll

if no anonymous access is allowed and the .netrc file contains my user name and API token.
And if the RSS client doesn't support this method? It's obvious people won't use curl to get their RSS.


Please demonstrate that the issue you're experiencing is not due to your RSS client being complete crap by providing output of the above (or similar, e.g. passing user name and API token directly on the command line) curl commands (alternatively wget) showing that the issue occurs there as well.
It's not because it has a web browser incorporated (KDE). Without enabling access to anonymous for viewing, I can't read the RSS (because it can't login, because of the login portal), however if I do enable, I can get RSS (as anonymous ofc. with privileges).

I do not exclude that the web browser of Akregator might be poor since I can login with ease with any other dedicated browser (Chrome, Mozilla Firefox etc.)

My guess is to make it compatible or add a &netrc= for the API token.
Tried various solutions around the internet with the API token but all failed at the login portal.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cloudformation] (JENKINS-24643) Unable to launch large templates

2014-09-09 Thread uism...@ea.com (JIRA) 














































Usman Ismail
 created  JENKINS-24643


Unable to launch large templates















Issue Type:


Bug



Affects Versions:


current



Assignee:


edovale



Components:


cloudformation



Created:


09/Sep/14 1:42 PM



Description:


Unable to use large Cloud Formation templates because we get the following error:


 "at 'templateBody' failed to satisfy constraint: Member must have
   length less than or equal to 51200"
 

We should upload to s3 and then use that URL to launch the template as the AWS web console does.




Project:


Jenkins



Priority:


Major



Reporter:


Usman Ismail

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ws-cleanup] (JENKINS-20056) When deleting the entire workspace, perform it asynchronously

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 















































SCM/JIRA link daemon
 resolved  JENKINS-20056 as Fixed


When deleting the entire workspace, perform it asynchronously
















Change By:


SCM/JIRA link daemon
(09/Sep/14 1:44 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ws-cleanup] (JENKINS-20056) When deleting the entire workspace, perform it asynchronously

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-20056


When deleting the entire workspace, perform it asynchronously















Code changed in jenkins
User: Oliver Gondža
Path:
 src/main/java/hudson/plugins/ws_cleanup/Cleanup.java
 src/main/java/hudson/plugins/ws_cleanup/PreBuildCleanup.java
 src/main/java/hudson/plugins/ws_cleanup/RemoteCleaner.java
 src/main/java/hudson/plugins/ws_cleanup/Wipeout.java
 src/main/java/hudson/plugins/ws_cleanup/WsCleanup.java
 src/test/java/hudson/plugins/ws_cleanup/CleanupTest.java
http://jenkins-ci.org/commit/ws-cleanup-plugin/8e31d6a90fa0310ab18ab1384ac4fe142fa65c4d
Log:
  [FIXED JENKINS-20056] Delete workspace asynchronously


Compare: https://github.com/jenkinsci/ws-cleanup-plugin/compare/784d5afb95eb...8e31d6a90fa0




























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ws-cleanup] (JENKINS-20056) When deleting the entire workspace, perform it asynchronously

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-20056


When deleting the entire workspace, perform it asynchronously















Code changed in jenkins
User: Oliver Gondža
Path:
 src/test/java/hudson/plugins/ws_cleanup/CleanupTest.java
http://jenkins-ci.org/commit/ws-cleanup-plugin/0af6bfbc2a5eef5c1664d02bc9b450c9f45654e6
Log:
  JENKINS-20056 Some more tests





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials

2014-09-09 Thread dan...@beckweb.net (JIRA) 














































Daniel Beck
 commented on  JENKINS-6610


RSS Feeds Ought to Accept Credentials















Did you try the http://user:apitoken@jenkins/rssAll format for URLs with embedded authentication?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-17116) gracefull job termination

2014-09-09 Thread dan...@beckweb.net (JIRA) 














































Daniel Beck
 commented on  JENKINS-17116


gracefull job termination















Martin d'Anjou:

This has gone from bad to worst

Unhelpful statement without mentioning the involved Jenkins versions. Which were bad, which are worse?

how do I set the Log to FINER or higher on the process tree, and where do I look up the log?

Go to http://jenkins/log, create a new log recorder (use any name), add a logger named hudson.util.ProcessTree and set level to FINER. Save. Go to the log recorder's page occassionally when the issue occurs to see what it logs.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials

2014-09-09 Thread dan...@beckweb.net (JIRA) 














































Daniel Beck
 commented on  JENKINS-6610


RSS Feeds Ought to Accept Credentials















And if the RSS client doesn't support this method? It's obvious people won't use curl to get their RSS. ... My guess is to make it compatible or add a &netrc= for the API token.

To clarify, this is basic HTTP auth under the hood. --netrc just reads the username and password from a file rather than expecting username and password as parameters on the command line. I tested this just to be absolutely sure, 
curl -u danielbeck:my_API_token http://jenkins/rssAll
 works like a charm as well on an instance (Jenkins 1.565.2) without anon read access.

Hence my assertion that, if your RSS (HTTP) client cannot do basic HTTP authentication, that's not a problem of Jenkins.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [role-strategy] (JENKINS-19409) User names should not be case sensitive.

2014-09-09 Thread walter.nag...@zf.com (JIRA) 














































Walter Nagler
 commented on  JENKINS-19409


User names should not be case sensitive.















Works for me, too.
In combination with Active Directory plugin



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time

2014-09-09 Thread slide.o....@gmail.com (JIRA) 














































Alex Earl
 commented on  JENKINS-24638


No E-Mail sent when build of new branch fails for first time















If Jenkins says "no changes" then email-ext will also see no changes and there won't be developers or culprits. This sounds like an issue in either core or git scm.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [delivery-pipeline] (JENKINS-24644) NPE when View is configured with a non existing firstJob

2014-09-09 Thread pat...@diabol.se (JIRA) 














































Patrik Boström
 created  JENKINS-24644


NPE when View is configured with a non existing firstJob















Issue Type:


Bug



Assignee:


Patrik Boström



Components:


delivery-pipeline



Created:


09/Sep/14 2:48 PM



Description:


NPE when View is configured with a non existing firstJob


Sep 05, 2014 4:19:51 PM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: it.allViewJobNamesAsJson in /jenkins/view/-Pipeline/api/json. Reason: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor179.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24)
at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55)
at hudson.util.HudsonIsLoading.doDynamic(HudsonIsLoading.java:45)
at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.kohsuke.stap

[JIRA] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials

2014-09-09 Thread williamle...@java.net (JIRA) 














































williamleara
 commented on  JENKINS-6610


RSS Feeds Ought to Accept Credentials















As I mentioned in the original issue write-up:

my RSS reader supports Basic, Digest and NTLM authentication schemes

Being that is that case, and considering that multiple people are having the problem with a variety of RSS readers, this is not an RSS client 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [extended-choice-parameter] (JENKINS-24639) ExtendedChoiceParameter not supported in Jenkins CLI (ssh)

2014-09-09 Thread dan...@beckweb.net (JIRA) 














































Daniel Beck
 updated  JENKINS-24639


ExtendedChoiceParameter not supported in Jenkins CLI (ssh)
















Not an issue with CLI, the plugin's parameter type just needs to implement ParameterDefinition.createValue(CLICommand, String).





Change By:


Daniel Beck
(09/Sep/14 3:05 PM)




Component/s:


cli



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials

2014-09-09 Thread dan...@beckweb.net (JIRA) 














































Daniel Beck
 commented on  JENKINS-6610


RSS Feeds Ought to Accept Credentials















Could you provide a log of the HTTP requests and responses sent by/to your RSS reader?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-flow] (JENKINS-13523) Missing option "Add timestamps to the Console Output" (Build Environment)

2014-09-09 Thread dan.russ...@smartstream-stp.com (JIRA) 














































dan russell
 commented on  JENKINS-13523


Missing option "Add timestamps to the Console Output" (Build Environment)















Being groovy can always add your own, though would be nice if the option was supported

println "job scheduled at" + new Date()
build("job")
println "job completed at" + new Date()



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [custom-tools] (JENKINS-24645) Portions of config go missing

2014-09-09 Thread csui...@gmail.com (JIRA) 














































Chris Suich
 created  JENKINS-24645


Portions of config go missing















Issue Type:


Bug



Affects Versions:


current



Assignee:


Oleg Nenashev



Attachments:


com.cloudbees.jenkins.plugins.customtools.CustomTool.xml, com.cloudbees.jenkins.plugins.customtools.CustomTool.xml.bk, config.diff, config.xml, config.xml.bk



Components:


custom-tools, toolenv



Created:


09/Sep/14 3:14 PM



Description:


We have been running into an issue where we are losing portions of our global config. It appears that it might be tied to when global config changes are saved, but periodically our build start failing and when we investigate, we find that our configuration is not in the state we expect it to.

We have noticed the following config changes:

	JDK Install from java.sun.com version gets changed from what we. (7u5 -> 8u20)
	Custom tool installers are removed. For example, we have a custom tool for housing our custom ant tasks. The installer is just a zip extract, but the installer is removed from the config (see diff below).



After noticing this happened, I performed a diff of the Jenkins config files and our back. Some relevant portions of the diff and the munged configs are attached.




Environment:


Jenkins 1.578 on Ubuntu 14.04




Project:


Jenkins



Labels:


jenkins
custom-tools-0.4
jdk
tools
config
configuration
save




Priority:


Critical



Reporter:


Chris Suich

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github-oauth] (JENKINS-24010) github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus'

2014-09-09 Thread wav...@gmail.com (JIRA) 














































Marc Harter
 commented on  JENKINS-24010


github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus' 















There is a discussion about this same issue happening in this case:
https://issues.jenkins-ci.org/browse/JENKINS-20883

FWIW, I agree.  I would like to see this allowed through (or some more controls on what is allowed through) as I can't allow READ for everybody just to show the build status.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [copyartifact] (JENKINS-24626) Unable to CopyArtifact from builds using older CopyArtifact plugin

2014-09-09 Thread de...@ikedam.jp (JIRA) 














































ikedam
 commented on  JENKINS-24626


Unable to CopyArtifact from builds using older CopyArtifact plugin















Let me know:

	Does SubJob work fine after upgrading copyartifact to 1.31?
	Did MainJob work fine before upgrading copyartifact to 1.31?



And could you attach following files?

	configurations of those jobs. They are placed at ${JENKINS_HOME}/jobs/(jobname)/config.xml
	console outputs for a succeeded build and a failed build.





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [custom-tools] (JENKINS-24645) Portions of config go missing

2014-09-09 Thread csui...@gmail.com (JIRA) 














































Chris Suich
 updated  JENKINS-24645


Portions of config go missing
















Change By:


Chris Suich
(09/Sep/14 3:25 PM)




Attachment:


jenkins.log





Description:


We have been running into an issue where we are losing portions of our global config. It appears that it might be tied to when global config changes are saved, but periodically our build start failing and when we investigate, we find that our configuration is not in the state we expect it to.We have noticed the following config changes:- JDK Install from java.sun.com version gets changed from what we. (7u5 -> 8u20)- Custom tool installers are removed. For example, we have a custom tool for housing our custom ant tasks. The installer is just a zip extract, but the installer is removed from the config (see diff below).After noticing this happened, I performed a diff of the Jenkins config files and our back. Some relevant portions of the diff and the munged configs are attached.
Edit: Forgot some details...- We have Jenkins installed on Ubuntu via apt-get and started via 'service jenkins start'.- I did not find any errors in the log (which is attached). After we noticed that the config had been changed, I looked at the config.xml's last modified time and noted it was last changed on September 9th at 10:27 am.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-24546) Git plugin doesn't use environment variables when running git for polling

2014-09-09 Thread egues...@java.net (JIRA) 














































eguess74
 commented on  JENKINS-24546


Git plugin doesn't use environment variables when running git for polling















I'm sorry I don't understand your last comment. 
The actual problem is stil there as the polling doesn't seem to be explicitly using master node settings to perform the poll - isn't it how it is supposed to behave?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger

2014-09-09 Thread egues...@java.net (JIRA) 














































eguess74
 commented on  JENKINS-19013


Gerrit Trigger: NPE on manual trigger















@rin_ne - yes, that fixed the issue for me, thank you. Sorry for the noise.
OTOH i see this mistkae quite often in web, so may be it would make sense to maek it default selection?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-19013) Gerrit Trigger: NPE on manual trigger

2014-09-09 Thread egues...@java.net (JIRA) 












































  
eguess74
 edited a comment on  JENKINS-19013


Gerrit Trigger: NPE on manual trigger
















@rin_ne - yes, that fixed the issue for me, thank you. Sorry for the noise.
OTOH i see this mistake quite often in web, so may be it would make sense to make it default selection?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24645) Portions of config go missing

2014-09-09 Thread csui...@gmail.com (JIRA) 














































Chris Suich
 updated  JENKINS-24645


Portions of config go missing
















Change By:


Chris Suich
(09/Sep/14 3:38 PM)




Component/s:


core



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [openid] (JENKINS-24646) Jenkins not able to access the openID server URL when clicked on login

2014-09-09 Thread junaid.sha...@msn.com (JIRA) 














































junaid shaikh
 created  JENKINS-24646


Jenkins not able to access the openID server URL when clicked on login 















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


openid



Created:


09/Sep/14 3:40 PM



Description:


I have a CAS server configured with LDAP. 
The OpenID plugin is able to validate the openID URL without any problems i.e. when I put my openID URL in the openID SSO field and click on validate it says OK. But when I click on the login button it gives an error 404. It seems that after I click on Login the plugin is not able to resolve the URL and hence the error. I tried debugging but nothing looks promising so far.

I have attached the stack trace below for your kind reference. 


Stack trace

javax.servlet.ServletException: org.openid4java.discovery.DiscoveryException: 0x706: Failed to discover OpenID: http://localhost:9090/cfgmgnt.cas.sso/login/
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
	at org.mortbay.jetty.s

[JIRA] [openid] (JENKINS-24288) Noclassdef found in openID plugin

2014-09-09 Thread junaid.sha...@msn.com (JIRA) 















































junaid shaikh
 resolved  JENKINS-24288 as Fixed


Noclassdef found in openID plugin
















Change By:


junaid shaikh
(09/Sep/14 3:41 PM)




Status:


Open
Resolved





Assignee:


Kohsuke Kawaguchi





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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24647) Deleting last build and building a new one will loose project result trend

2014-09-09 Thread alghe.glo...@gmail.com (JIRA) 














































Alexandru Gheorghe
 created  JENKINS-24647


Deleting last build and building a new one will loose project result trend















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


09/Sep/14 4:00 PM



Description:


How to reproduce:

	have some jobs in history
	build a job
	delete it
	build a new job
	result: project's trend is now lost (blank, white)






Environment:


OS: Ubuntu 14.04 LTS; Java: java version "1.6.0_31" + OpenJDK Runtime Environment (IcedTea6 1.13.3) (6b31-1.13.3-1ubuntu1~0.12.04.2) + OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode); Jenkins v1.578




Fix Versions:


current



Project:


Jenkins



Priority:


Minor



Reporter:


Alexandru Gheorghe

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'

2014-09-09 Thread t...@boulderlabs.com (JIRA) 














































Tres Spicher
 commented on  JENKINS-7695


archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'















I am seeing this in 1.571:


ERROR: Failed to archive artifacts: *.log
java.io.IOException: java.io.IOException: Failed to extract /var/lib/jenkins/workspace/OneOneOne/transfer of 6 files
	at hudson.FilePath.readFromTar(FilePath.java:2119)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:2031)
	at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61)
	at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:183)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:736)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:685)
	at hudson.model.Run.execute(Run.java:1757)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:234)
Caused by: java.io.IOException: unexpected EOF with 1921 bytes unread
	at hudson.org.apache.tools.tar.TarInputStream.read(TarInputStream.java:349)
	at java.io.FilterInputStream.read(FilterInputStream.java:90)
	at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792)
	at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769)
	at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744)
	at hudson.util.IOUtils.copy(IOUtils.java:40)
	at hudson.FilePath.readFromTar(FilePath.java:2109)
	... 12 more

	at hudson.FilePath.copyRecursiveTo(FilePath.java:2038)
	at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61)
	at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:183)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:736)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:685)
	at hudson.model.Run.execute(Run.java:1757)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:234)
Caused by: java.util.concurrent.ExecutionException: java.io.IOException: request to write '4053' bytes exceeds size in header of '85889' bytes for entry 'models.log'
	at hudson.remoting.Channel$3.adapt(Channel.java:772)
	at hudson.remoting.Channel$3.adapt(Channel.java:767)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:2034)
	... 11 more
Caused by: java.io.IOException: request to write '4053' bytes exceeds size in header of '85889' bytes for entry 'models.log'
	at hudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284)
	at hudson.util.io.TarArchiver.visit(TarArchiver.java:114)
	at hudson.util.DirScanner.scanSingle(DirScanner.java:49)
	at hudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2571)
	at hudson.FilePath.writeToTar(FilePath.java:2083)
	at hudson.FilePath.access$1000(FilePath.java:180)
	at hudson.FilePath$41.invoke(FilePath.java:2024)
	at hudson.FilePath$41.invoke(FilePath.java:2020)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2492)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at hudson.remoting.Engine$1$1.run(Engine.java:63)
	at java.lang.Thread.run(Thread.java:701)
Build step 'Archive the artifacts' changed build result to FAILURE

[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception

2014-09-09 Thread meenal.khandel...@cerner.com (JIRA) 














































Meenal Khandelwal
 commented on  JENKINS-23641


Builds are failing due to GitHubCommitNotifier exception















I am getting a similar error, It is only showing this error:


ERROR: Publisher com.cloudbees.jenkins.GitHubCommitNotifier aborted due to exception
11:07:06 java.lang.NullPointerException
11:07:06 	at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:53)
11:07:06 	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
11:07:06 	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
11:07:06 	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
11:07:06 	at hudson.model.Build$BuildExecution.post2(Build.java:183)
11:07:06 	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
11:07:06 	at hudson.model.Run.execute(Run.java:1765)
11:07:06 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
11:07:06 	at hudson.model.ResourceController.execute(ResourceController.java:89)
11:07:06 	at hudson.model.Executor.run(Executor.java:240)


This error is associated with only one pull request. I tried building other pull request for the same repository, they all ran fine.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception

2014-09-09 Thread meenal.khandel...@cerner.com (JIRA) 












































  
Meenal Khandelwal
 edited a comment on  JENKINS-23641


Builds are failing due to GitHubCommitNotifier exception
















I am getting a similar error, It is showing this error:


ERROR: Publisher com.cloudbees.jenkins.GitHubCommitNotifier aborted due to exception
11:07:06 java.lang.NullPointerException
11:07:06 	at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:53)
11:07:06 	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
11:07:06 	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
11:07:06 	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
11:07:06 	at hudson.model.Build$BuildExecution.post2(Build.java:183)
11:07:06 	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
11:07:06 	at hudson.model.Run.execute(Run.java:1765)
11:07:06 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
11:07:06 	at hudson.model.ResourceController.execute(ResourceController.java:89)
11:07:06 	at hudson.model.Executor.run(Executor.java:240)


This error is associated with only one pull request. I tried building other pull request for the same repository, they all ran fine.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24636) upload file via CLI build a job with file parameter fail, if the file is large and the server is a windows machine

2014-09-09 Thread dan...@beckweb.net (JIRA) 














































Daniel Beck
 updated  JENKINS-24636


upload file via CLI build a job with file parameter fail, if the file is large and the server is a windows machine
















Have you tested with Linux server, or why limit to Windows in the title?





Change By:


Daniel Beck
(09/Sep/14 5:23 PM)




Labels:


remoting





Affects Version/s:


current





Component/s:


core



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tfs] (JENKINS-23033) TFS Password visible in view source

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 















































SCM/JIRA link daemon
 resolved  JENKINS-23033 as Fixed


TFS Password visible in view source
















Change By:


SCM/JIRA link daemon
(09/Sep/14 5:24 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tfs] (JENKINS-23033) TFS Password visible in view source

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-23033


TFS Password visible in view source















Code changed in jenkins
User: Nicolas De Loof
Path:
 pom.xml
 src/main/java/hudson/plugins/tfs/TeamFoundationServerScm.java
 src/main/resources/hudson/plugins/tfs/TeamFoundationServerScm/config.jelly
 src/test/java/hudson/plugins/tfs/browsers/TeamSystemWebAccessBrowserTest.java
http://jenkins-ci.org/commit/tfs-plugin/5e391d94d936c5837048d63eb83b7a11a9ffdcdd
Log:
  [FIXED JENKINS-23033] don’t use String but Secret to store password
UI binding will use a cipher and avoid it to be exposed as plain text in HTML form.





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [cloudformation] (JENKINS-24643) Unable to launch large templates

2014-09-09 Thread edov...@gmail.com (JIRA) 














































edovale
 commented on  JENKINS-24643


Unable to launch large templates















This should probably not be a bug but a missing feature. I am thinking that we should allow for the user to enter a URL to a cf template file.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tfs] (JENKINS-23033) TFS Password visible in view source

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-23033


TFS Password visible in view source















Code changed in jenkins
User: Nicolas De Loof
Path:
 src/main/java/hudson/plugins/tfs/TeamFoundationServerScm.java
 src/main/resources/hudson/plugins/tfs/TeamFoundationServerScm/config.jelly
 src/test/java/hudson/plugins/tfs/browsers/TeamSystemWebAccessBrowserTest.java
http://jenkins-ci.org/commit/tfs-plugin/bd98b91ea614c307a6bb1e0af36d9dd2a5646e29
Log:
  [FIXED JENKINS-23033] don’t use String but Secret to store password
UI binding will use a cipher and avoid it to be exposed as plain text in HTML form.





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23665) Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password

2014-09-09 Thread dan...@beckweb.net (JIRA) 














































Daniel Beck
 commented on  JENKINS-23665


Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password















Kohsuke's traveling this week. I'll try to (remember to) point him to this change at next week's governance meeting.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-24648) Git poll always finds changes when there is non when used with Gerrit trigger strategy

2014-09-09 Thread egues...@java.net (JIRA) 














































eguess74
 created  JENKINS-24648


Git poll always finds changes when there is non when used with Gerrit trigger strategy















Issue Type:


Bug



Assignee:


rsandell



Components:


gerrit-trigger, git



Created:


09/Sep/14 6:01 PM



Description:


I have gerrit configured to react on changes in all branches (**) but the buids are using the property $GERRIT_BRANCH set to ref/heads/my_branch
WHen polls are running i see that the last built revision matches the ones that are available in mainline - there is no other revisions that are coming from the git ls-remote command that poll uses. Yet git poll reports it found changes and it triggeres the rebuild.
in changes list for the project all latest builds are having the same one commit over and over again.





Environment:


linux




Project:


Jenkins



Priority:


Major



Reporter:


eguess74

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-24648) Git poll always finds changes when there is none when used with Gerrit trigger strategy

2014-09-09 Thread egues...@java.net (JIRA) 














































eguess74
 updated  JENKINS-24648


Git poll always finds changes when there is none when used with Gerrit trigger strategy
















Change By:


eguess74
(09/Sep/14 6:35 PM)




Summary:


Git poll always finds changes when there is
 non
 none
 when used with Gerrit trigger strategy



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list

2014-09-09 Thread ullrich.haf...@gmail.com (JIRA) 














































Ulli Hafner
 commented on  JENKINS-24611


Warnings plugin, missing AntJavaParser in the parser selection list 















Would it be possible if you could update the test case (and parser) on your own? Seems not easy to work in a foreign locale for me. I added the test case in AntJavacParserTest#testIssue24611.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-24611


Warnings plugin, missing AntJavaParser in the parser selection list 















Code changed in jenkins
User: Ulli Hafner
Path:
 src/test/java/hudson/plugins/warnings/parser/AntJavacParserTest.java
http://jenkins-ci.org/commit/warnings-plugin/51df96d0253d4541d3131bbe1f4927d16b4da3fb
Log:
  JENKINS-24611 Added testcase.





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24604) Polling fails in "node on demand" environments

2014-09-09 Thread ewilt...@gmail.com (JIRA) 














































Elliot Wiltshire
 commented on  JENKINS-24604


Polling fails in "node on demand" environments















Hi Michael,

I don't believe the (Perforce plugin) polling would happen in this case, since the build is failing fairly high up the chain. Could you please tell me which version of Jenkins you're running? Also, if you trigger a build manually does it work properly?

Thanks,
-e. 



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24604) Polling fails in "node on demand" environments

2014-09-09 Thread mr...@sjm.com (JIRA) 














































Michael Rose
 commented on  JENKINS-24604


Polling fails in "node on demand" environments















Hi Elliot Wiltshire,

Yes, manual triggers do work.

Version information:
Jenkins version 1.575 
P4 plugin version 1.0.12

Thanks
Michael



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24604) Polling fails in "node on demand" environments

2014-09-09 Thread ewilt...@gmail.com (JIRA) 














































Elliot Wiltshire
 commented on  JENKINS-24604


Polling fails in "node on demand" environments















Hi Michael,

Thanks for checking those for me. It looks like this issue is with the Jenkins core, and not the Perforce plugin itself, based on your version information and this related (grandparent) ticket: https://issues.jenkins-ci.org/browse/JENKINS-22750

There are a couple workarounds suggested there, which I hope will be of some help.

-e.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24604) Polling fails in "node on demand" environments

2014-09-09 Thread ewilt...@gmail.com (JIRA) 















































Elliot Wiltshire
 closed  JENKINS-24604 as Not A Defect


Polling fails in "node on demand" environments
















Not a defect in the Perforce plugin - this looks like it's an issue with the Jenkins core.





Change By:


Elliot Wiltshire
(09/Sep/14 7:32 PM)




Status:


Open
Closed





Assignee:


Elliot Wiltshire





Resolution:


Not A Defect



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24565) P4 Plugin doesn't support perforce edge server

2014-09-09 Thread ewilt...@gmail.com (JIRA) 














































Elliot Wiltshire
 commented on  JENKINS-24565


P4 Plugin doesn't support perforce edge server















Hi Punith,

Can you please verify that this is not a configuration issue related to the client you are using? The error message seems to indicate that the client Jenkins is mis-configured. Was this working before against a non-edge server? Can you please copy the output from "p4 client -o noclient" and paste here?

Thanks,
-e.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [azure-slave] (JENKINS-24649) Allow to stop / deallocate and start / allocate existing VMs on demand

2014-09-09 Thread sschube...@gmail.com (JIRA) 














































Sebastian Schuberth
 created  JENKINS-24649


Allow to stop / deallocate and start / allocate existing VMs on demand















Issue Type:


New Feature



Assignee:


Martin Sawicki



Components:


azure-slave



Created:


09/Sep/14 7:37 PM



Description:


In addition to creating VMs based on captured templates, please allow to stop / deallocate and start / allocate existing VMs on demand (for some background info see e.g. [1]). That way an Azure VM would not be billed unless it's being used as a Jenkins node.

One thing that might be tricky is to handle the case where a reallocated VMs get assigned another IP because to Jenkins, it must still appear as the same node.

[1] http://blogs.technet.com/b/keithmayer/archive/2013/06/19/windows-azure-virtual-machines-there-s-more-than-1-way-to-shutdown-a-vm.aspx




Project:


Jenkins



Priority:


Major



Reporter:


Sebastian Schuberth

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24604) Polling fails in "node on demand" environments

2014-09-09 Thread mr...@sjm.com (JIRA) 














































Michael Rose
 commented on  JENKINS-24604


Polling fails in "node on demand" environments















The issue you referenced say the problem was resolved in 1.565, but I'm running 1.575 and still seeing it. I'm guessing this b/c the Perforce plugin does use a workspace when polling which they said they weren't going to address. So basically (if I'm summarizing that issue right) Perforce polling will not work for a completely node on demand environment, I have to keep atleast one node running at all times.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [groovy] (JENKINS-9130) Add a dynamic parser to colorize and indent groovy textareas

2014-09-09 Thread sschube...@gmail.com (JIRA) 














































Sebastian Schuberth
 commented on  JENKINS-9130


Add a dynamic parser to colorize and indent groovy textareas















Hmm, so what's the status of this? I recently saw that the Scriptler plugin has nice syntax highlighting and line numbers, and I was about to propose the same for the Groovy and Groovy Postbuild plugins. Because at least the Groovy plugin versions we're using do not yet seem to have this feature enabled, although my understanding is that ever since the commit at [1] from 2011 the Jenkins core offers syntax highlighted textboxes.

[1] https://github.com/jenkinsci/jenkins/commit/19b81cfb2a61b4b02e07450152d6781455443b87



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-17116) gracefull job termination

2014-09-09 Thread martin.danjo...@gmail.com (JIRA) 














































Martin d'Anjou
 commented on  JENKINS-17116


gracefull job termination















Sorry I should have been more useful in my comment. By worst I meant that I have found that a killed job can corrupt the current job's workspace. I have found a way to reproduce this corruption 100% of the time.

I use Jenkins 1.578 and Java SE JRE 1.7.0_45-b18) Java HotSpot 64-bit Server VM (build 24.35-b08).

I launch jenkins from linux RHEL 6.4 (Santiago) with java -jar jenkins.war

The job needs to be configured with the following script (it is a variation on the python script above):

#!/usr/bin/python
import signal
import time
import os
def handler(*ignored):
time.sleep(120)
fh = open("a_file.txt","a")
fh.write("Handler of Build number: "+os.environ['BUILD_NUMBER'])
fh.close()

signal.signal(signal.SIGTERM, handler)
fh = open("a_file.txt","w")
fh.write("Main of Build number: "+os.environ['BUILD_NUMBER'])
fh.close()
time.sleep(120)



Then configure the job to archive the artifact named a_file.txt
Run two jobs back to back, kill the first one shortly after it started. Leave the second one to complete until it ends normally.

The log as configured in the above comment, shows:

killAll: process=java.lang.UNIXProcess@3d7c07c9 and envs={HUDSON_COOKIE=06668ba4-b481-4a17-86b3-5f4fbd4061b2}
Sep 09, 2014 3:30:49 PM FINE hudson.util.ProcessTree
Recursively killing pid=1840
Sep 09, 2014 3:30:49 PM FINE hudson.util.ProcessTree
Killing pid=1840
Sep 09, 2014 3:30:49 PM FINE hudson.util.ProcessTree
Recursively killing pid=1840
Sep 09, 2014 3:30:49 PM FINE hudson.util.ProcessTree
Killing pid=1840



The unix process table, after the kill, shows that both jobs are still running:

mdanjou   1251   953  0 10:07 pts/30   00:01:46   java -jar jenkins.war
mdanjou   1840  1251  0 15:30 pts/30   00:00:00 /usr/bin/python /tmp/hudson6469713064377741807.sh
mdanjou   1851  1251  0 15:30 pts/30   00:00:00 /usr/bin/python /tmp/hudson1969984296722384280.sh


Both jobs are still running.

When the second job completes, examine its artifact. It contains this:

Main of Build number: 18Handler of Build number: 17



So the killed build (#17) corrupts the workspace of the running build (#18).



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [artifactory] (JENKINS-23795) error connecting jenkins to artifactory

2014-09-09 Thread harschw...@yahoo.com (JIRA) 














































harschware
 commented on  JENKINS-23795


error connecting jenkins to artifactory















In my case, I had MAVEN_HOME configured correctly, but did not have a JDK configured and no JAVA_HOME.  Downloading Java and configuring it Jenkins did the trick.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-17116) gracefull job termination

2014-09-09 Thread dan...@beckweb.net (JIRA) 














































Daniel Beck
 commented on  JENKINS-17116


gracefull job termination















Makes sense. I don't see how this could be circumvented. Maybe by waiting a bit to see whether SIGTERM worked, and if not, send SIGKILL? But Jenkins uses the JRE's abstraction of "kill a Unix process" and that behavior appears to be implementation dependent.

Should be possible to write a plugin that sends SIGKILL if configured (e.g. for specific jobs only). Would that help?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [groovy] (JENKINS-9130) Add a dynamic parser to colorize and indent groovy textareas

2014-09-09 Thread sschube...@gmail.com (JIRA) 












































  
Sebastian Schuberth
 edited a comment on  JENKINS-9130


Add a dynamic parser to colorize and indent groovy textareas
















Hmm, so what's the status of this? I recently saw that the Scriptler plugin has nice syntax highlighting and line numbers, and I was about to propose the same for the Groovy and Groovy Postbuild plugins. Because at least the Groovy plugin versions we're using do not yet seem to have this feature enabled, although my understanding is that ever since the commit at [1] from 2011 the Jenkins core offers syntax highlighted textboxes.

EDIT: Correction, I just verifier that the Groovy plugin version 1.20 indeed has syntax highlighting, but the Groovy Postbuild plugin version 1.10 still has not.

[1] https://github.com/jenkinsci/jenkins/commit/19b81cfb2a61b4b02e07450152d6781455443b87



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [groovy-postbuild] (JENKINS-24650) Add syntax highlighting like the Scriptler and Groovy plugin have

2014-09-09 Thread sschube...@gmail.com (JIRA) 














































Sebastian Schuberth
 created  JENKINS-24650


Add syntax highlighting like the Scriptler and Groovy plugin have















Issue Type:


Improvement



Assignee:


wolfs



Components:


groovy-postbuild



Created:


09/Sep/14 8:10 PM



Description:


The Scriptler and Groovy plugins already offer syntax highlighting and line numbers as part of their textboxes. It would be nice to have the same for the Groovy Postbuild plugin.




Project:


Jenkins



Priority:


Major



Reporter:


Sebastian Schuberth

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [delivery-pipeline] (JENKINS-24644) NPE when View is configured with a non existing firstJob

2014-09-09 Thread pat...@diabol.se (JIRA) 














































Patrik Boström
 commented on  JENKINS-24644


NPE when View is configured with a non existing firstJob















Created PR 
https://github.com/Diabol/delivery-pipeline-plugin/pull/82
With 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [html5-notifier] (JENKINS-13591) Plugin doesn't support jenkins URL prefix (--prefix option)

2014-09-09 Thread pe...@eisentraut.org (JIRA) 















































Peter Eisentraut
 closed  JENKINS-13591 as Fixed


Plugin doesn't support jenkins URL prefix (--prefix option)
















works as described





Change By:


Peter Eisentraut
(09/Sep/14 8:34 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [azure-slave] (JENKINS-24649) Allow to stop / deallocate and start / allocate existing VMs on demand

2014-09-09 Thread marc...@microsoft.com (JIRA) 














































Martin Sawicki
 commented on  JENKINS-24649


Allow to stop / deallocate and start / allocate existing VMs on demand















planning to look into that in the next release, but ETA TBD still.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception

2014-09-09 Thread david.joel.tan...@gmail.com (JIRA) 














































David Tanner
 commented on  JENKINS-23641


Builds are failing due to GitHubCommitNotifier exception















What is special about that pull request, or the branch that it is pulling from?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [maven-deployment-linker] (JENKINS-24651) Memory Leak when downloading large file from linked project

2014-09-09 Thread bdg...@gmail.com (JIRA) 














































Brian Goad
 created  JENKINS-24651


Memory Leak when downloading large file from linked project















Issue Type:


Bug



Affects Versions:


current



Assignee:


Larry Shatzer, Jr.



Components:


maven-deployment-linker



Created:


09/Sep/14 9:01 PM



Description:


We are running Jenkins without any heap specified (we also had 1gb specified and still ran into this issue). 

When trying to download an RPM generated that is just under 170MB in size using the "Get linked maven deployments" build step, the job fails with a heap error.

download maven artifact: http://build/nexus/content/repositories/snapshots/com/xxx/xxx/xxx/7.0.0-SNAPSHOT/xxx-7.0.0-20140905.222907-269-xxx.rpm to /var/www/xxx/xxx/xxx/xxx-7.0.0-20140905.222907-269-xxx.rpm
FATAL: Java heap space
java.lang.OutOfMemoryError: Java heap space
	at org.jboss.netty.buffer.HeapChannelBuffer.(HeapChannelBuffer.java:42)
	at org.jboss.netty.buffer.BigEndianHeapChannelBuffer.(BigEndianHeapChannelBuffer.java:34)
	at org.jboss.netty.buffer.ChannelBuffers.buffer(ChannelBuffers.java:134)
	at org.jboss.netty.buffer.HeapChannelBufferFactory.getBuffer(HeapChannelBufferFactory.java:69)
	at org.jboss.netty.buffer.DynamicChannelBuffer.ensureWritableBytes(DynamicChannelBuffer.java:86)
	at org.jboss.netty.buffer.DynamicChannelBuffer.writeBytes(DynamicChannelBuffer.java:235)
	at org.jboss.netty.buffer.AbstractChannelBuffer.writeBytes(AbstractChannelBuffer.java:441)
	at com.ning.http.client.providers.netty.NettyResponse.getResponseBodyAsStream(NettyResponse.java:106)
	at hudson.plugins.mavendeploymentlinker.MavenDeploymentDownloader.downloadFile(MavenDeploymentDownloader.java:246)
	at hudson.plugins.mavendeploymentlinker.MavenDeploymentDownloader.perform(MavenDeploymentDownloader.java:214)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
	at hudson.model.Build$RunnerImpl.build(Build.java:178)
	at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473)
	at hudson.model.Run.run(Run.java:1410)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:238)

When I examine the Jenkins Monitoring Heap graph, I see that it has spiked up high. If I just leave Jenkins running, the heap continues to rise and never completely GCs. Eventually (after about a day), Jenkins gets so bogged down that it becomes unusable and needs a restart.




Project:


Jenkins



Priority:


Major



Reporter:


Brian Goad

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24604) Polling fails in "node on demand" environments

2014-09-09 Thread ewilt...@gmail.com (JIRA) 














































Elliot Wiltshire
 reopened  JENKINS-24604


Polling fails in "node on demand" environments
















Although I do think this is related to the Jenkins core, and not the Perforce plugin itself, I'm re-opening this and will discuss with other developers. There may be a way to do an SCM poll without a workspace.





Change By:


Elliot Wiltshire
(09/Sep/14 9:01 PM)




Resolution:


Not A Defect





Status:


Closed
Reopened



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception

2014-09-09 Thread meenal.khandel...@cerner.com (JIRA) 














































Meenal Khandelwal
 commented on  JENKINS-23641


Builds are failing due to GitHubCommitNotifier exception















There was nothing different about this branch. It was just a pull request for the same repo in which the branch exist. I had a similar branch which worked just fine.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [maven-deployment-linker] (JENKINS-24651) Memory Leak when downloading large file from linked project

2014-09-09 Thread lar...@gmail.com (JIRA) 















































Larry Shatzer, Jr.
 assigned  JENKINS-24651 to Dominik Bartholdi



Memory Leak when downloading large file from linked project
















Change By:


Larry Shatzer, Jr.
(09/Sep/14 9:06 PM)




Assignee:


Larry Shatzer, Jr.
Dominik Bartholdi



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tasks-plugin] (JENKINS-23635) When Ignore-Case is set, tasks types should be rolled up regardless of case

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-23635


When Ignore-Case is set, tasks types should be rolled up regardless of case















Code changed in jenkins
User: Ulli Hafner
Path:
 src/test/java/plugins/TaskScannerPluginTest.java
http://jenkins-ci.org/commit/acceptance-test-harness/59ecf51ec380d31e880acfdbf16ef2f3e9573c33
Log:
  JENKINS-23635 Update of test case.

Tags are now printed in upper case when ignoreCase is set.





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tasks-plugin] (JENKINS-17225) Allow regular expressions as tags

2014-09-09 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-17225


Allow regular expressions as tags















Code changed in jenkins
User: Ulli Hafner
Path:
 pom.xml
 src/main/java/org/jenkinsci/test/acceptance/plugins/tasks/AbstractTaskScannerBuildSettings.java
 src/test/java/plugins/CheckstylePluginTest.java
 src/test/java/plugins/TaskScannerPluginTest.java
 src/test/resources/tasks_plugin/regexp/pom.xml
 src/test/resources/tasks_plugin/regexp/regexp.txt
http://jenkins-ci.org/commit/acceptance-test-harness/0d9bb7cd3fe6794e89eb4ca6671b5fd715d177e7
Log:
  JENKINS-17225 Added test cases that show that the regexp tags feature works.





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-24648) Git poll always finds changes when there is none when used with Gerrit trigger strategy

2014-09-09 Thread egues...@java.net (JIRA) 














































eguess74
 commented on  JENKINS-24648


Git poll always finds changes when there is none when used with Gerrit trigger strategy















i will try the alternative approach recommended on the gerrit trigger plugin page: " If this does not work for you set Refspec to refs/changes/:refs/changes/ and 'Branches to build' to $GERRIT_REFSPEC."



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24604) Polling fails in "node on demand" environments

2014-09-09 Thread mr...@sjm.com (JIRA) 














































Michael Rose
 commented on  JENKINS-24604


Polling fails in "node on demand" environments















Thanks!



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [master-slave] (JENKINS-5413) SCM polling getting hung

2014-09-09 Thread brian.sm...@novatel.com (JIRA) 














































Brian Smith
 commented on  JENKINS-5413


SCM polling getting hung















I haven't had this issue since we started doing weekly reboots of the whole system (master and nodes).



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception

2014-09-09 Thread david.joel.tan...@gmail.com (JIRA) 














































David Tanner
 commented on  JENKINS-23641


Builds are failing due to GitHubCommitNotifier exception















Was the branch deleted or changed before the build ran or something?  When I first got things running here there were several times that someone would close the PR just after Jenkins picked it up.  But I don't recall this being the error.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24645) Portions of config go missing

2014-09-09 Thread o.v.nenas...@gmail.com (JIRA) 














































Oleg Nenashev
 commented on  JENKINS-24645


Portions of config go missing















Have you seen notifications about "Old data" on ${JENKINS_URL}/manage page?

Most probably, the issue is related to the core update.
"hudson.tools.ZipExtractionInstaller" comes from the core



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24645) Portions of config go missing

2014-09-09 Thread o.v.nenas...@gmail.com (JIRA) 












































  
Oleg Nenashev
 edited a comment on  JENKINS-24645


Portions of config go missing
















Have you seen notifications about "Old data" on ${JENKINS_URL}/manage page?

Most probably, the issue is related to the core update.
"hudson.tools.ZipExtractionInstaller" comes from the core, but there was no changes in it for about 10 months



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-24645) Portions of config go missing

2014-09-09 Thread csui...@gmail.com (JIRA) 














































Chris Suich
 commented on  JENKINS-24645


Portions of config go missing















There is nothing in /manage and I haven't ever seen anything there.

This is a relatively new instance - this setup was fresh installed 2-3 months ago.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  1   2   >