Plus, #2 only stops new installs All three items seem good practice.
On Wed, Nov 2, 2016 at 10:35 AM, Stephen Connolly
wrote:
> I think it would be irresponsible of the project to continue to publish a
> plugin with a known vulnerability. If and admin really wants to install it
> they can pul
First, this probably should be on the -user list.
Second, it seems strange to me to have a non-bootstrapped node which
already has Jenkins on it.
On Fri, Sep 23, 2016 at 2:29 PM, Irfan Sayed wrote:
> please suggest
> Regards
>
>
> On Fri, Sep 23, 2016 at 11:23 AM, Irfan Sayed wrote:
>>
>> Hi,
It may be orphaned, but people are committing and submitting pull
requests to it as recently as a month or two ago.
I guess I just don't understand why bother to deprecate a particular
plugin that is in use with 3500+ installations. There is support for
migrating old plugin configuration, but it's
This should be on the jenkinsci-user list, not on the jenkinsci-dev list.
Jenkins Distributed Builds are unrelated to Apache Maven parallel builds.
On Wed, Apr 20, 2016 at 4:09 PM, Foyzul Hassan wrote:
> Hi All,
>
> For our research work we need to build large open source projects and in
> that
e
> Jenkins-ci.org website was last overhauled, but I am guessing at least 5
> years ago.
>
> On Tue, Oct 6, 2015 at 8:34 PM, jieryn wrote:
>>
>> Seriously, this idea is so obvious I almost hate to mention it.
>>
>> Make the site a repository and accept pull reque
Ok, sorry. I really don't like anything that certain people are
putting out. If I misread this, I apologize. I haven't had time to
respond in all the 454 threads about redesign.
I don't like the direction any of this is going and I finally have time to type.
On Tue, Oct 6, 2015 at 11:34 PM, Micha
Seriously, this idea is so obvious I almost hate to mention it.
Make the site a repository and accept pull requests. How hard is that?
I bet the site would improve drastically with small and simple pull
requests, but also large changes which let users really go wild.
Jenkins was made great by Koh
(replies inline)
On Tue, Oct 6, 2015 at 11:27 PM, Michael Neale wrote:
> (replies inline)
>
> On Wednesday, October 7, 2015 at 2:22:47 PM UTC+11, Jesse Farinacci wrote:
>>
>> Frankly speaking, and I'm sorry to be so honest, but your ideas are
>> quite simply retrograde. If you're going to redesig
Aside from what I've already said:
* mobile first; responsive
* servlet 3.0/ jax-rs 1.1
* pretend stapler never existed
* pretend our icon system never existed; use font-awesome
* make keyboard shortcuts (see my plugin) part of the base
* make the entire UI based on jax-rs so we can re-skin it eas
Frankly speaking, and I'm sorry to be so honest, but your ideas are
quite simply retrograde. If you're going to redesign the site, can you
please not make it look like it was invented back in 2000? Seriously.
Make it responsive by default. Use font icons. Get rid of stapler, use
servlet 3.0. Can we
The king is dead. Long live the king!
On Tue, Oct 6, 2015 at 6:39 PM, Kohsuke Kawaguchi wrote:
> Hello, fellow Jenkins developers,
>
> In an continuing effort to remove/reduce SPoF and bottlenecks, I'm
> announcing that I'm handing over the crown of the remoting lead to Oleg
> Nenashev.
>
> I've
My $0.02 is that you're totally on the wrong track entirely. In the
redesign. In the claim that the website is shit. I don't think I've
ever disagreed more with a single person not working at Oracle.
On Tue, Oct 6, 2015 at 7:02 PM, Gus Reiber wrote:
> Hey all,
>So a related thread exists here
https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Report+Card
I wrote a backend job that produces a report of plugins which
"probably" are neglected. Neglected in this context being a plugin
with required core that is very old.
On Mon, Oct 5, 2015 at 5:25 PM, Oleg Nenashev wrote:
> I have 1-yea
Sorry about the name, I guess I thought more people would be familiar
with satellite technology than actually are.. ;-) Now I'm glad I
didn't choose first choice of KH-10.
+1 project rename
On Thu, Sep 17, 2015 at 6:33 AM, Daniel Beck wrote:
>
> On 17.09.2015, at 11:03, Baptiste Mathus wrote:
>
Sigh. You must be, you must be the change you want to see in the world. :-)
On Thu, Sep 10, 2015 at 2:07 PM, jieryn wrote:
> You must the the change you want to see in the world. :-)
>
> On Thu, Sep 10, 2015 at 2:06 PM, Antonio Manuel Muñiz Martín
> wrote:
>> 2015-09-10 19:2
You must the the change you want to see in the world. :-)
On Thu, Sep 10, 2015 at 2:06 PM, Antonio Manuel Muñiz Martín
wrote:
> 2015-09-10 19:27 GMT+02:00 jieryn :
>> https://github.com/jenkinsci/keyhole
>
> Not working due to https://developers.google.com/maps/support/kmlmaps
>
https://github.com/jenkinsci/keyhole
On Thu, Sep 10, 2015 at 11:55 AM, Alyssa Tong wrote:
> Hello,
>
> I would like to request to have a map like THIS on jenkinsci.org. This would
> be good for the community to know where some local Jenkins activities are in
> case they'd like to join. It's also
https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Report+Card
On Jun 9, 2015 04:24, "Stephen Connolly"
wrote:
> In pseudocode:
>
> FOR repo IN (SELECT repo FROM github WHERE last_commit < now - 3 months)
> CREATE PULL REQUEST update base jenkins version to LTS-1
> END
> WAIT 1 month
>
> I sug
It's interesting, but ultimately seems to me to be not correct.
The goal of the java -jar jenkins.war is just ease of use. It isn't
about tuning it to squeeze out a modest 12% improvement in a single
scenario. And you still would face Stepen's very real JIT argument.
Additionally, these gains are
It's you.
$ time wget
http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi
--2014-05-12 12:17:11--
http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi
Resolving updates.jenkins-ci.org... 199.193.196.24
Connecting to updates.
I upgraded all plugins, including Subversion and its dependencies.
After a few hours of builds, I do not see anything awry. It seems
good. Great job!
I'm using Jenkins LTS 1.532.2.
On Mon, Feb 3, 2014 at 1:53 PM, jieryn wrote:
> I'll give the 2.0 a run for its money later in the
Ok, thank you Stephen for making the doc updates. I apologize for the
harshness in my language, and now that you've documented the changes
(plus the sparse LDAP page), I can more easily see your side about the
relative externally facing impact that would require documentation
updates.. so, sorry.
good, but worse, it is deliberately obscurant.
On Sat, Feb 1, 2014 at 8:38 AM, Stephen Connolly
wrote:
> Go for it
>
>
> On Saturday, February 1, 2014, jieryn wrote:
>>
>> Is the wiki going to be updated with the changes?
>>
>> On Fri, Jan 31, 2014 at 7:25 AM,
Is the wiki going to be updated with the changes?
On Fri, Jan 31, 2014 at 7:25 AM, Stephen Connolly
wrote:
> all voted me down and suggest that we just go and release the 2.0 version.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To un
https://issues.jenkins-ci.org/browse/JENKINS-20618 - upgrade from LTS
1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException
Another LTS migration-oriented issue. It doesn't seem to be causing
trouble that I can detect visually though..
Seems most of our stuff is working on this LTS.
https://issues.jenkins-ci.org/browse/JENKINS-20586 - first browser
page load for 1.532.1-RC1 triggers JSONException
On Wed, Nov 13, 2013 at 7:00 PM, Kohsuke Kawaguchi
wrote:
> See http://jenkins-ci.org/stable-rc
>
> I still need to look at the changelog to see how to generate the updated
> one.
Complete.
On Tue, Aug 6, 2013 at 12:32 PM, prithish chanda
wrote:
> Can you please review the code once and give me commit access, my changes
> can be found @https://github.com/jenkinsci/sitemonitor-plugin/pull/4
> username :- prithishchanda
IRC: jenkins-admin : Added prithishchanda as a GitHub
27 matches
Mail list logo
