[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Vanja Radovanović commented on JENKINS-25267 Gitlab hook not building on merge request object @Henri as you probably read in previous comments, the plugin currently does not support this. I am a bit ambivalent to the idea in the first place. Why would you need such a thing when the above described flow works nicely? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Vanja Radovanović commented on JENKINS-25267 Gitlab hook not building on merge request object Ah, ok This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Vanja Radovanović commented on JENKINS-25267 Gitlab hook not building on merge request object Not at this point. Processing MR's requires a lot of communication with Gitlab, not just processing it's payload. And we have other more pressing topics to solve. I am still fishing for a right use case to solve though. If you can describe why you need MR to be built, e.g. a bit more detailed flow, that could be helpful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-24232) Hook fails on parametrized jobs
Vanja Radovanović commented on JENKINS-24232 Hook fails on parametrized jobs No definite timeline just yet. Have to close a few remaining issues. Hopefully in a month. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs] (JENKINS-20636) RVM and NodeJS plugins are incompatible
Vanja Radovanović commented on JENKINS-20636 RVM and NodeJS plugins are incompatible I've had the same experience with rbenv plugin. Started by user Vanja Radovanović [EnvInject] - Loading node environment variables. Building remotely on ci-clave (available linux) in workspace /opt/jenkins/workspace/test-project Wiping out workspace first. Cloning the remote Git repository Cleaning workspace $ bash -c "[ -d \$HOME/.rbenv ]" $ bash -c "[ -d \$HOME/.rbenv/plugins/ruby-build ]" Just ignoring local Ruby version. $ bash -c "mkdir \$HOME/.rbenv.lock" $ bash -c "mkdir \$HOME/.rbenv.lock" $ bash -c "mkdir \$HOME/.rbenv.lock" . $ bash -c "mkdir \$HOME/.rbenv.lock" ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com org.jruby.exceptions.RaiseException: (LockError) could not acquire lock in 1000 seconds. at RUBY.release_lock(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv/semaphore.rb:31) at RUBY.synchronize(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv/semaphore.rb:14) at RUBY.setup!(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv.rb:24) at RUBY.setup(C:/.jenkins/plugins/rbenv/WEB-INF/classes/models/rbenv_wrapper.rb:61) at RUBY.setUp(C:/.jenkins/plugins/rbenv/WEB-INF/classes/vendor/gems/gems/jenkins-plugin-runtime-0.2.3/lib/jenkins/model/environment_proxy.rb:8) project=hudson.maven.MavenModuleSet@9230959[test-project-module] project.getModules()=[hudson.maven.MavenModule@2d785573[test-project/org.test:test-project-module][test-project-module/org.test:test-project-module][relativePath:]] project.getRootModule()=hudson.maven.MavenModule@2d785573[test-project/org.test:test-project-module][test-project-module/org.test:test-project-module][relativePath:] FATAL: (LockError) could not release lock in 1000 secs. org.jruby.exceptions.RaiseException: (LockError) could not release lock in 1000 secs. at RUBY.release_lock(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv/semaphore.rb:44) at RUBY.synchronize(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv/semaphore.rb:17) at RUBY.setup!(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv.rb:24) at RUBY.setup(C:/.jenkins/plugins/rbenv/WEB-INF/classes/models/rbenv_wrapper.rb:61) at RUBY.setUp(C:/.jenkins/plugins/rbenv/WEB-INF/classes/vendor/gems/gems/jenkins-plugin-runtime-0.2.3/lib/jenkins/model/environment_proxy.rb:8) I've tried with an updated version of NodeJS plugin that uses jenkins parent 1.575 and maven-hpi-plugin 1.106 but without any luck. From what I see, rbenv plugin can execute native bash commands normally (e.g. directory location testing) but the PATH is not set for it so commands like mkdir, git, env and others just fail. When I turn off the NodeJS plugin from the job configuration, everything works as expected. We use Jenkins 1.575. The master is a windows machine and the slave is CentOS one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook] (JENKINS-23370) Gitlab web hook fails when Cross Site Request Forgery protection is active
Vanja Radovanović closed JENKINS-23370 as Fixed Gitlab web hook fails when Cross Site Request Forgery protection is active This has been resolved with issue #30 @ github, see https://github.com/elvanja/jenkins-gitlab-hook-plugin/issues/30 Change By: Vanja Radovanović (17/Jul/14 6:47 AM) Status: Open Closed Assignee: VanjaRadovanović 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] [gitlab-hook] (JENKINS-20598) Add an option to deactivate hook for a job
Vanja Radovanović closed JENKINS-20598 as Fixed Add an option to deactivate hook for a job Exactly like Alex said. That should be sufficient to filter out unwanted jobs. This is also mentioned in documentation: https://github.com/elvanja/jenkins-gitlab-hook-plugin#additional-notes Change By: Vanja Radovanović (17/Jul/14 6:46 AM) Status: Open Closed 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.
