Re: [Build failure analyzer] Request commit access

; > Den tis 13 nov. 2018 kl 21:36 skrev Tim Jacomb : > >> CC maintainers >> >> On Tue, 13 Nov 2018 at 20:31, Tim Jacomb wrote: >> >>> Hi >>> >>> I would like to request commit access for the build failure analyzer >>> plugin >>

[Slack plugin] Request commit access

Hi I would like to request commit access for the slack plugin It has been discussed briefly here: https://github.com/jenkinsci/slack-plugin/issues/402 Github: timja Jenkins infra: timja Thanks Tim -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: [Slack plugin] Request commit access

CC maintainers On Wed, 14 Nov 2018 at 20:25, Tim Jacomb wrote: > Hi > > I would like to request commit access for the slack plugin > It has been discussed briefly here: > https://github.com/jenkinsci/slack-plugin/issues/402 > > Github: timja > Jenkins infra: timja >

[Slack plugin] Request commit access

Hi I would like to request commit access for the slack plugin It has been discussed briefly here: https://github.com/jenkinsci/slack-plugin/issues/402 Github: timja Jenkins infra: timja Thanks Tim -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: [Build failure analyzer] Request commit access

CC maintainers On Tue, 13 Nov 2018 at 20:31, Tim Jacomb wrote: > Hi > > I would like to request commit access for the build failure analyzer plugin > > I would like to clean it up and do some more development on it > > Github: timja > Jenkins infra: timja > > Than

[Build failure analyzer] Request commit access

Hi I would like to request commit access for the build failure analyzer plugin I would like to clean it up and do some more development on it Github: timja Jenkins infra: timja Thanks Tim -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: [Slack plugin] Request commit access

the plugin binary upload). > > > On Wednesday, November 28, 2018 at 9:31:01 AM UTC+11, Tim Jacomb wrote: >> >> Hi >> >> Its been about two weeks now >> As detailed here: >> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin >> >> May I please ta

Re: [Slack plugin] Request commit access

Hi Its been about two weeks now As detailed here: https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin May I please take over this plugin? I've tagged on github: On Wed, 14 Nov 2018 at 20:27, Tim Jacomb wrote: > CC maintainers > > On Wed, 14 Nov 2018 at 20:25, Tim Jacomb wrote

Re: Calling a Jenkins plugin from pipeline

You need to be in a node block for that to work node { Your step } On Fri, 8 Feb 2019 at 07:35, prasad.pofali via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hi, > > I have created a simple Jenkins plugin which prints a Hello world on > Jenkins console. This plugin is

Appending to build log after complete

Hi I'm looking at fixing JENKINS-54840 in the build-failure-analyzer plugin It has functionality where a user can force another analysis to be run on a build This gets the log file on disk, opens a PrintStream to it and appends log information

Re: Proposal - Introducing Global Probot configuration for Release Drafter and other tools

ant ADMIN role permissions to maintainers, but some > plugins indeed use admin. I prefer to focus on a more common case in the > guidelines > > BR, Oleg > > On Tue, May 28, 2019, 18:40 Tim Jacomb wrote: > >> I’m pretty sure maintainers can just add the app themselves a

Re: Proposal - Introducing Global Probot configuration for Release Drafter and other tools

I’m pretty sure maintainers can just add the app themselves as it’s approved for the org, assuming they have admin permission on the repo I didn’t need an infra ticket when I set it up on the slack plugin... Thanks Tim On Tue, 28 May 2019 at 15:02, Oleg Nenashev wrote: > I agree it makes

Re: Appending to build log after complete

Thanks Jesse I've created an Action. https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/106 Any feedback welcomed Thanks Tim On Mon, 3 Jun 2019 at 13:03, Jesse Glick wrote: > On Mon, Jun 3, 2019 at 3:51 AM Tim Jacomb wrote: > > It has functionality where a user

Re: Creating an env variable via API

What I do for this is set the SECRETS environment variably and point it to a directory on the file system which had the secrets in it. Basically pretending I’m using docker secrets Thanks Tim On Tue, 11 Jun 2019 at 10:27, Parichay Barpanda wrote: > Thanks Gaven. Groovy is cool but we are using

JEP-200? azure-vm-agents PR issue

Hi I'm having an issue adding configuration-as-code support to the azure-vm-agents plugin (On Mac, linux all tests pass, and on windows when run through intellij they also pass) On windows when run on the command line a couple of unit tests fail with: "Refusing to marshal

Re: JEP-200? azure-vm-agents PR issue

/9c94fb0dafee9e60a7424345810295a9ad4142c6 Tim On Mon, 29 Apr 2019 at 16:57, Tim Jacomb wrote: > Hi > > I'm having an issue adding configuration-as-code support to the > azure-vm-agents plugin > (On Mac, linux all tests pass, and on windows when run through intellij > they also pass) > On windows wh

Re: Budget request: Community Bridge trial run for a JCasC project

pment tools). You can find his proposal > <https://docs.google.com/document/d/1aPfkmyMQRCcipVa0htFt-i7X_pkQHSVKfR5qT60HQZ8/edit?usp=sharing> > here. > he has already done some contributions, and JCasC plugin team is ready to > mentor the student (Joseph Petersen and Tim Jacomb would

Re: Library(JollyDay)'s properties file cannot be found by WebAppClassLoader in Jenkins runtime.

This should hopefully explain it for you: https://jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/ Thanks Tim On Wed, 17 Jul 2019 at 15:32, Jack Shen wrote: > Link to the issue in Jira: > https://issues.jenkins-ci.org/browse/JENKINS-58530 > > > I'm trying to use

Re: Proposal: Jenkins Core PR reviewers team

Sounds good to me On Thu, 19 Sep 2019 at 12:26, Oleg Nenashev wrote: > Hi all, > > I would like to make a proposal w.r.t the Jenkins Core review process. > > As you may see from the pull requests > , currently we have a pretty > heavy process which

Re: Proposal: Jenkins Core PR reviewers team

I would be interested in joining this team On Thursday, 19 September 2019 12:26:46 UTC+1, Oleg Nenashev wrote: > > Hi all, > > I would like to make a proposal w.r.t the Jenkins Core review process. > > As you may see from the pull requests > ,

Re: Proposal: Moving the plugin adoption labels from Wiki to GitHub topics

+1 On Mon, 11 Nov 2019 at 14:23, Oleg Nenashev wrote: > Hi all, > > Currently the Adoption labels are on Wiki, and hence it is no longer a way > to mark plugins for adoption or unmark them for common contributors. I > suggest moving the process to GitHub and to use a more-or-less common >

Re: Next LTS baseline selection

2.205 has the password field redesign in it which would be good to get in, I’ve been bitten by that before. There’s a PR to the JCasC plugin with the suggested work around which might fix the issue (awaiting feedback before merging) Thanks Tim On Thu, 21 Nov 2019 at 07:51, ogondza wrote: > I

Re: Jenkins debug

Can’t you just use the regular jetty:run command with mvnDebug? https://github.com/jenkinsci/jenkins/blob/master/CONTRIBUTING.md#building-and-debugging On Tue, 17 Dec 2019 at 19:12, Carlos Henrique Oliveira dos Santos < chos2...@gmail.com> wrote: > I found out that jenkins-dev plugin is point

Re: Proposal: Official Docker Image maintenance team (Jenkins and Agents)

I would recommend dropping team from the name. It’s a GitHub team, the word is implied Tim On Thu, 12 Dec 2019 at 10:34, Oleg Nenashev wrote: > Thanks to all for the feedback > https://github.com/orgs/jenkinsci/teams/team-docker-packaging was created > (actually I renamed @jenkinsci/docker),

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

type of > integration between GitHub topics and the plugin site, and we can also > replace queries on the Wiki page while moving it to jenkins.io > > On Friday, October 18, 2019 at 6:52:02 PM UTC+2, Tim Jacomb wrote: >> >> Could use GitHub topics? Or just add to the readme

Re: tools.bom not working for recent LTS version of jenkins?

There’s an open pull request for the latest LTS line https://github.com/jenkinsci/bom/pull/110 I think the main reason for the delay is the trilead-api split from core has caused issues in a few plugins tests Tim On Thu, 24 Oct 2019 at 05:24, Mark Waite wrote: > > > On Wed, Oct 23, 2019 at

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

Could use GitHub topics? Or just add to the readme On Fri, 18 Oct 2019 at 15:24, Robert Sandell wrote: > And how do I mark a plugin as up for adoption without the wiki labels? > > /B > > Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick : > >> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck wrote:

Re: Proposal to switch from OpenJDK to AdoptOpenJDK

You shouldn’t need to set any flags on java 8 since u191 for enhanced container support https://medium.com/adorsys/usecontainersupport-to-the-rescue-e77d6cfea712 On Fri, 25 Oct 2019 at 19:21, Oleg Nenashev wrote: > As for your comment on OpenJ9, what did you mean by saying it will be more >>

Re: builds have stopped building with windows 8 slaves

Isn’t this the same as the previous email in this group about constant ci.jenkins.io failures? On Sat, 26 Oct 2019 at 20:07, Mike Caspar wrote: > (I changed the IP addresses to not leak out IP addresses) > > When windows 8 test machines are launched, I get this message from Blue > Ocean. >

Re: Enabling ImgBot in jenkinsci and in jenkins-infra/jenkins.io?

+1 On Mon, 7 Oct 2019 at 11:10, Raihaan Shouhell wrote: > I think its a good idea +1 > > On Monday, 7 October 2019 16:09:29 UTC+8, Oleg Nenashev wrote: >> >> Hi all, >> >> I would like to enable ImgBot in >> some of my plugins in order to optimize image

Re: Proposal teams: GitHub teams for active contributors without write permissions

What benefit does the team have? Over just adding the person to the org On Sun, 6 Oct 2019 at 01:12, Oleg Nenashev wrote: > Hi all, > > I would like to sign-off creating GitHub teams for active contributors who > do not have write access to repositories in jenkinsci and jenkins-infra >

Re: How to rename a Jenkins plugin?

Normally you would update the plugin name in the your pom.xml and do a release https://github.com/jenkinsci/ibm-asoc-plugin/blob/master/pom.xml#L4 This will update the display name but not the artifact ID, i.e. it will still show up in URLs like the plugin site Other than that I think you need

Re: 502 proxy error on ci.jenkins.io

Seems to be happening again now https://p.datadoghq.com/sb/0Igb9a-dca9738dbb5048025c005182a8f240c0 On Wed, 2 Oct 2019 at 15:14, Paul Allen wrote: > Thanks - It seems to be working now. > > > On 2 Oct 2019, at 10:24, Olblak wrote: > > > > As you can see on this status page, there is definitely

Re: Newest base pom with really old plugin

I would highly recommend just picking a version that the plugin bom supports, it makes dependency management far easier On Thu, 19 Dec 2019 at 11:33, Mark Waite wrote: > > > On Thu, Dec 19, 2019 at 2:32 AM 'Gavin Mogan' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> wrote: > >>

Re: Newest base pom with really old plugin

The minimum recommended version in the docs is 2.138.x https://jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/ On Thu, 19 Dec 2019 at 12:13, Tim Jacomb wrote: > I would highly recommend just picking a version that the plugin bom > supports, it makes dependency mana

Re: JEP-225: Folder-based access control for any credentials provider

nature of builds. > > Chris > > On 13 Feb 2020, at 06:40, Tim Jacomb wrote: > > Which bit were you unclear about? > Point 1? > > Point 1 is a request based authorisation, nothing is allowed to use it by > default, jobs request to use it and then an autrhorised person

Re: GitHub issues option in HOSTING

ector be installed on the Jira we’ve already got? > 2. If not, can anyone provide a (vague) timescale for getting things into > Jira Cloud and enabling the connector? (I appreciate this is probably a > long job.) > > Chris > > On Sat, 8 Feb 2020, at 2:14 PM, Daniel

Re: JEP-225: Folder-based access control for any credentials provider

Not directly related, possibly even to this JEP, But wanted to add a couple of features I’ve seen in other systems, 1. Require authorisation, before allowed to use, I.e build is run and fails because the credential isn’t authorised for that job but then an administrator can authorise it and it

Re: LTS baseline selection

We've been running 2.222 in production since first thing Monday, No issues so far, We enabled the global background build discarder, it ran for about 9 hours on the first run and cleared up ~200GB of space, We're very happy with the disk cleanup feature in 2.221 (thanks DB) Thanks Tim On Tue,

Re: LTS baseline selection

That looks like a fairly minor css tweak to fix that, is it just the search input? I wouldn’t exclude it from LTS for that issue On Tue, 25 Feb 2020 at 13:52, Ullrich Hafner wrote: > While I like the new look, a mix of the new UI and the existing material > theme looks kind of weird now, even

Re: LTS baseline selection

u also: > >- enable the new header UI? >- enable JEP-223? > > Thanks! > > > On Wed, Feb 26, 2020 at 11:02 AM Tim Jacomb wrote: > >> We've been running 2.222 in production since first thing Monday, >> >> No issues so far, >> >> We en

Re: Support List on jenkins.io?

ssions on the repo level is easier that wrangling with a new repo and > the delivery pipeline patches > > > On Thu, Jan 23, 2020 at 12:07 PM Tim Jacomb wrote: > >> Is there a problem with using code owners for those files? >> >> On Thu, 23 Jan 2020 at 11:05, Oleg Nena

Re: Support List on jenkins.io?

Is there a problem with using code owners for those files? On Thu, 23 Jan 2020 at 11:05, Oleg Nenashev wrote: > Hi all, > > Thanks to everyone involved in this discussion. I would also like to move > the page and to improve its look Moving the Commercial Support >

Re: Proposal: Automatically requesting code reviews from plugin developer teams (CODEOWNERS)

> are visible only to members of the organization, not the general public. I > think since it is not exposed to the general public that this should be ok? > > On Mon, Jan 13, 2020 at 6:00 AM Marky Jackson > wrote: > >> But the teams are not, and that could expose individuals witho

Re: What is the best approach for mutually exclusive permissions - re: proposed Jenkins.CONFIGURE and Jenkins.SYSTEM_READ permissions

nd a way to > provide both of these features to the user in a way that makes sense and > provides a non-confusing experience. > > thanks > -mike > > > > On Thursday, January 23, 2020 at 2:57:00 PM UTC-5, Tim Jacomb wrote: >> >> >> >> (replies inl

Re: What is the best approach for mutually exclusive permissions - re: proposed Jenkins.CONFIGURE and Jenkins.SYSTEM_READ permissions

Thank Tim On Mon, 27 Jan 2020 at 17:48, Tim Jacomb wrote: > Perfect thanks Michael > > On Mon, 27 Jan 2020 at 15:21, Michael Cirioli > wrote: > >> Tim, >> >> I've added a section to our proposed JEP-223 >> <https://github.com/jenkinsci/jep/tree/mast

JEP-13: timja youtube permissions for JCasc

Hi As a sub-project leader for JCasc I'm requesting permission to upload videos to the jenkinsci youtube channel for JCasC sub-project meetings https://github.com/jenkinsci/jep/blob/master/jep/13/README.adoc#eligibility I have a signed ICLA:

GitHub issues option in HOSTING

Hi GitHub issues use is growing in the ecosystem, many plugins are now using it, Some benefits from my experience in using it: - Easy subscription to issues / pull requests for repositories I maintain / co-maintain - Much easier to be a co-maintainer, with JIRA only the

Re: How to create a private repo under github.com/jenkinsci?

It’s not possible to have a private repo, the plan that jenkinsci is on only supports public repos On Mon, 3 Feb 2020 at 08:00, 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Why do you need it to be private? If it's for your own development, do it > in your own

Re: Adopt a plugin request

It’s you jenkins jira / artifactory account On Thu, 30 Jan 2020 at 17:41, Terry Moreland wrote: > Just getting around to this now, and want to confirm the username in the > yaml file under permissions, that should be the Jenkins-ci username or > github one? > > Just want to be clear because

Re: PROPOSAL: Remove network discovery services

+1 on removing it, is there actually going to be anyone using it who is updating their Jenkins version? I.e is a plugin needed? On Thu, 30 Jan 2020 at 19:50, Slide wrote: > I'm +1 on this, reducing the attack footprint for core is a good idea. > > On Thu, Jan 30, 2020 at 11:41 AM Jeff Thompson

Re: GitHub issues option in HOSTING

rged, and you can click on a commit to see what version it was released >in, JIRA on the other hand is very out of sync. > > > We had that in Jira as well. The service was located on Kohsuke’s server > is now not running anymore. I think it would be awesome if we could restore

Re: Wiki redirects, wiki exporter, and plugin changelogs

migrate their changelog from wiki to GitHub CHANGELOG.md file using > wiki exporter and continue to maintain the changelog manually. > > Deepest and most sincere thanks to Gavin Mogan for his excellent work on > the transition of plugin documentation from Wiki to GitHub! Thanks also to >

Re: GitHub issues option in HOSTING

(replies inline) On Sat, 8 Feb 2020 at 12:13, Daniel Beck wrote: > > On Fri, Feb 7, 2020 at 7:31 PM 'Gavin Mogan' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> wrote: > >> I also really want to see issues.jenkins go away, but mostly due to how >> slow it is. I don't think cloud is a

Re: What is the best approach for mutually exclusive permissions - re: proposed Jenkins.CONFIGURE and Jenkins.SYSTEM_READ permissions

(replies inline) On Wed, 22 Jan 2020 at 01:24, Michael Cirioli wrote: > (moving this discussion from https://github.com/jenkinsci/jep/pull/261 in > order to have more visibility) > >- Both proposals expect plugins to override getRequiredPermission() in >order to determine what should

Re: JIRA Sign Up Issues

p.s. thanks to all involved, Oleg, olblak, halkeye, tyler and daniel and anyone I missed :) On Thu, 23 Jan 2020 at 20:24, Tim Jacomb wrote: > Hi David > > That should be fixed now (I was able to create an account after deploying > the fix) > > Thanks > Tim > > O

Re: JIRA Sign Up Issues

Hi David That should be fixed now (I was able to create an account after deploying the fix) Thanks Tim On Wed, 22 Jan 2020 at 16:35, Olblak wrote: > Hi David, > > Thanks for reporting this, It seems the problem is not gone. > I give it another look > > > --- > gpg --keyserver keys.gnupg.net

Re: Any plans for the github checks API?

+1 would be great, I've done some ground laying work for it here: https://github.com/jenkinsci/github-branch-source-plugin/pull/269 It requires a github-api-plugin version to be published with a recent ish version of github-api Thanks Tim On Mon, 27 Jan 2020 at 16:09, Raihaan Shouhell wrote:

Re: Proposal: Moving the plugin adoption labels from Wiki to GitHub topics

The badge could be automatically added on the plugin site if one of the adopt topics is added to the GitHub repo? On Tue, 18 Feb 2020 at 08:01, Ivan Fernandez Calvo wrote: > Sure, the badge is something additional, > something that users can see when they go to the documentation, then they >

Re: Proposal: Jenkins Core PR reviewers team

+1 from my side On Tue, 18 Feb 2020 at 08:10, Francisco Javier Fernandez < fjfernan...@cloudbees.com> wrote: > Oleg, Marky, +1 from my side. Any help is always more than welcome! > > El domingo, 16 de febrero de 2020, 19:59:06 (UTC+1), Marky Jackson > escribió: >> >> Thank you kindly Oleg,

Re: Looking for potential weekend hackathon ideas

Might be interesting to see where you could get with the GitHub checks api? Here’s the gsoc project proposal: https://jenkins.io/projects/gsoc/2020/project-ideas/github-checks/ On Thu, 20 Feb 2020 at 17:03, Matt Sicker wrote: > Hi all, > > I'll be attending Hack Illinois [1], a weekend-long

Re: GitHub issues option in HOSTING

Who is going to update it? And what benefit does that bring? And moving to the cloud version brings less features, a new account type everyone has to sign up to, but less maintenance On Mon, 10 Feb 2020 at 10:28, Ullrich Hafner wrote: > Ok, then let us summarize the side track: > We cannot and

Re: [GSOC 2020 PROJECT IDEA] Jenkins distribution customize service

This used to be done for pipeline with the 'workflow-aggregator' plugin, afaik it's not very popular though? and isn't really being maintained anymore Any one able to provide any background? Or why this would be a good / bad idea Thanks Tim On Fri, 21 Feb 2020 at 14:50, Chris Kilding wrote: >

Re: Commit access request (File operations plugin)

Please cc him in this thread, if there’s no response we normally wait 2 weeks from cc and then grant access On Sun, 23 Feb 2020 at 18:23, Ramzi El-Yafi wrote: > Hi, > > As per the adopt a plugin guidelines, I would like to request commit > access to the file operations plugin: > > *Plugin Repo:

Re: JEP-225: Folder-based access control for any credentials provider

you clarify, maybe > with an example? > > Chris > > On 12 Feb 2020, at 18:01, Tim Jacomb wrote: > >  > > Not directly related, possibly even to this JEP, > > But wanted to add a couple of features I’ve seen in other systems, > > 1. Require authorisation, be

Re: Presenting frontend toolchain changes

Normal jira sounds fine to me, Webpack is a very standard front end tool these days On Thu, 9 Jan 2020 at 17:26, Felix Queiruga wrote: > Hi everybody, > > I have a working draft for replacing js-builder with webpack on Jenkins > core (not on plugins). The branch is a WIP, it's only missing

Re: Proposal: Automatically requesting code reviews from plugin developer teams (CODEOWNERS)

Possibly could give maintainers team maintainer permission to help with that if the person they want to add is a member of the org On Mon, 13 Jan 2020 at 13:37, Daniel Beck wrote: > How do you plan to address issues in plugins whose maintainers are largely > (or even completely) managed outside

Re: Proposal: Automatically requesting code reviews from plugin developer teams (CODEOWNERS)

The list of maintainers is already public in the repository permissions list, +1 for changing this I assume the API call needs to be updated slightly in the IRC bot Thanks Tim On Mon, 13 Jan 2020 at 12:46, Marky Jackson wrote: > Oleg, > I feel that need some form of consent from maintainers.

Re: Plugin host

https://jenkins.io/doc/developer/publishing/requesting-hosting/ On Thu, 26 Dec 2019 at 16:46, selva vignesh wrote: > Hello Team, > Currently, I am looking for a guide to host my plugin in Jenkins side. > Kindly assite me. > Thanks in advance > > -- > You received this message because you are

Re: Plugin host

osting plugin? > > On Thu, Dec 26, 2019 at 2:10 PM Tim Jacomb wrote: > >> https://jenkins.io/doc/developer/publishing/requesting-hosting/ >> >> >> On Thu, 26 Dec 2019 at 16:46, selva vignesh >> wrote: >> >>> Hello Team, >>> Currently, I

Re: Uninstall plugin

Docs for that are here: https://wiki.jenkins.io/plugins/servlet/mobile?contentId=65142785#content/view/65142785 Possibly documented on Jenkins.io as well but didn’t come up when I googled it... On Fri, 27 Dec 2019 at 21:07, selva vignesh wrote: > Team, > In global Configuration I'm saving

Re: Happy Holiday

Personally I’ve never found the invite system in slack very difficult, (not as simple as straight GitHub integration :( ) but you just deploy an app like https://github.com/outsideris/slack-invite-automation/blob/master/README.md, add a badge to your readme and then people self service sign

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

do you mean #jenkins on irc or gitter http://gitter.im/jenkinsci/jenkins ? gitter jenkins is are very heavy user channel irc jenkins isn't so bad but still lots of people after pipeline help. On the kubernetes slack there's a few, -users and -dev channels Which helps separate out the noise in

Re: Proposal: Windows support policy for Jenkins

Sounds reasonable to me +1, I speak as someone who barely ever touches Windows and never for Jenkins though Thanks Tim On Friday, 10 April 2020 13:26:51 UTC+1, Oleg Nenashev wrote: > > Dear all, > > As you probably know, Jenkins core and some plugins contain native code, > and hence they rely

Re: [Proposal] Centralize chat on matrix

Hi I've just had a try of matrix using riot.im The UI looks nice and it's easier the core matrix.org server than IRC Few negatives I found though: * Bridging to IRC on freenode required some googling as you get insta kicked out as you haven't identified to nickserv, needed to google around to

Re: [Proposal] Centralize chat on matrix

> > > if we were to use this is there a reason not to use the SaaS version > (other than LDAP auth)? > > I think if we did modular.im, we could still use ldap, and they might be > have open source pricing. I think its something that cdf might be > interested in. > > I just don't like slack

Re: How to perform a plugin release to Jenkins Artifact Repository through Continuous Integration?

There's a proposal for automating plugin release here: https://jenkins.io/jep/221 Not sure what's needed to get it going though, would be great to get done Thanks Tim On Fri, 10 Apr 2020 at 16:46, Slide wrote: > Yes, all releases are done manually. There are some ideas floating around > to do

Re: Configuration Slicing plugin adoption

Normally you use the Jenkins bom https://github.com/jenkinsci/bom Which includes the common plugins that are depended on, it saves a lot of time when updating versions. Thanks Tim On Mon, 13 Apr 2020 at 12:44, Guy Sheffer wrote: > Thanks Oleg, > To anyone that could help, > I have got as far

New bom lines released

Hi Just a note to say we've recently shipped the following bom lines: - 2.190.x - 2.204.x - 2.222.x We are no longer shipping updates for 2.150.x Usage guide: https://github.com/jenkinsci/bom#usage Releases: https://github.com/jenkinsci/bom/releases Thanks Tim -- You received this

Re: plugin parent 4.0

gt; wrote: >> >>> +1 >>> >>> I don't remember if I've pushed any commits that use the beta parent, >>> but I've tried it out on a variety of different plugins I've investigated. >>> I've found it to work better than any of the other earlie

Re: plugin parent 4.0

Hi plugin pom 4 is now released, Full release notes including all beta versions: https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.0 Thanks Tim On Wed, 15 Apr 2020 at 19:52, Tim Jacomb wrote: > This seems not to have happened, I'm happy to do it Oleg if you're too >

Re: Jenkins Plugin Wiki

Possibly that could have an impact I’m hoping to look at this soon On Tue, 7 Apr 2020 at 18:30, Mark Waite wrote: > Interesting. I see the same outdated page that you show in your > screenshot. > > The ci.jenkins.io build queue is quite long right now. The acceptance > test harness is

Re: ANN: Agent Docker images renaming on April 12-13

+1 to inbound agent rename What about just ssh-agent for the ssh one? We don’t need to worry about the plugin name clash here I think Thanks Tim On Sun, 12 Apr 2020 at 09:36, 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > sshd-agent? > > On Sun, Apr 12, 2020 at

Re: Configuration Slicing plugin adoption

more experience than me could take a look > its likely something simple I overlooked. > > Thanks for helping out, > Guy > > On Monday, April 13, 2020 at 3:29:20 PM UTC+3, Tim Jacomb wrote: >> >> Normally you use the Jenkins bom >> https://github.com/jenkinsci/bom &g

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

Also this for moderation on slack: https://github.com/foqal/slack-moderator/blob/master/README.md On Thu, 9 Apr 2020 at 12:51, Tim Jacomb wrote: > There’s this project for a public archive of slack: > https://github.com/dutchcoders/slackarchive > > We would need the equivalent for

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

There’s this project for a public archive of slack: https://github.com/dutchcoders/slackarchive We would need the equivalent for IRC as well I think. With IRC currently there’s no public log of any of the Jenkins channels. Each person needs to log it then self or pay / run a service that will do

Re: Maintainer of copy-editors group on GitHub?

+1 You should have it due to your role as documentation officer imo On Fri, 17 Apr 2020 at 15:10, Mark Waite wrote: > I'd like to be assigned as a maintainer of the copy-editors team on the > Jenkins CI GitHub account. > > Are there specific steps that I should take to be granted maintainer >

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

I think a core-dev chat room would be useful, I don’t think it needs limiting to just be core-developers though Anything related to development on the core would be welcomed there Thanks Tim On Wed, 8 Apr 2020 at 13:17, Oleg Nenashev wrote: > Hi all, > > In the Proposal: Expanding the

Re: Git plugin 5.0 require Jenkins 2.190.3

You aren’t breaking anything so I don’t know why you would need to break it. On Thu, 26 Mar 2020 at 21:29, Mark Waite wrote: > > On Thu, Mar 26, 2020 at 3:17 PM Jesse Glick wrote: > >> On Thu, Mar 26, 2020 at 10:47 AM Mark Waite >> wrote: >> > No breaking changes in API's in the transition

Re: GitHub issues option in HOSTING

That's cool Radek, was this what you used to migrate them? https://github.com/parcelLab/jira-to-github Or something else? On Wed, 25 Mar 2020 at 16:27, Radek Antoniuk wrote: > I would like to vote +1 for GitHub Issues. > > I tried migration via the API for jira plugin and the only thing that

Re: plugin patent 4.0

I've been using it on a few plugins, no issues On Thu, 26 Mar 2020 at 09:11, James Nord wrote: > Hi Oleg et al. > > is it time to move the plugin parent out of beta? > > have not seen any negative feedback (or positive door that matter) but > I've been using it for numerous proprietary plugins

Re: plugin parent 4.0

2.164.x is fine, the bom sample plugin is using it on this version On Thu, 23 Apr 2020 at 08:53, Ullrich Hafner wrote: > > > Am 23.04.2020 um 01:06 schrieb 'Gavin Mogan' via Jenkins Developers < > jenkinsci-dev@googlegroups.com>: > > I'll update to 2.164, or tell dependabot to ignore this dep.

Re: Plugin: Liquibase Runner

Has Keith approved this somewhere? Here or in GitHub? On Thu, 23 Apr 2020 at 15:28, Robert Reeves wrote: > Just wanted to check on the adoption status. We have a PR submitted that > resolves the security issue. We'd like to be able to push to master and do > a release. Thanks! > > -- > You

Re: LTS baseline selection for the successor of 2.222

2.235 would also be my preference, I've got 2 (hopefully) last system read PRs, I would love to get in before the LTS On Wed, 29 Apr 2020 at 14:54, Daniel Beck wrote: > > > > On 29. Apr 2020, at 12:44, Oliver Gondža wrote: > > > > In accordance we recently approved process changes, we are

Re: Plugin: Liquibase Runner

I would check you deploy credentials in your settings.xml as a first step, it should be fairly quick to give you permission unless the job is broken On Fri, 1 May 2020 at 14:15, Robert Reeves wrote: > Hi, Team! > > > > Thanks for accepting the PR to give my GitHub/Artifactory user access to >

Re: Welcome GSoC 2020 students and mentors!

> In addition to the newcomer students, we will have a number of experienced > and newcomer contributors who will be mentoring Jenkins projects: Kristin > Whetstone, Jeff Pearce, Xiaojie Zhao, Andrey Falko, Oleg Nenashev, Michael > Cirioli, Mark Waite, Francisco Fernandez, Parichay Bar

Re: Governance and Jenkins is the Way on Jumbotron

+1 On Tue, 5 May 2020 at 02:07, Mark Waite wrote: > The "Jenkins is the Way > " blog post > invites users to share their Jenkins stories. I would like to see us > highlight the collection and highlighting of Jenkins experiences even

Re: Next Jenkins weekly

Couldn’t multiple instances run it? It makes sense to me that release runs the the tests on the artifacts, And also makes sense that ci.jenkins.io has tests that it’s working (possibly it could have simpler tests and doesn’t need to run the full acceptance tests set) Thanks Tim On Fri, 24 Apr

Re: Proposal: Making the Hosting team official (and onboarding new members)

ocument its roles somewhere on >>jenkins.io. Scope: plugin and component hosting on Jenkins resources >>(GitHub, Update Centers, etc.) >>- Grant permissions to active contributors who are interested and who >>already have experience with the hosting process (e.g.

Re: Proposal: Making the Hosting team official (and onboarding new members)

would propose to create an official team and to >>> introduce an onboarding process: >>> >>> Proposal >>> >>>- Make the "Hosting Team" official, document its roles somewhere on >>>jenkins.io. Scope: plugin and component hosti

  1   2   3   4   5   6   >