[JIRA] [github-plugin] (JENKINS-23995) Adding commit status context in github-plugin
SCM/JIRA link daemon commented on JENKINS-23995 Adding commit status context in github-plugin Code changed in jenkins User: Kanstantsin Shautsou Path: pom.xml src/main/java/com/cloudbees/jenkins/GitHubCommitNotifier.java src/main/java/com/cloudbees/jenkins/GitHubSetCommitStatusBuilder.java http://jenkins-ci.org/commit/github-plugin/58a61481fac3b9d920e233639a1a605fa65ad38b Log: [FIXED JENKINS-23995] Set commit status context This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23995) Adding commit status context in github-plugin
SCM/JIRA link daemon commented on JENKINS-23995 Adding commit status context in github-plugin Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/cloudbees/jenkins/GitHubCommitNotifier.java src/main/java/com/cloudbees/jenkins/GitHubSetCommitStatusBuilder.java http://jenkins-ci.org/commit/github-plugin/598565c77c4bfab31894e009ade676d9c3a0ef11 Log: Merge pull request #50 from KostyaSha/JENKINS-23995 [FIXED JENKINS-23995] Set context for GH status Compare: https://github.com/jenkinsci/github-plugin/compare/b82a66631be0...598565c77c4b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23995) Adding commit status context in github-plugin
SCM/JIRA link daemon resolved JENKINS-23995 as Fixed Adding commit status context in github-plugin Change By: SCM/JIRA link daemon (25/Feb/15 8:14 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] [core] (JENKINS-26042) Highlight most recent build in Dashboard
Alexandru Gheorghe commented on JENKINS-26042 Highlight most recent build in Dashboard In addition to this (tell me please if another separate ticket is needed) we could even provide a "recent builds" list to be displayed just above Build Queue (or under) for example in dashboard. We could show the last 10 most recent builds, the reason for this is that in All view with 22 items it's difficult to spot which were build just a while ago. Can show something like: menu here New item ... ... ... Build Queue No Builds in queue. Most recent 10 builds Status my_build1 my_build2 ... Build Executor Status 1 Idle 2 Idle N Status This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves-plugin] (JENKINS-7641) Slaves hang when archiving artifacts
pedro reis commented on JENKINS-7641 Slaves hang when archiving artifacts Havin sometimes this issue with Jenkins Master v1.565.3 @ Ubuntu 2.6.24-23-server and Jenkins Slave @ Windows 7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp-plugin] (JENKINS-26059) Expand variables before using conditional
Brantone resolved JENKINS-26059 as Fixed Expand variables before using conditional Change By: Brantone (25/Feb/15 9:01 AM) Status: In Progress Resolved Assignee: Brantone 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] [hockeyapp-plugin] (JENKINS-26059) Expand variables before using conditional
Brantone started work on JENKINS-26059 Expand variables before using conditional Change By: Brantone (25/Feb/15 9:00 AM) 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] [hockeyapp-plugin] (JENKINS-26059) Expand variables before using conditional
Brantone commented on JENKINS-26059 Expand variables before using conditional https://github.com/jenkinsci/hockeyapp-plugin/pull/27 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle-plugin] (JENKINS-17287) Provide support for ScalaStyle warnings
Jan Goyvaerts commented on JENKINS-17287 Provide support for ScalaStyle warnings Pending I presume. Does somebody know a good large Scala project build with Maven ? Such that it generates loads of warnings ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [timestamper-plugin] (JENKINS-21687) Add api call for current jenkins time
stevengbrown assigned JENKINS-21687 to Unassigned Add api call for current jenkins time Change By: stevengbrown (25/Feb/15 9:17 AM) Assignee: stevengbrown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [timestamper-plugin] (JENKINS-27054) Radio buttons would be easier to click if associated text was part of a
SCM/JIRA link daemon resolved JENKINS-27054 as Fixed Radio buttons would be easier to click if associated text was part of a Change By: SCM/JIRA link daemon (25/Feb/15 9:15 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] [timestamper-plugin] (JENKINS-27054) Radio buttons would be easier to click if associated text was part of a
SCM/JIRA link daemon commented on JENKINS-27054 Radio buttons would be easier to click if associated text was part of a Code changed in jenkins User: Steven Brown Path: src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory/usersettings.jelly http://jenkins-ci.org/commit/timestamper-plugin/20ce1113d7a2e4f8e6e4ac0b6495a8d6e018778c Log: [FIXED JENKINS-27054] Wrap radio buttons in a label element This allows the options to be selected by clicking on the text. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-login-plugin] (JENKINS-27117) google login plugin not working
sudhakar bellamkonda created JENKINS-27117 google login plugin not working Issue Type: Bug Assignee: recampbell Attachments: Screenshot-from-2015-02-25.png Components: google-login-plugin Created: 25/Feb/15 9:18 AM Description: the below error pops up while login, i.e. jenkins takes the google credentials and throws this error. screenshot of conf attached. 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$4.doDispatch(MetaClass.java:211) 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:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:91) 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:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
[JIRA] [timestamper-plugin] (JENKINS-26794) Simple console timestamp option
stevengbrown assigned JENKINS-26794 to Unassigned Simple console timestamp option Change By: stevengbrown (25/Feb/15 9:22 AM) Assignee: stevengbrown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27113) Escape absolute path contained in globaly exposed variable $WORKSPACE
Daniel Beck commented on JENKINS-27113 Escape absolute path contained in globaly exposed variable $WORKSPACE I don't think escaping works like you expect it to. In particular, this change would break everything that today handles spaces correctly. What specifically do you have problems with? In shell build steps, for example, you can just wrap $WORKSPACE in double quotes and you're good. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance-plugin] (JENKINS-26990) Text parameters get converted to String
AppId Man commented on JENKINS-26990 Text parameters get converted to String I couldn't manage to find the source of this bug, but I wrote a workaround which works for me. https://github.com/appidman/jenkins-inheritance-plugin/commit/cb39016b846821dcec21d06e1537aa1c06aa5163 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26042) Highlight most recent build in Dashboard
Daniel Beck commented on JENKINS-26042 Highlight most recent build in Dashboard You're describing something completely unrelated. Keep issues limited to one problem/feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27116) Deployment fail after successful Build
Daniel Beck resolved JENKINS-27116 as Not A Defect Deployment fail after successful Build This is an issue tracker, not a support site. Change By: Daniel Beck (25/Feb/15 9:35 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [timestamper-plugin] (JENKINS-27054) Radio buttons would be easier to click if associated text was part of a
stevengbrown commented on JENKINS-27054 Radio buttons would be easier to click if associated text was part of a Thanks Paul, I've added the label tags. Nice usability improvement. If I remove the closing input tags from this file, Jenkins isn't able to parse it. Although the closing tags aren't present in the final generated HTML. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-27118) Exception due to https://api.github.com/repos///collaborators not found
Tadej Janež created JENKINS-27118 Exception due to https://api.github.com/repos///collaborators not found Issue Type: Bug Assignee: Sam Kottler Components: github-oauth-plugin Created: 25/Feb/15 9:48 AM Description: I'm seeing the following exception when a certain user tries to log-in via the GitHub OAuth plugin: Feb 25, 2015 8:57:19 AM SEVERE org.jenkinsci.plugins.GithubAuthenticationToken hasRepositoryPermission an exception was thrown java.util.concurrent.ExecutionException: java.io.FileNotFoundException: https://api.github.com/repos/genialis/genesis/collaborators at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at com.google.common.util.concurrent.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:132) at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2381) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at org.jenkinsci.plugins.GithubAuthenticationToken.hasRepositoryPermission(GithubAuthenticationToken.java:161) at org.jenkinsci.plugins.GithubRequireOrganizationMembershipACL.hasRepositoryPermission(GithubRequireOrganizationMembershipACL.java:246) at org.jenkinsci.plugins.GithubRequireOrganizationMembershipACL.hasPermission(GithubRequireOrganizationMembershipACL.java:92) at hudson.security.ACL.hasPermission(ACL.java:68) at hudson.model.AbstractItem.hasPermission(AbstractItem.java:504) at jenkins.model.Jenkins.getItem(Jenkins.java:2321) at hudson.model.Hudson.getJob(Hudson.java:142) at sun.reflect.GeneratedMethodAccessor300.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) 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:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) 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:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) 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.doF
[JIRA] [timestamper-plugin] (JENKINS-27054) Radio buttons would be easier to click if associated text was part of a
stevengbrown commented on JENKINS-27054 Radio buttons would be easier to click if associated text was part of a Included in 1.5.16 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] [cloudfoundry-plugin] (JENKINS-27119) path attribute in manifest.yml is not evaluated relative to the manifest.yml file
Matthias Vach created JENKINS-27119 path attribute in manifest.yml is not evaluated relative to the manifest.yml file Issue Type: Bug Assignee: William Gautier Components: cloudfoundry-plugin Created: 25/Feb/15 9:59 AM Description: I do have manifest.yml files which contain the attribute "path". e.g "path: web" Additionally I configured the cf plugin to read the manifest from gitRepo/manifest.yml. Now pushing applications fails: ERROR: Could not find file: /home/hudson/workspace//web (No such file or directory) Which is true because the path need to be evaluated relative to the manifest.yml file which would be: /home/hudson/workspace//gitRepo/web Project: Jenkins Priority: Minor Reporter: Matthias Vach This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-27118) Exception due to https://api.github.com/repos///collaborators not found
Tadej Janež updated JENKINS-27118 Exception due to https://api.github.com/repos///collaborators not found This is the screen a user gets when this exception happens. Change By: Tadej Janež (25/Feb/15 10:10 AM) Attachment: Jenkins GitHub OAuth plugin problem.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] [remoting] (JENKINS-26947) Unattended wait in the remoting code
James Nord commented on JENKINS-26947 Unattended wait in the remoting code Have you disabled the PIngThread at all? AFAICT netem does not kill the connection - the remote end will be retransmitting the packets - and as such the channel is not closed. The PingThread should eventually notice this (10 minutes interval + 4 minute timeout) so after at most 14 minutes the connection should be killed and this thread unblock. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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
pedro reis edited a comment on JENKINS-7641 Slaves hang when archiving artifacts Havin sometimes this issue with Jenkins Master v1.565.3 @ Ubuntu 2.6.24-23-server and Jenkins Slave @ Windows 7 but was maybe because of the build not making the *.zip file that is our artifact This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [notification-plugin] (JENKINS-25558) Notifications Plugin does not honor the "http_proxy" environment variable
SCM/JIRA link daemon commented on JENKINS-25558 Notifications Plugin does not honor the "http_proxy" environment variable Code changed in jenkins User: Marcello de Sales Path: src/main/java/com/tikal/hudson/plugins/notification/Protocol.java http://jenkins-ci.org/commit/notification-plugin/da26771d3d37fa77c26345ac7ab35529a9eef31a Log: JENKINS-25558: Notifications Plugin does not honor the "http_proxy" environment variable: Fix This commit partially fixes the problem by using an HTTP Proxy without authentication. In addition, it does not provide test cases, but it does work properly. The message after using a new build of this plugin was as follows: Started by user mdesales Notifying endpoint 'HTTP:https://zapier.com/hooks/catch/o54xyk/' Building in workspace /app/installs/jenkins/jobs/Status Notification/workspace Notifying endpoint 'HTTP:https://zapier.com/hooks/catch/o54xyk/' Finished: SUCCESS (Sorry, in a rush to get things done and I can try providing a test with an internal http proxy server). modified: src/main/java/com/tikal/hudson/plugins/notification/Protocol.java Verifying if the environment variable "http_proxy" is set. If so, decorate the connection with the proxy information before making the HTTP request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [notification-plugin] (JENKINS-25558) Notifications Plugin does not honor the "http_proxy" environment variable
SCM/JIRA link daemon commented on JENKINS-25558 Notifications Plugin does not honor the "http_proxy" environment variable Code changed in jenkins User: Haggai Philip Zagury Path: src/main/java/com/tikal/hudson/plugins/notification/Protocol.java http://jenkins-ci.org/commit/notification-plugin/c5c81d049fb7d2b7bcd17f539825e74c55194476 Log: Merge pull request #16 from marcellodesales/master JENKINS-25558: Notifications Plugin does not honor the "http_proxy" env Variable Compare: https://github.com/jenkinsci/notification-plugin/compare/d3d00a547eed...c5c81d049fb7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactdeployer-plugin] (JENKINS-26629) ArtifactDeployer does absolutely nothing
pedro reis commented on JENKINS-26629 ArtifactDeployer does absolutely nothing This continues to occur at plugin version 0.33. Another doubt on usage: Can we use multiple artifact like this?: stage/*/.zip,stage/*/.tgz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-26947) Unattended wait in the remoting code
Yoann Dubreuil commented on JENKINS-26947 Unattended wait in the remoting code No, I did not disable the ping thread. In fact, I did nothing special, just started a fresh Jenkins instance and connected it to this docker slave. I took the thread dump 30 minutes after the disconnection. Will relaunch the test this afternoon to see if it would ever times out or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactdeployer-plugin] (JENKINS-26629) ArtifactDeployer does absolutely nothing
pedro reis
updated JENKINS-26629
ArtifactDeployer does absolutely nothing
Change By:
pedro reis
(25/Feb/15 10:39 AM)
Description:
We're using Jenkins 1.565.3 and can't operate ArtifactDeployer 0.32
or 0
.
33.
We use matrix jobs, that makes builds in several platforms (maybe this is the problem?).
It doesn't outputs any message (bad or good), even if we explicitly write an invalid input file."Fail build if there are no files to deploy" also doesn't fails the build.Tried also inside Flexible publish:"[Boolean condition] checking [true] against [^(1|y|yes|t|true|on|run)$] (origin token: ${REDO_BUILD})Run condition [Or] enabling perform for step [[ArtifactDeployer] - Deploy the artifacts from build workspace to remote locations]"Anyone has any clues? After overcoming this, what is the correct way of setting the input file(s) and output destination?Input: . Does it accept *?Output: . Do we need to write something like "file://" before? . Are the bars \ or / or \\ or //?Does this
dependends
paths dependend
whether we are in a Jenkins slave windows or linux?
It really shouldn't, so I hope not.
I suggest an example should exist at the plug-in webpage.Thanks in advance
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-27082) Sparse checkouts and submodules: Error on checkout, submodule missing
Ronny Schuetz commented on JENKINS-27082 Sparse checkouts and submodules: Error on checkout, submodule missing @Mark: Good point. Just tried it manually and had to add .gitmodules to .git/info/sparse-checkout to make it work; adding .gitmodules to the sparse checkout paths in the Jenkins job seems to help here as well. Maybe it would help, if git-internal files would be checked out always, independently of the sparse checkout option? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-22637) "Copy Artifacts Plugin" should support ArtifactManager
Markus Eisenmann commented on JENKINS-22637 "Copy Artifacts Plugin" should support ArtifactManager Any progress on this - IMHO long outstanding - 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] [gitlab-hook-plugin] (JENKINS-27101) Undefined method isOlderThan on automatic project creation
Javier Palacios commented on JENKINS-27101 Undefined method isOlderThan on automatic project creation I'm not sure if I understand you, but If I'm right it is maybe a documentation problem. From what I understand in your report, you are actually creating a project from a template, and in that case, the only action taken when copying the template is to replace the repository url and enable the project because template could be disabled). It seems that you are expecting that some variables defined on the template get replaced with some values from payload. It looks like REPOSITORY_URL is actually replaced, but it isn't. Whatever the template has configured as git url is discarded and filled from payload (actually, I use templates with empty git url). And accordingly, the branch specification is kept exactly as in template. And your final job has one useless parameter (probably two). If you remove the two parameters of your template and set the branch specifier to origin/master, you'll probably get what you expect. But take into account that templating only acts when the push is for an unknown repo. Once you get the template realized, you need to enable "classic" automatic branch creation to get extra instances for that same project when other branches are pushed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-27101) Undefined method isOlderThan on automatic project creation
Javier Palacios resolved JENKINS-27101 as Fixed Undefined method isOlderThan on automatic project creation Change By: Javier Palacios (25/Feb/15 11:08 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] [repository-connector-plugin] (JENKINS-24243) Add ability to disable using the global configured proxy
Raphaël UNIQUE commented on JENKINS-24243 Add ability to disable using the global configured proxy ++ important issue also here This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [compress-artifacts-plugin] (JENKINS-27042) java.util.zip.ZipException thrown when reading artifacts from archive larger than 4G
Oliver Gondža started work on JENKINS-27042 java.util.zip.ZipException thrown when reading artifacts from archive larger than 4G Change By: Oliver Gondža (25/Feb/15 11:50 AM) 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] [checkstyle-plugin] (JENKINS-17287) Provide support for ScalaStyle warnings
Ulli Hafner commented on JENKINS-17287 Provide support for ScalaStyle warnings If no one is providing an example project that exposes the bug I can't help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1
Kanstantsin Shautsou commented on JENKINS-27093 Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1 Hi, Paul, could you provide two consecutive build.xml files (you can cut any private if) that were triggered and the result of manual run for git command from polling log? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated
Marcelo Behera commented on JENKINS-11176 Promotion criteria "If the build is a release build" is broken and displays duplicated This is still a problem with Jenkins: 1.575, Release: 2.4.1, Promoted: 2.19. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-27120) Make JacocoPublisher a SimpleBuildStep
Jesse Glick created JENKINS-27120 Make JacocoPublisher a SimpleBuildStep Issue Type: New Feature Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 25/Feb/15 12:56 PM Description: See the guide to allowing this publisher to be used from a Workflow. Project: Jenkins Labels: workflow Priority: Major 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] [build-user-vars-plugin] (JENKINS-26953) Support for workflow-plugin
Jesse Glick updated JENKINS-26953 Support for workflow-plugin Change By: Jesse Glick (25/Feb/15 1:02 PM) Labels: build-user-vars-plugin workflow -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] [shelve-project-plugin] (JENKINS-26432) Allow shelving of Workflow
Jesse Glick updated JENKINS-26432 Allow shelving of Workflow Change By: Jesse Glick (25/Feb/15 1:01 PM) Labels: Shelve workflow -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] [testng-plugin] (JENKINS-27121) Make testng.Publisher a SimpleBuildStep
Jesse Glick created JENKINS-27121 Make testng.Publisher a SimpleBuildStep Issue Type: New Feature Assignee: Nalin Makar Components: testng-plugin Created: 25/Feb/15 1:01 PM Description: See the guide for making this publisher available from a Workflow build. Project: Jenkins Labels: workflow Priority: Major 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] [build-user-vars-plugin] (JENKINS-26953) Support for workflow-plugin
Jesse Glick updated JENKINS-26953 Support for workflow-plugin Change By: Jesse Glick (25/Feb/15 1:02 PM) Assignee: Jesse Glick Component/s: workflow-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] [build-user-vars-plugin] (JENKINS-26953) Workflow support for Build User Vars
Jesse Glick updated JENKINS-26953 Workflow support for Build User Vars Change By: Jesse Glick (25/Feb/15 1:03 PM) Summary: Support Workflow support for workflow-plugin Build User Vars Issue Type: Improvement New Feature Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slack-plugin] (JENKINS-27122) Resets values for folded parameters when you hit "Apply" but not "Save"
Timur Batyrshin created JENKINS-27122 Resets values for folded parameters when you hit "Apply" but not "Save" Issue Type: Bug Assignee: Unassigned Components: slack-plugin Created: 25/Feb/15 1:05 PM Description: There are some parameters inside job folded under "Advanced" button. When you edit the job and hit "Apply" rather than "Save" the parameters for "Notify Repeated Failure" and "Include Test Summary" are reset to default values (true and false respectively). I see this behaviour both when "Advanced" section is expanded or not expanded. Project: Jenkins Priority: Minor Reporter: Timur Batyrshin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slack-plugin] (JENKINS-27122) Resets values for folded parameters when you hit "Apply" but not "Save"
Timur Batyrshin commented on JENKINS-27122 Resets values for folded parameters when you hit "Apply" but not "Save" Actually this probably does not directly relate to "Apply" button. I've just started to see this for one of my jobs after I've hit "Apply" button but it could be conincidence. No matter what button I hit – "Apply" or "Save" – these 2 parameters are not updated (nor in config.xml). Other parameters are updated 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] [build-failure-analyzer-plugin] (JENKINS-27123) Workflow support for Build Failure Analyzer
Jesse Glick created JENKINS-27123 Workflow support for Build Failure Analyzer Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 25/Feb/15 1:19 PM Description: At a minimum, replacing AbstractProject with Job wherever it appears, and AbstractBuild with Run; unclear if you are relying on specific methods in these types that have no replacement. TransientProjectActionFactory may be replaced by TransientActionFactory. Project: Jenkins Labels: workflow Priority: Major 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] [build-failure-analyzer-plugin] (JENKINS-27123) Workflow support for Build Failure Analyzer
SCM/JIRA link daemon commented on JENKINS-27123 Workflow support for Build Failure Analyzer Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/2ec399aa1d54432b22fbd5052b24d824da4670d3 Log: JENKINS-27120 JENKINS-27121 JENKINS-26953 JENKINS-27123 JENKINS-26432 Noting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-27120) Make JacocoPublisher a SimpleBuildStep
SCM/JIRA link daemon commented on JENKINS-27120 Make JacocoPublisher a SimpleBuildStep Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/2ec399aa1d54432b22fbd5052b24d824da4670d3 Log: JENKINS-27120 JENKINS-27121 JENKINS-26953 JENKINS-27123 JENKINS-26432 Noting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shelve-project-plugin] (JENKINS-26432) Allow shelving of Workflow
SCM/JIRA link daemon commented on JENKINS-26432 Allow shelving of Workflow Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/2ec399aa1d54432b22fbd5052b24d824da4670d3 Log: JENKINS-27120 JENKINS-27121 JENKINS-26953 JENKINS-27123 JENKINS-26432 Noting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng-plugin] (JENKINS-27121) Make testng.Publisher a SimpleBuildStep
SCM/JIRA link daemon commented on JENKINS-27121 Make testng.Publisher a SimpleBuildStep Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/2ec399aa1d54432b22fbd5052b24d824da4670d3 Log: JENKINS-27120 JENKINS-27121 JENKINS-26953 JENKINS-27123 JENKINS-26432 Noting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars-plugin] (JENKINS-26953) Workflow support for Build User Vars
SCM/JIRA link daemon commented on JENKINS-26953 Workflow support for Build User Vars Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/2ec399aa1d54432b22fbd5052b24d824da4670d3 Log: JENKINS-27120 JENKINS-27121 JENKINS-26953 JENKINS-27123 JENKINS-26432 Noting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slack-plugin] (JENKINS-27122) Resets values for folded parameters when you hit "Apply" but not "Save"
Timur Batyrshin commented on JENKINS-27122 Resets values for folded parameters when you hit "Apply" but not "Save" P.S. my version of plugin is 1.7, I'm running Jenkins 1.599 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27124) When generating the jobs locally, exceptions occur when folder don't exist yet
Nico Mommaerts created JENKINS-27124 When generating the jobs locally, exceptions occur when folder don't exist yet Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 25/Feb/15 1:49 PM Description: When running the DSL scripts locally, when a job is generated that should be inside a folder, and there is no corresponding directory for that folder, the job quits with an exception. It's rather cumbersome to recreate the Jenkins folder hierarchy locally, especially when there 100's of folders. Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.simontuffs.onejar.Boot.run(Boot.java:313) at com.simontuffs.onejar.Boot.main(Boot.java:161) Caused by: java.io.FileNotFoundException: folder\subfolder\jobname.xml (The system cannot find the path specified) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:212) at java.io.FileOutputStream.(FileOutputStream.java:165) at java.io.FileWriter.(FileWriter.java:90) at org.codehaus.groovy.runtime.DefaultGroovyMethods.newWriter(DefaultGroovyMethods.java:16226) at org.codehaus.groovy.runtime.DefaultGroovyMethods.write(DefaultGroovyMethods.java:15326) at org.codehaus.groovy.runtime.dgm$931.invoke(Unknown Source) at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMet hodSite.java:271) at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) at javaposse.jobdsl.dsl.FileJobManagement.createOrUpdateConfig(FileJobManagement.groovy:49) at javaposse.jobdsl.dsl.DslScriptLoader.extractGeneratedJobs(DslScriptLoader.java:111) at javaposse.jobdsl.dsl.DslScriptLoader.runDslEngine(DslScriptLoader.java:94) at javaposse.jobdsl.dsl.DslScriptLoader$runDslEngine.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) at javaposse.jobdsl.Run$_main_closure2.doCall(Run.groovy:35) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:877) at groovy.lang.Closure.call(Closure.java:412) at groovy.lang.Closure.call(Closure.java:425) at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1376) at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1348) at org.codehaus.groovy.runtime.dgm$162.invoke(Unknown Source) at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMet hodSite.java:271) at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.gr
[JIRA] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Brice Ruzand commented on JENKINS-27100 Regressions in 1.12 and 1.13 I have got the same trouble. If you open the missing image URL, you ve got the folling stack trace (it may help) : Caused by: java.lang.Error: Unresolved compilation problem: Messages cannot be resolved at hudson.plugins.performance.PerformanceReportMap.doRespondingTimeGraph(PerformanceReportMap.java:206) at sun.reflect.GeneratedMethodAccessor565.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) ... 77 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Brice Ruzand edited a comment on JENKINS-27100 Regressions in 1.12 and 1.13 I have got the same trouble, Performance Breakdown by URI charts cannot be showed. If you open the missing image URL, you ve got the folling stack trace (it may help) : Caused by: java.lang.Error: Unresolved compilation problem: Messages cannot be resolved at hudson.plugins.performance.PerformanceReportMap.doRespondingTimeGraph(PerformanceReportMap.java:206) at sun.reflect.GeneratedMethodAccessor565.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) ... 77 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27125) Support for ignorePostCommitHooks in the scm trigger
Nico Mommaerts created JENKINS-27125 Support for ignorePostCommitHooks in the scm trigger Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 25/Feb/15 1:55 PM Description: The xml should look like this: @midnight true Corresponds to the 'Ignore post-commits hook' checkbox in the scm trigger part. Project: Jenkins Priority: Minor Reporter: Nico Mommaerts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27125) Support for ignorePostCommitHooks in the scm trigger
Nico Mommaerts assigned JENKINS-27125 to Nico Mommaerts Support for ignorePostCommitHooks in the scm trigger Change By: Nico Mommaerts (25/Feb/15 1:56 PM) Assignee: Daniel Spilker Nico Mommaerts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-26947) Unattended wait in the remoting code
Yoann Dubreuil commented on JENKINS-26947 Unattended wait in the remoting code The executor thread is still blocked 2 hours after slave gets disconnected. Stack of the blocked thread is: "Executor #0 for dumb-docker-ssh : executing gameoflife #41 / waiting for hudson.remoting.Channel@7b736159:Channel to Maven [java, -cp, /home/jenkins/bis/maven31-agent.jar:/home/jenkins/bis/tools/hudson.tasks.Maven_MavenInstallation/3.2.2/boot/plexus-classworlds-2.5.1.jar:/home/jenkins/bis/tools/hudson.tasks.Maven_MavenInstallation/3.2.2/conf/logging, jenkins.maven3.agent.Maven31Main, /home/jenkins/bis/tools/hudson.tasks.Maven_MavenInstallation/3.2.2, /home/jenkins/bis/slave.jar, /home/jenkins/bis/maven31-interceptor.jar, /home/jenkins/bis/maven3-interceptor-commons.jar, 42104]" daemon prio=10 tid=0x7f11f0187800 nid=0x6d4f in Object.wait() [0x7f1245eb2000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x879416d8> (a hudson.remoting.UserRequest) at hudson.remoting.Request.call(Request.java:146) - locked <0x879416d8> (a hudson.remoting.UserRequest) at hudson.remoting.Channel.call(Channel.java:751) at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:161) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:840) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1745) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be
Lorelei McCollum created JENKINS-27126 New Scroll bar in Jenkins Build history is showing when shouldn't be Issue Type: Bug Assignee: Unassigned Attachments: jenkins.png Components: core Created: 25/Feb/15 2:33 PM Description: We just updated to the latest jenkins version. We like the updates to the build history to control really long text. However it seems we are always seeing "scroll bars" now which are HUGE, but the text is not scrollable and does show up entirely. So not sure why the scroll bar is there This may be an enhancement and not a bug.. but he fact the txt isn't scrollable is why I created a bug. See the screen shot When the txt is longer it is actually wrapping.. so not sure why we have the scroll bar then? I also may have tagged the wrong component and I am sorry if I did so. Project: Jenkins Priority: Minor Reporter: Lorelei McCollum This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Marcus Jacobsson commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted Have the same problem with Jenkins LTS 1.580.3. In our case the nodes goes offline a few hours after restarting the master server and it's not all node, just a few each time (different nodes each time). The server is running on Ubuntu 14.04 and the slaves are running Windows 7 x64 Connection was broken java.io.EOFException at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:616) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuildscript-plugin] (JENKINS-27089) Unexpected behavior when selecting "Run scripts only ..." in a post-build action
Skip Williams commented on JENKINS-27089 Unexpected behavior when selecting "Run scripts only ..." in a post-build action Sorry, this issue does not involve "Execute a set of scripts" but rather "Post build task". If I select "Post build task" from the "Add post-build action" dropdown, I can create multiple post build tasks and then I can get myself into the scenario originally described. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-26947) Unattended wait in the remoting code
James Nord commented on JENKINS-26947 Unattended wait in the remoting code possibly a duplicate of JENKINS-10840 Soemthing strange is going on with Docker and tc. with 2 freestyle builds I see a failure and the salve is disconnected with. noformat java.io.IOException: remote file operation failed: /home/jenkins/data/jenkins-slave.exe at hudson.remoting.Channel@7407d0f5:docker_ssh: hudson.remoting.ChannelClosedException: channel is already closed at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:967) at hudson.FilePath.exists(FilePath.java:1435) at org.jenkinsci.modules.windows_slave_installer.SlaveExeUpdater$1.call(SlaveExeUpdater.java:46) at org.jenkinsci.modules.windows_slave_installer.SlaveExeUpdater$1.call(SlaveExeUpdater.java:37) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:549) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:751) at hudson.FilePath.act(FilePath.java:978) ... 9 more Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) ERROR: Socket connection to SSH server was lost java.io.IOException: Peer sent DISCONNECT message (reason code 2): Packet corrupt at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:766) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:489) at java.lang.Thread.run(Thread.java:745) noformat But a single bit packet corruption should cause the packet to be thrown away by the OS layer due to a TCP checksum miss-match and not to be seen by the application. The other interesting thing is that a build can be runnign fine and it only dies when a new build is kicked off - I would not expect an issue in setting up a new channel in the multiplex (from what KK said) to fail the other channels. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-26947) Unattended wait in the remoting code
James Nord edited a comment on JENKINS-26947 Unattended wait in the remoting code possibly a duplicate of JENKINS-10840 Soemthing strange is going on with Docker and tc. with 2 freestyle builds I see a failure and the salve is disconnected with. java.io.IOException: remote file operation failed: /home/jenkins/data/jenkins-slave.exe at hudson.remoting.Channel@7407d0f5:docker_ssh: hudson.remoting.ChannelClosedException: channel is already closed at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:967) at hudson.FilePath.exists(FilePath.java:1435) at org.jenkinsci.modules.windows_slave_installer.SlaveExeUpdater$1.call(SlaveExeUpdater.java:46) at org.jenkinsci.modules.windows_slave_installer.SlaveExeUpdater$1.call(SlaveExeUpdater.java:37) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:549) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:751) at hudson.FilePath.act(FilePath.java:978) ... 9 more Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) ERROR: Socket connection to SSH server was lost java.io.IOException: Peer sent DISCONNECT message (reason code 2): Packet corrupt at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:766) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:489) at java.lang.Thread.run(Thread.java:745) But a single bit packet corruption should cause the packet to be thrown away by the OS layer due to a TCP checksum miss-match and not to be seen by the application. The other interesting thing is that a build can be runnign fine and it only dies when a new build is kicked off - I would not expect an issue in setting up a new channel in the multiplex (from what KK said) to fail the other channels. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testfairy-plugin] (JENKINS-26991) jarsigner failing with "Invalid keystore format"
Gil Tselsnchuk resolved JENKINS-26991 as Fixed jarsigner failing with "Invalid keystore format" Keystore type "pkcs12" support added Change By: Gil Tselsnchuk (25/Feb/15 3:10 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] [testfairy-plugin] (JENKINS-26991) jarsigner failing with "Invalid keystore format"
Gil Tselsnchuk edited a comment on JENKINS-26991 jarsigner failing with "Invalid keystore format" Keystore type "pkcs12" support added in Version 2.4 https://wiki.jenkins-ci.org/display/JENKINS/TestFairy+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] [workflow-plugin] (JENKINS-27127) wait/notify steps
Jesse Glick
created JENKINS-27127
wait/notify steps
Issue Type:
New Feature
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
25/Feb/15 3:26 PM
Description:
waitUntil (JENKINS-25570) is useful when you need to poll for some external result. But there are cases where direct notification of a state change is possible, and this is more efficient than repeatedly polling. So there should be a wait step, probably with an optional timeout.
One use case is for a flow to await an event notification from an external system. To support this it would probably suffice to have an UnprotectedRootAction endpoint accepting POST requests (or even GET, for convenience); like /git/notifyCommit and similar endpoints, the event would be advisory, so the flow would need to verify that the event really took place:
while (externalSystemNotReady()) {wait()}
Alternately/additionally, the endpoint could require a specific event ID, request authentication, accept a (JSON?) payload, etc. You can use input for such purposes, but this is focused on human interaction, rather than REST calls from another mechanical system.
Another use case, which might be different enough to warrant a distinct step, is for one branch of a flow to notify another branch that some condition has been met and that it is safe to proceed; a kind of semaphore. This could serve as a generic alternative to JENKINS-26052 (fork/join):
def done = [:]
parallel a: {
// do prep work A
done.a = true
notify() // wake up all waiters
}, b: {
// do prep work B
done.b = true
notify()
}, c: {
// do prep work C
done.c = true
notify()
}, d: {
while (!(done.a && done.b)) {wait()}
// do later work D
}, e: {
while (!(done.b && done.c)) {wait()}
// do later work E
}
Here the D branch could start as soon as A and B are finished even while C is running, whereas E could start as soon as B and C are finished even if A is taking longer, etc. You can already write
waitUntil {done.a && done.b}
but a direct notification is preferable.
In order to support complex orchestrations, it would be desirable for notify to work across builds of a single flow, and across distinct flows in the system (assuming there is some way of communicating current state). It would even be useful to be able to support cross-master notifications, which is where this use case blends into the first.
Project:
Jenkins
Labels:
parallel
Priority:
Major
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] [compress-artifacts-plugin] (JENKINS-27042) java.util.zip.ZipException thrown when reading artifacts from archive larger than 4G
Oliver Gondža commented on JENKINS-27042 java.util.zip.ZipException thrown when reading artifacts from archive larger than 4G Fixed in https://github.com/jenkinsci/compress-artifacts-plugin/pull/5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be
Daniel Beck updated JENKINS-27126 New Scroll bar in Jenkins Build history is showing when shouldn't be Change By: Daniel Beck (25/Feb/15 3:49 PM) Labels: user-experience Assignee: Tom FENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be
Daniel Beck commented on JENKINS-27126 New Scroll bar in Jenkins Build history is showing when shouldn't be What web browser is this? What is the description used, if any? Any custom JS/CSS running for Jenkins (e.g. Simple Theme Plugin, Greasemonkey)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be
Lorelei McCollum commented on JENKINS-27126 New Scroll bar in Jenkins Build history is showing when shouldn't be Chrome 40 no description is set no custom JS or CSS running, none of those themes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27093) Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1
Kanstantsin Shautsou edited a comment on JENKINS-27093 Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1 Hi, Paul, could you provide two consecutive build.xml files (you can cut any private info) that were triggered and the result of manual run for git command from polling log? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-27128) Compress Build Log Plugin: Logs of Multi-configuration jobs are not compressed
Valentin David created JENKINS-27128 Compress Build Log Plugin: Logs of Multi-configuration jobs are not compressed Issue Type: Bug Assignee: Daniel Beck Components: other Created: 25/Feb/15 4:14 PM Description: After enabling the plugin, and enabling compression in the multi-configuration job, new build of jobs get only the main log file compressed on the filesystem. Logs for each combination are left uncompressed on the filesystem. Tested with version 1.0 of the plugin with Jenkins 1.599 on Debian Jessie. Note: component compress-buildlog-plugin is not available, so it is filed under other. Project: Jenkins Priority: Minor Reporter: Valentin David This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27129) More consistent use of PauseAction
Jesse Glick created JENKINS-27129 More consistent use of PauseAction Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 25/Feb/15 4:24 PM Description: Currently PauseAction is added only by InputStep. But it makes sense to add also for SleepStep (JENKINS-26120) and WaitForConditionStep (JENKINS-25570), as well as for the proposed wait step (JENKINS-27127). This would allow visualizations to give a better picture of which flow builds and branches were active at a given time, compute running time more accurately, etc. Project: Jenkins Priority: Minor 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] [git-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1
Paul Sokolovsky commented on JENKINS-27093 Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1 Thanks for the replies and commits already made. So, our situation is that we have pretty busy production Jenkins system, so there's only limited experimentation can be done there, and in limited time I had to look into this issue, I traced it just to the source line in the original description above. This is also 1st time I looked into SCM polling, so I don't know how related data is stored and other details. But job we had issues to is actually public: https://ci.linaro.org/job/trigger-linux-ltsi/ . As you can see (note: builds in question may expire in a week or two), from build #132 Feb 23, 2015 11:33:10 AM to build #161 Feb 23, 2015 1:58:09 PM , build triggered every 5 mins, which is SCM polling period for that job. But typical poll log looks like: https://ci.linaro.org/job/trigger-linux-ltsi/160/pollingLog/ (content quoted above in the original description). Kanstantsin: The repo is public, running git command from poll log, I get the expected output (I also thought that maybe there's stray space or something gets parsed, but I confirmed it all looks ok). Will try to look up those build.xml's as a next step. $ /usr/bin/git -c core.askpass=true ls-remote -h git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git 8e63197ffe7750c94c8ea9d159ce3e46a76bfcf2 refs/heads/linux-2.6.11.y d04a37911968d919fa842ad40fa9e9ff1dd10904 refs/heads/linux-2.6.12.y 816e9c6c226227c4862b2067aace0f450cc92635 refs/heads/linux-2.6.13.y 789f444285aedfb04af7aa3748aa52e99ac4bd8f refs/heads/linux-2.6.14.y f70602f4f6248735a02c61a1323c9151a33a3775 refs/heads/linux-2.6.15.y 6b0daf99dd2392b024bdca05530e4e761bc3cdae refs/heads/linux-2.6.16.y 78ace17e51d4968ed2355e8f708d233d1cc37f6d refs/heads/linux-2.6.17.y 299a2479bca6211f845158761920ec480f35a229 refs/heads/linux-2.6.18.y 09780ab3b26507776671900e0ed7920f297498ed refs/heads/linux-2.6.19.y f3815da6b4fd508cc3574399248e2e15cb8a617f refs/heads/linux-2.6.20.y a31a9035702124423c3aa5aa848937f165753a4f refs/heads/linux-2.6.21.y 37579d1574f6c18f1f648201c6b0850ac94094cd refs/heads/linux-2.6.22.y 6531868a73a6c91bf0e3e60ded7d1440ee24dfa8 refs/heads/linux-2.6.23.y 928bb8c418b5f9e96dbccc8d7eafb6635ae81548 refs/heads/linux-2.6.24.y 00935daeb04cd54a67b66c9e3babc23389251a98 refs/heads/linux-2.6.25.y 63e0e67b17dc233f93f709610971bbfadc97f75e refs/heads/linux-2.6.26.y bc4e1a77b06519a01e7aed1125695598e27ddeb2 refs/heads/linux-2.6.27.y 5861c853a3f529b9c6a338dd7c4a7afec397ea7a refs/heads/linux-2.6.28.y 12010107aaf417503b7e413d84f2554080aebfe2 refs/heads/linux-2.6.29.y 0d0675cf44c85bd3c0d891845aa02f9249cd7c68 refs/heads/linux-2.6.30.y a389e98d2c6e1900f035befe215f541436bcb0b2 refs/heads/linux-2.6.31.y 3bd0d1ad14c3566107e391732e4df658b005ad67 refs/heads/linux-2.6.32.y 86a705267a2a502a3d62ef0797e449677b25835f refs/heads/linux-2.6.33.y 5878e067ecac4bd2320e933ec485c01190a5b881 refs/heads/linux-2.6.34.y 675f7660ffb0e1880011f6b3c4f9ac241491e3cd refs/heads/linux-2.6.35.y 69ad303ab8321656d6144d13b2444a5595bb6581 refs/heads/linux-2.6.36.y e396c9d8699c95d52b2abcc2d4d5f9616e839734 refs/heads/linux-2.6.37.y 4b7a6d2528bfb625cc359d89ac16439b0ec744ea refs/heads/linux-2.6.38.y ea0dc0dc1c1dca25e50384e300a528db57ee7de5 refs/heads/linux-2.6.39.y 5dba9ddd98cbc7ad319d687887981a0ea0062c75 refs/heads/linux-3.0.y 9bb1282f6a7754955c18be912fbc2b55d133f1b9 refs/heads/linux-3.1.y 5cfc71ce138e79ceb6250f78137dd05ba52e9d34 refs/heads/linux-3.10.y 5ee54f38171b9b3541c5e9cf9c3a9e53455fd8b4 refs/heads/linux-3.11.y 22ccf8f1a5450ac5a6bc2bb519699838017ce1ea refs/heads/linux-3.12.y 2d20120bba8475c963a8d28dd0ffa13637fa3ad7 refs/heads/linux-3.13.y a74f1d1204a5c892466b52ac68ee6443c1e459d7 refs/heads/linux-3.14.y f35b5e46feabab668a44df5b33f3558629f94dfc refs/heads/linux-3.15.y d0335e4feea0d3f7a8af3116c5dc166239da7521 refs/heads/linux-3.16.y bc15d4627aa8f562a1c5ec9d84076b8db25bab31 refs/heads/linux-3.17.y a17f9bf1f7cd3412b9920577a7c0ec34cb81b233 refs/heads/linux-3.18.y bfa76d49576599a4b9f9b7a71f23d73d6dcff735 refs/heads/linux-3.19.y fd623507bdcee1f7a387ae86adb7a66b431dd056 refs/heads/linux-3.2.y 845720650c557a75262b629b0bc228fffcf64638 refs/heads/linux-3.3.y 28895317f9a7d726cd13fc9b5447cb5dcb5cd22c refs/heads/linux-3.4.y f2b152564afdf9c9917c17d1c41c1082c82067bd refs/heads/linux-3.5.y b2824f4e0990716407b0c0e7acee75bb6353febf refs/heads/linux-3.6.y 356d8c6fb2a7cf49e836742738a8b9a47e77cfea refs/heads/linux-3.7.
[JIRA] [ec2-plugin] (JENKINS-26716) Jobs throttled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary
Trevor Baker updated JENKINS-26716 Jobs throttled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary Change By: Trevor Baker (25/Feb/15 4:54 PM) Description: When concurrent jobs are throttled across categories new ec2 provisioned slaves are not launched when they are required. The ec2 plugin should not detect that even though there may be executors available that they can not run the job(s) due to concurrent throttling. These two plugins should interop as expected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27093) Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1
Paul Sokolovsky updated JENKINS-27093 Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1 build.xml's from builds #159, #160 of the job above are attached. Change By: Paul Sokolovsky (25/Feb/15 5:10 PM) Attachment: 159-build.xml Attachment: 160-build.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-26245) Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing
Jussi Malinen commented on JENKINS-26245 Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing Hi! Typically during development you would use: mvn hpi:run that start a local standalone jenkins with the latest plugin in use. The jobs that you create there are not removed when you run mvn clean, so you can keep on using the jobs you created once. I think it would be easiest to work like that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-26245) Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing
Jussi Malinen commented on JENKINS-26245 Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing And that bug about stapler you run into, I have found it earlier and am cleaning up my fix for commit right now. It should not show up if you use mvn hpi:run. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated
Marcelo Behera assigned JENKINS-11176 to Marcelo Behera Promotion criteria "If the build is a release build" is broken and displays duplicated Change By: Marcelo Behera (25/Feb/15 5:21 PM) Assignee: Marcelo Behera This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep-plugin] (JENKINS-24242) On evaluation failure is not being honored
Jason Tsai commented on JENKINS-24242 On evaluation failure is not being honored is it possible for me to mark the status as "ABORTED" or "SKIPPED" (show a grey ball in status) instead of the default "SUCCESS"? (blue ball) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated
Marcelo Behera started work on JENKINS-11176 Promotion criteria "If the build is a release build" is broken and displays duplicated Change By: Marcelo Behera (25/Feb/15 5:22 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] [robot-plugin] (JENKINS-26245) Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing
Jussi Malinen edited a comment on JENKINS-26245 Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing Hi! Typically during development you would use: mvn hpi:run that starts a local standalone jenkins with the current development code for robot plugin in use. The jobs that you create there are not removed when you run mvn clean, so you can keep on using the jobs you created once. I think it would be easiest to work like that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-23209) Provide a way to provide all warning that occurred in a test case
Jussi Malinen commented on JENKINS-23209 Provide a way to provide all warning that occurred in a test case Hi! There doesnt seem to be too much interesting in implementing this and no one at Nokia has requested this (our sponsor). But if you would like to make a pull request, we could then include this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-24281) Add option to move files during test result publishing
Jussi Malinen commented on JENKINS-24281 Add option to move files during test result publishing Could you elaborate why the copy is not enough? Wouldnt the files that are copied get removed later anyway? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-26980) Enable configuration of "Robot Results" column in the default job list view
Jussi Malinen commented on JENKINS-26980 Enable configuration of "Robot Results" column in the default job list view Cheers, the pull request looks good. I think it is better to keep it by default, so that we dont change the behaviour for all the current users. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated
Marcelo Behera
resolved JENKINS-11176 as Fixed
Promotion criteria "If the build is a release build" is broken and displays duplicated
No método registerExtension(), da classe ReleasePromotionCondition, coloquei um teste se a instância da classe DescriptorImpl já havia sido adicionada na lista, não permitindo a duplicação do objeto condição. Mudei também o tipo de retorno do método newInstance() de PromotionCondition para ReleasePromotionCondition na classe DescriptorImpl.
public static void registerExtension() {
DescriptorExtensionList listPromotionCondition = PromotionCondition.all();
if(!listPromotionCondition.contains(DescriptorImpl.class)){
PromotionCondition.all().add(new DescriptorImpl());
}
}
public ReleasePromotionCondition newInstance(StaplerRequest req, JSONObject formData) throws FormException {
return new ReleasePromotionCondition();
}
Change By:
Marcelo Behera
(25/Feb/15 5:31 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] [robot-plugin] (JENKINS-22603) Add support Dashboard View
Jussi Malinen commented on JENKINS-22603 Add support Dashboard View I havent used the dashboard view myself... Unless someone from Nokia requests this, I dont think we will have time to do this in near future. We are happy about all pull requests 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] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated
Marcelo Behera
edited a comment on JENKINS-11176
Promotion criteria "If the build is a release build" is broken and displays duplicated
In registerExtension ( ) method , the ReleasePromotionCondition class, put a test whether the instance of DescriptorImpl class had already been added to the list , preventing duplication of the object condition. Also changed the return type of the newInstance() method of PromotionCondition to ReleasePromotionCondition in DescriptorImpl class.
public static void registerExtension() {
DescriptorExtensionList listPromotionCondition = PromotionCondition.all();
if(!listPromotionCondition.contains(DescriptorImpl.class)){
PromotionCondition.all().add(new DescriptorImpl());
}
}
public ReleasePromotionCondition newInstance(StaplerRequest req, JSONObject formData) throws FormException {
return new ReleasePromotionCondition();
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated
Marcelo Behera
edited a comment on JENKINS-11176
Promotion criteria "If the build is a release build" is broken and displays duplicated
In registerExtension ( ) method , the ReleasePromotionCondition class, put a test whether the instance of DescriptorImpl class had already been added to the list , preventing duplication of the object condition. Also changed the return type of the newInstance () method of PromotionCondition to ReleasePromotionCondition in DescriptorImpl class.
public static void registerExtension() {
DescriptorExtensionList listPromotionCondition = PromotionCondition.all();
if(!listPromotionCondition.contains(DescriptorImpl.class)){
PromotionCondition.all().add(new DescriptorImpl());
}
}
public ReleasePromotionCondition newInstance(StaplerRequest req, JSONObject formData) throws FormException {
return new ReleasePromotionCondition();
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated
Marcelo Behera closed JENKINS-11176 as Fixed Promotion criteria "If the build is a release build" is broken and displays duplicated Change By: Marcelo Behera (25/Feb/15 5:34 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-23077) robotframework plugin throws exception on missing output-dir when the build fails
Jussi Malinen commented on JENKINS-23077 robotframework plugin throws exception on missing output-dir when the build fails Couldnt you do this so, that you would have robot tests a job that is executed automatically after your build job, if that passes? And so if the build fails, the robot job is never executed? Am I missing something important? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-19024) Ability to set thresholds with test number in addition to percentage
Jussi Malinen commented on JENKINS-19024 Ability to set thresholds with test number in addition to percentage this has been open for a long time... Is someone still missing this feature currently? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [timestamper-plugin] (JENKINS-27054) Radio buttons would be easier to click if associated text was part of a
Paul Fee commented on JENKINS-27054 Radio buttons would be easier to click if associated text was part of a I got the 1.5.16 update via the Manage Plugins page and confirmed that the enhancement worked as expected. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-20465) output.xml with date-timestamp not found
Jussi Malinen commented on JENKINS-20465 output.xml with date-timestamp not found Using filename output*.xml seems to work for me. I assume this is not a problem anymore? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [token-macro-plugin] (JENKINS-27130) Failed to load jobs after upgrading Jenkins
Zuhao Chen created JENKINS-27130 Failed to load jobs after upgrading Jenkins Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: token-macro-plugin Created: 25/Feb/15 6:17 PM Description: After I upgrade to the latest Jenkins and all plugins to latest version. I see bunch of there exception in logs. SEVERE: Failed Loading job VXOA_Test_PyUnit_6.2 java.lang.NoClassDefFoundError: org/jenkinsci/plugins/tokenmacro/DataBoundTokenMacro at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:756) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at hudson.plugins.emailext.EmailExtTemplateActionFactory.createFor(EmailExtTemplateActionFactory.java:35) at hudson.model.AbstractProject.createTransientActions(AbstractProject.java:749) at hudson.model.Project.createTransientActions(Project.java:235) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:739) at hudson.model.AbstractProject.onLoad(AbstractProject.java:332) at hudson.model.Project.onLoad(Project.java:95) at hudson.model.Items.load(Items.java:279) at jenkins.model.Jenkins$18.run(Jenkins.java:2655) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:885) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.lang.ClassNotFoundException: org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1375) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) ... 25 more Feb 24, 2015 3:22:46 PM jenkins.InitReactorRunner$1 onTaskFailed Project: Jenkins Priority: Major Reporter: Zuhao Chen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27131) Possibility to get used logfile and line number of warning in logfile
nif y
created JENKINS-27131
Possibility to get used logfile and line number of warning in logfile
Issue Type:
Improvement
Assignee:
Ulli Hafner
Components:
warnings-plugin
Created:
25/Feb/15 6:46 PM
Description:
To due the fact that some log-files consists of warnings but neither information about source code file nor information about line number, it would be helpful to link to the log-file and the line number of the warning in the log-file instead.
e.g. @ groovy-script
...
String fileName = {selected log-file currently parsed}
String lineNumber = {lineNumber in log-file currently analyzed}
...
return new Warning(fileName, Integer.parseInt(lineNumber), "Dynamic Parser", "xyz Warning", message);
To work around the problem if the parser is analyzing stdout instead of a log-file, either stdout could be linked (if possible) or the problem should be handled in the groovy-script.
Project:
Jenkins
Priority:
Minor
Reporter:
nif y
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [configure-job-column-plugin] (JENKINS-16744) crash when loading job configuration page
Jay Burrill commented on JENKINS-16744 crash when loading job configuration page I am seeing this error under a new installation of Jenkins on RHEL 6.3. Is there a known solution? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-16536) PermGen leak
Jay Burrill commented on JENKINS-16536 PermGen leak I am seeing this in a new installation of Jenkins 1.599 on RHEL 6.3: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.599.jar!/jenkins/model/Jenkins/configure.jelly:59:84: java.lang.OutOfMemoryError: PermGen space at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) 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.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:46) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) 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 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.serv
