date:20150325
















































Night Wolf
 resolved  JENKINS-27264 as Fixed


Latest 1.5 SBT Plugin does not work
















Run hudson.model.DownloadService.Downloadable.all().each { it.updateNow() }  in script console to update the list 





Change By:


Night Wolf
(26/Mar/15 5:11 AM)




Status:


Open
Resolved





Assignee:


uzilan
Night Wolf





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] [sbt-plugin] (JENKINS-27612) SBT Install from scala-sbt.org is very out of date

Night Wolf
updated JENKINS-27612

SBT Install from scala-sbt.org is very out of date

Change By:

Night Wolf
(26/Mar/15 5:10 AM)

Description:

I have a simple Jenkins server running Ubuntu. Just building off master.
The
auto install
list of plugins
from scala-sbt.org
does not work
is super out dated
.
In the logs I just see;Invalid tool ID
The most recent version was
0.13.
7[chot-bi-build] $ java -Xms512m -Xmx512m -XX:ReservedCodeCacheSize=128m -Dsbt.override.build.repos=true -Dsbt.repository.config=./project/repositories -Dsbt.override.build.repos=true -Dsbt.repository.config=./project/repositories -jar /var/lib/jenkins/tools/org.jvnet.hudson.plugins.SbtPluginBuilder_SbtInstallation/
1 yet
0.13.
7 clean scalastyle coverage test coverageAggregate
8 was just released. Can we update the list of sbt versions in the sbt jenkins 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] [sbt-plugin] (JENKINS-27612) SBT Install from scala-sbt.org is very out of date















































Night Wolf
 updated  JENKINS-27612


SBT Install from scala-sbt.org is very out of date
















Change By:


Night Wolf
(26/Mar/15 5:10 AM)




Priority:


Minor
Critical



























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] [sbt-plugin] (JENKINS-27264) Latest 1.5 SBT Plugin does not work















































Night Wolf
 commented on  JENKINS-27264


Latest 1.5 SBT Plugin does not work















so running hudson.model.DownloadService.Downloadable.all().each { it.updateNow() }  will get the install from scala-sbt.org to work but its pretty much pointless. The most recent version that comes up is 0.13.1... 0.13.8 was just released! 



























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] [sbt-plugin] (JENKINS-27612) SBT Install from scala-sbt.org is very out of date















































Night Wolf
 created  JENKINS-27612


SBT Install from scala-sbt.org is very out of date















Issue Type:


Bug



Assignee:


uzilan



Components:


sbt-plugin



Created:


26/Mar/15 5:09 AM



Description:


I have a simple Jenkins server running Ubuntu. Just building off master. The auto install from scala-sbt.org does not work. In the logs I just see;
Invalid tool ID 0.13.7
[chot-bi-build] $ java -Xms512m -Xmx512m -XX:ReservedCodeCacheSize=128m -Dsbt.override.build.repos=true -Dsbt.repository.config=./project/repositories -Dsbt.override.build.repos=true -Dsbt.repository.config=./project/repositories -jar /var/lib/jenkins/tools/org.jvnet.hudson.plugins.SbtPluginBuilder_SbtInstallation/0.13.7 clean scalastyle coverage test coverageAggregate




Environment:


Ubuntu 14




Project:


Jenkins



Priority:


Minor



Reporter:


Night Wolf

























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] [envinject-plugin] (JENKINS-27611) NPE when disabling envinject on a project, can't disable envinject
















































Craig Ringer
 resolved  JENKINS-27611 as Duplicate


NPE when disabling envinject on a project, can't disable envinject
















Duplicates #27496





Change By:


Craig Ringer
(26/Mar/15 4:08 AM)




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] [envinject-plugin] (JENKINS-27611) NPE when disabling envinject on a project, can't disable envinject















































Craig Ringer
 created  JENKINS-27611


NPE when disabling envinject on a project, can't disable envinject















Issue Type:


Bug



Assignee:


Gregory Boissinot



Attachments:


support.zip



Components:


envinject-plugin



Created:


26/Mar/15 4:07 AM



Description:


Created a normal (non-matrix) job and enabled envinject by checking:

"Prepare an environment for the run" Saved the build.

Later, went to disable envinject by unchecking "Prepare an environment for the run". Saved the build.

Saving the job config caused an NPE in the envinject plugin:


javax.servlet.ServletException: java.lang.NullPointerException
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123)
	at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)
	at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at

[JIRA] [core] (JENKINS-27564) Race condition when rendering the executors list















































SCM/JIRA link daemon
 commented on  JENKINS-27564


Race condition when rendering the executors list















Code changed in jenkins
User: Stephen Connolly
Path:
 core/src/main/java/hudson/Functions.java
 core/src/main/java/hudson/model/AbstractCIBase.java
 core/src/main/java/hudson/model/Computer.java
 core/src/main/java/hudson/model/Executor.java
 core/src/main/java/hudson/model/Hudson.java
 core/src/main/java/hudson/model/Node.java
 core/src/main/java/hudson/model/Queue.java
 core/src/main/java/hudson/model/ResourceController.java
 core/src/main/java/hudson/slaves/AbstractCloudSlave.java
 core/src/main/java/hudson/slaves/ComputerRetentionWork.java
 core/src/main/java/hudson/slaves/NodeProvisioner.java
 core/src/main/java/hudson/slaves/RetentionStrategy.java
 core/src/main/java/hudson/slaves/SlaveComputer.java
 core/src/main/java/jenkins/model/Jenkins.java
 core/src/main/java/jenkins/model/Nodes.java
 core/src/main/java/jenkins/util/AtmostOneTaskExecutor.java
 core/src/main/resources/hudson/model/Messages.properties
 core/src/main/resources/lib/hudson/executors.jelly
 core/src/main/resources/lib/layout/layout.jelly
http://jenkins-ci.org/commit/jenkins/92147c3597308bc05e6448ccc41409fcc7c05fd7
Log:
  [FIXED JENKINS-27565] Refactor the Queue and Nodes to use a consistent locking strategy

The test system I set up to verify resolution of customer(s)' issues driving this change, required
additional changes in order to fully resolve the issues at hand. As a result I am bundling these
changes:


	Moves nodes to being store in separate config files outside of the main config file (improves performance) [FIXED JENKINS-27562]
	Makes the Jenkins is loading screen not block on the extensions loading lock [FIXED JENKINS-27563]
	Removes race condition rendering the list of executors [FIXED JENKINS-27564] [FIXED JENKINS-15355]
	Tidy up the locks that were causing deadlocks with the once retention strategy in durable tasks [FIXED JENKINS-27476]
	Remove any requirement from Jenkins Core to lock on the Queue when rendering the Jenkins UI [FIXED-JENKINS-27566]































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-27563) Prevent Jenkins from blocking HTTP requests during start-up















































SCM/JIRA link daemon
 commented on  JENKINS-27563


Prevent Jenkins from blocking HTTP requests during start-up















Code changed in jenkins
User: Stephen Connolly
Path:
 core/src/main/java/hudson/Functions.java
 core/src/main/java/hudson/model/AbstractCIBase.java
 core/src/main/java/hudson/model/Computer.java
 core/src/main/java/hudson/model/Executor.java
 core/src/main/java/hudson/model/Hudson.java
 core/src/main/java/hudson/model/Node.java
 core/src/main/java/hudson/model/Queue.java
 core/src/main/java/hudson/model/ResourceController.java
 core/src/main/java/hudson/slaves/AbstractCloudSlave.java
 core/src/main/java/hudson/slaves/ComputerRetentionWork.java
 core/src/main/java/hudson/slaves/NodeProvisioner.java
 core/src/main/java/hudson/slaves/RetentionStrategy.java
 core/src/main/java/hudson/slaves/SlaveComputer.java
 core/src/main/java/jenkins/model/Jenkins.java
 core/src/main/java/jenkins/model/Nodes.java
 core/src/main/java/jenkins/util/AtmostOneTaskExecutor.java
 core/src/main/resources/hudson/model/Messages.properties
 core/src/main/resources/lib/hudson/executors.jelly
 core/src/main/resources/lib/layout/layout.jelly
http://jenkins-ci.org/commit/jenkins/92147c3597308bc05e6448ccc41409fcc7c05fd7
Log:
  [FIXED JENKINS-27565] Refactor the Queue and Nodes to use a consistent locking strategy

The test system I set up to verify resolution of customer(s)' issues driving this change, required
additional changes in order to fully resolve the issues at hand. As a result I am bundling these
changes:


	Moves nodes to being store in separate config files outside of the main config file (improves performance) [FIXED JENKINS-27562]
	Makes the Jenkins is loading screen not block on the extensions loading lock [FIXED JENKINS-27563]
	Removes race condition rendering the list of executors [FIXED JENKINS-27564] [FIXED JENKINS-15355]
	Tidy up the locks that were causing deadlocks with the once retention strategy in durable tasks [FIXED JENKINS-27476]
	Remove any requirement from Jenkins Core to lock on the Queue when rendering the Jenkins UI [FIXED-JENKINS-27566]































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-27562) Move slave configuration out of main configuration file and into per-slave config files.















































SCM/JIRA link daemon
 commented on  JENKINS-27562


Move slave configuration out of main configuration file and into per-slave config files.















Code changed in jenkins
User: Stephen Connolly
Path:
 core/src/main/java/hudson/Functions.java
 core/src/main/java/hudson/model/AbstractCIBase.java
 core/src/main/java/hudson/model/Computer.java
 core/src/main/java/hudson/model/Executor.java
 core/src/main/java/hudson/model/Hudson.java
 core/src/main/java/hudson/model/Node.java
 core/src/main/java/hudson/model/Queue.java
 core/src/main/java/hudson/model/ResourceController.java
 core/src/main/java/hudson/slaves/AbstractCloudSlave.java
 core/src/main/java/hudson/slaves/ComputerRetentionWork.java
 core/src/main/java/hudson/slaves/NodeProvisioner.java
 core/src/main/java/hudson/slaves/RetentionStrategy.java
 core/src/main/java/hudson/slaves/SlaveComputer.java
 core/src/main/java/jenkins/model/Jenkins.java
 core/src/main/java/jenkins/model/Nodes.java
 core/src/main/java/jenkins/util/AtmostOneTaskExecutor.java
 core/src/main/resources/hudson/model/Messages.properties
 core/src/main/resources/lib/hudson/executors.jelly
 core/src/main/resources/lib/layout/layout.jelly
http://jenkins-ci.org/commit/jenkins/92147c3597308bc05e6448ccc41409fcc7c05fd7
Log:
  [FIXED JENKINS-27565] Refactor the Queue and Nodes to use a consistent locking strategy

The test system I set up to verify resolution of customer(s)' issues driving this change, required
additional changes in order to fully resolve the issues at hand. As a result I am bundling these
changes:


	Moves nodes to being store in separate config files outside of the main config file (improves performance) [FIXED JENKINS-27562]
	Makes the Jenkins is loading screen not block on the extensions loading lock [FIXED JENKINS-27563]
	Removes race condition rendering the list of executors [FIXED JENKINS-27564] [FIXED JENKINS-15355]
	Tidy up the locks that were causing deadlocks with the once retention strategy in durable tasks [FIXED JENKINS-27476]
	Remove any requirement from Jenkins Core to lock on the Queue when rendering the Jenkins UI [FIXED-JENKINS-27566]































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-15355) AdjunctManager: exception upon startup















































SCM/JIRA link daemon
 commented on  JENKINS-15355


AdjunctManager: exception upon startup















Code changed in jenkins
User: Stephen Connolly
Path:
 core/src/main/java/hudson/Functions.java
 core/src/main/java/hudson/model/AbstractCIBase.java
 core/src/main/java/hudson/model/Computer.java
 core/src/main/java/hudson/model/Executor.java
 core/src/main/java/hudson/model/Hudson.java
 core/src/main/java/hudson/model/Node.java
 core/src/main/java/hudson/model/Queue.java
 core/src/main/java/hudson/model/ResourceController.java
 core/src/main/java/hudson/slaves/AbstractCloudSlave.java
 core/src/main/java/hudson/slaves/ComputerRetentionWork.java
 core/src/main/java/hudson/slaves/NodeProvisioner.java
 core/src/main/java/hudson/slaves/RetentionStrategy.java
 core/src/main/java/hudson/slaves/SlaveComputer.java
 core/src/main/java/jenkins/model/Jenkins.java
 core/src/main/java/jenkins/model/Nodes.java
 core/src/main/java/jenkins/util/AtmostOneTaskExecutor.java
 core/src/main/resources/hudson/model/Messages.properties
 core/src/main/resources/lib/hudson/executors.jelly
 core/src/main/resources/lib/layout/layout.jelly
http://jenkins-ci.org/commit/jenkins/92147c3597308bc05e6448ccc41409fcc7c05fd7
Log:
  [FIXED JENKINS-27565] Refactor the Queue and Nodes to use a consistent locking strategy

The test system I set up to verify resolution of customer(s)' issues driving this change, required
additional changes in order to fully resolve the issues at hand. As a result I am bundling these
changes:


	Moves nodes to being store in separate config files outside of the main config file (improves performance) [FIXED JENKINS-27562]
	Makes the Jenkins is loading screen not block on the extensions loading lock [FIXED JENKINS-27563]
	Removes race condition rendering the list of executors [FIXED JENKINS-27564] [FIXED JENKINS-15355]
	Tidy up the locks that were causing deadlocks with the once retention strategy in durable tasks [FIXED JENKINS-27476]
	Remove any requirement from Jenkins Core to lock on the Queue when rendering the Jenkins UI [FIXED-JENKINS-27566]































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] [durable-task-plugin] (JENKINS-27476) Plugin casue deadlock on Jenkins LTS 1.596.1















































SCM/JIRA link daemon
 commented on  JENKINS-27476


Plugin casue deadlock on Jenkins LTS 1.596.1















Code changed in jenkins
User: Stephen Connolly
Path:
 core/src/main/java/hudson/Functions.java
 core/src/main/java/hudson/model/AbstractCIBase.java
 core/src/main/java/hudson/model/Computer.java
 core/src/main/java/hudson/model/Executor.java
 core/src/main/java/hudson/model/Hudson.java
 core/src/main/java/hudson/model/Node.java
 core/src/main/java/hudson/model/Queue.java
 core/src/main/java/hudson/model/ResourceController.java
 core/src/main/java/hudson/slaves/AbstractCloudSlave.java
 core/src/main/java/hudson/slaves/ComputerRetentionWork.java
 core/src/main/java/hudson/slaves/NodeProvisioner.java
 core/src/main/java/hudson/slaves/RetentionStrategy.java
 core/src/main/java/hudson/slaves/SlaveComputer.java
 core/src/main/java/jenkins/model/Jenkins.java
 core/src/main/java/jenkins/model/Nodes.java
 core/src/main/java/jenkins/util/AtmostOneTaskExecutor.java
 core/src/main/resources/hudson/model/Messages.properties
 core/src/main/resources/lib/hudson/executors.jelly
 core/src/main/resources/lib/layout/layout.jelly
http://jenkins-ci.org/commit/jenkins/92147c3597308bc05e6448ccc41409fcc7c05fd7
Log:
  [FIXED JENKINS-27565] Refactor the Queue and Nodes to use a consistent locking strategy

The test system I set up to verify resolution of customer(s)' issues driving this change, required
additional changes in order to fully resolve the issues at hand. As a result I am bundling these
changes:


	Moves nodes to being store in separate config files outside of the main config file (improves performance) [FIXED JENKINS-27562]
	Makes the Jenkins is loading screen not block on the extensions loading lock [FIXED JENKINS-27563]
	Removes race condition rendering the list of executors [FIXED JENKINS-27564] [FIXED JENKINS-15355]
	Tidy up the locks that were causing deadlocks with the once retention strategy in durable tasks [FIXED JENKINS-27476]
	Remove any requirement from Jenkins Core to lock on the Queue when rendering the Jenkins UI [FIXED-JENKINS-27566]































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-27565) Nodes can be removed as idle before the assigned tasks have started















































SCM/JIRA link daemon
 commented on  JENKINS-27565


Nodes can be removed as idle before the assigned tasks have started















Code changed in jenkins
User: Stephen Connolly
Path:
 core/src/main/java/hudson/Functions.java
 core/src/main/java/hudson/model/AbstractCIBase.java
 core/src/main/java/hudson/model/Computer.java
 core/src/main/java/hudson/model/Executor.java
 core/src/main/java/hudson/model/Hudson.java
 core/src/main/java/hudson/model/Node.java
 core/src/main/java/hudson/model/Queue.java
 core/src/main/java/hudson/model/ResourceController.java
 core/src/main/java/hudson/slaves/AbstractCloudSlave.java
 core/src/main/java/hudson/slaves/ComputerRetentionWork.java
 core/src/main/java/hudson/slaves/NodeProvisioner.java
 core/src/main/java/hudson/slaves/RetentionStrategy.java
 core/src/main/java/hudson/slaves/SlaveComputer.java
 core/src/main/java/jenkins/model/Jenkins.java
 core/src/main/java/jenkins/model/Nodes.java
 core/src/main/java/jenkins/util/AtmostOneTaskExecutor.java
 core/src/main/resources/hudson/model/Messages.properties
 core/src/main/resources/lib/hudson/executors.jelly
 core/src/main/resources/lib/layout/layout.jelly
http://jenkins-ci.org/commit/jenkins/92147c3597308bc05e6448ccc41409fcc7c05fd7
Log:
  [FIXED JENKINS-27565] Refactor the Queue and Nodes to use a consistent locking strategy

The test system I set up to verify resolution of customer(s)' issues driving this change, required
additional changes in order to fully resolve the issues at hand. As a result I am bundling these
changes:


	Moves nodes to being store in separate config files outside of the main config file (improves performance) [FIXED JENKINS-27562]
	Makes the Jenkins is loading screen not block on the extensions loading lock [FIXED JENKINS-27563]
	Removes race condition rendering the list of executors [FIXED JENKINS-27564] [FIXED JENKINS-15355]
	Tidy up the locks that were causing deadlocks with the once retention strategy in durable tasks [FIXED JENKINS-27476]
	Remove any requirement from Jenkins Core to lock on the Queue when rendering the Jenkins UI [FIXED-JENKINS-27566]































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] [s3-plugin] (JENKINS-23897) S3 plugin's signed URL expiry is extremely sensitive to clock drift
















































Craig Ringer
 resolved  JENKINS-23897 as Fixed


S3 plugin's signed URL expiry is extremely sensitive to clock drift
















Change By:


Craig Ringer
(26/Mar/15 3:36 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [s3-plugin] (JENKINS-14611) S3 plugin credentials lost after service restart, must be re-entered / saved















































Craig Ringer
 commented on  JENKINS-14611


S3 plugin credentials lost after service restart, must be re-entered / saved















I haven't seen this issue. Can you still reproduce it in a current 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] [s3-plugin] (JENKINS-23897) S3 plugin's signed URL expiry is extremely sensitive to clock drift















































Craig Ringer
 commented on  JENKINS-23897


S3 plugin's signed URL expiry is extremely sensitive to clock drift















This fix has been merged.



























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] [s3-plugin] (JENKINS-18839) S3 plugin fails to upload to EU region (wrong endpoint)















































Craig Ringer
 commented on  JENKINS-18839


S3 plugin fails to upload to EU region (wrong endpoint)















This is a smidge broken - it defaults to GOVCLOUD for upgrades, and it doesn't offer any way to select the legacy no-region-selected s3 URI .



























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-26582) ISE from RunMap.put after reloading config

2015-03-25 Thread benjamin.cl...@clearchain.com (JIRA)















































Benjamin Close
 commented on  JENKINS-26582


ISE from RunMap.put after reloading config















Update to this issue. It's definitely seems related to multiple new jobs starting at the same time.
Once the executor dies, jobs queue up. If I then restart the thread with no new jobs starting the pending jobs queue will clear itself over time. If another job comes along at the right time, the thread death may occur.



























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







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-27290) Communication Error, Syntax Problem

2015-03-25 Thread jenkins...@kay-strobach.de (JIRA)















































Kay Strobach
 commented on  JENKINS-27290


Communication Error, Syntax Problem















sadly i missed to store the broken jenkins version. I upgraded it the last time I was on the system, let's close the issue for now, if it occurs again i will add more information.



























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







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-27290) Communication Error, Syntax Problem

2015-03-25 Thread jenkins...@kay-strobach.de (JIRA)
















































Kay Strobach
 closed  JENKINS-27290 as Cannot Reproduce


Communication Error, Syntax Problem
















Change By:


Kay Strobach
(26/Mar/15 2:44 AM)




Status:


Open
Closed





Resolution:


Cannot Reproduce



























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







-- 
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-27607) Incorrect MIME type served for api/json?jsonp















































dogfood
 commented on  JENKINS-27607


Incorrect MIME type served for api/json?jsonp















Integrated in  jenkins_main_trunk #4031
 JENKINS-27607 Reproduced in test. (Revision ac80ef27ddd8307d3f57d1185868ac8d92df88a1)

 Result = SUCCESS
jesse glick : ac80ef27ddd8307d3f57d1185868ac8d92df88a1
Files : 

	test/src/test/java/hudson/model/ApiTest.java





























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-27447) LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page

2015-03-25 Thread dspa...@yahoo-inc.com (JIRA)















































Daryl Spartz
 commented on  JENKINS-27447


LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page















I've attached what needs to used to recreate, don't know if you have tried. I'm digging into another issue at the moment.



























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-27607) Incorrect MIME type served for api/json?jsonp















































Jesse Glick
 commented on  JENKINS-27607


Incorrect MIME type served for api/json?jsonp















If backporting, beware that the trunk diff does not show the bump of Stapler to 1.236 as here and here, which would be needed for older versions.



























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] [svnmerge-plugin] (JENKINS-27610) Mark build as unstable on failure















































SCM/JIRA link daemon
 commented on  JENKINS-27610


Mark build as unstable on failure















Code changed in jenkins
User: Hugues Chabot
Path:
 pom.xml
 src/main/java/jenkins/plugins/svnmerge/RebaseBuilder.java
 src/main/java/jenkins/plugins/svnmerge/Utility.java
 src/main/resources/jenkins/plugins/svnmerge/RebaseBuilder/config.groovy
http://jenkins-ci.org/commit/svnmerge-plugin/1e481ce60c006cc18a6170d026cd64dd5d81ed57
Log:
  Merge pull request #28 from Vinnie555/master

[FIXED JENKINS-27609] Add Support for Matrix build
[FIXED JENKINS-27610] Mark build as unstable on failure


Compare: https://github.com/jenkinsci/svnmerge-plugin/compare/6293430199b0...1e481ce60c00




























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-27607) Incorrect MIME type served for api/json?jsonp
















































Jesse Glick
 resolved  JENKINS-27607 as Fixed


Incorrect MIME type served for api/json?jsonp
















Change By:


Jesse Glick
(26/Mar/15 1:08 AM)




Status:


In Progress
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-27607) Incorrect MIME type served for api/json?jsonp















































SCM/JIRA link daemon
 commented on  JENKINS-27607


Incorrect MIME type served for api/json?jsonp















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/Api.java
 test/src/test/java/hudson/model/ApiTest.java
http://jenkins-ci.org/commit/jenkins/bd4d15785f06e58db5e5a72a091c78411e734dfa
Log:
  JENKINS-27607 Noting merge of #1623.


Compare: https://github.com/jenkinsci/jenkins/compare/e54b19d87231...bd4d15785f06




























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-27607) Incorrect MIME type served for api/json?jsonp















































SCM/JIRA link daemon
 commented on  JENKINS-27607


Incorrect MIME type served for api/json?jsonp















Code changed in jenkins
User: Jesse Glick
Path:
 test/src/test/java/hudson/model/ApiTest.java
http://jenkins-ci.org/commit/jenkins/ac80ef27ddd8307d3f57d1185868ac8d92df88a1
Log:
  JENKINS-27607 Reproduced in test.





























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] [svnmerge-plugin] (JENKINS-27609) Add Support for Matrix build















































SCM/JIRA link daemon
 commented on  JENKINS-27609


Add Support for Matrix build















Code changed in jenkins
User: Hugues Chabot
Path:
 pom.xml
 src/main/java/jenkins/plugins/svnmerge/RebaseBuilder.java
 src/main/java/jenkins/plugins/svnmerge/Utility.java
 src/main/resources/jenkins/plugins/svnmerge/RebaseBuilder/config.groovy
http://jenkins-ci.org/commit/svnmerge-plugin/1e481ce60c006cc18a6170d026cd64dd5d81ed57
Log:
  Merge pull request #28 from Vinnie555/master

[FIXED JENKINS-27609] Add Support for Matrix build
[FIXED JENKINS-27610] Mark build as unstable on failure


Compare: https://github.com/jenkinsci/svnmerge-plugin/compare/6293430199b0...1e481ce60c00




























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] [svnmerge-plugin] (JENKINS-27610) Mark build as unstable on failure

2015-03-25 Thread hugues.cha...@gmail.com (JIRA)















































Hugues Chabot
 created  JENKINS-27610


Mark build as unstable on failure















Issue Type:


Improvement



Assignee:


Kohsuke Kawaguchi



Components:


svnmerge-plugin



Created:


26/Mar/15 1:02 AM



Description:


Add an option to mark the build as unstable if the merge fails.




Project:


Jenkins



Priority:


Minor



Reporter:


Hugues Chabot

























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] [svnmerge-plugin] (JENKINS-27609) Add Support for Matrix build

2015-03-25 Thread hugues.cha...@gmail.com (JIRA)















































Hugues Chabot
 created  JENKINS-27609


Add Support for Matrix build















Issue Type:


Improvement



Assignee:


Kohsuke Kawaguchi



Components:


svnmerge-plugin



Created:


26/Mar/15 12:59 AM



Description:


Support matrix style builds.




Project:


Jenkins



Priority:


Minor



Reporter:


Hugues Chabot

























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-27055) Slave To Master Access Control needs updating for JENKINS_HOME layout change















































dogfood
 commented on  JENKINS-27055


Slave To Master Access Control needs updating for JENKINS_HOME layout change















Integrated in  jenkins_main_trunk #4030
 [FiXED JENKINS-27055]  should now also match numeric build IDs. (Revision 20c458d9933b5d25fc472f84ba8dbbf4eae5edee)

 Result = SUCCESS
jesse glick : 20c458d9933b5d25fc472f84ba8dbbf4eae5edee
Files : 

	test/src/test/java/jenkins/security/DefaultFilePathFilterTest.java
	core/src/main/java/jenkins/security/s2m/FilePathRuleConfig.java





























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-27599) Incomplete deployment of Jenkins artifacts to Maven Central















































Daniel Beck
 commented on  JENKINS-27599


Incomplete deployment of Jenkins artifacts to Maven Central















Would be interesting to know who uploaded this 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] [core] (JENKINS-27599) Incomplete deployment of Jenkins artifacts to Maven Central
















































Daniel Beck
 resolved  JENKINS-27599 as Not A Defect


Incomplete deployment of Jenkins artifacts to Maven Central
















I pinged Kohsuke Kawaguchi on IRC about this issue.

That said, I'm afraid this isn't the issue tracker for your problem as it's not actually about Jenkins, or the Jenkins project infrastructure.





Change By:


Daniel Beck
(25/Mar/15 11:59 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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







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

[JIRA] [core] (JENKINS-27594) Jetty based jenkins leaves many sockets in close_wait state
















































Daniel Beck
 resolved  JENKINS-27594 as Incomplete


Jetty based jenkins leaves many sockets in close_wait state
















This is an issue tracker, not a support website. And for a bug report, this contains not enough information to investigate further.

Please see:
https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue
https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump





Change By:


Daniel Beck
(25/Mar/15 11:49 PM)




Status:


Open
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] [docker-build-publish-plugin] (JENKINS-27608) option to squash image commits

2015-03-25 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 created  JENKINS-27608


option to squash image commits















Issue Type:


Improvement



Assignee:


Nicolas De Loof



Components:


docker-build-publish-plugin



Created:


25/Mar/15 11:45 PM



Description:


you can't use `RUN rm /tmp` to cleanup image from unnecessary files created by previous commands in Dockerfile. This results in complex Dockerfile or one-line RUN commands.

using docker export | docker import you can "squash" the image layers into a single one-layer docker image, making Dockerfile simpler and preserving image size.




Project:


Jenkins



Priority:


Minor



Reporter:


Nicolas De Loof

























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-27590) Could not connect to pkg.jenkins-ci.org:80 (199.193.196.24). - connect (110: Connection timed out)
















































Daniel Beck
 resolved  JENKINS-27590 as Cannot Reproduce


Could not connect to pkg.jenkins-ci.org:80 (199.193.196.24). - connect (110: Connection timed out)
















Looks like a transient error that has been resolved.





Change By:


Daniel Beck
(25/Mar/15 11:47 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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







-- 
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-26900) Hide flyweight master executor when ≥1 heavyweight executors running as subtasks















































dogfood
 commented on  JENKINS-26900


Hide flyweight master executor when ≥1 heavyweight executors running as subtasks















Integrated in  jenkins_main_trunk #4029
 [FIXED JENKINS-26900] AsynchronousExecution.displayCell (Revision bb80340a92538cdc783a55a28d42bcacd46673f4)

 Result = SUCCESS
jesse glick : bb80340a92538cdc783a55a28d42bcacd46673f4
Files : 

	core/src/main/resources/lib/hudson/executors.jelly
	core/src/main/java/jenkins/model/queue/AsynchronousExecution.java





























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-22941) Way to mark an Executable that should not block isReadyToRestart















































dogfood
 commented on  JENKINS-22941


Way to mark an Executable that should not block isReadyToRestart















Integrated in  jenkins_main_trunk #4029
 [FIXED JENKINS-22941] AsynchronousExecution.blocksRestart (Revision 8589b211f9a99fa47d022a77bd7936636175898a)

 Result = SUCCESS
jesse glick : 8589b211f9a99fa47d022a77bd7936636175898a
Files : 

	core/src/main/java/hudson/model/Executor.java
	core/src/main/java/jenkins/model/Jenkins.java
	core/src/main/java/hudson/model/RestartListener.java
	core/src/main/java/jenkins/model/queue/AsynchronousExecution.java





























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-26090) Executables.getExecutor















































dogfood
 commented on  JENKINS-26090


Executables.getExecutor















Integrated in  jenkins_main_trunk #4029
 [FIXED JENKINS-26090] Executables.getExecutor (Revision f2f988e81fc42d69d32c09dfd8958d53e4dedb30)

 Result = SUCCESS
jesse glick : f2f988e81fc42d69d32c09dfd8958d53e4dedb30
Files : 

	core/src/main/java/hudson/model/queue/Executables.java
	core/src/main/java/hudson/model/Run.java





























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-26092) executors.jelly interface underspecified















































dogfood
 commented on  JENKINS-26092


executors.jelly interface underspecified















Integrated in  jenkins_main_trunk #4029
 JENKINS-26092 Noting some things that could be improved. (Revision 09f7a2d3d120d77497da1e566a6719ec6feac7ee)

 Result = SUCCESS
jesse glick : 09f7a2d3d120d77497da1e566a6719ec6feac7ee
Files : 

	core/src/main/resources/lib/hudson/buildProgressBar.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-25938) Lock an Executor without creating a Thread















































dogfood
 commented on  JENKINS-25938


Lock an Executor without creating a Thread















Integrated in  jenkins_main_trunk #4029
 JENKINS-25938 Introduced AsynchronousExecutable. (Revision 46a900f4cb468853c5dca844d258b5b862c3a8bf)

 Result = SUCCESS
jesse glick : 46a900f4cb468853c5dca844d258b5b862c3a8bf
Files : 

	core/src/main/java/hudson/model/OneOffExecutor.java
	core/src/main/java/hudson/model/Queue.java
	core/src/main/java/hudson/model/Executor.java
	core/src/main/java/hudson/model/AbstractBuild.java
	core/src/main/java/hudson/model/Computer.java
	core/src/main/java/jenkins/model/queue/Executable2.java
	core/src/main/java/hudson/model/ResourceController.java
	core/src/main/java/hudson/model/queue/WorkUnitContext.java





























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] [multijob-plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild













































  
Michael Merritt
 edited a comment on  JENKINS-17704


Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
















Just an update that we're still seeing these errors in Jenkins 1.605 and multijob plugin 1.16



























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] [multijob-plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild













































  
Michael Merritt
 edited a comment on  JENKINS-17704


Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
















Nevermind, re-reporting an old issue.



























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







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

[JIRA] [multijob-plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild















































Michael Merritt
 commented on  JENKINS-17704


Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild















Also seeing this same error fairly frequently in jenkins 1.605 and multijob plugin 1.16



























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] [multijob-plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild













































  
Michael Merritt
 edited a comment on  JENKINS-17704


Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
















Also seeing this same error fairly frequently in jenkins 1.605 and multijob plugin 1.16. Haven't seen it disrupt the our multi-jobs yet, but seeing it frequently in the logs.



























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







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

[JIRA] [warnings-plugin] (JENKINS-22264) MSBuild parser does not support multi-language output

2015-03-25 Thread tonktonk.tinker...@gmail.com (JIRA)















































Stefan Landström
 commented on  JENKINS-22264


MSBuild parser does not support multi-language output















Perhaps the "Warnung" output came from another tool run during the build?

My understanding is that the output category should not be localized in order for it to be picked up by MSBuild.

	https://msdn.microsoft.com/en-us/library/yxkt8b26.aspx
	http://blogs.msdn.com/b/msbuild/archive/2006/11/03/msbuild-visual-studio-aware-error-messages-and-message-formats.aspx



For future reference it can also be worth mentioning that Microsoft has now open-sourced MSBuild, so it's possible to see their current implementation for how this is handled:
https://github.com/Microsoft/msbuild/blob/master/src/Shared/CanonicalError.cs



























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-27055) Slave To Master Access Control needs updating for JENKINS_HOME layout change
















































Jesse Glick
 resolved  JENKINS-27055 as Fixed


Slave To Master Access Control needs updating for JENKINS_HOME layout change
















Change By:


Jesse Glick
(25/Mar/15 10:38 PM)




Status:


In Progress
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-27055) Slave To Master Access Control needs updating for JENKINS_HOME layout change















































SCM/JIRA link daemon
 commented on  JENKINS-27055


Slave To Master Access Control needs updating for JENKINS_HOME layout change















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/jenkins/security/s2m/FilePathRuleConfig.java
 test/src/test/java/jenkins/security/DefaultFilePathFilterTest.java
http://jenkins-ci.org/commit/jenkins/e54b19d872317e135c46a415df80651d0de8dbfa
Log:
  JENKINS-27055 Noting merge of #1621.


Compare: https://github.com/jenkinsci/jenkins/compare/cfa4b100be1b...e54b19d87231




























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-27055) Slave To Master Access Control needs updating for JENKINS_HOME layout change















































SCM/JIRA link daemon
 commented on  JENKINS-27055


Slave To Master Access Control needs updating for JENKINS_HOME layout change















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/jenkins/security/s2m/FilePathRuleConfig.java
 test/src/test/java/jenkins/security/DefaultFilePathFilterTest.java
http://jenkins-ci.org/commit/jenkins/20c458d9933b5d25fc472f84ba8dbbf4eae5edee
Log:
  [FiXED JENKINS-27055]  should now also match numeric build IDs.





























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-12396) Jobs remain on executor for 20 minutes after they finish

Daniel Beck
commented on JENKINS-12396

Jobs remain on executor for 20 minutes after they finish

I don't know if it's because our Jenkins Master is Windows based and NTFS is not good at handling deletes, or that we have a lot of jobs or that our jobs are quite large (many hundreds of files) or some combination of these but this stage can regularly take in excess of an hour to complete after the job has reported that it has finished.

The stack trace shows Jenkins is busy with determining what builds may be deleted, not the actual deleting itself.

It feels like it would be nicer if the build discard process occurred as a background housekeeping operation rather than as an inline part of the latest build, possibly also only having a single cleanup process rather than every job being able to trigger these tasks concurrently might be a good idea.

Needs stronger justification than "it doesn't work on my instance".

Get a few more thread dumps for this thread to determine where it's spending the most time. Could well be too little RAM on the Jenkins master to keep builds in memory, resulting in repeated build loading and discarding from memory.

[JIRA] [core] (JENKINS-22941) Way to mark an Executable that should not block isReadyToRestart
















































Jesse Glick
 resolved  JENKINS-22941 as Fixed


Way to mark an Executable that should not block isReadyToRestart
















Change By:


Jesse Glick
(25/Mar/15 10:33 PM)




Status:


In Progress
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-26090) Executables.getExecutor
















































Jesse Glick
 resolved  JENKINS-26090 as Fixed


Executables.getExecutor
















Change By:


Jesse Glick
(25/Mar/15 10:33 PM)




Status:


In Progress
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-25938) Lock an Executor without creating a Thread
















































Jesse Glick
 resolved  JENKINS-25938 as Fixed


Lock an Executor without creating a Thread
















Change By:


Jesse Glick
(25/Mar/15 10:33 PM)




Status:


In Progress
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-27607) Incorrect MIME type served for api/json?jsonp















































Jesse Glick
 started work on  JENKINS-27607


Incorrect MIME type served for api/json?jsonp
















Change By:


Jesse Glick
(25/Mar/15 10:15 PM)




Status:


Open
In Progress



























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







-- 
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-27607) Incorrect MIME type served for api/json?jsonp















































Jesse Glick
 created  JENKINS-27607


Incorrect MIME type served for api/json?jsonp















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


core



Created:


25/Mar/15 10:13 PM



Description:


Retroactively filing issue for PR 1595: JSONP is served as application/json when it should be application/_javascript_.




Project:


Jenkins



Labels:


stapler
json
rest
lts-candidate




Priority:


Critical



Reporter:


Jesse Glick

























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] [credentials-binding-plugin] (JENKINS-27389) credentials set via 'withCredentials' block isn't accesible from 'env'
















































Jesse Glick
 assigned  JENKINS-27389 to Jesse Glick



credentials set via 'withCredentials' block isn't accesible from 'env' 
















Change By:


Jesse Glick
(25/Mar/15 9:58 PM)




Assignee:


Kohsuke Kawaguchi
Jesse Glick



























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-26090) Executables.getExecutor















































Jesse Glick
 started work on  JENKINS-26090


Executables.getExecutor
















Change By:


Jesse Glick
(25/Mar/15 9:53 PM)




Status:


Open
In Progress



























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







-- 
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-22941) Way to mark an Executable that should not block isReadyToRestart















































Jesse Glick
 updated  JENKINS-22941


Way to mark an Executable that should not block isReadyToRestart
















Change By:


Jesse Glick
(25/Mar/15 9:53 PM)




Status:


Reopened
Open



























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-26090) Executables.getExecutor















































Jesse Glick
 updated  JENKINS-26090


Executables.getExecutor
















Change By:


Jesse Glick
(25/Mar/15 9:53 PM)




Status:


Reopened
Open



























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-22941) Way to mark an Executable that should not block isReadyToRestart















































Jesse Glick
 started work on  JENKINS-22941


Way to mark an Executable that should not block isReadyToRestart
















Change By:


Jesse Glick
(25/Mar/15 9:53 PM)




Status:


Open
In Progress



























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







-- 
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-22941) Way to mark an Executable that should not block isReadyToRestart















































Jesse Glick
 reopened  JENKINS-22941


Way to mark an Executable that should not block isReadyToRestart
















Change By:


Jesse Glick
(25/Mar/15 9:53 PM)




Resolution:


Fixed





Status:


Resolved
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] [workflow-plugin] (JENKINS-26900) Hide flyweight master executor when ≥1 heavyweight executors running as subtasks















































Jesse Glick
 updated  JENKINS-26900


Hide flyweight master executor when ≥1 heavyweight executors running as subtasks
















Change By:


Jesse Glick
(25/Mar/15 9:52 PM)




Status:


Reopened
Open



























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-26090) Executables.getExecutor















































Jesse Glick
 reopened  JENKINS-26090


Executables.getExecutor
















Change By:


Jesse Glick
(25/Mar/15 9:53 PM)




Resolution:


Fixed





Status:


Resolved
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] [workflow-plugin] (JENKINS-26900) Hide flyweight master executor when ≥1 heavyweight executors running as subtasks















































Jesse Glick
 started work on  JENKINS-26900


Hide flyweight master executor when ≥1 heavyweight executors running as subtasks
















Change By:


Jesse Glick
(25/Mar/15 9:52 PM)




Status:


Open
In Progress



























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







-- 
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-26900) Hide flyweight master executor when ≥1 heavyweight executors running as subtasks















































Jesse Glick
 reopened  JENKINS-26900


Hide flyweight master executor when ≥1 heavyweight executors running as subtasks
















Got closed accidentally due to Kohsuke Kawaguchi doing a second-level PR from @jenkinsci, which confuses the JIRA link daemon.





Change By:


Jesse Glick
(25/Mar/15 9:52 PM)




Resolution:


Fixed





Status:


Resolved
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] [delivery-pipeline-plugin] (JENKINS-27290) Communication Error, Syntax Problem
















































Patrik Boström
 assigned  JENKINS-27290 to Kay Strobach



Communication Error, Syntax Problem
















Change By:


Patrik Boström
(25/Mar/15 9:40 PM)




Assignee:


Patrik Boström
Kay Strobach



























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







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-27604) Error communicating to server! Server Error
















































Patrik Boström
 assigned  JENKINS-27604 to Unassigned



Error communicating to server! Server Error
















Change By:


Patrik Boström
(25/Mar/15 9:38 PM)




Assignee:


Patrik Boström



























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







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

[JIRA] [git-client-plugin] (JENKINS-27606) Git submodule updates ignore url.insteadOf settings in the global config file

2015-03-25 Thread chadkillingswo...@gmail.com (JIRA)















































Chad Killingsworth
 created  JENKINS-27606


Git submodule updates ignore url.insteadOf settings in the global config file















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git-client-plugin



Created:


25/Mar/15 9:35 PM



Description:


When the git config file has url settings such as:

[url "ssh://g...@myserver.com:7999"]
	insteadOf = https://myserver.com:8443/scm

git submodule update still attempts to clone from the https url. I'm using this to try to override the remote URL for specific submodules.

Here's the error message:

Cloning into 'folder/modulename'...
fatal: Authentication failed for 'https://myserver.com:8443/scm/proj/project.git/'
Clone of 'https://myserver.com:8443/scm/proj/project.git/' into submodule path 'folder/modulename' failed

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:86)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$6.execute(CliGitAPIImpl.java:893)
	at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:83)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1047)
	at hudson.scm.SCM.checkout(SCM.java:484)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1270)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531)
	at hudson.model.Run.execute(Run.java:1751)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)




Environment:


Jenkins: 1.605 on Windows

git-client-plugin: 1.16.1




Project:


Jenkins



Priority:


Minor



Reporter:


Chad Killingsworth

























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







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-27604) Error communicating to server! Server Error















































Patrik Boström
 commented on  JENKINS-27604


Error communicating to server! Server Error















Is the parameterized-trigger plugin installed and enabled?



























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







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-27604) Error communicating to server! Server Error

2015-03-25 Thread zio...@gmail.com (JIRA)















































KY Lee
 updated  JENKINS-27604


Error communicating to server! Server Error
















Change By:


KY Lee
(25/Mar/15 9:25 PM)




Attachment:


MultiJob.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] [teamconcert-plugin] (JENKINS-27605) Allow setting the max SCM content threads on non-build definition builds

2015-03-25 Thread develo...@trajano.net (JIRA)















































Archimedes Trajano
 created  JENKINS-27605


Allow setting the max SCM content threads on non-build definition builds















Issue Type:


Improvement



Assignee:


Unassigned


Components:


teamconcert-plugin



Created:


25/Mar/15 9:23 PM



Description:


Allow setting the max SCM content threads on non-build definition builds, I have tried to do it through preferences.properties and through -Dteam.scm.maxContentThreads=100 to no avail.

I think there is some code being thought of but it isn't fleshed out yet.

https://github.com/jenkinsci/teamconcert-plugin/blob/master/com.ibm.team.build.hjplugin-rtc/src/main/java/com/ibm/team/build/internal/hjplugin/rtc/RepositoryConnection.java#L430




Environment:


JTS 4.0.0




Project:


Jenkins



Labels:


team-concert




Priority:


Minor



Reporter:


Archimedes Trajano

























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







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-27604) Error communicating to server! Server Error

2015-03-25 Thread zio...@gmail.com (JIRA)















































KY Lee
 updated  JENKINS-27604


Error communicating to server! Server Error
















Change By:


KY Lee
(25/Mar/15 9:23 PM)




Environment:


Jenkins ver. 1.580.3 on Windows Server 2012 R2 running as a windows service.Plugins:parameterized-trigger	2.26delivery-pipeline-plugin	0.8.9jenkins-multijob-plugin	1.16
junit	1.4



























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







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-27604) Error communicating to server! Server Error

2015-03-25 Thread zio...@gmail.com (JIRA)

KY Lee
created JENKINS-27604

Error communicating to server! Server Error

Issue Type:

Bug

Assignee:

Patrik Boström

Attachments:

DeliveryPipelineView-StackTrace.txt, ParameterizedTrigger-stacktrace.txt

Components:

delivery-pipeline-plugin, parameterized-trigger-plugin

Created:

25/Mar/15 9:22 PM

Description:

Got this error when trying out Delivery Pipeline Plugin with 3 freestyle projects that basically echo Hello world and all parsed environment variables from Jenkins.

I also cannot proceed with any MultiJob projects with MultiJob phases, with those 3 new empty freestyle jobs with default parameters.

I don't know which plugin is the culprit, but according to the stacktraces, parameterizedtrigger has the most occurrences.

Let me know if you need more info.

Environment:

Jenkins ver. 1.580.3 on Windows Server 2012 R2 running as a windows service.

Plugins:

parameterized-trigger 2.26

delivery-pipeline-plugin 0.8.9

jenkins-multijob-plugin 1.16

Project:

Jenkins

Priority:

Critical

Reporter:

KY Lee

[JIRA] [core] (JENKINS-27569) Polling error from git

2015-03-25 Thread mark.earl.wa...@gmail.com (JIRA)
















































Mark Waite
 closed  JENKINS-27569 as Cannot Reproduce


Polling error from git 
















Change By:


Mark Waite
(25/Mar/15 9:17 PM)




Status:


Resolved
Closed



























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







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

[JIRA] [job-dsl-plugin] (JENKINS-27603) ConcurrentModificationException when running seed job

2015-03-25 Thread m...@daniel-spilker.com (JIRA)















































Daniel Spilker
 created  JENKINS-27603


ConcurrentModificationException when running seed job















Issue Type:


Bug



Assignee:


Daniel Spilker



Components:


job-dsl-plugin



Created:


25/Mar/15 8:46 PM



Description:


Under some circumstances, the seed job fails with a ConcurrentModificationException.


java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:922)
at java.util.HashMap$KeyIterator.next(HashMap.java:956)
at com.google.common.collect.AbstractMapBasedMultimap$WrappedCollection$WrappedIterator.next(AbstractMapBasedMultimap.java:484)
at com.google.common.collect.Iterators$7.computeNext(Iterators.java:701)
at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at com.google.common.collect.Sets.removeAllImpl(Sets.java:1598)
at com.google.common.collect.Sets.removeAllImpl(Sets.java:1627)
at com.google.common.collect.AbstractMapBasedMultimap$WrappedSet.removeAll(AbstractMapBasedMultimap.java:614)
at javaposse.jobdsl.plugin.ExecuteDslScripts.updateTemplates(ExecuteDslScripts.java:226)
at javaposse.jobdsl.plugin.ExecuteDslScripts.perform(ExecuteDslScripts.java:183)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772)
at hudson.model.Build$BuildExecution.build(Build.java:199)
at hudson.model.Build$BuildExecution.doRun(Build.java:160)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535)
at hudson.model.Run.execute(Run.java:1732)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:234)





Environment:


Job DSL Plugin 1.25




Project:


Jenkins



Priority:


Major



Reporter:


Daniel Spilker

























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] [job-dsl-plugin] (JENKINS-27602) Job gets deleted and re-created after removing "using"

2015-03-25 Thread m...@daniel-spilker.com (JIRA)















































Daniel Spilker
 created  JENKINS-27602


Job gets deleted and re-created after removing "using"















Issue Type:


Bug



Assignee:


Daniel Spilker



Components:


job-dsl-plugin



Created:


25/Mar/15 8:43 PM



Description:


After removing template inheritance from a job, the job is deleted and re-created. Thereby the job loses it's build history.

Initial DSL script with template inheritance:

job('test') {
  using('template')
}


Modified DSL script without inheritance:

job('test') {
}


Seed job output:

Processing provided DSL script
Existing templates:
template
Unreferenced templates:
template
Adding items:
GeneratedJob{name='test'}
Removing items:
GeneratedJob{name='test', template='template'}





Project:


Jenkins



Priority:


Major



Reporter:


Daniel Spilker

























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-26900) Hide flyweight master executor when ≥1 heavyweight executors running as subtasks















































SCM/JIRA link daemon
 commented on  JENKINS-26900


Hide flyweight master executor when ≥1 heavyweight executors running as subtasks















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/jenkins/model/queue/AsynchronousExecution.java
 core/src/main/resources/lib/hudson/executors.jelly
http://jenkins-ci.org/commit/jenkins/bb80340a92538cdc783a55a28d42bcacd46673f4
Log:
  [FIXED JENKINS-26900] AsynchronousExecution.displayCell





























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-26900) Hide flyweight master executor when ≥1 heavyweight executors running as subtasks
















































SCM/JIRA link daemon
 resolved  JENKINS-26900 as Fixed


Hide flyweight master executor when ≥1 heavyweight executors running as subtasks
















Change By:


SCM/JIRA link daemon
(25/Mar/15 8:26 PM)




Status:


In Progress
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-26090) Executables.getExecutor
















































SCM/JIRA link daemon
 resolved  JENKINS-26090 as Fixed


Executables.getExecutor
















Change By:


SCM/JIRA link daemon
(25/Mar/15 8:26 PM)




Status:


In Progress
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-26092) executors.jelly interface underspecified















































SCM/JIRA link daemon
 commented on  JENKINS-26092


executors.jelly interface underspecified















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/resources/lib/hudson/buildProgressBar.jelly
http://jenkins-ci.org/commit/jenkins/09f7a2d3d120d77497da1e566a6719ec6feac7ee
Log:
  JENKINS-26092 Noting some things that could be improved.





























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-22941) Way to mark an Executable that should not block isReadyToRestart















































SCM/JIRA link daemon
 commented on  JENKINS-22941


Way to mark an Executable that should not block isReadyToRestart















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/Executor.java
 core/src/main/java/hudson/model/RestartListener.java
 core/src/main/java/jenkins/model/Jenkins.java
 core/src/main/java/jenkins/model/queue/AsynchronousExecution.java
http://jenkins-ci.org/commit/jenkins/8589b211f9a99fa47d022a77bd7936636175898a
Log:
  [FIXED JENKINS-22941] AsynchronousExecution.blocksRestart





























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-22941) Way to mark an Executable that should not block isReadyToRestart
















































SCM/JIRA link daemon
 resolved  JENKINS-22941 as Fixed


Way to mark an Executable that should not block isReadyToRestart
















Change By:


SCM/JIRA link daemon
(25/Mar/15 8:26 PM)




Status:


In Progress
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-25938) Lock an Executor without creating a Thread















































SCM/JIRA link daemon
 commented on  JENKINS-25938


Lock an Executor without creating a Thread















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/AbstractBuild.java
 core/src/main/java/hudson/model/Computer.java
 core/src/main/java/hudson/model/Executor.java
 core/src/main/java/hudson/model/OneOffExecutor.java
 core/src/main/java/hudson/model/Queue.java
 core/src/main/java/hudson/model/ResourceController.java
 core/src/main/java/hudson/model/queue/WorkUnitContext.java
 core/src/main/java/jenkins/model/queue/Executable2.java
http://jenkins-ci.org/commit/jenkins/46a900f4cb468853c5dca844d258b5b862c3a8bf
Log:
  JENKINS-25938 Introduced AsynchronousExecutable.





























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-26090) Executables.getExecutor















































SCM/JIRA link daemon
 commented on  JENKINS-26090


Executables.getExecutor















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/Run.java
 core/src/main/java/hudson/model/queue/Executables.java
http://jenkins-ci.org/commit/jenkins/f2f988e81fc42d69d32c09dfd8958d53e4dedb30
Log:
  [FIXED JENKINS-26090] Executables.getExecutor





























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-27601) instance caps incorrectly calculated

2015-03-25 Thread tba...@circle.com (JIRA)

Trevor Baker
created JENKINS-27601

instance caps incorrectly calculated

Issue Type:

Bug

Assignee:

Francis Upton

Components:

ec2-plugin

Created:

25/Mar/15 8:19 PM

Description:

Instance counts towards the cap feature are incorrectly counted when you use the same AMI for multiple jenkins slave types it with differing ec2 instance types. The count is a sum of all the instances provisioned by the plugin rather than the number provisioned per discrete slave configuration.

https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/EC2Cloud.java#L241

If the ami id and the tag jenkins_slave_type match, it is counted toward the cap.

Scenario:

slave description: small slave
ami: ami-12345
instance type: t1.small
cap: 5

slave description: big slave
ami: ami-12345
instance type: c3.xlarge
cap: 2

If there are five "small slaves" running it won't provision any "big slaves", reports the following:

AMI Instance cap of 2 reached for ami ami-12345, not provisioning.

Environment:

ec2-plugin 1.26

jenkins 1.605

Project:

Jenkins

Priority:

Major

Reporter:

Trevor Baker

[JIRA] [delivery-pipeline-plugin] (JENKINS-27584) NullPointerException in ManualStep.getManualStepLatest















































Patrik Boström
 commented on  JENKINS-27584


NullPointerException in ManualStep.getManualStepLatest















Found one way to produce NPE, have done a fix on this branch:
https://github.com/Diabol/delivery-pipeline-plugin/tree/JENKINS-27584_NPE

Do you have possibility to test 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] [weblogic-deployer-plugin] (JENKINS-27561) Error plugin weblogic

2015-03-25 Thread r...@orange.fr (JIRA)













































  
Raphael CHAUMIER
 edited a comment on  JENKINS-27561


Error plugin weblogic
















So your deployment failed (it's due to a Spring misconfigurationof the bean 'actionEvaluator' in your war). This is why the plugin execution failed

If you fix the issue and run the job after I think it will be ok.



























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] [weblogic-deployer-plugin] (JENKINS-27561) Error plugin weblogic

2015-03-25 Thread r...@orange.fr (JIRA)















































Raphael CHAUMIER
 commented on  JENKINS-27561


Error plugin weblogic















So your deployment failed (it's due to a Spring misconfigurationof the bean 'actionEvaluator' in your war). This is why the plugin execution failed

If you fix the issue and run the job after. I thin it will be ok.



























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] [ssh-slaves-plugin] (JENKINS-7641) Slaves hang when archiving artifacts

2015-03-25 Thread steve.si...@oracle.com (JIRA)













































  
steve sides
 edited a comment on  JENKINS-7641


Slaves hang when archiving artifacts
















I see this also (the stack trace if from killing the job while it's archiving). The problem is sometimes it gets stuck while archiving. It looks as it everything is archived, but for some reason the job won't complete..until you cancel it.
Using 1.598. Jenkins running on RHEL6.4 using jdk 1.8.0_31.



























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-plugin] (JENKINS-27477) github-plugin does not work with "insteadOf" in git url

2015-03-25 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-27477


github-plugin does not work with "insteadOf" in git url















Could PR your proposed changes for further discussion?



























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-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder















































SCM/JIRA link daemon
 commented on  JENKINS-25127


Hook uninstalled if job is in a subfolder















Code changed in jenkins
User: Ryan Gardner
Path:
 src/main/java/com/cloudbees/jenkins/Cleaner.java
http://jenkins-ci.org/commit/github-plugin/2a49bac65fb7e05cd083e8b445ad2fcfb689ae0a
Log:
  Address JENKINS-25127 by using getAllIItems instead of getItems





























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







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-27584) NullPointerException in ManualStep.getManualStepLatest















































Patrik Boström
 commented on  JENKINS-27584


NullPointerException in ManualStep.getManualStepLatest















Do you have any information how to reproduce the issue?



























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







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

[JIRA] [walldisplay-plugin] (JENKINS-26873) Sorting by Status does not work correctly

2015-03-25 Thread pellepels...@gmail.com (JIRA)
















































Christian Pelster
 resolved  JENKINS-26873 as Fixed


Sorting by Status does not work correctly
















Change By:


Christian Pelster
(25/Mar/15 6:58 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] [walldisplay-plugin] (JENKINS-26873) Sorting by Status does not work correctly