[JIRA] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Kanstantsin Shautsou commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Feel free to check. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-27643) Job Config History is not saved when perfoming config changes
Dominik Kaspar created JENKINS-27643 Job Config History is not saved when perfoming config changes Issue Type: Bug Assignee: Mirko Friedenhagen Components: jobconfighistory-plugin Created: 27/Mar/15 7:33 AM Description: We are using the JobConfigHistory plugin (2.6) and have recently realized that no config changes have been saved to disk for many weeks. When clicking on the "Job Config History" link of a job, a list of changes appears, but the newest one is very old. We therefore upgraded to version 2.10, but that did not really help: now the history seems to be working but is only available on the main page (global history of all changes) the new problem is that there are no more "Job Config History" links in the jobs, so it's hard to navigate to the interesting changes. When moving back to 2.6: the links appear again in the jobs some recent changes (done while 2.10 was installed) appear! but the problem is again that new configuration changes are not stored (only old content and changes performed while 2.10 was installed) Are these known issues? We still use Jenkins 1.532.3, could that be the problem? Project: Jenkins Priority: Minor Reporter: Dominik Kaspar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-20263) Artifact Resolver does not retrieve the latest version from central Maven Repository
Robert Kleinschmager commented on JENKINS-20263 Artifact Resolver does not retrieve the latest version from central Maven Repository still there in version 1.11 maybe it's also related to the own local repo (store at /tmp/repositoryconnector-repo/ by default) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-20263) Artifact Resolver does not retrieve the latest version from central Maven Repository
Robert Kleinschmager edited a comment on JENKINS-20263 Artifact Resolver does not retrieve the latest version from central Maven Repository still there in version 1.1.1 maybe it's also related to the own local repo (store at /tmp/repositoryconnector-repo/ by default) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Daniel Beck commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Kanstantsin Shautsou You resolved this despite a report it's not actually fixed, not me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Kanstantsin Shautsou commented on JENKINS-25127 Hook uninstalled if job is in a subfolder I tired from your spam comments. Commit was done with fix but has no FIXED prefix to automatically close issue. If issue persist, then requester will reopen. If you want handle this issue and plugin maintaining then go! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27620) SCM polling broken for servers with variable in path
Derk-Jan Hartman commented on JENKINS-27620 SCM polling broken for servers with variable in path This is highly likely yes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-27591) Improve performance of initial scan by narrowing the job config pattern
Jonas Kåveby commented on JENKINS-27591 Improve performance of initial scan by narrowing the job config pattern Okay, disabling strategies one by one makes more sense, my misunderstanding. the SCM Sync status footer I was wrong, this doesn't seem to be affected (I was sloppy reading footer.jelly yesterday). detailed commit messages Since the job strategy would be disabled and the manual strategy used instead, the commit messages would be Modification on configuration(s) / Item renamed / File hierarchy deleted instead of Job XYZ configuration updated / Job XYZ hierarchy renamed from ABC to DEF / Job XYZ hierarchy deleted. It makes it less clear what's been changed when skimming the changes in an scm browser, but it's not a blocker. the ability to customize commit messages The decorateOnsubmitForm logic in footer.jelly is only shown if the current page matches a PageMatcher from a strategy. If the job strategy is disabled and the manual strategy used instead, I assume there will be no PageMatcher matching URIs like view/All/job/myjob/configure, so the user won't be given an opportunity to provide a custom commit message when configuring jobs. Not a big issue. So, the tradeoff would be improved performance against less clarity in the SCM history. I think it's an acceptable tradeoff, but the best would be if I could keep both of course. By the way, I found a bug in the PageMatcher regexp in JobConfigScmSyncStrategy. I'll post a separate JIRA issue for 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] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Christopher Orr
commented on JENKINS-25127
Hook uninstalled if job is in a subfolder
Leandro Lucarella: Just a quick comment; I haven't tested this code, but you should be able to use the Jenkins Script Console to re-save all affected jobs. Saving the job config should cause the hook to be created on GitHub:
for (job in Jenkins.instance.getAllItems(AbstractProject.class)) {
if (job.getTrigger(GitHubPushTrigger.class) != null) {
println("Saving " + job);
job.save();
}
}
You'll probably have to add some "import" statements at the top for the relevant classes.
Or if you want test it first on individual jobs, you can get a single job like this: Jenkins.instance.getItem('job-name-goes-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] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Daniel Beck commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Kanstantsin Shautsou cleared up my confusion on IRC: The hooks that have been removed are gone. You need to reconfigure them in Jenkins to have them re-register. At least with the fix, they should not be getting removed again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Kanstantsin Shautsou commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Plugin may provide some helper method that should re-calculated hooks, but i have no time for checking. Such method may be triggered from script console or even from button in global page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27644) Ability to show server-driven Jenkins project notifications in the UI
Christopher Orr
created JENKINS-27644
Ability to show server-driven Jenkins project notifications in the UI
Issue Type:
New Feature
Assignee:
Unassigned
Components:
core
Created:
27/Mar/15 8:48 AM
Description:
Background
Regardless of whether the ongoing Java version upgrade debate settles on Java 7 or Java 8, we should do as much as possible to advise users (as long as possible) in advance of the upcoming Java upgrade requirement.
Yes, people should ideally have a test environment and test every single Jenkins upgrade, so it's "their fault" if an upgrade goes bad, but we also have a diverse and large (100K!) userbase, plus a shiny "Upgrade automatically" button in the UI. So there will likely be a substantial number of people who will hit the button and complain loudly when Jenkins does not come up again due to an outdated JDK. There will also be people who upgrade automatically via a package manager (i.e. might not check the changelog on the website), or by downloading the WAR from the home page (but may not click through to the changelog).
Feature request
So, it would be nice if there was a way to notify users directly within the Jenkins UI.
We already show warnings on the Manage Jenkins page, based on the current state of the installation (e.g. outdated config files, broken reverse proxy, encryption re-key required).
But it would be nice to have messages that we can add (and remove) dynamically. For a Java upgrade warning, or for security advisories, for example.
This could be implemented by editing a JSON file that lives on updates.jenkins-ci.org (i.e. probably held in git and deployed by J-o-J) and gets fetched regularly by Jenkins, or by (somehow) adding another JSON object to the update-center.json.
It should be possible to make messages time-limited ("display until end of 2015-03-31"), and version-limited ("display if version >= 1.599 && version <= 1.606"). Optional extras could include a Java version restriction ("only show if JRE < 8"), a platform check ("only show on Windows"), or perhaps installation source ("only show for .rpm users" (not sure we can figure that out)). The Java check would be the most useful one just now.
Messages should be shown at the top on the Manage Jenkins page. It may be a nice addition if there was a "message type" field that allowed more urgent messages to be shown at the top of each page (similar to how "Jenkins is about to shut down" appears), though those should be dismissable (e.g. by storing a flag in a cookie).
Messages should probably be visible only to people with Jenkins#ADMINISTER permission. Or to everybody, if there is no authentication enabled (i.e. small installations, where it's probably fine to show this to all users).
So, as mentioned, I think this would be very useful for the Java upgrade scenario (i.e. show the message " Notice: Jenkins will soon require a modern Java version: see http://xxx." if "version < 1.XXX").
But this would also be generically useful in the future, e.g. for security advisories (e.g. the really urgent ones this week), or for time-limited messages that should not be hardcoded into the WAR file and should preferably not require an upgrade to remove them (e.g. the "Jenkins 100K" sidebar link, the "1.387" background change etc.).
Project:
Jenkins
Priority:
Major
Reporter:
Christopher Orr
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You
[JIRA] [scm-sync-configuration-plugin] (JENKINS-27591) Improve performance of initial scan by narrowing the job config pattern
Frédéric Camblor commented on JENKINS-27591 Improve performance of initial scan by narrowing the job config pattern Agree with your assumptions, you're right This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27644) Ability to show server-driven Jenkins project notifications in the UI
Christopher Orr
updated JENKINS-27644
Ability to show server-driven Jenkins project notifications in the UI
Change By:
Christopher Orr
(27/Mar/15 8:49 AM)
Description:
h4. BackgroundRegardless of whether the ongoing Java version upgrade debate settles on Java 7 or Java 8, we should do as much as possible to advise users (as long as possible) in advance of the upcoming Java upgrade requirement.Yes, people should ideally have a test environment and test every single Jenkins upgrade, so it's "their fault" if an upgrade goes bad, but we also have a diverse and large (100K!) userbase, plus a shiny "Upgrade automatically" button in the UI. So there will likely be a substantial number of people who will hit the button and complain loudly when Jenkins does not come up again due to an outdated JDK. There will also be people who upgrade automatically via a package manager (i.e. might not check the changelog on the website), or by downloading the WAR from the home page (but may not click through to the changelog).h4. Feature requestSo, it would be nice if there was a way to notify users directly within the Jenkins UI.We already show warnings on the Manage Jenkins page, based on the current state of the installation (e.g. outdated config files, broken reverse proxy, encryption re-key required).But it would be nice to have messages that we can add (and remove) dynamically. For a Java upgrade warning, or for security advisories, for example.This could be implemented by editing a JSON file that lives on updates.jenkins-ci.org (i.e. probably held in git and deployed by J-o-J) and gets fetched regularly by Jenkins, or by (somehow) adding another JSON object to the {{update-center.json}}.It should be possible to make messages time-limited ("display until end of 2015-03-31"), and version-limited ("display if version >= 1.599 && version <= 1.606"). Optional extras could include a Java version restriction ("only show if JRE < 8"), a platform check ("only show on Windows"), or perhaps installation source ("only show for .rpm users" (not sure we can figure that out)). The Java check would be the most useful one just now.Messages should be shown at the top on the Manage Jenkins page. It may be a nice addition if there was a "message type" field that allowed more urgent messages to be shown at the top of each page (similar to how "Jenkins is about to shut down" appears), though those should be dismissable (e.g. by storing a flag in a cookie).Messages should probably be visible only to people with {{Jenkins#ADMINISTER}} permission. Or to everybody, if there is no authentication enabled (i.e. small installations, where it's probably fine to show this to all users).So, as mentioned, I think this would be very useful for the Java upgrade scenario
(
,
i.e. show the message "(!) Notice: Jenkins will soon require a modern Java version: see
)
.But this would also be generically useful in the future, e.g. for security advisories (
e.g.
like
the really urgent ones this week), or for time-limited messages that should not be hardcoded into the WAR file and should preferably not require an upgrade to remove them (e.g. the "Jenkins 100K" sidebar link, the "1.387" background change etc.).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-27635) Downstream build can start running before upstream build has completed
Oliver Gondža
updated JENKINS-27635
Downstream build can start running before upstream build has completed
Change By:
Oliver Gondža
(27/Mar/15 9:04 AM)
Description:
This is a problem in case downstream build refers to the build of a parent project by permalink such as {{LAST_SUCCESSFUL}} and expect it will match the exact build that triggered the downstream build. This is a reasonable expectation if downstream build is triggered for stable/successful builds only.I observed several downstream builds copied different versions of artifacts from upstream project. Due to a heavily contended queue it took ~2 minutes to schedule all downstream builds using {{hudson.tasks.BuildTrigger}}. And as the actual scheduling is done before upstream completes, several downstream builds was scheduled fast enough to observe old permalink value.The scheduling should take place *after* upstream build is done.
Btw, I was not able
EDIT: Nothing special needs
to
find any documentation for the assumption that
happen actually. This is what
upstream
and
is doing at the time single
downstream
build should not overlap
runs
in
time
unittest without any artificial slowdowns
.
{noformat}"Executor #1 for master : executing test0 #1" #35 prio=5 java.lang.Thread.State: RUNNABLE at java.net.URLStreamHandler.parseURL(URLStreamHandler.java:265) at sun.net.www.protocol.file.Handler.parseURL(Handler.java:67) at java.net.URL.(URL.java:614) - locked <0xb31a06e> (a java.util.jar.JarFile) at java.net.URL.(URL.java:482) at sun.misc.URLClassPath$FileLoader.getResource(URLClassPath.java:1058) at sun.misc.URLClassPath.getResource(URLClassPath.java:199) at java.net.URLClassLoader$1.run(URLClassLoader.java:358) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) - locked <0x671b9b7f> (a java.lang.Object) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2615) at java.lang.Class.getDeclaredMethod(Class.java:2007) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:165) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:149) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:86) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:99) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) - locked <0x457de3bb> (a java.lang.Object) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at com.thoughtworks.xstream.XStream.toXML(XStream.java:988) at hudson.XmlFile.write(XmlFile.java:178) at hudson.model.Run.save(Run.java:1898) at hudson.model.Run.execute(Run.java:1795) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:263) - locked <0x4bf22da1> (a java.lang.Object){noformat}
[JIRA] [core] (JENKINS-27635) Downstream build can start running before upstream build has completed
Oliver Gondža started work on JENKINS-27635 Downstream build can start running before upstream build has completed Change By: Oliver Gondža (27/Mar/15 9:18 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] [maven-plugin] (JENKINS-26391) getAssignedLabel in MavenModule is implemented with lazy loading
SCM/JIRA link daemon commented on JENKINS-26391 getAssignedLabel in MavenModule is implemented with lazy loading Code changed in jenkins User: christ66 Path: core/src/main/java/hudson/model/Label.java test/src/test/java/hudson/model/NodeTest.java http://jenkins-ci.org/commit/jenkins/7a2dc32cc3b309a4391ada820732a550d9d4badc Log: JENKINS-26391 Prevent lazy loading operation when obtaining label information. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-27614) Can't execute Jenkins' self-installed Groovy on Windows 2012 slave
Dirk Heinrichs commented on JENKINS-27614 Can't execute Jenkins' self-installed Groovy on Windows 2012 slave Yes, that's the strange thing, I could run it from a cmd window. However, seems to be a problem in Windows Server 2012, we've also seen these permission problems elsewhere. Recursively assigning "full control" for $JENKINS_HOME to the user running the slave solved the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-27614) Can't execute Jenkins' self-installed Groovy on Windows 2012 slave
vjuranek closed JENKINS-27614 as Not A Defect Can't execute Jenkins' self-installed Groovy on Windows 2012 slave thanks for info - closing. Please reopen if you find out that's actually a problem Groovy plugin. Thanks. Change By: vjuranek (27/Mar/15 9:44 AM) Status: Open Closed 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] [jenkins-tracker] (JENKINS-27645) High memory usage by Jenkins ver. 1.580.1 & slave error
NARAYAN PRADHAN created JENKINS-27645 High memory usage by Jenkins ver. 1.580.1 & slave error Issue Type: Bug Assignee: Unassigned Components: jenkins-tracker Created: 27/Mar/15 9:48 AM Description: Hello, We are facing two issue with our Jenkins setups 1> Jenkins memory usage is very hight. We are running quite few jobs around 15-20 and observing heap memory usage increase gradually and reach upto 4 to 4.5 GB and. is this generic behavior or we have to upgrade to new version of Jenkins LTS. 2> we are facing below pasted error with downstream jobs --- FATAL: Remote call on Rhel6.3-2014-supbl603 failed java.io.IOException: Remote call on Rhel6.3-2014-supbl603 failed at hudson.remoting.Channel.call(Channel.java:760) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:941) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:556) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.ClassFormatError: Failed to load javax.servlet.ServletException at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:325) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:237) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at hudson.util.ProcessTree.getKillers(ProcessTree.java:151) at hudson.util.ProcessTree$OSProcess.killByKiller(ProcessTree.java:212) at hudson.util.ProcessTree$UnixProcess.kill(ProcessTree.java:557) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:564) at hudson.util.ProcessTree$Unix.killAll(ProcessTree.java:488) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:953) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:944) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) at ..remote call to Rhel6.3-2014-supbl603(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) ... 6 more Caused by: java.lang.UnsupportedClassVersionError: javax/servlet/ServletException : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.lang.ClassLoader.defineClass(ClassLoader.java:480) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:323) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:237) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at hudson.util.ProcessTree.getKillers(ProcessTree.java:151) at hudson.util.ProcessTree$OSProcess.killByKiller(ProcessTree.java:212) at hudson.util.ProcessTree$UnixProcess.kill(ProcessTree.java:557) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:564) at hudson.util.ProcessTree$Unix.killAll(ProcessTree.java:488) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:953) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:944) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecu
[JIRA] [websphere-deployer-plugin] (JENKINS-27646) Unable to connect to remote server
Marco Musolf created JENKINS-27646 Unable to connect to remote server Issue Type: Bug Assignee: Unassigned Attachments: Ping.jpg Components: websphere-deployer-plugin Created: 27/Mar/15 9:52 AM Description: I have tried to deploy an ear application to remote websphere but i am not able to ping the server within plugin configuration dialog. I have successfully deployed on a local server. This is what I did in order to configure remote server : 1. Copy DummyClientKeyFile.jks and DummyClientTrustFile.jks from remote server to jenkins server and configured those files within plugin dialog. 2. Import remote server certificates by using InstallCert program mentioned in plugin documentation by using hostname 9043 as parmeter. hostname is the remote server address and 9043 soap port of admin console 3. copying jssecacerts which contains both certificates from step 2. into JRE/lib/security where JRE is the java runtime environment jenkins is runnging under 4. restart jenkins server I am not able to ping the server always get a ssl exception : Any help will be appreciate Connection failed: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host XX at port 8879. at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:635) at com.ibm.websphere.management.AdminClientFactory.access$000(AdminClientFactory.java:127) at com.ibm.websphere.management.AdminClientFactory$1.run(AdminClientFactory.java:210) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63) at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:206) at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.connect(WebSphereDeploymentService.java:234) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin$DescriptorImpl.doTestConnection(WebSphereDeployerPlugin.java:334) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doF
[JIRA] [downstream-ext-plugin] (JENKINS-11455) Support Parameters for Downstream Projects
Julian Junghans commented on JENKINS-11455 Support Parameters for Downstream Projects Currently I am not able to find a way to stop triggering parameterized downstreams of rebuilding matrix subjobs via matrix-reloaded plugin. I hoped that the Downstream-Ext Plugin would support me there, but unfortunately it is not possible to set up parameters here. From my Point of View these plugins are related so closely that merging these would provide more benefits than doubling code to cover all possible use cases. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21618) wrong Load statistics: busy executors in minus
SCM/JIRA link daemon commented on JENKINS-21618 wrong Load statistics: busy executors in minus Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Label.java core/src/main/java/hudson/model/LoadStatistics.java core/src/main/java/hudson/model/OverallLoadStatistics.java core/src/main/java/hudson/slaves/NodeProvisioner.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/java/jenkins/model/UnlabeledLoadStatistics.java core/src/main/resources/hudson/model/Messages.properties core/src/test/java/hudson/model/LoadStatisticsTest.java http://jenkins-ci.org/commit/jenkins/6b8af39b0317bad90851d4f8025fd71fadb9deaa Log: [FIXED JENKINS-21618] Ensure that the LoadStatistics return a self-consistent result. The original method of computing load statistics would compute the total and idle counts independently which could lead to counting errors while jobs started in between the different state counting operations. This change switches to returning a `LoadStatisticsSnapshot` so that callers will get a single consistent view of the counts which was valid for at least one point in time during the collection of the snapshot. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21618) wrong Load statistics: busy executors in minus
SCM/JIRA link daemon resolved JENKINS-21618 as Fixed wrong Load statistics: busy executors in minus Change By: SCM/JIRA link daemon (27/Mar/15 10:17 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27563) Prevent Jenkins from blocking HTTP requests during start-up
SCM/JIRA link daemon commented on JENKINS-27563 Prevent Jenkins from blocking HTTP requests during start-up Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27565) Nodes can be removed as idle before the assigned tasks have started
SCM/JIRA link daemon commented on JENKINS-27565 Nodes can be removed as idle before the assigned tasks have started Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25938) Lock an Executor without creating a Thread
SCM/JIRA link daemon commented on JENKINS-25938 Lock an Executor without creating a Thread Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15355) AdjunctManager: exception upon startup
SCM/JIRA link daemon commented on JENKINS-15355 AdjunctManager: exception upon startup Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27564) Race condition when rendering the executors list
SCM/JIRA link daemon commented on JENKINS-27564 Race condition when rendering the executors list Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26391) getAssignedLabel in MavenModule is implemented with lazy loading
SCM/JIRA link daemon commented on JENKINS-26391 getAssignedLabel in MavenModule is implemented with lazy loading Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27566) Excessive locking on the Queue when rendering the Jenkins UI
SCM/JIRA link daemon commented on JENKINS-27566 Excessive locking on the Queue when rendering the Jenkins UI Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-27476) Plugin casue deadlock on Jenkins LTS 1.596.1
SCM/JIRA link daemon commented on JENKINS-27476 Plugin casue deadlock on Jenkins LTS 1.596.1 Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22941) Way to mark an Executable that should not block isReadyToRestart
SCM/JIRA link daemon commented on JENKINS-22941 Way to mark an Executable that should not block isReadyToRestart Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26900) Hide flyweight master executor when ≥1 heavyweight executors running as subtasks
SCM/JIRA link daemon commented on JENKINS-26900 Hide flyweight master executor when ≥1 heavyweight executors running as subtasks Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-6167) JNLP slave should support a connection via HTTP proxy
SCM/JIRA link daemon commented on JENKINS-6167 JNLP slave should support a connection via HTTP proxy Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21618) wrong Load statistics: busy executors in minus
SCM/JIRA link daemon commented on JENKINS-21618 wrong Load statistics: busy executors in minus Code changed in jenkins User: Stephen Connolly Path: changelog.html http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a Log: Noting merges JENKINS-15355 JENKINS-21618 JENKINS-22941 JENKINS-25938 JENKINS-26391 JENKINS-26900 JENKINS-27476 JENKINS-27563 JENKINS-27564 JENKINS-27565 JENKINS-27566 Fixing link text for JENKINS-6167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-20039) TestLink plugin indicates test case as "not run" and TestLink is not updated with build status
Garden Dwarf commented on JENKINS-20039 TestLink plugin indicates test case as "not run" and TestLink is not updated with build status Hi, I received no help and the issue is still there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26391) getAssignedLabel in MavenModule is implemented with lazy loading
dogfood commented on JENKINS-26391 getAssignedLabel in MavenModule is implemented with lazy loading Integrated in jenkins_main_trunk #4040 JENKINS-26391 Prevent lazy loading operation when obtaining label information. (Revision 7a2dc32cc3b309a4391ada820732a550d9d4badc) Result = SUCCESS schristou88 : 7a2dc32cc3b309a4391ada820732a550d9d4badc Files : core/src/main/java/hudson/model/Label.java test/src/test/java/hudson/model/NodeTest.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-17156) If Updater fails to update due to missing permission, it crashes and never flushes the comment queue
Stephan Krull commented on JENKINS-17156 If Updater fails to update due to missing permission, it crashes and never flushes the comment queue see https://github.com/jenkinsci/jira-plugin/pull/50 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27635) Downstream build can start running before upstream build has completed
Oliver Gondža
updated JENKINS-27635
Downstream build can start running before upstream build has completed
Change By:
Oliver Gondža
(27/Mar/15 11:40 AM)
Description:
This is a problem in case downstream build refers to the build of a parent project by permalink such as {{LAST_SUCCESSFUL}} and expect it will match the exact build that triggered the downstream build. This is a reasonable expectation if downstream build is triggered for stable/successful builds only.I observed several downstream builds copied different versions of artifacts from upstream project. Due to a heavily contended queue it took ~2 minutes to schedule all downstream builds using {{hudson.tasks.BuildTrigger}}. And as the actual scheduling is done before upstream completes, several downstream builds was scheduled fast enough to observe old permalink value.
The scheduling should take place *after* upstream build is done.EDIT: Nothing special needs to happen actually. This is what upstream is doing at the time single downstream runs in unittest without any artificial slowdowns.{noformat}"Executor #1 for master : executing test0 #1" #35 prio=5 java.lang.Thread.State: RUNNABLE at java.net.URLStreamHandler.parseURL(URLStreamHandler.java:265) at sun.net.www.protocol.file.Handler.parseURL(Handler.java:67) at java.net.URL.(URL.java:614) - locked <0xb31a06e> (a java.util.jar.JarFile) at java.net.URL.(URL.java:482) at sun.misc.URLClassPath$FileLoader.getResource(URLClassPath.java:1058) at sun.misc.URLClassPath.getResource(URLClassPath.java:199) at java.net.URLClassLoader$1.run(URLClassLoader.java:358) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) - locked <0x671b9b7f> (a java.lang.Object) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2615) at java.lang.Class.getDeclaredMethod(Class.java:2007) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:165) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:149) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:86) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:99) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) - locked <0x457de3bb> (a java.lang.Object) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at com.thoughtworks.xstream.XStream.toXML(XStream.java:988) at hudson.XmlFile.write(XmlFile.java:178) at hudson.model.Run.save(Run.java:1898) at hudson.model.Run.execute(Run.java:1795) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:263) - locked <0x4bf22da1> (a java.lang.Object){noformat}
This message is automatically generated
[JIRA] [jira-plugin] (JENKINS-13500) Jira plugin post "integrated in" comment on every build
Stephan Krull commented on JENKINS-13500 Jira plugin post "integrated in" comment on every build This bug is considered in https://github.com/jenkinsci/jira-plugin/pull/50 and definitily a duplicate of JENKINS-17156 (hence should be 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] [core] (JENKINS-27635) Downstream build can start running before upstream build has completed
Oliver Gondža resolved JENKINS-27635 as Duplicate Downstream build can start running before upstream build has completed Closing as a duplicate of JENKINS-20989. Change By: Oliver Gondža (27/Mar/15 11:41 AM) Status: In Progress Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-binding-plugin] (JENKINS-27631) Do not even temporarily save secrets in Workflow build record
SCM/JIRA link daemon commented on JENKINS-27631 Do not even temporarily save secrets in Workflow build record Code changed in jenkins User: Jesse Glick Path: pom.xml src/test/java/org/jenkinsci/plugins/credentialsbinding/impl/BindingStepTest.java http://jenkins-ci.org/commit/credentials-binding-plugin/40af344b6444edac754d8da7eda0ac238190f6f3 Log: Merge pull request #5 from jglick/stronger-tests JENKINS-27631 Stronger tests Compare: https://github.com/jenkinsci/credentials-binding-plugin/compare/0baec040aa1b...40af344b6444 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-binding-plugin] (JENKINS-27631) Do not even temporarily save secrets in Workflow build record
SCM/JIRA link daemon commented on JENKINS-27631 Do not even temporarily save secrets in Workflow build record Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/credentialsbinding/impl/BindingStepTest.java http://jenkins-ci.org/commit/credentials-binding-plugin/16c180f4add799acc8d5f58b73e63dc285380ed9 Log: JENKINS-27631 But demonstrating that it is stored temporarily. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extreme-feedback-plugin] (JENKINS-27647) Transparent background with Extreme Feedback Panel Plugin
Florian Schindler created JENKINS-27647 Transparent background with Extreme Feedback Panel Plugin Issue Type: Bug Assignee: emanuelez Attachments: Jenkins_menu_visible.png Components: extreme-feedback-plugin Created: 27/Mar/15 12:01 PM Description: Using Extrem Feedback Panel (1.2.2 or 1.2.3) and jenkins.war 1.606 the background in the browser is transparent (see screenshot). I would expect that there is no transparent background, no menu entries visible, ... This is independent of the browser I used for testing. Using jenkins.war version 1.596 I don't have this issue and the screen looks OK. Environment: • Windows 7 64 bit. • jenkins.war 1.606 • eXtreme Feedback Panel 1.2.2 or 1.2.3 • Internet Explorere 11 • Firefox 36.0.4 • Google Chrome 41.0.2272.101 m (64-bit) Project: Jenkins Priority: Minor Reporter: Florian Schindler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27648) Introduce directory desposal service
Oliver Gondža
created JENKINS-27648
Introduce directory desposal service
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
27/Mar/15 12:03 PM
Description:
Jenkins discards directories that are not needed any longer all the time. Aside from the fact it is subject of different random failures (on windows, on NFS, etc.), it is also a time consuming operation.
Instead of deleting such files synchronously, I propose to create Jenkins-wide service where directories (as {{FilePath}}s) can be registered for latter disposal. The service will rename the directory so it will appear deleted immediately and delete the renamed one latter.
Similar approach is implemented in Workspace cleanup plugin though the solution leaks renamed directories in case the deletion fails.
Such service will track registered directories even after the deletion failed and retry as many times as necessary or possibly report to admin that there is a problem Jenkins itself cannot handle despite repeated attempts.
There are several areas that can benefit from this aside from Workspace cleanup. though, I am not sure if this behaviour should replace what `FilePath#deleteRecursive` currently does.
Project:
Jenkins
Priority:
Minor
Reporter:
Oliver Gondža
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-27648) Introduce directory desposal service
Oliver Gondža
updated JENKINS-27648
Introduce directory desposal service
Change By:
Oliver Gondža
(27/Mar/15 12:04 PM)
Description:
Jenkins discards directories that are not needed any longer all the time. Aside from the fact it is subject of different random failures (on windows, on NFS, etc.), it is also a time consuming operation.Instead of deleting such files synchronously, I propose to create Jenkins-wide service where directories
(as {{FilePath}}s)
can be registered for latter disposal. The service will rename the directory so it will appear deleted immediately and delete the renamed one latter.Similar approach is implemented in [Workspace cleanup plugin|https://issues.jenkins-ci.org/browse/JENKINS-20056] though the solution leaks renamed directories in case the deletion fails.Such service will track registered directories even after the deletion failed and retry as many times as necessary or possibly report to admin that there is a problem Jenkins itself cannot handle despite repeated attempts.There are several areas that can benefit from this aside from Workspace cleanup. though, I am not sure if this behaviour should replace what `FilePath#deleteRecursive` currently does.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [xfpanel-plugin] (JENKINS-26006) Can't change background color
Florian Schindler commented on JENKINS-26006 Can't change background color I can also confirm Alexander Wenzel's observation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27648) Introduce directory desposal service
Oliver Gondža
updated JENKINS-27648
Introduce directory desposal service
Change By:
Oliver Gondža
(27/Mar/15 12:05 PM)
Description:
Jenkins discards directories that are not needed any longer all the time. Aside from the fact it is subject of different random failures (on windows, on NFS, etc.), it is also a time consuming operation.Instead of deleting such files synchronously, I propose to create Jenkins-wide service where directories can be registered for latter disposal. The service will rename the directory so it will appear deleted immediately and delete the renamed one latter.Similar approach is implemented in [Workspace cleanup plugin|https://issues.jenkins-ci.org/browse/JENKINS-20056] though the solution leaks renamed directories in case the deletion fails.Such service will track registered directories even after the deletion failed and retry as many times as necessary or possibly report to admin that there is a problem Jenkins itself cannot handle despite repeated attempts.There are several areas that can benefit from this aside from Workspace cleanup. though, I am not sure if this behaviour should replace what
`
{{
FilePath#deleteRecursive
`
}}
currently does.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-27510) Support "Deploy artifacts to maven repository" for Maven jobs
Daniel Spilker resolved JENKINS-27510 as Fixed Support "Deploy artifacts to maven repository" for Maven jobs Will be released in 1.31. Change By: Daniel Spilker (27/Mar/15 12:15 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27512) Support icons for folders
Daniel Spilker resolved JENKINS-27512 as Won't Fix Support icons for folders That's part of a commercial plugin which I can't test, so it's not going to be included in the DSL. Change By: Daniel Spilker (27/Mar/15 12:15 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-27649) Custom commit message not possible when configuring jobs
Jonas Kåveby created JENKINS-27649 Custom commit message not possible when configuring jobs Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 27/Mar/15 12:14 PM Description: The commit comment form doesn't always appear when saving a job configuration. The fault seems to lie in the PageMatcher regexp. I've tested the current regexp against a couple of different URIs: "view/x//job/a/configure" Passed "view/x//job/a/job/b/configure" Passed "view/x//job/a/job/b/job/c/configure" Passed "/job/a/configure" Passed "/job/a/job/b/configure" Passed "/view/x//job/a/job/b/job/c/configure" Passed "view/x/job/a/job/b/configure" Failed! "/job/ab/job/b/configure" Failed! "view/x/job/a/configure" Failed! "/view/x/job/a/configure" Failed! "job/a/configure" Failed! "///view/x//job//a//job//b/job//c//configure" Failed! Some of the failed URIs are real-life examples of URIs where the commit comment form doesn't appear, others are more hypothetical. I can work around the problem by adding an extra slash to my URIs when I configure jobs. Instead of opening view/All/job/myjob/configure in my browser, I open view/All//job/myjob/configure. Environment: Jenkins 1.580.3, SCM Sync Configuration Plugin 0.0.8 Project: Jenkins Priority: Minor Reporter: Jonas Kåveby This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-27649) Custom commit message not possible when configuring jobs
Jonas Kåveby commented on JENKINS-27649 Custom commit message not possible when configuring jobs The following regexp matches all the example URIs: "^/*(.*view/+[^/]+/+)?(job/+[^/]+/+)+configure$" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-27591) Improve performance of initial scan by narrowing the job config pattern
Jonas Kåveby commented on JENKINS-27591 Improve performance of initial scan by narrowing the job config pattern I agree with you that JENKINS-19659 is the proper solution to the problem reported in this issue. Thank you for your time analysing this! I've written JENKINS-27649 to track the regexp bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-20989) PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
Oliver Gondža assigned JENKINS-20989 to Oliver Gondža PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered Change By: Oliver Gondža (27/Mar/15 12:31 PM) Assignee: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-20989) PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
Oliver Gondža commented on JENKINS-20989 PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered Giving this a try in https://github.com/jenkinsci/jenkins/pull/1628 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-8688) Clearcase polling doesn't work with Linux Master and Windows Slave
Xiaokun Hou commented on JENKINS-8688 Clearcase polling doesn't work with Linux Master and Windows Slave I tried commands in linux with command. No result returned. cleartool lsh -fmt "%Xn\n" -avobs If '-avobs' is not used, then it works. I'm afraid it's a clearcase 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] [testlink-plugin] (JENKINS-20039) TestLink plugin indicates test case as "not run" and TestLink is not updated with build status
Bruno P. Kinoshita commented on JENKINS-20039 TestLink plugin indicates test case as "not run" and TestLink is not updated with build status Sorry for not being able to help you now Garden. I'll keep busy for the next months due to my relocation, but should you have any pull request we can merge it and cut a new release. Cheers, Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27368) job-dsl folder should support using only a name argument
Daniel Spilker commented on JENKINS-27368 job-dsl folder should support using only a name argument Will be released in 1.31. https://github.com/jenkinsci/job-dsl-plugin/pull/425 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27368) job-dsl folder should support using only a name argument
Daniel Spilker started work on JENKINS-27368 job-dsl folder should support using only a name argument Change By: Daniel Spilker (27/Mar/15 1:06 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] [job-dsl-plugin] (JENKINS-27050) Parameterized seed job is automatically triggered after change
Daniel Spilker resolved JENKINS-27050 as Not A Defect Parameterized seed job is automatically triggered after change Change By: Daniel Spilker (27/Mar/15 1:09 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21618) wrong Load statistics: busy executors in minus
dogfood commented on JENKINS-21618 wrong Load statistics: busy executors in minus Integrated in jenkins_main_trunk #4044 Result = UNSTABLE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27492) Permission deprecation warning in authorization context
Daniel Spilker commented on JENKINS-27492 Permission deprecation warning in authorization context That's a problem with the Groovy closure resolve strategy (http://docs.groovy-lang.org/latest/html/gapi/groovy/lang/Closure.html#getResolveStrategy%28%29). The each method uses the default resolve strategy "owner first" (http://docs.groovy-lang.org/latest/html/gapi/groovy/lang/Closure.html#OWNER_FIRST) and thus picks the permission method from the freeStyleJob closure instead of the authorization closure. So avoiding each by using a for loop fixes the problem. The warnings will go away when the deprecated permission methods on the job level have been removed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-27650) Page loads slow with hundreds of throttled builds in queue
recampbell
created JENKINS-27650
Page loads slow with hundreds of throttled builds in queue
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
throttle-concurrent-builds-plugin
Created:
27/Mar/15 1:44 PM
Description:
When there are hundreds of throttled builds in the queue, page loads increase by an order of magnitude.
Steps to reproduce:
Run Jenkins 1.580.2 and latest throttle-concurrent-builds plugin
Create a matrix job with 200 combinations (attached)
In the same job, select "Throttle Concurrent Builds" with a maximum of 7 builds throttled as part of a category called 'semaphore'
Set number of executors on the 'master' queue to 200
Run the job. There should only be 7 builds running due to the throttling
Page load times will increase by an order of magnitude – I observed 10 seconds from {time curl http://localhost:8080/jenkins/ajaxBuildQueue}
If you remove the throttling in the job configuration, the page load times will be under 50 ms.
Environment:
Jenkins 1.580.2
Project:
Jenkins
Labels:
performance
Priority:
Critical
Reporter:
recampbell
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-27492) Permission deprecation warning in authorization context
Nicholas Russell commented on JENKINS-27492 Permission deprecation warning in authorization context Ok, sounds good. 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] [job-dsl-plugin] (JENKINS-27368) job-dsl folder should support using only a name argument
Daniel Spilker resolved JENKINS-27368 as Fixed job-dsl folder should support using only a name argument Change By: Daniel Spilker (27/Mar/15 1:57 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] [job-dsl-plugin] (JENKINS-27368) job-dsl folder should support using only a name argument
SCM/JIRA link daemon commented on JENKINS-27368 job-dsl folder should support using only a name argument Code changed in jenkins User: Daniel Spilker Path: docs/Job-DSL-Commands.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/DslFactory.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/JobParent.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/JobParentSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/d3e01323ae8bf0082e549a52853ed7ebb596416a Log: Merge pull request #425 from CoreMedia/JENKINS-27368 JENKINS-27368 made closure parameter optional for factory methods Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/59e48dbc83df...d3e01323ae8b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27467) Add an "On the side" mode similar to the OpenID plugin
Mike Chmielewski commented on JENKINS-27467 Add an "On the side" mode similar to the OpenID plugin I strongly agree with this. I have a large-ish user base on the built-in user database, some of whom are contractors without corporate accounts. Having the internal DB as a fallback would be ideal. Without this, I can't really use this plugin, which is too bad, because having to maintain separate user DBs and credentials is tedious from a user and admin perspective. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26761) WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart
Kenneth Baltrinic commented on JENKINS-26761 WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart @jglick, sorry I lost you with my comments and am not doing a good job of watching this thread. Here is the bottom line from what I can tell: As the stacktrace shows, the problem is that b.checkouts is null on line 419 (here). (Note this seem to have moved to around line 423 on master). I have identified two different build.xml files for the same job wherein for the one, when it hits this line, checkouts is non-null and for the other when it hits, checkouts is null. I am hoping that you can feed these two attached files into Jenkins' deserializer and figure out why the one is yielding a null checkout property when the other does not. As I recall the first file ...-build.xml is the one that yeilds the null value and ...-build-1.xml is the one that works as expected. Hope that helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-27650) Page loads slow with hundreds of throttled builds in queue
Oleg Nenashev commented on JENKINS-27650 Page loads slow with hundreds of throttled builds in queue Hi Ryan, This issue is being caused by the behavior of Queue cache in Jenkins core. See the discussion in JENKINS-20046 It's possible to somehow optimize the performance of the plugin (e.g. by internal caching), but in general I would recommend to improve the behavior of Queue caching for web interfaces. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26391) getAssignedLabel in MavenModule is implemented with lazy loading
SCM/JIRA link daemon commented on JENKINS-26391 getAssignedLabel in MavenModule is implemented with lazy loading Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Label.java http://jenkins-ci.org/commit/jenkins/98605d0afb441f7953875097953e626128d31825 Log: After JENKINS-26391 we need to compare labels based on matching names not instance identity This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27097) wrong timezone reported in changes
Vasili Kvockin commented on JENKINS-27097 wrong timezone reported in changes Thank you for the clarification. No, I see no need to retain 1.6 compatibility. It would probably help the users if the git-plugin page would mention the minimum required java version. It already mentions minimum requirements for dependencies and git runtime. Additionally, it would help developers if there would be some kind of check for minimum version. At least they wouldn't then ask the same question I did. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-20039) TestLink plugin indicates test case as "not run" and TestLink is not updated with build status
Garden Dwarf commented on JENKINS-20039 TestLink plugin indicates test case as "not run" and TestLink is not updated with build status Hi Bruno, I've stopped trying to find a solution. My comment was just to answer Nilam about the progress on the issue. Cheers, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22936) Move rename infrastructure from Job to AbstractItem
Jesse Glick commented on JENKINS-22936 Move rename infrastructure from Job to AbstractItem Nicolas De Loof also found a problem with Trigger.start. I am thinking that the current system should be abandoned and replaced with a _javascript_ prompt before the form is submitted. Once you POST the submission the change is final. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26761) WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart
Jesse Glick commented on JENKINS-26761 WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart Well I already knew that the problems involved the checkouts field being null. The question is how this happens, since both build.xml files contain a definition for this field. That is why I want to know if there is some way to reproduce the problem from scratch, so I can actually debug it. The only noteworthy difference I see between the two files is that JENKINS-26761-build-1.xml lacks a queueId. This field was added in 1.601, matching your comment that you upgraded to 1.602 at some point. Anyway it is unlikely that has any relationship. I can easily suppress the exception; the underlying bug would remain, and polling would not work on this job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27620) SCM polling broken for servers with variable in path
Daniel Beck commented on JENKINS-27620 SCM polling broken for servers with variable in path Should be trivial to determine based on the file modification date of JENKINS_HOME/plugins/subversion.hpi (or .jpi). Both current and previous Subversion plugin versions would be helpful. Also, anything interesting in the logs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27462) Adjust syntax of subviews of nestedView
Daniel Spilker commented on JENKINS-27462 Adjust syntax of subviews of nestedView Will be released in 1.31. https://github.com/jenkinsci/job-dsl-plugin/pull/426 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27462) Adjust syntax of subviews of nestedView
Daniel Spilker started work on JENKINS-27462 Adjust syntax of subviews of nestedView Change By: Daniel Spilker (27/Mar/15 2:56 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26582) ISE from RunMap.put after reloading config
Damion Alexander commented on JENKINS-26582 ISE from RunMap.put after reloading config I have been able to consistently reproduce the thread death with "Stash Webhook to Jenkins" (v2.6) triggering a Multi-Configuration job. Our installation is relatively new, and this is the first time we setup anything to do triggering of jobs. Log of session Mar 27, 2015 2:39:52 PM INFO hudson.plugins.git.GitStatus$JenkinsAbstractProjectListener onNotifyCommit Scheduling BUILD: Code Deploy to build commit 7410c63de6e0431ee7c831bfdc1f2ba909b00385 Mar 27, 2015 2:39:52 PM INFO hudson.plugins.git.GitStatus$JenkinsAbstractProjectListener onNotifyCommit Scheduling BUILD: Code Deploy » py27 to build commit 7410c63de6e0431ee7c831bfdc1f2ba909b00385 Mar 27, 2015 2:39:52 PM INFO hudson.plugins.git.GitStatus$JenkinsAbstractProjectListener onNotifyCommit PostCommitHooks are disabled on DEPLOY: code_deploy Mar 27, 2015 2:39:52 PM SEVERE hudson.model.Executor run Unexpected executor death java.lang.IllegalStateException: /var/lib/jenkins/jobs/build_code_deploy/configurations/axis-TOXENV/py27/builds/8 already existed; will not overwite with build_code_deploy/TOXENV=py27 #8 at hudson.model.RunMap.put(RunMap.java:187) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) at hudson.model.Executor.run(Executor.java:213) Mar 27, 2015 2:40:20 PM INFO hudson.model.Run execute build_code_deploy/TOXENV=py27 #9 main build action completed: SUCCESS Mar 27, 2015 2:40:21 PM INFO hudson.model.Run execute build_code_deploy #9 main build action completed: SUCCESS Mar 27, 2015 2:40:44 PM INFO hudson.model.Run execute deploy_code_deploy #11 main build action completed: SUCCESS Of interest Build #8 is the previous successful run, build #9 is the current run and succeeds in a different thread. Versions component version Jenkins 1.606 Stash 3.1.0 Stash Webhook to Jenkins 2.60 ShiningPanda plugin 0.21 Job Configuration Job Name: build_code_deploy SCM: git (ssh) Branches: */master Poll SCM: H 0 1 1 * Configuration Matrix: Tox; py27 Build: Tox Builder, $configuration_file=tox.ini, recreate (checked) Post-build: trigger job= deploy_code_deploy, Publish JUnit test result, Notify Stash Instance Stash Plugin: Configured to only build from Master This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-plugin] (JENKINS-27651) EventListener not reconfigured after job is renamed
Nicolas De Loof created JENKINS-27651 EventListener not reconfigured after job is renamed Issue Type: Bug Assignee: jyrkiput Components: gerrit-plugin Created: 27/Mar/15 3:04 PM Description: Triggers don't get stopped/started after job rename confirmation (two phase job configuration form submission), this result with listener being configured for old job name, and no listener for the new one. Project: Jenkins Priority: Minor Reporter: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-13765) PTC Integrity Plugin - Restore Timestamp Not Working
Patrick Merschmann reopened JENKINS-13765 PTC Integrity Plugin - Restore Timestamp Not Working Reopened like discussed within the emails. An official workaround would be great. Looking forward to see some solution. Change By: Patrick Merschmann (27/Mar/15 3:05 PM) Resolution: Won't Fix Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26582) ISE from RunMap.put after reloading config
Jesse Glick commented on JENKINS-26582 ISE from RunMap.put after reloading config Hmm, do not have Stash available, so I wonder if there is a way to reproduce without using proprietary tools. I would be tempted to ascribe this to yet another weird bug in the matrix-project plugin except that there are some reports from people using freestyle as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26582) ISE from RunMap.put after reloading config
Damion Alexander commented on JENKINS-26582 ISE from RunMap.put after reloading config The Stash Webhook plugin makes a GET request to the jenkins server. So one should just need Jenkins, the Git plugins (scm-api, git client plugin, git plugin), and something to serve git. GET /git/notifyCommit?url=""> This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26582) ISE from RunMap.put after reloading config
Greg BOUGEARD commented on JENKINS-26582 ISE from RunMap.put after reloading config Yep, we're using a freestyle project with a matrix configuration This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27652) Workflow support for Slack Notifications (Pre and Post build)
Pedro Algarvio created JENKINS-27652 Workflow support for Slack Notifications (Pre and Post build) Issue Type: New Feature Assignee: Jesse Glick Components: slack-plugin, workflow-plugin Created: 27/Mar/15 3:29 PM Description: Add Workflow support for Slack Notifications (Pre and Post build) Project: Jenkins Priority: Minor Reporter: Pedro Algarvio This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27462) Adjust syntax of subviews of nestedView
SCM/JIRA link daemon commented on JENKINS-27462 Adjust syntax of subviews of nestedView Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Migration.md docs/View-Reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/DslFactory.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/JobParent.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/ViewFactory.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/views/NestedViewsContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/views/NestedViewSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/60e887f5cbdb411e7f702abb51b0b78f647d8321 Log: Merge pull request #426 from CoreMedia/JENKINS-27462 JENKINS-27462 Adjust syntax of subviews of nestedView Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/ca84b389738f...60e887f5cbdb This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27462) Adjust syntax of subviews of nestedView
SCM/JIRA link daemon commented on JENKINS-27462 Adjust syntax of subviews of nestedView Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Migration.md docs/View-Reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/DslFactory.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/JobParent.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/ViewFactory.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/views/NestedViewsContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/views/NestedViewSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/03ebbe65a46bdacf4f636f0a5143fc5e7a301759 Log: Adjust syntax of subviews of nestedView, JENKINS-27462 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27462) Adjust syntax of subviews of nestedView
Daniel Spilker resolved JENKINS-27462 as Fixed Adjust syntax of subviews of nestedView Change By: Daniel Spilker (27/Mar/15 3: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] [slack-plugin] (JENKINS-27652) Workflow support for Slack Notifications (Pre and Post build)
SCM/JIRA link daemon commented on JENKINS-27652 Workflow support for Slack Notifications (Pre and Post build) Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/24f4496e9654c82dc596cb372da5e6eafa1b4d2f Log: JENKINS-27652 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-27652) Workflow support for Slack Notifications (Pre and Post build)
Jesse Glick updated JENKINS-27652 Workflow support for Slack Notifications (Pre and Post build) Change By: Jesse Glick (27/Mar/15 3:31 PM) Priority: Minor Major Labels: workflow 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] [mercurial-plugin] (JENKINS-27316) Exception thrown when using variable in Mercurial Repo URL
Kyle Leinen commented on JENKINS-27316 Exception thrown when using variable in Mercurial Repo URL We currently managed all of our feature branches through the usage of our Job DSL scripting (which we are peeking at the Workflow plugin set for a next revision of that). What our one-off jobs allow for is to have changesets built that don't exist on our central server. This allows for developers to get some CI system time on their changeset without having to create a specific branch and job for their feature. Just to give a view of scale here, if we had to create a branch build for every story we have in flight, we would have over 200 branch build for just one of our projects. Currently we restrict our branch builds to project teams, which still is around 30. Anyways, if being able to "hide" or disable this warning is difficult or not in the direction you want to take, no worries there. We have been thinking of writing a script that parses out and removes that warning from the logs via a cron script. That way it can still be generated but we can throw it away since it is noise for us, but maybe not for others. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder I tried the script but I get this error: groovy.lang.MissingPropertyException: No such property: GitHubPushTrigger for class: Script1 I don't know anything about groovy or java, that means I need an import? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Kanstantsin Shautsou commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Hi, you need import com.cloudbees.jenkins.GitHubPushTrigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-13765) PTC Integrity Plugin - Restore Timestamp Not Working
SCM/JIRA link daemon commented on JENKINS-13765 PTC Integrity Plugin - Restore Timestamp Not Working Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/IntegrityCMMember.java src/main/java/hudson/scm/IntegrityCheckoutTask.java http://jenkins-ci.org/commit/integrity-plugin/f57bae636f4f68594bf1ee9365e2b55980139315 Log: [FIXED JENKINS-13765] Resolving this issue as a workaround, since the si proejctco command ingnores the --retoreTimestamp 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] [integrity-plugin] (JENKINS-13765) PTC Integrity Plugin - Restore Timestamp Not Working
SCM/JIRA link daemon resolved JENKINS-13765 as Fixed PTC Integrity Plugin - Restore Timestamp Not Working Change By: SCM/JIRA link daemon (27/Mar/15 4:14 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Thanks a lot! The script have worked (I got the expected println() output) but no re-registration of hooks to GitHub happened :-/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26744) Support ALWAYS Continuation Condition in Multi-Phase Jobs
Christian Goetze commented on JENKINS-26744 Support ALWAYS Continuation Condition in Multi-Phase Jobs Falls Du mal nach San Francisco kommst, gibt es definitiv Bier! Vielen Dank This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-27316) Exception thrown when using variable in Mercurial Repo URL
Jesse Glick commented on JENKINS-27316 Exception thrown when using variable in Mercurial Repo URL we are peeking at the Workflow plugin set for a next revision of that Workflow is not a substitute for Job DSL. They are more or less orthogonal. changesets built that don't exist on our central server This is something that could be supported as a “branch source” in the Multi-Branch API, I think. (For example, the Git implementation has support for pull requests, which are hosted in a distinct repository.) Someone needs to write that branch source but I think it is a relatively minor exercise—the API does not require in-depth Jenkins plugin expertise. if we had to create a branch build That is the point of the Multi-Branch API: the creation of the subprojects (and their “garbage collection”) is automated. difficult or not in the direction you want to take No, this is a valid bug report, I was just offering tangential suggestions based on your use case. I am not promising to implement it (assuming you are not a CloudBees support customer), but a pull request would be welcome. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dockerhub-plugin] (JENKINS-27653) Credentials plugin support
Kohsuke Kawaguchi created JENKINS-27653 Credentials plugin support Issue Type: New Feature Assignee: Unassigned Components: dockerhub-plugin Created: 27/Mar/15 4:39 PM Description: For other plugins that interact with Docker Hub (including Docker Hub Enterprise), this plugin should provide the credentials implementations. To support multiple endpoints, the credential should also specify the API endpoint. This way a Jenkins administrator only needs to configure a credential once, then use it across all sorts of docker related plugins. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Kanstantsin Shautsou commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Leandro Lucarella, let's try to clarify: 1) is initial issue was fixed in new release? First user confirmed that it prevents hooks clean up This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
