[JIRA] (JENKINS-5413) SCM polling getting hung
Title: Message Title Meng Xin Zhu commented on JENKINS-5413 Re: SCM polling getting hung Still happening on Jenkins LTS 2.19.4. My job is periodically polling from git repo(every 5 minutes). However the scm polling might hang infinitely without timeout. The subsequent manually job building also is blocked by scm polling. It's definitely a critical issue to impact the usability of jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-34165) Null pointer exception polling from git job to bitbucket repo
Title: Message Title Meng Xin Zhu commented on JENKINS-34165 Re: Null pointer exception polling from git job to bitbucket repo I am able to reproduce the same exception when building a job only checking option 'This build is parameterized' without defining any certain parameter. jenkins ver, 1.651.2 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] [parameterized-trigger-plugin] (JENKINS-30217) The response of building parametered build via remote api is broken
Title: Message Title Meng Xin Zhu created an issue Jenkins / JENKINS-30217 The response of building parametered build via remote api is broken Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 31/Aug/15 2:43 AM Environment: in both 1.627(without plugin) and 1.609.2 Priority: Critical Reporter: Meng Xin Zhu When triggering a new build without parameters via remote api, we can get a the queued item url for retrieving the build detail later. It works fine. ➜ rest git:(master) curl -X POST http://localhost:8080/job/TestBuildWithoutParameter/build -D - HTTP/1.1 201 Created X-Content-Type-Options: nosniff Location: http://localhost:8080/queue/item/5/ Content-Length: 0
[JIRA] [parameterized-trigger-plugin] (JENKINS-30217) The response of building parametered build via remote api is broken
Title: Message Title Meng Xin Zhu updated an issue Jenkins / JENKINS-30217 The response of building parametered build via remote api is broken Change By: Meng Xin Zhu Labels: apiparameterized-triggerremote 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] [docker-build-step-plugin] (JENKINS-29775) client is too old, minimum supported API version is 1.12
Title: Message Title Meng Xin Zhu commented on JENKINS-29775 Re: client is too old, minimum supported API version is 1.12 He meat you have to specify the docker client API version in docker step plugin of Jenkins global configuration. It works fine for me after corrected the version of client API in global configuration. 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] [cli] (JENKINS-17929) Fail to run 'groovysh' in CLI due to insufficient permission
Meng Xin Zhu
created JENKINS-17929
Fail to run groovysh in CLI due to insufficient permission
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
cli
Created:
13/May/13 6:00 AM
Description:
1: verified that I am authenticated: java -jar jenkins-cli.jar -s http://myserver/jenkins who-am-i
Authenticated as: myuser
Authorities:
authenticated
2: tried to run a trivial script via groovysh and got an error
java -jar jenkins-cli.jar -s http://myserver/jenkins groovysh 'jenkins.model.Jenkins.instance.pluginManager.plugins.each { println("${it.longName} - ${it.version}") };'
Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
at $Proxy2.main(Unknown Source)
at hudson.cli.CLI.execute(CLI.java:271)
at hudson.cli.CLI._main(CLI.java:417)
at hudson.cli.CLI.main(CLI.java:322)
Caused by: hudson.remoting.ProxyException: hudson.security.AccessDeniedException2: anonymous is missing the Administer permission
The workaround is using command 'groovysh' instead.
java -jar jenkins-cli.jar -s http://localhost:8080/jenkins/ groovy test_script.gsh
It's also discussed in group.1
1 https://groups.google.com/forum/#!msg/jenkinsci-users/Vb1p7tbWfQk/4vcVrHOC19MJ
Environment:
version 1.502
Project:
Jenkins
Priority:
Major
Reporter:
Meng Xin Zhu
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [cli] (JENKINS-13744) Can't build job with project-based security even the user is an adminstrator via CLI
Meng Xin Zhu commented on JENKINS-13744 Cant build job with project-based security even the user is an adminstrator via CLI It works fine on version 1.502 now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
Meng Xin Zhu commented on JENKINS-16940 Git publisher fails with Invalid id: origin/master when trying to publish changes +1 It's a regression bug, very annoying. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-14814) Ping-pong builds store excessively large CauseAction
Meng Xin Zhu commented on JENKINS-14814 Ping-pong builds store excessively large CauseAction Do you know which build starts to have this fix? Because I still see similar issue happened in LTS 1.480.2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-13744) Can't build job with project-based security even the user is an adminstrator via CLI
Meng Xin Zhu created JENKINS-13744: -- Summary: Can't build job with project-based security even the user is an adminstrator via CLI Key: JENKINS-13744 URL: https://issues.jenkins-ci.org/browse/JENKINS-13744 Project: Jenkins Issue Type: Bug Components: cli Environment: Jenkins 1.451, Reporter: Meng Xin Zhu Use private key and public key for authentication. The job has project-based security, and anonymous even can't read it. The running user is an administrator and added in the project-based list to run it. java -jar jenkins-cli.jar -s http://szg-build.wrs.com:8080 who-am-i Authenticated as: kzhu0 Authorities: users authenticated java -jar jenkins-cli.jar -s http://szg-build.wrs.com:8080 get-job myjob No such job 'myjob' perhaps you meant 'Core - Scripting'? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
