Re: Devops World Jenkins World 2019: Slide Desk Presentation Templates?

Hi Martin, I am adding Skylar to this thread so she can send you the template. Thank you. alyssa On Thu, Jul 11, 2019 at 6:33 PM martinda wrote: > Hi, > > I'd like to work on my slides for DW/JW 2019. > > Is there a Google Slide Deck template available? > > Thanks, > Martin > > -- > You

Devops World Jenkins World 2019: Slide Desk Presentation Templates?

Hi, I'd like to work on my slides for DW/JW 2019. Is there a Google Slide Deck template available? Thanks, Martin -- 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: Jenkins Contributor Summit - Aug 12 San Francisco

Hi Tracy, I plan on being there. Main interest: Google Summer of Code. Martin -- 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: XTrigger-Lib needs maintenance/release

Pull request submitted for release permissions: https://github.com/jenkins-infra/repository-permissions-updater/pull/1216 Could I also be give access to the github repo for xtrigger-lib, please? Repo: https://github.com/jenkinsci/xtrigger-lib GitHub id: TonyNoble Jenkins id: stealthdj I'll look

Re: Trouble verifying build history deletion with mock Jobs

I have updated my PR#3 with a WORK-IN-PROGRESS titling and mentioned not to merge it in the description. On Thursday, July 11, 2019 at 4:16:37 PM UTC-4, Benjamin Beggs wrote: > > This is good advice, I will follow it moving

Re: Trouble verifying build history deletion with mock Jobs

This is good advice, I will follow it moving forward. FWIW, the title line of the PR description said that unit tests were *currently *being written for feature and the last comment made on it mentioned my intention to change the unit testing method with a set of rewrites. On Thursday, July

Re: Trouble verifying build history deletion with mock Jobs

This is good advice, I will follow it moving forward. FWIW, the title line of the PR description said that unit tests were *currently *being written for feature and the last comment made on it mentioned my intention to change the unit testing method with a set of rewrites. On Thu, Jul 11, 2019 at

Re: Trouble verifying build history deletion with mock Jobs

I've found its good practice to prefix/include "WIP" or "WORK IN PROGRESS" in the title. Labels are only assignable by committers/triagers On Thu, Jul 11, 2019 at 12:46 PM martinda wrote: > For: > >> to tell him that PR#2 needed review and shouldn't have been merged >> > > Are you able to

Re: Trouble verifying build history deletion with mock Jobs

For: > to tell him that PR#2 needed review and shouldn't have been merged > Are you able to assign a label to the PR? I have used labels like "do not merge" before. Martin -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe

Re: XTrigger-Lib needs maintenance/release

On Thu, Jul 11, 2019 at 10:27 AM Tony Noble wrote: > any breaking change of the xtrigger plugin would require all dependant > plugins to be updated and a co-ordinated release organised Yes…so do not make breaking changes. > The issue I see there is that (from what I can see) all the dependent

Re: Plugin pom http/https mass cleanup

On 7/11/19 8:22 AM, Jesse Glick wrote: On Thu, Jul 11, 2019 at 7:51 AM Daniel Beck wrote: 3. Start with PRs, but merge myself when maintainers don't. This is basically what Oliver ended up doing when we added Jenkinsfiles to plugin repositories.[2] +1 for this. An unmentioned benefit over #1

Re: SCMCheckout in WorkflowRun

> > On Wed, Jul 10, 2019 at 5:14 PM Ullrich Hafner > wrote: >> 1. Checkout from SCM >> 2a Build >> 2b Record warnings and blame authors in affected files > > Yet there is a `dir` step in there. So are you talking about this? > > dir('src') { > checkout scm > sh 'mvn install' >

Re: Plugin pom http/https mass cleanup

I like #3 as well. If you're not already using some form of pull request creation script, I recommend the `hub ` command from GitHub. I like submitted a pull request from the same terminal window where I'm performing all my other operations. On Thu, Jul 11, 2019

Re: Trouble verifying build history deletion with mock Jobs

Thanks for all the ideas here. I think I've settled on my implementation for this, it's a little different than what's been suggested but I think it's efficient and clean. The ModifiedLogRotator subtracts the daysToKeep integer from the Calendar.DAY_OF_YEAR record. I've added a test class

Re: XTrigger-Lib needs maintenance/release

On Thu, Jul 11, 2019 at 3:17 PM Jesse Glick wrote: > Completely routine; you just declare a Maven dependency and you are > done. Certainly less exotic and trouble-prone than the current design. > > > https://jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/ > > Thanks.

Re: Plugin pom http/https mass cleanup

On Thu, Jul 11, 2019 at 7:51 AM Daniel Beck wrote: > 3. Start with PRs, but merge myself when maintainers don't. This is basically > what Oliver ended up doing when we added Jenkinsfiles to plugin > repositories.[2] +1 for this. An unmentioned benefit over #1 is that CI will catch fatal

Re: XTrigger-Lib needs maintenance/release

On Thu, Jul 11, 2019 at 6:14 AM Tony Noble wrote: > how to create plugins that are essentially subclasses of other plugins (which > is what would need to happen if xtrigger was migrated to be a plugin) Completely routine; you just declare a Maven dependency and you are done. Certainly less

Re: Jenkins 2.176.2 LTS RC testing started

On 02/07/2019 17.37, Daniel Beck wrote: On 2. Jul 2019, at 10:31, Oliver Gondža wrote: JENKINS-57515 Major Jenkins 2.181 AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so

Re: Plugin pom http/https mass cleanup

Definitely 3 sounds great. And yeah, I personally still would like at some point to revive the recurring auto-pr approach from the other thread to cleanup our status wrt. maintainership (and hence encourage new maintainers to step up on abandoned plugins). Le jeu. 11 juil. 2019 à 13:51, Daniel

Plugin pom http/https mass cleanup

Hi everyone, a large number of plugins (and possibly other components) define HTTP URLs for dependency resolution and in some cases, distribution repositories. I'd like to clean this up. There are a few options here: 1. I just directly commit to the repos with this minimal change. AFAICT,

Re: XTrigger-Lib needs maintenance/release

Hi @oleg-nenashev, That sounds ideal. I do remember the thread now, but have to admit - I'm very much of the 'just keep it working' approach for the moment, until I get my head around how to create plugins that are essentially subclasses of other plugins (which is what would need to happen if

Re: XTrigger-Lib needs maintenance/release

FTR, there was a thread about the next steps for XTrigger lib: https://groups.google.com/forum/#!searchin/jenkinsci-dev/XTrigger%7Csort:date/jenkinsci-dev/voKBrqz7V_o/rCP5ysYZBwAJ AFAICT, we still need to get a release, and ownership has not been fully transferred to anyone.

XTrigger-Lib needs maintenance/release

I realise this isn't a plugin as such, so not sure how the process would work. A number of trigger plugins, mine included (urltrigger) rely on xtrigger-lib to perform the core job handling and cron scheduling. From what I can see, Gregory Boissinot used to maintain this, along with the dependent