date:20150105
















































Oleg Nenashev
 assigned  JENKINS-24857 to Oleg Nenashev



Builds happening because of false-positive SCM changes
















Change By:


Oleg Nenashev
(05/Jan/15 9:06 AM)




Assignee:


OlegNenashev



























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] [subversion-plugin] (JENKINS-24377) Create Tag (Tag this build) Not working

2015-01-05 Thread r...@kamstrup.dk (JIRA)















































Rasmus Pedersen
 commented on  JENKINS-24377


Create Tag (Tag this build) Not working















Realized that the svn authentication depending on the cached of the svn password stored in the user profile.
Does this mean that the username and password you choose for "Credentials for tagging" has no meaning?



























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] [instant-messaging-plugin] (JENKINS-6560) Plugin should use project.getFullDisplayName() instead of project.getName()

2015-01-05 Thread peter.van.d...@netherlabs.nl (JIRA)















































Peter van Dijk
 reopened  JENKINS-6560


Plugin should use project.getFullDisplayName() instead of project.getName()
















Please reopen for !cb, see comment at https://issues.jenkins-ci.org/browse/JENKINS-6560?focusedCommentId=218649page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-218649





Change By:


Peter van Dijk
(05/Jan/15 11:31 AM)




Resolution:


Fixed





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] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions

2015-01-05 Thread golube...@gmail.com (JIRA)

Valeri Golubev
commented on JENKINS-24338

Issues with docker permissions

I had the same issue, as described earlier, that docker container was successfully running under 'su - jenkins' but failed when executing by script build step.
Versions:
jenkins: 1.555
os: CentOS release 6.6 (Final)
docker: Docker version 1.3.2, build 39fa2fa/1.3.2

I found a work-around, that probably can be helpful to further clarify the issue.

In order to allow jenkins to create and manage docker containers via 'execute script' build step, you can configure docker service to apply 'jenkins' group ownership to the socket, rather than adding jenkins user to the default-used 'docker' group.
This configuration can be achieved by adding the '-G jenkins' arguments to the docker service config file.

For example, on centos6, I updated the following file:
cat /etc/sysconfig/docker

Docker Upstart and SysVinit configuration file

Customize location of Docker binary (especially for development testing).
DOCKER="/usr/bin/docker"
0
Use DOCKER_OPTS to modify the daemon startup options.
DOCKER_OPTS=' --host=unix:///var/run/docker.sock --restart=false -g /opt/app/jenkins/docker -G jenkins'

and it resulted to the following permissions:
srw-rw 1 root jenkins 0 Jan 5 12:22 docker.sock

[JIRA] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions

2015-01-05 Thread golube...@gmail.com (JIRA)

Valeri Golubev
edited a comment on JENKINS-24338

Issues with docker permissions

I found a work-around, that probably can be helpful to further clarify the issue.

For example, on centos6, I updated the following file:

cat /etc/sysconfig/docker

Docker Upstart and SysVinit configuration file

and it resulted to the following permissions:
srw-rw 1 root jenkins 0 Jan 5 12:22 docker.sock

[JIRA] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions

2015-01-05 Thread golube...@gmail.com (JIRA)

Valeri Golubev
edited a comment on JENKINS-24338

Issues with docker permissions

I found a work-around, that probably can be helpful to further clarify the issue.

For example, on centos6, I updated the following file:

cat /etc/sysconfig/docker
# Docker Upstart and SysVinit configuration file

# Customize location of Docker binary (especially for development testing).
DOCKER="/usr/bin/docker"
0
# Use DOCKER_OPTS to modify the daemon startup options.
DOCKER_OPTS=' --host=unix:///var/run/docker.sock --restart=false -g /opt/app/jenkins/docker -G jenkins'

and it resulted to the following permissions:
srw-rw 1 root jenkins 0 Jan 5 12:22 docker.sock

[JIRA] [core] (JENKINS-4501) WorkspaceCleanupThread deletes Matrix project workspaces
















































Daniel Beck
 resolved  JENKINS-4501 as Incomplete


WorkspaceCleanupThread deletes Matrix project workspaces
















Please file a new issue as I requested above. The behavior of workspace cleanup was completely rewritten in 1.551, so whatever's wrong in later versions is likely unrelated to this report.

That said, 1.569 is over half a year old and too old for new issue reports. I hope that's just a typo.

Make sure to create a log recorder for the logger hudson.model.WorkspaceCleanupThread on level ALL to find out what it actually does (https://wiki.jenkins-ci.org/display/JENKINS/Logging). "Deleted all workspaces" doesn't look like the cleanup thread's behavior at all.

Resolving as incomplete again.





Change By:


Daniel Beck
(05/Jan/15 11:51 AM)




Status:


Reopened
Resolved





Resolution:


Incomplete



























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] [jenkins-flowdock] (JENKINS-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException

Daniel Beck
commented on JENKINS-26257

ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException

First off, ALL CAPS TEXT IS CONSIDERED YELLING so stop that. Besides, it's both more difficult to read and unprofessional, making you look like a 12 year old.

Second, you should read and follow the advice of https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue because this report doesn't contain nearly enough information to investigate further. In fact, the little information it contains is partially wrong (Flowdock Plugin and Plugin Usage Plugin have absolutely nothing to do with your problem), which means it's your own fault nobody cares. You addressed the report to completely wrong components.

Third, everyone handling these reports is an unpaid volunteer working in their spare time and under no obligation to do anything. This, combined with the previous two points means that it's unlikely you'll get help here.

There are companies providing paid support for Jenkins (e.g. CloudBees when buying a Jenkins Enterprise subscription). Consider going that route to get guaranteed response times.

[JIRA] [jacoco-plugin] (JENKINS-26254) Jacoco plugin is too slow and occupies too much microprocessor time

2015-01-05 Thread il...@redhat.com (JIRA)















































Ilia Meerovich
 commented on  JENKINS-26254


Jacoco plugin is too slow and occupies too much microprocessor time















OK, I made a little investigation.
It seems that serialization/de-serialisation in https://github.com/jenkinsci/jacoco-plugin/blob/master/src/main/java/hudson/plugins/jacoco/ExecutionFileLoader.java
takes a lot of cpu, also load doesn't not spread evenly on all cores (I used htop).
In our case I'm speaking about ovirt project (~3800 classes).
iftop doesn't shows significant network traffic and iostat also doesn't shows significant load.
So analyse of the same jacoco.exec file on idle jenkins taking 30-50 seconds, but on production jenkins it can take 30-50 minutes.





























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] [junit-plugin] (JENKINS-9980) Add the Publish JUnit test result report option to maven job configuration page

2015-01-05 Thread javier.palac...@fon.com (JIRA)















































Javier Palacios
 commented on  JENKINS-9980


Add the Publish JUnit test result report option to maven job configuration page















We also have this problem. We run the additional tests from a shell buildstep. If the buildstep runs after the maven execution the extra tests are not reported, but if we move the step to pre-build stage, they get properly shown.
The main drawback of this workaround is that 'clean' target cannot be used in the list of maven goals, because it removes the target/surefire-reports directory where the junit reports are copied to.



























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] [workflow-plugin] (JENKINS-26157) Subversion doesn't work correctly

2015-01-05 Thread tg9...@gmx-topmail.de (JIRA)















































Thomas Goeppel
 commented on  JENKINS-26157


Subversion doesnt work correctly















Yes, it does! I had read it before, but one needs to be somewhat familiar with the code to understand the documentation.



























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-plugin] (JENKINS-26286) Can not use token (like WARNINGS_NEW) in pre-send script email

2015-01-05 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-26286


Can not use token (like WARNINGS_NEW) in pre-send script email















I'd take a look at the code for the Warnings Plugin. https://github.com/jenkinsci/warnings-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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page

2015-01-05 Thread svvivekan...@gmail.com (JIRA)















































Vivekanand SV
 updated  JENKINS-26077


Multiple Test Reports Graphs and Links in Job Page
















Change By:


Vivekanand SV
(05/Jan/15 12:34 PM)




Description:


IveupgradedJenkinsfrom1.575to1.594.Afterupdating,thenIopenthejobpage,Isee2graphsandlinksforthetestreports.Thoughtestreportsarecorrectandavailable,thereare2instanceofitpointingtothesameURLs.IusexUnitplugintopublishmyJUnitreportsasIneededawaytochangethebuildstatusbasedonthetestPASS/FAILcountthatIwantedwhichIwasnotabletodoinJUnitplugin.Also,allthebuildsarenotshowninthegraphs.Inthereferenceimageattached,IvebeenusingbothCoberturaandxUnitforallthebuilds,buttestgraphstartsonlyfrombuild#322whileitshouldvestartedfrombuild#291asintheCoberturagraph.Iveattachedthescreenshotofthejobpage
andconfigpage
forreference.
Andtheconfig.xmlhasthefollowingcontentunderthepublisherstagpublishersxunitplugin=xunit@1.90/hudson.plugins.cobertura.CoberturaPublisherplugin=cobertura@1.9.5/hudson.tasks.ArtifactArchiver//publishersRemovedtagcontentsforbrevity.





Attachment:


ScreenShot2014-12-18at10.30.54am.png



























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







-- 
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-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















































Oleg Nenashev
 commented on  JENKINS-26257


ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















+1 regarding Daniel's comments

Regarding the issue...
Probably, it's a bug in remoting layer. Seems the provided stacktrace is incomplete, so it's impossible to find the real cause. 

The core is quite old (1.518), so as a first step I would recommend updating to the latest or latest LTS version.



























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-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















































Oleg Nenashev
 updated  JENKINS-26257


ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException
















Change By:


Oleg Nenashev
(05/Jan/15 12:33 PM)




Component/s:


core





Component/s:


remoting





Component/s:


jenkins-flowdock





Component/s:


plugin-usage-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] [core] (JENKINS-25869) Jenkins is getting crashed and shutting down once in a while

2015-01-05 Thread hvam...@gmail.com (JIRA)















































Vamsi Hari
 updated  JENKINS-25869


Jenkins is getting crashed and shutting down once in a while
















Daniel - I had attached all the info requested by you. FYI, In the job config files i had commented host names and mentioned respective details over there.  





Change By:


Vamsi Hari
(05/Jan/15 12:55 PM)




Attachment:


PortalEXT-EAR-deployment-PEO-config.xml





Attachment:


PortalEXT-myts-static-STATIC-deployment-config.xml





Attachment:


support.zip





Attachment:


SystemInformation[Jenkins].htm



























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-plugin] (JENKINS-26286) Can not use token (like WARNINGS_NEW) in pre-send script email

2015-01-05 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-26286


Can not use token (like WARNINGS_NEW) in pre-send script email















That's correct, you would need to use code to retrieve the warning count.



























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] [findbugs-plugin] (JENKINS-21723) Findbugs plugin uses absolute URL for link to report















































Ulli Hafner
 commented on  JENKINS-21723


Findbugs plugin uses absolute URL for link to report















Does the column that links to the latest stable build work? It also uses a absolute URL: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/views/LastStableColumn/column.jelly



























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] [findbugs-plugin] (JENKINS-21723) Findbugs plugin uses absolute URL for link to report













































 
Ulli Hafner
 edited a comment on  JENKINS-21723


Findbugs plugin uses absolute URL for link to report
















Does the column that links to the latest stable build work? It also uses an absolute URL: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/views/LastStableColumn/column.jelly



























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-25601) JDK9 with jigsaw file layer is not detected as valid JDK

2015-01-05 Thread barb...@irit.fr (JIRA)















































Eric Barboni
 commented on  JENKINS-25601


JDK9 with jigsaw file layer is not detected as valid JDK 















Hi, sorry for the delay.
  I build from source (skipping test because of javassist  jdk 8 ) as I did not find a jenkins.war on the cloudbees jenkins instance.

It's working: JDK 9 folder is detected as jdk, and older jdk 7 or jdk 8 are also detected as jdk



























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-plugin] (JENKINS-26290) Git plugin periodically fails to find commit















































Mark Waite
 commented on  JENKINS-26290


Git plugin periodically fails to find commit















I've seen that message infrequently myself. If you're willing to insert some debugging code into the git plugin and deploy it into your environment where the random failure happens, it could provide deeper understand of the problem.

What I'd suggest (without having written the code):


	Insert additional debug code into the GitException which only executes if the stderr of the exception includes the message "reference is not a tree"
	In that additional debug code, run "git show SHA1-in-the-error"
	In that additional debug code, run "git ls-remote origin SHA1-in-the-error"



I think the intermittent nature of the problem means that you'll need to insert the debug code into your production instance, or you'll need to configure another instance which shows the problem.



























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] [otabuilder-plugin] (JENKINS-26289) Plugin update fails

2015-01-05 Thread ja...@howeswho.co.uk (JIRA)















































James Howe
 created  JENKINS-26289


Plugin update fails















Issue Type:


Bug



Assignee:


Unassigned


Components:


otabuilder-plugin



Created:


05/Jan/15 1:19 PM



Description:


hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/plugins/otabuilder/0.3.1/otabuilder.hpi (redirected to: http://mirrors.jenkins-ci.org/plugins/otabuilder/0.3.1/otabuilder.hpi)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:791)
	at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1138)
	at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1298)
	at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1116)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/plugins/otabuilder/0.3.1/otabuilder.hpi
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
	at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1675)
	at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1673)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1671)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1244)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:756)
	... 7 more
Caused by: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/plugins/otabuilder/0.3.1/otabuilder.hpi
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1624)
	at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2678)
	at java.net.URLConnection.getHeaderFieldLong(URLConnection.java:639)
	at java.net.URLConnection.getContentLengthLong(URLConnection.java:511)
	at java.net.URLConnection.getContentLength(URLConnection.java:495)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:755)
	... 7 more




Project:


Jenkins



Priority:


Major



Reporter:


James Howe

























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-plugin] (JENKINS-26290) Git plugin periodically fails to find commit

2015-01-05 Thread m...@mikemcquaid.com (JIRA)















































Mike McQuaid
 created  JENKINS-26290


Git plugin periodically fails to find commit















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git-plugin



Created:


05/Jan/15 1:26 PM



Description:


Thanks for all your great work with this plugin; not sure how I'd live without it!

Around ~1% of jobs triggered by GitHub pull requests fail to find the merge commit with output like the below. I'd love to help you debug this as it's been driving me mad for a wee while (I don't know why I've only just filed this now). If I immediately rebuild the job then it always works fine so it's a weird intermittent issue. Even a workaround that would let me e.g. retry the Git operations here would be fantastic.

Thanks folks!

Started by upstream project "Homebrew Pull Requests" build number 19312
originally caused by:
 GitHub pull request #35564 of commit 13c8c95db0d399cd387ec362e35d9917df1465f8 automatically merged.
EnvInject - Loading node environment variables.
Building remotely on yosemite in workspace /Users/brew/Jenkins/workspace/Homebrew Pull Requests/version/yosemite
  git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
  git config remote.origin.url https://github.com/Homebrew/homebrew.git # timeout=10
Fetching upstream changes from https://github.com/Homebrew/homebrew.git
  git --version # timeout=10
  git -c core.askpass=true fetch --tags --progress https://github.com/Homebrew/homebrew.git +refs/heads/:refs/remotes/origin/ +refs/pull/:refs/remotes/origin/pr/ # timeout=5
Checking out Revision c1d392f8a050cb7049b3afee8772b34491150e21 (origin/pr/35564/merge)
  git config core.sparsecheckout # timeout=10
  git checkout -f c1d392f8a050cb7049b3afee8772b34491150e21
FATAL: Could not checkout null with start point c1d392f8a050cb7049b3afee8772b34491150e21
hudson.plugins.git.GitException: Could not checkout null with start point c1d392f8a050cb7049b3afee8772b34491150e21
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1674)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
	at ..remote call to yosemite(Native Method)
	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
	at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
	at hudson.remoting.Channel.call(Channel.java:752)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
	at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
	at com.sun.proxy.$Proxy52.execute(Unknown Source)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:992)
	at hudson.scm.SCM.checkout(SCM.java:488)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1257)
	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.matrix.MatrixRun.run(MatrixRun.java:146)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at

[JIRA] [bitbucket-plugin] (JENKINS-24999) Build triggered by SCM change without activating trigger in the job configuration















































SCM/JIRA link daemon
 commented on  JENKINS-24999


Build triggered by SCM change without activating trigger in the job configuration















Code changed in jenkins
User: Felix Belzunce Arcos
Path:
 src/main/java/com/cloudbees/jenkins/plugins/BitBucketTrigger.java
 src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java
http://jenkins-ci.org/commit/bitbucket-plugin/d5e9cb6a15d9ed1e2313fa656a2361170c74042e
Log:
  JENKINS-24999





























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] [bitbucket-plugin] (JENKINS-24999) Build triggered by SCM change without activating trigger in the job configuration















































SCM/JIRA link daemon
 commented on  JENKINS-24999


Build triggered by SCM change without activating trigger in the job configuration















Code changed in jenkins
User: Nicolas De loof
Path:
 src/main/java/com/cloudbees/jenkins/plugins/BitBucketTrigger.java
 src/main/java/com/cloudbees/jenkins/plugins/BitbucketHookReceiver.java
http://jenkins-ci.org/commit/bitbucket-plugin/3e96df05dbf8d8e3a0b896c18f28a48b3fcd2c97
Log:
  Merge pull request #4 from fbelzunc/JENKINS-24999

Fixed JENKINS-24999 Build triggered by SCM change without activating trigger in the job configuration


Compare: https://github.com/jenkinsci/bitbucket-plugin/compare/a035a1b8b27a...3e96df05dbf8




























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-plugin] (JENKINS-26286) Can not use token (like WARNINGS_NEW) in pre-send script email

2015-01-05 Thread ktou...@free.fr (JIRA)













































 
Kristel Touron
 updated  JENKINS-26286


Can not use token (like WARNINGS_NEW) in pre-send script email
















Do you have any idea where is the info stored? 
I can't find any work around in Google.



























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-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587

2015-01-05 Thread clifford...@gmail.com (JIRA)















































Clifford Sanders
 commented on  JENKINS-26048


Jenkins no longer cleaning up child processes when build stopped - as of 1.587















One of our maven jobs aborts because of a timeout during a test but the process on the slave is never stopped.

I created a freestyle job with an 'Invoke top-level Maven targets' build step. When the job aborts the process on the slave is also stopped.

During the holidays we updated from 1.574 to 1.594



























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-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException

2015-01-05 Thread swapnils...@gmail.com (JIRA)















































swapnil soor
 commented on  JENKINS-26257


ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















Sorry for irritation caused due to cap letter , I had no intentions to do so. I do understand being this a free service nobody is obliged to provide guaranteed response. But most of the time I found good solutions by the experts here only.

Anyways thanks for the response Daniel. I will change the component to core, thanks!

@Oleg, Sorry the Jenkins Version Used is: 1.588, we had upgraded this recently. I have provided only the error snippet, may be I might have missed in our setup which is leading to this error, any clue/pointer in debuging would be helpful.

Since it was throwing the exception in hudson packages, I thought its a coding bug. On jenkins console I am getting below exception though the build is successful, right after Maven Build Success message.
Error is repetitive hence didn't posted the whole thread:

INFO Final Memory: 245M/562M
INFO 
ERROR: Asynchronous execution failure
java.util.concurrent.ExecutionException: java.lang.ClassCastException
	at hudson.remoting.Channel$3.adapt(Channel.java:784)
	at hudson.remoting.Channel$3.adapt(Channel.java:779)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
	at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:143)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	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 java.lang.Thread.run(Thread.java:701)
Caused by: java.lang.ClassCastException
	line no..21
	..
	..
	line no..2020
ERROR: Asynchronous execution failure
java.util.concurrent.ExecutionException: java.lang.ClassCastException
	at hudson.remoting.Channel$3.adapt(Channel.java:784)
	at hudson.remoting.Channel$3.adapt(Channel.java:779)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
	at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:143)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	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 java.lang.Thread.run(Thread.java:701)
Caused by: java.lang.ClassCastException
	at .(Unknown Source)
	at ..remote call to channel(Native Method)
	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
	at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
	at hudson.remoting.Channel$3.adapt(Channel.java:782)
	... 14 more
ERROR: Asynchronous execution failure
java.util.concurrent.ExecutionException: java.lang.ClassCastException
	at hudson.remoting.Channel$3.adapt(Channel.java:784)
	at hudson.remoting.Channel$3.adapt(Channel.java:779)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
	at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:143)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at

[JIRA] [git-plugin] (JENKINS-26290) Git plugin periodically fails to find commit













































 
Mark Waite
 edited a comment on  JENKINS-26290


Git plugin periodically fails to find commit
















I've seen that message infrequently myself. If you're willing to insert some debugging code into the git plugin and deploy it into your environment where the random failure happens, it could provide deeper understanding of the problem.

What I'd suggest (without having written the code):


	Insert additional debug code into the GitException which only executes if the stderr of the exception includes the message "reference is not a tree"
	In that additional debug code, run "git show SHA1-in-the-error"
	In that additional debug code, run "git ls-remote origin SHA1-in-the-error"



I think the intermittent nature of the problem means that you'll need to insert the debug code into your production instance, or you'll need to configure another instance which shows the problem.



























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-plugin] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587















































Daniel Beck
 updated  JENKINS-26048


Jenkins no longer cleaning up child processes when build stopped - as of 1.587
















Comment indicates this issue is specific to the Maven project type.





Change By:


Daniel Beck
(05/Jan/15 2:32 PM)




Component/s:


maven-plugin





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] [git-plugin] (JENKINS-26290) Git plugin periodically fails to find commit

2015-01-05 Thread m...@mikemcquaid.com (JIRA)















































Mike McQuaid
 commented on  JENKINS-26290


Git plugin periodically fails to find commit















I'm willing to insert that code, yeh. Longer-term I'd also be happy with just a retry on this too.



























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-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















































Daniel Beck
 commented on  JENKINS-26257


ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException















Make sure the slave.jar on the slaves is up to date. VersionColumn Plugin can help you with that. SSH Slaves take care of this automatically, but if you're launching using a different mechanism, that may be a problem.



























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] [scm-sync-configuration-plugin] (JENKINS-24621) Footer shadows save button on job config

2015-01-05 Thread aforlo...@gmail.com (JIRA)















































Anthony Forloney
 commented on  JENKINS-24621


Footer shadows save button on job config















This problem also exists without the SCM Sync Plugin installed.



























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-25869) Jenkins is getting crashed and shutting down once in a while















































Daniel Beck
 commented on  JENKINS-25869


Jenkins is getting crashed and shutting down once in a while















I'd try to make sure to unset the http_proxy and related environment variables before starting the Jenkins process (or rather Tomcat in your case?), instead (if necessary) using proxy configuration in Jenkins (Manage Jenkins » Manage Plugins » Advanced). This may result in child processes (e.g. shell scripts and the tools they run) not inheriting the proxy configuration by default though.

The bug may well be in the gconf (Gnome) library or the JDK, as that's where the crash occurs.
http://hg.openjdk.java.net/jdk7u/jdk7u/jdk/file/54acd5cd0485/src/solaris/native/sun/net/spi/DefaultProxySelector.c#l155

Please also note that the user and password to the proxy are included in plain text in the support bundle (nodes/master/environment.txt), so you should change those now.



























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







-- 
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] [ec2-plugin] (JENKINS-15078) Be able to set Instance Name

2015-01-05 Thread bosox...@gmail.com (JIRA)















































Jay Perry
 commented on  JENKINS-15078


Be able to set Instance Name















Any way to get the Name tag set in aws so when I go to the aws console I can tell what agents are what?



























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] [ec2-plugin] (JENKINS-15078) Be able to set Instance Name

2015-01-05 Thread bosox...@gmail.com (JIRA)













































 
Jay Perry
 edited a comment on  JENKINS-15078


Be able to set Instance Name
















Any way to get the Name tag set in aws so when I go to the aws console I can tell what agents are what?  It seems you can add a tag in Jenkins after the node is up but I would like to have any instances created as part of a cloud profile to get a particular aws tag.  Is this supported?



























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] [ec2-plugin] (JENKINS-15078) Be able to set Instance Name

2015-01-05 Thread bosox...@gmail.com (JIRA)















































Jay Perry
 commented on  JENKINS-15078


Be able to set Instance Name















Nevermind, I was able to find Tags in the Advanced section.



























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] [dashboard-view-plugin] (JENKINS-19634) Test Statistic Grid: not sorting by percentage correctly

2015-01-05 Thread shawn.mccart...@gmail.com (JIRA)















































Shawn McCarthy
 commented on  JENKINS-19634


Test Statistic Grid: not sorting by percentage correctly















I created a pull request for this : https://github.com/jenkinsci/jenkins/pull/1509 . I attached the screenshots in the pull request as well. I updated sortable.js to check for data that ends with % , and sort it just like currency (remove all characters except 0-9 and '.'). This doesn't take into consideration if the percentage is 100% or 0% (treats it as 100 and 0 respectively).



























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-plugin] (JENKINS-26293) email-ext-plugin FILE token macro apostrophe escaping

2015-01-05 Thread denisblanche...@gmail.com (JIRA)

Denis Blanchette
created JENKINS-26293

email-ext-plugin FILE token macro apostrophe escaping

Issue Type:

Bug

Assignee:

Alex Earl

Components:

email-ext-plugin

Created:

05/Jan/15 4:36 PM

Description:

I have a job that sends an HTML e-mail with the email-ext-plugin.

The content is configured as such :
${FILE, path="MyFile.html"}

Where MyFile.html is generated from a Python script.

There is an apostrophe in the content of the file. Before the latest update to email-ext-plugin it was displayed "'". Now it is displayed "" in the email client (tested on OWA and Outlook).

The change seems to be related to this line : https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/java/hudson/plugins/emailext/plugins/CssInliner.java#L78
The added .escapeMode(Entities.EscapeMode.xhtml)) changes the apostrophe to it's ampersand escaped version.

There is probably a good reason why this line was modified in the first place, but I wonder if there would be a way to make it work on my end. Maybe make the escaping mode configurable?

Thank you

Environment:

Email Extension Plugin 2.39, Token Macro 1.10, Jenkins 1.580.2. Windows Server 2012

Project:

Jenkins

Labels:

email-ext

Priority:

Minor

Reporter:

Denis Blanchette

[JIRA] [core] (JENKINS-26294) WARNING: 'stapler-class' is deprecated is shown on almost every extension















































Ulli Hafner
 created  JENKINS-26294


WARNING: stapler-class is deprecated is shown on almost every extension















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


05/Jan/15 4:38 PM



Description:


Due to commit https://github.com/stapler/stapler/commit/82b0a45924b083796d04c94661bbef7b80e2d2bf the Jenkins log fills with a lot of messages. Seems that almost every plug-in/extension is affected. 

Example log:
https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/lastCompletedBuild/testReport/plugins/CheckStylePluginTest/should_collect_warnings_in_build/

In my plug-ins I don't use stapler-class explicitely, this is something inherited from core. So it is not clear what to do as a plg-in developer.




Project:


Jenkins



Priority:


Minor



Reporter:


Ulli Hafner

























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-26294) WARNING: 'stapler-class' is deprecated is shown for almost every extension















































Ulli Hafner
 updated  JENKINS-26294


WARNING: stapler-class is deprecated is shown for almost every extension
















Change By:


Ulli Hafner
(05/Jan/15 4:39 PM)




Summary:


WARNING:stapler-classisdeprecatedisshown
on
for
almosteveryextension



























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-26294) WARNING: 'stapler-class' is deprecated is shown for almost every extension















































Ulli Hafner
 updated  JENKINS-26294


WARNING: stapler-class is deprecated is shown for almost every extension
















Change By:


Ulli Hafner
(05/Jan/15 4:42 PM)




Description:


Duetocommithttps://github.com/stapler/stapler/commit/82b0a45924b083796d04c94661bbef7b80e2d2bftheJenkinslogfillswithalotofmessages.Seemsthatalmosteveryplug-in/extensionisaffected.Examplelog:https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/lastCompletedBuild/testReport/plugins/CheckStylePluginTest/should_collect_warnings_in_build/Inmyplug-insIdontusestapler-classexplicitely,thismightbesomethinginheritedfromcore.Soitisnotclearwhattodoasaplug-indeveloper.IsthereanythingIcandohereinmyplug-in?Oneaffectedplug-inischeckstyle:hereIgetthemessagesfor{noformat}master54521|WARNING:stapler-classisdeprecated:hudson.plugins.checkstyle.CheckStylePublishermaster52856|WARNING:stapler-classisdeprecated:hudson.plugins.checkstyle.CheckStyleColumn

{noformat}



























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-26294) WARNING: 'stapler-class' is deprecated is shown for almost every extension















































Ulli Hafner
 updated  JENKINS-26294


WARNING: stapler-class is deprecated is shown for almost every extension
















Change By:


Ulli Hafner
(05/Jan/15 4:41 PM)




Description:


Duetocommithttps://github.com/stapler/stapler/commit/82b0a45924b083796d04c94661bbef7b80e2d2bftheJenkinslogfillswithalotofmessages.Seemsthatalmosteveryplug-in/extensionisaffected.Examplelog:https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/lastCompletedBuild/testReport/plugins/CheckStylePluginTest/should_collect_warnings_in_build/Inmyplug-insIdontusestapler-classexplicitely,this
is
mightbe
somethinginheritedfromcore.Soitisnotclearwhattodoasa
plg
plug
-indeveloper.
IsthereanythingIcandohereinmyplug-in?Oneaffectedplug-inischeckstyle:hereIgetthemessagesfor{noformat}master54521|WARNING:stapler-classisdeprecated:hudson.plugins.checkstyle.CheckStylePublishermaster52856|WARNING:stapler-classisdeprecated:hudson.plugins.checkstyle.CheckStyleColumn{noformat}



























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] [perforce-plugin] (JENKINS-25830) Since upgrading to 1.590 the Max # of builds to keep with artifacts option does not seem to work















































Oleg Nenashev
 commented on  JENKINS-25830


Since upgrading to 1.590 the Max # of builds to keep with artifacts option does not seem to work















No problem. 1.3.29 was quite unstable due to my changes in variables substitution engine. It may affect the log rotation if Jenkins tries to clean a job's workspace from it. 

Please re-open the issue if it happens again



























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] [perforce-plugin] (JENKINS-25830) Since upgrading to 1.590 the Max # of builds to keep with artifacts option does not seem to work
















































Oleg Nenashev
 resolved  JENKINS-25830 as Cannot Reproduce


Since upgrading to 1.590 the Max # of builds to keep with artifacts option does not seem to work
















Change By:


Oleg Nenashev
(05/Jan/15 4:34 PM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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-plugin] (JENKINS-26293) email-ext-plugin FILE token macro apostrophe escaping

2015-01-05 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-26293


email-ext-plugin FILE token macro apostrophe escaping















I actually have a different fix for this already for the next release.



























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] [xcode-plugin] (JENKINS-26295) Parsing issue due to unit test made with Swift

2015-01-05 Thread clem...@omsignal.com (JIRA)















































Clem Jan
 created  JENKINS-26295


Parsing issue due to unit test made with Swift















Issue Type:


Bug



Assignee:


Unassigned


Components:


xcode-plugin



Created:


05/Jan/15 4:55 PM



Description:


(Using jenkins Xcode plugin)
I tried with Objective C unit test and it is working. But when we are running Swift unit tests we have this issue :

Test Case '-OMPlus_DemoTests.OMSWorkoutReportProjectorTests testZeroesDontContributeToAggregates' started.
/Users/builder/.jenkins/jobs/project/workspace/projectName/OMPlus-Demo-Tests/OMSWorkoutReportProjectorTests.swift:256: error: -OMPlus_DemoTests.OMSWorkoutReportProjectorTests testZeroesDontContributeToAggregates : XCTAssertEqual failed: ("18") is not equal to ("15") - peak HR from second workout
FATAL: Log statements out of sync: current test suite was 'OMSWorkoutReportProjectorTests' and not 'OMPlus_DemoTests.OMSWorkoutReportProjectorTests'

Do you have a fix in progress for this issue ?




Project:


Jenkins



Priority:


Blocker



Reporter:


Clem Jan

























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/dry/DryAnnotationsAggregator.java
 src/main/java/hudson/plugins/dry/DryMavenResult.java
 src/main/java/hudson/plugins/dry/DryMavenResultAction.java
 src/main/java/hudson/plugins/dry/DryPublisher.java
 src/main/java/hudson/plugins/dry/DryReporter.java
 src/main/java/hudson/plugins/dry/DryReporterResult.java
 src/main/java/hudson/plugins/dry/DryResult.java
 src/main/java/hudson/plugins/dry/MavenDryResultAction.java
http://jenkins-ci.org/commit/dry-plugin/ee4a8b6203a4caf10855dd8ddf5341a6f55e08ee
Log:
  FIXED JENKINS-13458 Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 .idea/codeStyleSettings.xml
 .idea/libraries/Maven__org_jvnet_hudson_plugins_analysis_core_1_65.xml
 .idea/libraries/Maven__org_jvnet_hudson_plugins_analysis_test_1_11.xml
 analysis-collector
 analysis-core
 dry
 pmd
 tasks
 warnings
http://jenkins-ci.org/commit/analysis-suite-plugin/43474638ad5a84ca7d9a697a1ad9d19119f603b1
Log:
  FIXED JENKINS-13458 Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/warnings/WarningsAnnotationsAggregator.java
 src/main/java/hudson/plugins/warnings/WarningsBuildHistory.java
 src/main/java/hudson/plugins/warnings/WarningsProjectAction.java
 src/main/java/hudson/plugins/warnings/WarningsPublisher.java
 src/main/java/hudson/plugins/warnings/WarningsResult.java
 src/test/java/hudson/plugins/warnings/WarningsPublisherTest.java
http://jenkins-ci.org/commit/warnings-plugin/96c2df676a21dc3c3368f8e91e7c188d2946403e
Log:
  FIXED JENKINS-13458 Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsAnnotationsAggregator.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsMavenResult.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsMavenResultAction.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsPublisher.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporter.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporterResult.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsResult.java
 plugin/src/main/java/hudson/plugins/findbugs/MavenFindBugsResultAction.java
http://jenkins-ci.org/commit/findbugs-plugin/2b0b1b8d1b3da6fdb454b4e3caabce62e22c8a7d
Log:
  FIXED JENKINS-13458 Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 checkstyle.iml
 pom.xml
 src/main/java/hudson/plugins/checkstyle/CheckStyleAnnotationsAggregator.java
 src/main/java/hudson/plugins/checkstyle/CheckStyleMavenResult.java
 src/main/java/hudson/plugins/checkstyle/CheckStyleMavenResultAction.java
 src/main/java/hudson/plugins/checkstyle/CheckStylePublisher.java
 src/main/java/hudson/plugins/checkstyle/CheckStyleReporter.java
 src/main/java/hudson/plugins/checkstyle/CheckStyleReporterResult.java
 src/main/java/hudson/plugins/checkstyle/CheckStyleResult.java
 src/main/java/hudson/plugins/checkstyle/MavenCheckStyleResultAction.java
 src/main/java/hudson/plugins/checkstyle/parser/CheckStyleParser.java
 src/test/java/hudson/plugins/checkstyle/parser/CheckStyleParserTest.java
 src/test/resources/hudson/plugins/checkstyle/parser/checkstyle-result-build1.xml
 src/test/resources/hudson/plugins/checkstyle/parser/checkstyle-result-build2.xml
 src/test/resources/hudson/plugins/checkstyle/parser/checkstyle-result-build3.xml
 src/test/resources/hudson/plugins/checkstyle/parser/checkstyle-result-build4.xml
http://jenkins-ci.org/commit/checkstyle-plugin/369e5fb065dc8fa3137f0c9016451d3e11a8f5fc
Log:
  FIXED JENKINS-13458 Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 pmd.iml
 pom.xml
 src/main/java/hudson/plugins/pmd/PmdAnnotationsAggregator.java
 src/main/java/hudson/plugins/pmd/PmdMavenResult.java
 src/main/java/hudson/plugins/pmd/PmdMavenResultAction.java
 src/main/java/hudson/plugins/pmd/PmdPublisher.java
 src/main/java/hudson/plugins/pmd/PmdReporter.java
 src/main/java/hudson/plugins/pmd/PmdReporterResult.java
 src/main/java/hudson/plugins/pmd/PmdResult.java
 src/main/java/hudson/plugins/pmd/parser/PmdParser.java
http://jenkins-ci.org/commit/pmd-plugin/bf11ab5a02fdbbae20a7503fad468723f6bee29b
Log:
  FIXED JENKINS-13458 Added an option to use previous build as a reference.





























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-21341) Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int)















































Jesse Glick
 commented on  JENKINS-21341


Job failure on remote node running JDK1.8 - java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int)















Pity this was not backported to the 1.554.x line.



























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/tasks/MavenTasksResultAction.java
 src/main/java/hudson/plugins/tasks/TasksAnnotationsAggregator.java
 src/main/java/hudson/plugins/tasks/TasksMavenResult.java
 src/main/java/hudson/plugins/tasks/TasksMavenResultAction.java
 src/main/java/hudson/plugins/tasks/TasksPublisher.java
 src/main/java/hudson/plugins/tasks/TasksReporter.java
 src/main/java/hudson/plugins/tasks/TasksReporterResult.java
 src/main/java/hudson/plugins/tasks/TasksResult.java
http://jenkins-ci.org/commit/tasks-plugin/0ae7469b4f68430d7c2d29567fb80ef41819b989
Log:
  FIXED JENKINS-13458 Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/analysis/core/AbstractAnnotationParser.java
 src/main/java/hudson/plugins/analysis/core/BuildHistory.java
 src/main/java/hudson/plugins/analysis/core/BuildResult.java
 src/main/java/hudson/plugins/analysis/core/HealthAwarePublisher.java
 src/main/java/hudson/plugins/analysis/core/HealthAwareRecorder.java
 src/main/java/hudson/plugins/analysis/core/HealthAwareReporter.java
 src/main/resources/util/thresholds.jelly
 src/main/resources/util/thresholds.properties
 src/main/resources/util/thresholds_de.properties
 src/test/java/hudson/plugins/analysis/core/BuildHistoryTest.java
http://jenkins-ci.org/commit/analysis-core-plugin/1a2ebe2a80da6cdf429a442cc3b2be8494337441
Log:
  FIXED JENKINS-13458 Added an option to use previous build as a reference.





























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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build















































SCM/JIRA link daemon
 commented on  JENKINS-13458


Add switch to set reference build always as the latest build















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/analysis/collector/AnalysisAnnotationsAggregator.java
 src/main/java/hudson/plugins/analysis/collector/AnalysisPublisher.java
 src/main/java/hudson/plugins/analysis/collector/AnalysisResult.java
http://jenkins-ci.org/commit/analysis-collector-plugin/8c4ac1d376dfa056f60c7968d426a7a0aed0982d
Log:
  FIXED JENKINS-13458 Added an option to use previous build as a reference.





























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-26294) WARNING: 'stapler-class' is deprecated is shown for almost every extension
















































Daniel Beck
 resolved  JENKINS-26294 as Duplicate


WARNING: stapler-class is deprecated is shown for almost every extension
















https://github.com/jenkinsci/jenkins/pull/1443 will fix this.





Change By:


Daniel Beck
(05/Jan/15 5:41 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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







-- 
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] [matrix-project-plugin] (JENKINS-5794) cannot kill master matrix build job unless all sub-jobs are individually killed
















































Oliver Gondža
 resolved  JENKINS-5794 as Fixed


cannot kill master matrix build job unless all sub-jobs are individually killed
















Closing as this works in modern Jenkins.





Change By:


Oliver Gondža
(05/Jan/15 10:51 PM)




Status:


Open
Resolved





Assignee:


abayer





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] [workflow-plugin] (JENKINS-26300) CPS interpreter fails on calls to find(), findAll() default methods

2015-01-05 Thread a...@bedatadriven.com (JIRA)















































Alexander Bertram
 created  JENKINS-26300


CPS interpreter fails on calls to find(), findAll() default methods















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


workflow-plugin



Created:


05/Jan/15 9:29 PM



Description:


The CPS interpreter does not translate calls to .find() , .findAll() default methods correctly.

The following test case fails:

assert evalCPS("[1,2,3].find { it  1 }") == 2


I see that groovy-cps has an CpsDefaultGroovyMethods class that provides an alternate implementation of each(). Does this mean that all methods that accept a closure as an argument will also fail?




Project:


Jenkins



Priority:


Major



Reporter:


Alexander Bertram

























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] [matrix-project-plugin] (JENKINS-3491) Verbose configuration info for multi-config jobs
















































Oliver Gondža
 resolved  JENKINS-3491 as Fixed


Verbose configuration info for multi-config jobs
















Closing as out of date. Note sure about 2009 (when this issue was created) but with modern Jenkins one can use labels (or label expressions) as matrix axes and even when your slave names does not say much, label names should.





Change By:


Oliver Gondža
(05/Jan/15 9:37 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







-- 
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-26277) Memory leak

2015-01-05 Thread ma...@ooyala.com (JIRA)

Mario Rincon
updated JENKINS-26277

Memory leak

The title of this bug was "Memory leak and long operation pauses".

We are confident that we found the reason for the sluggishness and had nothing to do with Jenkins. i've updated the title accordingly.

We do still have the problem of the memory leak.

Change By:

Mario Rincon
(05/Jan/15 11:03 PM)

Summary:

Memoryleak
andlongoperationpauses

Description:

FromthemomentJenkinsisstartedup,itbeginsconsumingRAMslowly.Afterseveralhours(~18h),thememoryistotallyconsumed.
Additionally,formostGUIactivitiesJenkinsisveryslow.Listingtheinstalledplugins,forexample,takesseveral(+5)minutes.Showingaviewsimpleneverhappens;itkeepsloadingthepageforever.

OthertwoJavaprocessesarerunningonthismachine.
Wehave23slaves.9ofthemareinofflinestatus.Wehaveabuildqueueof~30jobsalways;someofthesejobsdontgoupbecausetheirassignedhostsareoffline.Idontknowifthismatters.

[JIRA] [core] (JENKINS-26277) Memory leak

2015-01-05 Thread ma...@ooyala.com (JIRA)















































Mario Rincon
 commented on  JENKINS-26277


Memory leak















Dan,

Thanks. yes, I updated the same file twice. My mistake. I'll also send next report as txt file or another format.



























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] [matrix-project-plugin] (JENKINS-8506) Matrix 'Job of Jobs'















































Oliver Gondža
 commented on  JENKINS-8506


Matrix Job of Jobs















There are several ways to implement this, including https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin. Resolving as matrix is not an optimal solution here.



























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-26298) Console output does not scroll anymore















































Daniel Beck
 updated  JENKINS-26298


Console output does not scroll anymore
















The changes to style.css in https://github.com/jenkinsci/jenkins/compare/jenkins-1.594...jenkins-1.596 are the culprit for the scroll issue.

Assigning to Tom FENNELLY as he'll know best how to resolve this.





Change By:


Daniel Beck
(05/Jan/15 10:31 PM)




Assignee:


TomFENNELLY



























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-plugin] (JENKINS-25586) Build Failed when triggered from VisualStudio.com Web Hooks

2015-01-05 Thread lanc...@gmail.com (JIRA)















































Lance Hambling
 commented on  JENKINS-25586


Build Failed when triggered from VisualStudio.com Web Hooks















On further inspection this can be avoided by unchecking the "Notify Build Start" option in the "Slack Notifications" settings for the project. This obviously removes the functionality to post notifications to Slack when a build starts 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] [junit-plugin] (JENKINS-26276) Expose JUnit test results to workflow scripts















































Jesse Glick
 started work on  JENKINS-26276


Expose JUnit test results to workflow scripts
















Change By:


Jesse Glick
(05/Jan/15 10:34 PM)




Status:


Open
InProgress



























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] [junit-plugin] (JENKINS-26276) Expose JUnit test results to workflow scripts
















































Jesse Glick
 assigned  JENKINS-26276 to Alexander Bertram



Expose JUnit test results to workflow scripts
















Change By:


Jesse Glick
(05/Jan/15 10:34 PM)




Assignee:


JesseGlick
AlexanderBertram



























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] [workflow-plugin] (JENKINS-26157) Subversion doesn't work correctly















































Jesse Glick
 commented on  JENKINS-26157


Subversion doesnt work correctly















PRs to clarify documentation would be welcome. Possibly TUTORIAL.md needs to be clearer about the fact that polling (incl. commit notification endpoints)  changelogs run using whatever SCM definitions were encountered in the last 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] [core] (JENKINS-26298) Console output does not scroll anymore















































Daniel Beck
 commented on  JENKINS-26298


Console output does not scroll anymore















Confirmed. Do you know what the last version was when this worked?



























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-26298) Console output does not scroll anymore

2015-01-05 Thread klemens.ed...@lunifera.com (JIRA)















































Klemens Edler
 commented on  JENKINS-26298


Console output does not scroll anymore















Thanks for busying yourself with this minor issue!

I upgraded from 1.594 where it worked as desired.



























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] [workflow-plugin] (JENKINS-26300) CPS interpreter fails on calls to find(), findAll() default methods
















































Jesse Glick
 assigned  JENKINS-26300 to Kohsuke Kawaguchi



CPS interpreter fails on calls to find(), findAll() default methods
















Change By:


Jesse Glick
(05/Jan/15 10:16 PM)




Assignee:


JesseGlick
KohsukeKawaguchi



























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] [workflow-plugin] (JENKINS-26267) Workflow plugin fails to archive files due to java.lang.NoClassDefFoundError















































Jesse Glick
 commented on  JENKINS-26267


Workflow plugin fails to archive files due to java.lang.NoClassDefFoundError















Yes, that is using a different code path (avoiding the custom step).



























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] [workflow-plugin] (JENKINS-26192) Add support for Grape (@Grab) in workflow scripts















































Jesse Glick
 commented on  JENKINS-26192


Add support for Grape (@Grab) in workflow scripts















For the case of web service client libraries, again I do not think you want to run these as plain blocking Java calls (for example using an existing grape) because they involve network I/O which would block the CPS VM thread and not survive interruption. You could write a Step using asynchronous I/O. Or you could use DurableTaskStep, such as simply via sh, or perhaps we need a variant that runs the local JRE/bin/java with a main class, or runs a forked groovy interpreter, etc.

I had no particular plans for cross-server code reuse other than via plugins with steps. The GroovyShellDecorator extension point allows other options. If Grape supports Groovy-source-based libraries then supporting it from Workflow would presumably work via this extension point.



























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-26277) Memory leak

2015-01-05 Thread ma...@ooyala.com (JIRA)













































 
Mario Rincon
 edited a comment on  JENKINS-26277


Memory leak
















The title of this bug was "Memory leak and long operation pauses". 

We are confident that we found the reason for the sluggishness and had nothing to do with Jenkins. i've updated the title and description accordingly.

We do still have the problem of the memory leak.




























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-26277) Memory leak















































Daniel Beck
 commented on  JENKINS-26277


Memory leak















To clarify, it's still OOM crashing regularly?



























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-22275) Save of job configuration doesn't work after removing a parameter under 'This build is parameterized'
















































Daniel Beck
 resolved  JENKINS-22275 as Duplicate


Save of job configuration doesnt work after removing a parameter under This build is parameterized
















Cannot reproduce the issue on a pristine instance of 1.596 with Chrome 39, therefore resolving again. Note that nightly, alpha, beta, or Canary versions of browsers are not supported, see https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix

Please read https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue and file a new issue that can be investigated independently from this one (i.e. let's not spam the watchers), as the problem you're experiencing seems to only occur on some circumstances.





Change By:


Daniel Beck
(05/Jan/15 9:34 PM)




Status:


Reopened
Resolved





Resolution:


Duplicate



























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







-- 
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] [matrix-project-plugin] (JENKINS-8439) Pick Nodes using Multiple Labels
















































Oliver Gondža
 resolved  JENKINS-8439 as Fixed


Pick Nodes using Multiple Labels
















This can be addressed using label _expression_ axis.





Change By:


Oliver Gondža
(05/Jan/15 10:19 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] [junit-plugin] (JENKINS-26276) Expose JUnit test results to workflow scripts















































Jesse Glick
 commented on  JENKINS-26276


Expose JUnit test results to workflow scripts















There seems to be an issue with the commit status

Yes, the plugin handling PRs got broken by some change on GitHub (I think); we are waiting for Kohsuke Kawaguchi to fix it.



























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-plugin] (JENKINS-26290) Git plugin periodically fails to find commit















































Mark Waite
 commented on  JENKINS-26290


Git plugin periodically fails to find commit















The last retry logic change I submitted made things worse rather than better. I submitted JENKINS-26225 to remind me that it needs to be fixed, and to remind me that I need to write more automated tests surrounding retry logic.



























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] [findbugs-plugin] (JENKINS-21723) Findbugs plugin uses absolute URL for link to report















































Mark Waite
 commented on  JENKINS-21723


Findbugs plugin uses absolute URL for link to report















In my ssh tunnel environment, when I add a column to my view for "Last Stable", it works fine through the ssh tunnel.



























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] [jacoco-plugin] (JENKINS-23066) Allow cleaning up parts of Jacoco report artifcats retained

2015-01-05 Thread devm...@gmail.com (JIRA)















































Andrew Harris
 commented on  JENKINS-23066


Allow cleaning up parts of Jacoco report artifcats retained















I have the exact use-case described here. I don't want to keep all of the Jacoco artifacts, but I do want to maintain a long-term coverage graph. I can't find a good way to do this without a slightly dangerous shell script. Having the option to remove Jacoco artifacts after publishing would be great.



























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-plugin] (JENKINS-26296) Fix for null pointer exception when user enters github url with wrong format

2015-01-05 Thread a...@alexrothenberg.com (JIRA)















































alex rothenberg
 created  JENKINS-26296


Fix for null pointer exception when user enters github url with wrong format















Issue Type:


Bug



Assignee:


Sam Kottler



Components:


github-oauth-plugin



Created:


05/Jan/15 6:12 PM



Description:


When a user enters a github url with a bad format the gitub-oauth-plugin would throw a null pointer exception breaking the jenkins UI for the homepage.

Now it checks for the null and will treat that job as forbidden so not shown.

Fix is in Github PR - https://github.com/jenkinsci/github-oauth-plugin/pull/32 




Project:


Jenkins



Priority:


Major



Reporter:


alex rothenberg

























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] [labeled-test-groups-publisher-plugin] (JENKINS-13376) Ability to add in new groups of test types

2015-01-05 Thread lbordow...@yahoo-inc.com (JIRA)
















































Larry Bordowitz
 resolved  JENKINS-13376 as Fixed


Ability to add in new groups of test types
















Let me know if this works alright. The fix should provide backwards compatibility, so it shouldn't interfere with previous versions if you upgrade it.





Change By:


Larry Bordowitz
(05/Jan/15 6:11 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] [core] (JENKINS-26292) Symlinks unter builds (lastSuccessfulBuild, lastFailedBuild, buidlNum, etc) are not working in a shared folder















































Daniel Beck
 commented on  JENKINS-26292


Symlinks unter builds (lastSuccessfulBuild, lastFailedBuild, buidlNum, etc) are not working in a shared folder















Directory junctions are probably considered directories by Java, which means they're indistinguishable from folders, making a complete mess of everything.



























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] [labeled-test-groups-publisher-plugin] (JENKINS-13376) Ability to add in new groups of test types