Re: Backporting for LTS 2.89.3 complete
Thanks! On Wed, Jan 3, 2018 at 3:12 PM, Oliver Gondža <ogon...@gmail.com> wrote: > Backporting is done and the RC will be pushed later today provided the > tests pass. > > I have decided to postpone one minor fix and 2 performance optimizations > without significant negative impact reported: > > Postponed: > JENKINS-48348 Major Sun, 3 Dec 2017 10:37:42 > + > If task can be run only on master, use shortcut > https://issues.jenkins-ci.org/browse/JENKINS-48348 > JENKINS-48350 Major Sun, 3 Dec 2017 10:41:09 > + > Cache estimated duration for execution > https://issues.jenkins-ci.org/browse/JENKINS-48350 > JENKINS-34254 Major Sun, 17 Dec 2017 14:26:20 > + > Shutdown of jenkins via the /exit URL doesn't work in 2.0 > b/c of 403 > https://issues.jenkins-ci.org/browse/JENKINS-34254 > Fixed: > JENKINS-48604 Blocker Tue, 19 Dec 2017 21:23:13 > + > Jenkins 2.96 downgrades script-security plugin on core > update > https://issues.jenkins-ci.org/browse/JENKINS-48604 > JENKINS-48593 Minor Sun, 24 Dec 2017 15:06:36 > + > System property hudson.consoleTailKB is ignored > https://issues.jenkins-ci.org/browse/JENKINS-48593 > JENKINS-48505 Minor Mon, 18 Dec 2017 13:48:08 > + > Lock contention in ExtensionList.getExtensionList > https://issues.jenkins-ci.org/browse/JENKINS-48505 > JENKINS-48365 CriticalSun, 17 Dec 2017 > 14:24:47 + > Command launcher plugin does not get installed on core > update crossing 2.86 > https://issues.jenkins-ci.org/browse/JENKINS-48365 > JENKINS-48349 Major Sun, 3 Dec 2017 10:41:14 > + > Cache permission id to avoid allocating of new strings > https://issues.jenkins-ci.org/browse/JENKINS-48349 > JENKINS-48080 Minor Sun, 3 Dec 2017 20:08:14 > + > Setup Wizard hangs if confirm password is incorrect while > creating admin user > https://issues.jenkins-ci.org/browse/JENKINS-48080 > > Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 > Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.8 > 9.3-fixed > Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.8 > 9.3-rejected > -- > oliver > > -- > 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/ms > gid/jenkinsci-dev/f2cdd003-b096-de87-77a9-4d6166f4e0a3%40gmail.com. > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B72q53ndrWP4SRKgJtxzk_O9OmAXtCniFg34ApKLcu4rQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Proposal: Release Break during holiday season
Hi, I had added the two weeks to the testing period assuming weeklies would be taking the break as well, but given that that is not needed, using them for backporting makes more sense as you all comment. Thanks! On Mon, Nov 20, 2017 at 9:14 AM, Oliver Gondža <ogon...@gmail.com> wrote: > On 2017-11-20 08:31, Oleg Nenashev wrote: > >> Hi, >> >> LTS release break looks good to me. >> We have lots of pending bugfix-alike changes in pull requests, and these >> 2 weeks also give a chance to integrate more into Weekly releases and then >> consider these changes for .3 backporting. >> >> Wouldn't it be advantageous to move this RC back to Jan 3 to allow >> for more flexibility in backporting late fixes? Or is there an >> advantage to having a four week RC testing period? >> >> +1, we just need to stay a bit conservative while backporting the things. >> Or we could have RC-1 and RC-2 (in the case we plan to do weeklies) >> > > I have no strong feelings here. Given the number of potential candidates > Oleg mentioned, It would probably be better to extend the backporting > period so there is more time to integrate those changes. That would be: > > * Dec 6th 2017: LTS 2.89.1 (as planned). > * Jan 3rd 2018: LTS 2.89.2 RC. > * Jan 17th 2018: LTS 2.89.2 > > I do not think 4 week testing window add much value if spread over > holidays. > > -- > oliver > > -- > 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/ms > gid/jenkinsci-dev/8930a52a-249c-9db1-77e8-5170d1b290e3%40gmail.com. > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B7r5QefguzxL39L3gVsi-jXsqYkSn61%3D0%3Dqd2hKakYOiQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Proposal: Release Break during holiday season
Hi All, IIRC in the last couple of years (at least) there have been a small break of the normal release cycles during the holiday season. I've seen no discussion on the topic yet so I would like to start it, as this information may be relevant for the planning of time off for many people involved or affected (directly or indirectly) by the release dates. An initial proposal would be, as in previous years, a 2-week break. Looking at this year's calendar and the current planned schedule, my proposal would be to introduce these two weeks in the 2.89.2 RC testing period, so the schedule would be: - Dec 6th 2017: LTS 2.89.1 (as planned). - Dec 10th 2017: Weekly 2.94 (as planned). - Dec 17th 2017: Weekly 2.95 (as planned). - Dec 20th 2017: LTS 2.89.2 RC (as planned). - Dec 24th 2017: Skipped weekly - Dec 31st 2017: Skipped weekly - Jan 3rd 2018: Skipped LTS. - Jan 7th 2018: Weekly 2.96 - Jan 14th 2018: Weekly 2.97 - Jan 17th 2018: LTS 2.89.2 - Jan 21st 2018: Weekly 2.98 WDYT? I've proposed this topic for the agenda of the governance meeting of Nov 22nd. Thanks! -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B7uLsF%3DMGZMOpHJqydqRp1U7D1-gs_2zaVXWHzv5ifrkQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Speeding up the ATH
One thing that could encourage moving certain tests from the ATH to the JTH would be JENKINS-41827 <https://issues.jenkins-ci.org/browse/JENKINS-41827>. On Mon, Oct 2, 2017 at 1:52 PM, Oliver Gondža <ogon...@gmail.com> wrote: > A lot of comments and valuable feedback has popped up by the end of the > week. Let me react here instead of on individual messages. > > - No argument on slow test run, high flakiness, fragility. Some of that is > caused by not enough attention as ATH stands a bit aside the delivery > pipeline. Bringing it to PR builds of core or plugins would point more > people to it (hopefully making it better) but it would be annoying at first > until we make it more mature/stable. The question is if we are willing to > bite the bullet here. > > - With regards to the *kinds* of tests that should be part of ATH, the > thing is this was never defined so different kinds got in. I tend to agree > that what can be written against JTH, should. Perhaps it would be > beneficial to write that down and guard no more such tests are added to > prevent further bloating. The existing ones can either be deleted, migrated > or tolerated based on how much effort does it take to maintain them. > > - Ad smoke tests: This seems like a good compromise (starting point?) for > PR integration for several reasons. No question the actual test set should > be revisited. All (sufficiently distinct) core scenarios + recommended > plugin set scenarios + some popular scenarios of non-recommended plugins? > > - Speaking of deleting flaky tests - I am willing to give this a try as > the idea of stable build sounds wonderful and almost unheard of in ATH > land. As a maintainer of downstream plugin update center certified by ATH > internally, I am less excited. Again, I would like to see some consensus on > the process. Sometimes it might be enough to check JTH covers same scenario > or it can be migrated easily. What if it does not and the scenario appears > fundamental? How to tell? > > Please let me know if there are any additional thoughts or I have not > commented on something. Later this week, I intend to summarize this in a > doc or two in ATH repo to base our future decisions on (w.r.t. removing > tests, not accepting them, etc.) and update the thread with PR link. > > -- > oliver > > -- > 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/ms > gid/jenkinsci-dev/6379b1ca-a85d-9041-1695-e9cd02aa042b%40gmail.com. > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B7bxf-Kv68T5F0VPqdB6r18K-aw6MqhfnBFrvet_8sD-g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins 2.73.1 LTS RC testing started
Hi, In case the issue is finally considered severe enough to be included in .1, I just wanted to point out that we completed out testing with the rc before remoting was retracted from 3.11 to 3.10 and found no issues, in case it helps in deciding whether (and where) a backport is needed. Thanks On Wed, Sep 13, 2017 at 2:26 PM, Vincent Latombe <vincent.lato...@gmail.com> wrote: > 2017-09-13 12:40 GMT+02:00 Daniel Beck <m...@beckweb.net>: > >> >> > On 13. Sep 2017, at 12:11, Vincent Latombe <vincent.lato...@gmail.com> >> wrote: >> > >> > Docker environment >> >> Is this going to be a problem in the official Jenkins Docker images? > > > I created a reproducer (in the ticket) using only the official Jenkins > Docker image. > > -- > 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/CAH-zGCgJvv7P5DAQMmnorCcW2UzJoOXK7 > CzKfjrgPqfPz1L59w%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-zGCgJvv7P5DAQMmnorCcW2UzJoOXK7CzKfjrgPqfPz1L59w%40mail.gmail.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B46DW9L6V-9gox8d5-vcRhJ8EBw8On77amQJtHzjcBktg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Request to join Jenkins Security Team
+1 On Thu, Aug 31, 2017 at 3:00 PM, Baptiste Mathus <m...@batmat.net> wrote: > +1. > > Le 29 août 2017 16:14, "Robert Sandell" <rsand...@cloudbees.com> a écrit : > >> +1 >> >> 2017-08-28 19:29 GMT+02:00 Christopher Orr <ch...@orr.me.uk>: >> >>> Hi there, >>> >>> I'd like to request to join the security team. >>> I've got all the prerequisites listed (2FA, CLA, nickname on IRC). >>> >>> Thanks, >>> Chris >>> >>> -- >>> 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/ms >>> gid/jenkinsci-dev/1503941343.3112205.1087569072.66BA5581%40w >>> ebmail.messagingengine.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Robert Sandell >> *Software Engineer* >> *CloudBees Inc.* >> >> -- >> 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/ms >> gid/jenkinsci-dev/CALzHZS048dz9ufW9zCEskaUJnmGzVyTaW8RO5DP% >> 2B-2YDiwJPdA%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS048dz9ufW9zCEskaUJnmGzVyTaW8RO5DP%2B-2YDiwJPdA%40mail.gmail.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/CANWgJS4yad2nPs45aFsswy7jN% > 3D1Tr3jneX%2Bt2dgDvGiwH6boEw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4yad2nPs45aFsswy7jN%3D1Tr3jneX%2Bt2dgDvGiwH6boEw%40mail.gmail.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B5e0awsmW2FtdLgFY2HBQtACQG2LM6GnBUTUbEZi_KgOA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Backporting for LTS 2.60.3 started
Thanks! On Thu, Aug 3, 2017 at 12:34 PM, Oliver Gondža <ogon...@gmail.com> wrote: > I am sorry but I was not able to make it to the meeting on the last > moment. I have backported the 4 candidates and I am pushing the RC today. > JENKINS-45057 seems pretty nasty yet not backported, I am open to revisit > that for 2.60.3 once merged to master. > > -- > oliver > > -- > 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/ms > gid/jenkinsci-dev/00f51d06-4899-73ba-0f9b-5996eae5e8b3%40gmail.com. > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B5Tn0NpxHAP6VQCEO1ptODLORhKzevb726n0uFtjPX7Zg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Backporting for LTS 2.60.3 started
So, what's the status of the RC? Is it going to be pushed today / tomorrow or is it waiting on some additional backport? On Wed, Aug 2, 2017 at 8:06 PM, Oleg Nenashev <o.v.nenas...@gmail.com> wrote: > We have two pending pull requests for JENKINS-45057. > I think it worth to consider backporting them. Will try to get one of the > fixes landed in the next weekly > > четверг, 27 июля 2017 г., 17:07:01 UTC+2 пользователь Andreas Mandel > написал: >> >> All valid points, for sure. This aspect of the Train Model was not clear >> to me... I need to find a way for me how to reduce the risk to run into >> such issues as much as possible for our productive system. We do tests in >> advance and feedback - but actually this is not very formal (on our side) >> and for sure it lacks some heavy load tests and tests that leave the system >> at work for a longer time period. >> >> Now that I'm affected, I think it is important to somehow flag the LTS >> with such issues - actually one can do a Jira Query to find all known open >> issues or use the https://jenkins.io/changelog-stable/ page to check for >> the weather condition and then decide based on the likely long list of >> tickets if it is OK do go forward or not. >> >> I can not say why the issue did not get more attention earlier. IMHO it >> is a kind of time bomb for every Jenkins installation, it might be >> undetected for smaller installations especially if they go with the weekly >> releases and so get restarted at least once a week. >> >> At the end we try to support to get the issue solved - hope this happens >> soon. >> >> Thanks and kind regards, Andreas. >> >> Am Donnerstag, 27. Juli 2017 12:56:55 UTC+2 schrieb Daniel Beck: >>> >>> >>> > On 27. Jul 2017, at 07:19, Andreas Mandel <andreas...@gmail.com> >>> wrote: >>> > >>> > Thanks for the feedback. Does this mean, according to plan, you >>> release LTS versions even with blocker issues? Or do you judge the severity >>> of the issue different? >>> >>> Yes. The train model means we leave the station no matter what. >>> Otherwise we just get bogged down in discussions what constitutes a blocker >>> issue while holding off releases to include well-soaked bug fixes. >>> >>> > but time is unfortunately quite limited. >>> >>> If I'm right with my guess of 2.53 as the first affected release, the >>> problem was around for almost 3 months between introduction of the issue >>> and the original report, which was created only after 2.60.1 was released. >>> As we rely on users reporting and voting on issues they encounter for >>> things like deciding on an LTS baseline, it's no surprise this got in. >>> >>> I asked a month ago in a comment for people who encounter this issue to >>> narrow down in which release the problem was introduced. Despite having 20 >>> watchers now, nobody seems to have taken the time to do that yet. >>> >>> Does that look consistent with an urgent blocker issue to you? >>> >>> -- > 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/aef7efb7-7708-491c-ad13-f6007716a939% > 40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/aef7efb7-7708-491c-ad13-f6007716a939%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B7CpCvLYs_Vg_TEUBUrVHDOVtM1D9yaeS5L_h%3DXRWSLqQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Adopt jquery plugin
Hi, This is my formal request to adopt the jquery plugin <https://github.com/jenkinsci/jquery-plugin>. Though not listed for adoption <https://wiki.jenkins-ci.org/display/JENKINS/Adopt+a+Plugin>, it has had no activity for almost two years (it can probably be considered to not have a current maintainer) and there are a couple of merged PRs that need a release. I already have commit permissions and permissions to deploy are requested here <https://github.com/jenkins-infra/repository-permissions-updater/pull/277>. Thanks! -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B6ugYuW13knTzuSByzzQomhK7k2ZxjLzRsSY%3DnHseztXQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: mailer release?
James, I'll take a look at it and perform the release. Andrés On Thu, Sep 1, 2016 at 5:49 AM, James Dumay <jdu...@cloudbees.com> wrote: > It would be also great if someone could volunteer to give it a quick test > > On Thursday, September 1, 2016 at 1:32:37 PM UTC+10, James Dumay wrote: >> >> Hi all, >> >> How can I go about getting a new release of mailer? I recently added >> support to it for the Display URL Provider API >> >> https://github.com/jenkinsci/mailer-plugin/pull/29 >> >> Thanks >> 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. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/0a745368-0e5d-40be-81d5-517618548f9f% > 40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/0a745368-0e5d-40be-81d5-517618548f9f%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B7VDDCjdA%3DrsuszC_v6Bmyj78r1g27-0DORi%3DeoNoO1pw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: InjectedTest error when using plugin parent 2.3
We could include them, so that they get correctly resolved. The thing is that given the JTH version is configurable, some coordination between some versions would be needed (maybe using profiles)... Of course, this would be a transient situation for older plugins in the new parent pom but we should take care of it On Mon, Apr 18, 2016 at 8:21 AM, Oleg Nenashev <o.v.nenas...@gmail.com> wrote: > In my case is has been caused by the outdated dependency in parent pom > (2.6) > > [INFO] org.jenkins-ci.plugins:promoted-builds:hpi:2.26-SNAPSHOT > [INFO] +- org.jenkins-ci.main:maven-plugin:jar:2.0:compile > [INFO] | +- org.apache.httpcomponents:httpcore:jar:4.2.4:compile > > httpcore 4.3+ is required to make it operational. > Another similar issue in my tests: > https://github.com/groupon/DotCi/pull/213/files > > I would propose to add explicit lib dependencies to the parent POM. > @Andres WDYT? > > вторник, 8 марта 2016 г., 1:50:13 UTC+1 пользователь Jesse Glick написал: >> >> On Mon, Mar 7, 2016 at 5:44 PM, Andres Rodriguez >> <arodr...@cloudbees.com> wrote: >> > You should look in your dependency tree for conflicting dependencies >> and >> > resolve them. >> >> Example: >> >> >> https://github.com/jenkinsci/pipeline-stage-view-plugin/commit/c83c436aee00f1b02922cfa346f2ad33b3b044a3 >> > -- > 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/84dc4dff-1d84-40da-bef3-6d4bd0ceacbf%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/84dc4dff-1d84-40da-bef3-6d4bd0ceacbf%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B7NCW-v%2B3dSy3V8AjW7%3DcY2D3%2BqO5FDQnpg04NCo3ZXpw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: InjectedTest error when using plugin parent 2.3
ooter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > > > > -- > 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/4cbdae20-f052-4754-b647-db84b36c4b71%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/4cbdae20-f052-4754-b647-db84b36c4b71%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B4BToggasktWFasysnH0718COBu8_CqUzxTGj51hoOLrQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [PROPOSAL] New Parent POM for Jenkins Plugins
Hi Baptiste, The exclusions where introduced in this PR: https://github.com/jenkinsci/jenkins/pull/1816 I'll try to get more context to include in the POM comments. Thanks! On Sat, Jan 30, 2016 at 9:52 PM, Baptiste Mathus <m...@batmat.net> wrote: > Hi, > > Trying to build on an old version (1.447.2), I get the following error: > Found Banned Dependency: org.sonatype.sisu:sisu-guice:jar:3.1.0 > > Before/while excluding the dependency I'd like to understand, could > someone provide some context about that? > IIUC, this may be because we already use guice, and sisu-guice is a > patched one, so it would indeed conflict. > The question is: does it mean a whole bunch of plugins potentially would > still be embedding currently sisu-guice? > > I think that it would be good to document why those dependencies are > banned as a comment in > https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml#L510L514 > > Thanks for the feedback > > > 2016-01-22 19:58 GMT+01:00 Jesse Glick <jgl...@cloudbees.com>: > >> Update: we are up to 2.2, and 1.645 will have been the last release of >> the old POM. >> >> -- >> 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/CANfRfr1ZCqu8FAz7M254cFPWb4KPw9uXZx7aPjtdkOT2fe_EUA%40mail.gmail.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/CANWgJS6oZkExqbd%3DxzmTKVL-W%3DrX5LW_-5tHCHoqEceoQBOHug%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6oZkExqbd%3DxzmTKVL-W%3DrX5LW_-5tHCHoqEceoQBOHug%40mail.gmail.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B4HrviHDTLaiitYPjBoM2dWYE75%3Dws%3DEc232ba5xangKw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [PROPOSAL] New Parent POM for Jenkins Plugins
Hi, We've done tests with versions back to 1.509.4. Adjusting `jekins.version`, `jenkins-test-harness.version` and java.level to the appropriate settings should be no problem for previous versions. Regarding node stuff, you have `node.version`and `npm.version`properties, but other customization may require overriding some config in the profiles. Thanks! On Thu, Jan 21, 2016 at 11:07 AM, Robert Sandell <rsand...@cloudbees.com> wrote: > Thanks! > > Is there any known minimum version of core this can work with? > E.g. can I update my plugin to this with jenkins.version=1.404 ? > > Or maybe is there some recommended minimum core to start using this with? > I was thinking of the usage of npm and node settings might assume things? > > /B > > On Thu, Jan 21, 2016 at 8:45 AM, Andres Rodriguez < > arodrig...@cloudbees.com> wrote: > >> Hi, >> >> A first version with coordinates `org.jenkins-ci.plugins:plugin:pom:2.0` >> has been released. >> The source is now at its new location >> https://github.com/jenkinsci/plugin-pom. >> >> Regards, >> >> Andrés >> >> >> >> >> On Wed, Jan 20, 2016 at 6:10 PM, Andres Rodriguez < >> arodrig...@cloudbees.com> wrote: >> >>> >>> On Wed, Jan 20, 2016 at 6:03 PM, Jesse Glick <jgl...@cloudbees.com> >>> wrote: >>> >>>> On Wed, Jan 20, 2016 at 4:22 AM, Stephen Connolly >>>> <stephen.alan.conno...@gmail.com> wrote: >>>> >> I would suggest `javadoc:javadoc clean >>>> >> install` >>>> > >>>> > -1 as that may give a false fail on a clean checkout where the javadoc >>>> > plugin references generated classes >>>> >>>> Possibly. What I do in `workflow-plugin`, which has served me well, is >>>> to just include `javadoc:javadoc` in a profile activated when not >>>> `skipTests`. That ensures that all “full builds” including CI verify >>>> the absence of Javadoc errors, so you do not get a nasty surprise on >>>> release day. Routine developer builds—where you are just trying to get >>>> artifacts created so you can `hpi:run` etc.—do not incur the expense. >>>> >>>> >>> That has been included, but independently of findbugs: >>> https://github.com/andresrc/plugin-pom/blob/03f2c716f68f9142d3b8fbb14fd9b8af3d154b0a/pom.xml#L804-L827 >>> >>> >>>> -- >>>> 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/CANfRfr05ksqCt7UJmKd4FWnZUMtNAXASO6ESShWt-3hmqAYXUg%40mail.gmail.com >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Regards, >>> >>> Andres Rodriguez >>> www.cloudbees.com >>> >>> >> >> >> -- >> Regards, >> >> Andres Rodriguez >> www.cloudbees.com >> >> -- >> 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/CAM9%3DZ%2B7OJrWbhsLFkTavDqDTeZhkkM0tyYfy8hC1jKyxL1FZmA%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAM9%3DZ%2B7OJrWbhsLFkTavDqDTeZhkkM0tyYfy8hC1jKyxL1FZmA%40mail.gmail.com?utm_medium=email_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Robert Sandell > *Software Engineer* > *CloudBees Inc.* > > -- > 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/CALzHZS20iY1vg0nkRW8P5dBDgctCdnGP%3DC8O%2B1mYZg3u4bBJVw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS20iY1vg0nkRW8P5dBDgctCdnGP%3DC8O%2B1mYZg3u4bBJVw%40mail.gmail.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B5cE-MPe-KvOqs57k3JbuboP222vjUFp%2BXJ%3DJ0A88sjJA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [PROPOSAL] New Parent POM for Jenkins Plugins
You can set JTH to the version you need: `jenkins-test-harness.version` Thanks! On Thu, Jan 21, 2016 at 11:19 AM, Robert Sandell <rsand...@cloudbees.com> wrote: > Maybe it's the test harness that is setting the lower limit of 1.580.1 > > .B > > On Thu, Jan 21, 2016 at 11:07 AM, Robert Sandell <rsand...@cloudbees.com> > wrote: > >> Thanks! >> >> Is there any known minimum version of core this can work with? >> E.g. can I update my plugin to this with jenkins.version=1.404 ? >> >> Or maybe is there some recommended minimum core to start using this with? >> I was thinking of the usage of npm and node settings might assume things? >> >> /B >> >> On Thu, Jan 21, 2016 at 8:45 AM, Andres Rodriguez < >> arodrig...@cloudbees.com> wrote: >> >>> Hi, >>> >>> A first version with coordinates `org.jenkins-ci.plugins:plugin:pom:2.0` >>> has been released. >>> The source is now at its new location >>> https://github.com/jenkinsci/plugin-pom. >>> >>> Regards, >>> >>> Andrés >>> >>> >>> >>> >>> On Wed, Jan 20, 2016 at 6:10 PM, Andres Rodriguez < >>> arodrig...@cloudbees.com> wrote: >>> >>>> >>>> On Wed, Jan 20, 2016 at 6:03 PM, Jesse Glick <jgl...@cloudbees.com> >>>> wrote: >>>> >>>>> On Wed, Jan 20, 2016 at 4:22 AM, Stephen Connolly >>>>> <stephen.alan.conno...@gmail.com> wrote: >>>>> >> I would suggest `javadoc:javadoc clean >>>>> >> install` >>>>> > >>>>> > -1 as that may give a false fail on a clean checkout where the >>>>> javadoc >>>>> > plugin references generated classes >>>>> >>>>> Possibly. What I do in `workflow-plugin`, which has served me well, is >>>>> to just include `javadoc:javadoc` in a profile activated when not >>>>> `skipTests`. That ensures that all “full builds” including CI verify >>>>> the absence of Javadoc errors, so you do not get a nasty surprise on >>>>> release day. Routine developer builds—where you are just trying to get >>>>> artifacts created so you can `hpi:run` etc.—do not incur the expense. >>>>> >>>>> >>>> That has been included, but independently of findbugs: >>>> https://github.com/andresrc/plugin-pom/blob/03f2c716f68f9142d3b8fbb14fd9b8af3d154b0a/pom.xml#L804-L827 >>>> >>>> >>>>> -- >>>>> 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/CANfRfr05ksqCt7UJmKd4FWnZUMtNAXASO6ESShWt-3hmqAYXUg%40mail.gmail.com >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> >>>> -- >>>> Regards, >>>> >>>> Andres Rodriguez >>>> www.cloudbees.com >>>> >>>> >>> >>> >>> -- >>> Regards, >>> >>> Andres Rodriguez >>> www.cloudbees.com >>> >>> -- >>> 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/CAM9%3DZ%2B7OJrWbhsLFkTavDqDTeZhkkM0tyYfy8hC1jKyxL1FZmA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAM9%3DZ%2B7OJrWbhsLFkTavDqDTeZhkkM0tyYfy8hC1jKyxL1FZmA%40mail.gmail.com?utm_medium=email_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Robert Sandell >> *Software Engineer* >> *CloudBees Inc.* >> > > > > -- > Robert Sandell > *Software Engineer* > *CloudBees Inc.* > > -- > 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/CALzHZS2MTGRfjBDdvBjae9hUWqVwPwGApY7cyoirzpCOw7OXNQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS2MTGRfjBDdvBjae9hUWqVwPwGApY7cyoirzpCOw7OXNQ%40mail.gmail.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B4UQC1MLohcMV7h3UKhPCzTf%2B24rvnb5c8QuirqdffRJw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [PROPOSAL] New Parent POM for Jenkins Plugins
Hi, A first version with coordinates `org.jenkins-ci.plugins:plugin:pom:2.0` has been released. The source is now at its new location https://github.com/jenkinsci/plugin-pom. Regards, Andrés On Wed, Jan 20, 2016 at 6:10 PM, Andres Rodriguez <arodrig...@cloudbees.com> wrote: > > On Wed, Jan 20, 2016 at 6:03 PM, Jesse Glick <jgl...@cloudbees.com> wrote: > >> On Wed, Jan 20, 2016 at 4:22 AM, Stephen Connolly >> <stephen.alan.conno...@gmail.com> wrote: >> >> I would suggest `javadoc:javadoc clean >> >> install` >> > >> > -1 as that may give a false fail on a clean checkout where the javadoc >> > plugin references generated classes >> >> Possibly. What I do in `workflow-plugin`, which has served me well, is >> to just include `javadoc:javadoc` in a profile activated when not >> `skipTests`. That ensures that all “full builds” including CI verify >> the absence of Javadoc errors, so you do not get a nasty surprise on >> release day. Routine developer builds—where you are just trying to get >> artifacts created so you can `hpi:run` etc.—do not incur the expense. >> >> > That has been included, but independently of findbugs: > https://github.com/andresrc/plugin-pom/blob/03f2c716f68f9142d3b8fbb14fd9b8af3d154b0a/pom.xml#L804-L827 > > >> -- >> 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/CANfRfr05ksqCt7UJmKd4FWnZUMtNAXASO6ESShWt-3hmqAYXUg%40mail.gmail.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Regards, > > Andres Rodriguez > www.cloudbees.com > > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B7OJrWbhsLFkTavDqDTeZhkkM0tyYfy8hC1jKyxL1FZmA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [PROPOSAL] New Parent POM for Jenkins Plugins
On Wed, Jan 20, 2016 at 6:03 PM, Jesse Glick <jgl...@cloudbees.com> wrote: > On Wed, Jan 20, 2016 at 4:22 AM, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: > >> I would suggest `javadoc:javadoc clean > >> install` > > > > -1 as that may give a false fail on a clean checkout where the javadoc > > plugin references generated classes > > Possibly. What I do in `workflow-plugin`, which has served me well, is > to just include `javadoc:javadoc` in a profile activated when not > `skipTests`. That ensures that all “full builds” including CI verify > the absence of Javadoc errors, so you do not get a nasty surprise on > release day. Routine developer builds—where you are just trying to get > artifacts created so you can `hpi:run` etc.—do not incur the expense. > > That has been included, but independently of findbugs: https://github.com/andresrc/plugin-pom/blob/03f2c716f68f9142d3b8fbb14fd9b8af3d154b0a/pom.xml#L804-L827 > -- > 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/CANfRfr05ksqCt7UJmKd4FWnZUMtNAXASO6ESShWt-3hmqAYXUg%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B70wf7TfK1j1dYvQ0p1FoYNCyXAb24d8dVvo8qC92VNjw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [PROPOSAL] New Parent POM for Jenkins Plugins
On Tue, Jan 19, 2016 at 8:49 PM, Jesse Glick <jgl...@cloudbees.com> wrote: > On Mon, Jan 18, 2016 at 4:35 AM, <arodrig...@cloudbees.com> wrote: > > The current proposal is being pushed to > > https://github.com/andresrc/plugin-pom. > > Since there is no PR for the POM itself, I am putting comments here. > > `` does not seem like it belongs. The POM need not be > used by plugins hosted under the Jenkins organization. > Done > > AFAIK the test dependency on `jenkins-war` should be on > `war-for-test`, not `war`. > > Done > I would suggest `javadoc:javadoc clean > install` rather than `clean > install javadoc:javadoc` since Javadoc generation > is likely a lot faster than running tests, and more likely to be > failing without anyone knowing about it before. > > Consider > https://github.com/jenkinsci/workflow-plugin/blob/master/pom.xml#L201-L211 > which I have found invaluable. Could be added later of course. > > I've added a mix between the existing approach and workflow's, in order to keep the exclusionFilter profile optional as well. I've also moved running javadoc when tests are active to a profile and removed it from the release profile. > -- > 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/CANfRfr0ZHQrbgT1QP5G3DxgifLTO4M1g3ZkMv-H7aVK3_1g_XQ%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B4jTjvSFkG1dHswXSu%2BZLhRCLyquYT80hP2eJUkqj04HQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [PROPOSAL] New Parent POM for Jenkins Plugins
On Tue, Jan 19, 2016 at 8:19 PM, Jesse Glick <jgl...@cloudbees.com> wrote: > On Tue, Jan 19, 2016 at 6:27 AM, <arodrig...@cloudbees.com> wrote: > > Decide the final artifact maven coordinates: following the criteria used > in > > jenkins-test-harness, we could keep the same groupId / artifactId than > > before and bump version to 2.0. > > Yes I think making it be `org.jenkins-ci.plugins:plugin:pom:2.0` would > be appropriate. If nothing else, this advertises it as an upgrade for > people who use standard Maven tools or IDEs to look for new versions > of artifacts (in this case parent POM). Of course you need to make > certain changes to your plugin’s POM to use it (in most cases you > would want to define `jenkins.version` at a minimum), but that seems > OK—the bump in major version should be sufficient indication that > something noteworthy has changed. > That was my thought as well. It has already been updated to to those coordinates. > > > Create a repository in the jenkinsci GitHub org (by someone with > permissions > > forking the existing one). > > I can do this if there are no objections. The main question is the > repository name. `plugin-pom`? > > That was my thought as well. I checked is was available before creating the initial repo. > > Perform a release. > > And I suggest that `jenkinsci/jenkins/plugins/pom.xml` be deleted. > Sure, I'll prepare a PR. Thanks > > -- > 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/CANfRfr0A6jrobt2phksSqC9cE_qh%3D56wEnhOmurhFerj5DgRmA%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B6TKtiy3sQVf3P-f0fgxR3G4HBsk5POD0jFvzOhHGcRzQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Adopt a Plugin: port-allocator
Thank you very much!! On Wed, Nov 18, 2015 at 4:15 PM, Baptiste Mathus <m...@batmat.net> wrote: > Seems like you have the id on JIRA. > > Done. > > 2015-11-18 16:11 GMT+01:00 Baptiste Mathus <m...@batmat.net>: > >> Hi, >> >> Is your JIRA id the same? or different? >> >> Thanks >> >> 2015-11-18 16:03 GMT+01:00 <arodrig...@cloudbees.com>: >> >>> Hi, >>> >>> I would like to adopt the port-allocator plugin ( >>> https://wiki.jenkins-ci.org/display/JENKINS/Port+Allocator+Plugin), so >>> I request commit access to the repo ( >>> https://github.com/jenkinsci/port-allocator-plugin). My github id is >>> andresrc. >>> >>> Thanks! >>> >>> -- >>> 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/f85cac09-2851-4f42-8163-dab8ebb91080%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/f85cac09-2851-4f42-8163-dab8ebb91080%40googlegroups.com?utm_medium=email_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Baptiste MATHUS - http://batmat.net >> Sauvez un arbre, >> Mangez un castor ! >> > > > > -- > Baptiste MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! > > -- > 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/CANWgJS5%2BmQ88PNfnt8MvBmv%2BE%2B%3Dy5aTTLLKq0qW5nObvGZJYqw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5%2BmQ88PNfnt8MvBmv%2BE%2B%3Dy5aTTLLKq0qW5nObvGZJYqw%40mail.gmail.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- 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/CAM9%3DZ%2B66Qc2%3DyMrE9fPqAcia1DGbFKfw7fyWWkttg09wKOGWSQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
