Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

I raised a ticket here - https://issues.jenkins-ci.org/browse/INFRA-2183. Please let me know if I can assign it to someone or you can ping someone who can help fix it. Thanks in advance. On Wednesday, July 17, 2019 at 12:26:46 AM UTC+5:30, Jesse Glick wrote: > > On Tue, Jul 16, 2019 at 2:47 PM

Re: Keep Build Forever interface listing disappears with plugin on legacy Jenkins

On Tue, Jul 16, 2019 at 4:53 PM 'Benjamin Beggs' via Jenkins Developers wrote: > In modern Jenkins (at least 2.7.3 and up, though I expect this is true for > many earlier versions as well) this Strategy can be selected and builds will > continue to show their "Keep Build Forever" option.

Keep Build Forever interface listing disappears with plugin on legacy Jenkins

I'm developing an update to the enhanced-old-build-discarder-plugin which adds a dropdown listing in the *Discard old builds* setting *Strategy *called Enhanced Log Rotator allowing for some additional conditional specifications with build discards. In modern Jenkins (at least 2.7.3 and up,

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

On Tue, Jul 16, 2019 at 2:47 PM Parichay Barpanda wrote: > Invalid archive retrieved from Jenkins, perhaps the plugin is not properly > incrementalized? Well Tyler added this particular error message, perhaps related to INFRA-2125:

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

By specifying the binary files in .gitattributes the build passed but the plugin is not deployed incrementally. The deploy stage fails with a message: Invalid archive retrieved from Jenkins, perhaps the plugin is not properly incrementalized? The build result for the latest commit can be found

Maintainer for webhook-step-plugin

I wanted to propose myself being added as a maintainer to the webhook-step-plugin. There are some PR's that would be good to merge that have been around for some time. I am using this plugin at work and would like to get those PR's merged into a formal release (I am using a self-built version

Re: m2Release attn Dominik Bartholdi

Hey James, No, I I’m not using - its years since the last time I did... So yes, please feel free to put it up for adoption. /Domi > On 16 Jul 2019, at 15:19, James Nord wrote: > > Hi Dominik, > > I have not used the m2release plugin for over 4 years now and have not been > actively

m2Release attn Dominik Bartholdi

Hi Dominik, I have not used the m2release plugin for over 4 years now and have not been actively maintaining it. I don't know if you are still using the plugin interested or otherwise interested in keeping things moving. If you're not interested I'll put the plugin up for adoption. Regards

Re: Proposal: Adding support resources to jenkinsci GitHiub and jenkins.io

> > support.jenkins.io > > is > the logical place I would look up for support but that site doesn’t exist > (yet). > I would rather think about jenkins.io/support so that we do not need to

Re: Proposal: Adding support resources to jenkinsci GitHiub and jenkins.io

Just one thought only partially related to your proposal is that on the Commercial Support page, should there be some kind of disclaimer stating that being listed there in no way is to be viewed as endorsement by the Jenkins project? (Perhaps that's just something to roll into a migration into a

Proposal: Adding support resources to jenkinsci GitHiub and jenkins.io

support.jenkins.io is the logical place I would look up for support but that site doesn’t exist (yet). -- 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

Proposal: Adding support resources to jenkinsci GitHiub and jenkins.io

Hi all, After getting initial feedback in https://github.com/jenkinsci/.github/pull/14, I would like to follow-up in the developer mailing list to have a wider discussion. *Problem*: we receive a lot of support requests in GitHub issues and Jenkins JIRA, but we do not provide support in common

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

Awesome Gavin. It was .gitattributes that caused the binary files to change. Thanks. On Tue, Jul 16, 2019 at 3:47 PM Gavin wrote: > Oh shot in the dark here. > > > https://github.com/jenkinsci/gitlab-branch-source-plugin/blob/develop/.gitattributes > is set to change the endings of all files.

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

Oh shot in the dark here. https://github.com/jenkinsci/gitlab-branch-source-plugin/blob/develop/.gitattributes is set to change the endings of all files. That could potentially mess with binary files. I'm not certain about this but you might need to say your images are binary. Especially if your

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

Hi Gavin, I'm trying to fix it in https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/1. I tried to see git status after `mvn clean install`, it says tree is clean and build still fails. On Tue 16 Jul, 2019, 15:38 Gavin, wrote: > Whats the deploy stage? In the jenkins pipeline? In

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

Whats the deploy stage? In the jenkins pipeline? In maven? Have you tried a clean clone of your develop branch. Running mvn clean install, then checking git status to see what if anything is generated. Develop seems to be running properly.

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

Hi Jesse, I had added the webapp directory to .gitignore to test the build. Now I tried to remove classes that might have affected the images such as GitLabAvatarCache (didn't work), refixed svgs and the pngs (didn't work). The current work can be found in this commit -