Re: Jenkins Common Coding Questions in GSoC 2019

Current failure in that PR is a compile error, not enforcer related. Also, update to latest parent pom to use latest enforcer plugin already. Le mar. 4 juin 2019 à 07:39, Yufei Zhang a écrit : > Hi, this is the related PR : >

Re: Jenkins Common Coding Questions in GSoC 2019

Hi, this is the related PR : https://github.com/jenkinsci/external-workspace-manager-plugin/pull/62 The java version should be : [INFO] Maven Version: 3.6.0 [INFO] JDK Version: 1.8.0_212 normalized as: 1.8.0-212 [INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 4.15.0-50-generic

Re: Jenkins Common Coding Questions in GSoC 2019

Can you push a PR somewhere that shows the failure? Can you run with mvn -V compile and show the first lines (i.e. the JDK and maven versions in use). Also I'd recommend bumping to the latest parent pom (3.43 to date) Le mar. 4 juin 2019 à 06:53, Yufei Zhang a écrit : > QUESTION 6 : This is a

Re: Jenkins Common Coding Questions in GSoC 2019

> > QUESTION 6 : This is a AWS Java SDK related problem and I think it has > something to do with the pom.xml > When I run *mvn compile*, it has error like this : Execution display-info of goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.: NullPointerException Part

Re: RunWithSCM

On Mon, Jun 3, 2019 at 6:25 PM 'Gavin Mogan' via Jenkins Developers wrote: > For example. FreeStyleProject/AbstractProject has getAllActions() exported as > Actions, which I've gotten working in graphql, but I lose the ability to have > per instance exports. > > Since action is not an extension

Re: RunWithSCM

> `@ExportedBean` you mean? Or `@Exported`? These annotations cannot be used on interfaces or interface methods. Well that explains that and certain other related questions I'm now handling interfaces specifically in a different way (Making a fake graphql "type" that implements the interface as

[EVENTS]: DevOps World Jenkins - World Lisbon CFP closing June 9, 2019

Hi All, Friendly reminder the CFP for Lisbon will be closing this Sunday, June 9 at 11:59pm PT https://www.cvent.com/c/abstracts/6eb10034-9500-43a1-97cd-ab4d9230d7f9 If you're attending , the Jenkins community has a discount code *JWFOSS* for 30%

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

+1 from me obviously. Anyone actually needed old *dev* tooling can use current tags/releases, though I believe nobody really does need this. Le lun. 3 juin 2019 à 15:27, Oleg Nenashev a écrit : > Hi all, > > Java 7 has not been supported in Jenkins LTS since 2.60.1, which was > released almost

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

+1 from me. Not a big fan of holding on to support for super old things. On Mon, Jun 3, 2019 at 9:10 AM Robert Sandell wrote: > +1 > I thought we already had dropped Java 7 support in the tooling :/ > > /B > > Den mån 3 juni 2019 kl 15:58 skrev Mark Waite : > >> >> >> On Mon, Jun 3, 2019 at

Re: Maintenance Window - ci.jenkins.io - 2019/03/06 - 9AM UTC+2

Congrats to all involved!! On Mon, Jun 3, 2019 at 9:55 AM Mark Waite wrote: > > > On Mon, Jun 3, 2019 at 7:30 AM Oleg Nenashev > wrote: > >> Thanks to everybody who contributed to this migration! >> > > Hearty congratulations! That's a great achievement. > > >> Adoption of Java 11 should give

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

+1 I thought we already had dropped Java 7 support in the tooling :/ /B Den mån 3 juni 2019 kl 15:58 skrev Mark Waite : > > > On Mon, Jun 3, 2019 at 7:38 AM Jesse Glick wrote: > >> On Mon, Jun 3, 2019 at 9:27 AM Oleg Nenashev >> wrote: >> > a green light to whomever wants to drop old Java

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

On Mon, Jun 3, 2019 at 7:38 AM Jesse Glick wrote: > On Mon, Jun 3, 2019 at 9:27 AM Oleg Nenashev > wrote: > > a green light to whomever wants to drop old Java version support from > Dev tools > > +1. I see no reason to waste core dev time handling obsolete > platforms. If some plugin maintainer

Re: hashicorp vault plugin new release

Added Peter Tierno (current maintainer) to Cc On Mon, Jun 3, 2019 at 3:55 PM Oleg Nenashev wrote: > last update was on Feb 16, so IMHO there is a chance it is still maintained > > On Monday, June 3, 2019 at 3:30:23 PM UTC+2, Damien Coraboeuf wrote: >> >> Hi, >> >> The current version of the

Re: hashicorp vault plugin new release

last update was on Feb 16, so IMHO there is a chance it is still maintained On Monday, June 3, 2019 at 3:30:23 PM UTC+2, Damien Coraboeuf wrote: > > Hi, > > The current version of the hashicorp vault plugin 2.2.0 ( > https://github.com/jenkinsci/hashicorp-vault-plugin) and the associated >

Re: Maintenance Window - ci.jenkins.io - 2019/03/06 - 9AM UTC+2

On Mon, Jun 3, 2019 at 7:30 AM Oleg Nenashev wrote: > Thanks to everybody who contributed to this migration! > Hearty congratulations! That's a great achievement. > Adoption of Java 11 should give us some gradual improvements in the > infrastructure, especially for Docker-based flows. > > I

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

On Mon, Jun 3, 2019 at 9:27 AM Oleg Nenashev wrote: > a green light to whomever wants to drop old Java version support from Dev > tools +1. I see no reason to waste core dev time handling obsolete platforms. If some plugin maintainer insists on providing support for very old core lines for

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

Sounds OK to me. On Monday, June 3, 2019 at 2:27:47 PM UTC+1, Oleg Nenashev wrote: > > Hi all, > > Java 7 has not been supported in Jenkins LTS since 2.60.1, which was > released almost 2 years ago (June 27, 2017). Over past two years, a > majority of plugins updated their requirements to

Re: Maintenance Window - ci.jenkins.io - 2019/03/06 - 9AM UTC+2

Thanks to everybody who contributed to this migration! Adoption of Java 11 should give us some gradual improvements in the infrastructure, especially for Docker-based flows. I also wonder about using Zulu for Windows agents. Should not we move to AdoptOpenJDK as it was discussed in

hashicorp vault plugin new release

Hi, The current version of the hashicorp vault plugin 2.2.0 (https://github.com/jenkinsci/hashicorp-vault-plugin) and the associated pipeline plugin 1.2 (https://github.com/jenkinsci/hashicorp-vault-pipeline-plugin) do not seem to support the Hashicorp Vault V2 API. However, the code on the

Proposal - Phasing out Java 7 support in Jenkins Dev tools

Hi all, Java 7 has not been supported in Jenkins LTS since 2.60.1, which was released almost 2 years ago (June 27, 2017). Over past two years, a majority of plugins updated their requirements to 2.60.3 and above, and there are only few exceptions in top-50 plugins (Mailer, Git Client, Git Server,

Re: Facing Error in loading Build Action page

On Thu, May 30, 2019 at 7:52 AM selva vignesh wrote: > No page found 'sidepanel.jelly' for class > io.jenkins.plugins.sample.BuildAction Exception. > > What is `it` in this case? What type does the `getBuild()` method return? Not sure where you are copying this example from exactly,

Re: Appending to build log after complete

On Mon, Jun 3, 2019 at 3:51 AM Tim Jacomb wrote: > 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 to it about the scan result Should be rewritten to do something else,

Re: Jenkins Common Coding Questions in GSoC 2019

On Sun, Jun 2, 2019 at 2:39 AM Joseph P wrote: > Q5: I'd recommend using optionalProperty over optionalBlock Yes. See `ui-samples-plugin` for an example of usage. Essentially, you can define a `@CheckForNull` field of some `Describable` type. The `config.jelly` of that type will appear when the

Re: Jenkins Common Coding Questions in GSoC 2019

On Sat, Jun 1, 2019 at 9:00 PM Yufei Zhang wrote: > For Q4, we can use a Boolean fields `boolean` not `Boolean`. -- 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 Common Coding Questions in GSoC 2019

On Wed, May 22, 2019 at 10:41 AM Matt Sicker wrote: > For Q1, I'm not sure how data bound constructor works with inherited > classes. Only a concrete class may use `@DataBoundConstructor`. It should be a compile-time error to apply it to an `abstract` class. (If it is not, fix the annotation

Re: Maintenance Window - ci.jenkins.io - 2019/03/06 - 9AM UTC+2

Thank you Olivier. A side note on the report of issues: please make sure to use the label `java11` so it can popup in different filters. BR, -- Adrien Le lun. 3 juin 2019 à 11:38, Olblak a écrit : > Hi Everybody, > > I am happy to announce that ci.jenkins.io is now running on Java 11. > >

Re: Maintenance Window - ci.jenkins.io - 2019/03/06 - 9AM UTC+2

Hi Everybody, I am happy to announce that ci.jenkins.io is now running on Java 11. Thanks Adrien Lecharpentier and Baptiste Mathus for their help during the migration and more globally thanks to all the people involved in the platform-sig for their work on

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

Coding Questions: (GSoC) Artifact Promotion Plugin for Pipeline

Hi all! I am currently working on detaching the required modules/extensions from the promoted-builds-plugin for a new plugin as proposed. However, I have the following questions: 1) I assume that the entire promotion process starts from *PromotionCondition* abstract class and the flow goes like:

Coding Questions: (GSoC) Artifact Promotion Plugin For Pipelines.

Hello All! I am currently working on detaching required modules/extensions from the promoted-builds for the new plugin as proposed. However, I have the following questions: 1) I assume that the promotion process gets injected from PromotionCondition and the flow goes like: