Re: Jenkins Common Coding Questions in GSoC 2019

[Baptiste Mathus]

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 :
> 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
>
> When I delete the related pom entry for AWS java SDK, it will goes to the
> compile phase, but with the AWS Java pom entry, it fails at enforce.
>
> 在 2019年6月3日星期一 UTC-7下午10:09:45，Baptiste Mathus写道：
>>
>> 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 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 of my pom.xml look like this
>>>
>>> 
>>> org.jenkins-ci.plugins
>>> plugin
>>> 3.18
>>> 
>>>
>>> external-workspace-manager
>>> 1.1.3-SNAPSHOT
>>> hpi
>>>
>>> 
>>> 2.60.3
>>> 8
>>>
>>> -Xmx1024m
>>>
>>> 
>>>
>>>
>>> and the AWS Java SDK property was copied from ec2-plugin pom.xml.
>>> it looks like
>>>
>>> 
>>> org.jenkins-ci.plugins
>>> aws-java-sdk
>>> 1.11.457
>>> 
>>>
>>>
>>> And the pom.xml in ec2-plugin looks like
>>>
>>> 
>>> org.jenkins-ci.plugins
>>> plugin
>>> 3.25
>>> 
>>>
>>>
>>> I tried upgrade my plugin version to 3.25, but didn't work, does anyone
>>> know what's the potential problem ? Thanks !
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> 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 jenkin...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/2ab86fec-880c-4470-9604-e14d7df64e22%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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 discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/bfc0a42c-dacf-49bb-91d9-9704d159de46%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4XWRAxA17B4YHejgPPLaCXfB-%2BhdeqTVN-bOny1fWe%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Common Coding Questions in GSoC 2019

[Yufei Zhang]

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

When I delete the related pom entry for AWS java SDK, it will goes to the 
compile phase, but with the AWS Java pom entry, it fails at enforce.

在 2019年6月3日星期一 UTC-7下午10:09:45，Baptiste Mathus写道：
>
> 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 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 of my pom.xml look like this
>>
>> 
>> org.jenkins-ci.plugins
>> plugin
>> 3.18
>> 
>>
>> external-workspace-manager
>> 1.1.3-SNAPSHOT
>> hpi
>>
>> 
>> 2.60.3
>> 8
>>
>> -Xmx1024m
>>
>>  
>>
>>
>> and the AWS Java SDK property was copied from ec2-plugin pom.xml.
>> it looks like 
>>
>> 
>> org.jenkins-ci.plugins
>> aws-java-sdk
>> 1.11.457
>> 
>>
>>  
>> And the pom.xml in ec2-plugin looks like 
>>
>> 
>> org.jenkins-ci.plugins
>> plugin
>> 3.25
>> 
>>
>>
>> I tried upgrade my plugin version to 3.25, but didn't work, does anyone 
>> know what's the potential problem ? Thanks !
>>
>>
>>
>>
>>
>>
>>
>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/2ab86fec-880c-4470-9604-e14d7df64e22%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/bfc0a42c-dacf-49bb-91d9-9704d159de46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Common Coding Questions in GSoC 2019

[Baptiste Mathus]

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 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 of my pom.xml look like this
>
> 
> org.jenkins-ci.plugins
> plugin
> 3.18
> 
>
> external-workspace-manager
> 1.1.3-SNAPSHOT
> hpi
>
> 
> 2.60.3
> 8
>
> -Xmx1024m
>
> 
>
>
> and the AWS Java SDK property was copied from ec2-plugin pom.xml.
> it looks like
>
> 
> org.jenkins-ci.plugins
> aws-java-sdk
> 1.11.457
> 
>
>
> And the pom.xml in ec2-plugin looks like
>
> 
> org.jenkins-ci.plugins
> plugin
> 3.25
> 
>
>
> I tried upgrade my plugin version to 3.25, but didn't work, does anyone
> know what's the potential problem ? Thanks !
>
>
>
>
>
>
>
>
> --
> 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 discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/2ab86fec-880c-4470-9604-e14d7df64e22%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6ywqmoDJ87gOLss0n1T-DvCE29PS3LG4%3DkbbgDDGNqVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Common Coding Questions in GSoC 2019

[Yufei Zhang]

>
> 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 of my pom.xml look like this


org.jenkins-ci.plugins
plugin
3.18


external-workspace-manager
1.1.3-SNAPSHOT
hpi


2.60.3
8

-Xmx1024m

 


and the AWS Java SDK property was copied from ec2-plugin pom.xml.
it looks like 


org.jenkins-ci.plugins
aws-java-sdk
1.11.457


 
And the pom.xml in ec2-plugin looks like 


org.jenkins-ci.plugins
plugin
3.25



I tried upgrade my plugin version to 3.25, but didn't work, does anyone 
know what's the potential problem ? Thanks !








-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2ab86fec-880c-4470-9604-e14d7df64e22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: RunWithSCM

[Jesse Glick]

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 point, they are not annotated with 
> @Extension, so Is there a another way to get this? Even a slow way cause i'm 
> just doing it on startup. I've been trying to google for various ways to get 
> all the classes that implement an implementation

Not sure I follow. You are asking if there is a way to get all
possible `Action` subtypes that might be returned from a
`getAllActions()` method? If so, it is not possible, at least not in
any supported way. The same would apply to pretty much any abstract
type in Jenkins—`Cause`, `CauseOfInterruption`, ad nauseam.

> Can I find all classes that are @Exported?

Without scanning all bytecode in the system? No.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr38aBtCmGi%3Dhg%2BYK5J7AOADKuLQq%3DwWEP_rV8K0bzA1-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: RunWithSCM

['Gavin Mogan' via Jenkins Developers]

> `@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 a fallback)

> Sounds like a question about GraphQL,

Its a bit of all 3. Stapler works somewhat in runtime, looking at the
annotations of the actual class, graphql you need to define the schema
before the query is executed. Ideally even before its sent. When its still
being built. So i'm having to shift my designs a bit.

For the most part I have something basic working that gets data. Right now
I'm using ExtensionList's TopLevelDescriptor to find all the job types, and
then building a graphql schema from those. Its working beautifully, but
some of the lower level objects I'm unsure how to handle.

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 point, they are not annotated with
@Extension, so Is there a another way to get this? Even a slow way cause
i'm just doing it on startup. I've been trying to google for various ways
to get all the classes that implement an implementation but not really
having much luck. As far as I can tell, stapler doesn't have a master list,
it just has a cache it uses when you ask for the model -
https://github.com/stapler/stapler/blob/master/core/src/main/java/org/kohsuke/stapler/export/ModelBuilder.java

Okay, since i started writing this, I found out about the reflections
class/library.

so I think I can do as follows, which is probably a little expensive (And
fairly slow, had to limit it to just hudson/jenkins package names), but is
only done on startup:

```
for (Package pkg :  Package.getPackages()) {
if (pkg.getName().toLowerCase().contains("jenkins") ||
pkg.getName().toLowerCase().contains("hudson")) {
Reflections reflections = new
Reflections(pkg.getName());
classQueue.addAll(reflections.getSubTypesOf(clazz));
}
}
```

Is there a better way of doing this? Can I find all classes that are
@Exported?

Gavin





On Fri, May 31, 2019 at 7:30 AM Jesse Glick  wrote:

> On Fri, May 31, 2019 at 3:17 AM 'Gavin Mogan' via Jenkins Developers
>  wrote:
> > From a stapler point of view I have a few questions about RunWithSCM and
> other job interfaces.
> >
> > 1) Is there any reason its not exported? I'm assuming because the
> classes that actually implement it are exported?
>
> `@ExportedBean` you mean? Or `@Exported`? These annotations cannot be
> used on interfaces or interface methods.
>
> > 2) Is there anything special about RunWithSCM and its kin that would
> help me find other useful implementations?
>
> Can you be more explicit?
>
> > With graphql, when fetching data, as I understand it, you need to say
> how to handle subclasses.
>
> Sounds like a question about GraphQL, or its Java bindings (that mixin
> interfaces are not well supported), rather than about Jenkins per se.
>
> >... on FreeStyleProject { // scm stuff (legacy) }
> >... on RunWithSCM { // modern scm stuff  }
>
> In this case `AbstractBuild` is retrofitted to implement `RunWithSCM`
> so the first clause would not be necessary.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/RklYADD2uKc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0cwe28ORgJDUnwTZu0Ls-%2BY4RHcQ3DAVbvxkYAU9f5oQ%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuvW5m4T%3DTLu55y0vw3WdBt%2BeNodDwCaTst0TDmmgVp0zA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Alyssa Tong]

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% discount.

thnx,
alyssa

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNayDT%2Bt%2Bv7%3DfRJp7z5zdCoVqcPbQN5NKAdPJP4g6wfdajw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Baptiste Mathus]

+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 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, Pipeline: Stage Step, Pipeline: REST API). First 3 plugins are also
> about moving to 2.60.x+ because of the ongoing work on JCasc plugin support
> in these plugins. I think it is a time to discuss phasing out Java 7
> support in our development tools.
>
> *Why?*
>
>- Not all upstream libraries still support Java 7 (e.g. Animal Sniffer
>1.18 in this PR ).
>So we cannot update newest patches, including ones which might be required
>for JDK 11 support in our build tools
>- We have some dependencies and profiles specific to Java 7. It
>increases the maintenance cost
>- While we support Java 7, It is harder to include new dependencies
>and improve our test frameworks
>
> *What do I propose to change?*
>
>- Drop Java 7 and Jenkins 2.59- support in Plugin POM
>
>- Drop Java 7 support from Jenkins parent POM
> (one we use for core and its libs)
>- Drop Java 7 support from Jenkins Test Harness, bump the target core
>to 2.60.3.
>   - It will allow us to extend the test frameworks, e.g. by embedding
>   JCasC support there (e.g. this benchmarking PR
>    by
>   Abhyudaya)
>- Drop Java 7 support in Docker Fixtures and other test libraries we
>maintain in the Jenkins community
>- Drop Java 7 support and old Core support from Plugin Compat Teste
>r, if feasible
>- Remove 2.59- test conditions and checks from Jenkins Acceptance Test
>Harness 
>- ... // and so on
>
> Such phase out could be done incrementally when maintainers or
> contributors are interested to do so. I would consider this thread as
> giving a green light to whomever wants to drop old Java version support
> from Dev tools.
>
> Would appreciate feedback.
>
> Best regards,
> Oleg
>
>
>
>
> --
> 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 discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDExo3iEqugyCABm9cT3zsaXwF4qhmr63%3Deej3Yt1%2BdKA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPyTVp28XEkiuws%3DYN5c9HifGP0ytCns-vXqyJxpsOYmz0Pv5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Matt Sicker]

+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 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 insists on providing support for
>>> very old core lines for whatever reason, they can create a backport
>>> branch, or simply decline to update tool versions, but it is
>>> appropriate for all plugins in the Setup wizard’s recommended list to
>>> use a 2.60.x or newer baseline and use current tooling.
>>>
>>>
>> +1 from me as well.
>>
>>
>>> --
>>> 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 discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr17qrqwOuzQu27U-WHxmjKqYuYFbdxRGKooj4ovfZRmQQ%40mail.gmail.com
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
>> --
>> 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 discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEmSgUwOx236tCPTa1tWu-6PFef22%3DCw%3DX5_WfSZSTkAQ%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> *Robert Sandell*
> Software Engineer
> CloudBees, Inc.
> [image: CloudBees-Logo.png] 
> E: rsand...@cloudbees.com
> Twitter: robert_sandell
>
> --
> 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 discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1FX_h5P0pEEKhnnNh2m9HmzVkAfGJkSfmi1pL8cZY%2Bkw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Matt Sicker
Senior Software Engineer, CloudBees

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4oz-kA6DXQt7WsZpq26E4rSFXiR3vxD1xucWDZxhgVSF-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Parker Ennis]

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 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
>> https://groups.google.com/forum/#!msg/jenkinsci-dev/ae71SSLtdU4/ZUjNn3CsAgAJ
>>  ?
>>
>>
> +1
> AdoptOpenJDK has been working great for me in both Windows and Linux
> environments.
>
> Mark Waite
>
>
>> BR, Oleg
>>
>>
>> On Monday, June 3, 2019 at 1:11:24 PM UTC+2, Adrien Lecharpentier wrote:
>>>
>>> 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.

 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 jenkins running on java 11.

 Excepted minor issues that we fixed  during the migration, upgrading
 from jdk8 to jdk11 was really easy.

 In short we executed following steps:

- Set jenkins master in maintenance mode "Prepare for shutdown".
- Backup jenkins home, yolo
- Update JAVA_OPTS with options specific to java11 as defined here

 
  mainly
related to the garbage collector
- Move from the docker image jenkins/jenkins:lts-alpine to
jenkins/jenkins:lts-jdk11
- Restart Jenkins
- Ensure linux/windows agents use the same major java version than
master ( java 11 )


 For the windows agent we had to change the init script to use
 zulu11.31.11
  
 instead
 of zulu8.28.0.1
 
 And the linux agent was already using java11 anyway since we upgrade
 the agent to ubuntu 18.04

 As usual, feel free to report any issues that you may have about
 ci.jenkins.io, on issues.jenkins-ci.org using the 'infra' project.

 Remark, upgrading the other jenkins intances to java11 is not yet
 planned.

 Cheers

 ---
 -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
 ---




 On Mon, May 27, 2019, at 11:57 AM, Olblak wrote:

 Hi Everybody,

 The platform sig  has been working
 hard on running jenkins with java11 and it's now time to use it in a real
 life scenario.

 Adrien Lecharpentier and I will upgrade ci.jenkins.io next Monday 3th
 of June at 9AM UTC+2.

 As usually with such maintenance, we'll communicate in different ways:
 * We'll be on a call using Google Meet
  and on irc #jenkins-infra
 * We'll notify on this mail thread and update INFRA-2115
  when the migration
 is done.

 In short we'll execute following steps:
 * Set jenkins master in maintenance mode "Prepare for shutdown"
 * Backup jenkins home
 * Update JAVA_OPTS with options specific to java11
 * Move from the docker image jenkins/jenkins:lts-alpine to
 jenkins/jenkins:jdk11
 * Ensure linux/windows agents use the same major java version than
 master ( java 11 )

 Remark: We won't (voluntarily ) modify the other jenkins instances, at
 least for this maintenance window.

 Cheers

 ---
 -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
 ---


 --
 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 jenkin...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/b0ec4765-ba06-4460-a832-c9522c1f796e%40www.fastmail.com
 
 .
 For more options, visit https://groups.google.com/d/optout.


 --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Developers" 

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

[Robert Sandell]

+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 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 whatever reason, they can create a backport
>> branch, or simply decline to update tool versions, but it is
>> appropriate for all plugins in the Setup wizard’s recommended list to
>> use a 2.60.x or newer baseline and use current tooling.
>>
>>
> +1 from me as well.
>
>
>> --
>> 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 discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr17qrqwOuzQu27U-WHxmjKqYuYFbdxRGKooj4ovfZRmQQ%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Thanks!
> Mark Waite
>
> --
> 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 discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEmSgUwOx236tCPTa1tWu-6PFef22%3DCw%3DX5_WfSZSTkAQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] 
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1FX_h5P0pEEKhnnNh2m9HmzVkAfGJkSfmi1pL8cZY%2Bkw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 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 whatever reason, they can create a backport
> branch, or simply decline to update tool versions, but it is
> appropriate for all plugins in the Setup wizard’s recommended list to
> use a 2.60.x or newer baseline and use current tooling.
>
>
+1 from me as well.


> --
> 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 discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr17qrqwOuzQu27U-WHxmjKqYuYFbdxRGKooj4ovfZRmQQ%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEmSgUwOx236tCPTa1tWu-6PFef22%3DCw%3DX5_WfSZSTkAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: hashicorp vault plugin new release

[Oleg Nenashev]

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 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 master branch seems to be OK.
>>
>> Does anybody know if this plugin is actively maintained, and if a release
>> is somehow planned? This would avoid us to fork this plugin internally.
>>
>> Thanks,
>> Damien
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/vFKgulTPxIg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/09edd796-096e-438b-825f-063154f24370%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCAVGS_mBUPiMQGgsWU%3DJ598qnqW9k%3DazUBhCbXR45MhA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: hashicorp vault plugin new release

[Oleg Nenashev]

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 
> 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 master branch seems to be OK.
>
> Does anybody know if this plugin is actively maintained, and if a release 
> is somehow planned? This would avoid us to fork this plugin internally.
>
> Thanks,
> Damien
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/09edd796-096e-438b-825f-063154f24370%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Mark Waite]

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 also wonder about using Zulu for Windows agents. Should not we move to
> AdoptOpenJDK as it was discussed in
> https://groups.google.com/forum/#!msg/jenkinsci-dev/ae71SSLtdU4/ZUjNn3CsAgAJ
>  ?
>
>
+1
AdoptOpenJDK has been working great for me in both Windows and Linux
environments.

Mark Waite


> BR, Oleg
>
>
> On Monday, June 3, 2019 at 1:11:24 PM UTC+2, Adrien Lecharpentier wrote:
>>
>> 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.
>>>
>>> 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 jenkins running on java 11.
>>>
>>> Excepted minor issues that we fixed  during the migration, upgrading
>>> from jdk8 to jdk11 was really easy.
>>>
>>> In short we executed following steps:
>>>
>>>- Set jenkins master in maintenance mode "Prepare for shutdown".
>>>- Backup jenkins home, yolo
>>>- Update JAVA_OPTS with options specific to java11 as defined here
>>>
>>> 
>>>  mainly
>>>related to the garbage collector
>>>- Move from the docker image jenkins/jenkins:lts-alpine to
>>>jenkins/jenkins:lts-jdk11
>>>- Restart Jenkins
>>>- Ensure linux/windows agents use the same major java version than
>>>master ( java 11 )
>>>
>>>
>>> For the windows agent we had to change the init script to use
>>> zulu11.31.11
>>>  
>>> instead
>>> of zulu8.28.0.1
>>> 
>>> And the linux agent was already using java11 anyway since we upgrade the
>>> agent to ubuntu 18.04
>>>
>>> As usual, feel free to report any issues that you may have about
>>> ci.jenkins.io, on issues.jenkins-ci.org using the 'infra' project.
>>>
>>> Remark, upgrading the other jenkins intances to java11 is not yet
>>> planned.
>>>
>>> Cheers
>>>
>>> ---
>>> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
>>> ---
>>>
>>>
>>>
>>>
>>> On Mon, May 27, 2019, at 11:57 AM, Olblak wrote:
>>>
>>> Hi Everybody,
>>>
>>> The platform sig  has been working
>>> hard on running jenkins with java11 and it's now time to use it in a real
>>> life scenario.
>>>
>>> Adrien Lecharpentier and I will upgrade ci.jenkins.io next Monday 3th
>>> of June at 9AM UTC+2.
>>>
>>> As usually with such maintenance, we'll communicate in different ways:
>>> * We'll be on a call using Google Meet
>>>  and on irc #jenkins-infra
>>> * We'll notify on this mail thread and update INFRA-2115
>>>  when the migration is
>>> done.
>>>
>>> In short we'll execute following steps:
>>> * Set jenkins master in maintenance mode "Prepare for shutdown"
>>> * Backup jenkins home
>>> * Update JAVA_OPTS with options specific to java11
>>> * Move from the docker image jenkins/jenkins:lts-alpine to
>>> jenkins/jenkins:jdk11
>>> * Ensure linux/windows agents use the same major java version than
>>> master ( java 11 )
>>>
>>> Remark: We won't (voluntarily ) modify the other jenkins instances, at
>>> least for this maintenance window.
>>>
>>> Cheers
>>>
>>> ---
>>> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
>>> ---
>>>
>>>
>>> --
>>> 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 jenkin...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/b0ec4765-ba06-4460-a832-c9522c1f796e%40www.fastmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>> --
>>> 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 jenkin...@googlegroups.com.
>>> To view this discussion on the web visit
>>> 

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

[Jesse Glick]

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 whatever reason, they can create a backport
branch, or simply decline to update tool versions, but it is
appropriate for all plugins in the Setup wizard’s recommended list to
use a 2.60.x or newer baseline and use current tooling.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr17qrqwOuzQu27U-WHxmjKqYuYFbdxRGKooj4ovfZRmQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[James Nord]

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 2.60.3 and above, and 
> there are only few exceptions in top-50 plugins (Mailer, Git Client, Git 
> Server, Pipeline: Stage Step, Pipeline: REST API). First 3 plugins are also 
> about moving to 2.60.x+ because of the ongoing work on JCasc plugin support 
> in these plugins. I think it is a time to discuss phasing out Java 7 
> support in our development tools.
>
> *Why?*
>
>- Not all upstream libraries still support Java 7 (e.g. Animal Sniffer 
>1.18 in this PR ). 
>So we cannot update newest patches, including ones which might be required 
>for JDK 11 support in our build tools
>- We have some dependencies and profiles specific to Java 7. It 
>increases the maintenance cost
>- While we support Java 7, It is harder to include new dependencies 
>and improve our test frameworks
>
> *What do I propose to change?*
>
>- Drop Java 7 and Jenkins 2.59- support in Plugin POM 
>
>- Drop Java 7 support from Jenkins parent POM 
> (one we use for core and its libs)
>- Drop Java 7 support from Jenkins Test Harness, bump the target core 
>to 2.60.3. 
>   - It will allow us to extend the test frameworks, e.g. by embedding 
>   JCasC support there (e.g. this benchmarking PR 
>    by 
>   Abhyudaya)
>- Drop Java 7 support in Docker Fixtures and other test libraries we 
>maintain in the Jenkins community
>- Drop Java 7 support and old Core support from Plugin Compat Teste 
>r, if feasible
>- Remove 2.59- test conditions and checks from Jenkins Acceptance Test 
>Harness 
>- ... // and so on
>
> Such phase out could be done incrementally when maintainers or 
> contributors are interested to do so. I would consider this thread as 
> giving a green light to whomever wants to drop old Java version support 
> from Dev tools.
>
> Would appreciate feedback.
>
> Best regards,
> Oleg
>
>
>
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/58fce30f-771e-4cdb-be94-3afd9835d036%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Oleg Nenashev]

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 
https://groups.google.com/forum/#!msg/jenkinsci-dev/ae71SSLtdU4/ZUjNn3CsAgAJ
 ?

BR, Oleg


On Monday, June 3, 2019 at 1:11:24 PM UTC+2, Adrien Lecharpentier wrote:
>
> 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.
>>
>> 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 jenkins running on java 11.
>>
>> Excepted minor issues that we fixed  during the migration, upgrading from 
>> jdk8 to jdk11 was really easy.
>>
>> In short we executed following steps:
>>
>>- Set jenkins master in maintenance mode "Prepare for shutdown".
>>- Backup jenkins home, yolo
>>- Update JAVA_OPTS with options specific to java11 as defined here 
>>
>> 
>>  mainly 
>>related to the garbage collector
>>- Move from the docker image jenkins/jenkins:lts-alpine to 
>>jenkins/jenkins:lts-jdk11
>>- Restart Jenkins
>>- Ensure linux/windows agents use the same major java version than 
>>master ( java 11 )
>>
>>
>> For the windows agent we had to change the init script to use 
>> zulu11.31.11 
>>  
>> instead 
>> of zulu8.28.0.1 
>> 
>> And the linux agent was already using java11 anyway since we upgrade the 
>> agent to ubuntu 18.04
>>
>> As usual, feel free to report any issues that you may have about 
>> ci.jenkins.io, on issues.jenkins-ci.org using the 'infra' project.
>>
>> Remark, upgrading the other jenkins intances to java11 is not yet planned.
>>
>> Cheers
>>
>> ---
>> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
>> ---
>>
>>
>>
>>
>> On Mon, May 27, 2019, at 11:57 AM, Olblak wrote:
>>
>> Hi Everybody, 
>>
>> The platform sig  has been working 
>> hard on running jenkins with java11 and it's now time to use it in a real 
>> life scenario. 
>>
>> Adrien Lecharpentier and I will upgrade ci.jenkins.io next Monday 3th of 
>> June at 9AM UTC+2.
>>
>> As usually with such maintenance, we'll communicate in different ways:
>> * We'll be on a call using Google Meet 
>>  and on irc #jenkins-infra
>> * We'll notify on this mail thread and update INFRA-2115 
>>  when the migration is 
>> done.
>>
>> In short we'll execute following steps:
>> * Set jenkins master in maintenance mode "Prepare for shutdown"
>> * Backup jenkins home
>> * Update JAVA_OPTS with options specific to java11
>> * Move from the docker image jenkins/jenkins:lts-alpine to 
>> jenkins/jenkins:jdk11
>> * Ensure linux/windows agents use the same major java version than master 
>> ( java 11 )
>>
>> Remark: We won't (voluntarily ) modify the other jenkins instances, at 
>> least for this maintenance window.
>>
>> Cheers
>>
>> ---
>> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
>> ---
>>
>>
>> --
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/b0ec4765-ba06-4460-a832-c9522c1f796e%40www.fastmail.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/a94927d2-520c-4953-b666-50d9eb6ba10e%40www.fastmail.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Adrien Lecharpentier
>

-- 

hashicorp vault plugin new release

[Damien Coraboeuf]

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 master branch seems to be OK.

Does anybody know if this plugin is actively maintained, and if a release 
is somehow planned? This would avoid us to fork this plugin internally.

Thanks,
Damien

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6ab186a0-4a94-463c-b595-e8d74d173e22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Proposal - Phasing out Java 7 support in Jenkins Dev tools

[Oleg Nenashev]

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, Pipeline: Stage Step, Pipeline: REST API). First 3 plugins are also
about moving to 2.60.x+ because of the ongoing work on JCasc plugin support
in these plugins. I think it is a time to discuss phasing out Java 7
support in our development tools.

*Why?*

   - Not all upstream libraries still support Java 7 (e.g. Animal Sniffer
   1.18 in this PR ). So
   we cannot update newest patches, including ones which might be required for
   JDK 11 support in our build tools
   - We have some dependencies and profiles specific to Java 7. It
   increases the maintenance cost
   - While we support Java 7, It is harder to include new dependencies and
   improve our test frameworks

*What do I propose to change?*

   - Drop Java 7 and Jenkins 2.59- support in Plugin POM
   
   - Drop Java 7 support from Jenkins parent POM
    (one we use for core and its libs)
   - Drop Java 7 support from Jenkins Test Harness, bump the target core to
   2.60.3.
  - It will allow us to extend the test frameworks, e.g. by embedding
  JCasC support there (e.g. this benchmarking PR
   by
  Abhyudaya)
   - Drop Java 7 support in Docker Fixtures and other test libraries we
   maintain in the Jenkins community
   - Drop Java 7 support and old Core support from Plugin Compat Teste
   r, if feasible
   - Remove 2.59- test conditions and checks from Jenkins Acceptance Test
   Harness 
   - ... // and so on

Such phase out could be done incrementally when maintainers or contributors
are interested to do so. I would consider this thread as giving a green
light to whomever wants to drop old Java version support from Dev tools.

Would appreciate feedback.

Best regards,
Oleg

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDExo3iEqugyCABm9cT3zsaXwF4qhmr63%3Deej3Yt1%2BdKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Facing Error in loading Build Action page

[Jesse Glick]

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, but
if this Jelly file is associated with a `BuildAction`, then that class
should have a `getBuild()` method returning a `Run`.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3v-xkzx5YbAHBbmzL6VZPHz4pgc1Yf8GYD74PUrHhKqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Appending to build log after complete

[Jesse Glick]

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, like attach an `Action` that
somehow displays an analysis, for example in a box on the build’s
index page.

> Is there a supported way to append to a log file after the build is completed?

No.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3a3pF7prC6Q7Xf0WSQ16fSDf1MsUhgkSqcGgQN8FoOkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Common Coding Questions in GSoC 2019

[Jesse Glick]

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 box is checked.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3E-T7EFtUV3ySZ3cx35-6Ur7TGZLim-qcE2q74-o9ZRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Common Coding Questions in GSoC 2019

[Jesse Glick]

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 email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1q5WM6cVzLHbMFRnm457RZO6c9cFLMmRPrMB6AZ92v_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Common Coding Questions in GSoC 2019

[Jesse Glick]

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 processor!)

> For Q2, this has something to do with the Jenkins API for
> Descriptor/Describable. Typically, you can use a no-arg constructor in
> your Descriptor class to call Descriptor's default constructor which
> uses reflection to determine the proper class argument. For more
> advanced scenarios, you may need to pass an explicit class reference
> to the constructor

Some `abstract` subtypes of `Descriptor` include a `protected`
constructor accepting `Class` just in case some concrete subclass does
not use the normal idiom of defining the descriptor as a nested class
of the corresponding `Describable`. Generally you can ignore this
overload.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr28Abr7LkHE6uEAnD0bgJ%2BZkU-F%2Beg3cLnDPMEMuiNFWw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Adrien Lecharpentier]

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.
>
> 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 jenkins running on java 11.
>
> Excepted minor issues that we fixed  during the migration, upgrading from
> jdk8 to jdk11 was really easy.
>
> In short we executed following steps:
>
>- Set jenkins master in maintenance mode "Prepare for shutdown".
>- Backup jenkins home, yolo
>- Update JAVA_OPTS with options specific to java11 as defined here
>
> 
>  mainly
>related to the garbage collector
>- Move from the docker image jenkins/jenkins:lts-alpine to
>jenkins/jenkins:lts-jdk11
>- Restart Jenkins
>- Ensure linux/windows agents use the same major java version than
>master ( java 11 )
>
>
> For the windows agent we had to change the init script to use zulu11.31.11
>  instead
> of zulu8.28.0.1
> 
> And the linux agent was already using java11 anyway since we upgrade the
> agent to ubuntu 18.04
>
> As usual, feel free to report any issues that you may have about
> ci.jenkins.io, on issues.jenkins-ci.org using the 'infra' project.
>
> Remark, upgrading the other jenkins intances to java11 is not yet planned.
>
> Cheers
>
> ---
> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
>
>
>
>
> On Mon, May 27, 2019, at 11:57 AM, Olblak wrote:
>
> Hi Everybody,
>
> The platform sig  has been working
> hard on running jenkins with java11 and it's now time to use it in a real
> life scenario.
>
> Adrien Lecharpentier and I will upgrade ci.jenkins.io next Monday 3th of
> June at 9AM UTC+2.
>
> As usually with such maintenance, we'll communicate in different ways:
> * We'll be on a call using Google Meet
>  and on irc #jenkins-infra
> * We'll notify on this mail thread and update INFRA-2115
>  when the migration is
> done.
>
> In short we'll execute following steps:
> * Set jenkins master in maintenance mode "Prepare for shutdown"
> * Backup jenkins home
> * Update JAVA_OPTS with options specific to java11
> * Move from the docker image jenkins/jenkins:lts-alpine to
> jenkins/jenkins:jdk11
> * Ensure linux/windows agents use the same major java version than master
> ( java 11 )
>
> Remark: We won't (voluntarily ) modify the other jenkins instances, at
> least for this maintenance window.
>
> Cheers
>
> ---
> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
>
>
> --
> 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 discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/b0ec4765-ba06-4460-a832-c9522c1f796e%40www.fastmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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 discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/a94927d2-520c-4953-b666-50d9eb6ba10e%40www.fastmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adrien Lecharpentier

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAKwJSvwWi59v5K8RjjXFU%3DcNOhibV%2B_v%3DVMxhPTeN4dZruPtag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Olblak]

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 jenkins running on java 11.

Excepted minor issues that we fixed during the migration, upgrading from jdk8 
to jdk11 was really easy.

In short we executed following steps:
 * Set jenkins master in maintenance mode "Prepare for shutdown".
 * Backup jenkins home, yolo
 * Update JAVA_OPTS with options specific to java11 as defined here 

 mainly related to the garbage collector
 * Move from the docker image jenkins/jenkins:lts-alpine to 
jenkins/jenkins:lts-jdk11
 * Restart Jenkins
 * Ensure linux/windows agents use the same major java version than master ( 
java 11 )

For the windows agent we had to change the init script to use zulu11.31.11 
 instead 
of zulu8.28.0.1 

And the linux agent was already using java11 anyway since we upgrade the agent 
to ubuntu 18.04

As usual, feel free to report any issues that you may have about ci.jenkins.io, 
on issues.jenkins-ci.org using the 'infra' project.

Remark, upgrading the other jenkins intances to java11 is not yet planned.

Cheers

---
-> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---




On Mon, May 27, 2019, at 11:57 AM, Olblak wrote:
> Hi Everybody, 
> 
> The platform sig  has been working hard on 
> running jenkins with java11 and it's now time to use it in a real life 
> scenario. 
> 
> Adrien Lecharpentier and I will upgrade ci.jenkins.io next Monday 3th of June 
> at 9AM UTC+2.
> 
> As usually with such maintenance, we'll communicate in different ways:
> * We'll be on a call using Google Meet  
> and on irc #jenkins-infra
> * We'll notify on this mail thread and update INFRA-2115 
>  when the migration is done.
> 
> In short we'll execute following steps:
> * Set jenkins master in maintenance mode "Prepare for shutdown"
> * Backup jenkins home
> * Update JAVA_OPTS with options specific to java11
> * Move from the docker image jenkins/jenkins:lts-alpine to 
> jenkins/jenkins:jdk11
> * Ensure linux/windows agents use the same major java version than master ( 
> java 11 )
> 
> Remark: We won't (voluntarily ) modify the other jenkins instances, at least 
> for this maintenance window.
> 
> Cheers
> 
> ---
> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
> 
> 

> --
>  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 discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/b0ec4765-ba06-4460-a832-c9522c1f796e%40www.fastmail.com
>  
> .
>  For more options, visit https://groups.google.com/d/optout.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a94927d2-520c-4953-b666-50d9eb6ba10e%40www.fastmail.com.
For more options, visit https://groups.google.com/d/optout.

Appending to build log after complete

[Tim Jacomb]

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 to it about the scan result
Code:
https://github.com/jenkinsci/build-failure-analyzer-plugin/blob/master/src/main/java/com/sonyericsson/jenkins/plugins/bfa/sod/ScanOnDemandTask.java#L110

On recent pipeline versions this is logging exceptions on every call
"WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid
calling getLogFile on TestWorkflow/TestWorkflow #362
java.lang.UnsupportedOperationException"

Is there a supported way to append to a log file after the build is
completed? I see ways to get an InputStream, the log text and writeLogTo
(seems to be for writing a whole log though)

Or should this functionality be re-written?
My guess is that build-failure-analyzer should probably have it's own log
file, which can just be overwritten on every scan.
If this is the approach is there any good example out there that you would
recommend?

Thanks
Tim

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicsP%2B1hpkVEjT319ZTg9oS7_KrAt2x0qe6HzFYDAFv72w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Coding Questions: (GSoC) Artifact Promotion Plugin for Pipeline

[prastik Gyawali]

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:
* PromotionCondition -> PromotionProcess -> Actual 
Conditions(Manual,Self...) -> PromotionProcess.*
 After listing all the conditions in the DescribableList how do we 
actually match the input parameter for promotion to the exact class(eg: if 
user wants manual promotion, how does the plugin send the 
build/other information to the exact class(self,manual.java.) for 
further processing?  )
I found the *getPromotionCondition *method to be close. But this method is 
not called anywhere in the conditions.? 
  public PromotionCondition getPromotionCondition(String 
promotionClassName) {
for (PromotionCondition condition : conditions) {
if (condition.getClass().getName().equals(promotionClassName)) {
return condition;
}
}

return null;
}

2) Also if the flow is incorrect please help rectify it. And after the 
respective promotion modules are called is:
public Future considerPromotion2

used for the final promotion.

Thank You!!

Reference Links : link-1 

 
, link-2 

 
, link-3 


-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5675157d-b34b-4e2d-9c2f-2891513f80ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[prastik Gyawali]

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:
  PromotionCondition -> PromotionProcess -> Conditions(Self,Manual...) 
-> PromotionProcess


-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0cb6cc4a-aa92-4701-a6e2-7052a236c464%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.