Re: Revisiting bundled plugins

[Tom Fennelly]

On Friday, September 4, 2015 at 3:31:54 PM UTC+1, James Nord wrote:
>
> For v1 all I am saying is we need to have *a* solution to the problem 
> (not *what* that solution needs to be).  If the chosen solution is 
> pointing users to a document that explains some workarounds (possibly 
> provides links to scripts or juseppe etc) then a solution exists and I am 
> happy.
> If the solution is telling users they need an internet connection then I 
> am not happy (as that's not a solution).
>
>
+1 Agreed  

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ffe96d29-00c1-49ee-90f2-782a2c830d6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

On Friday, September 4, 2015 at 5:37:26 PM UTC+1, Daniel Beck wrote:
>
> >> For version 1 of this, can't we just document some possible solutions 
> to this problem and point the user to these solutions from inside the 
> wizard on detecting the fact that there's no internet connection? This 
> seems easy enough and we can test it over a period of time. If it's a big 
> issue we'll at least have some real data to work with. 
> > 
> > For v1 all I am saying is we need to have a solution to the problem (not 
> what that solution needs to be).  If the chosen solution is pointing users 
> to a document that explains some workarounds (possibly provides links to 
> scripts or juseppe etc) then a solution exists and I am happy. 
>
> I think we should be able to do this pretty easily. There are several 
> possible approached to deal with this, and we can point them to it. Even if 
> we just package the previous bundled plugins into a zip file and make that 
> available as a separate download, it won't be worse (except for having to 
> download two things instead of one) than what we have today. But we should 
> be able to do something much better than that (scripted bundle creation or 
> script to download selection + depenencies) with a bit of effort. 
>

This sounds like a practical approach to me +1

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/fea579ab-fa18-4255-908d-1bd5f6f5e01e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Automatic tool installation - too many choices?

[Martin Weber]

Hi all,

my crawler for cmake.org gives 31 choices for end users to install.
Would that be OK or should I try to reduce the number?

Choices for cmake are
"id": "3.3.1",
"id": "3.3.0",
"id": "3.2.3",
"id": "3.2.2",
"id": "3.2.1",
"id": "3.2.0",
"id": "3.1.3",
"id": "3.1.2",
"id": "3.1.1",
"id": "3.1.0",
"id": "3.0.2",
"id": "3.0.1",
"id": "3.0.0",
"id": "2.8.12",
"id": "2.8.11", <-- opensuse13.1 has rpms for this
"id": "2.8.10",
"id": "2.8.9",
"id": "2.8.8",
"id": "2.8.7",
"id": "2.8.6",
"id": "2.8.5",
"id": "2.8.4",
"id": "2.8.3",
"id": "2.8.2",
"id": "2.8.1",
"id": "2.8.0",
"id": "2.6.4",  <-- RHEL5/6/7 have rpms for this
"id": "2.6.3",
"id": "2.6.2",
"id": "2.6.1",
"id": "2.6.0",

Regards,
Martin

-- 
Cd wrttn wtht vwls s mch trsr.


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4550419.t3GcVMjPSd%40linux.
For more options, visit https://groups.google.com/d/optout.

Re: Commit access to jenkinsci/SCTMExecutor-plugin

[Oleg Nenashev]

In GitHub the right approach to the contribution is to create pull requests 
from forks to the master repo. In such case the plugin developers will be 
able to review and accept the pull request.

Anyway I've granted the commit permissions to Sebastian. He dhould get an 
invitation to the jenkinsci org soon.

BR, Oleg

суббота, 5 сентября 2015 г., 13:50:30 UTC+3 пользователь Thomas Fuerer 
написал:
>
> Hi seb, 
>
> I'm wondering, because I'm not able to set ownership or commit rights on 
> this project, even I'm the maintainer and owner of this project. 
>
> So maybe one of the jenkins staff can help us. 
>
> Meanwhile I saw you allready forked the project, but I'm not sure if in 
> this case the release worflow will work? 
>
> thanks, 
> Thomas 
>
> Am 21.08.2015 um 12:23 schrieb Sebastian Kornexl: 
> > Hi, 
> > 
> >   
> > 
> > when the source was on SVN I already had permissions to commit. 
> > 
> >   
> > 
> > Can I have these permission on GitHub too? 
> > 
> >   
> > 
> > Rep: https://github.com/jenkinsci/SCTMExecutor-plugin 
> > 
> > GitHub account: donkaes 
> > 
> >   
> > 
> > Time for a new release of this plugin. 
> > 
> >   
> > 
> > Thanks, 
> > 
> > Sebastian 
> > 
> >   
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "Jenkins Developers" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to jenkinsci-de...@googlegroups.com  
> > . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com
>  
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com?utm_medium=email_source=footer>.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e9ef07c6-c05d-4fd5-8293-ce64c9ab47b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Modularized JavaScript code in Jenkins Core .... how about it?

[Tom Fennelly]

Hi Surya. We're not inventing anything new for the bundling/packaging part. It 
uses Browserify for that, which is similar to Webpack.

So you are not against the idea of adding build steps to Jenkins core re 
supporting modularised JavaScript?

Sent from my iPhone

> On 6 Sep 2015, at 17:23, Surya Gaddipati  wrote:
> 
> Hi Tom,
> 
> I've been packaging all kinds of js stuff with webpack. Avoids all kinds of 
> problems with globals ect that you described. 
>  I am not quite sure if we need to invent a jenkins specific solution here. 
> 
> Here is an example using elm 
> 
> https://github.com/DotCi/DotCiPipelineViewer 
> 
> example using react and co
> 
> https://github.com/groupon/DotCi 
> 
> None of those leaks globals.
> 
> Surya
> 
>> On Saturday, September 5, 2015 at 7:32:01 AM UTC-5, Tom Fennelly wrote:
>> Something that might help ... a description of the state of JavaScript in 
>> Jenkins as we see it.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/0wu31f3az_w/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/6948e86e-7313-44f9-93cd-ea6b42158093%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0B84D67D-5876-4BFC-ACA7-DDEE85F817D2%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automatic tool installation - too many choices?

[Daniel Beck]

Look at the other tools.

Play Framework -- 24 versions
Ant -- 28 versions
Maven -- 33 versions
Groovy -- 76 versions
Gradle -- 89 versions
NodeJS -- 155 versions

So 31 for cmake looks low enough. Unless you've seem complaints about Gradle, 
Groovy, or Nodejs?

> On 06.09.2015, at 07:35, Martin Weber  wrote:
> 
> Hi all,
> 
> my crawler for cmake.org gives 31 choices for end users to install.
> Would that be OK or should I try to reduce the number?
> 
> Choices for cmake are
>"id": "3.3.1",
>"id": "3.3.0",
>"id": "3.2.3",
>"id": "3.2.2",
>"id": "3.2.1",
>"id": "3.2.0",
>"id": "3.1.3",
>"id": "3.1.2",
>"id": "3.1.1",
>"id": "3.1.0",
>"id": "3.0.2",
>"id": "3.0.1",
>"id": "3.0.0",
>"id": "2.8.12",
>"id": "2.8.11",<-- opensuse13.1 has rpms for this
>"id": "2.8.10",
>"id": "2.8.9",
>"id": "2.8.8",
>"id": "2.8.7",
>"id": "2.8.6",
>"id": "2.8.5",
>"id": "2.8.4",
>"id": "2.8.3",
>"id": "2.8.2",
>"id": "2.8.1",
>"id": "2.8.0",
>"id": "2.6.4", <-- RHEL5/6/7 have rpms for this
>"id": "2.6.3",
>"id": "2.6.2",
>"id": "2.6.1",
>"id": "2.6.0",
> 
> Regards,
>   Martin
> 
> -- 
> Cd wrttn wtht vwls s mch trsr.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/4550419.t3GcVMjPSd%40linux.
> For more options, visit https://groups.google.com/d/optout.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/16D1CEC7-422B-4D5C-A937-228C2CC0B78B%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Modularized JavaScript code in Jenkins Core .... how about it?

[Surya Gaddipati]

Hi Tom,

I've been packaging all kinds of js stuff with webpack. Avoids all kinds of 
problems with globals ect that you described. 
 I am not quite sure if we need to invent a jenkins specific solution here. 

Here is an example using elm 

https://github.com/DotCi/DotCiPipelineViewer 

example using react and co

https://github.com/groupon/DotCi 

None of those leaks globals.

Surya

On Saturday, September 5, 2015 at 7:32:01 AM UTC-5, Tom Fennelly wrote:
>
> Something that might help ... a description of the state of JavaScript in 
> Jenkins as we see it 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6948e86e-7313-44f9-93cd-ea6b42158093%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Cloud plugin, provisioning

[Stanislav Baiduzhyi]

Hi All,

Quick question: writing cloud plugin, provisioning is called more than
once for the same label, but I have only one node to provision, should
I return the same instance once again, or should I return empty list
and Jenkins will reuse the node that was returned on first request?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFHiie5GcKQ9LU72K07y4OFcL3ZDSJQcWf7FiS2oEfRNwCnx3g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Commit access to jenkinsci/SCTMExecutor-plugin

[Thomas Fürer]

Hi Oleg,

thanks for helping, but why do I not have permissions to change
settings. I'm the founder, owner an maintainer of this plugin? I also
have a different plugin for jenkins (thinbackup) and here I'm able to
change the settings.

Regards,
Thomas

Am 06.09.2015 um 20:07 schrieb Oleg Nenashev:
> In GitHub the right approach to the contribution is to create pull
> requests from forks to the master repo. In such case the plugin
> developers will be able to review and accept the pull request.
> 
> Anyway I've granted the commit permissions to Sebastian. He dhould get
> an invitation to the jenkinsci org soon.
> 
> BR, Oleg
> 
> суббота, 5 сентября 2015 г., 13:50:30 UTC+3 пользователь Thomas Fuerer
> написал:
> 
> Hi seb,
> 
> I'm wondering, because I'm not able to set ownership or commit
> rights on
> this project, even I'm the maintainer and owner of this project.
> 
> So maybe one of the jenkins staff can help us.
> 
> Meanwhile I saw you allready forked the project, but I'm not sure if in
> this case the release worflow will work?
> 
> thanks,
> Thomas
> 
> Am 21.08.2015 um 12:23 schrieb Sebastian Kornexl:
> > Hi,
> >
> >  
> >
> > when the source was on SVN I already had permissions to commit.
> >
> >  
> >
> > Can I have these permission on GitHub too?
> >
> >  
> >
> > Rep: https://github.com/jenkinsci/SCTMExecutor-plugin
> 
> >
> > GitHub account: donkaes
> >
> >  
> >
> > Time for a new release of this plugin.
> >
> >  
> >
> > Thanks,
> >
> > Sebastian
> >
> >  
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it,
> send
> > an email to jenkinsci-de...@googlegroups.com 
> > .
> > To view this discussion on the web visit
> >
> 
> https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com
> 
> 
> 
> >
> 
>  
> >.
> 
> > For more options, visit https://groups.google.com/d/optout
> .
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/e9ef07c6-c05d-4fd5-8293-ce64c9ab47b4%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55EC8C0A.8030508%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.

Cloud plugin, disconnecting from slave properly

[Stanislav Baiduzhyi]

Hi All,

Another question regarding custom cloud plugins:

I'm creating a custom plugin that creates a node from prototype, uses
the node, discards it (or reverts the state).

I'm starting slave.jar with tcp and connecting to it. My
ComputerLauncher also implements ExecutorListener, and disconnects on
taskCompleted, and terminates/discards the node in afterDisconnect.
But I see huge stack traces about socket being closed.

I've copied the closing procedure from here:
https://github.com/jenkinsci/vsphere-cloud-plugin/blob/master/src/main/java/org/jenkinsci/plugins/vSphereCloudSlave.java#L305

So, what is the correct way to disconnect the channel before node termination?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFHiie6uFhaZtTB6%3DJetkxCFtYorb7bVWDi9DhRRhXxQLvcp3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Commit access to jenkinsci/SCTMExecutor-plugin

[Oleg Nenashev]

I have no permissions to check your permissions :(
CC'ed Daniel Beck, he should be able to do it.

2015-09-06 21:55 GMT+03:00 Thomas Fürer :

> Hi Oleg,
>
> thanks for helping, but why do I not have permissions to change
> settings. I'm the founder, owner an maintainer of this plugin? I also
> have a different plugin for jenkins (thinbackup) and here I'm able to
> change the settings.
>
> Regards,
> Thomas
>
> Am 06.09.2015 um 20:07 schrieb Oleg Nenashev:
> > In GitHub the right approach to the contribution is to create pull
> > requests from forks to the master repo. In such case the plugin
> > developers will be able to review and accept the pull request.
> >
> > Anyway I've granted the commit permissions to Sebastian. He dhould get
> > an invitation to the jenkinsci org soon.
> >
> > BR, Oleg
> >
> > суббота, 5 сентября 2015 г., 13:50:30 UTC+3 пользователь Thomas Fuerer
> > написал:
> >
> > Hi seb,
> >
> > I'm wondering, because I'm not able to set ownership or commit
> > rights on
> > this project, even I'm the maintainer and owner of this project.
> >
> > So maybe one of the jenkins staff can help us.
> >
> > Meanwhile I saw you allready forked the project, but I'm not sure if
> in
> > this case the release worflow will work?
> >
> > thanks,
> > Thomas
> >
> > Am 21.08.2015 um 12:23 schrieb Sebastian Kornexl:
> > > Hi,
> > >
> > >
> > >
> > > when the source was on SVN I already had permissions to commit.
> > >
> > >
> > >
> > > Can I have these permission on GitHub too?
> > >
> > >
> > >
> > > Rep: https://github.com/jenkinsci/SCTMExecutor-plugin
> > 
> > >
> > > GitHub account: donkaes
> > >
> > >
> > >
> > > Time for a new release of this plugin.
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Sebastian
> > >
> > >
> > >
> > > --
> > > You received this message because you are subscribed to the Google
> > > Groups "Jenkins Developers" group.
> > > To unsubscribe from this group and stop receiving emails from it,
> > send
> > > an email to jenkinsci-de...@googlegroups.com 
> > > .
> > > To view this discussion on the web visit
> > >
> >
> https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com
> >
> >
> > >
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com?utm_medium=email_source=footer
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com?utm_medium=email_source=footer
> >>.
> >
> > > For more options, visit https://groups.google.com/d/optout
> > .
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to jenkinsci-dev+unsubscr...@googlegroups.com
> > .
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/jenkinsci-dev/e9ef07c6-c05d-4fd5-8293-ce64c9ab47b4%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/e9ef07c6-c05d-4fd5-8293-ce64c9ab47b4%40googlegroups.com?utm_medium=email_source=footer
> >.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/GxfNANOJ5IY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/55EC8C0A.8030508%40googlemail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLA8w1ZsR3ubfDijoWebxQ8KCXOSvmHpGrDy7X2VUrWjxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.