Re: Jenkins UI/UX Hackathon on May 25-29

[Oleg Nenashev]

Hi all,

The event is live, and we have the initial bundle of resources published. 
Thanks to all reviewers and contributors! If you are planning to attend, it 
would be great if you could RSVP in the form so that we start planning.

   - Landing page: https://www.jenkins.io/events/online-hackfest/2020-uiux/
   - Registration form: https://forms.gle/MrkASJagxNvdXBbdA 
   - FAQ: https://www.jenkins.io/events/online-hackfest/2020-uiux/faq/
   - Doodle for the opening meetings on May 25: 
   https://doodle.com/poll/h7pwbstf5vf24ddf

This week we will keep working on project ideas for the hackfest, the web 
page will be updated accordingly. Please do not hesitate to submit pull 
request or to suggest topics here 

.

Best regards,
Oleg Nenashev



On Friday, May 8, 2020 at 11:12:56 AM UTC+2, Oleg Nenashev wrote:
>
> Hi all,
>
> Some updates:
>
>- Yesterday we had an overview of the suggested hackfest at the 
>Advocacy special interest group meeting
>- Recorded Hackfest overview: https://youtu.be/Wucs8Kzuq_g?t=288
>   - Meeting notes: 
>   
> https://docs.google.com/document/d/1K5dTSqe56chFhDSGNfg_MCy-LmseUs_S3ys_tg60sTs/edit#bookmark=id.mzvy4td1x4o2
>   - Continuous Delivery Foundation is likely to co-sponsor swag for 
>   the event
>- User Interface track. One day before we had a meeting with the 
>interested contributors. There we discussed potential topics for the UI 
>enhancements
>   - Current list of ideas: here 
>   
> 
>   - Meeting notes: 
>   
> https://docs.google.com/document/d/1Wve6fXV7mPkqtFn_gR9kfDWq-qOu6pPLYcDzKTjOHoI/edit#heading=h.fmype48v88f
>- Documentation track
>   - Mark started creating User documentation migration tickets in 
>   GitHub Issues: https://github.com/jenkins-infra/jenkins.io/issues
>
> I will try to submit a pull request with initial hackathon landing pages 
> today.
>
>
> Best regards,
> Oleg 
>
>
>
> On Monday, May 4, 2020 at 11:36:52 AM UTC+2, Oleg Nenashev wrote:
>>
>> Hi all,
>>
>> As discussed with Marky in the Advocacy and Outreach SIG channel, I would 
>> like to schedule a short call to discuss details with interested 
>> contributors. I have created a Doodle for Tuesday/Wednesday. In addition to 
>> that, we have a regular Advocacy meeting on Thursday, I also added 
>> the hackfest to its agenda.
>>
>> Best regards,
>> Oleg
>>
>> On Saturday, May 2, 2020 at 10:06:40 AM UTC+2, Oleg Nenashev wrote:
>>>
>>> Hi all,
>>>
>>> As it was discussed at the UX SIG meeting, at the CloudBees community 
>>> team we would like to organize an online hackathon which would focus on 
>>> Jenkins User Experience. We propose to hold a week-long hop-in/hop-off 
>>> event, similar to what we did in 2018 for the Jenkins and Java 10+ 
>>> online hackathon 
>>> . We 
>>> target May 25-29 so that it is aligned with the GSoC community bonding 
>>> phase. Event goals:
>>>
>>>- Bring contributors together, have some fun and community bonding
>>>- Facilitate contributions from newcomers,onboard new contributors
>>>- Drive progress in UI/UX and user documentation initiatives within 
>>>the Jenkins Roadmap 
>>>- Spread the word about ongoing UI/UX improvements
>>>- Enhance the Jenkins brand by leveraging Jenkins is The Way 
>>> campaign
>>>
>>> I have started a planning document 
>>> ,
>>>  everyone 
>>> is welcome to contribute and to propose their UI/UX project ideas 
>>> 
>>>  
>>> for the hackathon. This document will be converted into an event page, 
>>> similar to what we did for Hacktoberfest last year (landing 
>>> ). 
>>>  
>>> This event will be organized within the Advocacy SIG, and it 
>>> will be coordinated with UX and Docs SIGs. Other SIGs and working groups 
>>> are also welcome to join! We would like to keep the hackathon focused on UI 
>>> and UX, but there are areas for other SIGs to participate, e.g. Pipeline 
>>> Authoring UX or localization. It would be also great to have more reviewers 
>>> and event hosts, please sign up here 
>>> 
>>> .
>>>
>>> As always, any feedback will be appreciated and, if possible, 
>>> incorporated into the plan! Thanks to all contributors who participated in 
>>> the initial discussions.
>>>
>>> Best regards,
>>> 

Re: Jenkins-Infra pipeline library changes issue

[Oleg Nenashev]

We have reverted the recommendedConfigurations() patch for now.
Back to the drawing board, we still need to somehow ensure that recommended 
configurations can evolve without breaking instances.


On Tuesday, May 5, 2020 at 3:01:35 AM UTC+2, Richard Bywater wrote:
>
> Thanks. I totally somehow missed the "Gradle support in" part of that both 
> when I read it the couple of times and when I pasted... Time for a break I 
> think!
>
> Richard.
>
> On Tue, 5 May 2020 at 12:59, Slide > 
> wrote:
>
>>
>>
>> On Mon, May 4, 2020 at 5:53 PM Richard Bywater > > wrote:
>>
>>> On Tue, 5 May 2020 at 01:01, Jesse Glick >> > wrote:
>>>
 > I've got the build to work again by removing 
 recommendedConfigurations and switching to explicitly building the minimum 
 version of Jenkins that is referenced in the pom.xml

 This makes no sense. If you _only_ want to build the version
 referenced in `pom.xml`, just

 buildPlugin()

 The point of `configurations` is to build against _newer_ versions as 
 well.

>>>
>>> Thanks - I didn't realise that. After reading the README 
>>> https://github.com/jenkins-infra/pipeline-library I wasn't clear on 
>>> what the default behaviour was if you didn't specify any of the optional 
>>> arguments. I'm also confused by the statement "Gradle support in 
>>> buildPlugin() is deprecated and will be eventually removed. Please use 
>>> buildPluginWithGradle()". Is that actually accurate? Should we be using 
>>> Gradle builds by default now?
>>>  
>>>
>>
>> This just means that if you use Gradle to build your plugin, you should 
>> not be using buildPlugin() anymore, you should use buildPluginWithGradle() 
>> instead. Maven builds are still the normal and most supported method for 
>> building Jenkins plugins.
>>
>> -- 
>> Website: http://earl-of-code.com
>>
>> -- 
>> 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/CAPiUgVd%2BvoxjEASVCO30C9iobk2aDGp2fwZNWjvSj4P1X-uLyQ%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
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/fa6c7004-8e6a-4158-9bc1-eedea23cdb2f%40googlegroups.com.

Re: Jenkins plugin does not work when packaged as an hpi

[Jayalakshmi Nair]

Hi,

Thank you for the suggestion.

I looked into it. The jenkins.version in the pom is the same as the jenkins 
version to which the hpi is installed.
The problem still persists.

On Thursday, April 30, 2020 at 6:17:34 PM UTC+5:30, Jesse Glick wrote:
>
> On Thu, Apr 30, 2020 at 4:38 AM Jayalakshmi Nair 
> > wrote: 
> > We have a plugin which extends the Sectioned View and noticed that the 
> builds waiting in the queue are not displayed in Filtered build queue. This 
> was resolved by overriding the getItems() method in our plugin. 
> > The above changes works fine in the development environment (i.e. , 
> running using mvn hpi:run). 
> > But when we install the plugin to any version of Jenkins(packaged as 
> hpi), the above mentioned issue still exist. 
>
> Perhaps the `jenkins.version` in your POM is much older than what you 
> tried installing it in interactively. Try updating to a recent LTS 
> baseline. 
>

-- 
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/d5e96251-bc81-4284-b3b4-f2dbf9b1ef25%40googlegroups.com.

Re: ANN: Agent Docker images renaming on April 12-13

[Slide]

It might be better to start a new thread instead or reusing this one. FYI,
you should be using jenkins/inbound-agent instead of jenkins/jnlp-slave.
The latest will be Java 8, not Java 11.

On Mon, May 11, 2020 at 7:55 AM Jon Brohauge  wrote:

> Hi All,
>
> I've been mulling over my attempt to do a custom jenkins-agent for a few
> days now. Starting out by using the jenkinsci/jnlp-agent, and building
> stuff in on it from there. Creating my docker image is successful. Using
> the custom-agent in my ecs cluster works. Using it in my kubernetes
> cluster, not so much. I can see that the container spins up using "kubectl
> --namespace jenkins describe pods [custom-agent-instance]"
>
> From what I observe my custom-agent gets spun up alongside an obligatory
> "jenkins/jnlp-slave:4.0.1-1". AFAICT trying to do a simple "java -version"
> does not show the version of java that I have inside my own agent-image,
> but the version in the jnlp-slave image. I followed the excellent video
> tutorial by Marky Jackson (https://www.youtube.com/watch?v=h4hKSXjCqyI).
> I have even tried to do the same test "java -vertsion" with the
> jenkins/jnlp-slave:latest, which should show java 11. However same result
> as before. What am I doing wrong? Somehow pipeline does not get handed over
> to "my" image.
>
> Any help is appreciated
>
> Regards,
> 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 discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/667d4499-09b6-4bab-a8cc-85a3d61e5c46%40googlegroups.com
> 
> .
>


-- 
Website: http://earl-of-code.com

-- 
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/CAPiUgVfqYO2Mg0nEb4B_jkHN7U1Qh-4_%3Dz7OHmRjv-LL39WiMA%40mail.gmail.com.

Re: ANN: Agent Docker images renaming on April 12-13

[Jon Brohauge]

Hi All,

I've been mulling over my attempt to do a custom jenkins-agent for a few 
days now. Starting out by using the jenkinsci/jnlp-agent, and building 
stuff in on it from there. Creating my docker image is successful. Using 
the custom-agent in my ecs cluster works. Using it in my kubernetes 
cluster, not so much. I can see that the container spins up using "kubectl 
--namespace jenkins describe pods [custom-agent-instance]"

>From what I observe my custom-agent gets spun up alongside an obligatory 
"jenkins/jnlp-slave:4.0.1-1". AFAICT trying to do a simple "java -version" 
does not show the version of java that I have inside my own agent-image, 
but the version in the jnlp-slave image. I followed the excellent video 
tutorial by Marky Jackson (https://www.youtube.com/watch?v=h4hKSXjCqyI). I 
have even tried to do the same test "java -vertsion" with the 
jenkins/jnlp-slave:latest, which should show java 11. However same result 
as before. What am I doing wrong? Somehow pipeline does not get handed over 
to "my" image.

Any help is appreciated

Regards,
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/667d4499-09b6-4bab-a8cc-85a3d61e5c46%40googlegroups.com.

Re: How to add JaCoCo Jenkins plugin repo

[Jesse Glick]

On Sun, May 10, 2020 at 6:30 AM Ullrich Hafner  wrote:
> You need to write a custom Jenkinsfile.

FYI:

https://github.com/jenkins-infra/pipeline-library/pull/21

-- 
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/CANfRfr2EwZPPV4mpFw0mYTG6kL3u04WA-WvU%3D0iWeUHpiarvhg%40mail.gmail.com.

Re: How to add JaCoCo Jenkins plugin repo

[Ullrich Hafner]

> Am 11.05.2020 um 11:34 schrieb Shihaaz Buhary :
> 
> Do you mean that we can view the JaCoCo HTML reports in ci.jenkins.io 
>  itself?

Yes.

> If so, is there a sample Jenkinsfile that you can point me to?

I used that quite some time ago:
https://github.com/jenkinsci/analysis-model/blob/0332b1993edca1e6af9589b256f754dc5a3f2e71/Jenkinsfile
 


Now I create coverage reports with GitHub actions only. But it still should 
work. What you can do as well, take the current version
https://github.com/jenkinsci/analysis-model/blob/master/Jenkinsfile 

and add JaCoCo at the end (and adapt the maven options to invoke JaCoCo).


> 
> Thanks
> 
> On Sunday, May 10, 2020 at 4:00:16 PM UTC+5:30, Ullrich Hafner wrote:
> You need to write a custom Jenkinsfile. Then you also can add SpotBugs 
> reports, etc. 
> 
> 
>> Am 10.05.2020 um 09:58 schrieb Shihaaz Buhary >:
>> 
>> Hi All, 
>> 
>> I would like to add JaCoCo code coverage to my plugin repo. Is there a way 
>> that I can enable this in ci.jenkins.io  and view the 
>> HTML report? If not, what is the best or possible way that I can do this?
>> 
>> Thanks,
>> Shihaaz
>> 
>> -- 
>> 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/e0b4c9a1-b6ab-4bf2-be08-b3c69f6734d2%40googlegroups.com
>>  
>> .
> 
> 
> -- 
> 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/15e930f9-0303-480d-9101-2a11f1ea6ee3%40googlegroups.com
>  
> .

-- 
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/B11EA32B-B270-4038-B6CE-054B96439AF6%40gmail.com.

Re: How to add JaCoCo Jenkins plugin repo

[Shihaaz Buhary]

Do you mean that we can view the JaCoCo HTML reports in ci.jenkins.io itself? 
If so, is there a sample Jenkinsfile that you can point me to?

Thanks

On Sunday, May 10, 2020 at 4:00:16 PM UTC+5:30, Ullrich Hafner wrote:
>
> You need to write a custom Jenkinsfile. Then you also can add SpotBugs 
> reports, etc. 
>
>
> Am 10.05.2020 um 09:58 schrieb Shihaaz Buhary  >:
>
> Hi All, 
>
> I would like to add JaCoCo code coverage to my plugin repo. Is there a way 
> that I can enable this in ci.jenkins.io and view the HTML report? If not, 
> what is the best or possible way that I can do this?
>
> Thanks,
> Shihaaz
>
> -- 
> 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/e0b4c9a1-b6ab-4bf2-be08-b3c69f6734d2%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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/15e930f9-0303-480d-9101-2a11f1ea6ee3%40googlegroups.com.