[JIRA] [core] (JENKINS-27188) BUILDID and BUILD_TAG from previous project
Daniel Beck commented on JENKINS-27188 BUILDID and BUILD_TAG from previous project A user reported this issue affecting Jenkins 1.602. Does anyone watching this issue know anything about 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] [groovy-postbuild-plugin] (JENKINS-27317) Run Groovy script only on matrix parent
Sverre Moe created JENKINS-27317 Run Groovy script only on matrix parent Issue Type: New Feature Assignee: wolfs Components: groovy-postbuild-plugin Created: 10/Mar/15 4:25 PM Description: Would it be possible to have Groovy Postbuild to only run the script on matrix parent? I have a groovy script I want to run once after all matrix configurations have been triggered and completed. Project: Jenkins Priority: Major Reporter: Sverre Moe 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] [gradle-plugin] (JENKINS-27310) gradle automatic install Invalid tool ID
Daniel Beck commented on JENKINS-27310 gradle automatic install Invalid tool ID Please provide the content of the Gradle related file (hudson.plugins.gradle.GradleInstaller.json or similar) in JENKINS_HOME/updates. 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-27311) 404 on actions such as "Add build step" and "Add post-build action"
Daniel Beck commented on JENKINS-27311 404 on actions such as "Add build step" and "Add post-build action" Troubleshooting hints here: https://issues.jenkins-ci.org/browse/JENKINS-9142?focusedCommentId=163204&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-163204 The requests don't look like it, but make sure you don't have dozens of cookies for this domain. 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-27349) Git SCM-polling uses wrong parameter values for a parametrized branchspec
Jean Blanchard commented on JENKINS-27349 Git SCM-polling uses wrong parameter values for a parametrized branchspec I updated my original pull-request to fix only this. https://github.com/jenkinsci/git-plugin/pull/293 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] [delivery-pipeline-plugin] (JENKINS-27354) Error communicating to server! timeout
Anders Nyström created JENKINS-27354 Error communicating to server! timeout Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 11/Mar/15 10:15 AM Description: Gets this error "Error communicating to server! timeout" every time I try to look at my pipeline. It only works like 1 time on 10 to 20 tries. Jenkins version: 1.599 Delivery Pipeline Plugin: 0.8.9 Project: Jenkins Priority: Blocker Reporter: Anders Nyström 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] [websphere-deployer-plugin] (JENKINS-22393) Problem deploying EAR to WAS 7
Florent Moisson commented on JENKINS-22393 Problem deploying EAR to WAS 7 Hi, I prepared a fix to this issue on a github fork, however the pull request is failing because of the IC. The IBM libraries are no longer available on repo.jenkins-ci.org, does anyone know if these deletions are intentional? Fork : https://github.com/Floww/websphere-deployer-plugin Build log : https://jenkins.ci.cloudbees.com/job/plugins/job/websphere-deployer-plugin/9/console Flo. 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-27318) MissingMethodException when name column used within collection closure of job dsl script
Kyle Cronin
created JENKINS-27318
MissingMethodException when name column used within collection closure of job dsl script
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
10/Mar/15 4:56 PM
Description:
The following job dsl script will cause a MissingMethodException to be thrown. Though if name() is removed from the columns configuration, the script works.
def views = ['-Default-':[regex:'.*-default\$'],
'9.3':[regex:'.*-9\\.3\$']]
views.each { name, cfg ->
listView(name) {
jobs {
regex(cfg.regex)
}
columns {
status()
weather()
name()
lastSuccess()
lastFailure()
lastDuration()
buildButton()
}
}
}
The resulting stack trace when the above script is executed on http://job-dsl.herokuapp.com/.
groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: () values: []
Possible solutions: wait(), any(), wait(long), any(groovy.lang.Closure), take(int), each(groovy.lang.Closure)
at script1426003356915461733692$_run_closure1_closure2_closure4.doCall(script1426003356915461733692.groovy:11)
at script1426003356915461733692$_run_closure1_closure2_closure4.doCall(script1426003356915461733692.groovy)
at javaposse.jobdsl.dsl.ContextHelper.executeInContext(ContextHelper.groovy:14)
at javaposse.jobdsl.dsl.ContextHelper$executeInContext.callStatic(Unknown Source)
at javaposse.jobdsl.dsl.ContextHelper$executeInContext.callStatic(Unknown Source)
at javaposse.jobdsl.dsl.views.ListView.columns(ListView.groovy:51)
at script1426003356915461733692$_run_closure1_closure2.doCall(script1426003356915461733692.groovy:8)
at javaposse.jobdsl.dsl.JobParent.processView(JobParent.groovy:116)
at javaposse.jobdsl.dsl.JobParent.this$4$processView(JobParent.groovy)
at javaposse.jobdsl.dsl.JobParent$this$4$processView.callCurrent(Unknown Source)
at javaposse.jobdsl.dsl.JobParent$this$4$processView.callCurrent(Unknown Source)
at javaposse.jobdsl.dsl.JobParent.listView(JobParent.groovy:85)
at script1426003356915461733692$_run_closure1.doCall(script1426003356915461733692.groovy:4)
at script1426003356915461733692.run(script1426003356915461733692.groovy:3)
at javaposse.jobdsl.dsl.DslScriptLoader.runDslEngineForParent(DslScriptLoader.java:72)
at javaposse.jobdsl.dsl.DslScriptLoader$runDslEngineForParent.call(Unknown Source)
at com.sheehan.jobdsl.DslScriptExecutor.execute(DslScriptExecutor.groovy:31)
at com.sheehan.jobdsl.ScriptExecutor$execute.call(Unknown Source)
at Ratpack$_run_closure1_closure3_closure7.doCall(Ratpack.groovy:39)
at ratpack.groovy.internal.ClosureInvoker.invoke(ClosureInvoker.java:65)
at ratpack.groovy.handling.internal.ClosureBackedHandler.handle(ClosureBackedHandler.java:42)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.next(DefaultContext.java:223)
at ratpack.http.internal.MethodHandler.handle(MethodHandler.java:41)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.insert(DefaultContext.java:237)
at ratpack.handling.internal.ChainHandler.handle(ChainHandler.java:37)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.insert(DefaultContext.java:246)
at ratpack.path.internal.PathHandler.handle(PathHandler.java:38)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.next(DefaultContext.java:223)
at ratpack.path.internal.PathHandler.handle(PathHandler.java:40)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.next(DefaultContext.java:223)
at ratpack.path.internal.PathHandler.handle(PathHandler.java:40)
at ratpack.handling.internal.DefaultContext.doNext(DefaultContext.java:448)
at ratpack.handling.internal.DefaultContext.insert(DefaultContext.java:237)
at ratpack.handling.internal.ChainHandler.handle(ChainHan
[JIRA] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Jean Blanchard commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name Actually it's not. Created JENKINS-27349 for it to have proper tracking. Also created related issues (that I also fixed in my original PR): JENKINS-27351 and JENKINS-27352. 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-27319) Folders don't support the authorization/permissions closure
Pedro Algarvio
created JENKINS-27319
Folders don't support the authorization/permissions closure
Issue Type:
Improvement
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
10/Mar/15 6:39 PM
Description:
There's no support for the authorization closure and respective permission.
I've made it work like:
maintenance-dsl.groovy
folder('maintenance') {
displayName('Jenkins Maintenance Jobs')
configure {
folder_properties = it.get('properties').get(0)
auth_matrix_prop = folder_properties.appendNode(
'com.cloudbees.hudson.plugins.folder.properties.AuthorizationMatrixProperty'
)
auth_matrix_prop.appendNode('permission').setValue(
":"
)
}
}
It would be nice to support the authorization closure like Jobs do.
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] [git-plugin] (JENKINS-24520) Recent changes is always empty
Craig Rodrigues commented on JENKINS-24520 Recent changes is always empty Is this still a problem with the latest version of git plugin, and multiple-scms plugin 0.4? 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-20607) GIT Plugin 2.0: Polling ignores commit from certain users not working
Hubert S edited a comment on JENKINS-20607 GIT Plugin 2.0: Polling ignores commit from certain users not working This works with: GIT Client 1.16.1 GIT plugin 2.3.5 Jenkins 1.580.1 What caught me is the syntax of the config. I was only putting in the email, and it turns out I need to be far more explicit. For instance, my Git commit username is: "First Last " For the Jenkins config field, I added: "First Last" "First Last " For this to start working. 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] [pam-auth-plugin] (JENKINS-25741) Unix User/Group Authentication Fails
Martijn van Iersel commented on JENKINS-25741 Unix User/Group Authentication Fails After recent upgrade I'm seeing the exact same issue. I get the same stack trace while attempting to log in with my unix account. I have jenkins 1.601 installed from the apt repositories. The log in /var/log/jenkins/jenkins.log does not give any additional 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] [core] (JENKINS-27353) Downstream projects get same build cause as its upstream project
Sverre Moe updated JENKINS-27353 Downstream projects get same build cause as its upstream project Change By: Sverre Moe (12/Mar/15 8:09 AM) Environment: Jenkins 1.599Matrix Project Plugin 1.4 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-27311) 404 on actions such as "Add build step" and "Add post-build action"
Daniel Beck commented on JENKINS-27311 404 on actions such as "Add build step" and "Add post-build action" The attached log does not even cover one second. To clarify, when reloading the $stapler/build/... URL, nothing gets added to the log? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27379) Stability issues faced with Jenkins 1.580.3 due to blocked threads
Ludovic Vercruysse created JENKINS-27379 Stability issues faced with Jenkins 1.580.3 due to blocked threads Issue Type: Bug Assignee: Unassigned Attachments: threads.txt Components: core Created: 12/Mar/15 8:17 AM Description: Dear, After upgrading our Jenkins instance from Jenkins 1.509.4 to Jenkins 1.580.3 (identified as LTS). Following this upgrade, we are facing stability issues and need to restart our Jenkins instance once or twice per day (which has an important impact for the company) The heapdump enclosed to this ticket show that several threads remain blocked in the JVM. "Finalizer" daemon prio=8 tid=3 BLOCKED As a result, CPU usage is increasing and the JVM fails in an OutOfMemory. As short term action, we have already increased by 4Gb the RAM of the server, but of course, it does not solve the issue, it only reduces a bit the impact. Have you already identified this issue ? If yes, is there a fix ? In which release ? Best regards Project: Jenkins Priority: Blocker Reporter: Ludovic Vercruysse 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-27211) Please add ability to use the git 'clean' options AFTER job execution
Nathan Neulinger commented on JENKINS-27211 Please add ability to use the git 'clean' options AFTER job execution I can clean the whole workspace, but that just means the inefficiency of updating the clone from repo server 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] [subversion-plugin] (JENKINS-27324) org.tmatesoft.svn.core.SVNException: svn: E175002: Processing REPORT request response failed
Berk Atabek closed JENKINS-27324 as Duplicate org.tmatesoft.svn.core.SVNException: svn: E175002: Processing REPORT request response failed Change By: Berk Atabek (12/Mar/15 8:17 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27311) 404 on actions such as "Add build step" and "Add post-build action"
Ivaylo Marinkov updated JENKINS-27311 404 on actions such as "Add build step" and "Add post-build action" I created the logger and have attached the output to the Jira. Change By: Ivaylo Marinkov (12/Mar/15 8:16 AM) Attachment: org.kohsuke.stapler.Stapler-log.txt 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-26668) Tag this build ignores credentials set up in Jenkins - only works if you have cached credentials in .subversion
Ville Nummela commented on JENKINS-26668 Tag this build ignores credentials set up in Jenkins - only works if you have cached credentials in .subversion jenkins version 1.596.1, plugin version 2.5. Tagging does not work from jenkins - it works fine from command line using jsvn with cached password. I would be quite happy if the workaround worked for me as well, but no... 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-27353) Downstream projects get same build cause as its upstream project
Sverre Moe created JENKINS-27353 Downstream projects get same build cause as its upstream project Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core, matrix-project-plugin Created: 11/Mar/15 10:00 AM Description: When a downstream project is triggered it gets the same build cause as its upstream project. If upstream project ProjectA is triggered manually by a user, then the downstream project ProjectB gets the same build cause. In effect there is no way to find out if ProjectB was triggered from an upstream project. From hudson.model.AbstractBuild: build.getCauses() will always yield hudson.model.Cause.UpstreamCause It works for a Free-style project, but its wrong cause in a Multi-Configuration Job. Free-style Jobs: ProjectA cause.toString() == hudson.model.Cause$UserIdCause@caebc9aa cause.getClass() == class hudson.model.Cause$UserIdCause ProjectB cause.toString() == job/projectA/1[hudson.model.Cause$UserIdCause@2efba933] cause.getClass() == class hudson.model.Cause$UpstreamCause Multi-configuration Jobs: ProjectA cause.toString() == hudson.model.Cause$UserIdCause@caebc9aa cause.getClass() == class hudson.model.Cause$UserIdCause ProjectB cause.toString() == job/projectA/1[hudson.model.Cause$UserIdCause@2efba933] cause.getClass() == class hudson.model.Cause$UserIdCause Project: Jenkins Priority: Critical Reporter: Sverre Moe 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-27352) Git SCM polling is not triggered from a push notification with a parametrized branchspec
Jean Blanchard commented on JENKINS-27352 Git SCM polling is not triggered from a push notification with a parametrized branchspec Fixed in pull-request https://github.com/jenkinsci/git-plugin/pull/309 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-27211) Please add ability to use the git 'clean' options AFTER job execution
Nathan Neulinger commented on JENKINS-27211 Please add ability to use the git 'clean' options AFTER job execution That's true, for the 'delete' case. However, it's a lot easier to universally say "Hey, if you have a job, mark it to 'git clean' at the end of the job if the job is successful". That takes care of most of the build scenarios where the content of the job is much larger than the repo. It looks like I could rig up something with: https://wiki.jenkins-ci.org/display/JENKINS/Global+Post+Script+Plugin Just seems like this would be much easier to have here since it's already controlling that cleanup process during init, and it's already aware of each of the clone paths in the 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] [workflow-plugin] (JENKINS-26761) WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart
Kenneth Baltrinic edited a comment on JENKINS-26761 WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart I realized that the question of lastSuccessfulBuild was spurious because what really matters is the most recent build, regardless of status. I checked all the builds and they all have the requisite linked-list entry. However, I have attached the xml for the most recent failed build. 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] [msbuild-plugin] (JENKINS-27181) Property validators in configuration verify directory exists when parameter is asking for an executable.
Ivo Bellin Salarin updated JENKINS-27181 Property validators in configuration verify directory exists when parameter is asking for an executable. Change By: Ivo Bellin Salarin (12/Mar/15 8:27 AM) Component/s: mstestrunner-plugin Component/s: mstest-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] [core] (JENKINS-27357) Warning about 'browser-based download' needs more explanation
davida2009 resolved JENKINS-27357 as Fixed Warning about 'browser-based download' needs more explanation Thanks - that answers my question. So I have marked this issue resolved. (I assume that the wrong indentation of the checkbox is addressed by another issue). Change By: davida2009 (12/Mar/15 8:28 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27361) In IE11, horiz scrollbar overlaps Jenkins content
davida2009 updated JENKINS-27361 In IE11, horiz scrollbar overlaps Jenkins content Attached screenshot. Change By: davida2009 (11/Mar/15 2:06 PM) Attachment: screenshot.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27256) Jenkins Remote API - Queue behavior changed
Daniel Beck commented on JENKINS-27256 Jenkins Remote API - Queue behavior changed I wrote a plugin that exposes the /queuefix/item/xx URL and can be used like /queue/item/xx. Source code (for the paranoid): https://github.com/daniel-beck/jenkins-queuefix-plugin Plugin download (for the inept): https://dl.dropboxusercontent.com/u/29853/queuefix-JENKINS-27256.hpi Plugins can be uploaded to Jenkins via the Manage Plugins "Advanced" tab. 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] [envinject-plugin] (JENKINS-27342) SCM polling fails with NPE in EnvInjectPluginAction$1.transformEntry [...] after upgrading to 1.91
wolfs commented on JENKINS-27342 SCM polling fails with NPE in EnvInjectPluginAction$1.transformEntry [...] after upgrading to 1.91 Thanks for looking into this. Is it necessary to release envinject-lib, too? Obviously after merging https://github.com/jenkinsci/envinject-lib/pull/4 and then pulling another release of the envinject-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] [core] (JENKINS-27357) Warning about 'browser-based download' needs more explanation
Daniel Beck updated JENKINS-27357 Warning about 'browser-based download' needs more explanation Change By: Daniel Beck (12/Mar/15 8:47 AM) Status: Reopened Open 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-27357) Warning about 'browser-based download' needs more explanation
Daniel Beck reopened JENKINS-27357 Warning about 'browser-based download' needs more explanation It's not. Change By: Daniel Beck (12/Mar/15 8:47 AM) Resolution: Fixed 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] [matrix-project-plugin] (JENKINS-27356) Configure short workspace name per project
Oliver Gondža commented on JENKINS-27356 Configure short workspace name per project Fix proposed: https://github.com/jenkinsci/matrix-project-plugin/pull/18 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-27311) 404 on actions such as "Add build step" and "Add post-build action"
Daniel Beck commented on JENKINS-27311 404 on actions such as "Add build step" and "Add post-build action" If you know how to add headers to your requests using your browser's dev tools, run the following in Manage Jenkins » Script Console: org.kohsuke.stapler.Dispatcher.TRACE_PER_REQUEST = true And then add the header X-Stapler-Trace: true to your /$stapler/bound requests. Then, the log recorder for the logger org.kohsuke.stapler.Dispatcher will log things on FINE, and the 404 response should also contain some debug output. If you don't know how to add headers, run org.kohsuke.stapler.Dispatcher.TRACE = true to enable debug logging for all requests. These changes can be undone any time by running the equivalent ... = false script. 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] [envinject-plugin] (JENKINS-27363) envinject-lib and envinject-plugin should handle null sensitive variables
Oleg Nenashev started work on JENKINS-27363 envinject-lib and envinject-plugin should handle null sensitive variables Change By: Oleg Nenashev (11/Mar/15 4:15 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] [git-plugin] (JENKINS-27332) git-plugin no longer detects changes of branch with /
Dennis Philpot commented on JENKINS-27332 git-plugin no longer detects changes of branch with / Confirmed, my bad only the Git Plugin ist needed. 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] [ant-plugin] (JENKINS-27376) British Pound symbol gets garbled and comes out as a ? mark from Jenkins
Daniel Beck resolved JENKINS-27376 as Cannot Reproduce British Pound symbol gets garbled and comes out as a ? mark from Jenkins Needs to happen with Jenkins versions that are recent. No older than 6-8 weeks for the weekly releases. Report is missing complete and precise instructions how to reproduce the issue. It's not clear how ant-plugin is involved. Change By: Daniel Beck (12/Mar/15 9:03 AM) Status: Open Resolved Resolution: Cannot Reproduce 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] [android-emulator-plugin] (JENKINS-25790) New adb connect command always fails to connect emulator on OS X
Christopher Orr resolved JENKINS-25790 as Duplicate New adb connect command always fails to connect emulator on OS X Change By: Christopher Orr (12/Mar/15 9:07 AM) Status: Open 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] [p4-plugin] (JENKINS-27365) Perforce ticketed credentials in p4 plugin incompatible with p4 command-line behavior
Russ Tremain commented on JENKINS-27365 Perforce ticketed credentials in p4 plugin incompatible with p4 command-line behavior WORK-AROUND is to create a Perforce password credential. Caveat: will not work in Perforce environments where the security level of p4d server has been raised, and password authentication is not allowed. 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] [android-emulator-plugin] (JENKINS-25496) android-21 emulator fails
Christopher Orr closed JENKINS-25496 as Incomplete android-21 emulator fails Change By: Christopher Orr (12/Mar/15 9:06 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-23688) Headless Linux and Valid ABIs: no ABIs.
Christopher Orr resolved JENKINS-23688 as Fixed Headless Linux and Valid ABIs: no ABIs. (Most) system images should now be automatically installed correctly. Change By: Christopher Orr (12/Mar/15 9:09 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-23600) SDK repositories and emulator images do not install
Christopher Orr resolved JENKINS-23600 as Fixed SDK repositories and emulator images do not install (Most) system images should now be automatically installed correctly. Change By: Christopher Orr (12/Mar/15 9:09 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr resolved JENKINS-11952 as Fixed Emulator occasionally hangs indefinitely on startup, unable to connect adb Version 2.13 of the plugin has been released, which includes the updates discussed here. Change By: Christopher Orr (12/Mar/15 9:11 AM) Status: Reopened Resolved Assignee: Richard Mortimer Christopher Orr 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] [android-emulator-plugin] (JENKINS-25336) ABI name parsing is broken
Christopher Orr closed JENKINS-25336 as Fixed ABI name parsing is broken Version 2.13 of the plugin has been released, which includes this fix. Change By: Christopher Orr (12/Mar/15 9:12 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr closed JENKINS-11952 as Fixed Emulator occasionally hangs indefinitely on startup, unable to connect adb I'm marking this issue as closed, though I'm aware of the likelihood that not everything is working brilliantly on every machine, all the time. But if there are still obvious issues in 2.13, let's please open a clean issue. Change By: Christopher Orr (12/Mar/15 9:13 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-13559) Allow extra parameters when running "Android monkey tester"
Christopher Orr closed JENKINS-13559 as Fixed Allow extra parameters when running "Android monkey tester" Version 2.13 of the plugin has been released, which includes this fix. Change By: Christopher Orr (12/Mar/15 9:12 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26338) Entering Emulator Executable value does not work
Christopher Orr closed JENKINS-26338 as Fixed Entering Emulator Executable value does not work Version 2.13 of the plugin has been released, which includes this fix. Change By: Christopher Orr (12/Mar/15 9:12 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-23688) Headless Linux and Valid ABIs: no ABIs.
Christopher Orr closed JENKINS-23688 as Fixed Headless Linux and Valid ABIs: no ABIs. Version 2.13 of the plugin has been released, which includes this fix. Change By: Christopher Orr (12/Mar/15 9:12 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-23252) Replace brackets for new Google APIs emulators
Christopher Orr closed JENKINS-23252 as Fixed Replace brackets for new Google APIs emulators Version 2.13 of the plugin has been released, which includes this fix. Change By: Christopher Orr (12/Mar/15 9:12 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-25497) aapt has been removed from platform-tools in latest SDK version
Christopher Orr closed JENKINS-25497 as Fixed aapt has been removed from platform-tools in latest SDK version Version 2.13 of the plugin has been released, which includes this fix. Change By: Christopher Orr (12/Mar/15 9:12 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-23134) Mixed separators fail for Linux paths
Christopher Orr closed JENKINS-23134 as Fixed Mixed separators fail for Linux paths Version 2.13 of the plugin has been released, which includes this fix. Change By: Christopher Orr (12/Mar/15 9:12 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-23346) Path to android-sdk subfolders is incorrect
Christopher Orr closed JENKINS-23346 as Duplicate Path to android-sdk subfolders is incorrect Change By: Christopher Orr (12/Mar/15 9:13 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-23735) Emulator plugin first time build "adb start-server" times out after 5 seconds
Christopher Orr closed JENKINS-23735 as Incomplete Emulator plugin first time build "adb start-server" times out after 5 seconds Version 2.13 of the plugin has been released, which helps mitigate the problems seen in JENKINS-11952. Change By: Christopher Orr (12/Mar/15 9:15 AM) Status: Open Closed Resolution: Incomplete 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] [android-emulator-plugin] (JENKINS-23600) SDK repositories and emulator images do not install
Christopher Orr closed JENKINS-23600 as Fixed SDK repositories and emulator images do not install Version 2.13 of the plugin has been released, which includes this fix. Change By: Christopher Orr (12/Mar/15 9:12 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26893) Unable to run emulator-arm to start emulator
Christopher Orr closed JENKINS-26893 as Fixed Unable to run emulator-arm to start emulator Version 2.13 of the plugin has been released, which includes this fix. Change By: Christopher Orr (12/Mar/15 9:12 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-22555) android.util.AndroidException: Can't connect to activity manager; is the system running?
Christopher Orr closed JENKINS-22555 as Fixed android.util.AndroidException: Can't connect to activity manager; is the system running? Version 2.13 of the plugin has been released, which includes this fix. Change By: Christopher Orr (12/Mar/15 9:12 AM) Status: Resolved Closed Assignee: 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 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-21712) Jenkins Update breaks Subversion credential configuration
dan russell commented on JENKINS-21712 Jenkins Update breaks Subversion credential configuration Just found this gem as well. Upgrading from 1.5.3 to 2.5 subversion plugin. Even in place generation means changing every 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] [android-emulator-plugin] (JENKINS-24956) Path Seperator on OSX. using $HOME + tools path causes problems
Christopher Orr closed JENKINS-24956 as Duplicate Path Seperator on OSX. using $HOME + tools path causes problems Change By: Christopher Orr (12/Mar/15 9:15 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-24817) Android emulator timeout during launch for 4.4 emulators
Christopher Orr closed JENKINS-24817 as Duplicate Android emulator timeout during launch for 4.4 emulators Change By: Christopher Orr (12/Mar/15 9:15 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Markus commented on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. We're also seeing this problem after upgrading to 2.5. Had to downgrade to 2.4.5. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-25790) New adb connect command always fails to connect emulator on OS X
Christopher Orr closed JENKINS-25790 as Duplicate New adb connect command always fails to connect emulator on OS X Version 2.13 of the plugin has been released, which helps mitigate the problems seen in JENKINS-11952. Change By: Christopher Orr (12/Mar/15 9:17 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26914) Can't use prefixed ABIs
Christopher Orr closed JENKINS-26914 as Duplicate Can't use prefixed ABIs Version 2.13 of the plugin has been released, which includes fixes for the mentioned issues. Change By: Christopher Orr (12/Mar/15 9:16 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26159) Emulator won't start when using android-20 API
Christopher Orr closed JENKINS-26159 as Duplicate Emulator won't start when using android-20 API Version 2.13 of the plugin has been released, which includes fixes for the mentioned issues. Change By: Christopher Orr (12/Mar/15 9:16 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-24736) Android emulator plugin does not use all available executors on a slave
Christopher Orr closed JENKINS-24736 as Not A Defect Android emulator plugin does not use all available executors on a slave Change By: Christopher Orr (12/Mar/15 9:19 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-13643) Allow AVD startup timeout to be configurable
Christopher Orr closed JENKINS-13643 as Won't Fix Allow AVD startup timeout to be configurable The timeout has been increased many times over the years, and it's automatically doubled for clean startups. Change By: Christopher Orr (12/Mar/15 9:23 AM) Status: Open Closed 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] [android-emulator-plugin] (JENKINS-11612) Add option to stop blocking for the emulator to start
Christopher Orr closed JENKINS-11612 as Won't Fix Add option to stop blocking for the emulator to start This would be complex to implement, and emulators are a lot faster nowadays than they were in 2011. Change By: Christopher Orr (12/Mar/15 9:21 AM) Status: Open Closed 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] [android-emulator-plugin] (JENKINS-20549) Unable to Start Android Emulator via Jenkins
Christopher Orr closed JENKINS-20549 as Incomplete Unable to Start Android Emulator via Jenkins Change By: Christopher Orr (12/Mar/15 9:25 AM) Status: Open Closed Resolution: Incomplete 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] [android-emulator-plugin] (JENKINS-15379) Emulator plugin occasionally hangs
Christopher Orr closed JENKINS-15379 as Fixed Emulator plugin occasionally hangs This shouldn't hang as of version 2.13. Change By: Christopher Orr (12/Mar/15 9:26 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.
[JIRA] [android-emulator-plugin] (JENKINS-23114) Emulators created by Jenkins fail to start: unknown skin name
Christopher Orr commented on JENKINS-23114 Emulators created by Jenkins fail to start: unknown skin name Is this still an issue in Jenkins with the latest SDK and build/platform tools? 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] [android-emulator-plugin] (JENKINS-25229) Update of sdk and build-tools for android-21 fails
Christopher Orr closed JENKINS-25229 as Duplicate Update of sdk and build-tools for android-21 fails Duplicates JENKINS-14100. Change By: Christopher Orr (12/Mar/15 9:28 AM) Status: Open Closed 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] [android-emulator-plugin] (JENKINS-11231) Overview screen to manage/delete/create emulators across build slaves
Christopher Orr closed JENKINS-11231 as Postponed Overview screen to manage/delete/create emulators across build slaves Change By: Christopher Orr (12/Mar/15 9:29 AM) Status: Open Closed Resolution: Postponed 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] [mansion-cloud-plugin] (JENKINS-27380) Registration banner not rendered properly on Jenkins page
Cyrille Le Clerc created JENKINS-27380 Registration banner not rendered properly on Jenkins page Issue Type: Bug Assignee: Unassigned Attachments: mansion-clud-plugin-truncated-banner.png Components: mansion-cloud-plugin Created: 12/Mar/15 9:35 AM Description: The green CloudBees registration banner is truncated. The workaround is to use the registration tile on the bottom left of the screen Environment: MacOSX 10.10.2 Firefox 36.0.1, Safari 8.0.3 (10600.3.18), Chrome 41.0.2272.76 Jenkins ver. 1.580.12.2 (Jenkins Enterprise by CloudBees 14.11) Project: Jenkins Priority: Minor Reporter: Cyrille Le Clerc 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-27353) Matrix Job: Build Cause is always UpstreamCause
Sverre Moe
updated JENKINS-27353
Matrix Job: Build Cause is always UpstreamCause
Change By:
Sverre Moe
(12/Mar/15 9:38 AM)
Summary:
Downstream projects get same build cause as its upstream project
Matrix Job: Build Cause is always UpstreamCause
Description:
When a downstream
project
multi-configuration job
is triggered
it gets
by an upstream multi-configuration job,
the
same
build cause
as its upstream project
is always UpstreamCause
.
If upstream project ProjectA
When also a Multi-configuration job
is triggered
manually
alone,
by a
user
User or SCM
,
then
the
downstream project ProjectB gets the same
build cause
is still UpstreamCause
.
In effect there
There
is no way to find out if
ProjectB
a downstream job
was triggered from an upstream
project
job, since each matrix configurations is always upstream from its parent
.From hudson.model.AbstractBuild:
For Multi-Configuration jobs then
build.getCauses() will always yield
a
hudson.model.Cause.UpstreamCause
Cause.toString() will always contain the original build cause from the upstream project.Cause.getClass() will always be Cause.UpstreamCauseCause.getShortDescription() will Probably because each matrix configuration is a downstream build from its upstream parent.Reproduce:Create 2 Free-style projects ProjectA and ProjectBCreate 2 Multi-conf projects ProjectC and ProjectDAdd Groovy Postbuild with this script{code}manager.build.getCauses().each { cause ->manager.listener.logger.println(cause.getClass())manager.listener.logger.println(cause.toString())manager.listener.logger.println(cause.getShortDescription())}{code}
It works for a Free-style project, but its wrong
build
cause in a Multi-Configuration Job.Free-style Jobs:ProjectA
cause.toString() ==
1 class
hudson.model.Cause$UserIdCause
@caebc9aa
cause.getClass() == class
2
hudson.model.Cause$UserIdCause
@caebc9aa
3 Started by user Sverre Moe
ProjectB
cause
1 class hudson
.
toString() ==
model.Cause$UpstreamCause2
job/
projectA
ProjectA
/
1
2
[hudson.model.Cause$UserIdCause@
2efba933
caebc9aa
]
cause.getClass() ==
3 Started by upstream project "ProjectA" build number 2Only running ProjectB1
class hudson.model.Cause$
UpstreamCause
UserIdCause
2 hudson.model.Cause$UserIdCause@caebc9aa
3 Started by user Sverre Moe
Multi-configuration Jobs:
ProjectA
ProjectC
cause
1 class hudson
.
toString() ==
model.Cause$UpstreamCause2 job/ProjectC/1[
hudson.model.Cause$UserIdCause@caebc9aa
]
cause.getClass() ==
3 Started by upstream project "ProjectC" build number 1ProjectD1
class hudson.model.Cause$
UserIdCause
UpstreamCause
ProjectBcause.toString() ==
2
job/
projectA
ProjectD
/1[
job/ProjectC/1[
hudson.model.Cause$UserIdCause@
2efba933
caebc9aa
]
]
cause.getClass() ==
3 Started by upstream project "ProjectD" build number 1Only running ProjectD:1
class hudson.model.Cause$
UpstreamCause2 job/ProjectD/2[hudson.model.Cause$
UserIdCause
@caebc9aa]3 Started by upstream project "ProjectD" build number 2The only way to find out if a project was triggered from an upstream project would be to parse toString(), find if it has a nested job.job/ProjectD/1[job/ProjectC/ == UpstreamCausejob/ProjectD/ != UpstreamCause
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-27256) Jenkins Remote API - Queue behavior changed
Morgwai Kotarbinski commented on JENKINS-27256 Jenkins Remote API - Queue behavior changed This bug has just broken all CI infrastructure at my organization and we had to downgrade to 1.600. Some more investigation: quiet period is NOT ignored and the item actually does await in the queue until the quiet period expires during the quiet period queue api (JENKINS_URL/queue/api/json) does show an item in it, but any attempt to access item's api (JENKINS_URL/queue/item/ITEM_ID/api/json), even while the item is in the quiet period results in 404 after the quiet period expires any attempt to access item's api also results in 404, although it should be accessible for 5 more minutes: https://issues.jenkins-ci.org/browse/JENKINS-26228?focusedCommentId=218310#comment-218310 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] [cli] (JENKINS-22346) CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean
SCM/JIRA link daemon commented on JENKINS-22346 CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/model/User.java http://jenkins-ci.org/commit/jenkins/80e9f3f50c3425c9b9b2bfdb58b03a1f1bd10aa3 Log: [FIXED JENKINS-22346] The original motivation for the fix (to prevent users from logging in once he's removed from the backend identity database) is legitimate, but it affected too many users. So as an escape hatch / non-promoted feature switch, I'm adding this option to bring back the old behaviour. 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] [cli] (JENKINS-22346) CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean
SCM/JIRA link daemon resolved JENKINS-22346 as Fixed CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean Change By: SCM/JIRA link daemon (12/Mar/15 9:40 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27336) Jenkins not saving configuration
Jay Kah commented on JENKINS-27336 Jenkins not saving configuration Thanks Daniel. Any suggestions on how to fix it? 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-27353) Matrix Job: Build Cause is always UpstreamCause
Sverre Moe commented on JENKINS-27353 Matrix Job: Build Cause is always UpstreamCause I had to rewrite this issue. It was a little disambiguous. The UI show the same as Cause.getShortDescription() and nested causes in causes.toString(). For each matrix build configurations it will always show "Started by upstream project". The Multi-configuration project ProjectD will show under each its configurations: Started by upstream project "ProjectD" originally caused by: Started by user Sverre Moe While parent will show: Started by user Sverre Moe 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-27256) Jenkins Remote API - Queue behavior changed
Morgwai Kotarbinski commented on JENKINS-27256 Jenkins Remote API - Queue behavior changed As I understand https://github.com/jenkinsci/jenkins/pull/1566/ does not solve https://issues.jenkins-ci.org/browse/JENKINS-26445 yet, so could we please revert it until it's fixed in a way not to break queue api? 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] [delivery-pipeline-plugin] (JENKINS-27270) Support jobs organized under folders
Patrik Boström commented on JENKINS-27270 Support jobs organized under folders Unfortunately the regexp is only matched against the project name and not against the full name including the foldername. I guess it is possible to fix the bug by matching against the full name. 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-27370) IntegritySCM checkout failure due to the java.sql.SQLException: Java exception: ': java.lang.NullPointerException
Cletus D'Souza commented on JENKINS-27370 IntegritySCM checkout failure due to the java.sql.SQLException: Java exception: ': java.lang.NullPointerException Is your Jenkins filesystem local to the server or on a network share? 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-27061) Strange exceptions whern performaing "si" in plugin 1.31
Grigoriy Milman commented on JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 There is at least one error present but a different one - - see JENKINS-27370. That error is related to particular new build job. Another build job was created about at the same time and workes fine! 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-27061) Strange exceptions whern performaing "si" in plugin 1.31
Cletus D'Souza commented on JENKINS-27061 Strange exceptions whern performaing "si" in plugin 1.31 Ok, in that case, I will close this issue and continue to track the new 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] [integrity-plugin] (JENKINS-27370) IntegritySCM checkout failure due to the java.sql.SQLException: Java exception: ': java.lang.NullPointerException
Grigoriy Milman commented on JENKINS-27370 IntegritySCM checkout failure due to the java.sql.SQLException: Java exception: ': java.lang.NullPointerException 1. Our Jenkins filesystem is local to the server. 2. That error is related to this/such particular new build job. Another build job was created about at the same time and work fine! Question, this PTC project has space character in the middle: /repository/TDE/QARI/Capacitor Test/Tantalum Capacitors/5160209/project.pj Is it 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] [maven-plugin] (JENKINS-27372) Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
Charles Chan
updated JENKINS-27372
Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
Change By:
Charles Chan
(11/Mar/15 8:17 PM)
Description:
We have a Maven project using the maven-source-plugin. When building theproject on Jenkins, it shows the following warning:
{noformat}
[INFO] *--- maven-jar-plugin:2.4:jar (default-jar) @ test-project ---*[INFO] Building jar:/home/jenkins/workspace/test-project/target/test-project-1.0.0-SNAPSHOT.jar[WARNING]Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
{noformat}
I tested with maven-source-plugin 2.2.1, 2.3, and 2.4 and all of theseversions exhibit the same problem. The problem does not appear if the project was compiled from NetBeans or command line.(Initially, I thought this was a Maven issue, therefore I started a thread at the Maven user's mailing list:http://maven-users.markmail.org/thread/jd74vnjnzfoef55e#query:+page:1+mid:no3jnbfgji2x63wj+state:results)
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-27353) Matrix Job: Build Cause is always UpstreamCause
Sverre Moe edited a comment on JENKINS-27353 Matrix Job: Build Cause is always UpstreamCause I had to rewrite this issue. It was a little disambiguous. The UI show the same as Cause.getShortDescription() and nested causes in causes.toString(). For each matrix build configurations it will always show "Started by upstream project". The problem is it will show UpstreamCause always even if triggered by User or SCM. The Multi-configuration project ProjectD will show under each its configurations: Started by upstream project "ProjectD" originally caused by: Started by user Sverre Moe While parent will show: Started by user Sverre Moe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle-plugin] (JENKINS-17287) Provide support for ScalaStyle warnings
Jan Goyvaerts commented on JENKINS-17287 Provide support for ScalaStyle warnings Let's try with Dick Wall's Subcut project: https://github.com/dickwall/subcut (1) Make- and change to a directory. (2) Run 'git clone https://github.com/dickwall/subcut.git'. (3) Replace pom.xml with the one provided. (There's an error in the scalatest dependency + added scalastyle) (4) Run 'mvn scalastyle:check' (5) Check the output file 'scalastyle-output.xml' I'm including the output file so you can check right now this is what you need. Is it ? 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] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
Thomas Müller commented on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds I have not seen this issue anymore since we upgraded to 1.600 - many 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] [checkstyle-plugin] (JENKINS-17287) Provide support for ScalaStyle warnings
Jan Goyvaerts updated JENKINS-17287 Provide support for ScalaStyle warnings Fixed pom.xml file + output of scalastyle:check. Change By: Jan Goyvaerts (12/Mar/15 9:56 AM) Attachment: pom.xml Attachment: scalastyle-output.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fingerprint-plugin] (JENKINS-19066) Do not spawn multiple files for fingerprints
Daniel Beck commented on JENKINS-19066 Do not spawn multiple files for fingerprints There's an option to fingerprint archived artifacts in the Advanced section of the post build step. 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-27353) Matrix Job: Build Cause is always UpstreamCause
Sverre Moe edited a comment on JENKINS-27353 Matrix Job: Build Cause is always UpstreamCause I had to rewrite this issue. It was a little disambiguous. The UI show the same as Cause.getShortDescription() and nested causes in causes.toString(). For each matrix build configurations it will always show "Started by upstream project". The problem is it will show UpstreamCause always even if triggered by User or SCM. The Multi-configuration project ProjectD will show under each its configurations: Started by upstream project "ProjectD" originally caused by: Started by user Sverre Moe While parent will show: Started by user Sverre Moe It would be a little more helpful if AbstractBuild.getCauses would list all nested causes in right order. Started by upstream project "ProjectD" build number 3 originally caused by: Started by upstream project "ProjectC" build number 2 originally caused by: Started by user Sverre Moe 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-27353) Matrix Job: Build Cause is always UpstreamCause
Sverre Moe edited a comment on JENKINS-27353 Matrix Job: Build Cause is always UpstreamCause I had to rewrite this issue. It was a little disambiguous. The UI show the same as Cause.getShortDescription() and nested causes in causes.toString(). For each matrix build configurations it will always show "Started by upstream project". The problem is it will show UpstreamCause always even if triggered by User or SCM. The Multi-configuration project ProjectD will show under each its configurations: Started by upstream project "ProjectD" originally caused by: Started by user Sverre Moe While parent will show: Started by user Sverre Moe It would be a little more helpful if AbstractBuild.getCauses would list all nested causes and in right order. Started by upstream project "ProjectD" build number 3 originally caused by: Started by upstream project "ProjectC" build number 2 originally caused by: Started by user Sverre Moe 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-27256) Jenkins Remote API - Queue behavior changed
Morgwai Kotarbinski commented on JENKINS-27256 Jenkins Remote API - Queue behavior changed @Daniel: WOW, many many thanks for this! I will try it later today. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-publisher-plugin] (JENKINS-27381) Last Success/Failure/Duration shows "N/A" on published instance
Jens Brejner created JENKINS-27381 Last Success/Failure/Duration shows "N/A" on published instance Issue Type: Bug Assignee: vjuranek Components: build-publisher-plugin Created: 12/Mar/15 10:13 AM Description: On the receiving master the values for "Last Success","Last Failure","Last Duration" on any views page shows "N/A". Could be related to: JENKINS-17239 JENKINS-18105 Environment: Jenkins 1.601. Sending master on ubuntu, receiving master runs on Windows. Latest version of the plugin Project: Jenkins Priority: Minor Reporter: Jens Brejner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-publisher-plugin] (JENKINS-27381) Last Success/Failure/Duration shows "N/A" on published instance
Jens Brejner updated JENKINS-27381 Last Success/Failure/Duration shows "N/A" on published instance If you send me a snapshot version I will be happy to help testing the fix. Change By: Jens Brejner (12/Mar/15 10:15 AM) Environment: Jenkins 1.601. Sending master on ubuntu, receiving master runs on Windows. Latest version of the plugin . The masters are in different timezones. 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] [envinject-plugin] (JENKINS-27382) EnvInject plugin passes astrisk to Gradle plugin
Marcus Collins
created JENKINS-27382
EnvInject plugin passes astrisk to Gradle plugin
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
envinject-plugin, gradle-plugin
Created:
12/Mar/15 10:19 AM
Description:
I created a local and global password.
In a shell step the password can be used successfully.
In the next build step of my build I have the Gradle plugin, the password arrives as asterisks.
As a work-around I have switched to use the MaskPassword plugin.
Test Script build.gradle:
task showGlobalEnv << {
println '\''Test match:'\'' + (System.env.TEST_ENV == 'T123')
System.env.TEST_ENV.each{ println it }
}
Output from version 1.90 (successful):
Test match:true
T
1
2
3
Output from version 1.91 (failure):
Test match:false
*
*
*
*
*
*
*
*
Environment:
EnvInject version 1.91 and version 1.91.1
Project:
Jenkins
Priority:
Major
Reporter:
Marcus Collins
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-27383) NPE with Git Tag Message Plugin
Claudio B created JENKINS-27383 NPE with Git Tag Message Plugin Issue Type: Bug Assignee: Christopher Orr Components: git-plugin Created: 12/Mar/15 10:21 AM Description: Using the git tag message plugin I receive a NullPointerException: Checking out Revision 7f63eea9111ef89bb3c6b109a779430f9a7d800a (refs/remotes/origin/develop) > git config core.sparsecheckout # timeout=10 > git checkout -f 7f63eea9111ef89bb3c6b109a779430f9a7d800a > git rev-list 56152421d2b22ced24473646e131d1c63414089c # timeout=10 > git describe --tags 7f63eea9111ef89bb3c6b109a779430f9a7d800a # timeout=10 > git tag -l -n1 # timeout=10 FATAL: null java.lang.NullPointerException at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getTagMessage(CliGitAPIImpl.java:2261) at hudson.plugins.git.GitAPI.getTagMessage(GitAPI.java:108) at org.jenkinsci.plugins.gittagmessage.GitTagMessageExtension.onCheckoutCompleted(GitTagMessageExtension.java:56) at hudson.plugins.git.extensions.GitSCMExtension.onCheckoutCompleted(GitSCMExtension.java:161) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1047) at hudson.scm.SCM.checkout(SCM.java:484) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Note: There was no gti-tag-message-plugin component, so I attached this issue to the git-plugin but assigned the issue to orrc. Sorry for any grief this might cause, please re-assign without further ado. Environment: Jenkins 1.598 Git Tag Message Plugin 1.2 Project: Jenkins Labels: git git-tag-message-plugin Priority: Minor Reporter: Claudio B 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-27384) Jenkins uses 100% cpu seems related to process leak
Jorge Dias created JENKINS-27384 Jenkins uses 100% cpu seems related to process leak Issue Type: Bug Assignee: Nicolas De Loof Components: core, git-client-plugin Created: 12/Mar/15 10:32 AM Description: Hi, currently we have a problem with our jenkins instance where it becomes totally unresponsive after around 1-2 days. I've noticed that when it starts failing I see a lot of this errors on the logs: https://gist.github.com/diasjorge/5ccf8cb8a69180dc94e7 I haven't been able to point which build may be causing the problems. Any ideas or suggestions please? Project: Jenkins Priority: Minor Reporter: Jorge Dias 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-27311) 404 on actions such as "Add build step" and "Add post-build action"
Ivaylo Marinkov updated JENKINS-27311 404 on actions such as "Add build step" and "Add post-build action" Change By: Ivaylo Marinkov (12/Mar/15 10:31 AM) Attachment: org.kohsuke.stapler.Dispatcher-log.txt 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-27311) 404 on actions such as "Add build step" and "Add post-build action"
Ivaylo Marinkov commented on JENKINS-27311 404 on actions such as "Add build step" and "Add post-build action" I added the header and am attaching the contents of the log. I can see the response now contains two new headers, Stapler-Trace-001 -> evaluate( :org.kohsuke.stapler.bind.BoundObjectTable,"/3dcbdb6b-087f-450b-988b-b6f97a7eb477/render") Stapler-Trace-002 -> evaluate(((StaplerFallback)).getStaplerFallback(),"/3dcbdb6b-087f-450b-988b-b6f97a7eb477/render") Doesn't seem to give hints on the 404 though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-27358) Unable to find a build for artifact copy when parameters tag is empty
Michal Kovarik edited a comment on JENKINS-27358 Unable to find a build for artifact copy when parameters tag is empty There is no parameters tag when the job is created manually. This issue does not occur when not using JJB. Jenkins job builder wasn't changed, so it's regression in Copy artifact 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.
