Re: kerberos-sso plugin lookign for a new maintianer.

ti > > On Thu, Nov 2, 2023 at 5:31 PM ogondza wrote: > >> Thanks, Jagruti Tiwari! >> >> I have sent you and invitation to maintain the GH repo. Follow up with >> filing a PR to get the release permissions, and tag me for approval: >> https://www.jenkins.io

Re: kerberos-sso plugin lookign for a new maintianer.

and functioning. > > I would like to learn the ropes of a Jenkins plugin maintainer and > maintain many more plugins in the future. > > Thanks, > Jagruti Tiwari > > On Mon, 30 Oct, 2023, 4:50 pm ogondza, wrote: > >> Hello, >> >> As the only active

Re: kerberos-sso plugin lookign for a new maintianer.

The repo: https://github.com/jenkinsci/kerberos-sso-plugin On Monday, October 30, 2023 at 12:19:58 PM UTC+1 ogondza wrote: > Hello, > > As the only active maintainer of the plugin for past several years, I will > no longer maintain it going forward. (No time, the org migr

kerberos-sso plugin lookign for a new maintianer.

Hello, As the only active maintainer of the plugin for past several years, I will no longer maintain it going forward. (No time, the org migrated to SAML). If you are interested to carry the torch long term, please let me know. Otherwise, I will flag the plugin officially up for an adoption.

Re: Releasing JCasC support for ghprb-plugin

I understand it feels strange, though it is the second best thing we can do in case we lack a maintainer. On Wednesday, January 6, 2021 at 5:53:37 PM UTC+1 msi...@cloudbees.com wrote: > I'd prefer if this plugin has an actual maintainer. Otherwise, this > also seems like false advertising that

Re: Data binding: Bind repeatable list of textboxes into List

Thanks for confirmation, folks. The issue have pointed me to using textarea to represent the list of strings making my life a whole lot simpler! On Wednesday, January 6, 2021 at 7:57:36 PM UTC+1 Jesse Glick wrote: > Note that `CustomDescribableModel` was intended to help with this sort of >

Re: LTS baseline selection for the successor of 2.235

Avoiding 2.250 so it is not confused with 2.150 is an interesting suggestion, though it does not outweigh stability so 2.249 is preferable over 2.251. I do not think backporting the only fix from 2.250 to 2.249 is going to confuse anyone: users need to track *when* the fix was introduced in

Re: Backporting for LTS 2.222.1 started

I agree that this one is quite nasty. Let's keep an eye on that and see if it can be fixed in .1. -- 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

Re: Jenkins 2.204.3 LTS RC testing started

Mark, how does the second RC perform in your testing? -- 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

Re: Jenkins 2.204.3 LTS RC testing started

Mark, thanks for reporting this. I have published an RC respin[1] with Java 8, until we identify the reason why is this causing problems. Please make sure the ongoing testing is done with ca01d0bf523d6752f54277ca4c91feef0d60acc75c42d65f65bbefe09f9e8e69 (sha256). Thanks! [1]

Re: Jenkins 2.204.1 LTS RC testing started

Thank you guys very much for keeping the quality bar high! As Baptiste said, better to be alarmed for without defect. My internal testing have not revered anything. The 2.204.1 can be released today. -- oliver -- You received this message because you are subscribed to the Google Groups

Re: Backporting for LTS 2.204.1 started

> >> I went through 2.205 and 2.206 changes and marked JIRA issues which may >> deserve backporting. >> >> Best regards, >> Oleg >> >> >> On Friday, November 22, 2019 at 9:18:16 AM UTC+1, ogondza wrote: >>> >>> Backporting

Re: Next LTS baseline selection

I like that idea, Jesse. Can we agree on picking 2.204 with JENKINS-58993 patched to only fail when assertions are on? -- 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

Re: Next LTS line selection open. Due 2019-08-27

See the previous message: https://groups.google.com/d/msg/jenkinsci-dev/FM8_kG1kdw8/sIOvRmEeBQAJ -- 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

Re: Jenkins 2.176.3 LTS RC testing started

I have published new RC with the late backport in. Available via http://mirrors.jenkins-ci.org/war-stable-rc/2.176.3/jenkins.war -- oliver -- You

Re: 2.176.1 LTS RC regression found (Was: Jenkins 2.176.1 LTS RC testing started)

Alright, I have filed https://github.com/jenkinsci/jenkins/pull/4047 to revert remoting on master. Once reviewed, I will backport that revert to LTS as well. Thanks! On Tuesday, May 28, 2019 at 5:13:02 PM UTC+2, Oleg Nenashev wrote: > > Remoting version downgrade is reasonable IMO. > > > On

Re: Jenkins extended choice parameter plugin: do you have write permission?

This is the second public call for maintainer's attention with no reply. I have flagged the plugin up-for-an-adoption. Vimil, feel free to correct once you are back, but for now, we have to presume this is abandoned. Thanks -- oliver -- You received this message because you are subscribed to

Re: The future of LTS certification

There is a striving discussion in the docs. One thing I failed to realize we need soon enough is the list of "Recognized use-cases" of ATH (drafted in the doc) I would like to get feedback on from as many people as I can. Another hot topic is how do deal with tests failing because of a defect

Re: The future of LTS certification

Thank you everyone for the feedback. We have put together an initial draft of what will become new process of ATH maintenance. I intend to collectively craft the final shape of the document in a couple of coming weeks and then make it official by adding it as a github repo contribution

Re: Backporting for LTS 2.150 started

Backporting is over. We have one candidate postponed for .2: Postponed: JENKINS-48775CriticalTue, 20 Nov 2018 14:53:06 + Proxy authentication error 407 even if 'check proxy' works https://issues.jenkins-ci.org/browse/JENKINS-48775 Fixed: JENKINS-54551

Re: Backporting for LTS 2.121.1 started

The backporting window is closing this Wednesday. There ware no candidates nominated (likely due to recent baseline choice) BUT there is the outstanding problem of JENKINS-51253[0]. There does not seem to be a consensus on whether/how to fix it[1] so I am wondering which version of remoting we

Re: Speeding up the ATH

Hey, Here is my draft for the smoke tests https://github.com/jenkinsci/acceptance-test-harness/pull/365 and documentation of the test acceptance / removal: https://github.com/jenkinsci/acceptance-test-harness/pull/364 Please, comment there for tuning. Note things can be further refined after

Re: Jenkins 2.73.1 LTS RC testing started

Agreed on the meeting the release will be cut with the regression compared to 2.60 line (with remoting 3.10) and Jenkins docker container will be updated not to be impacted. The proper fix will target 2.73.2. -- oliver -- You received this message because you are subscribed to the Google

Re: Jenkins 2.73.1 LTS RC testing started

I have reverted remoting back to version 3.10 and pushed another RC asking Mark to retest. Relevant issue https://issues.jenkins-ci.org/browse/JENKINS-46754 -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Re: Backporting for LTS 2.73.1 started

Given my traveling next week and a set of nontrivial candidates, I am postponing RC to Monday after scheduled date 2017-09-04. -- 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

Re: Backporting for LTS 2.60.1 started

Backporting is ready and RC will be pushed tomorrow morning UTC time. $ lts-candidate-stats 2.60.1 Rejected: JENKINS-40693MinorFri, 26 May 2017 08:06:29 + badMessage: 400 Bad Host header for HttpChannelOverHttp

Re: Jenkins 2.46.3 LTS RC testing started

/InstallWizardTest/wizardInstallSugestedTest/ [2] ``` INFO: Attempting to dynamic load /home/ogondza/code/jenkins/acceptance-test-harness/jhrevert/plugins/workflow-job.jpi May 24, 2017 2:29:43 PM hudson.model.UpdateCenter$DownloadJob run SEVERE: Failed to install Pipeline: Job java.io.IOException: Failed

Re: Pipeline DSL objects - class-loaders and compilation

Thanks for commenting on the PR. Am I right to assume that there is no practical advantage to distribute the objects that are returned into pipeline as runtime-compiled groovy, much less loading it through pipeline provided classloader? Returning POJOs of compiled classes is the way to go...

Re: Jenkins 2.46.2 LTS RC testing started

The tests looks good and noone reported any problems as well. This will be released on Wednesday unless something urgent pops up. -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

I am undecided on the subject. There clearly always are reasons to use newer/better version but is JDK 7 support really blocking us somewhere? Bugs we cannot fix / need to awkwardly compensate, features we can not deliver on Java 7? I felt much stronger against dropping Java 6 as we identified

Re: PR Builder not setup for foreman-node-sharing plugin

Thanks guys, it works now. -- 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

Re: PR Builder not setup for foreman-node-sharing plugin

Hmm, There is no job for that plugin at all. When I tried to create it from maven template I got "ERROR: script not yet approved for use". Is this not something that should be done by IRC bot when plugin is forked? -- oliver -- You received this message because you are subscribed to the

Re: Docker workflow runs with user not fully configured

https://issues.jenkins-ci.org/browse/JENKINS-38438 -- 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.

Re: [SPAM Low] [Proposal] - Release Jenkins 2.7.4 on this week

The test results[1] looks good. I am pushing the RC at the moment for manual retesting. Once confirmed, I am ok to get that released. FYI, I suggest[2] to have an explicit link type for issue that introduced another one. So hopefully, such situation will be lot less likely to reoccur. [1]

Re: Jenkins 2.7.3 LTS RC testing started

I have respun the RC with https://github.com/jenkinsci/jenkins/commit/27d8f06f1baabb320cc86527250bed5a7dacf85e reported by Oleg. Please make sure you are using build "rc-08/24/2016 06:31" for further testing. Thanks -- oliver -- You received this message because you are subscribed to

Re: Automate recommended plugin unittest run against latest Jenkins core

Right, not the best wording. What I had in mind is: "It is something we would like to have confirmed before declaring the release is good to go". Unfortunately, many maintainers do not put that much effort into making sure their plugins work with latests cores, myself including. -- oliver --

Re: Backporting for 2.7.1 has started

I consider backporting to be close. All was backported except for JENKINS-35641 and JENKINS-34923 where I would like it to have some extra soaking time. Note that I will not be able to attend the Governance meeting (travelling) so I will proceed with the rc at the closest time I am available

Re: Backporting for 2.7.1 has started

stephenconnolly on JENKINS-35402: [~olivergondza] I really would like this in the 2.7.1 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

Re: Jenkins cloud health reporting

An example of how integration with provisioning plugins will look like: https://github.com/jenkinsci/openstack-cloud-plugin/pull/71 -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop

Re: Backporting for 1.651.2 has started

I have backported remoting 2.57 to fix JENKINS-28289, JENKINS-33999 and JENKINS-32980. In case it incorporates another problems I have miss, let me now here or on the meeting. -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

Re: Jenkins cloud health reporting

Finally, there is something to show: -- 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

Re: Backporting for 1.651.2 has started

I have backported the nobrainers but the remoting related stuff deserves another look tomorow. -- 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

Re: Backporting for 1.651.2 has started

Consider https://github.com/jenkinsci/jenkins/pull/2283 once merged. -- 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

Backporting for 1.651.2 has started

Hi, Backporting for next LTS release is on. The RC will be published 2016-04-27. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed:

Re: Backporting for 1.651.1 has started

As agreed on meeting, I reverted JENKINS-28289 and JENKINS-26580 as they caused regression (JENKINS-33886). The tests runs fine. Oliver, please publish the RC. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this

Re: Jenkins cloud health reporting

Thanks, I have started to work on this and expect to have something to show latter this week. It seems to be possible to do a lot in cloud agnostic way (count provisioning attempts, report failures with exceptions, timings, etc.). Though, more interesting things will require plugins to

Re: [ANN] Openstack plugin 2.0 Beta is out

Version 2.0 is out[1], it should be available in update centers shortly. [1] http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/openstack-cloud/2.0/ -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: LTS status

I went through my regular routine and all looks good. Nobody else reported anything so I guess that is a green light for you. -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: Jenkins 2.0 initial setup plugin selection

How about some criteria for testing? Requiring X% for code coverage is clearly wrong. But how about the plugin needs to have _some_ tests? What I believe we should do is having a CI that verifies the plugin selection against the core version. Not sure we should use ATH or plugin-compat-tester

Re: Jenkins 1.642.1 LTS RC testing started

As agreed post meeting, this is good to be released. Kohsuke, could you? -- 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

Re: Backporting for 1.636.1 has started

The backporting is over. On the last meeting we agreed[1] to use more recent and more stable LTS baseline: 1.642. Kohsuke, we are ready for the RC. [1] http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-01-06-19.01.html -- oliver -- You received this message because

Re: Script Security plugin dry-run for pre-approval?

I would welcome if there ware multiple strategies aside of Whitelist-ing. I have got several plugins to update, but as those started to use script-security, I have to check it is not going to break anything first. What would help me (and Andrew) in this case is something akin permissive

Re: Changing the upcoming LTS baseline?

I have prepared stable branch for both 1.636 and 1.642[1]. Running ATH agains both: https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable/549/ https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable-1.642/1/ [1]

Re: Jenkins 1.625.3 LTS RC testing started

We are ready for the release. -- 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

Re: Backporting for 1.625.3 has started

Backported JENKINS-31649. Thanks Jesse. -- 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

Re: Backporting for 1.625.3 has started

As Daniel said, none of the issues was released in any weekly. I agree JENKINS-31649 is of low risk so I am opened to backport it. Although, the priority is only major, not many votes, not clear who is affected, no unittests. I do not consider JENKINS-31718 to be a serious candidate for .3 as

Re: Jenkins 1.625.2 LTS RC testing started

Testing is done, we are ready for the release. -- 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

Re: 1.625.2 status

It is, I have just updated the testing thread. -- 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

Re: Request hosting for a plugin

Great, forked as https://github.com/jenkinsci/openshift-pipeline-plugin. Welcome aboard! -- 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

Re: Jenkins 2.0 proposal

I see several problems with this BC breaking approach: - Countless instances will have to use both the DB and the FS as backend simultaneously for some time. If this will span several upgrades, downgrades will be a pain for the whole time. - There are plugins that depend on files heavily. (Copy

Re: Backporting for 1.625.1 has started

Is this tracked somewhere? How will this be addressed on master branch? -- 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

Re: Guidance on how far SECURITY fixes should go

On Tuesday, September 15, 2015 at 2:04:54 PM UTC+2, Stephen Connolly wrote: > > > The security fixes are typically prepared in advance for this reason > and pushed to every branch at the same time to minimize exposure. If > we do not do the concurrent releases then LTS becomes vulnerable. I

Re: Protecting githib master branches against force-push

My idea was preventing incidents like [1] to happen. I do not see a problem with force-pushing to feature branches (provided noone based ones work on that), not to mention we do not encourage people to create feature branches in core repo. [1]

Re: 1.609.3 RC posted

It does not seems to be published. [1] gives 404 and [2] serves 1.609.1-rc (not even 1.609.2-rc). [1] http://mirrors.jenkins-ci.org/war-stable-rc/1.609.3/jenkins.war [2] http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war -- oliver -- You received this message because you are

Re: Approval for XebiaLabs patron message

+1 -- 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

Re: Backporting for 1.609.3 has started

Right, The backporting is finished. -- 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

Re: Backporting for 1.609.2 has started

I have backported the rest: JENKINS-28690, JENKINS-28840, JENKINS-27289, JENKINS-14899 and JENKINS-28926. -- 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

Re: Is there a way to hide default actions?

I am not familiar with the plugin implementation enough, though I see no reason why such behaviour should not be in core as well. Anyway, having 2 plugins that does to same with slightly different defaults sounds odd to me. How about adding an option to the existing plugin that would register

Re: Is there a way to hide default actions?

There already is a plugin that injects parameters via URL already[1]. In that particular case it is the _plugin's_ URL that was hidden as it was causing confusion to users and was accessed by pre-generated URLs most of the time. [1]

Re: Backporting for 1.609.2 has started

On Tuesday, June 16, 2015 at 10:14:21 PM UTC+2, Jesse Glick wrote: The important part of the JENKINS-27289 was released over a month ago. Right: https://github.com/jenkinsci/jenkins/compare/8e19340...905930f -- oliver -- You received this message because you are subscribed to the Google

Re: Backporting for 1.609.2 has started

On Tuesday, June 16, 2015 at 9:10:37 PM UTC+2, Daniel Beck wrote: Could you add the end of backporting to your announcements in the future? It would be helpful to know when they're shorter than the usual two weeks. I proposed the qualifying half of JENKINS-27289 on the 10th, less than 48

Re: Backporting for 1.609.2 has started

Both backported. -- 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

Re: [UX] Jenkins controls compaction proposal

I am quite surprised how many people is dissatisfied with the sidepanel in current form. However, shell we ever do something about sidepanel, we will have to deal with it gracefully as plugins can contribute sidepanel tasks in several ways. Representing controls in an uniform way would be

Re: What will the next LTS be (was Re: Next LTS is 1.596)

-requisite for us to be able to mechanically pick the LTS base version - Low quality work can get into those releases because of the pressure it poses on contributors/commiters 19:34:05 ogondza I am afraid that knowing what will be the next lts before it is released can motivate people push

Re: Backporting for 1.596.2 started

Backporting is complete, we are ready for RC. -- 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

Re: Jenkins 1.596.1 RC Testing started

Testing period is over, we are ready for the release. -- 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.

Re: Backporting for 1.596.1 started

Backporting is over, we are ready for the RC. -- 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

Re: Test Failure: UpdateCenterTest.data:47-doData:73 » CertificateExpired NotAfter: Tue Jan 27

https://issues.jenkins-ci.org/browse/INFRA-219 -- 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

Re: Hot to set a particular buildwrapper using java/Groovy

Call add() to buildWrappersList. See: https://github.com/jenkinsci/build-timeout-plugin/blob/master/src/test/java/hudson/plugins/build_timeout/BuildTimeoutWrapperIntegrationTest.java#L47 -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers

Re: ATH execution for 580.2

I have merged and pushed jenkins-1.580.2 to stable-1.580. The pipeline should be back again. -- 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

Re: Jenkins 1.580.2 RC Testing

On Thursday, December 4, 2014 3:08:39 PM UTC+1, Mark Waite wrote: Is there a way to make that available as a docker image so that my startup and recovery time from experimenting with the RC would be reduced? Maybe it is already available and I don't know where to look? No, as far as I

Re: Backporting for 1.580.1 started

That would be great, Jesse, thanks! I will let you know as soon as backports are ready. -- 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

Re: 1.565.3 LTS RC testing started

Manual testing is over. Thank you guys for your help! -- 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

Re: 1.565.2 LTS RC testing started

RC testing is over. No new regressions introduced. -- 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

Re: 1.565.1 LTS RC testing started

RC testing is over. No new regressions was discovered. Thank you guys for testing it! -- 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

Re: Backporting for 1.565.1 has started

Backporting is over with 25 fixes in 1.565.1. RC should be published later today. Single candidate was rejected:: https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=truejqlQuery=labels+%3D+%221.565.1-rejected%22 -- oliver -- You received this message because you are

Re: automatic workspace cleanup

On Saturday, July 5, 2014 8:05:00 AM UTC+2, Shirhen Ince wrote: I want it to be automatic not that every user will need to chose to do so... this plugin does not do it. This is valid feature request for WS Cleanup plugin. -- oliver -- You received this message because you are subscribed

Re: Backporting for 1.554.3 started

Backporting is over. We are ready for RC. -- 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. For

Re: People using the LDAP plugin to connect to Active Directory

Let's agree to disagree. I'll note one more scenario used by several people: running ATH against old Jenkins versions. It used to work with 1.480 and a bunch of outdated plugins until very recently with minimal maintenance costs. I am keen to see your scalability framework made public. --

Re: People using the LDAP plugin to connect to Active Directory

I agree with Ulli here. Upgrade tests is something that would be great to have but turning ATH to what you describe does not make sense. 1) We _do_ want to know that version under test work on its own and not only if you upgrade your config from some earlier version. 2) If we start using

Re: How the get the user that does the build?

Hi, See `Run.getCauses()`. You can extract user identity from UserCause|UserIdCause. -- 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

Re: Backporting for 1.554.2 started

On Wednesday, May 14, 2014 11:20:27 AM UTC+2, Stephen Connolly wrote: https://github.com/jenkinsci/jenkins/commit/7c620e9fd321029e05f7cc994d3da1dde48411f7 But I also understand if this is too late in the day and we need to wait for 1.554.3... Yes, we will. Note the issue is not resolved.

Re: Solidifying acceptance-test-harness API

On Tuesday, May 13, 2014 12:49:54 PM UTC+2, Robert Sandell wrote: As long as the version number reflects API compatibility I don't see any problems with not staying backwards compatible and no direct need for a stable version. This is a good compromise. -- You received this message

Re: Backporting for 1.554.1 started

See backported fixes: https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+10172+AND+labels+%3D+%221.554.1-fixed%22 Tests are passing[1], acceptance test are in a good shape[2]. Thanks marco-miller for testing and backporting

Re: TDD for Jenkins Plugins and Groovy Extenions

Hi, I do not think there is any systematic way of doing this as the groovy scripts are evaluated in GroovyShell configured by the plugins. Each plugin configure variable binding on its own. Object passed might be both difficult to mock and available only under some circumstances. What can

Re: Unable to run selenium-test at jenkins.ci.cloudbees.com

see https://cloudbees.zendesk.com/requests/15609 -- 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.

Re: Unable to run selenium-test at jenkins.ci.cloudbees.com

Is there any development? -- 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. For more options, visit

Re: Backports for 1.532.2

Backporting those two plus JENKINS-20951. -- 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. For more

Re: Backports for 1.532.2

It seems that rc was no released. I have backported some more fixes. Selenium test verified locally as the cloudbees job is still broken. Kohsuke, please post RC. -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe

Re: mvn release does not work, only publishes SNAPSHOT releases

I have seen this problem today using: maven 3.1.1 maven-releas-plugin 2.2.2 git 1.8.5 Worked around downgrading git to 1.8.4. http://jira.codehaus.org/browse/MRELEASE-812 -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To

  1   2   >