[JIRA] [jclouds-plugin] (JENKINS-26083) Jenkins jcloud pluging fails to get and assign floating ip on openstack
Title: Message Title Marcus Klein commented on JENKINS-26083 Re: Jenkins jcloud pluging fails to get and assign floating ip on openstack The necessary request seems to be available in jclouds: org.jclouds.openstack.nova.v2_0.extensions.FloatingIPPoolApi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds-plugin] (JENKINS-26083) Jenkins jcloud pluging fails to get and assign floating ip on openstack
Title: Message Title Marcus Klein commented on JENKINS-26083 Re: Jenkins jcloud pluging fails to get and assign floating ip on openstack Same issue is described here for jclouds API: https://issues.apache.org/jira/browse/JCLOUDS-471 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds-plugin] (JENKINS-26083) Jenkins jcloud pluging fails to get and assign floating ip on openstack
Title: Message Title
Marcus Klein commented on JENKINS-26083
Re: Jenkins jcloud pluging fails to get and assign floating ip on openstack
I tried out the latest master. Assigning floating IPs to node works now as expected. But another problem appears now here. Allocating floating IPs still does not work. As stated in the initial description a floating IP pool name needs to be given to the allocate request. The allocation request without a floating IP pool name returns a 404 error from the OpenStack API:
T 2015/12/11 14:54:32.130121 192.168.32.26:52800 -> 10.20.31.200:8774 [AP] POST /v2/7829521236b143d2a6778e09ba588ec0/os-floating-ips HTTP/1.1..Accept: application/json..X-Auth-Token: 8b595861d20a4439a7a2c10c40f0fa56..User-Agent : jclouds/1.9.1 java/1.7.0_91..Content-Type: application/json..Host: controller-test.os.open-xchange.com:8774..Connection: keep-alive..Content-Length: 2
T 2015/12/11 14:54:32.130179 192.168.32.26:52800 -> 10.20.31.200:8774 [AP] {}
I noticed that the org.jclouds.openstack.nova.v2_0.compute.options.NovaTemplateOptions.floatingIpPoolNames never gets filled when Jenkins starts up and uses the JClouds plugin for the first time. So for OpenStack this needs to initialized. The request for that looks like this:
T 2015/12/11 15:10:04.302749 192.168.32.26:53526 -> 10.20.31.200:8774 [AP] GET /v2/7829521236b143d2a6778e09ba588ec0/os-floating-ip-pools HTTP/1.1..Host: controller-test.os.open-xchange.com:8774..Connection: keep-alive..User-Age nt: python-novaclient..Accept-Encoding: gzip, deflate..Accept: application/json..X-Auth-Token: fe5cbfa85d2f4fa6acd2e41b95952889
T 2015/12/11 15:10:04.672083 10.20.31.200:8774 -> 192.168.32.26:53526 [AP] HTTP/1.1 200 OK..Content-Type: application/json..Content-Length: 44..X-Compute-Request-Id: req-c7630be4-07f9-4abb-a88d-f9ca41872229..Date: Fri, 11 Dec 2 015 14:10:04 GMT..Connection: keep-alive{"floating_ip_pools": [ {"name": "dmz-net"}
]}
Another possible option is to provide a configuration text parameter where floating IP pools should be listed. Best would be to have a checkbox asking if JClouds should allocate floating IPs from all available floating IP pools - with above request to list floating IP pools - or from a configured list.
Add Comment
This message was sent by Atlassian
[JIRA] [release-plugin] (JENKINS-31702) Post successful build steps are executed when build fails
Title: Message Title Marcus Klein created an issue Jenkins / JENKINS-31702 Post successful build steps are executed when build fails Issue Type: Bug Assignee: Peter Hayes Components: release-plugin Created: 23/Nov/15 9:56 AM Environment: Standalone Jenkins 1.638 with release plugin 2.5.4 Labels: plugin Priority: Critical Reporter: Marcus Klein First build step was to copy artifacts from another job. This build step failed. Configured post successful build steps of the release plugin are executed anyway. But they should not be executed in my eyes when some build step fails. Do you have any hints how to debug this?
[JIRA] [release-plugin] (JENKINS-31702) Post successful build steps are executed when build fails
Title: Message Title Marcus Klein commented on JENKINS-31702 Re: Post successful build steps are executed when build fails I use the Git Publisher plugin as post successful build step. This plugin offers as first option to push only if build succeeds. But this option is broken, too. It fails with a NullPointerException: https://issues.jenkins-ci.org/browse/JENKINS-31678 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-31702) Post successful build steps are executed when build fails
Title: Message Title Marcus Klein edited a comment on JENKINS-31702 Re: Post successful build steps are executed when build fails I use the Git Publisher plugin as post successful build step. This plugin offers as first option to push only if build succeeds. But this option is broken, too. It fails with a NullPointerException: https://issues.jenkins-ci.org/browse/JENKINS-31678 So there is currently no possibility to push to Git only when the build succeeds. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31678) NullPointerException when using GitPublisher in release post build actions
Title: Message Title Marcus Klein created an issue Jenkins / JENKINS-31678 NullPointerException when using GitPublisher in release post build actions Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 20/Nov/15 11:29 AM Environment: Debian Wheezy running Jenkins 1.638 with git-plugin 2.4.0. Labels: git plugin exception Priority: Major Reporter: Marcus Klein Configure a job to use the Jenkins release plugin and use the Git publisher as release step after a successful release build. Tick the checkbox "Push only If Build Succeeds". Then a release build failes with the following NullPointerException: FATAL: null java.lang.NullPointerException at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:203) at hudson.plugins.release.ReleaseWrapper.executeBuildSteps(ReleaseWrapper.java:423) at hudson.plugins.release.ReleaseWrapper.access$300(ReleaseWrapper.java:99) at hudson.plugins.release.ReleaseWrapper$4.tearDown(ReleaseWrapper.java:370) at hudson.model.Build$BuildExecution.doRun(Build.java:173)
[JIRA] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains whitespace
Marcus Klein
commented on JENKINS-24686
scm-sync-configuration fails if job name contains whitespace
To work around this issue use the following code in the Jenkins Script console:
hudson.PluginWrapper scmPluginWrapper = jenkins.model.Jenkins.getInstance().getPluginManager().getPlugin("scm-sync-configuration");
java.util.List? commitsQueue = scmPluginWrapper.getPlugin().business.commitsQueue;
// commitsQueue.remove(0);
println(commitsQueue);
Uncomment then the commented line to remove the commit, that breaks the commit process.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-12006) Branch specifier does not replace matrix build variables
Marcus Klein commented on JENKINS-12006 Branch specifier does not replace matrix build variables I solved this by using a Git poll job polling every Git branch. This poll job then starts the long build pipeline and every job in this pipeline has a parameter for the branch. So I can achieve to use the same job for different branches. The main disadvantage is, that a green Jenkins does not mean, all branches are green. Only the last build of some branch is green. This does not get better when using the dynamic axis plugin for the branches. You still can not see, if all branches are green. So we have a last job in the pipeline, that collects all test results, build results from the complete pipeline and publishes that. Developers have then only to look into the builds of this last job to see, if some branch is green or not. Having this all in a matrix view would be much more convenient. And furthermore this matrix should be variable somehow, so developers can create feature branches and those are tested automatically, too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-24686) scm-sync-configuration fails if job name contains a whitespace
Marcus Klein created JENKINS-24686 scm-sync-configuration fails if job name contains a whitespace Issue Type: Bug Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 12/Sep/14 8:20 AM Description: scm-sync-configuration plugin is configured to sync to a Git repository. If a job contains a whitespace in its name, then the plugin fails to commit the configuration of that job. Sep 11, 2014 11:21:19 AM FINE hudson.plugins.scm_sync_configuration.SCMManipulator Checking in SCM files ... Sep 11, 2014 11:21:19 AM FINER org.apache.maven.scm.manager.ScmManager checkIn THROW org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.executeCommand(AbstractGitScmProvider.java:291) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.checkin(AbstractGitScmProvider.java:217) at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:415) at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:397) at org.apache.maven.scm.manager.AbstractScmManager.checkIn(AbstractScmManager.java:423) at hudson.plugins.scm_sync_configuration.SCMManipulator.checkinFiles(SCMManipulator.java:242) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.processCommitsQueue(ScmSyncConfigurationBusiness.java:208) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.access$000(ScmSyncConfigurationBusiness.java:29) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:143) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:141) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.maven.scm.ScmException: Error while executing command. at org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.execute(GitCommandLineUtils.java:122) at org.apache.maven.scm.provider.git.gitexe.command.checkin.GitCheckInCommand.executeCheckInCommand(GitCheckInCommand.java:129) at org.apache.maven.scm.command.checkin.AbstractCheckInCommand.executeCommand(AbstractCheckInCommand.java:54) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) ... 14 more Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error inside systemOut parser at org.codehaus.plexus.util.cli.CommandLineUtils$1.call(CommandLineUtils.java:188) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:107) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:74) at org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.execute(GitCommandLineUtils.java:118) ... 17 more Caused by: java.lang.IllegalArgumentException: Illegal character in path at index 0: "jobs/OXUpdater%20Core/config.xml" at java.net.URI.create(URI.java:859) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.resolveURI(GitStatusConsumer.java:251) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.resolvePath(GitStatusConsumer.java:232) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.consumeLine(GitStatusConsumer.java:138) at org.codehaus.plexus.util.cli.StreamPumper.consumeLine(StreamPumper.java:190) at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:135) Caused by: java.net.URISyntaxException: Illegal character in path at index 0: "jobs/OXUpdater%20Core/config.xml" at java.net.URI$Parser.fail(URI.java:2829) at java.net.URI$Parser.checkChars(URI.java:3002) at
[JIRA] [core] (JENKINS-21747) Artifact archiving fails with java.lang.NoClassDefFoundError
Marcus Klein commented on JENKINS-21747 Artifact archiving fails with java.lang.NoClassDefFoundError I encouter the same issue on Ubuntu 14.04.1 LTS. Ant 1.9.3, Oracle Java 1.8.0_20. When I look into the source code of Ant, this problem seems to be related to Ant. Some of the static initializers of org.apache.tools.ant.Location fail. Either this one: private static final FileUtils FILE_UTILS = FileUtils.getFileUtils(); or some import fails: import org.apache.tools.ant.util.FileUtils; import org.xml.sax.Locator; This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-14332) Repeated channel/timeout errors from Jenkins slave
Marcus Klein commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave My jobs are randomly failing with version 1.550 with the following exception: FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown: java.util.concurrent.TimeoutException: Ping started on 1392852728137 hasn't completed at 1392852968137 hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown: java.util.concurrent.TimeoutException: Ping started on 1392852728137 hasn't completed at 1392852968137 at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) at com.sun.proxy.$Proxy47.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:925) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.Ant.perform(Ant.java:217) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown: java.util.concurrent.TimeoutException: Ping started on 1392852728137 hasn't completed at 1392852968137 at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:927) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: hudson.remoting.Channel$OrderlyShutdown: java.util.concurrent.TimeoutException: Ping started on 1392852728137 hasn't completed at 1392852968137 ... 3 more Caused by: Command close created at at hudson.remoting.Command.init(Command.java:56) at hudson.remoting.Channel$CloseCommand.init(Channel.java:921) at hudson.remoting.Channel$CloseCommand.init(Channel.java:919) at hudson.remoting.Channel.close(Channel.java:1002) at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110) at hudson.remoting.PingThread.ping(PingThread.java:120) at hudson.remoting.PingThread.run(PingThread.java:81) Caused by: java.util.concurrent.TimeoutException: Ping started on 1392852728137 hasn't completed at 1392852968137 ... 2 more I rolled back to version 1.546 because I think it did not happen with that version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-12006) Branch specifier does not replace matrix build variables
Marcus Klein reopened JENKINS-12006 Branch specifier does not replace matrix build variables See my previous comment Change By: Marcus Klein (14/Nov/13 10:27 AM) Resolution: WontFix 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/groups/opt_out.
[JIRA] [git] (JENKINS-12006) Branch specifier does not replace matrix build variables
Marcus Klein commented on JENKINS-12006 Branch specifier does not replace matrix build variables @Nicolas: Your assumption is not correct. git SCM can detect changes in multiple branches during a single detect run. In our case this happens quite often. We are using the following branching model: http://nvie.com/posts/a-successful-git-branching-model/. This results in continuous commits in branches develop, release-something and hotfixes-something. Open-Xchange does this to develop features for the next release in branch develop, to harden the upcoming release in the release-something branch (bugfixing) and to maintain old releases (fixing of security issues e.g.). This requires builds in different branches if those branches have changes. Additionally I want to view and monitor test results in all these branches without selecting a certain job run. To do this, we want to use the matrix feature. Is this an exotic way of using git and Jenkins matrix feature? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Marcus Klein created JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 14/Mar/13 11:20 AM Description: With the latest update of the git-client-plugin the default behavior is to use the JGit implementation instead of the git command line tool. For the git command line tool I set up HTTP authentication using the file .netrc in the home directory of Jenkins. This does not work anymore with the default JGit implementation. I had to switch back to the git command line tool, which is pretty annoying because the system property needs to be added to the JVM options of every slave. Environment: Debian Squeeze, Jenkins 1.505, running in standalone mode, multiple slaves running on MacOS X and Debian Squeeze Project: Jenkins Priority: Major Reporter: Marcus Klein This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Marcus Klein commented on JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin You have to add -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true to the JVM options of the master and every slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15592) Endless loop in hudson.model.Job.getLastFailedBuild
Marcus Klein commented on JENKINS-15592 Endless loop in hudson.model.Job.getLastFailedBuild Jenkins should ignore the misleading link and create the link newly after a new stable build was done. Or it should even delete the misleading link. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15592) Endless loop in hudson.model.Job.getLastFailedBuild
Marcus Klein
commented on JENKINS-15592
Endless loop in hudson.model.Job.getLastFailedBuild
I found the broken links using this command:
find . -type l -exec file {} \; | grep broken
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
