[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 OK, if that's the way it is supposed to work, then fine. I deleted the workspace and your upgraded plugin worked perfectly, creating a version 1.8 checkout. So that's quite enough for me to use it in production. 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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
davida2009 created JENKINS-25535 Exception if email trigger enabled but no recipient specified Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 11/Nov/14 8:40 AM Description: If a job succeeds, and the email 'Success' trigger is enabled, but no recipients are specified for it, we see an exception in the system log: Nov 11, 2014 6:01:51 AM WARNING hudson.plugins.emailext.ExtendedEmailPublisher sendMail Could not send email. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:515) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:290) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:281) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:233) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1805) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: Jenkins 1.588 Email Ext plugin 2.38.2 Project: Jenkins Priority: Minor Reporter: davida2009 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] [configurationslicing-plugin] (JENKINS-25536) Adding some parameters
Hagen Seifert created JENKINS-25536 Adding some parameters Issue Type: Improvement Assignee: mdonohue Components: configurationslicing-plugin Created: 11/Nov/14 8:50 AM Description: It would be great to have some more configuration parameters in the slicing plugin: Block build when upstream project is building Block build when downstream project is building Subversion: Credentials Subversion: Ignore externals Subversion: Check-out Strategy Add timestamp to console output Project: Jenkins Priority: Minor Reporter: Hagen Seifert 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Oleg Nenashev edited a comment on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Related to JENKINS-25372, which has been caused by https://github.com/jenkinsci/jenkins/pull/1414. There were new fixes in 1.589. Have you seen the issue on the previous versions? (it would be great to know this version) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25372) No nodes under Restrict nodes
Oleg Nenashev updated JENKINS-25372 No nodes under Restrict nodes Change By: Oleg Nenashev (11/Nov/14 8:53 AM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm-plugin] (JENKINS-25342) Project templates should be parsed on the executing node (case 12207)
Mads Nielsen updated JENKINS-25342 Project templates should be parsed on the executing node (case 12207) Change By: Mads Nielsen (11/Nov/14 9:06 AM) Summary: Projecttemplatesshouldbeparsedontheexecutingnode (case12207) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm-plugin] (JENKINS-25342) Project templates should be parsed on the executing node (case 12207)
Mads Nielsen resolved JENKINS-25342 as Fixed Project templates should be parsed on the executing node (case 12207) Change By: Mads Nielsen (11/Nov/14 9:10 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] [ghprb-plugin] (JENKINS-22253) Problems Parsing
Kanstantsin Shautsou
commented on JENKINS-22253
Problems Parsing
GitHub pull request #2043 of commit ef734b7d25172541d671f1ab5c032a2f8a0caa2b automatically merged.
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Injecting as environment variables the properties content
[EnvInject] - Variables injected successfully.
[EnvInject] - Injecting contributions.
Building remotely on Node1 in workspace /var/lib/jenkins/workspace/PR-builder
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository g...@github.com:project/repo.git
git init /var/lib/jenkins/workspace/PR-builder # timeout=10
Fetching upstream changes from g...@github.com:project/repo.git
git --version # timeout=10
git fetch --tags --progress g...@github.com:project/repo.git +refs/heads/*:refs/remotes/origin/*
git config remote.origin.url g...@github.com:project/repo.git # timeout=10
git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
git config remote.origin.url g...@github.com:project/repo.git # timeout=10
Fetching upstream changes from g...@github.com:project/repo.git
git fetch --tags --progress g...@github.com:project/repo.git +refs/pull/*:refs/remotes/origin/pr/*
git rev-parse origin/pr/2043/merge^{commit} # timeout=10
FATAL: Command "git rev-parse origin/pr/2043/merge^{commit}" returned status code 128:
stdout: origin/pr/2043/merge^{commit}
stderr: fatal: ambiguous argument 'origin/pr/2043/merge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
hudson.plugins.git.GitException: Command "git rev-parse origin/pr/2043/merge^{commit}" returned status code 128:
stdout: origin/pr/2043/merge^{commit}
stderr: fatal: ambiguous argument 'origin/pr/2043/merge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1435)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1411)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1407)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1110)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1120)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:516)
at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257)
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:310)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
GitHub Pull Request Builder 1.16-5
GitHub plugin 1.9.1
GIT plugin 2.2.7
Jenkins GIT client plugin 1.11.0
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] [ghprb-plugin] (JENKINS-22253) Problems Parsing
Kanstantsin Shautsou
edited a comment on JENKINS-22253
Problems Parsing
GitHub pull request #2043 of commit ef734b7d25172541d671f1ab5c032a2f8a0caa2b automatically merged.
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Injecting as environment variables the properties content
[EnvInject] - Variables injected successfully.
[EnvInject] - Injecting contributions.
Building remotely on Node1 in workspace /var/lib/jenkins/workspace/PR-builder
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository g...@github.com:project/repo.git
git init /var/lib/jenkins/workspace/PR-builder # timeout=10
Fetching upstream changes from g...@github.com:project/repo.git
git --version # timeout=10
git fetch --tags --progress g...@github.com:project/repo.git +refs/heads/*:refs/remotes/origin/*
git config remote.origin.url g...@github.com:project/repo.git # timeout=10
git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
git config remote.origin.url g...@github.com:project/repo.git # timeout=10
Fetching upstream changes from g...@github.com:project/repo.git
git fetch --tags --progress g...@github.com:project/repo.git +refs/pull/*:refs/remotes/origin/pr/*
git rev-parse origin/pr/2043/merge^{commit} # timeout=10
FATAL: Command "git rev-parse origin/pr/2043/merge^{commit}" returned status code 128:
stdout: origin/pr/2043/merge^{commit}
stderr: fatal: ambiguous argument 'origin/pr/2043/merge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
hudson.plugins.git.GitException: Command "git rev-parse origin/pr/2043/merge^{commit}" returned status code 128:
stdout: origin/pr/2043/merge^{commit}
stderr: fatal: ambiguous argument 'origin/pr/2043/merge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1435)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1411)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1407)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1110)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1120)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:516)
at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257)
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:310)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
GitHub Pull Request Builder 1.16-5
GitHub plugin 1.9.1
GIT plugin 2.2.7
Jenkins GIT client plugin 1.11.0
Can this issue be caused because of closed/merged PR?
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
[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
podskalsky commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration I've updated from Jenkins ver. 1.585 to 1.589 - before this update everything was 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] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
podskalsky updated JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Change By: podskalsky (11/Nov/14 9:44 AM) Environment: Jenkinsver.1.589LatestPluginsSolaris10Firefox+Chrome MavenBuildJob 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
podskalsky updated JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Change By: podskalsky (11/Nov/14 9:44 AM) Attachment: 2014-11-1110_42_32-TicTacToe_Maven_externalConfig[Jenkins].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] [pretested-integration-plugin] (JENKINS-25069) Plugin does not work with stash-git-hook
Per Arnold Blaasmo edited a comment on JENKINS-25069 Plugin does not work with stash-git-hook Can you please add a description on this 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] [pretested-integration-plugin] (JENKINS-25069) Plugin does not work with stash-git-hook
Per Arnold Blaasmo commented on JENKINS-25069 Plugin does not work with stash-git-hook Can you please add a description om this 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] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
podskalsky updated JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Change By: podskalsky (11/Nov/14 9:44 AM) Environment: Jenkinsver.1.589LatestPluginsSolaris10 Firefox+Chrome 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-25364) Unable to update workspace error
Paul Allen closed JENKINS-25364 as Cannot Reproduce Unable to update workspace error Change By: Paul Allen (11/Nov/14 9:46 AM) Status: Open Closed Resolution: CannotReproduce 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-25300) Several of my p4 projects do not list *any* changes between builds
Paul Allen closed JENKINS-25300 as Fixed Several of my p4 projects do not list *any* changes between builds Core issue fixed in 1.0.17 (minor fixes to be released in 1.0.18) Change By: Paul Allen (11/Nov/14 9:49 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] [pretested-integration-plugin] (JENKINS-25069) Plugin does not work with stash-git-hook
Per Arnold Blaasmo commented on JENKINS-25069 Plugin does not work with stash-git-hook We use the Stash Jenkins Webhook v2.6.0. That has a check box for not using SHA1 when triggering Jenkins. That work for us and Jenkins will trigger a build that the pretested plugin handles OK. There is a Jenkins Issue (JENKINS-24133) for the Git-plugin about handling triggers where SHA1 is used and to find the branch name. Until that us solved I suggest using v2.6.0 of the Stash Jenkins Webhook and check for not using SHA1. 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] [pretested-integration-plugin] (JENKINS-25069) Plugin does not work with stash-git-hook
Mads Nielsen updated JENKINS-25069 Plugin does not work with stash-git-hook Change By: Mads Nielsen (11/Nov/14 9:59 AM) Description: Theplugindoesnotworkwiththedefaultsettingswithversion2.6.0oftheStashJenkinsWebhook2.6.0.https://marketplace.atlassian.com/plugins/com.nerdwin15.stash-stash-webhook-jenkinsWhenyouwanttousethestashpluginbesuretocheckthecheckboxtonotuseSHA1whentriggeringjenkins. 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-25537) REST api provides incomplete information
Morne Joubert
created JENKINS-25537
REST api provides incomplete information
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
11/Nov/14 10:06 AM
Description:
Hi,
I use the REST api's (json and XML) to process our Jenkins builds.
The normal perforce plugin provides the following information in the changeSet list.
"changeSet" : {
"items" : [
{
"affectedPaths" : [
"ma_tools/bin/stream_tester/cmd_stream_tester.exe",
"ma_tools/bin/stream_tester/jenkins.dll",
"ma_tools/bin/stream_tester/stream_tester.exe",
"ma_tools/metrics/REST.py",
"ma_tools/metrics/stat_upload.py"
],
"author" : {
"absoluteUrl" : "http://jenkins.gb-mlb.u-blox.net:8080/user/mjou",
"fullName" : "mjou"
},
"commitId" : null,
"msg" : "Copying //MA_SW/ci_tools to tools (//MA_SW/tools)",
"timestamp" : -1,
"changeNumber" : "71891",
"changeTime" : "2014-11-10 17:54:01"
},
When i do the same REST calls on jobs using the p4 plugin some very important fields are missing.
"changeSet" : {
"items" : [
{
"affectedPaths" : null,
"author" : {
"absoluteUrl" : "http://jenkins.gb-mlb.u-blox.net:8080/user/mjou",
"fullName" : "mjou"
},
"commitId" : null,
"msg" : "U_MA_TLS-194 : Add option to email stream owners\nU_MA_TLS-188: Add option to create workspace per job\nU_MA_TLS-182: Fix bug with running status after job has completed\n",
"timestamp" : -1
}
],
The important fields :
"changeNumber" : "71891",
"changeTime" : "2014-11-10 17:54:01"
are missing.
I have also noted that the affectedPaths is also null but this is of a lower priority than the changeNumber and changeTime.
Project:
Jenkins
Priority:
Critical
Reporter:
Morne Joubert
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-25523) Multiple SCMs Plugin doesn't work with Mercurial since 1.588
Sergey Grinev updated JENKINS-25523 Multiple SCMs Plugin doesnt work with Mercurial since 1.588 Increasing priority as issues can be easily reproduced on clean jenkins Clean experiment: download latests jenkins.war (1.589) add Mercurial plugin (1.51) it will install MultipleSCM as a dependency create job with 2 mercurial repositories run it and get exception Change By: Sergey Grinev (11/Nov/14 10:28 AM) Priority: Major Critical 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Del Hyman-Jones edited a comment on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed Does anyone know if there is an option to stop Jenkins from killing processes completely as a global option instead of having to add the BUILD_ID to every single job? I have tried adding this as an env variable at the node level but it doesn't appear to give the desired results (same PDB errors were still occurring), maybe I'm doing something wrong or misunderstanding how this is working under the hood? We were running CruiseControl for years and never had this problem but we did however have issues where processes were not terminating properly and builds would run forever until someone intervened. Sometimes we still get this with Jenkins so from my point of view one problem is better than two so I'd rather just have an option to tell Jenkins not to force terminate anything - ever. If this cannot be done with the current version (ours is 1.566) Can we at least add a check box that says "Do not auto-terminate processes" as an option in a future release and let the user decide? 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-25538) Add Phabricator as Repository Browser
Alexander Obuhovich updated JENKINS-25538 Add Phabricator as Repository Browser Change By: Alexander Obuhovich (11/Nov/14 10:46 AM) Issue Type: Bug Improvement 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-25538) Add Phabricator as Repository Browser
Alexander Obuhovich created JENKINS-25538 Add Phabricator as Repository Browser Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 11/Nov/14 10:45 AM Description: I know, that Git plugin supports Phabricator as Repository browser since 2013. Maybe same option can be added here? Project: Jenkins Priority: Minor Reporter: Alexander Obuhovich 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-25221) Content of Custom Workspace changes in v1.585
Moshe Zvi commented on JENKINS-25221 Content of Custom Workspace changes in v1.585 I'm on 1.588, and in a Maven project I don't see the custom workspace option at all... 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Dirk Kuypers commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration We updated from 1.588 and see this behaviour with the newest version. Downgrade will take another hour 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Oleg Nenashev commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Added Matthew Moore to Cc 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-18935) Make Subversion plugin support Subversion 1.8
Jason Spotswood commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I would recommend that almost all Jenkins job should delete the workspace at the start of the job. This prevents a plethora of issues, including the need to upgrade any files managed by SVN. 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-18935) Make Subversion plugin support Subversion 1.8
Shannon Kerr commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I humbly disagree, Jason, on the full delete. "Emulate clean checkout..." works perfectly for us. It deletes un-versioned files, deletes modified files, and then runs an svn update, which replaces the deleted modified files as well as updates all of the other repository elements. For us, this saves us a good 5 minutes as our repository is rather large. We typically build on 3 platforms (today serially), so this cuts 15 minutes from our build. I can't imagine what issues we might still be facing by using this option, but at least nothing has bitten us yet. That said, I has this plugin ever supported upgrading working copies from one version of Subversion to another? We've always been on 1.7, so it's a test I've never tried. If it hasn't supported this, then I wouldn't expect it to support it now. I think there is a plugin out there that will allow you to add a pre-svn activities step where you could first run the svn upgrade, but I could be wrong 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] [summary_report-plugin] (JENKINS-25466) Exception String index out of range in summary_report plugin
deruyter commented on JENKINS-25466 Exception String index out of range in summary_report plugin Hi, The release process failed. I work on it today to upload the latest version Regards 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-25372) No nodes under Restrict nodes
Alexandru Gheorghe commented on JENKINS-25372 No nodes under Restrict nodes Seems it went under: release v1.589 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure
Omar Ahmad commented on JENKINS-25392 Post Build Steps still running regardless of Pre Step Groovy Script failure Hi, Ok, I think we are both confused here. I will start with my confusions and then address yours. I am using Jenkins version 1.554.3. I am using Maven Project Plugin 2.5. When I create a maven project in Jenkins, the job has three sections. Pre steps, Main Build and Post Steps. If I add a maven invoking pre step and purposely make it fail, then the entire job stops at the pre step. However, if I add a "execute system groovy script" (which I believe is part of the groovy plugin) as a pre build step, and purposely cause that script to throw an exception, the build does not stop and causes subsequent post build steps to run. My initial thoughts were that this should be posted against the groovy plugin, however as I am writing this I can see that perhaps this should be posted against the maven project plugin. Are you saying the post build and pre build steps that are part of a maven project in Jenkins is part of Jenkins core functionality? If so I will update the component to this. Thank you and apologies for the requirement to clarify this. 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-25372) No nodes under Restrict nodes
Oleg Nenashev commented on JENKINS-25372 No nodes under Restrict nodes Just a notification Jenkins users... Please be aware about JENKINS-25533 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Shannon Kerr commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed How are you trying to run this, Del? At first, I didn't have success getting it going, but now I seem to have it working fine. The BUILD_ID does seem to be an effective solution (I do worry about the memory leak though). I'm using the simple batch solution in comment 6, not the python solution. You just have to make sure that the mspdbsrv file is in your path and it should work fine. We use a batch wrapper, which is under version control, for our builds and I added code that says "If this is a Jenkins build, execute this block". To decide if this if a Jenkins build, I just check to see if JENKINS_URL is defined. Since I added that, we've not seen this issue return. Let me know if I can help in some way. 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-18935) Make Subversion plugin support Subversion 1.8
aleksas commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I think Jason meant to delete workspace checked out using current 1.7 svn, and checkout a fresh one using v1.8. Afterwards "Emulate clean checkout" should work as it did before. 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-18935) Make Subversion plugin support Subversion 1.8
aleksas edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I think Jason meant to delete workspace checked out using current 1.7 (or any earlier) svn plugin, and checkout a fresh one using v1.8. Afterwards "Emulate clean checkout" should work as it did before. 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-18935) Make Subversion plugin support Subversion 1.8
aleksas edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I think Jason meant to delete workspace checked out using current 1.7 (or any earlier) svn plugin, and checkout a fresh copy using v1.8. Afterwards "Emulate clean checkout" should work as it did before. 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-18935) Make Subversion plugin support Subversion 1.8
Shannon Kerr commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Perhaps, but it is phrased in such a way that it sounds like this should be the proper wait to operate in general. My apologies if I'm still misreading 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-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure
vjuranek commented on JENKINS-25392 Post Build Steps still running regardless of Pre Step Groovy Script failure Hi, what I can do (I actually already did so, but will double check) is to verify that when exception is thrown (and is not caught) in the groovy script, groovy build step will return non-zero value from perform method. How this exit code is handled by other Jenkins parts (like maven plugin), cannot be effected by groovy plugin. However, I'll double check and confirm here, that groovy plugin return non-zero value from perform method when exception is thrown. 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] [cloudbees-folder-plugin] (JENKINS-25539) Folder plugin
Ulli Hafner created JENKINS-25539 Folder plugin Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder-plugin Created: 11/Nov/14 1:12 PM Description: I'm not sure if this is a bug or a new improvement: I have several folders with round about 100 jobs in each of them. My requirement is to reuse the same view to show the results of the jobs of every folder. So I tried to create a new top-level Jenkins view that defines the view columns to use. Then I added this view in every folder as new view using the + button and the option "Include a global view". However, when I select this view in a folder, then the listed jobs are all jobs that are visible in the top-level view. I think there should be at least an option to show only those jobs here that are part of the selected folder. Environment: 1.580.1, folders: 4.7 Project: Jenkins Priority: Minor Reporter: Ulli Hafner 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] [cloudbees-folder-plugin] (JENKINS-25539) Views in folders should show only jobs that are part of folder
Ulli Hafner updated JENKINS-25539 Views in folders should show only jobs that are part of folder Change By: Ulli Hafner (11/Nov/14 1:13 PM) Summary: Folderplugin Viewsinfoldersshouldshowonlyjobsthatarepartoffolder 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] [cloudbees-folder-plugin] (JENKINS-25539) Derived views in folders should show only jobs that are part of that folder
Ulli Hafner updated JENKINS-25539 Derived views in folders should show only jobs that are part of that folder Change By: Ulli Hafner (11/Nov/14 1:14 PM) Summary: Derivedviewsinfoldersshouldshowonlyjobsthatarepartof that folder 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] [nodelabelparameter-plugin] (JENKINS-24280) Environment variables get corrupted when using Node parameter
Jeff G commented on JENKINS-24280 Environment variables get corrupted when using Node parameter Also confirmed on Jenkins 1.580.1 with Env Inject 1.90. I cannot uninstall Env Inject to verify. The work around of running pinned to a node instead of using the Node Parameter plugin does work as expected. 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-25488) New UI wastes horizontal space
Adrian Robert
commented on JENKINS-25488
New UI wastes horizontal space
A partial work-around is to edit responsive-grid.css to make the following changes:
.col-sm-9 { width: 25%; }
.col-sm-15 { width: 70%; }
I no CSS expert but it seems like just putting percentages here is not enough to ensure a good experience. Perhaps putting a small percentage for the sidebar plus a minimum? Or using some kind of fixed em/ex measure and a max percentage?
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-18935) Make Subversion plugin support Subversion 1.8
Jason Spotswood commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I did mean that in most cases I would expect deletion of the workspace to be the norm. However we do our builds differently in the they do not take long to check out (i.e. we have hundreds of small builds that are only triggered when something changes). As well, when we had used the "Use svn update as much as possible" option, we found that it would often miss updating stuff that and then we wasted heaps of time trying to figure things out. I completely understand that for large checkouts, that deleting the workspace would have a high cost to it. That said, the "Emulate clean checkout..." option might be worth checking out as it sounds like a potential winner as long as it is stable. Of course I will only try that after I have upgraded the plugin to use 1.8. Thanks for sharing your comments. 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] [htmlpublisher-plugin] (JENKINS-25540) HTMLPublisher. Link to report isn't generated
Dmitry F updated JENKINS-25540 HTMLPublisher. Link to report isnt generated Change By: Dmitry F (11/Nov/14 1:35 PM) Description: HTMLPublisherrenderonlynameofHTMReport 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] [htmlpublisher-plugin] (JENKINS-25540) HTMLPublisher. Link to report isn't generated
Dmitry F created JENKINS-25540 HTMLPublisher. Link to report isnt generated Issue Type: Bug Assignee: mcrooney Attachments: broken_link.png, direct_link.png, log.png, settings.png Components: htmlpublisher-plugin Created: 11/Nov/14 1:33 PM Project: Jenkins Priority: Major Reporter: Dmitry F 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] [htmlpublisher-plugin] (JENKINS-25540) HTMLPublisher. Link to report isn't generated
Dmitry F updated JENKINS-25540 HTMLPublisher. Link to report isnt generated Change By: Dmitry F (11/Nov/14 1:40 PM) Description: Jenkins:1.589HTMLPublisher:1.3*HTMLPublisher*renderonlynameofHTMReport,see !broken_link.png |thumbnail ! butdirectlinkisworking !direct_link.png |thumbnail !reportwasgeneratedaswell !log.png |thumbnail ! settingsare correct !settings.png |thumbnail ! 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] [htmlpublisher-plugin] (JENKINS-25540) HTMLPublisher. Link to report isn't generated
Dmitry F updated JENKINS-25540 HTMLPublisher. Link to report isnt generated Change By: Dmitry F (11/Nov/14 1:39 PM) Description: Jenkins:1.589 HTMLPublisher :1.3*HTMLPublisher* renderonlynameofHTMReport ,see!broken_link.png|thumbnail!butdirectlinkisworking!direct_link.png|thumbnail!reportwasgeneratedaswell!log.png|thumbnail!settingsarecorrect!settings.png|thumbnail! 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-25541) Supports Dashboard View portlets
Victor Martinez created JENKINS-25541 Supports Dashboard View portlets Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 11/Nov/14 1:48 PM Description: It would be useful to extend this plugin in order to allow the connection to the Dashboard View plugin https://wiki.jenkins-ci.org/display/JENKINS/Dashboard+View An example of another plugin: https://github.com/jenkinsci/release-plugin/blob/master/src/main/java/hudson/plugins/release/dashboard/RecentReleasesPortlet.java Thanks Project: Jenkins Labels: supports-dashboard-view Priority: Minor Reporter: Victor Martinez 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] [pretested-integration-plugin] (JENKINS-25542) Git SHA is not translated to branch and checked accordingly
Bue Petersen created JENKINS-25542 Git SHA is not translated to branch and checked accordingly Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 11/Nov/14 2:08 PM Description: The Pretested Integration plugin uses 'Branch Specifier' from the Git plugin as source branch, and 'Integration branch' field in the Pretested Integration plugin as destination. When the integration job uses polling, the job only runs on branches that matches the "Branch Specifier", so only those are integrated. When job is started in another way, eg. by upstream job with at Git commit SHA passed, it may try to integrate other branches (the one the passed git commit SHA lives on). This is because the SHA is not translated to a branch, and that branch is checked against our criterias for running integration. Translate SHA to branch name, and check that the conditions for running is okay (these conditions are established already, or in other cases). Just implement translation. See also JENKINS-24909 Project: Jenkins Priority: Critical Reporter: Bue Petersen 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-25543) Animation broken in IE11
davida2009 created JENKINS-25543 Animation broken in IE11 Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Nov/14 2:11 PM Description: Running IE11 on Win 8.1, job ball does not flash and job progress bar (red, moving diagonal stripe) does not animate. Icons behave correctly in Chrome. Environment: Jenkins 1.588 IE11 Project: Jenkins Priority: Minor Reporter: davida2009 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] [sauce-ondemand-plugin] (JENKINS-25411) With latest updates, sauce-ondemand no longer works; gives an error
Andrei Costescu commented on JENKINS-25411 With latest updates, sauce-ondemand no longer works; gives an error Update: the same thing happened, it runs once then that 0 byte file re-appears magically. And the second time the job runs the exception is back. I added for now a job that just deletes that file after the main job runs for now as a workaround. 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] [pretested-integration-plugin] (JENKINS-25544) Default repository name (origin) must work with git scm and multi SCMs git
Bue Petersen created JENKINS-25544 Default repository name (origin) must work with git scm and multi SCMs git Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 11/Nov/14 2:33 PM Description: JENKINS-24754 implemented support for Multi SCMs plugin, but still working with git, and support for using several git repositories with the normal git plugin. Repositories are default named `origin`, `origin1` and the pretested plugin needs configuration for integration branch (eg. `master`) and a named repository (eg. `origin`). Default configuration is `master` and `origin`, thus using several git repositories and forgetting to chose names should work. It will just asume it is the first repository (which the git plugin names `origin` by default). This is to not break all builds upon updating to next release (that is soon to be). The choice is also made, as it is the current situation. Project: Jenkins Priority: Major Reporter: Bue Petersen 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] [cloudformation-plugin] (JENKINS-12851) Create builder so a CF stack can be created as a build step.
edovale resolved JENKINS-12851 as Fixed Create builder so a CF stack can be created as a build step. Change By: edovale (11/Nov/14 2:38 PM) Status: InProgress 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Del Hyman-Jones edited a comment on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed I've added the block from above into the Jenkins command for the job at the moment but yesterday I got this error and there was only one build running so it is likely a different issue. 33X509Helper.h(118): fatal error C1090: PDB API call failed, error code '23' : '( I've even tried setting BUILD_ID=dontKillMe under the node configuration in Environment variables but I have been getting the original problem with that setting also. I even tried restarting the jenkins client service on the build server just in case it was needed for the env variable to be set for all child processes but it's not helping it seems. If this is working for yourself (@Shannon) I have to be doing something stupid. It seems that putting BUILD_ID under the node settings will be overridden when the build runds and will set BUILD_ID back to the build time. 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Del Hyman-Jones edited a comment on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed I've added the block from above into the Jenkins command for the job at the moment but yesterday I got this error and there was only one build running so it is likely a different issue. 33X509Helper.h(118): fatal error C1090: PDB API call failed, error code '23' : '( I've even tried setting BUILD_ID=dontKillMe under the node configuration in Environment variables but I have been getting the original problem with that setting also. I even tried restarting the jenkins client service on the build server just in case it was needed for the env variable to be set for all child processes but it's not helping it seems. If this is working for yourself (@Shannon) I have to be doing something stupid. It seems that putting BUILD_ID under the node settings will be overridden when the build runds and will set BUILD_ID back to the build time. Which rules out having a global setting allowing me to turn this off. 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Del Hyman-Jones commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed I've added the block from above into the Jenkins command for the job at the moment but yesterday I got this error and there was only one build running so it is likely a different issue. 33X509Helper.h(118): fatal error C1090: PDB API call failed, error code '23' : '( I've even tried setting BUILD_ID=dontKillMe under the node configuration in Environment variables but I have been getting the original problem with that setting also. I even tried restarting the jenkins client service on the build server just in case it was needed for the env variable to be set for all child processes but it's not helping it seems. If this is working for yourself (@Shannon) I have to be doing something stupid. In fact as of writing this I think I have just proved that setting env vars under node properties just does not work. running SET as the command shows that any variables set there do not appear for the build to use and BUILD_ID is still set to a date and time. restarting the Jenkins client service does nothing either! Also the Env plugin says the same thing as set and those variables just aren't being set as expected. 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] [pretested-integration-plugin] (JENKINS-25545) Multiple git repository names are not check and repositories risk be merged
Bue Petersen
created JENKINS-25545
Multiple git repository names are not check and repositories risk be merged
Issue Type:
Bug
Assignee:
Praqma Support
Components:
pretested-integration-plugin
Created:
11/Nov/14 2:45 PM
Description:
With multiple git repositories, the post-build step is not using them correctly and several situations have been seen where one repo is tried to be integrated into another and pushed.
This mixes up repositories and is fatal for the plugin.
Reproduce:
using git scm plugin (not multiscm)
configure it to two repositories
repo1, explicitly named origin in the git scm configuration
repo2, explicitly not named in the git scm configuration
branch specifier that triggers on both repos if they change
pretested integration configuration: master + origin
both repo must be able to checkout into same folder, without filename clashes (this is not normal wanted behavior, but it doesn't matter for this test)
make a commit on a ready branch in {{repo2}, with a new file that doesn't exist in either of the repo
Result: **The file get integrated into origin (repo1) instead of of not at all.
Environment:
2.2.0-snapshot build
Project:
Jenkins
Priority:
Blocker
Reporter:
Bue Petersen
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] [pretested-integration-plugin] (JENKINS-25542) Git SHA is not translated to branch and checked accordingly (our case 12284)
Bue Petersen updated JENKINS-25542 Git SHA is not translated to branch and checked accordingly (our case 12284) Change By: Bue Petersen (11/Nov/14 2:48 PM) Summary: GitSHAisnottranslatedtobranchandcheckedaccordingly (ourcase12284) 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] [pretested-integration-plugin] (JENKINS-25544) Default repository name (origin) must work with git scm and multi SCMs git (our case 12285)
Bue Petersen updated JENKINS-25544 Default repository name (origin) must work with git scm and multi SCMs git (our case 12285) Change By: Bue Petersen (11/Nov/14 2:47 PM) Summary: Defaultrepositoryname(origin)mustworkwithgitscmandmultiSCMsgit (ourcase12285) Environment: 2.2.0-snapshotbuild 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] [pretested-integration-plugin] (JENKINS-25512) If two branchheads points to same commit, wrong branch might get deleted (our case 12269)
Bue Petersen updated JENKINS-25512 If two branchheads points to same commit, wrong branch might get deleted (our case 12269) Change By: Bue Petersen (11/Nov/14 2:48 PM) Summary: Iftwobranchheadspointstosamecommit,wrongbranchmightgetdeleted (ourcase12269) 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] [pretested-integration-plugin] (JENKINS-25545) Multiple git repository names are not check and repositories risk be merged (our case 12286)
Bue Petersen updated JENKINS-25545 Multiple git repository names are not check and repositories risk be merged (our case 12286) Change By: Bue Petersen (11/Nov/14 2:51 PM) Summary: Multiplegitrepositorynamesarenotcheckandrepositoriesriskbemerged (ourcase12286) 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] [pretested-integration-plugin] (JENKINS-25069) Plugin does not work with stash-git-hook (our case 12132)
Bue Petersen updated JENKINS-25069 Plugin does not work with stash-git-hook (our case 12132) Change By: Bue Petersen (11/Nov/14 2:50 PM) Summary: Plugindoesnotworkwithstash-git-hook (ourcase12132) 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] [pretested-integration-plugin] (JENKINS-25546) Support individual git scm configuration part in the Multi SCMs plugin
Bue Petersen created JENKINS-25546 Support individual git scm configuration part in the Multi SCMs plugin Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 11/Nov/14 3:08 PM Description: The following image describe how *several git configuration sections* in the Multi SCMs plugin are not supported: https://github.com/Praqma/pretested-integration-plugin/blob/9a68e17c11d579aa9eacc7502acd077cf0fde8d9/docs/Illegal_JENKINS24754.png We need support for this, and this is the needed configuration to make each git repository checkout into it own sub-directory. That is not possible using several git repos pr. configuration as we currently - only - support: https://github.com/Praqma/pretested-integration-plugin/blob/9a68e17c11d579aa9eacc7502acd077cf0fde8d9/docs/legal_JENKINS24754.png Implementation details: from the git plugin, several git build object will be parsed to the pretested plugin - see https://github.com/Praqma/pretested-integration-plugin/blob/9a68e17c11d579aa9eacc7502acd077cf0fde8d9/docs/More_than_1_gitBuild_data.png we will check the list... if they have the same name, we will fail with an description if the are named differently, we will do the usual checks (branch name, pattern, sha, branch head ...) Environment: 2.2.0-snapshop Project: Jenkins Priority: Major Reporter: Bue Petersen 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] [pretested-integration-plugin] (JENKINS-25546) Support individual git scm configuration part in the Multi SCMs plugin (our case 12287)
Bue Petersen updated JENKINS-25546 Support individual git scm configuration part in the Multi SCMs plugin (our case 12287) Change By: Bue Petersen (11/Nov/14 3:10 PM) Summary: SupportindividualgitscmconfigurationpartintheMultiSCMsplugin (ourcase12287) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-25523) Multiple SCMs Plugin doesn't work with Mercurial since 1.588
James Ascroft-Leigh
updated JENKINS-25523
Multiple SCMs Plugin doesnt work with Mercurial since 1.588
Change By:
James Ascroft-Leigh
(11/Nov/14 3:17 PM)
Description:
Iveupgradedfromjenkins1.585andalljobswithMultipleSCMpluginfailswithnextexception:
{code}
FATAL:org.jenkinsci.plugins.multiplescms.MultiSCMRevisionStatecannotbecasttohudson.plugins.mercurial.MercurialTagActionjava.lang.ClassCastException:org.jenkinsci.plugins.multiplescms.MultiSCMRevisionStatecannotbecasttohudson.plugins.mercurial.MercurialTagAction athudson.plugins.mercurial.MercurialSCM.determineChanges(MercurialSCM.java:603) athudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:552) athudson.scm.SCM.checkout(SCM.java:484) atorg.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118) athudson.model.AbstractProject.checkout(AbstractProject.java:1258) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) athudson.model.Run.execute(Run.java:1759) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240)
{code}
N.b.:*NewjobwithMultipleSCMpluginfailssameway.*Mercurialpluginworkscorrectly
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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Martin Beller commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration We upgraded from 1.588 to 1.589 and see this behaviour with the newest version. A downgrade to 1.588 solves the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25547) Clients on slave nodes are not auto-created
Nick Poole created JENKINS-25547 Clients on slave nodes are not auto-created Issue Type: Bug Assignee: Paul Allen Components: p4-plugin Created: 11/Nov/14 3:30 PM Description: In a matrix build environment, where one axis is slave nodes, builds fail on nodes that do not have client workspaces predefined. The problem appears to be that the client is checked before it would be created in CheckoutTask.java on line 126. Project: Jenkins Priority: Critical Reporter: Nick Poole 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-25547) Clients on slave nodes are not auto-created
Paul Allen commented on JENKINS-25547 Clients on slave nodes are not auto-created Please can you send me a failed build log output. 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] [mercurial-plugin] (JENKINS-25523) Multiple SCMs Plugin doesn't work with Mercurial since 1.588
James Ascroft-Leigh commented on JENKINS-25523 Multiple SCMs Plugin doesnt work with Mercurial since 1.588 For convenience, here are the links to the lines in the stacktrace... https://github.com/jenkinsci/mercurial-plugin/blob/master/src/main/java/hudson/plugins/mercurial/MercurialSCM.java#L603 https://github.com/jenkinsci/mercurial-plugin/blob/master/src/main/java/hudson/plugins/mercurial/MercurialSCM.java#L552 https://github.com/jenkinsci/jenkins/blob/c04cdcd9f717ddcd3e8c9dbe86cb353c14ae511e/core/src/main/java/hudson/scm/SCM.java#L484 https://github.com/jenkinsci/multiple-scms-plugin/blob/master/src/main/java/org/jenkinsci/plugins/multiplescms/MultiSCM.java#L118 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-19728) Much needed dependency management between jobs
Jesse Glick updated JENKINS-19728 Much needed dependency management between jobs Change By: Jesse Glick (11/Nov/14 3:47 PM) Labels: workflow 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-19728) Much needed dependency management between jobs
Jesse Glick commented on JENKINS-19728 Much needed dependency management between jobs Have you tried implementing these kinds of use cases using the Workflow system? It does nothing magical in terms of investigating dependencies; it just runs the things you told it to, in the order you told it, under the conditions you specified. Nonetheless it has some aspects which allow it to model the kinds of scenarios you discuss better than the Build Flow DSL plugin. In particular: While there is a build step to call out to “legacy” jobs, you need not use this at all, and can have all steps defined in one flow. This means that there is no chance of some subsection of the script being invoked independently and out of context—unless you made the flow parameterized and wrote its script to expect to skip some stages sometimes. You can have multiple SCM checkouts in one flow, with a single polling/changelog function. archive and unarchive let you pass artifacts between workspaces without using the Copy Artifact plugin. Or, if different stages can all run in one workspace, you need not do any copying at all. In common with Build Flow: You can freely pass information from one part of the flow to another, as local variables. You can use parallel to run some things concurrently, with an implicit join. 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-25548) StageStep should reject duplicate stage names
Jesse Glick created JENKINS-25548 StageStep should reject duplicate stage names Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 11/Nov/14 3:59 PM Description: If you run stage 'Dev' stage 'Dev' the second call should be treated as an error. Project: Jenkins Labels: robustness Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-25523) Multiple SCMs Plugin doesn't work with Mercurial since 1.588
James Ascroft-Leigh commented on JENKINS-25523 Multiple SCMs Plugin doesnt work with Mercurial since 1.588 Downgrading Mercurial plugin (1.51) to Mercurial plugin (1.50) seems to be a viable workaround for now. At least one of my jobs is getting past the SCM checkout stage now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25539) Derived views in folders should show only jobs that are part of that folder
Jesse Glick assigned JENKINS-25539 to Unassigned Derived views in folders should show only jobs that are part of that folder Change By: Jesse Glick (11/Nov/14 4:24 PM) Assignee: JesseGlick 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-25539) Derived views in folders should show only jobs that are part of that folder
Jesse Glick updated JENKINS-25539 Derived views in folders should show only jobs that are part of that folder Never heard of anyone trying to use derived views this way. The expectation is that each folder has its own set of views, and if you want to share some configuration across folders, you copy them. And if you want to avoid copying, you do so the same way you would share any configuration across any items: use the Templates plugin in the case of Jenkins Enterprise, or various OSS plugins which purport to solve DRY (not sure if any can handle arbitrary Item s like Folder s though). Change By: Jesse Glick (11/Nov/14 4:24 PM) Issue Type: Bug Improvement Labels: foldersview Component/s: core Component/s: cloudbees-folder-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-25539) Derived views in folders should show only jobs that are part of that folder
Jesse Glick commented on JENKINS-25539 Derived views in folders should show only jobs that are part of that folder Not to say that such an option for Include a global view would not make sense, just that this is only one way of addressing the ultimate requirement. 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-25144) Basic Authentication in combination with Session is broken
Daniel Beck commented on JENKINS-25144 Basic Authentication in combination with Session is broken 1.580.2 RC is due this week, so this won't be soaked enough. Inclusion in .3 is more likely. 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Daniel Beck commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration What project types are affected? 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] [script-security-plugin] (JENKINS-25524) SandboxInterceptorTest templates test failure blocking compilation
Jesse Glick commented on JENKINS-25524 SandboxInterceptorTest templates test failure blocking compilation Sure. Fortunately this fix was pretty easy to make. I think there are probably more obscure corner cases that are not yet being handled correctly, so pull requests with accompanying tests are welcome. (In this case it was not the functionality you really cared about, but rather the fact that the test was nondeterministic on Java 7+. Ironically it was asserting the wrong overload, though it could have failed on some runs either way.) 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] [thinBackup] (JENKINS-20395) Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server
M Chon commented on JENKINS-20395 Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server I am also getting this error. Would it be possible to have an option to ThinBackup to have it create .tar files (and possibly also .tgz) instead of .zip files? As I understand it, .zip is less efficient than .tar because it tries to individually compress each component file before adding to the archive. Whereas .tar creates the archive, which you can then zip all at once, at the end. 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-25549) FlowNode should have transient action integration
Kohsuke Kawaguchi created JENKINS-25549 FlowNode should have transient action integration Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 11/Nov/14 5:41 PM Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19728) Much needed dependency management between jobs
Kevin Phillips commented on JENKINS-19728 Much needed dependency management between jobs We had tried the Build Flow plugin, which does meet some of our needs, but one thing in particular it didn't seem to handle was the ability to run sub-sets of the dependency tree depending on which job has changes made to it. For example, if job B depends on job A and someone commits a change to job B we don't want job A to be built. This is necessary to improve build efficiency in our current infrastructure because building (and, by extension, testing) each module in our dependency tree is very time consuming, even for "no-op" builds. When you mention the Jenkins "workflow system", I assume you are referring to this plugin project I found on GitHub (which I believe you may be a contributor or maintainer). I have to say I hadn't heard of this plugin until you mentioned it, but it does sound promising. If it supports this sort of partial-build operation I just mentioned I may be interested in trying it. Specifically, if two dependent jobs can be configured with separate / independent SCM URLs so they may be triggered independently, while still allowing the build orchestration based on the job dependencies let me know. Even better, if you can point me to an example of how this may be done using that plugin I will let you know whether it works for our needs. 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-pipeline-plugin] (JENKINS-25551) Add % build complete to page title so it shows in browser tab
Ben Lesh created JENKINS-25551 Add % build complete to page title so it shows in browser tab Issue Type: New Feature Assignee: Unassigned Components: build-pipeline-plugin, core Created: 11/Nov/14 5:59 PM Description: I'm unsure if I've submitted this under the proper components. But it would be nice of the build % complete would show in the browser tab if I have it open, so that I can continue working in other tabs and know when it's done. Usually this would be done by appending/prepending the percentage to the title of the HTML. Perhaps even the favicon could change from blue to red to green? It's certainly an unimportant feature, but it would be very nice. Project: Jenkins Labels: jenkins ui browser Priority: Minor Reporter: Ben Lesh 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-25550) Hard kill
Jesse Glick created JENKINS-25550 Hard kill Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: workflow-plugin Created: 11/Nov/14 5:53 PM Description: Would be useful to have the equivalent of a SIGKILL for a WorkflowRun: immediately terminate the FlowExecution (with ABORTED), throw away all threads, and mark all StepContext as invalid. Would help in case regular interruption fails for whatever reason. Project: Jenkins Labels: robustness Priority: Major Reporter: Jesse Glick 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] [warnings-plugin] (JENKINS-24463) PyLint parse missing errors
Kevin Phillips commented on JENKINS-24463 PyLint parse missing errors I just hit this same problem with one of my projects. Something else I discovered that is worth considering is that it appears that when you call pylint code directly from other scripts, the --msg-template parameter seems to be ignored. I'm not sure if this is a defect in the library itself or maybe my use of the library atm. If it is a defect with the pylint code I'll report a bug with them, but in the meantime if you choose to document the expected output format as part of your parser plugin rather than create a new parser (which does seem preferable), you may want to mention this tidbit. 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] [warnings-plugin] (JENKINS-24463) PyLint parse missing errors
Chris Powell
commented on JENKINS-24463
PyLint parse missing errors
I just ended up requiring my various projects to include the following snippet in there pylintrc. It seems to be working well.
REPORTS
output-format=text
reports=no
msg-template={path}:{line}: {msg_id}({symbol}), {obj} {msg}
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] [warnings-plugin] (JENKINS-24463) PyLint parse missing errors
Kevin Phillips commented on JENKINS-24463 PyLint parse missing errors Another possible improvement here might be to do some basic content validation within your parser, and if it seems like the content of the log file being parsed doesn't meet the format specification you expect you could provide some kind of helpful feedback to the user, something to the effect of "pylint output not in the expected format. See online documentation for details of the expected format." I know this would have been greatly helpful to me since I just spent the last several hours messing with my Python code and Jenkins plugins trying to get this to work and at no point did any of these tools indicate a potential configuration problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25552) Git Polling with keys fails for Windows master and OSX slave
Nicolae Ghimbovschi created JENKINS-25552 Git Polling with keys fails for Windows master and OSX slave Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 11/Nov/14 6:41 PM Description: The job is configured to use the git command for unix. Git authentication is key based. When manually triggering the job, it works. Git Polling does not work. The Jenkins master is a windows machine, the slave is OS X 10.9 Started on Nov 11, 2014 7:26:49 PM Using strategy: Default poll Last Built Revision: Revision 4dd28ae36ea5534d2ad666e70edbcb22b412b3ff (refs/remotes/origin/develop) using GIT_SSH to set credentials MobileDaily GitHub key git ls-remote -h g...@bitbucket.org:alexmx/en-ios-internship.git develop # timeout=10 FATAL: hudson.plugins.git.GitException: Error performing command: git ls-remote -h g...@bitbucket.org:alexmx/en-ios-internship.git develop hudson.util.IOException2: hudson.plugins.git.GitException: Error performing command: git ls-remote -h g...@bitbucket.org:alexmx/en-ios-internship.git develop at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:475) at hudson.scm.SCM.poll(SCM.java:401) at hudson.model.AbstractProject._poll(AbstractProject.java:1429) at hudson.model.AbstractProject.poll(AbstractProject.java:1332) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: hudson.plugins.git.GitException: Error performing command: git ls-remote -h g...@bitbucket.org:alexmx/en-ios-internship.git develop at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1442) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1223) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1136) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1127) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:2057) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:509) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:473) ... 12 more Caused by: java.io.IOException: Cannot run program "git": CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:803) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1431) ... 18 more Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.init(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) ... 24 more Done. Took 22 ms No changes Environment: Jenkins ver. 1.580.1 Latest git-plugin Project: Jenkins Labels: git git-plugin polling unix windows Priority: Minor Reporter:
[JIRA] [jabber-plugin] (JENKINS-25505) jabber-plugin 1.28 cannot resolve host with javax.naming.NameNotFoundException: DNS name not found
kutzi commented on JENKINS-25505 jabber-plugin 1.28 cannot resolve host with javax.naming.NameNotFoundException: DNS name not found This build of the plugin uses a version of the Smack library which could fix the issue: https://dl.dropboxusercontent.com/u/25863594/jabber.hpi Would be great if you could test 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] [jabber-plugin] (JENKINS-25505) jabber-plugin 1.28 cannot resolve host with javax.naming.NameNotFoundException: DNS name not found
kutzi updated JENKINS-25505 jabber-plugin 1.28 cannot resolve host with javax.naming.NameNotFoundException: DNS name not found Change By: kutzi (11/Nov/14 6:54 PM) Summary: AfterUpgradejenkinsto jabber-plugin 1. 587 28 cannot sendmessage resolvehost with jabber javax.naming.NameNotFoundException:DNSnamenotfound 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] [global-build-stats-plugin] (JENKINS-16475) Build stats graph configuration lost after Jenkins Restart
Astro Ashtar edited a comment on JENKINS-16475 Build stats graph configuration lost after Jenkins Restart Everytime my jenkins service crashes and I reboot, i see this error which is the same as above. I am on Windows Server 2012 and using the most up to date Jenkins v1.589 When this happens, it takes about 20 minutes for my jenkins to get back online and visible through the web url. Nov 11, 2014 11:27:59 AM hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver reloadPlugin SEVERE: Unable to read C:\Program Files (x86)\Jenkins\global-build-stats.xml java.io.IOException: Unable to read C:\Program Files (x86)\Jenkins\global-build-stats.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at hudson.Plugin.load(Plugin.java:244) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.load(GlobalBuildStatsPlugin.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver.reloadPlugin(GlobalBuildStatsPluginSaver.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsBusiness.reloadPlugin(GlobalBuildStatsBusiness.java:382) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin$GlobalBuildStatsItemListener.onLoaded(GlobalBuildStatsPlugin.java:149) at jenkins.model.Jenkins.init(Jenkins.java:845) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:225) Caused by: com.thoughtworks.xstream.converters.ConversionException: : no more data available - expected end tag /list to close start tag list from line 1, parser stopped on END_TAG seen .../un\n /jbr\n ... @70946:4 : : no more data available - expected end tag /list to close start tag list from line 1, parser stopped on END_TAG seen .../un\n /jbr\n ... @70946:4 Debugging information message : : no more data available - expected end tag /list to close start tag list from line 1, parser stopped on END_TAG seen .../un\n /jbr\n ... @70946:4 cause-exception : com.thoughtworks.xstream.io.StreamException cause-message : : no more data available - expected end tag /list to close start tag list from line 1, parser stopped on END_TAG seen .../un\n /jbr\n ... @70946:4 class : java.util.ArrayList required-type : java.util.ArrayList converter-type : hudson.util.RobustCollectionConverter path: /list line number : 70946 version : not available class1: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin required-type1: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin converter-type1 : hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter path1 : /hudson.plugins.global_build_stats.GlobalBuildStatsPlugin line number1 : 2 --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1044) at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:139) at hudson.plugins.global_build_stats.xstream.migration.AbstractMigrator.readGlobalBuildStatsPOJO(AbstractMigrator.java:35) at hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter.unmarshal(GlobalBuildStatsXStreamConverter.java:159) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at
[JIRA] [global-build-stats-plugin] (JENKINS-16475) Build stats graph configuration lost after Jenkins Restart
Astro Ashtar commented on JENKINS-16475 Build stats graph configuration lost after Jenkins Restart Everytime my jenkins service crashes and I reboot, i see this error which is the same as above. I am on Windows Server 2012 and using the most up to date Jenkins v1.589 Nov 11, 2014 11:27:59 AM hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver reloadPlugin SEVERE: Unable to read C:\Program Files (x86)\Jenkins\global-build-stats.xml java.io.IOException: Unable to read C:\Program Files (x86)\Jenkins\global-build-stats.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at hudson.Plugin.load(Plugin.java:244) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.load(GlobalBuildStatsPlugin.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver.reloadPlugin(GlobalBuildStatsPluginSaver.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsBusiness.reloadPlugin(GlobalBuildStatsBusiness.java:382) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin$GlobalBuildStatsItemListener.onLoaded(GlobalBuildStatsPlugin.java:149) at jenkins.model.Jenkins.init(Jenkins.java:845) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:225) Caused by: com.thoughtworks.xstream.converters.ConversionException: : no more data available - expected end tag /list to close start tag list from line 1, parser stopped on END_TAG seen .../un\n /jbr\n ... @70946:4 : : no more data available - expected end tag /list to close start tag list from line 1, parser stopped on END_TAG seen .../un\n /jbr\n ... @70946:4 Debugging information message : : no more data available - expected end tag /list to close start tag list from line 1, parser stopped on END_TAG seen .../un\n /jbr\n ... @70946:4 cause-exception : com.thoughtworks.xstream.io.StreamException cause-message : : no more data available - expected end tag /list to close start tag list from line 1, parser stopped on END_TAG seen .../un\n /jbr\n ... @70946:4 class : java.util.ArrayList required-type : java.util.ArrayList converter-type : hudson.util.RobustCollectionConverter path: /list line number : 70946 version : not available class1: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin required-type1: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin converter-type1 : hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter path1 : /hudson.plugins.global_build_stats.GlobalBuildStatsPlugin line number1 : 2 --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1044) at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:139) at hudson.plugins.global_build_stats.xstream.migration.AbstractMigrator.readGlobalBuildStatsPOJO(AbstractMigrator.java:35) at hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter.unmarshal(GlobalBuildStatsXStreamConverter.java:159) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at
[JIRA] [core] (JENKINS-25543) Animation broken in IE11
Daniel Beck updated JENKINS-25543 Animation broken in IE11 Change By: Daniel Beck (11/Nov/14 7:39 PM) Labels: user-experience 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-25549) FlowNode should have transient action integration
Jesse Glick commented on JENKINS-25549 FlowNode should have transient action integration One use case: add a transient action to every node which offers the equivalent of doConfigDotXml using SimpleXStreamFlowNodeStorage. Useful for diagnosing the content of a flow node without going to disk. 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] [nodelabelparameter-plugin] (JENKINS-24280) Environment variables get corrupted when using Node parameter
Daniel Beck commented on JENKINS-24280 Environment variables get corrupted when using Node parameter I cannot uninstall Env Inject to verify. But you can set up a second Jenkins instance, without Env Inject, to try to reproduce the issue there. If it works with only NodeLabel parameter, and then you install env-inject, and then it starts failing, you know what's going on. 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-25537) REST api provides incomplete information
Daniel Beck commented on JENKINS-25537 REST api provides incomplete information Looks more like an improvement, or does P4 guarantee/aim for feature parity? 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] [plugin-proposals] (JENKINS-522) Allow feature-level enable/disable for plugins
Daniel Beck commented on JENKINS-522 Allow feature-level enable/disable for plugins Fixed by https://wiki.jenkins-ci.org/display/JENKINS/Extension+Filter+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-19728) Much needed dependency management between jobs
Jesse Glick commented on JENKINS-19728 Much needed dependency management between jobs There is no built-in notion of a “partial build”. Probably something like that could be created as an operator if there is sufficient demand. There would still be one job with a sequence of builds, but some of these would be skipping build steps based on an inspection of the SCM changelog and a determination that nothing has changed in this area since the previous 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.
