Kohsuke linked to ASF's guidelines for use of their trademarks, but I think
the section above the guidelines is more relevant:
http://www.apache.org/foundation/marks/#principles
In particular, I would call out this sentence (emphasis added):
To avoid infringing ASF's marks, you should verify
Wouldn't it better to replicate from Artifactory? What if you had multiple
Jenkins jobs that deployed artifacts? Then each one would have to be
configured with multiple URLs. What something other than Jenkins jobs also
uploaded to Artifactory?
-- Dean
From: Mandeep Mehra
-∞
But not because I think black on white is better; that is a matter of
preference.
This change forces the author's preference on everyone with no way to opt
out of it for people who prefer the existing theme. Furthermore, you would
then ask the maintainers of other plugins to have to change
performance suffered badly when I had emptied the pool of random data. I
think that is why Stephen recommends using /dev/urandom so that your program
won't block while waiting for random data.
Mark Waite
On Tue, Jul 29, 2014 at 10:44 PM, Dean Yu dean...@gmail.com
javascript:_e(%7B%7D,'cvml
in the queue: SSH server support.
On 30 July 2014 15:53, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
On 30 July 2014 14:48, Dean Yu dean...@gmail.com wrote:
the problem goes away by downgrading the library.
It would be great if you could determine whether the new version
Hi folks,
We just upgraded our cluster from 1.509.4 to 1.554.3, and discovered a
significant increase in our build times. Builds that typically took ~50 to
complete started taking ~90 minutes to finish, sometimes spiking to 2
hours. While researching, we found this JIRA[1] which reported that
I'm guessing the desired value is to be able to drop a new version of
stapler into an older version of Jenkins. Providing this value as a plugin
is sort of an implementation detail. If I exploded an older jenkins.war,
dropped in new stapler jars, and repackaged the war, would that work?
-- Dean
Withers ch...@simplistix.co.uk wrote:
On 17/05/2013 21:50, Dean Yu wrote:
However, if I do the following on the job that created the artifacts
used by the matrix build:
build = job.getLastBuild()
for (fp in build.getFingerPrints()) {
println fg.getUsages();
}
...I do see the matrix children
On 5/16/13 1:29 AM, Chris Withers ch...@simplistix.co.uk wrote:
On 16/05/2013 09:19, Chris Withers wrote:
Nope, don't think that's it...
Taking one matrix job as an example, I have Record fingerprints to
track usage turned on, but if I do
job.getLastBuild().getBuildFingerprints() on that
Ah. Sounds like you're working with freestyle or matrix jobs. Those need
to have the Record fingerprints to track usage option configured
explicitly in the projects. It doesn't happen automatically like it does
for Maven projects.
-- Dean
On 5/14/13 8:18 AM, Chris Withers
Hi Chris,
From a Fingerprint instance, you can call getOriginal() to get a
Fingerprint.BuildPtr object that refers to the source of fingerprint. (Or
null if the fingerprint was generated outside of Jenkins.) You can also
call getJobs() on a Fingerprint object to get a list of job names that
them, how do I get the fingerprints of those artifacts
starting from a build object?
cheers,
Chris
On 14/05/2013 16:56, Dean Yu wrote:
Hi Chris,
From a Fingerprint instance, you can call getOriginal() to get a
Fingerprint.BuildPtr object that refers to the source of fingerprint.
(Or
null
as part of the remote calling chain. I find it
hard to believe that you can achieve the necessary savings, at lease
purely from the remoting layer. It seems that you'd need some code in
Jenkins to help tune the prefetch algorithm.
-- Dean
On 5/12/13 8:08 AM, Dean Yu dean...@gmail.com wrote:
Do
Do you also prefetch inherited classes? I wonder if that would help. Also, can
you measure the number of classes that were prefetched but never used?
-- Dean
On Saturday, May 11, 2013 2:10:18 PM UTC-7, Kohsuke Kawaguchi wrote:
(Context: see https://github.com/jenkinsci/remoting/pull/10)
I think you're on the right track. I think that you do need to save off the
new instance in getNewInstance(), so that when the user reconfigures, you
can call cancel() on it to cancel the pending run. Then, instead of calling
doAperiodicRun(), call doRun() which is inherited from AperiodicWork.
I've asked for this before. Please consider defining a git API that allows
for swapping in different client implementations. We've seen from the
Subversion plugin that some people would prefer the ability to use the native
client, while others are OK with SvnKit.
-- Dean
From: Emanuele
: AbstractTestResultAction#getFailedTests()
On 01/24/2013 11:17 AM, Dean Yu wrote:
MetaTabulatedResult is in the inheritance chain for CaseResult.
Not that I can see. I think the proposed return type was List? extends
hudson.tasks.test.TestResult.
Type erasure should allow existing callers
Here's the commit where this was added:
https://github.com/jenkinsci/jenkins/commit/f9823e39d17debd2e914ce13cdeec3b43581f09e
I would call this a case of poor abstraction. Seems like the signature should
return List? extends MetaTabulatedResult.
-- Dean
From: Nalin Makar
Hi David,
Thanks for pointing this out. I think it's worth creating a Considerations
sub-topic of the post-commit hook on the page that has the details you've
described before. Please go ahead and update the wiki.
-- Dean
From: David Pärsson
On 12/6/12 6:31 PM, Jesse Glick jgl...@cloudbees.com wrote:
On 12/06/2012 08:03 PM, Dean Yu wrote:
I'm not a big fan of the shared plugin model. As a user, I've gotten
bitten way to many times by compatibility problems this causes.
Then report those problems and drive them to get fixed please
Hi folks, specifically rpetti and kutzi,
I'd like to do some work to provide a post-commit hook for the Perforce
plugin[1]. Looking through that code base, it's looks like it started life
modeled on the Subversion plugin, but it has diverged significantly. I'm not
going to attempt to
which is used by IRC, Jabber and more.
Have you thought about that approach? It offers IMO a lot of advantages
over the having-it-in-core approach. Most notably to offer bug fixes/new
feature without the need to update the core.
cheers
Kutzi
Am 06.12.2012 22:54, schrieb Dean Yu:
Hi folks
for different SCM branches.
Using the MultiJob plugin allows the main (parent) upstream project to know
when all of its requested compiles and testing has finished.
I hope that this makes sense.
Thanks,
Marek Gimza
On Fri, Sep 21, 2012 at 4:31 PM, Dean Yu
d...@shutterfly.commailto:d...@shutterfly.com
But also, support for concurrent matrix builds were added in 1.466:
What's new in 1.466 (2012/05/28)
* Maven plugin: expand variables in Room POM field (issue
13822https://issues.jenkins-ci.org/browse/JENKINS-13822)
* Exposed plugin manager and update center to the REST API
* Enabled
The second point could be what's happening.
During our investigations into this, I was noticing a lot of IOException:
Resource temporarily unavailable exceptions being raised when sending the
Unexport command. When I noticed this, I modified the TCP buffer sizes via
sysctl to see if we were
And the confirm the first item, clearing the flag in a finally block makes
it so the probe isn't tripped. So not a re-entrant call to send then.
-- Dean
On 6/7/12 7:41 PM , Dean Yu d...@yahoo-inc.com wrote:
The second point could be what's happening.
During our investigations into this, I
What latest release was this fixed in? We usually wait for a bug fix to be
publicly available for a week or two before it's considered for inclusion
in an LTS.
-- Dean
On 5/17/12 2:50 AM , Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
On 17 May 2012 10:13, Vojtech Juranek
On 4/16/12 12:21 PM , Mirko Friedenhagen mfriedenha...@gmail.com wrote:
Hello everybody,
I just installed
https://wiki.jenkins-ci.org/display/JENKINS/LabeledTestGroupsPublisher+Plugin
and now links for tests are just going into nirvana (see
This pull request[1] proposes an extension point that allows extra buttons
to be put on the project page, in the area with the Disable build and
Keep this build forever buttons.
My comment when I reviewed it was that actions added to this area wouldn't
be supported by the new context menu
Very nice!
-- Dean
On 2/28/12 4:22 PM , Kohsuke Kawaguchi kkawagu...@cloudbees.com wrote:
I've pushed this in
https://github.com/jenkinsci/jenkins/tree/breadcrumb
Most of the list view links now support navigation menus (it's just a
matter of adding class='model-link' to the a tag),
It would be great if the menu could be activated from any link to a model
object, not just from the breadcrumb bar. For example, there have been many
times I wished I could quickly jump to the configuration or console of a job
from the upstream/downstream jobs section of a page. We could get rid
31 matches
Mail list logo
