Quantcast

new plugin fork request

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

new plugin fork request

junoyoon
Hi.

I've developed a new Jenkins plugin named "simpleupdatesite-plugin"
which makes the Jenkins plugin update easy.

https://github.com/junoyoon/simpleupdatesite-plugin

Please fork it in jenkins-ci.

Thanks in advance.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: new plugin fork request

Christopher Orr
Hi there,

On 10/09/2011 19:57, junoyoon wrote:
> I've developed a new Jenkins plugin named "simpleupdatesite-plugin"
> which makes the Jenkins plugin update easy.

Isn't updating plugins already very easy? :)
Can you perhaps describe a bit more what the plugin does, or show some
screenshots?


> https://github.com/junoyoon/simpleupdatesite-plugin
>
> Please fork it in jenkins-ci.

What's your GitHub username?

Also, while I note you have an "MIT License" file in your repository,
your source files are marked as "NHN PROPRIETARY" -- I'm guessing that's
not really the case.  Can you maybe fix the headers?

Regards,
Chris
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: new plugin fork request

junoyoon
Sorry for lack of explanation.

In our company(NHN) there are hundreds of Jenkins dedicated servers and thousands of projects.
Each Jenkins server is managed by each development team manually at first and 
a dedicated Jenkins engineer(me!!) supports them if they have the unsolved problems. 

While supporting such a big Jenkins farm, we have faced various Jenkins instance management problems. 
One of them was that it was hard to deploy new or updated plugins to all the Jenkins instances; especially, custom plugins made by us. 
Nobody really kept eyes on the plugin release status, unless the current plugins were not working. 
Even though they noticed it, they easily lost their way while checking more than 400 plugins.

Another problem was that it was hard to give good enough instructions to the each team 
since there were few developers who could understand the plugin usage completely. 
It was even more difficult to Koreans who are not good at English.

So a year ago, we decided to make our own Jenkins support plugin named "simpleupdatesite" which exposes the mandatory plugin update status, announcement and "Ask a support" button in the main page of the Jenkins. They all connect to our custom Jenkins support site and download our own updatesite.json and announcement rss entries. find the attachment for the screenshot.

Even though the this plugin seems to use a different mechanism, Actually It's not.. 
It uses the update site extension point which Jenkins provides.

It is successfully deployed to all Jenkins instances in our company and really saves our effort. and I'd like to share this plugin in Jenkins community.
I'm writing the custom support server deployment guide as well,

And.. I fix the file headers. Now they have MIT license term.


2011/9/11 Christopher Orr <[hidden email]>
Hi there,


On 10/09/2011 19:57, junoyoon wrote:
I've developed a new Jenkins plugin named "simpleupdatesite-plugin"
which makes the Jenkins plugin update easy.

Isn't updating plugins already very easy? :)
Can you perhaps describe a bit more what the plugin does, or show some screenshots? What's your GitHub username?

Also, while I note you have an "MIT License" file in your repository, your source files are marked as "NHN PROPRIETARY" -- I'm guessing that's not really the case.  Can you maybe fix the headers?

Regards,
Chris


simpleupdatesitewidget.png (109K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: new plugin fork request

junoyoon
And.. I missed one.

My github is junoyoon.

Thanks in advance.

On 9월11일, 오후11시37분, Juno Yoon <[hidden email]> wrote:

> Sorry for lack of explanation.
>
> In our company(NHN) there are hundreds of Jenkins dedicated servers and
> thousands of projects.
> Each Jenkins server is managed by each development team manually at first
> and
> a dedicated Jenkins engineer(me!!) supports them if they have the unsolved
> problems.
>
> While supporting such a big Jenkins farm, we have faced various Jenkins
> instance management problems.
> One of them was that it was hard to deploy new or updated plugins to all the
> Jenkins instances; especially, custom plugins made by us.
> Nobody really kept eyes on the plugin release status, unless the current
> plugins were not working.
> Even though they noticed it, they easily lost their way while checking more
> than 400 plugins.
>
> Another problem was that it was hard to give good enough instructions to the
> each team
> since there were few developers who could understand the plugin usage
> completely.
> It was even more difficult to Koreans who are not good at English.
>
> So a year ago, we decided to make our own Jenkins support plugin named
> "simpleupdatesite" which exposes the mandatory plugin update status,
> announcement and "Ask a support" button in the main page of the Jenkins.
> They all connect to our custom Jenkins support site and download our own
> updatesite.json and announcement rss entries. find the attachment for the
> screenshot.
>
> Even though the this plugin seems to use a different mechanism, Actually
> It's not..
> It uses the update site extension point which Jenkins provides.
>
> It is successfully deployed to all Jenkins instances in our company and
> really saves our effort. and I'd like to share this plugin in Jenkins
> community.
> I'm writing the custom support server deployment guide as well,
>
> And.. I fix the file headers. Now they have MIT license term.
>
> 2011/9/11 Christopher Orr <[hidden email]>
>
>
>
>
>
>
>
> > Hi there,
>
> > On 10/09/2011 19:57, junoyoon wrote:
>
> >> I've developed a new Jenkins plugin named "simpleupdatesite-plugin"
> >> which makes the Jenkins plugin update easy.
>
> > Isn't updating plugins already very easy? :)
> > Can you perhaps describe a bit more what the plugin does, or show some
> > screenshots?
>
> >  https://github.com/junoyoon/**simpleupdatesite-plugin<https://github.com/junoyoon/simpleupdatesite-plugin>
>
> >> Please fork it in jenkins-ci.
>
> > What's your GitHub username?
>
> > Also, while I note you have an "MIT License" file in your repository, your
> > source files are marked as "NHN PROPRIETARY" -- I'm guessing that's not
> > really the case.  Can you maybe fix the headers?
>
> > Regards,
> > Chris
>
>
>
>  simpleupdatesitewidget.png
> 108K보기다운로드
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: new plugin fork request

domi@fortysix.ch
In reply to this post by junoyoon
I like it!  +1

On 11.09.2011, at 16:37, Juno Yoon wrote:

Sorry for lack of explanation.

In our company(NHN) there are hundreds of Jenkins dedicated servers and thousands of projects.
Each Jenkins server is managed by each development team manually at first and 
a dedicated Jenkins engineer(me!!) supports them if they have the unsolved problems. 

While supporting such a big Jenkins farm, we have faced various Jenkins instance management problems. 
One of them was that it was hard to deploy new or updated plugins to all the Jenkins instances; especially, custom plugins made by us. 
Nobody really kept eyes on the plugin release status, unless the current plugins were not working. 
Even though they noticed it, they easily lost their way while checking more than 400 plugins.

Another problem was that it was hard to give good enough instructions to the each team 
since there were few developers who could understand the plugin usage completely. 
It was even more difficult to Koreans who are not good at English.

So a year ago, we decided to make our own Jenkins support plugin named "simpleupdatesite" which exposes the mandatory plugin update status, announcement and "Ask a support" button in the main page of the Jenkins. They all connect to our custom Jenkins support site and download our own updatesite.json and announcement rss entries. find the attachment for the screenshot.

Even though the this plugin seems to use a different mechanism, Actually It's not.. 
It uses the update site extension point which Jenkins provides.

It is successfully deployed to all Jenkins instances in our company and really saves our effort. and I'd like to share this plugin in Jenkins community.
I'm writing the custom support server deployment guide as well,

And.. I fix the file headers. Now they have MIT license term.


2011/9/11 Christopher Orr <[hidden email]>
Hi there,


On 10/09/2011 19:57, junoyoon wrote:
I've developed a new Jenkins plugin named "simpleupdatesite-plugin"
which makes the Jenkins plugin update easy.

Isn't updating plugins already very easy? :)
Can you perhaps describe a bit more what the plugin does, or show some screenshots? What's your GitHub username?

Also, while I note you have an "MIT License" file in your repository, your source files are marked as "NHN PROPRIETARY" -- I'm guessing that's not really the case.  Can you maybe fix the headers?

Regards,
Chris

<simpleupdatesitewidget.png>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: new plugin fork request

Christopher Orr
In reply to this post by junoyoon
Interesting!

You now have a repo on GitHub that you can use:
https://github.com/jenkinsci/simpleupdatesite-plugin

Out of interest, how do you manage updates of Jenkins itself?  Do you
keep all instances on the same version, e.g. the new Jenkins LTS release
line?

Regards,
Chris


On 11/09/2011 16:37, Juno Yoon wrote:

> Sorry for lack of explanation.
>
> In our company(NHN) there are hundreds of Jenkins dedicated servers and
> thousands of projects.
> Each Jenkins server is managed by each development team manually at
> first and
> a dedicated Jenkins engineer(me!!) supports them if they have the
> unsolved problems.
>
> While supporting such a big Jenkins farm, we have faced various Jenkins
> instance management problems.
> One of them was that it was hard to deploy new or updated plugins to all
> the Jenkins instances; especially, custom plugins made by us.
> Nobody really kept eyes on the plugin release status, unless the current
> plugins were not working.
> Even though they noticed it, they easily lost their way while checking
> more than 400 plugins.
>
> Another problem was that it was hard to give good enough instructions to
> the each team
> since there were few developers who could understand the plugin usage
> completely.
> It was even more difficult to Koreans who are not good at English.
>
> So a year ago, we decided to make our own Jenkins support plugin named
> "simpleupdatesite" which exposes the mandatory plugin update status,
> announcement and "Ask a support" button in the main page of the Jenkins.
> They all connect to our custom Jenkins support site and download our own
> updatesite.json and announcement rss entries. find the attachment for
> the screenshot.
>
> Even though the this plugin seems to use a different mechanism, Actually
> It's not..
> It uses the update site extension point which Jenkins provides.
>
> It is successfully deployed to all Jenkins instances in our company and
> really saves our effort. and I'd like to share this plugin in Jenkins
> community.
> I'm writing the custom support server deployment guide as well,
>
> And.. I fix the file headers. Now they have MIT license term.
>
>
> 2011/9/11 Christopher Orr <[hidden email] <mailto:[hidden email]>>
>
>     Hi there,
>
>
>     On 10/09/2011 19:57, junoyoon wrote:
>
>         I've developed a new Jenkins plugin named "simpleupdatesite-plugin"
>         which makes the Jenkins plugin update easy.
>
>
>     Isn't updating plugins already very easy? :)
>     Can you perhaps describe a bit more what the plugin does, or show
>     some screenshots?
>
>
>
>         https://github.com/junoyoon/__simpleupdatesite-plugin
>         <https://github.com/junoyoon/simpleupdatesite-plugin>
>
>         Please fork it in jenkins-ci.
>
>
>     What's your GitHub username?
>
>     Also, while I note you have an "MIT License" file in your
>     repository, your source files are marked as "NHN PROPRIETARY" -- I'm
>     guessing that's not really the case.  Can you maybe fix the headers?
>
>     Regards,
>     Chris
>
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: new plugin fork request

junoyoon
Actually, we've recommended 1.395 version so far because we were not sure who will win eventually.

Now.. It's time for us to switch to Jenkins and choose one of LTS release line .. :-)

That's the one of the reason I share this plugin.

Regards


2011/9/12 Christopher Orr <[hidden email]>
Interesting!

You now have a repo on GitHub that you can use:
https://github.com/jenkinsci/simpleupdatesite-plugin

Out of interest, how do you manage updates of Jenkins itself?  Do you keep all instances on the same version, e.g. the new Jenkins LTS release line?

Regards,
Chris



On 11/09/2011 16:37, Juno Yoon wrote:
Sorry for lack of explanation.

In our company(NHN) there are hundreds of Jenkins dedicated servers and
thousands of projects.
Each Jenkins server is managed by each development team manually at
first and
a dedicated Jenkins engineer(me!!) supports them if they have the
unsolved problems.

While supporting such a big Jenkins farm, we have faced various Jenkins
instance management problems.
One of them was that it was hard to deploy new or updated plugins to all
the Jenkins instances; especially, custom plugins made by us.
Nobody really kept eyes on the plugin release status, unless the current
plugins were not working.
Even though they noticed it, they easily lost their way while checking
more than 400 plugins.

Another problem was that it was hard to give good enough instructions to
the each team
since there were few developers who could understand the plugin usage
completely.
It was even more difficult to Koreans who are not good at English.

So a year ago, we decided to make our own Jenkins support plugin named
"simpleupdatesite" which exposes the mandatory plugin update status,
announcement and "Ask a support" button in the main page of the Jenkins.
They all connect to our custom Jenkins support site and download our own
updatesite.json and announcement rss entries. find the attachment for
the screenshot.

Even though the this plugin seems to use a different mechanism, Actually
It's not..
It uses the update site extension point which Jenkins provides.

It is successfully deployed to all Jenkins instances in our company and
really saves our effort. and I'd like to share this plugin in Jenkins
community.
I'm writing the custom support server deployment guide as well,

And.. I fix the file headers. Now they have MIT license term.


2011/9/11 Christopher Orr <[hidden email] <mailto:[hidden email]>>


   Hi there,


   On 10/09/2011 19:57, junoyoon wrote:

       I've developed a new Jenkins plugin named "simpleupdatesite-plugin"
       which makes the Jenkins plugin update easy.


   Isn't updating plugins already very easy? :)
   Can you perhaps describe a bit more what the plugin does, or show
   some screenshots?



       https://github.com/junoyoon/__simpleupdatesite-plugin
       <https://github.com/junoyoon/simpleupdatesite-plugin>

       Please fork it in jenkins-ci.


   What's your GitHub username?

   Also, while I note you have an "MIT License" file in your
   repository, your source files are marked as "NHN PROPRIETARY" -- I'm
   guessing that's not really the case.  Can you maybe fix the headers?

   Regards,
   Chris




Loading...