Re: BuildFlow Plugin licence - Afferro GPL / GPL?
The plugin was initially created under AGPL, but I got approval to relicense it under MIT. https://github.com/jenkinsci/build-flow-plugin/commit/022b40b86383ef678184bf6fe6497be033254555 2013/8/20 teilo teilo+goo...@teilo.net Hi Nicolas/Cloudbees/other buildflow contributors. Currently the licence of the BuildFlow plugin is a mix of Affero GPL v3 (jelly files) and Lesser GPL v3 (most others), the pom.xml states LGPL v3. Is this just an oversight when the plugin was re-licensed - or is this really a mix? (also any chance of changing it to something without the GPL v3 patent issues to make it more company friendly - even if it is dual licenced with the Jenkins enterprise plugins) I don't ask for much do I ;-) /James -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: commit access for new plugin
forked as https://github.com/jenkinsci/graphite-plugin 2013/8/21 Joachim Rodrigues rodrigues.joac...@gmail.com Hi I just finished a plugin that send metrics to a graphite server. https://github.com/joachim-rodrigues/graphiteIntegrator For the moment it just send : number of tests, tests skipped, tests failed, build duration, cobertura total line coverage and cobertura total branch coverage to one or more graphite servers. But I am going to enrich the number of metrics for next release. Can i have the jenkins-plugin github access to commit this plugin ? Thanks Joachim -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: commit access for new plugin
Ok thanks but i can't see the plugin in the plugin managment section of my jenkins server. Do i have to do something to install this plugin by this way on my server ? On Wednesday, August 21, 2013 8:17:41 AM UTC+2, nicolas de loof wrote: forked as https://github.com/jenkinsci/graphite-plugin 2013/8/21 Joachim Rodrigues rodrigue...@gmail.com javascript: Hi I just finished a plugin that send metrics to a graphite server. https://github.com/joachim-rodrigues/graphiteIntegrator For the moment it just send : number of tests, tests skipped, tests failed, build duration, cobertura total line coverage and coberturatotal branch coverage to one or more graphite servers. But I am going to enrich the number of metrics for next release. Can i have the jenkins-plugin github access to commit this plugin ? Thanks Joachim -- 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 javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Re: 1.509.3 RC1 posted
Hi, we are having another regression with 1.509.3 RC, namely, there is an Artifactory plugin bug that seems to have resurfaced: does this bug appears only when using 1.509.3 RC? Quickly looking on it seems to me like a bug in Artifactory plugin, not Jenkins core, but the root cause could be in the core. Thanks Vojta signature.asc Description: This is a digitally signed message part.
Re: commit access for new plugin
You'll probably want to read through https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins including the section on releasing the plugin for people (including yourself) to use. Richard. On Wed, Aug 21, 2013 at 7:36 PM, Joachim Rodrigues rodrigues.joac...@gmail.com wrote: Ok thanks but i can't see the plugin in the plugin managment section of my jenkins server. Do i have to do something to install this plugin by this way on my server ? On Wednesday, August 21, 2013 8:17:41 AM UTC+2, nicolas de loof wrote: forked as https://github.com/**jenkinsci/graphite-pluginhttps://github.com/jenkinsci/graphite-plugin 2013/8/21 Joachim Rodrigues rodrigue...@gmail.com Hi I just finished a plugin that send metrics to a graphite server. https://github.com/joachim-**rodrigues/graphiteIntegratorhttps://github.com/joachim-rodrigues/graphiteIntegrator For the moment it just send : number of tests, tests skipped, tests failed, build duration, cobertura total line coverage and coberturatotal branch coverage to one or more graphite servers. But I am going to enrich the number of metrics for next release. Can i have the jenkins-plugin github access to commit this plugin ? Thanks Joachim -- 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. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: commit access for new plugin
plugin has to be released and deployed to jenkins-ci.org maven repository, then update-center index rebuilt (once a day afaik) 2013/8/21 Joachim Rodrigues rodrigues.joac...@gmail.com Ok thanks but i can't see the plugin in the plugin managment section of my jenkins server. Do i have to do something to install this plugin by this way on my server ? On Wednesday, August 21, 2013 8:17:41 AM UTC+2, nicolas de loof wrote: forked as https://github.com/**jenkinsci/graphite-pluginhttps://github.com/jenkinsci/graphite-plugin 2013/8/21 Joachim Rodrigues rodrigue...@gmail.com Hi I just finished a plugin that send metrics to a graphite server. https://github.com/joachim-**rodrigues/graphiteIntegratorhttps://github.com/joachim-rodrigues/graphiteIntegrator For the moment it just send : number of tests, tests skipped, tests failed, build duration, cobertura total line coverage and coberturatotal branch coverage to one or more graphite servers. But I am going to enrich the number of metrics for next release. Can i have the jenkins-plugin github access to commit this plugin ? Thanks Joachim -- 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. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: BuildFlow Plugin licence - Afferro GPL / GPL?
Excellent - I was hoping for GPLv2 but MIT should streamline being able to push patches back! BTW - the pom.xml still references LGPL v3 licenses license nameLGPL 3/name urlhttp://www.gnu.org/licenses/lgpl.html/url distributionrepo/distribution /license /licenses On Wednesday, 21 August 2013 07:14:42 UTC+1, nicolas de loof wrote: The plugin was initially created under AGPL, but I got approval to relicense it under MIT. https://github.com/jenkinsci/build-flow-plugin/commit/022b40b86383ef678184bf6fe6497be033254555 2013/8/20 teilo teilo+...@teilo.net javascript: Hi Nicolas/Cloudbees/other buildflow contributors. Currently the licence of the BuildFlow plugin is a mix of Affero GPL v3 (jelly files) and Lesser GPL v3 (most others), the pom.xml states LGPL v3. Is this just an oversight when the plugin was re-licensed - or is this really a mix? (also any chance of changing it to something without the GPL v3 patent issues to make it more company friendly - even if it is dual licenced with the Jenkins enterprise plugins) I don't ask for much do I ;-) /James -- 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 javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: BuildFlow Plugin licence - Afferro GPL / GPL?
2013/8/21 teilo teilo+goo...@teilo.net Excellent - I was hoping for GPLv2 but MIT should streamline being able to push patches back! I've documented short term plan on https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin in case you have some clever solution to existing limitations ;) BTW - the pom.xml still references LGPL v3 licenses license nameLGPL 3/name urlhttp://www.gnu.org/licenses/lgpl.html/url distributionrepo/distribution /license /licenses fixed. On Wednesday, 21 August 2013 07:14:42 UTC+1, nicolas de loof wrote: The plugin was initially created under AGPL, but I got approval to relicense it under MIT. https://github.com/jenkinsci/**build-flow-plugin/commit/** 022b40b86383ef678184bf6fe6497b**e033254555https://github.com/jenkinsci/build-flow-plugin/commit/022b40b86383ef678184bf6fe6497be033254555 2013/8/20 teilo teilo+...@teilo.net Hi Nicolas/Cloudbees/other buildflow contributors. Currently the licence of the BuildFlow plugin is a mix of Affero GPL v3 (jelly files) and Lesser GPL v3 (most others), the pom.xml states LGPL v3. Is this just an oversight when the plugin was re-licensed - or is this really a mix? (also any chance of changing it to something without the GPL v3 patent issues to make it more company friendly - even if it is dual licenced with the Jenkins enterprise plugins) I don't ask for much do I ;-) /James -- 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. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: BuildFlow Plugin licence - Afferro GPL / GPL?
Hasn’t Kohskue already provided a solution that could be leveraged? http://groovy-sandbox.kohsuke.org/ would need some work to also ask DSLExtensions what they need to run. Short term I am working on limiting concurrent execution of jobs in a flow to prevent exhaustion (there is no point pulling myjob#2 from the queue when myjob#3 is in the queue as well - think parameterised jobs and build(myjob, upstream:build; other:fred) ). This is as a sepated plugin for the DSL - but I have some simple fixes for JENKINS-15966, typos and extend the DSL help (so that extensions can also display some help) that are for the flow plugin. Hopefully I should have clearance for these sometime next week. /James On Wednesday, 21 August 2013 11:03:02 UTC+1, nicolas de loof wrote: 2013/8/21 teilo teilo+...@teilo.net javascript: Excellent - I was hoping for GPLv2 but MIT should streamline being able to push patches back! I've documented short term plan on https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin in case you have some clever solution to existing limitations ;) BTW - the pom.xml still references LGPL v3 licenses license nameLGPL 3/name urlhttp://www.gnu.org/licenses/lgpl.html/url distributionrepo/distribution /license /licenses fixed. On Wednesday, 21 August 2013 07:14:42 UTC+1, nicolas de loof wrote: The plugin was initially created under AGPL, but I got approval to relicense it under MIT. https://github.com/jenkinsci/**build-flow-plugin/commit/** 022b40b86383ef678184bf6fe6497b**e033254555https://github.com/jenkinsci/build-flow-plugin/commit/022b40b86383ef678184bf6fe6497be033254555 2013/8/20 teilo teilo+...@teilo.net Hi Nicolas/Cloudbees/other buildflow contributors. Currently the licence of the BuildFlow plugin is a mix of Affero GPL v3 (jelly files) and Lesser GPL v3 (most others), the pom.xml states LGPL v3. Is this just an oversight when the plugin was re-licensed - or is this really a mix? (also any chance of changing it to something without the GPL v3 patent issues to make it more company friendly - even if it is dual licenced with the Jenkins enterprise plugins) I don't ask for much do I ;-) /James -- 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. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- 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 javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: acces to https://github.com/jenkinsci/jira-plugin
is anybody home? воскресенье, 18 августа 2013 г., 14:02:20 UTC+4 пользователь Artem Koshelev написал: Hi, nobody had respond to my pull-request in a week, so can you give me commit rights? My github account is artkoshelev. Artem -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: BuildFlow Plugin licence - Afferro GPL / GPL?
2013/8/21 teilo teilo+goo...@teilo.net Hasn’t Kohskue already provided a solution that could be leveraged? ** **http://groovy-sandbox.kohsuke.org/ would need some work to also ask DSLExtensions what they need to run. That's an option, not sure how nicely this will integrated and cover DSL security requirements. Another difficult thing is the DSL must RUN with permission for user who CONFIGURED the job when retrieving jobs by name. Short term I am working on limiting concurrent execution of jobs in a flow to prevent exhaustion (there is no point pulling myjob#2 from the queue when myjob#3 is in the queue as well - think parameterised jobs and build(myjob, upstream:build; other:fred) ). Not sure to understand, can you describe with more details ? This is as a sepated plugin for the DSL - but I have some simple fixes for JENKINS-15966, typos and extend the DSL help (so that extensions can also display some help) that are for the flow plugin. Hopefully I should have clearance for these sometime next week. ok, waiting for pull request then ;) /James On Wednesday, 21 August 2013 11:03:02 UTC+1, nicolas de loof wrote: 2013/8/21 teilo teilo+...@teilo.net Excellent - I was hoping for GPLv2 but MIT should streamline being able to push patches back! I've documented short term plan on https://wiki.jenkins-ci.** org/display/JENKINS/Build+**Flow+Pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Pluginin case you have some clever solution to existing limitations ;) BTW - the pom.xml still references LGPL v3 licenses license nameLGPL 3/name urlhttp://www.gnu.**org/licenses/lgpl.html http://www.gnu.org/licenses/lgpl.html/url distributionrepo/**distribution /license /licenses fixed. On Wednesday, 21 August 2013 07:14:42 UTC+1, nicolas de loof wrote: The plugin was initially created under AGPL, but I got approval to relicense it under MIT. https://github.com/jenkinsci/**b**uild-flow-plugin/commit/**022b40** b86383ef678184bf6fe6497b**e03325**4555https://github.com/jenkinsci/build-flow-plugin/commit/022b40b86383ef678184bf6fe6497be033254555 2013/8/20 teilo teilo+...@teilo.net Hi Nicolas/Cloudbees/other buildflow contributors. Currently the licence of the BuildFlow plugin is a mix of Affero GPL v3 (jelly files) and Lesser GPL v3 (most others), the pom.xml states LGPL v3. Is this just an oversight when the plugin was re-licensed - or is this really a mix? (also any chance of changing it to something without the GPL v3 patent issues to make it more company friendly - even if it is dual licenced with the Jenkins enterprise plugins) I don't ask for much do I ;-) /James -- 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. For more options, visit https://groups.google.com/**grou**ps/opt_outhttps://groups.google.com/groups/opt_out . -- 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. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Plugin not shown in Update Center
Hello all highly respectable developers, I do really need you help. I'm stuck now for about a whole day, did a lot of research and just wont find the correct solution. My Plugin I have created just wont show up in the Jenkins Update Center, though it is listed here http://dl.aragost.com/jenkins/updates/update-center.json and can be found here http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/Relution/ Could someone please give me some Information, what I am doing wrong? The console output after running mvn release:prepare release:perform is the following : Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/Relution/1.528/Relution-1.528-javadoc.jar (182 KB at 79.4 KB/sec) [INFO] [INFO] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] [INFO] [INFO] Total time: 1:40.526s [INFO] [INFO] Finished at: Wed Aug 21 10:51:10 CEST 2013 [INFO] [INFO] Final Memory: 40M/85M [INFO] [INFO] [INFO] Cleaning up after release... [INFO] [INFO] BUILD SUCCESS I really don't know where to search further or what I should/could change in the process. Thanks in advance! -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Repository for https://github.com/jenkinsci
Hello jenkins Team, because I just can't find the correct email address where to send it to, so I am trying it this way. I got a github Repository, which can be found here: https://github.com/cbugyimway/jenkins-mcap-eas-plugin And would really like to get a repository in your space, because I want to get the Plugin into your Jenkins Update Center I got my plugin already uploaded here http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/Relution/1.526/ and here https://wiki.jenkins-ci.org/display/JENKINS/Jenkins-Relution, but for the final entry in your update center, if I did get it right, I need to have a repository in your jenkins github. Thanks in advance, Christian Bugyi Apprentice M-Way Solutions GmbH Headquarter Stuttgart Company address: Leitzstr. 45 70469 Stuttgart Phone +49 (0) 711-49066-459 Mobile +49 (0) 172-7525077 Fax +49 (0) 711-49066-463 c.bu...@mwaysolutions.commailto:c.bu...@mwaysolutions.com http://www.mwaysolutions.comhttp://www.mwaysolutions.com/ http://www.catoo.iohttp://www.catoo.io/ http://www.the-m-project.nethttp://www.the-m-project.net/ Commercial Register: Stuttgart HRB 25158 Management: Volker Hahn, Richard Malley, Charlie Cavolina, Peter Necheles This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhaltes, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Repository for https://github.com/jenkinsci
I've forked your repo as https://github.com/jenkinsci/mcap-eas-plugin please update pom.xml SCM to reflect this change 2013/8/21 Christian Bugyi c.bu...@mwaysolutions.com Hello jenkins Team, because I just can't find the correct email address where to send it to, so I am trying it this way. I got a github Repository, which can be found here: https://github.com/cbugyimway/jenkins-mcap-eas-plugin And would really like to get a repository in your space, because I want to get the Plugin into your Jenkins Update Center I got my plugin already uploaded here http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/Relution/1.526/ and here https://wiki.jenkins-ci.org/display/JENKINS/Jenkins-Relution, but for the final entry in your update center, if I did get it right, I need to have a repository in your jenkins github. Thanks in advance, *Christian Bugyi* Apprentice M-Way Solutions GmbH Headquarter Stuttgart Company address: Leitzstr. 45 70469 Stuttgart Phone +49 (0) 711-49066-459 Mobile +49 (0) 172-7525077 Fax +49 (0) 711-49066-463 *c.bu...@mwaysolutions.com* http://www.mwaysolutions.com http://www.catoo.io http://www.the-m-project.net Commercial Register: Stuttgart HRB 25158 Management: Volker Hahn, Richard Malley, Charlie Cavolina, Peter Necheles This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhaltes, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
RE: BuildFlow Plugin licence - Afferro GPL / GPL?
Short term I am working on limiting concurrent execution of jobs in a flow to
prevent exhaustion (there is no point pulling myjob#2 from the queue when
myjob#3 is in the queue as well - think parameterised jobs and build(myjob,
upstream:build; other:fred) ).
Not sure to understand, can you describe with more details ?
Sure, hopefully I can explain this better with an example.
Take an example flow that is triggered by a commit job.
build(level1_smoke, run: upstream)
build(level2_tests, run: upstream)
build(level3_indepthtests, run: upstream)
assuming
a commit build take 10 minutes
level1_smoke build takes 5 minutes
level2_tests build take 20 minutes
level3_indepth build takes 1 hour
(you want to manage the flow with the flow plugin - why wouldn't you)
Given any commit you want to know quickly if the level1_smoke tests fail (or
pass).
As such you need to enable concurrent executions of flow_job
As commits can be hitting the SCM for commit constantly we will have a run of
commit every 10 minutes, without any restrictions (given that the jobs are
parameterised) we will very quickly have lots of entries for the subsequent
jobs.
As we want some quick turnaround (we want to know as soon as possible when a
commit doesn't pass all these tests) we need to enable concurrent exectution of
these level_* jobs.
This will very quicky exhaust a large number of executors.
In reality - you don't care about knowing if every build of commit passes all
the tests.
What you care about is knowing that when level3_indepth tests have run against
a particular commit build that all the preceding jobs in the flow have also
passed and run against the exact same commit run and that any invocation of the
level3_indepth tests will run against the most recent commit that has also
passed the preceding level2_tests.
The non-flow way could be for level3_indepth to get the latest run of commit
as it started and to be triggered by a successful level2_test. This has a
drawback as you could get a run for which there is no successful level2 tests.
Alternatively you can use promoted builds - but that punts logic up to the
commit build which may be undesirable for various reasons.
Or you could get the run from the leve2_test that caused the level3_indepth to
run - this way makes it harder to use some Jenkins plugins, and moves a lot of
the intelligence to the Job (which should just be concentrating on the test
task at hand).
So back to the BuildFlow - We have multiple FlowRuns running concurrently and
say level3_indepth is running we don't want to start another one. However as
soon as level3_indepth has finished we want the most recent attempt to start a
new level3_indepth to succeed (and any that are not the most recent to abort
the flow run)
Doing this in the Flow DSL makes sense as there you can take advantage of
things extra flow features like parallel / guard rescue etc, showing the
build graph etc...
So the aboce leads to something like the following:
build(level1_smoke, run: upstream)
block (level2) {
build(level2_tests, run: upstream)
}
block (level3) {
build(level3_indepthtests, run: upstream)
}
Now this makes even more sense when you have realise that all the tests are
cucumber tests just with different tags - and these can actually be the same
job - (thus reducing job maintainance) and can be parameterised further...
Which leads to something like the following..
build(acceptance_tests, run: upstream, level:1)
block (level2) {
build(acceptance_tests, run: upstream, level:2)
}
block (level3) {
parallel {
build(acceptance_tests, run: upstream, level:3a)
build(acceptance_tests, run: upstream, level:3b)
}
}
This will run acceptance_tests with level:1 for every invocation of the
BuildFlow. However it will only run acceptance_tests for the latest level:2
if a level:2 job is not already running.
If it is not running the the flowrun will wait. If multiple FlowRuns are
waiting for the level2 block then when the block is released only the most
recent FlowRun will be able to enter it - and all others will have the FlowRun
Aborted.The block can also run across multiple jobs for example the
level3 block will prevent any new starts of 3a or 3b tests.
Or in a time line (at is the acceptance_tests job)
t=0flow#1 - at level=1
t=5flow#1 - at level=2
t=10 flow#2 - at level=1
t=20 flow#3 - at level=1
t=25 flow#1 - [ at level=3a, at level=3b ]
t=25 flow#2 (aborted as flow#3 is waiting to enter the same block)
t=25 flow#3 - at level=2
t=65 flow#3 - [ at level=3a, at level=3b ]
Hopefully that clears things up a bit. If something is not clear let me know
(as I will eventually need to put something like this on the Wiki)
/James
--
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
Re: Plugin not shown in Update Center
Hi, From the logs, it seems you only released some hours ago. If so, I guess you should just wait still a few hours so the information propagates. Cheers Le 21 août 2013 14:23, c.bu...@mwaysolutions.com a écrit : Hello all highly respectable developers, I do really need you help. I'm stuck now for about a whole day, did a lot of research and just wont find the correct solution. My Plugin I have created just wont show up in the Jenkins Update Center, though it is listed here http://dl.aragost.com/jenkins/updates/update-center.json and can be found here http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/Relution/ Could someone please give me some Information, what I am doing wrong? The console output after running mvn release:prepare release:perform is the following : Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/Relution/1.528/Relution-1.528-javadoc.jar(182 KB at 79.4 KB/sec) [INFO] [INFO] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] [INFO] [INFO] Total time: 1:40.526s [INFO] [INFO] Finished at: Wed Aug 21 10:51:10 CEST 2013 [INFO] [INFO] Final Memory: 40M/85M [INFO] [INFO] [INFO] Cleaning up after release... [INFO] [INFO] BUILD SUCCESS I really don't know where to search further or what I should/could change in the process. Thanks in advance! -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Plugin not shown in Update Center
Hi and thank you for your answer. I would be so happy, if this would fix my problem :) -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: JDK Parameter (New Plugin)
Hi Daniel. The plugin has problems with concurrent builds at the moment as it is referenced on the wiki page. It is on our roadmap to change the implementation to support that case in the future. It is supporting aborted builds. On 20/08/13 17:54, Daniel Beck wrote: Just looked at the code a bit. How does this behave with parallel executions of the same project? Does it handle aborted builds? On 19.08.2013, at 15:52, Baris Batiege baris.bati...@datalex.com wrote: Hey, along with Fabio Neves, I developed a plugin called JDK Parameter Choice. The plugin lets you add a build parameter which allows the JDK that will be used to be chosen on a per build basis. The JDKs that can be chosen from can be specified on the configuration page of any job that has the JDK parameter enabled. The plugin was originally designed to solve the issue of letting a user without configure permissions choose separate JDKs per build of a job in a simple way. I’ve made a wiki page for it here: https://wiki.jenkins-ci.org/display/JENKINS/JDK+Parameter+Plugin and the github repo for it is here:https://github.com/Sargemck/JDK_Parameter_Choice . I’d appreciate it if someone could approve this and put it on jenkinsci. Please let me know if you see any issues or potential improvements that could be made to the plugin. Thanks in advance, Baris Batiege (Datalex) -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Plastic SCM plugin for Jenkins: build issue
Hi, I´ve performed a few changes in a Jenkins plugin ( https://github.com/jenkinsci/plasticscm-plugin), but when I perform a pull request to the repo, a build is automatically done by BuildHive system. It fails because BuildHive systems uses Java 7 by default and the plugin needs Java 6 to be built. How can I configure BuildHive to use Java 6? In case it´s not possible, How can I disable automatic BuildHive system? I can build locally the plugin and then upload it to Jenkins web page. Regards, Carlos -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Found reliance on default encoding in ... 66 cases
Hi all, while building jenkins and running findbugs on the jenkins sources I noticed that findbugs detected 66 issues were the coding is relying on the default platform encoding. Is that intended? Or does it make sence when I'll propose a change which switches all those cases to utf-8? Regards Matthias -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: acces to https://github.com/jenkinsci/jira-plugin
I added you as a committer. Welcome aboard! Ulli Am 18.08.2013 um 12:02 schrieb Artem Koshelev artkoshe...@gmail.com: Hi, nobody had respond to my pull-request in a week, so can you give me commit rights? My github account is artkoshelev. Artem -- 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. For more options, visit https://groups.google.com/groups/opt_out. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Re: 1.509.3 RC1 posted
It may be a change in the core that is causing the resurfacing of the bug. It seems to have something to do with the path name, which has a $ in it, e.g. ERROR: Archived artifact is missing: /var/lib/jenkins/jobs/Check/modules/com.example.pm.multimodule.core$multimodule-core/builds/2011-06-15_06-52-05/archive/com.example.pm.multimodule.core/multimodule-core/2.6.2-SNAPSHOT/pom.xml see: https://issues.jenkins-ci.org/browse/JENKINS-10082 (which now has links to the other issues.) thx, -Russ At 9:48 AM +0200 8/21/13, Vojtech Juranek wrote: Hi, we are having another regression with 1.509.3 RC, namely, there is an Artifactory plugin bug that seems to have resurfaced: does this bug appears only when using 1.509.3 RC? Quickly looking on it seems to me like a bug in Artifactory plugin, not Jenkins core, but the root cause could be in the core. Thanks Vojta -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Plastic SCM plugin for Jenkins: build issue
I think you'd be best making the plugin Java 7 compatible especially as
Java 6 is now EOL.
I don't have access to the code right now but I could be a simple matter of
the parent Pom version being too low as some older Poms did rely on com.sun
classes that aren't in Openjdk/Java 7.
Richard.
On Thursday, August 22, 2013, Carlos Alba wrote:
Hi,
I´ve performed a few changes in a Jenkins plugin (
https://github.com/jenkinsci/plasticscm-plugin), but when I perform a
pull request to the repo, a build is automatically done by BuildHive
system. It fails because BuildHive systems uses Java 7 by default and the
plugin needs Java 6 to be built.
How can I configure BuildHive to use Java 6?
In case it´s not possible, How can I disable automatic BuildHive system? I
can build locally the plugin and then upload it to Jenkins web page.
Regards,
Carlos
** **
--
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 javascript:_e({},
'cvml', 'jenkinsci-dev%2bunsubscr...@googlegroups.com');.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Plastic SCM plugin for Jenkins: build issue
To reply further, got access to see what the pom.xml was for the plasticscm plugin. Does look like its the old parent version that will be stopping Java 7 compatibility. I'm not a Maven whizz but here's what I recently changed the Gradle plugin's parent in the pom to which works nicely: parent groupIdorg.jenkins-ci.plugins/groupId artifactIdplugin/artifactId version1.427/version /parent Richard. On Thu, Aug 22, 2013 at 7:07 AM, Richard Bywater rich...@byh2o.com wrote: I think you'd be best making the plugin Java 7 compatible especially as Java 6 is now EOL. I don't have access to the code right now but I could be a simple matter of the parent Pom version being too low as some older Poms did rely on com.sun classes that aren't in Openjdk/Java 7. Richard. On Thursday, August 22, 2013, Carlos Alba wrote: Hi, I´ve performed a few changes in a Jenkins plugin ( https://github.com/jenkinsci/plasticscm-plugin), but when I perform a pull request to the repo, a build is automatically done by BuildHive system. It fails because BuildHive systems uses Java 7 by default and the plugin needs Java 6 to be built. How can I configure BuildHive to use Java 6? In case it´s not possible, How can I disable automatic BuildHive system? I can build locally the plugin and then upload it to Jenkins web page. Regards, Carlos ** ** -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Re: 1.509.3 RC1 posted
On Wed, Aug 21, 2013 at 1:33 PM, Russ Tremain ru...@releasetools.org wrote: It seems to have something to do with the path name, which has a $ in it, e.g. jobs/Check/modules/com.example.pm.multimodule.core$multimodule-core IIRC there was a recent bugfix to use '$' rather than ':' in Maven module directory names since some systems had problems with ':'. So sounds like the Artifactory plugin is faling to quote arguments in a Launcher, etc. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Found reliance on default encoding in ... 66 cases
On Wed, Aug 21, 2013 at 11:23 AM, Matthias Vach matthias.v...@googlemail.com wrote: Is that intended? Not sure. At least *some* uses of the default encoding are intentional (however unfortunate): the build log is written in default encoding for the slave, for example. Generally speaking, we should be using UTF-8 wherever possible, but when interaction with the stdio of external processes is involved, this may not be possible. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Plastic SCM plugin for Jenkins: build issue
Getting slightly OT from the original post but the reason I chose 1.427 was any version between 1.420 and 1.427 seemed to complain about some cloudbee-licence thing. (Using thing as I can't remember the exact details :) ) Richard. On Thu, Aug 22, 2013 at 8:54 AM, Jesse Glick jgl...@cloudbees.com wrote: On Wed, Aug 21, 2013 at 4:45 PM, Richard Bywater rich...@byh2o.com wrote: Does look like its the old parent version that will be stopping Java 7 compatibility. Right, you need at least 1.420 parent POM to build. 1.424 was the first LTS thereafter, if you want to be conservative in baseline version (though for new feature development you may well prefer to update to a more recent LTS). -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Re: 1.509.3 RC1 posted
I've investigated this and it turns out that in our case, the problem was that when a job was deleted and recreated, the re-added job had archivingDisabledtrue/archivingDisabled in the config file (this is set via Advanced Options under the maven build step configuration). Not sure why/how this happened, but Jenkins archiving must be enabled for Artifactory to pick up the artifacts and send them to the server. It is possible that the Artifactory plugin should enforce this or issue a warning. Thankfully, I don't think it had anything to do with 1.509.3 RC1, which we've been running in production since 8/16 now. thanks, -Russ At 4:56 PM -0400 8/21/13, Jesse Glick wrote: On Wed, Aug 21, 2013 at 1:33 PM, Russ Tremain ru...@releasetools.org wrote: It seems to have something to do with the path name, which has a $ in it, e.g. jobs/Check/modules/com.example.pm.multimodule.core$multimodule-core IIRC there was a recent bugfix to use '$' rather than ':' in Maven module directory names since some systems had problems with ':'. So sounds like the Artifactory plugin is faling to quote arguments in a Launcher, etc. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Found reliance on default encoding in ... 66 cases
In those cases would it not be better to explicitly pass the platform charset to make it obvious it is a conscious decision? -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Found reliance on default encoding in ... 66 cases
On Wed, Aug 21, 2013 at 5:54 PM, teilo teilo+goo...@teilo.net wrote: In those cases would it not be better to explicitly pass the platform charset to make it obvious it is a conscious decision? Yes. At least for the run log it already does, so if FB is turning up usages of e.g. new FileWriter(File) then these ought to get corrected. A fair number of usages are known to be ASCII-only, but passing ASCII there would be clearer and safer. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
New plugin request
Hello everyone, I've recently authored a new plugin -- github-pull-request-notifier I've made the initial pom changes outlined here: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins github repo: https://github.com/hawknewton/jenkins-github-pull-request-notifier My jenkins-ci.org account is hawknewton Thanks! -- H -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: New plugin request
Hello, what is the difference between your plugin and the existing https://wiki.jenkins-ci.org/display/JENKINS/Github+pull+request+builder+plugin? Vincent 2013/8/22 Hawk Newton hawk.new...@gmail.com Hello everyone, I've recently authored a new plugin -- github-pull-request-notifier I've made the initial pom changes outlined here: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins github repo: https://github.com/hawknewton/jenkins-github-pull-request-notifier My jenkins-ci.org account is hawknewton Thanks! -- H -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
