[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 If the problem is fixed, Steve Christou, you're our hero! Out of curiosity, why was the old svnkit so patched, if it wasn't needed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Christian Symmons commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module Hi, we are seeing the same issue on a single OSX Client (Linux Master Server). Version 1.572. I've noticed it on two builds this morning. At the time, the build script was doing an untar in the command shell. x lib/QtXmlPatterns.framework/Versions/Current/Headers/qxmlnamepool.hFATAL: Invalid object ID 473 iota=474 java.lang.IllegalStateException: Invalid object ID 473 iota=474 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:304) at hudson.remoting.ExportTable.get(ExportTable.java:288) at hudson.remoting.Channel.getExportedObject(Channel.java:596) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:301) 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$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.Exception: Object was recently deallocated #473 (ref.0) : hudson.Launcher$RemoteLaunchCallable$1 Created at Thu Nov 06 02:55:27 GMT 2014 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:91) at hudson.remoting.ExportTable.export(ExportTable.java:266) at hudson.remoting.Channel.export(Channel.java:592) at hudson.remoting.Channel.export(Channel.java:583) at hudson.remoting.Channel.export(Channel.java:553) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1078) 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$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680) Released at Thu Nov 06 02:55:28 GMT 2014 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:125) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:332) at hudson.remoting.Channel.unexport(Channel.java:600) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remoting.UnexportCommand@52a2a0cb created at at hudson.remoting.Command.init(Command.java:67) at hudson.remoting.Command.init(Command.java:50) at hudson.remoting.UnexportCommand.init(UnexportCommand.java:33) at hudson.remoting.RemoteInvocationHandler.finalize(RemoteInvocationHandler.java:229) at java.lang.System$2.invokeFinalize(System.java:1267) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:98) at java.lang.ref.Finalizer.access$100(Finalizer.java:34) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:210) at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:297) ... 14 more Caused by: Released at Thu Nov 06 02:55:28 UTC 2014 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:125) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:332) at hudson.remoting.Channel.unexport(Channel.java:600) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:475) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by:
[JIRA] [git-plugin] (JENKINS-25465) ${GIT_BRANCH} macro expands full branch name + remotes instead of short name
Maciej Matys
created JENKINS-25465
${GIT_BRANCH} macro expands full branch name + remotes instead of short name
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git-plugin
Created:
06/Nov/14 9:04 AM
Description:
Docs says that ${GIT_BRANCH} macro should expands to the full branch name, such as 'origin/master'. Otherwise(without fullName parameter), it only expands to the short name, such as 'master', but without fullName parameter it expands to 'remotes/origin/master' with fullName parameter it doesn't work at all.
Environment:
Centos OS 6,
git version 1.7.12.4,
Jenkins ver. 1.588,
GIT plugin 2.2.7
Project:
Jenkins
Priority:
Major
Reporter:
Maciej Matys
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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build
Thomas Saunders commented on JENKINS-13458 Add switch to set reference build always as the latest build I was looking into providing this but was having issues with the inheritance from the -core, and presentation in the job (Can get a setting saved per job, but cannot display it back in the configuration). 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
Magnus Jacobsson
created JENKINS-25466
Exception String index out of range in summary_report plugin
Issue Type:
Bug
Assignee:
Unassigned
Components:
summary_report-plugin
Created:
06/Nov/14 9:12 AM
Description:
An exception occurs because the length check is wrong here:
https://github.com/jenkinsci/summary_report-plugin/blob/master/src/main/resources/hudson/plugins/summary_report/ACIPluginBuildAction/componentField.jelly#L17
This line is:
j:if test="${(b.href != null) (b.href.length() 6) (b.href.substring(0,7) != 'http://') (b.href.substring(0,8) != 'https://')}"
and should be changed to something like:
j:if test="${(b.href != null) (b.href.length() 6) (b.href.substring(0,7) != 'http://') (b.href.length() 7) (b.href.substring(0,8) != 'https://')}"
Here is the crash dump:
2014-nov-06 09:32:50 hudson.ExpressionFactory2$JexlExpression evaluate
VARNING: Caught exception evaluating: (b.href != null) (b.href.length() 6) (b.href.substring(0,7) != 'http://') (b.href.substring(0,8) != 'https://') in /job/main-Maxtest_dtmprotocol_sw112/15/. Reason: java.lang.StringIndexOutOfBoundsException: String index out of range: 8
java.lang.StringIndexOutOfBoundsException: String index out of range: 8
at java.lang.String.substring(String.java:1946)
at sun.reflect.GeneratedMethodAccessor163.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at org.apache.commons.jexl.parser.ASTNENode.value(ASTNENode.java:55)
at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54)
at org.apache.commons.jexl.parser.ASTAndNode.value(ASTAndNode.java:61)
at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54)
at org.apache.commons.jexl.parser.ASTExpressionExpression.value(ASTExpressionExpression.java:56)
at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)
at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsBoolean(ExpressionSupport.java:71)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:97)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
[JIRA] [multiple-scms-plugin] (JENKINS-9287) Configuration is not saven when two git repositories are added
Jeebitesh Kalantri commented on JENKINS-9287 Configuration is not saven when two git repositories are added This issue is persisting from long time, it would be great if we can have resolution for this, it will be good for people who are using GIT and TFS. As we know TFS does not support external like Subversion, so this plugin becomes more and more important. 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-failure-analyzer-plugin] (JENKINS-25467) Capture group replacement not working
Michael Keppler
created JENKINS-25467
Capture group replacement not working
Issue Type:
Bug
Assignee:
Tomas Westling
Components:
build-failure-analyzer-plugin
Created:
06/Nov/14 9:43 AM
Description:
The replacement of capture groups in descriptions is not working for me. I've tried this multiple times now.
Example issue description:
Maven build failed in project ${1,1}.
Example indication (single line):
.Failed to execute goal.*on project (.):
The regular _expression_ matches, the failure cause is reported, but the ${1,1} is still contained verbatim in the description of the found issue.
Am I doing it wrong? If so, the documentation of this feature might need an update.
Project:
Jenkins
Priority:
Major
Reporter:
Michael Keppler
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-25341) Improve reconcile by using -m option
Paul Allen commented on JENKINS-25341 Improve reconcile by using -m option I have implemented the feature, but found a P4-Java bug. The MODTIME is not set during the sync; not sure how long it will take to get a fix for this. However, P4-Java will soon be open sourced, so I can start making my own fixes 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] [pvcs_scm-plugin] (JENKINS-8243) NPE from Polling PVCS
Isabelle Theis
commented on JENKINS-8243
NPE from Polling PVCS
It's because of the pvcs_scm Plugin returning, it doesn't need a workspace to poll:
PvcsScm.java
// {{{ requiresWorkspaceForPolling
/**
* @todo
*/
@Override
public boolean requiresWorkspaceForPolling() {
return false;
}
In that case the launcher is null:
AbstractProject.java
if (scm.requiresWorkspaceForPolling()) {
...
} else {
// polling without workspace
LOGGER.fine("Polling SCM changes of " + getName());
if (pollingBaseline==null) // see NOTE-NO-BASELINE above
calcPollingBaseline(getLastBuild(),null,listener);
PollingResult r = scm.poll(this, null, null, listener, pollingBaseline);
pollingBaseline = r.remote;
return r;
}
Who could change this to fix 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] [git-plugin] (JENKINS-24934) Git clone with merging tries to checkout non-existing revision since force-push
Wannes Sels commented on JENKINS-24934 Git clone with merging tries to checkout non-existing revision since force-push No, it probably wont be. The second problem you described should be fixed in 2.2.8 the first problem you described is something else. The matrix coordinator job can do a merge, but has no way of sharing that new commit to the matrix jobs. As a workaround I suggest you split this in 2 jobs: 1 job to do the merge and push in a temporary branch, optionally in a separate repository. This job can then trigger the matrix job and pass the git revision. Configure the matrix job with the temporary branch, and it will pick up the merge. 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-24934) Can't use matrix job with pre-build merge
Wannes Sels updated JENKINS-24934 Cant use matrix job with pre-build merge Change By: Wannes Sels (06/Nov/14 10:07 AM) Summary: Gitclone Cantusematrixjob with mergingtriestocheckoutnon pre - existingrevisionsinceforce-push buildmerge 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-24934) Can't use matrix job with pre-build merge
Wannes Sels commented on JENKINS-24934 Cant use matrix job with pre-build merge Does anyone have a suggestion on how to make sure the other matrix jobs can receive the (merge) commit(s) created by the matrix coordinator job? Should the matrix coordinator temporarily host a git server? Should the matrix coordinator create a bundle containing only those new commits and distribute it to the other matrix jobs? 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] [multijob-plugin] (JENKINS-25452) Change implementation of Build Only If SCMChanges to be check just if it's configure
hagzag resolved JENKINS-25452 as Fixed Change implementation of Build Only If SCMChanges to be check just if its configure fixed with PR - https://github.com/jenkinsci/tikal-multijob-plugin/pull/57 Change By: hagzag (06/Nov/14 10:18 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] [multijob-plugin] (JENKINS-25452) Change implementation of Build Only If SCMChanges to be check just if it's configure
hagzag closed JENKINS-25452 as Fixed Change implementation of Build Only If SCMChanges to be check just if its configure https://github.com/jenkinsci/tikal-multijob-plugin/pull/57 Change By: hagzag (06/Nov/14 10:18 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Morne Joubert commented on JENKINS-25341 Improve reconcile by using -m option while we wait for this fix, would it be possible to add some timing info on the console to see how long the reconcile takes, sync takes etc? Also it is possible to add a verbosity mode to allow the output of some of the p4 commands if it is relevant ? 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-failure-analyzer-plugin] (JENKINS-18544) Missing dependency to git
Jan Feindt commented on JENKINS-18544 Missing dependency to git Please check if this issue can be solved by updating to new gerrit-trigger version. see https://issues.jenkins-ci.org/browse/JENKINS-22813 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 commented on JENKINS-25364 Unable to update workspace error It was regarding my post on 31st: Please can you also try this against your server and not via the proxy. It just eliminates one more item. When you commented "I tried to sync to server directly from command line" I thought you had bypassed the proxy. The sort of errors you are getting suggests a poor network link or some sort of QoS. If you are using a proxy, then please try editing the Credentials to access the server directly. 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-25430) Clicking on console icon doesn't work
Dennis Philpot commented on JENKINS-25430 Clicking on console icon doesnt work This Issue is mentioned twice, although this one was earlier this Issue JENKINS-25430 is quite better documented. 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] [azure-slave-plugin] (JENKINS-24649) Allow to stop / deallocate and start / allocate existing VMs on demand
Sebastian Schuberth commented on JENKINS-24649 Allow to stop / deallocate and start / allocate existing VMs on demand Any updates on the ETA? If we're not able to get this in a reasonable time frame, we're forced to move from Azure to AWS as the Jenkins ec2 plugin 1 already has this feature. 1 https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+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] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Paul Allen commented on JENKINS-25341 Improve reconcile by using -m option P4Java is a native API so it doesn't run commands as such. I have had another request to list all synced files, I guess I could look to add more information about the files processed for other operations (reconcile/sync/delete/etc...). As for timing operations I think there is some Jenkins support for this. I would need to read up on this, unless you know of the particular methods? It might be best to raise these as two separate 'Improvements'. 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-25341) Improve reconcile by using -m option
Morne Joubert commented on JENKINS-25341 Improve reconcile by using -m option the timing plugin is VERY buggy and doesn't support the Jenkins LTS versions very well. I will add it as 2 extra feature requests 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-25468) Add a Verbosity option to allow detailed p4 info
Morne Joubert created JENKINS-25468 Add a Verbosity option to allow detailed p4 info Issue Type: New Feature Assignee: Unassigned Components: p4-plugin Created: 06/Nov/14 11:57 AM Description: It would be good to have a verbosity boolean flag the user can set to display the output of the various commands. e.g. what files where synced, what files was reverted, deleted etc Project: Jenkins Priority: Minor 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] [p4-plugin] (JENKINS-24741) Expose duration of plugin steps
Morne Joubert updated JENKINS-24741 Expose duration of plugin steps Change By: Morne Joubert (06/Nov/14 12:00 PM) Summary: Exposedurationofplugin steps Description: Itwouldbegoodtoexposethedurationofthe p4 actions (inenvvariablesifpossible) soicantrackhowlongittookfor reconsile, cleanup,syncetc.Icanthentracksyncsthattaketoolongetc. ThereisapluginthatcanaddtimestampstologsbutitistoobuggyanddoesntalwayssupporttheJenkinsLTSversion 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] [swarm-plugin] (JENKINS-25064) Swarm toollocations don't work for all tools
SCM/JIRA link daemon commented on JENKINS-25064 Swarm toollocations dont work for all tools Code changed in jenkins User: nico.mommaerts Path: plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java http://jenkins-ci.org/commit/swarm-plugin/73da69a23a67a7af32bc8df24fa9ff10906f6de9 Log: FIXED JENKINS-25064 Instead of constructing the toollocation key, just use the existing descriptor 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] [swarm-plugin] (JENKINS-25064) Swarm toollocations don't work for all tools
SCM/JIRA link daemon commented on JENKINS-25064 Swarm toollocations dont work for all tools Code changed in jenkins User: Peter Jönsson Path: plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java http://jenkins-ci.org/commit/swarm-plugin/0dddc0fccbbe5797ef4b8a032ed19948092da18a Log: Merge pull request #20 from mrdfuse/JENKINS-25064 FIXED JENKINS-25064 Instead of constructing the toollocation key, just use the existing descriptor Compare: https://github.com/jenkinsci/swarm-plugin/compare/30ee1f19cb0d...0dddc0fccbbe 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] [swarm-plugin] (JENKINS-25064) Swarm toollocations don't work for all tools
SCM/JIRA link daemon resolved JENKINS-25064 as Fixed Swarm toollocations dont work for all tools Change By: SCM/JIRA link daemon (06/Nov/14 12:12 PM) 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] [other] (JENKINS-25469) Unable to deleate wrongly created Radiator View
Lukasz Mazurkiewicz created JENKINS-25469 Unable to deleate wrongly created Radiator View Issue Type: Bug Assignee: Unassigned Components: other Created: 06/Nov/14 12:20 PM Description: Oops! A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/cinas02/ci_home/blnfj112-vm01/plugins/radiatorviewplugin/WEB-INF/lib/classes.jar!/hudson/model/RadiatorView/jobs.jelly:5:52: j:invoke method toRows threw exception: null at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:157) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:131) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:82) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:52) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at
[JIRA] [other] (JENKINS-25469) Unable to deleate wrongly created Radiator View
Lukasz Mazurkiewicz commented on JENKINS-25469 Unable to deleate wrongly created Radiator View lukasz.mazurkiew...@redknee.com 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
Steven Christou commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 aristedes Thank you! . Josef Andersson Thanks. There were a lot of custom code in the old svnkit mostly for other plugins like blamesvn plugin, and svnmerge plugin. Before any new release could be made, I need to fix/release these plugins first. I have a WIP PR for svn 1.8: PR 103. 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] [artifactdeployer-plugin] (JENKINS-25461) ArtifactDeployer breaks under recent build(s) of Jenkins
Paul Fletcher commented on JENKINS-25461 ArtifactDeployer breaks under recent build(s) of Jenkins I'm getting the same issue on Windows Server 2012 Standard with 1.586 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] [artifactdeployer-plugin] (JENKINS-25461) ArtifactDeployer breaks under recent build(s) of Jenkins
Paul Fletcher edited a comment on JENKINS-25461 ArtifactDeployer breaks under recent build(s) of Jenkins I'm getting the same issue on Windows Server 2012 Standard with 1.586 [ArtifactDeployer] - Starting deployment from the post-action ... ERROR: Publisher org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher aborted due to exception java.lang.AbstractMethodError at com.sun.jna.Structure.fieldOrder(Structure.java:884) at com.sun.jna.Structure.getFields(Structure.java:910) at com.sun.jna.Structure.deriveLayout(Structure.java:1058) at com.sun.jna.Structure.calculateSize(Structure.java:982) at com.sun.jna.Structure.calculateSize(Structure.java:949) at com.sun.jna.Structure.allocateMemory(Structure.java:375) at com.sun.jna.Structure.init(Structure.java:184) at com.sun.jna.Structure.init(Structure.java:172) at com.sun.jna.Structure.init(Structure.java:159) at com.sun.jna.Structure.init(Structure.java:151) at org.jruby.ext.posix.BaseNativeFileStat.init(BaseNativeFileStat.java:9) at org.jruby.ext.posix.WindowsFileStat.init(WindowsFileStat.java:21) at org.jruby.ext.posix.WindowsPOSIX.allocateStat(WindowsPOSIX.java:17) at org.jruby.ext.posix.BaseNativePOSIX.stat(BaseNativePOSIX.java:182) at com.atlassian.ant.tasks.PermissionsUtils.getPermissions(PermissionsUtils.java:21) at com.atlassian.ant.tasks.CopyWithPerms.doFileOperations(CopyWithPerms.java:75) at org.jenkinsci.plugins.artifactdeployer.service.LocalCopy$1CopyImpl.doFileOperations(LocalCopy.java:60) at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:567) at org.jenkinsci.plugins.artifactdeployer.service.LocalCopy.copyAndGetNumbers(LocalCopy.java:83) at org.jenkinsci.plugins.artifactdeployer.service.ArtifactDeployerCopy.invoke(ArtifactDeployerCopy.java:70) at org.jenkinsci.plugins.artifactdeployer.service.ArtifactDeployerCopy.invoke(ArtifactDeployerCopy.java:40) at hudson.FilePath.act(FilePath.java:919) at hudson.FilePath.act(FilePath.java:897) at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher.processDeployment(ArtifactDeployerPublisher.java:202) at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher._perform(ArtifactDeployerPublisher.java:128) at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher.perform(ArtifactDeployerPublisher.java:99) 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.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) 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] [mailer-plugin] (JENKINS-25470) Provided mail-1.4.4.jar seems to be missing the smtp provider
Christian Nolte created JENKINS-25470 Provided mail-1.4.4.jar seems to be missing the smtp provider Issue Type: Bug Assignee: Unassigned Components: mailer-plugin Created: 06/Nov/14 1:02 PM Description: When configuring jenkins so that it uses localhost to send mails and test-send a mail, it fails. After each update of jenkins we currently have to remove WEB-INF/lib/mail-*.jar and restart Tomcat, so that the system mail.jar is being used (which works). This seems to be: lrwxrwxrwx 1 root root 52 7. Dez 2011 /etc/alternatives/javamail - /usr/share/java/classpathx-mail-1.3.1-monolithic.jar which works fine. The resulting exception is: javax.mail.NoSuchProviderException: smtp at javax.mail.Session.getService(Session.java:798) at javax.mail.Session.getTransport(Session.java:720) at javax.mail.Session.getTransport(Session.java:660) at javax.mail.Session.getTransport(Session.java:640) at javax.mail.Session.getTransport(Session.java:697) at javax.mail.Transport.send0(Transport.java:192) at javax.mail.Transport.send(Transport.java:124) at hudson.tasks.Mailer$DescriptorImpl.doSendTestMail(Mailer.java:522) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Ben Daniels commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Thanks Steven for your efforts on 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] [artifactdeployer-plugin] (JENKINS-25461) ArtifactDeployer breaks under recent build(s) of Jenkins
Paul Fletcher edited a comment on JENKINS-25461 ArtifactDeployer breaks under recent build(s) of Jenkins I'm getting the same issue on Windows Server 2012 Standard with 1.586 Looks like its related to JENKINS-24521 [ArtifactDeployer] - Starting deployment from the post-action ... ERROR: Publisher org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher aborted due to exception java.lang.AbstractMethodError at com.sun.jna.Structure.fieldOrder(Structure.java:884) at com.sun.jna.Structure.getFields(Structure.java:910) at com.sun.jna.Structure.deriveLayout(Structure.java:1058) at com.sun.jna.Structure.calculateSize(Structure.java:982) at com.sun.jna.Structure.calculateSize(Structure.java:949) at com.sun.jna.Structure.allocateMemory(Structure.java:375) at com.sun.jna.Structure.init(Structure.java:184) at com.sun.jna.Structure.init(Structure.java:172) at com.sun.jna.Structure.init(Structure.java:159) at com.sun.jna.Structure.init(Structure.java:151) at org.jruby.ext.posix.BaseNativeFileStat.init(BaseNativeFileStat.java:9) at org.jruby.ext.posix.WindowsFileStat.init(WindowsFileStat.java:21) at org.jruby.ext.posix.WindowsPOSIX.allocateStat(WindowsPOSIX.java:17) at org.jruby.ext.posix.BaseNativePOSIX.stat(BaseNativePOSIX.java:182) at com.atlassian.ant.tasks.PermissionsUtils.getPermissions(PermissionsUtils.java:21) at com.atlassian.ant.tasks.CopyWithPerms.doFileOperations(CopyWithPerms.java:75) at org.jenkinsci.plugins.artifactdeployer.service.LocalCopy$1CopyImpl.doFileOperations(LocalCopy.java:60) at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:567) at org.jenkinsci.plugins.artifactdeployer.service.LocalCopy.copyAndGetNumbers(LocalCopy.java:83) at org.jenkinsci.plugins.artifactdeployer.service.ArtifactDeployerCopy.invoke(ArtifactDeployerCopy.java:70) at org.jenkinsci.plugins.artifactdeployer.service.ArtifactDeployerCopy.invoke(ArtifactDeployerCopy.java:40) at hudson.FilePath.act(FilePath.java:919) at hudson.FilePath.act(FilePath.java:897) at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher.processDeployment(ArtifactDeployerPublisher.java:202) at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher._perform(ArtifactDeployerPublisher.java:128) at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher.perform(ArtifactDeployerPublisher.java:99) 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.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) 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-25471) Changes in pipelineview is missing the latest commits
Anders Nyström created JENKINS-25471 Changes in pipelineview is missing the latest commits Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 06/Nov/14 1:42 PM Description: Changes in pipelineview is missing the latest commits. For eg: If you have a pipeline and something triggers it the changes will be there, but if the pipeline itself makes changes by for eg commiting stuff. The change wont be there until the next run of the pipeline even if the next stage actually use this change. Project: Jenkins Priority: Minor Reporter: Anders Nyström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [radiatorview-plugin] (JENKINS-25463) 404 When Clicking on a Job
Baptiste Mathus resolved JENKINS-25463 as Duplicate 404 When Clicking on a Job Change By: Baptiste Mathus (06/Nov/14 2:06 PM) Status: Open Resolved Assignee: howama BaptisteMathus Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [radiatorview-plugin] (JENKINS-23096) radiatorviewplugin has incorrect links for jobs in folders
Baptiste Mathus commented on JENKINS-23096 radiatorviewplugin has incorrect links for jobs in folders Fixed with 1.22 released yesterdeay. 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] [radiatorviewplugin] (JENKINS-25472) Clicking on a job never built links to 404
Baptiste Mathus created JENKINS-25472 Clicking on a job never built links to 404 Issue Type: Bug Assignee: Unassigned Components: radiatorviewplugin Created: 06/Nov/14 2:11 PM Description: When setting the option "Show stable build", job that have never been built are also shown. If you click on their link, it links to .../thejob/lastBuild which sends to 404. IMO this should just send to the least surprising thing: the job itself instead of the last build. Project: Jenkins Priority: Minor Reporter: Baptiste Mathus 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] [disk-usage-plugin] (JENKINS-20135) Disk usage plugin: error 404
Marco Descher edited a comment on JENKINS-20135 Disk usage plugin: error 404 This issue still exists on my updated-jenkins Jenkins ver. 1.580.1 with disk-usage plugin 0.24! The url presented is https://sbe.medelexis.ch/jenkins/disk-usage it should be https://sbe.medelexis.ch/jenkins/plugin/disk-usage/ however! This accounts for the link on the main jenkins page! 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] [disk-usage-plugin] (JENKINS-20135) Disk usage plugin: error 404
Marco Descher commented on JENKINS-20135 Disk usage plugin: error 404 This issue still exists on my updated-jenkins Jenkins ver. 1.580.1 with disk-usage plugin 0.24! The url presented is https://sbe.medelexis.ch/jenkins/disk-usage it should be https://sbe.medelexis.ch/jenkins/plugin/disk-usage/ however! 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] [radiatorviewplugin] (JENKINS-25472) Clicking on a job never built links to 404
SCM/JIRA link daemon commented on JENKINS-25472 Clicking on a job never built links to 404 Code changed in jenkins User: Baptiste Mathus Path: src/main/java/hudson/model/JobViewEntry.java http://jenkins-ci.org/commit/radiatorview-plugin/eb74f5193601bddeee3503c2c39aab53edd34ff4 Log: FIXED JENKINS-25472 Job never built 404 Now we direct to the job page instead of the lastBuild if there's none. 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] [radiatorviewplugin] (JENKINS-25472) Clicking on a job never built links to 404
SCM/JIRA link daemon resolved JENKINS-25472 as Fixed Clicking on a job never built links to 404 Change By: SCM/JIRA link daemon (06/Nov/14 2:22 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25473) Unnecessarily slow serialized I/O for top-level item loading in loadTasks
Jesse Glick created JENKINS-25473 Unnecessarily slow serialized I/O for top-level item loading in loadTasks Issue Type: Bug Assignee: Unassigned Components: core Created: 06/Nov/14 2:46 PM Description: Filing https://github.com/jenkinsci/jenkins/pull/1439 retroactively. Project: Jenkins Labels: performance lts-candidate startup 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] [core] (JENKINS-25473) Unnecessarily slow serialized I/O for top-level item loading in loadTasks
Jesse Glick resolved JENKINS-25473 as Fixed Unnecessarily slow serialized I/O for top-level item loading in loadTasks Change By: Jesse Glick (06/Nov/14 2:46 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6097) Update Center could upgrade plugins to latest-release-for-my-Hudson
Jesse Glick started work on JENKINS-6097 Update Center could upgrade plugins to latest-release-for-my-Hudson Change By: Jesse Glick (06/Nov/14 2:55 PM) Status: Open InProgress 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-6097) Update Center could upgrade plugins to latest-release-for-my-Hudson
Jesse Glick updated JENKINS-6097 Update Center could upgrade plugins to latest-release-for-my-Hudson Change By: Jesse Glick (06/Nov/14 2:57 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-6097) Update Center could upgrade plugins to latest-release-for-my-Hudson
Jesse Glick commented on JENKINS-6097 Update Center could upgrade plugins to latest-release-for-my-Hudson Same goal, different technique: pay attention to update-center.json?version=… and serve different content, so that the advertised “latest” plugin version is simply that which works with your current version (or some approximation of it). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6097) Update Center could upgrade plugins to latest-release-for-my-Hudson
Jesse Glick assigned JENKINS-6097 to Kohsuke Kawaguchi Update Center could upgrade plugins to latest-release-for-my-Hudson Change By: Jesse Glick (06/Nov/14 2:57 PM) Assignee: KohsukeKawaguchi 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-24213) Jenkins slaves repeatable disconnect and connect during startup, related to remoting/nio or swarm plugin
Andy Chen commented on JENKINS-24213 Jenkins slaves repeatable disconnect and connect during startup, related to remoting/nio or swarm plugin Please, please fix this bug. I keep seeing this issue every 3 days for my 30+ Slaves after upgraded to build 1.587. It happened on previous build but not that frequent. 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-25473) Unnecessarily slow serialized I/O for top-level item loading in loadTasks
dogfood commented on JENKINS-25473 Unnecessarily slow serialized I/O for top-level item loading in loadTasks Integrated in jenkins_main_trunk #3798 JENKINS-25473 Retroactively filing #1439. (Revision bcdae275d049639cfd6d4892fe03d61e5a59d466) Result = UNSTABLE jesse glick : bcdae275d049639cfd6d4892fe03d61e5a59d466 Files : changelog.html 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] [jobconfighistory-plugin] (JENKINS-25456) POSTing to existing job config.xml results in 'java.io.IOException: Failed to persist config.xml'
Jake Carlson
commented on JENKINS-25456
POSTing to existing job config.xml results in java.io.IOException: Failed to persist config.xml
Is this perhaps related to https://github.com/jenkinsci/jenkins/commit/2b9cfe3a475cc5851fe91d33a917f3db1e33ef23 ? I have attempted to use a Groovy script in Jenkins console. I can retrieve the job by calling 'hudson.model.Hudson.instance.getItem('my-job');'. But once I update the job config.xml I can no longer do so without reloading all configuration files from disk (which isn't feasible for us). It seems that the removal of doReload in AbstractItem.updateByXml is causing Jenkins to purge the job from memory?
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] [multijob-plugin] (JENKINS-25474) MultiJob Plugin not recognizing job failures for continuation condition
Bryan Grant created JENKINS-25474 MultiJob Plugin not recognizing job failures for continuation condition Issue Type: Bug Assignee: Unassigned Attachments: multijob1.tiff, multijob2.tiff Components: multijob-plugin Created: 06/Nov/14 4:38 PM Description: We have setup a multijob build with multiple phases in which each job should move to the next phase in the event of a failure. When a failure is detected, the multijob is continuing to execute the downstream jobs rather than exit. I tested the reverse with continuing on a success and that works but not the continue on a failure. Please advise, images of the job run are attached. Environment: Jenkins ver. 1.554.10.1 (Jenkins Enterprise by CloudBees 14.05) RHEL 6.5 java version 1.7.0_51 Project: Jenkins Labels: plugin multijob Priority: Critical Reporter: Bryan Grant 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] [teamconcert-plugin] (JENKINS-25475) Jenkins is not aware of personal builds, personal build failurse mark Jenkins job status as failed
ravi khetani created JENKINS-25475 Jenkins is not aware of personal builds, personal build failurse mark Jenkins job status as failed Issue Type: Bug Assignee: Unassigned Attachments: support.zip Components: teamconcert-plugin Created: 06/Nov/14 5:05 PM Description: When initiating personal builds from rtc, only the user that initiated a build can see build failures for personal builds. In Jenkins the overall build status is updated to broken if a personal build fails, as Jenkins is not aware of the Personal Build concept Environment: Support file attached Project: Jenkins Labels: scm plugin Priority: Major Reporter: ravi khetani 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-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Andy Pham commented on JENKINS-7695 archiving throws hudson.util.IOException2: java.io.IOException: request to write 3977 bytes exceeds size in header of 41955006 Also see this in 1.582 11:33:56 ERROR: Failed to archive artifacts: _test/** 11:33:56 java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: request to write '1757' bytes exceeds size in header of '132283' bytes for entry '_test/output.log' 11:33:56 at hudson.FilePath.copyRecursiveTo(FilePath.java:2039) 11:33:56 at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) 11:33:56 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:217) 11:33:56 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) 11:33:56 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 11:33:56 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) 11:33:56 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) 11:33:56 at hudson.model.Build$BuildExecution.post2(Build.java:183) 11:33:56 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) 11:33:56 at hudson.model.Run.execute(Run.java:1770) 11:33:56 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 11:33:56 at hudson.model.ResourceController.execute(ResourceController.java:89) 11:33:56 at hudson.model.Executor.run(Executor.java:240) 11:33:56 Caused by: java.util.concurrent.ExecutionException: java.io.IOException: request to write '1757' bytes exceeds size in header of '132283' bytes for entry '_test/output.log' 11:33:56 at hudson.remoting.Channel$3.adapt(Channel.java:772) 11:33:56 at hudson.remoting.Channel$3.adapt(Channel.java:767) 11:33:56 at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) 11:33:56 at hudson.FilePath.copyRecursiveTo(FilePath.java:2037) 11:33:56 ... 12 more 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] [change-assembly-version-plugin] (JENKINS-25476) Encoding problem when writing file on windows.
Leonardo Kobus created JENKINS-25476 Encoding problem when writing file on windows. Issue Type: Bug Assignee: Unassigned Components: change-assembly-version-plugin Created: 06/Nov/14 5:46 PM Description: Andy Hush says: I'm having the sample problem. Version 1.4.1 of the plug-in. A question mark is ... I'm having the sample problem. Version 1.4.1 of the plug-in. A question mark is inserted as the first character of every AssemblyInfo.cs. msbuild fails with: Properties\AssemblyInfo.cs(1,1): error CS0116: A namespace cannot directly contain members such as fields or methods I think it's a real question mark, not a unicode indicator. EDIT: Looking at the code, FilePath.readToString() and write() are used. According to the documentation, readToString() uses "current system encoding". For Windows, that is code page 932, aka windows-31j. However, my AssemblyInfo.cs files are UTF-8. I believe that Visual Studio uses UTF-8 by default. So perhaps the solution is to use core Java classes that can deal with different encodings. I am not a Java programmer, so I don't know what those would be. Source : https://wiki.jenkins-ci.org/display/JENKINS/Change+Assembly+Version Environment: Windows Project: Jenkins Priority: Minor Reporter: Leonardo Kobus 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] [artifactdeployer-plugin] (JENKINS-25461) ArtifactDeployer breaks under recent build(s) of Jenkins
Daniel Beck commented on JENKINS-25461 ArtifactDeployer breaks under recent build(s) of Jenkins Caused by the upgrade of the bundled JNA from 3.x to 4.x in Jenkins 1.586. Plugin needs to bundle its own JNA (and prefer using that) or upgrade the library this plugin expects. 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] [github-oauth-plugin] (JENKINS-25459) Authorization by Github Commiter strategy broken.
Heiko Heijenga commented on JENKINS-25459 Authorization by Github Commiter strategy broken. Same problem here. Everyone in the 'Admin User Names' list can use Jenkins fine, anybody who's not receives exceptions all over the place. 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] [azure-slave-plugin] (JENKINS-24649) Allow to stop / deallocate and start / allocate existing VMs on demand
suresh nallamilli commented on JENKINS-24649 Allow to stop / deallocate and start / allocate existing VMs on demand I am working on it and will provide you ETA in next week. 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] [hp-application-automation-tools-plugin] (JENKINS-25477) Unable to connect to ALM 12.01
Winston Polhamus created JENKINS-25477 Unable to connect to ALM 12.01 Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 06/Nov/14 6:46 PM Description: When attempting to initiate an ALM Performance Center test, I receive: "Building on master in workspace /opt/jenkins/jobs/appserv-nationnow_perf-test_stage/workspace Failed login to ALM Server URL: https://hpalm.x.xxx.net/qcbin/. Exception: com.hp.application.automation.tools.common.SSEException: java.net.ConnectException: Connection refused Empty Results" Environment: Jenkins 1.572 Linux w/ Windows 2008 R2 slave, HP ALM PC 12.01 Project: Jenkins Priority: Major Reporter: Winston Polhamus 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] [clang-scanbuild-plugin] (JENKINS-17092) Clang Scan-Build Plugin needs updating to handle newer scan-build output directory layout
Paul Eipper commented on JENKINS-17092 Clang Scan-Build Plugin needs updating to handle newer scan-build output directory layout Please apply the fix, it's been available as a pull request on github since 2013: https://github.com/jenkinsci/clang-scanbuild-plugin/pull/3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-23736) Emulator plugin can not run emulator if user is not logged on to desktop
Vitaliy Popov commented on JENKINS-23736 Emulator plugin can not run emulator if user is not logged on to desktop https://github.com/stisti/jenkins-app - it is help me!!! 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] [azure-slave-plugin] (JENKINS-24649) Allow to stop / deallocate and start / allocate existing VMs on demand
Sebastian Schuberth commented on JENKINS-24649 Allow to stop / deallocate and start / allocate existing VMs on demand Looking forward to it, 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] [core] (JENKINS-25424) Exception when editing nodes
Oleg Nenashev updated JENKINS-25424 Exception when editing nodes Change By: Oleg Nenashev (06/Nov/14 7:59 PM) Assignee: LevonSaldamli Component/s: xvnc-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-25261) Missing dependency on RPM package
Oleg Nenashev commented on JENKINS-25261 Missing dependency on RPM package Could you provide the full stack trace? IMO, it's better to make the core fonts-tolerant (e.g. fallback to a default font) instead of adding dependencies into RPM 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-25204) Unhandled UsernameNotFoundException may appear in BasicAuthenticationFilter::doFilter()
Oleg Nenashev assigned JENKINS-25204 to Oleg Nenashev Unhandled UsernameNotFoundException may appear in BasicAuthenticationFilter::doFilter() Change By: Oleg Nenashev (06/Nov/14 8:03 PM) Assignee: OlegNenashev 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] [hp-application-automation-tools-plugin] (JENKINS-25478) HTTPS to HP ALM PC
Winston Polhamus created JENKINS-25478 HTTPS to HP ALM PC Issue Type: New Feature Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 06/Nov/14 8:13 PM Description: it appears that when integrating directly to HP Performance Center, only HTTP is supported. In our environment we would require HTTPS support. Environment: HP ALM PC 12.01, Jenkins 1.572 Linux w/ Windows Slave Project: Jenkins Priority: Minor Reporter: Winston Polhamus 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] [junit-plugin] (JENKINS-24006) Customize number of Junit test failures that affect weather
Jesse Glick updated JENKINS-24006 Customize number of Junit test failures that affect weather Change By: Jesse Glick (06/Nov/14 8:42 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24006) Customize number of Junit test failures that affect weather
Jesse Glick started work on JENKINS-24006 Customize number of Junit test failures that affect weather Change By: Jesse Glick (06/Nov/14 8:42 PM) Status: Open InProgress 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] [junit-plugin] (JENKINS-24006) Customize number of Junit test failures that affect weather
Jesse Glick assigned JENKINS-24006 to Jesse Glick Customize number of Junit test failures that affect weather Change By: Jesse Glick (06/Nov/14 8:42 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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build
Ivan Andrus commented on JENKINS-13458 Add switch to set reference build always as the latest build I'm not sure what you mean by pressing build again getting rid of the unstable status. Simply pressing "Build Now" on the project does not work for me--it still uses the old reference build, and therefore fails again. Am I missing something? 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] [multijob-plugin] (JENKINS-25479) Multi-configuration project jobs cannot be opened if the multijob has been opened from some view
Mykola Grybyk created JENKINS-25479 Multi-configuration project jobs cannot be opened if the multijob has been opened from some view Issue Type: Bug Assignee: Unassigned Attachments: multijobPlugin-no-job-in-link.png Components: multijob-plugin Created: 06/Nov/14 9:35 PM Description: 1. create list view 2. create multijob in it 3. create Multi-configuration project job with some axis (at least one, any type) 4. add multijob phase with job created on step#3 5. open multijob, link should be like http://HOST:PORT/view/MY_VIEW/job/MULTIJOB/ 6. open multijob phase job, link is like http://HOST:PORT/view/MY_VIEW/axis1=someValue/ ACTUAL RESULT: 404 there is no job/job_name in link, so link is not valid and cannot be opened. EXPECTED RESULT: link should be like http://HOST:PORT/view/MY_VIEW/job/MULTICONFIG-JOB/axis1=someValue/ Environment: Jenkins 1.580.1, multijob plugin 1.14 Project: Jenkins Priority: Minor Reporter: Mykola Grybyk 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] [junit-plugin] (JENKINS-24006) Customize number of Junit test failures that affect weather
SCM/JIRA link daemon commented on JENKINS-24006 Customize number of Junit test failures that affect weather Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/tasks/junit/JUnitResultArchiver.java src/main/resources/hudson/tasks/junit/JUnitResultArchiver/config.jelly src/test/java/hudson/tasks/junit/JUnitResultArchiverTest.java src/test/resources/hudson/tasks/junit/JUnitResultArchiverTest/MockTestDataPublisher/config.jelly http://jenkins-ci.org/commit/junit-plugin/e6416e34c0987a839d3dc2a34938dd1d2ac0d035 Log: FIXED JENKINS-24006 Changes to healthScaleFactor were not actually being saved. Ripping out the archaic manual form binding code and replacing with the modern simplified scheme. 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] [junit-plugin] (JENKINS-24006) Customize number of Junit test failures that affect weather
SCM/JIRA link daemon resolved JENKINS-24006 as Fixed Customize number of Junit test failures that affect weather Change By: SCM/JIRA link daemon (06/Nov/14 10:03 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] [p4-plugin] (JENKINS-25480) Swarm review callback trigger too many times for matrix project
Michael Rose created JENKINS-25480 Swarm review callback trigger too many times for matrix project Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 06/Nov/14 10:25 PM Description: When the Jenkins job associated with a review is a matrix job, each configuration triggers the Swawrm callback url. Which leads to n+1 (number of configuation + parent configuration) callbacks. This leads to duplicate activity entries and duplicate email alerts. Since the failed/passed test link in swarm can only reference one Jenkins build (and since that build is the parent configuration), the job should only be triggering for the parent configuration. Environment: P4 plugin version: 1.0.16 Project: Jenkins Priority: Minor Reporter: Michael Rose 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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build
Ulli Hafner commented on JENKINS-13458 Add switch to set reference build always as the latest build @Ivan: if this feature will be implemented then you can press "Build now" again to reset the build status to stable. This is not really desired, feels like a bit of cheating to me... 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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build
Ulli Hafner commented on JENKINS-13458 Add switch to set reference build always as the latest build @Thomas: I can can give you some pointers on where to start if you are still interested... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle-plugin] (JENKINS-25481) API call results empty waring messages
Alexander Obuhovich
created JENKINS-25481
API call results empty waring messages
Issue Type:
Bug
Assignee:
Ulli Hafner
Attachments:
checkstyle-warnings.xml, Jenkins_CheckStyleHTML.png, Jenkins_CheckStyleJSON.png
Components:
checkstyle-plugin
Created:
06/Nov/14 10:31 PM
Description:
I have a build with checkstyle error message. The checkstyle.xml is produced by PHP_CodeSniffer.
See from attached how that build looks on the web and in JSON response (the warnings are represented by {}), so it's known that warnings exist, but their messages are missing.
Project:
Jenkins
Labels:
api
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] [checkstyle-plugin] (JENKINS-25481) API call results empty waring messages
Alexander Obuhovich commented on JENKINS-25481 API call results empty waring messages Same issue is with PMD report (PHP Mess Detector). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle-plugin] (JENKINS-25481) API call results empty waring messages
Ulli Hafner resolved JENKINS-25481 as Not A Defect API call results empty waring messages This is by design (for all Jenkins API calls?). If you use depth=0, then no sub entities are show in the API. If you use depth=1 then the sub entities are shown. checkstyleResult/api/json?depth=1 Change By: Ulli Hafner (06/Nov/14 10:36 PM) Status: Open Resolved Resolution: NotADefect 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] [active-directory-plugin] (JENKINS-24248) Cannot configure Active Directory Bind DN or Bind Password
Jeff Thornsen commented on JENKINS-24248 Cannot configure Active Directory Bind DN or Bind Password This is causing an issue for me attempting to stand up a Jenkins instance on Windows 7. If the Jenkins service is running as a local user, even if the machine is joined to a domain, it appears that the Active Directory plugin fails to look up the AD information. I believe we need the ability to specify the bindName, bindPassword, and groupLookupStrategy under the Advanced button, even when running Jenkins on Windows. Running the service as a domain user has no issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25482) Extended Email plugin triggers can't be configured
ajbanck created JENKINS-25482 Extended Email plugin triggers cant be configured Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 06/Nov/14 10:46 PM Description: When using the Extended Email plugin some triggers can't be configured. Checked the following triggers to be working with the ext. mail plugin but not supported by the DSL: Always FirstUnstable FixedUnhealthy SecondFailure StatusChanged Project: Jenkins Priority: Minor Reporter: ajbanck 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-25235) NPE on run()
David Tanner commented on JENKINS-25235 NPE on run() I am not sure how that could happen while the trigger is running. That line is helper.run(), and when .start() is called helper is initialized, or else it never calls super.start(). Are there more errors in the logs than that 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] [ghprb-plugin] (JENKINS-25227) Trigger build with comment when previous was ok
David Tanner commented on JENKINS-25227 Trigger build with comment when previous was ok What doest your global config have set for Test phrase? 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-25483) Build Pipeline version could be created after Environment Variables variables were injected
Rafael Ximenes created JENKINS-25483 Build Pipeline version could be created after Environment Variables variables were injected Issue Type: Improvement Assignee: Unassigned Components: build-pipeline-plugin Created: 06/Nov/14 10:56 PM Description: I'm trying to configure a "Build Pipeline Version" to an ANT JOB. All my tests showed the same: the Pipeline Version is created right after the SCM step and BEFORE any other step that allow me to raise a new Environment Variable or execute a shell to read a file to get the version. What would be a very good step-by-step option: Run SCM Run "EnvInject Plugin" plugin (here I can parse a file, run a script, etc, it is very useful) Then run the Pipeline Version Creation It is so easy to get the POM Version in a "Maven Project" with a "Maven Job", but so painful with a freestyle job. If there's a way you have already figured out how to set the Build Pipeline Version using some info coming from files downloaded from SCM step, I'm very interested to learn. All examples I have found were about maven jobs and POM's version Thank you Rafael Project: Jenkins Labels: build-pipeline-plugin Priority: Minor Reporter: Rafael Ximenes 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] [ec2-plugin] (JENKINS-4995) Support windows AMI's in EC2 plugin
Chad Myers commented on JENKINS-4995 Support windows AMIs in EC2 plugin For anyone else using Windows Server 2008 R2 SP1 as a slave, I kept running into problems running slave.jar due to JVM complaining about memory. It turns out there's a bug in Windows Server 2008 R2 SP1 that doesn't respect the WinRM setting for MaxMemoryPerShellMB and always uses 150MB no matter what you set. You can read about this problem and download the hotfix (big button at the top of the page) here: http://support.microsoft.com/kb/2842230 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] [multijob-plugin] (JENKINS-25484) Add support for multijob to retry only failed portions of a matrix build.
Jason Matson created JENKINS-25484 Add support for multijob to retry only failed portions of a matrix build. Issue Type: New Feature Assignee: Unassigned Components: multijob-plugin Created: 06/Nov/14 11:37 PM Description: Add support for multijob to retry only failed portions of a matrix build. Project: Jenkins Labels: matrix multi-job retry Priority: Minor Reporter: Jason Matson 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] [active-directory-plugin] (JENKINS-25485) Unable to login with standard Jenkins users when Active Directory plugin is in use
Michael Rose created JENKINS-25485 Unable to login with standard Jenkins users when Active Directory plugin is in use Issue Type: Bug Assignee: Unassigned Components: active-directory-plugin Created: 06/Nov/14 11:52 PM Description: We use the Active Directory plugin as our security realm. I noticed that even with Active Directory set up as the security realm, an administrator could still create users by navigating to http//JENKINS_URL/user/USERNAME and configuring them. This is useful b/c the newly created user receives an API token which allows jobs to be triggered from scripts. Furthermore there is more control over b/c permission can be setup to restrain them from doing anything except for what they were created to do. The problem that I'm seeing is that, though authentication is successful when using the API token, an internal error still occurs when the Active Directory plugin attempts to retrieve information about the user from Active Directory. There's an argument that could be made that this is correct behavior since the user does not exist in AD, however most tools that integrate with AD also allow for the tool's internal database to be used as a fallback. I think the plugin should not error out if the user directory and configuration file exists in JENKINS_HOME/users (or however internal users are defined ???). Here is the error message I am seeing. Nov 6, 2014 5:09:15 PM jenkins.security.BasicHeaderApiTokenAuthenticator authenticate WARNING: API token matched for user mynewname but the impersonation failed org.acegisecurity.userdetails.UsernameNotFoundException: Authentication was successful but cannot locate the user information for mynewname at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:273) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:196) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:140) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:30) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:282) at jenkins.security.BasicHeaderApiTokenAuthenticator.authenticate(BasicHeaderApiTokenAuthenticator.java:31) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:72) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at
[JIRA] [ghprb-plugin] (JENKINS-25235) NPE on run()
Kanstantsin Shautsou commented on JENKINS-25235 NPE on run() Yes, many, for the same job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23543) Launchctl does not load Jenkins on OS X 10.10 Yosemite
Mario Harvey commented on JENKINS-23543 Launchctl does not load Jenkins on OS X 10.10 Yosemite pull request: https://github.com/jenkinsci/jenkins/pull/1457 I tested on Yosemite, Mavericks, and Mountain Lion. 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] [analysis-core-plugin] (JENKINS-13458) Add switch to set reference build always as the latest build
Ivan Andrus commented on JENKINS-13458 Add switch to set reference build always as the latest build @Ulli, now I understand what you are saying. But that's exactly what I want because the warnings I get are often not really valid and/or impossible to fix (e.g. bugs in the tools). Some are good though, and so I want to know about new warnings so I can potentially fix them. But if I don't want to fix them I don't want to be constantly pestered. 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] [git-client-plugin] (JENKINS-20153) git plugin throws error if you don't specify a specific branch name
SCM/JIRA link daemon commented on JENKINS-20153 git plugin throws error if you dont specify a specific branch name Code changed in jenkins User: Stephan Pauxberger Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/00e36c78e050bb0c77932b2ee95800691a95b040 Log: (Re-)activated 'shared' clones. Shared now works as a special case of references. Fixed test for JENKINS-20153 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-client-plugin] (JENKINS-25387) JGit in git client should support reference repositories
SCM/JIRA link daemon commented on JENKINS-25387 JGit in git client should support reference repositories Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/Branch.java src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/main/java/org/jenkinsci/plugins/gitclient/CloneCommand.java src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/f330cd9e4dc1301830b432e26cd313ca7b812aaf Log: Merge pull request #151 from pauxus/jgit-references JENKINS-25387 Allow reference repositories for JGit as well. Compare: https://github.com/jenkinsci/git-client-plugin/compare/6296a9a6fcd3...f330cd9e4dc1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Jan Hollevoet commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection We are at v1.559 and intensively use the dist-fork plugin. This error hit us severely. Since a fixed port is used for JNLP slave agents (Global Security), the error did not occur anymore. 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.
