Re: Release not showing up

Hello, i'm experiencing the same problem. I released a new version of the Performance-Signature-* plugins but it still hasn't shown up on the update center. The release is available via repo.jenkins-ci.org:

Release not showing up

Hello, I released a new version of the OWASP Dependency-Track plugin yesterday, but it still hasn’t shown up on the update site. The version in question is 2.1.0. https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/dependency-track/2.1.0/

Re: jenkins official kubernetes operator

> > Making backup of ~50GB is not good idea. I don't want to make snowflake. > When new Jenkins master comes up it should starts with empty > `$JENKINS_HOME` and jenkins-operator have to configure it to desire state. > Backup is triggered before Jenkins master pod deletion and it have to be >

Request for co-maintainership of Timestamper plugin

As per https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess I would like to be permitted to perform releases of the Timestamper plugin, at a minimum to release the critical https://github.com/jenkinsci/timestamper-plugin/pull/25 and any follow-on changes that

Re: jenkins official kubernetes operator

On Thu, Jan 24, 2019 at 11:32 AM Tomasz Sęk wrote: >>> make backup of jobs history before Jenkins master pod deletion and restore >>> it in new pod > >> You do not just set a custom build record directory […] and use a persistent >> volume claim? […] >> Beware however that there is some more

Re: [plugin adoption]: Google Cloud Storage

Also created an issue in the repo: https://github.com/jenkinsci/google-storage-plugin/issues/50 On Thursday, January 24, 2019 at 10:34:10 AM UTC-8, Craig Barber wrote: > > Created an issue against the project to track the transfer: > https://issues.jenkins-ci.org/browse/JENKINS-55767 > > On

Request maintainer/co-maintainer for vstestrunner-plugin

Hi This is my official request for maintainership of vstestrunner-plugin @Erik Goughnour You never got the chance to look at the PRs after previous attempts at getting the open PRs merged. Best regards Joseph Petersen -- Forwarded message - From: Joseph P Date: Wed, Jul 25,

Re: Plugin Adoption: Google OAuth Plugin

I have now commented indicating approval of this request: https://github.com/jenkinsci/google-oauth-plugin/issues/27, https://issues.jenkins-ci.org/browse/JENKINS-55766. Thank you! On Wed, Jan 23, 2019 at 2:41 PM Craig Barber wrote: > The GCP Cloud Graphite: Platforms team would like to adopt

Re: [plugin adoption]: Google Cloud Storage

I've agreed to the transfer; I've made a Github issue if you need confirmation from my Github account: https://github.com/jenkinsci/google-storage-plugin/issues/49 On Thursday, January 24, 2019 at 12:40:10 PM UTC-5, Craig Barber wrote: > > The Cloud Graphite: Platforms team would like to adopt

Re: [plugin adoption]: Google Cloud Storage

Created an issue against the project to track the transfer: https://issues.jenkins-ci.org/browse/JENKINS-55767 On Thursday, January 24, 2019 at 9:40:10 AM UTC-8, Craig Barber wrote: > > The Cloud Graphite: Platforms team would like to adopt the GCS plugin. > > github repo:

Re: Plugin Adoption: Google OAuth Plugin

Created an issue against the component to track the transfer: https://issues.jenkins-ci.org/browse/JENKINS-55766 On Thursday, January 24, 2019 at 9:45:54 AM UTC-8, Craig Barber wrote: > > Forwarded to astroilov@ > Thanks! > > On Thursday, January 24, 2019 at 2:07:23 AM UTC-8, Baptiste Mathus

Re: Plugin Adoption: Google OAuth Plugin

Forwarded to astroilov@ Thanks! On Thursday, January 24, 2019 at 2:07:23 AM UTC-8, Baptiste Mathus wrote: > > Hello, > The usual timeout for this kind of request is 15 days. > Please have the current maintainer comment somewhere so we can see she or > he is OK with this request. > > AFAICT, it

Re: A new home for Jenkins

Thanks everyone who came to the Q The slides are available here & the recording is available here. If you are coming to FOSDEM, be sure to let us

[plugin adoption]: Google Cloud Storage

The Cloud Graphite: Platforms team would like to adopt the GCS plugin. github repo: https://github.com/jenkinsci/google-storage-plugin github username: https://github.com/craigatgoogle -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: jenkins official kubernetes operator

> > > > I forgot to mention that plugins are separated in two groups: required by > jenkins-operator(used to configure Jenkins)(A) and required by user(B). > A: > - they are installed by jenkins-operator before Jenkins can start up > - every single change requires restart of Jenkins master

Re: jenkins official kubernetes operator

On Wednesday, 23 January 2019 16:06:03 UTC+1, Jesse Glick wrote: > It sounds nice (I have not tried it). Some technical questions / comments: > make backup of jobs history before Jenkins master pod deletion and restore it in new pod > You do not just set a custom build record directory (IIRC

Re: Adopt instant-messaging-plugin

Assisting others: https://github.com/jenkinsci/instant-messaging-plugin/pulls On Thursday, January 24, 2019 at 5:14:51 PM UTC+1, Joseph P wrote: > > Please share link to code review  > > On Thursday, January 24, 2019 at 4:10:31 PM UTC+1, Jim Klimov wrote: >> >> Hello all, >> >> I am making

Re: Adopt instant-messaging-plugin

Please share link to code review  On Thursday, January 24, 2019 at 4:10:31 PM UTC+1, Jim Klimov wrote: > > Hello all, > > I am making some improvements to our Jenkins master interaction over > internal IRC, and it seems that the IM plugin which does the actual work is > not quite often

Adopt instant-messaging-plugin

Hello all, I am making some improvements to our Jenkins master interaction over internal IRC, and it seems that the IM plugin which does the actual work is not quite often updated (last release in 2015). I would like to bump its priority in the eyes of current maintainer (CCed) and/or ask

Re: [pipeline-github-plugin] - Trying to reach maintainer - https://github.com/aaronjwhiteside

hmm.. I didn't look at the master commits recently. Thank you. Let me log a new issue, looks like he is not following the comments on that closed PR. Thanks again. On Thursday, January 24, 2019 at 4:04:20 AM UTC-6, Baptiste Mathus wrote: > > There's no real process when a plugin is not

Re: Plugin Adoption: Google OAuth Plugin

Hello, The usual timeout for this kind of request is 15 days. Please have the current maintainer comment somewhere so we can see she or he is OK with this request. AFAICT, it would be from https://github.com/astroilov. Ideally, just have her or him comment in GitHub somewhere confirming, so we

Re: [pipeline-github-plugin] - Trying to reach maintainer - https://github.com/aaronjwhiteside

There's no real process when a plugin is not abandoned. https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin would be what to use, but here given the maintainer updated the plugin again 3 days ago, this does not look like abandoned. Added the maintainer in CC. Thanks Le mer. 23 janv. 2019 à

Fwd: Plugin Adoption: Google OAuth Plugin

-- Forwarded message - From: Craig Barber Date: Wed, Jan 23, 2019 at 2:41 PM Subject: Plugin Adoption: Google OAuth Plugin To: , Andrey Stroilov , Don McCasland , Vic Iglesias , Evan Brown The GCP Cloud Graphite: Platforms team would like to adopt the Google OAuth Plugin so