Re: Jenkins Common Coding Questions in GSoC 2019

Hi Yufei, I am running on commit 19164b7 with these versions: ~/Downloads/apache-maven-3.6.0/bin/mvn compile [INFO] Scanning for projects... [INFO] [INFO] -< org.jenkins-ci.plugins:external-workspace-manager >-- [INFO] Building External Workspace Manager Plugin 1.1.3-SNAPSHOT

Re: Proposal - Phasing out Java 7 support in Jenkins Dev tools

taking the consensus here, I will proceed with creating tickets and pull requests for the components mentioned in the original proposal (actually, just few of them like Plugin POM) On Monday, June 3, 2019 at 6:23:39 PM UTC+2, Baptiste Mathus wrote: > > +1 from me obviously. Anyone actually

Re: Proposal - Adding JCasC tests into Jenkins core test suite

If it makes sense to use the plugin-compat-test, we should go with this. I wasn't aware of its existence. On Tue, 4 Jun 2019, 22.18 Slide, wrote: > I agree with Jesse. The suite as is is so large already. The > plugin-compat-test was made for purposes similar to this I believe, so why > not use

Accessing PR head commit sha from a pipeline using branch source plugin

Hi, We are trying to simplify integration of SonarQube with most popular pull request provider, like GitHub or Bitbucket. Those ALM usually provide some API to report issues on PR (GitHub checks, Bitbucket Code Insight, ...). The APIs require to pass the PR HEAD commit sha1. We are trying to get

Re: Proposal - Adding JCasC tests into Jenkins core test suite

I agree with Jesse. The suite as is is so large already. The plugin-compat-test was made for purposes similar to this I believe, so why not use the tools that are available? On Tue, Jun 4, 2019 at 11:29 AM Jesse Glick wrote: > On Tue, Jun 4, 2019 at 1:23 PM Joseph P wrote: > > we would avoid

Re: Proposal - Adding JCasC tests into Jenkins core test suite

On Tue, Jun 4, 2019 at 1:23 PM Joseph P wrote: > we would avoid regressions that are related to configuration-as-code I think that should be handled differently, for example by something like JENKINS-45047, or `plugin-compat-tester`, or `buildPlugin.recommendedConfigurations()`, or Dependabot.

Re: Proposal - Adding JCasC tests into Jenkins core test suite

Sounds like a great idea to me. My 2-cents Jon -- 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

Proposal - Adding JCasC tests into Jenkins core test suite

Hi All In an effort to improve JCasC compatibility we would like to add the configuration-as-code-plugin into the Jenkins core test suite This will help us improve

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

Hi all, Just heads-up, 2.176.1 release will be delayed due to to some infrastructure issues. Kohsuke is traveling now, and the ETA for the release is Sunday, Jun 09. This is a temporary release infrastructure until the Core release Automation project is completed (see this thread

Re: Benchmarking Jenkins using Java Microbenchmark Harness (JMH)

Hi all, You can find the video recording of the demo here: https://www.youtube.com/watch?v=sr28UADG1AE There is also an ongoing pull request to make it a part of Jenkins Test Harness: https://github.com/jenkinsci/jenkins-test-harness/pull/135 Best regards, Oleg On Thursday, May 30, 2019 at

Re: Jenkins Common Coding Questions in GSoC 2019

Sorry I didn't make it clear, I want to fix this problem in my local environment, and this error has been up for a couple of times, I tried to figure out what is wrong but couldn't get a clue. I updated to 3.43 (latest) parent pom, and still couldn't find out which rule was broke. Not sure if