date:20210510

FTR we created the new *#lfx-security-2-pilot-with-snyk* channel in the CDF 
Slack workspace so that all sides can sync-up in a chat if needed.
You can join the workspace by following the guidelines in 
https://www.jenkins.io/chat/#continuous-delivery-foundation
All interested contributors and maintainers are welcome!

On Wednesday, May 5, 2021 at 10:25:50 PM UTC+2 Oleg Nenashev wrote:

> UPD: The Jenkins Governance meeting approved official participation in the 
> Pilot project.
> Approved by: Ulli Hafner, Gavin Mogan, Ewelina Wilkosz, Daniel Beck, 
> Baptiste Mathus, Mark Waite (+ Olivier I'd guess)
> Thanks everyone for the feedback!
>
>
> On Wednesday, May 5, 2021 at 7:28:36 PM UTC+2 Oleg Nenashev wrote:
>
>> Hi all,
>>
>> Just a quick update, we will be setting up a shared Slack channel in the 
>> CDF workspace. Once it is ready, we can use it for conversations.
>> Pending ticket to the CDF: 
>> https://github.com/cdfoundation/foundation/issues/330 
>>
>> BR, Oleg
>>
>> On Tuesday, May 4, 2021 at 9:30:06 AM UTC+2 Oleg Nenashev wrote:
>>
>>> Hi Olivier,
>>>
>>> For experiments, it might make sense to register Jenkins Infrastructure 
>>> as the second organization. I do not anticipate major overlap between 
>>> configs taking different technology stacks.
>>> Once Snyk adds support for multiple GitHub orgs, we can explore our 
>>> options. M>> standard GitHub App integration anyway (see my response to Daniel)
>>>
>>> If you want to start with the Jenkins Infra org, I think you can do it 
>>> even now on LFX Security 1.x && standard GitHUb integration. Then it can be 
>>> migrated to 2x.
>>> Let the LFX Security team know if you want one to be created.
>>>
>>> Best regards,
>>> Oleg
>>>
>>>
>>> On Tue, May 4, 2021 at 8:46 AM 'Olblak' via Jenkins Developers <
>>> jenkin...@googlegroups.com> wrote:
>>>
 Hi Oleg,

 Thanks for driving this.
 Once we are allowed to have a second Github Organization, I would be 
 very interested to experiment with it for the jenkins-infra organization. 

 On Monday, 3 May 2021 at 22:24:44 UTC+2 Oleg Nenashev wrote:

> Thanks for the interest Daniel!
>
> >> Would you like to participate as a contributor?
> > What does this entail?
>
> That's a good question, to be seen. As a part of the pilot project we 
> will need:
>
>- Try out LFX Security 2.0 and configure it for some of our 
>projects
>- Explore options for filtering out false positives, find a 
>solution for the Jenkins project taking its scale and needs
>- Try out other features like license analysis
>- Document the implementation for other maintainers
>- Keep evaluation notes and share feedback with Snyk/LFX Security. 
>If we experience blockers, multiple iterations might be required
>
> Note from the discussion: It is unlikely that we will be able to use 
> the standard Snyk's GitHub integration via GitHub App. We will likely 
> need 
> to integrate scanning submissions into our Jenkins pipelines (there is a 
> Snyk plugin FTR) or to use GitHub actions. Reason - GitHub Integration 
> cannot handle custom Bills of Materials which will be supported by the 
> LFX 
> Security 2.0 API (actually, by the Snyk backend).
>
> > Re licenses -- Is this something we're actively looking at as well, 
> or rather secondary. FWIW I can think of these use cases: That it's 
> actually open source; that it's compatible (no MIT plugin bundling GPL 
> dependencies or similar weirdness); that it's all OSI approved per 
> governance document. Anything else?
>
> Yes, looks good to me. I would rather prefer to avoid some licenses 
> where compatibility is disputed, e.g. traditional AGPL concerns.
>
>
> On Monday, May 3, 2021 at 9:35:17 PM UTC+2 Daniel Beck wrote:
>
>> Thanks again for driving this, Oleg! 
>>
>>
>> > On 3. May 2021, at 19:14, Oleg Nenashev  
>> wrote: 
>> > 
>> > The proposal is to start the pilot from a small list of the 
>> repositories controlled by the pilot project participants: Jenkins core, 
>> its libraries, and some plugins from maintainers who are interested to 
>> participate in the pilot project. 
>> > 
>> > Call for feedback: 
>> > • Would you approve doing an official pilot project together with 
>> Snyk and LFX Security? 
>>
>> Yes, definitely. 
>>
>> > • Would you like to participate as a contributor? 
>>
>> What does this entail? 
>>
>> > • Would you like your plugin to participate in the pilot project? 
>>
>> Yes (although my plugins tend not to have interesting dependencies so 
>> it's probably not that interesting). 
>>
>>
>> Re private PRs and security process (minute 25-28 in the transcripts, 
>> again around 0:51) -- I don't really see a need to handle dependency 
>> updates in

Re: Proposal: Adopting Stapler as official Jenkins project

On Mon, May 10, 2021 at 2:04 PM Oleg Nenashev 
wrote:

> Other Stapler related personal repositories can be also moved to the
> jenkinsci org
>

Sure; do you know of any?

https://javadoc.jenkins.io/component/stapler/ includes Javadoc only for
> https://github.com/stapler/stapler
>

https://github.com/stapler/stapler/tree/master/core specifically. The other
modules do not expose useful Java-level APIs that plugin authors should use
that I know of.

Other Stapler repositories like
> https://github.com/stapler/maven-stapler-plugin are not included
>

I do not think there is any need to publish Javadoc for any other
miscellaneous component. If and when a need arises, it is simple to include.

-- 
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/CANfRfr1Yz39ELgJRKu7rOPzcowqkh7NwD0sMx--N6LNFJU70Kg%40mail.gmail.com.

Re: Proposal: "Friend Of Jenkins" Revamp

2021-05-10 Thread Mark Waite

+1 from me on the proposal as well

On Monday, May 10, 2021 at 5:20:02 AM UTC-6 timja...@gmail.com wrote:

> +1 to proposal
>
> On Mon, 10 May 2021 at 11:08, Oleg Nenashev  wrote:
>
>> Would appreciate any feedback in this thread from the community
>>
>> On Wednesday, May 5, 2021 at 9:58:50 AM UTC+2 Oleg Nenashev wrote:
>>
>>> Dear all,
>>>
>>> We’ve recently had a few discussions with the board and Daniel Beck 
>>> about the “Friend of Jenkins” plugin. This is a plugin referenced from 
>>> https://www.jenkins.io/donate: *“In showing our appreciation, we’ll 
>>> send out a special "friend of Jenkins" plugin to those who have donated at 
>>> least 25 USD / 25 EUR. This plugin adds a little icon in the footer 
>>> section, telling that you are a friend of Jenkins. You can install this to 
>>> your Jenkins to show off that you’ve helped us”*. De facto, we have not 
>>> been doing so in the recent years. There are a few problems associated with 
>>> the plugin.
>>>
>>> *First of all*, you can become a “Friend of Jenkins” only by donating 
>>> money. IMO it goes against open source values, we should equally appreciate 
>>> all kinds of contributions and avoid promoting money donations 
>>> specifically. *Secondly*, the plugin is private source at the moment. 
>>> It is weird to send a private source plugin to anyone, especially as 
>>> appreciation. *Thirdly*, the plugin is dated. It has not been updated 
>>> for a while, and it does not use modern build/test pipelines. For example 
>>> the code still targets Jenkins 1.396 as the build target. Even if the code 
>>> is tiny, it is not good to send such a questionable build to Jenkins users 
>>> and suggest its installation. *Last but not least*, sending private 
>>> builds in email is flawed on its own due to the risk of various social 
>>> engineering attacks.
>>>
>>> I suggest that we completely tear down the “Friend of Jenkins” program:
>>>
>>>- We remove sections about “Friend of Jenkins” from the Donations 
>>>page
>>>- Instead of sending the plugin, the Jenkins Governance Board will 
>>>focus on sending appreciation letters and recognizing donations through 
>>>Jenkins social media. It should help us to build relationships with 
>>> donors 
>>>and hopefully get them involved in the community.
>>>
>>>
>>> Later actions (no specific timeline):
>>>
>>>- We (as community) open source the plugin as the standard Jenkins 
>>>plugin on https://github.com/jenkinsci, update it to the modern 
>>>development pipelines.
>>>- We update the plugin to reference 
>>>https://www.jenkins.io/participate/ instead of donations.  We might 
>>>add “Donate” as a type of participation to the list 
>>>- We release the plugin as 2.0, without changing the artifact ID. 
>>>Any user of the older private source version, if any, will be able to 
>>>update via the update center. Any Jenkins user will be also able to 
>>> install 
>>>it via the plugin manager, no preconditions.
>>>- We reference the plugin from the install wizard suggestions (not 
>>>installed by default), and other places.
>>>
>>> There were also some discussions about building signed versions of the 
>>> plugin and somehow allowing to verify the “Friend of Jenkins” status. 
>>> Although I proposed it, now I do not think it is really needed. We can 
>>> discuss it for future iterations.
>>>
>>> Would appreciate any feedback, and I suggest discussing that at the next 
>>> Governance meeting.
>>>
>>> Best regards,
>>> Oleg Nenashev
>>> Jenkins Governance Board
>>>
>>> -- 
>> 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-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/790a8d83-e939-4e96-adbe-98ca24f266dfn%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/7ecbe41e-7882-4351-a346-4cb53ade8955n%40googlegroups.com.

Re: Proposal: Adopting Stapler as official Jenkins project

+1

On Mon, 10 May 2021 at 19:10, Basil Crow  wrote:

> +1 for normalizing Stapler as a standard Jenkins sub-project. Keeping
> it as an independent project complicates maintenance efforts and does
> not provide a strong benefit.
>
> --
> 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/CAFwNDjoM%3Dxfx_U_QU98T7kets4aOsgUauJOGva5TB5LY3E2NUQ%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/CAH-3Bie9o%3DK7StKmXdBB5ga6__4ZBD42Ys_Zr1vn%3DDJp3sOt1Q%40mail.gmail.com.

Re: Proposal: Adopting Stapler as official Jenkins project

2021-05-10 Thread Basil Crow

+1 for normalizing Stapler as a standard Jenkins sub-project. Keeping
it as an independent project complicates maintenance efforts and does
not provide a strong benefit.

-- 
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/CAFwNDjoM%3Dxfx_U_QU98T7kets4aOsgUauJOGva5TB5LY3E2NUQ%40mail.gmail.com.

Re: Proposal: "Friend Of Jenkins" Revamp

I have submitted https://github.com/jenkins-infra/jenkins.io/pull/4343 with 
text updates

On Monday, May 10, 2021 at 1:20:02 PM UTC+2 timja...@gmail.com wrote:

> +1 to proposal
>
> On Mon, 10 May 2021 at 11:08, Oleg Nenashev  wrote:
>
>> Would appreciate any feedback in this thread from the community
>>
>> On Wednesday, May 5, 2021 at 9:58:50 AM UTC+2 Oleg Nenashev wrote:
>>
>>> Dear all,
>>>
>>> We’ve recently had a few discussions with the board and Daniel Beck 
>>> about the “Friend of Jenkins” plugin. This is a plugin referenced from 
>>> https://www.jenkins.io/donate: *“In showing our appreciation, we’ll 
>>> send out a special "friend of Jenkins" plugin to those who have donated at 
>>> least 25 USD / 25 EUR. This plugin adds a little icon in the footer 
>>> section, telling that you are a friend of Jenkins. You can install this to 
>>> your Jenkins to show off that you’ve helped us”*. De facto, we have not 
>>> been doing so in the recent years. There are a few problems associated with 
>>> the plugin.
>>>
>>> *First of all*, you can become a “Friend of Jenkins” only by donating 
>>> money. IMO it goes against open source values, we should equally appreciate 
>>> all kinds of contributions and avoid promoting money donations 
>>> specifically. *Secondly*, the plugin is private source at the moment. 
>>> It is weird to send a private source plugin to anyone, especially as 
>>> appreciation. *Thirdly*, the plugin is dated. It has not been updated 
>>> for a while, and it does not use modern build/test pipelines. For example 
>>> the code still targets Jenkins 1.396 as the build target. Even if the code 
>>> is tiny, it is not good to send such a questionable build to Jenkins users 
>>> and suggest its installation. *Last but not least*, sending private 
>>> builds in email is flawed on its own due to the risk of various social 
>>> engineering attacks.
>>>
>>> I suggest that we completely tear down the “Friend of Jenkins” program:
>>>
>>>- We remove sections about “Friend of Jenkins” from the Donations 
>>>page
>>>- Instead of sending the plugin, the Jenkins Governance Board will 
>>>focus on sending appreciation letters and recognizing donations through 
>>>Jenkins social media. It should help us to build relationships with 
>>> donors 
>>>and hopefully get them involved in the community.
>>>
>>>
>>> Later actions (no specific timeline):
>>>
>>>- We (as community) open source the plugin as the standard Jenkins 
>>>plugin on https://github.com/jenkinsci, update it to the modern 
>>>development pipelines.
>>>- We update the plugin to reference 
>>>https://www.jenkins.io/participate/ instead of donations.  We might 
>>>add “Donate” as a type of participation to the list 
>>>- We release the plugin as 2.0, without changing the artifact ID. 
>>>Any user of the older private source version, if any, will be able to 
>>>update via the update center. Any Jenkins user will be also able to 
>>> install 
>>>it via the plugin manager, no preconditions.
>>>- We reference the plugin from the install wizard suggestions (not 
>>>installed by default), and other places.
>>>
>>> There were also some discussions about building signed versions of the 
>>> plugin and somehow allowing to verify the “Friend of Jenkins” status. 
>>> Although I proposed it, now I do not think it is really needed. We can 
>>> discuss it for future iterations.
>>>
>>> Would appreciate any feedback, and I suggest discussing that at the next 
>>> Governance meeting.
>>>
>>> Best regards,
>>> Oleg Nenashev
>>> Jenkins Governance Board
>>>
>>> -- 
>> 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-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/790a8d83-e939-4e96-adbe-98ca24f266dfn%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/9e2a7b93-9b5b-481c-b54a-07be39b7840dn%40googlegroups.com.

Re: Proposal: Evaluating Twitter as code with @memkins

I will go ahead and setup a PoC tomorrow if no negative feedback

On Monday, May 10, 2021 at 2:37:27 PM UTC+2 Mark Waite wrote:

> +1 from me as well.  Thanks for doing it
>
> On Mon, May 10, 2021 at 5:20 AM Tim Jacomb  wrote:
>
>> +1
>>
>> On Mon, 10 May 2021 at 11:57, Oleg Nenashev  wrote:
>>
>>> Dear all,
>>>
>>> Last week I created the new Jenkins-related Twitter account: 
>>> https://twitter.com/memkins. The goal of this channel is to repost 
>>> funny memes and comics about Jenkins, while delivering best practices to 
>>> end users. Although this channel will include more sarcasm and 
>>> self-criticism than the official channel, the plan is to keep it overall 
>>> positive w.r.t Jenkins. It will also remain within the Jenkins Code of 
>>> Conduct boundaries.
>>>
>>> In the Jenkins Advocacy and Outreach SIG we had many discussions about 
>>> adopting a social media as code approach so that we could simplify content 
>>> contributions and to simplify reviews. Currently we do it manually via 
>>> Tweetdeck and Gitter based content reviews, and the process is not that 
>>> productive. In the case of Twitter, there is a GitHub action for that: 
>>> https://github.com/gr2m/twitter-together . I briefly evaluated it for 
>>> personal use, but the value would be rather evaluating it in a shared 
>>> account. And it looks much more convenient to test it on Memkins instead of 
>>> the official Jenkins accounts.
>>>
>>> With permission of the community, I would like to do the following:
>>>
>>>- Create a jenkinsci/memkins GitHub repository
>>>- Create a GitHub action which would post Tweets to @memkins. 
>>>Effectively it means that, in addition to the current moderators, all 
>>>GitHub Org Admins will get access to the account
>>>- Evaluate and document the flow
>>>
>>> If the experiment goes well, we can later update the IRC bot (or use 
>>> another automation), to automate pull requests to the repository via a chat 
>>> command or a GitHUb App form. Then we will be able to apply the same to the 
>>> main @jenkinsci or other accounts if all goes well.
>>>
>>> Best regards,
>>> Oleg Nenashev
>>>
>>> -- 
>>> 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-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCYzYeVP-JPnPWXc9su8jFAP9AA2q56ifBhaaJZsnoZLw%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>> -- 
>>
> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Advocacy and Outreach SIG" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkins-advocacy-and-o...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkins-advocacy-and-outreach-sig/CAH-3BicYwOQeftNxTvRHaFHCbqNd3mQY9oKNowq_UBCyu74vmA%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/6894cfcb-2a11-467c-85be-e6b37dc07f64n%40googlegroups.com.

Re: Proposal: Adopting Stapler as official Jenkins project

Thanks Jesse! Would also appreciate feedback w.r.t "TBD: We move Stapler 
repositories to jenkinsci . If there are other related personal 
repositories, we move them as well".
Responded to the rest below

> other related personal repositories 
>> What does this mean? 

Did not finish the bullet, sorry. "Other Stapler related personal 
repositories can be also moved to the jenkinsci org"

> http://stapler.kohsuke.org/  is deprecated 
and replaced by a reference to the Jenkins sub-project page

Thanks!

> Javadoc for Stapler components is republished on javadoc.jenkins.io

https://javadoc.jenkins.io/component/stapler/ includes Javadoc only for 
https://github.com/stapler/stapler
Other Stapler repositories like 
https://github.com/stapler/maven-stapler-plugin are not included 
No, I do not know whether any other component is actually needed.

On Monday, May 10, 2021 at 6:41:36 PM UTC+2 Jesse Glick wrote:

> On Mon, May 10, 2021 at 12:06 PM Oleg Nenashev  
> wrote:
>
>>
>>- Stapler is adopted as a Jenkins sub-project, with explicit 
>>expectation that we do not encourage external use
>>
>> +1 
>
>>
>>- maybe even target replacing it by another active OSS project later 
>>if not mission impossible
>>
>> This is impossible, let us not waste time discussing it.
>
>>
>>- We move Stapler repositories to jenkinsci.
>>
>> +1 (see INFRA-2908 )
>
>>
>>- other related personal repositories
>>
>> What does this mean?
>
>>
>>- We archive all repositories which are no longer used by Jenkins.
>>
>> +1 
>
>>
>>- http://stapler.kohsuke.org/ is deprecated and replaced by a 
>>   reference to the Jenkins sub-project page
>>   - Javadoc for Stapler components is republished on 
>>   javadoc.jenkins.io
>>
>> Both already done.
>

-- 
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/d3287767-71b6-4e5a-b531-cbcf68a9f04en%40googlegroups.com.

Re: External logs storage for Pipeline/FreeStyle jobs

Yes, JEP-207 was abandoned after, ehm some reorg at my company. Great to 
see my former teammates commenting in this thread :D

JEP-207 was indeed abandoned, but there were pull requests submitted to the 
Jenkins core and reference implementations (see the JEP for links). We had 
some disagreements with Jesse on APIs, especially w.r.t splitting the Log 
Storage and the Log Browser extensions (I needed it for Logstash/ELK where 
there might be multiple browsing implementations). But overall the API work 
was ready for merge with @Beta annotations IMHO. Same goes to External Log 
Storage API plugin. Note that JEP-207 was designed not only for 
AbstractProject-alike jobs, but it also added foundations for external Task 
Logs which is also a good use-case for centralized log systems.

The work could be definitely finished. As Jesse said, the most complicated 
part would be ensuring JEP-207 and JEP-210 interoperability without 
performance loss. Also there would be a major merge conflict if we recover 
the old PR I'd guess.

If somebody is interested, I am interested to participate as much as my 
time allows. Spoiler alert: not so much

On Monday, May 10, 2021 at 5:36:34 PM UTC+2 Jesse Glick wrote:

> On Mon, May 10, 2021 at 11:11 AM kuisathaverat  
> wrote:
>
>> it [is] only for pipelines so I have taken a look at JEP-207: External 
>> Build Logging support in the Jenkins Core 
>>  
>> but it seems abandoned
>>
>
> Yes. Something like that could be resurrected if there is a need, with 
> https://javadoc.jenkins.io/plugin/workflow-api/org/jenkinsci/plugins/workflow/log/package-summary.html
>  
> reworked to use the core API (there are still some Pipeline-specific 
> aspects such as step delineation).
>
> I am personally less interested in supporting non-Pipeline builds as in 
> addressing the key architectural limitation of current JEP-210 
> implementations, which is that Stapler and thus core classes involved in 
> log handling use `long` as a cursor rather than an opaque token, making it 
> impossible to offer high-performance log rendering inside Jenkins 
> (“classic”, Blue Ocean, etc.) particularly for running builds.
>
> what is the best approach to implement a distributed log system for 
>> FreeStyle jobs (and others), a ConsoleLogFilter?
>>
>
> Several longstanding plugins are able to *mirror* (non-Pipeline) log 
> output to external systems. Without something like JEP-207 you cannot have 
> the external system be the source of truth: Jenkins will continue streaming 
> the log to a local file, and reading it from there.
>

-- 
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/453bf8e6-30b9-43ce-90c2-b4f4dc7d7f78n%40googlegroups.com.

Re: HTMLUnit DefaultCssErrorHandler

2021-05-10 Thread 'Gavin Mogan' via Jenkins Developers

I vaguely remember when I did the upgrade to htmlunit for crawler

that there was a flag to say what version of the browser to act as. I think
the default is like Firefox 4 or something. (
https://htmlunit.sourceforge.io/apidocs/com/gargoylesoftware/htmlunit/BrowserVersion.html
possibly?)
does the default value need to be updated somewhere?

Digging into it a bit, I'm seeing "BEST_SUPPORTED" at
https://github.com/jenkinsci/jenkins-test-harness/blob/e14c168c8a573d7da7bb3360bd85dc3a4852665a/src/main/java/org/jvnet/hudson/test/JenkinsRule.java#L2231
but I have no idea what that means.

https://github.com/HtmlUnit/htmlunit/blob/master/src/main/java/com/gargoylesoftware/htmlunit/BrowserVersion.java#L109-L119
seems to imply chrome 90 and chrome 90 should have full css variable
support, so something is wacky?

On Mon, May 10, 2021 at 8:24 AM Jesse Glick  wrote:

> On Mon, May 10, 2021 at 10:31 AM Michael Tughan  wrote:
>
>> I'm betting that it hasn't been updated for new CSS3 syntax
>>
>
> If so, it is worth checking if there is an HtmlUnit update
> 
> which would correct the problem; and if not, file an issue upstream.
>
> --
> 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/CANfRfr33yk7prBaNdUkDj%3D%3D6sn99DZmCUAg5AzW1xvdNRgJS0Q%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/CAG%3D_DuuiQTMOenY%3D0m9_cPscXziB6kDtJsnOYc6aiMa%3DL9eOkA%40mail.gmail.com.

Re: Proposal: Adopting Stapler as official Jenkins project

On Mon, May 10, 2021 at 12:06 PM Oleg Nenashev 
wrote:

>
>- Stapler is adopted as a Jenkins sub-project, with explicit
>expectation that we do not encourage external use
>
> +1

>
>- maybe even target replacing it by another active OSS project later
>if not mission impossible
>
> This is impossible, let us not waste time discussing it.

>
>- We move Stapler repositories to jenkinsci.
>
> +1 (see INFRA-2908 )

>
>- other related personal repositories
>
> What does this mean?

>
>- We archive all repositories which are no longer used by Jenkins.
>
> +1

>
>- http://stapler.kohsuke.org/ is deprecated and replaced by a
>   reference to the Jenkins sub-project page
>   - Javadoc for Stapler components is republished on
>   javadoc.jenkins.io
>
> Both already done.

-- 
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/CANfRfr1kFr0_4Qk0rRx__gV2OCcG9JEjVLhAX2TEArqtu3gZbg%40mail.gmail.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

FTR I started https://groups.google.com/g/jenkinsci-dev/c/1T3yDHl1nEQ . I 
have a partially-completed proposal for Stapler in my drafts, so I went 
ahead and started the discussion

On Monday, May 10, 2021 at 2:16:38 PM UTC+2 Jesse Glick wrote:

> On Fri, May 7, 2021 at 7:13 PM Oleg Nenashev  wrote:
>
>> should we go ahead and move the repository to the jenkinsci org?
>>
>
> Fine with me. We should probably move `stapler/stapler` itself 
> (INFRA-2908); we have already started publishing to the Jenkins Artifactory 
> rather than OSSRH. 
>

-- 
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/acd9f997-eb3e-471b-834b-ae1ceb82b49en%40googlegroups.com.

Proposal: Adopting Stapler as official Jenkins project

Hi all,

I would like to follow-up on the previous discussions about the future of
Stapler. De-facto Stapler is a legacy project widely used only in Jenkins
(Jenkins core and plugins, and the old account app). I'd guess there are
little to no external usages left.

Stapler currently resides in a separate GitHub org:
https://github.com/stapler/ . It consists of 25 repositories, some of them
seem to be fully abandoned and unused.

I would suggest the following:

- Stapler is adopted as a Jenkins sub-project, with explicit expectation
that we do not encourage external use (and maybe even target replacing it
by another active OSS project later if not mission impossible)
- TBD: We move Stapler repositories to jenkinsci . If there are other
related personal repositories, we move them as well
- We archive all repositories which are no longer used by Jenkins.
- Component Ownership
- The Jenkins Core team becomes the nominal owner of
https://github.com/stapler/stapler and other components included in
the Jenkins core
- Other permissions are retained, e.g. Denys Digtiar will remain the
maintainer of the Intellij IDEA Stapler plugin
- The Jenkins Code of Conduct applies to Stapler
- Infrastructure
- http://stapler.kohsuke.org/ is deprecated and replaced by a
reference to the Jenkins sub-project page
- Javadoc for Stapler components is republished on javadoc.jenkins.io

Would appreciate feedback from the community members and Stapler
maintainers.

Best regards,
Oleg Nenashev

--
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/CAPfivLDTZykM5UFpPSXwW2MwdgHqnXDv6at%3DjRzJmp6E4PpJeQ%40mail.gmail.com.

Re: External logs storage for Pipeline/FreeStyle jobs

On Mon, May 10, 2021 at 11:11 AM kuisathaverat 
wrote:

> it [is] only for pipelines so I have taken a look at JEP-207: External
> Build Logging support in the Jenkins Core
> 
> but it seems abandoned
>

Yes. Something like that could be resurrected if there is a need, with
https://javadoc.jenkins.io/plugin/workflow-api/org/jenkinsci/plugins/workflow/log/package-summary.html
reworked to use the core API (there are still some Pipeline-specific
aspects such as step delineation).

I am personally less interested in supporting non-Pipeline builds as in
addressing the key architectural limitation of current JEP-210
implementations, which is that Stapler and thus core classes involved in
log handling use `long` as a cursor rather than an opaque token, making it
impossible to offer high-performance log rendering inside Jenkins
(“classic”, Blue Ocean, etc.) particularly for running builds.

what is the best approach to implement a distributed log system for
> FreeStyle jobs (and others), a ConsoleLogFilter?
>

Several longstanding plugins are able to *mirror* (non-Pipeline) log output
to external systems. Without something like JEP-207 you cannot have the
external system be the source of truth: Jenkins will continue streaming the
log to a local file, and reading it from there.

-- 
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/CANfRfr127dWwhFG5-v83w%3D0EhpkJLmGqRaV1W4TbBjRxd4WzKw%40mail.gmail.com.

Re: HTMLUnit DefaultCssErrorHandler

On Mon, May 10, 2021 at 10:31 AM Michael Tughan  wrote:

> I'm betting that it hasn't been updated for new CSS3 syntax
>

If so, it is worth checking if there is an HtmlUnit update
 which
would correct the problem; and if not, file an issue upstream.

-- 
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/CANfRfr33yk7prBaNdUkDj%3D%3D6sn99DZmCUAg5AzW1xvdNRgJS0Q%40mail.gmail.com.

External logs storage for Pipeline/FreeStyle jobs

2021-05-10 Thread kuisathaverat

Hi,

I've started a plugin to send pipeline logs to an Elasticsearch instance
using the described API in JEP-210: External log storage for Pipeline

It is based on the example implementation pipeline-cloudwatch-logs-plugin

The thing is that it only for pipelines so I have taken a look at JEP-207:
External Build Logging support in the Jenkins Core

but it seems abandoned, or it is what I understand reading the last comment
on jenkins#3575

Is that right? if so what is the best approach to implement a distributed
log system for FreeStyle jobs (and others), a ConsoleLogFilter?

-- 
Un Saludo
Iván Fernández Calvo

-- 
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/CAKo5Qrr8Yi%2BOZiN5aNE305iZJe7MZDDY1fPxj1MUbHnVDeVnbg%40mail.gmail.com.

Re: Backporting has started and the RC is scheduled for 19th May

Then let's postpone it until .2 at least

On Mon, May 10, 2021 at 4:44 PM Basil Crow  wrote:

> On Mon, May 10, 2021 at 2:35 AM Oleg Nenashev 
> wrote:
> >
> > I wonder whether we should also create a Remoting 4.8 backport this
> time: https://github.com/jenkinsci/remoting/releases/tag/remoting-4.8
> > There are 2 bugfixes which seem important though we could also just
> embed 4.8 into the LTS line. THere is one performance RFE and one minor
> feature added, so just backporting the version looks safe enough
>
> #449 is off-by-default and anyway only applies to the Swarm client
> rather than the Jenkins controller. The other changes, while not
> regression fixes, seem safe to me. I don't feel strongly either way.
>
> --
> 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/TPQum9wHFVg/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/CAFwNDjqR22pncxWPsmBq3biGDZZWtHBoN2Bm%2B1qfbv%3DXY1WhEQ%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/CAPfivLCzaDuPMSo3VWCjQvQ35u7eyRuzwwetecsg-1xfWstNYQ%40mail.gmail.com.

Re: Backporting has started and the RC is scheduled for 19th May

2021-05-10 Thread Basil Crow

On Mon, May 10, 2021 at 2:35 AM Oleg Nenashev  wrote:
>
> I wonder whether we should also create a Remoting 4.8 backport this time: 
> https://github.com/jenkinsci/remoting/releases/tag/remoting-4.8
> There are 2 bugfixes which seem important though we could also just embed 4.8 
> into the LTS line. THere is one performance RFE and one minor feature added, 
> so just backporting the version looks safe enough

#449 is off-by-default and anyway only applies to the Swarm client
rather than the Jenkins controller. The other changes, while not
regression fixes, seem safe to me. I don't feel strongly either way.

-- 
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/CAFwNDjqR22pncxWPsmBq3biGDZZWtHBoN2Bm%2B1qfbv%3DXY1WhEQ%40mail.gmail.com.

Re: HTMLUnit DefaultCssErrorHandler

2021-05-10 Thread Michael Tughan

No, because they're not actually errors. It's complaining about the 
property definitions like "--font-family-sans". I'm betting that it hasn't 
been updated for new CSS3 syntax, especially around properties.

Michael

On Monday, May 10, 2021 at 8:15:01 a.m. UTC-4 Jesse Glick wrote:

> Rather than silencing the warnings, can the alleged errors be fixed in 
> core?
>

-- 
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/a95234d3-0934-4c37-9deb-323ea6350f04n%40googlegroups.com.

Re: Using JDK 11 instead of JDK 8 in default docker images

What metric would people consider?

0? Few new issues? From personal experience on Java 11 I have never hit the
above issues (apart from illegal reflective access log messages)

Query I used to look:
https://issues.jenkins.io/browse/JENKINS-64831?filter=22940&jql=labels%20in%20(java11-compatibility)%20and%20resolution%20is%20EMPTY

On Mon, 10 May 2021 at 13:31, Jesse Glick  wrote:

> On Sun, May 9, 2021 at 4:10 AM Tim Jacomb  wrote:
>
>> encourage existing users to migrate
>>
>
> Feels a bit premature when the list of `java11-compatibility` issues still
> includes bugs in core and widely used plugins.
>
> (The only ones I have personal experience with are JENKINS-61212
> , which should only
> affect users terminating TLS in Jenkins, rather than a reverse
> proxy/ingress which I suppose is more customary; and JENKINS-57139
>  which affects the GUI
> agent installers that would be lightly deprecated in JEP-230 but for now
> remain in core.)
>
> --
> 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/CANfRfr0w-YsTD3odTAJouMGG2QZLRpq85Q6ynp8pzFEk0vJgzg%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/CAH-3BidtYq8i3qtbTnVrcq6G-Qpi%3DZT3KYKL1bPg5t92uwLRCQ%40mail.gmail.com.

Re: Proposal: Evaluating Twitter as code with @memkins

2021-05-10 Thread Mark Waite

+1 from me as well.  Thanks for doing it

On Mon, May 10, 2021 at 5:20 AM Tim Jacomb  wrote:

> +1
>
> On Mon, 10 May 2021 at 11:57, Oleg Nenashev 
> wrote:
>
>> Dear all,
>>
>> Last week I created the new Jenkins-related Twitter account:
>> https://twitter.com/memkins. The goal of this channel is to repost funny
>> memes and comics about Jenkins, while delivering best practices to end
>> users. Although this channel will include more sarcasm and self-criticism
>> than the official channel, the plan is to keep it overall positive w.r.t
>> Jenkins. It will also remain within the Jenkins Code of Conduct boundaries.
>>
>> In the Jenkins Advocacy and Outreach SIG we had many discussions about
>> adopting a social media as code approach so that we could simplify content
>> contributions and to simplify reviews. Currently we do it manually via
>> Tweetdeck and Gitter based content reviews, and the process is not that
>> productive. In the case of Twitter, there is a GitHub action for that:
>> https://github.com/gr2m/twitter-together . I briefly evaluated it for
>> personal use, but the value would be rather evaluating it in a shared
>> account. And it looks much more convenient to test it on Memkins instead of
>> the official Jenkins accounts.
>>
>> With permission of the community, I would like to do the following:
>>
>>- Create a jenkinsci/memkins GitHub repository
>>- Create a GitHub action which would post Tweets to @memkins.
>>Effectively it means that, in addition to the current moderators, all
>>GitHub Org Admins will get access to the account
>>- Evaluate and document the flow
>>
>> If the experiment goes well, we can later update the IRC bot (or use
>> another automation), to automate pull requests to the repository via a chat
>> command or a GitHUb App form. Then we will be able to apply the same to the
>> main @jenkinsci or other accounts if all goes well.
>>
>> Best regards,
>> Oleg Nenashev
>>
>> --
>> 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/CAPfivLCYzYeVP-JPnPWXc9su8jFAP9AA2q56ifBhaaJZsnoZLw%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Advocacy and Outreach SIG" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkins-advocacy-and-outreach-sig+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkins-advocacy-and-outreach-sig/CAH-3BicYwOQeftNxTvRHaFHCbqNd3mQY9oKNowq_UBCyu74vmA%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/CAO49JtEuARo13OQ6%3DLG%2BA_QHraAfy0GF0OVu0wtUJdgbPTVPhw%40mail.gmail.com.

Re: Using JDK 11 instead of JDK 8 in default docker images

On Sun, May 9, 2021 at 4:10 AM Tim Jacomb  wrote:

> encourage existing users to migrate
>

Feels a bit premature when the list of `java11-compatibility` issues still
includes bugs in core and widely used plugins.

(The only ones I have personal experience with are JENKINS-61212
, which should only affect
users terminating TLS in Jenkins, rather than a reverse proxy/ingress which
I suppose is more customary; and JENKINS-57139
 which affects the GUI
agent installers that would be lightly deprecated in JEP-230 but for now
remain in core.)

-- 
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/CANfRfr0w-YsTD3odTAJouMGG2QZLRpq85Q6ynp8pzFEk0vJgzg%40mail.gmail.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

On Fri, May 7, 2021 at 7:13 PM Oleg Nenashev  wrote:

> should we go ahead and move the repository to the jenkinsci org?
>

Fine with me. We should probably move `stapler/stapler` itself
(INFRA-2908); we have already started publishing to the Jenkins Artifactory
rather than OSSRH.

-- 
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/CANfRfr1rC%2Btqc4O24HMgLQgeyZ%2BDgGHy%2BaLL-LOR5%3DGkZSU%3DHg%40mail.gmail.com.

Re: HTMLUnit DefaultCssErrorHandler

2021-05-10 Thread 'Cyrille Le Clerc' via Jenkins Developers

Rather than silencing the warnings, can the alleged errors be fixed in core?

-- 
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/CANfRfr0p_-C_MP8KxrOmerfarv0CvFuv81-E7mhSJ1mR203aYg%40mail.gmail.com.

Re: Plugins using removed Guava APIs

Hello,

I couldn't find the source code of the cloudfoundry-bosh-cli . This plugin 
can be ignored as it it completely outdated, the BOSH CLI it integrates 
with has been replaced a long time ago by a BOSH CLI v2.

Cyrille

On Sunday, May 9, 2021 at 9:40:34 PM UTC+2 m...@basilcrow.com wrote:

> I found that we can easily remove Guava usages from SSH Build Agents
> and Node Label Parameter as well:
>
> https://github.com/jenkinsci/ssh-slaves-plugin/pull/228
> https://github.com/jenkinsci/nodelabelparameter-plugin/pull/28
>

-- 
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/45a1a99e-4f17-44cd-b370-a351ddb7333en%40googlegroups.com.

Re: HTMLUnit DefaultCssErrorHandler

2021-05-10 Thread Daniel Beck

My PR specifically adapted the tests to a reorg of the core CSS. Note the
messages I ended up suppressing in my example were different ones. These
messages are new and look like they're from the color definitions. I don't
know this area well enough to confidently dismiss all warnings as
irrelevant.


On Mon, May 10, 2021 at 1:19 PM Tim Jacomb  wrote:

> I thought Daniel already did a PR to the test harness for this? He might
> have selectively turned things off rather than a full silence though
>
> https://github.com/jenkinsci/jenkins-test-harness/pull/275
>
>
> On Mon, 10 May 2021 at 10:47, Angélique Jard  wrote:
>
>> spam for me, but it could be silenced by default and enabled in specific
>> use case maybe ?
>>
>> On Monday, May 10, 2021 at 11:44:19 AM UTC+2 jn...@cloudbees.com wrote:
>>
>>> Hi all,
>>>
>>> The jenkins-test-harness uses the default HTMLUnit CSS Error handle
>>> which logs two  warning for every CSS error it encounters.
>>>
>>> Does anyone actually care about these errors?  I am about to file a PR
>>> to silence them, but thought someone may care and may have a use for them?
>>>
>>> For example the warnings seem to be coming from core jenkins css files:
>>>
>>>  0.006 [id=1451] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer:
>>> Running on http://localhost:34751/jenkins/
>>>0.170 [id=1464] INFO jenkins.InitReactorRunner$1#onAttained: Started
>>> initialization
>>>0.171 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: Listed
>>> all plugins
>>>0.376 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained:
>>> Prepared all plugins
>>>0.388 [id=1464] INFO jenkins.InitReactorRunner$1#onAttained: Started
>>> all plugins
>>>4.407 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained:
>>> Augmented all extensions
>>>4.445 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: System
>>> config loaded
>>>4.456 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: System
>>> config adapted
>>>4.456 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: Loaded
>>> all jobs
>>>4.457 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained:
>>> Configuration for all jobs updated
>>>4.475 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained:
>>> Completed initialization
>>>4.558 [wf-1620192393655 #1] Started
>>>4.558 [wf-1620192393655 #1] Running in Durability level:
>>> MAX_SURVIVABILITY
>>>4.658 [wf-1620192393655 #1] [Pipeline] Start of Pipeline
>>>4.658 [wf-1620192393655 #1] [policy] The following policy will be
>>> validated:
>>>4.658 [wf-1620192393655 #1]   Policy
>>> [f222cdd7-a217-4922-aa06-d1c52da71bb7] containing rules:
>>>4.658 [wf-1620192393655 #1] [Agent Timeout] with properties ["Max
>>> Timeout": "120 MINUTES"]
>>>4.809 [wf-1620192393655 #1] [Pipeline] stage
>>>4.859 [wf-1620192393655 #1] [Pipeline] { (NORMAL Stage)
>>>4.859 [wf-1620192393655 #1] [Pipeline] timeout
>>>4.860 [wf-1620192393655 #1] Timeout set to expire in 1 hr 0 min
>>>4.860 [wf-1620192393655 #1] [Pipeline] {
>>>4.860 [wf-1620192393655 #1] [Pipeline] input
>>>4.910 [wf-1620192393655 #1] Deploy to Production?
>>>4.910 [wf-1620192393655 #1] Proceed or Abort
>>>6.024 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS
>>> error: '
>>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>>> [11:3] Error in style rule. (Invalid token "-". Was expecting one of:
>>> , , , "}", ";", "*".)
>>>6.024 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS
>>> warning: '
>>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>>> [11:3] Ignoring the following declarations in this rule.
>>>6.029 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS
>>> error: '
>>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>>> [397:21] Error in expression. (Invalid token " ". Was expecting one of:
>>> , "inherit", , , , , , ,
>>> , , , , ,
>>> , , , , , ,
>>> , , , , ,
>>> , , , , "progid:".)
>>>6.030 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS
>>> error: '
>>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>>> [426:23] Error in expression. (Invalid token " ". Was expecting one of:
>>> , "inherit", , , , , , ,
>>> , , , , ,
>>> , , , , , ,
>>> , , , , ,
>>> , , , , "progid:".)
>>>6.039 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS
>>> error: '
>>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>>> [1550:17] Error in class selector. (Invalid token "only". Was expecting:
>>> .)
>>>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS
>>> warning: '
>>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>>> [1550:17] Ignoring the whole rule.
>>>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS
>>> error: '
>>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>>

Re: Proposal: Evaluating Twitter as code with @memkins

+1

On Mon, 10 May 2021 at 11:57, Oleg Nenashev  wrote:

> Dear all,
>
> Last week I created the new Jenkins-related Twitter account:
> https://twitter.com/memkins. The goal of this channel is to repost funny
> memes and comics about Jenkins, while delivering best practices to end
> users. Although this channel will include more sarcasm and self-criticism
> than the official channel, the plan is to keep it overall positive w.r.t
> Jenkins. It will also remain within the Jenkins Code of Conduct boundaries.
>
> In the Jenkins Advocacy and Outreach SIG we had many discussions about
> adopting a social media as code approach so that we could simplify content
> contributions and to simplify reviews. Currently we do it manually via
> Tweetdeck and Gitter based content reviews, and the process is not that
> productive. In the case of Twitter, there is a GitHub action for that:
> https://github.com/gr2m/twitter-together . I briefly evaluated it for
> personal use, but the value would be rather evaluating it in a shared
> account. And it looks much more convenient to test it on Memkins instead of
> the official Jenkins accounts.
>
> With permission of the community, I would like to do the following:
>
>- Create a jenkinsci/memkins GitHub repository
>- Create a GitHub action which would post Tweets to @memkins.
>Effectively it means that, in addition to the current moderators, all
>GitHub Org Admins will get access to the account
>- Evaluate and document the flow
>
> If the experiment goes well, we can later update the IRC bot (or use
> another automation), to automate pull requests to the repository via a chat
> command or a GitHUb App form. Then we will be able to apply the same to the
> main @jenkinsci or other accounts if all goes well.
>
> Best regards,
> Oleg Nenashev
>
> --
> 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/CAPfivLCYzYeVP-JPnPWXc9su8jFAP9AA2q56ifBhaaJZsnoZLw%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/CAH-3BicYwOQeftNxTvRHaFHCbqNd3mQY9oKNowq_UBCyu74vmA%40mail.gmail.com.

Re: Proposal: "Friend Of Jenkins" Revamp

+1 to proposal

On Mon, 10 May 2021 at 11:08, Oleg Nenashev  wrote:

> Would appreciate any feedback in this thread from the community
>
> On Wednesday, May 5, 2021 at 9:58:50 AM UTC+2 Oleg Nenashev wrote:
>
>> Dear all,
>>
>> We’ve recently had a few discussions with the board and Daniel Beck about
>> the “Friend of Jenkins” plugin. This is a plugin referenced from
>> https://www.jenkins.io/donate: *“In showing our appreciation, we’ll send
>> out a special "friend of Jenkins" plugin to those who have donated at least
>> 25 USD / 25 EUR. This plugin adds a little icon in the footer section,
>> telling that you are a friend of Jenkins. You can install this to your
>> Jenkins to show off that you’ve helped us”*. De facto, we have not been
>> doing so in the recent years. There are a few problems associated with the
>> plugin.
>>
>> *First of all*, you can become a “Friend of Jenkins” only by donating
>> money. IMO it goes against open source values, we should equally appreciate
>> all kinds of contributions and avoid promoting money donations
>> specifically. *Secondly*, the plugin is private source at the moment. It
>> is weird to send a private source plugin to anyone, especially as
>> appreciation. *Thirdly*, the plugin is dated. It has not been updated
>> for a while, and it does not use modern build/test pipelines. For example
>> the code still targets Jenkins 1.396 as the build target. Even if the code
>> is tiny, it is not good to send such a questionable build to Jenkins users
>> and suggest its installation. *Last but not least*, sending private
>> builds in email is flawed on its own due to the risk of various social
>> engineering attacks.
>>
>> I suggest that we completely tear down the “Friend of Jenkins” program:
>>
>>- We remove sections about “Friend of Jenkins” from the Donations page
>>- Instead of sending the plugin, the Jenkins Governance Board will
>>focus on sending appreciation letters and recognizing donations through
>>Jenkins social media. It should help us to build relationships with donors
>>and hopefully get them involved in the community.
>>
>>
>> Later actions (no specific timeline):
>>
>>- We (as community) open source the plugin as the standard Jenkins
>>plugin on https://github.com/jenkinsci, update it to the modern
>>development pipelines.
>>- We update the plugin to reference
>>https://www.jenkins.io/participate/ instead of donations.  We might
>>add “Donate” as a type of participation to the list
>>- We release the plugin as 2.0, without changing the artifact ID. Any
>>user of the older private source version, if any, will be able to update
>>via the update center. Any Jenkins user will be also able to install it 
>> via
>>the plugin manager, no preconditions.
>>- We reference the plugin from the install wizard suggestions (not
>>installed by default), and other places.
>>
>> There were also some discussions about building signed versions of the
>> plugin and somehow allowing to verify the “Friend of Jenkins” status.
>> Although I proposed it, now I do not think it is really needed. We can
>> discuss it for future iterations.
>>
>> Would appreciate any feedback, and I suggest discussing that at the next
>> Governance meeting.
>>
>> Best regards,
>> Oleg Nenashev
>> Jenkins Governance Board
>>
>> --
> 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/790a8d83-e939-4e96-adbe-98ca24f266dfn%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/CAH-3Bidi2tWKQWmBntQN79d7dTyLw5osAhr8L4A4gs9xPiL%3DXA%40mail.gmail.com.

Re: HTMLUnit DefaultCssErrorHandler

I thought Daniel already did a PR to the test harness for this? He might
have selectively turned things off rather than a full silence though

https://github.com/jenkinsci/jenkins-test-harness/pull/275


On Mon, 10 May 2021 at 10:47, Angélique Jard  wrote:

> spam for me, but it could be silenced by default and enabled in specific
> use case maybe ?
>
> On Monday, May 10, 2021 at 11:44:19 AM UTC+2 jn...@cloudbees.com wrote:
>
>> Hi all,
>>
>> The jenkins-test-harness uses the default HTMLUnit CSS Error handle which
>> logs two  warning for every CSS error it encounters.
>>
>> Does anyone actually care about these errors?  I am about to file a PR to
>> silence them, but thought someone may care and may have a use for them?
>>
>> For example the warnings seem to be coming from core jenkins css files:
>>
>>  0.006 [id=1451] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer:
>> Running on http://localhost:34751/jenkins/
>>0.170 [id=1464] INFO jenkins.InitReactorRunner$1#onAttained: Started
>> initialization
>>0.171 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: Listed
>> all plugins
>>0.376 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: Prepared
>> all plugins
>>0.388 [id=1464] INFO jenkins.InitReactorRunner$1#onAttained: Started
>> all plugins
>>4.407 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained:
>> Augmented all extensions
>>4.445 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: System
>> config loaded
>>4.456 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: System
>> config adapted
>>4.456 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: Loaded
>> all jobs
>>4.457 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained:
>> Configuration for all jobs updated
>>4.475 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained:
>> Completed initialization
>>4.558 [wf-1620192393655 #1] Started
>>4.558 [wf-1620192393655 #1] Running in Durability level:
>> MAX_SURVIVABILITY
>>4.658 [wf-1620192393655 #1] [Pipeline] Start of Pipeline
>>4.658 [wf-1620192393655 #1] [policy] The following policy will be
>> validated:
>>4.658 [wf-1620192393655 #1]   Policy
>> [f222cdd7-a217-4922-aa06-d1c52da71bb7] containing rules:
>>4.658 [wf-1620192393655 #1] [Agent Timeout] with properties ["Max
>> Timeout": "120 MINUTES"]
>>4.809 [wf-1620192393655 #1] [Pipeline] stage
>>4.859 [wf-1620192393655 #1] [Pipeline] { (NORMAL Stage)
>>4.859 [wf-1620192393655 #1] [Pipeline] timeout
>>4.860 [wf-1620192393655 #1] Timeout set to expire in 1 hr 0 min
>>4.860 [wf-1620192393655 #1] [Pipeline] {
>>4.860 [wf-1620192393655 #1] [Pipeline] input
>>4.910 [wf-1620192393655 #1] Deploy to Production?
>>4.910 [wf-1620192393655 #1] Proceed or Abort
>>6.024 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS
>> error: '
>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>> [11:3] Error in style rule. (Invalid token "-". Was expecting one of:
>> , , , "}", ";", "*".)
>>6.024 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS
>> warning: '
>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>> [11:3] Ignoring the following declarations in this rule.
>>6.029 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS
>> error: '
>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>> [397:21] Error in expression. (Invalid token " ". Was expecting one of:
>> , "inherit", , , , , , ,
>> , , , , ,
>> , , , , , ,
>> , , , , ,
>> , , , , "progid:".)
>>6.030 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS
>> error: '
>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>> [426:23] Error in expression. (Invalid token " ". Was expecting one of:
>> , "inherit", , , , , , ,
>> , , , , ,
>> , , , , , ,
>> , , , , ,
>> , , , , "progid:".)
>>6.039 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS
>> error: '
>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>> [1550:17] Error in class selector. (Invalid token "only". Was expecting:
>> .)
>>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS
>> warning: '
>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>> [1550:17] Ignoring the whole rule.
>>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS
>> error: '
>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>> [1569:33] Error in class selector. (Invalid token "only". Was expecting:
>> .)
>>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS
>> warning: '
>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>> [1569:33] Ignoring the whole rule.
>>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS
>> error: '
>> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css'
>> [1588:49] E

Proposal: Evaluating Twitter as code with @memkins

Dear all,

Last week I created the new Jenkins-related Twitter account:
https://twitter.com/memkins. The goal of this channel is to repost funny
memes and comics about Jenkins, while delivering best practices to end
users. Although this channel will include more sarcasm and self-criticism
than the official channel, the plan is to keep it overall positive w.r.t
Jenkins. It will also remain within the Jenkins Code of Conduct boundaries.

In the Jenkins Advocacy and Outreach SIG we had many discussions about
adopting a social media as code approach so that we could simplify content
contributions and to simplify reviews. Currently we do it manually via
Tweetdeck and Gitter based content reviews, and the process is not that
productive. In the case of Twitter, there is a GitHub action for that:
https://github.com/gr2m/twitter-together . I briefly evaluated it for
personal use, but the value would be rather evaluating it in a shared
account. And it looks much more convenient to test it on Memkins instead of
the official Jenkins accounts.

With permission of the community, I would like to do the following:

- Create a jenkinsci/memkins GitHub repository
- Create a GitHub action which would post Tweets to @memkins.
Effectively it means that, in addition to the current moderators, all
GitHub Org Admins will get access to the account
- Evaluate and document the flow

If the experiment goes well, we can later update the IRC bot (or use
another automation), to automate pull requests to the repository via a chat
command or a GitHUb App form. Then we will be able to apply the same to the
main @jenkinsci or other accounts if all goes well.

Best regards,
Oleg Nenashev

--
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/CAPfivLCYzYeVP-JPnPWXc9su8jFAP9AA2q56ifBhaaJZsnoZLw%40mail.gmail.com.

Re: Proposal: "Friend Of Jenkins" Revamp

Would appreciate any feedback in this thread from the community

On Wednesday, May 5, 2021 at 9:58:50 AM UTC+2 Oleg Nenashev wrote:

> Dear all,
>
> We’ve recently had a few discussions with the board and Daniel Beck about 
> the “Friend of Jenkins” plugin. This is a plugin referenced from 
> https://www.jenkins.io/donate: *“In showing our appreciation, we’ll send 
> out a special "friend of Jenkins" plugin to those who have donated at least 
> 25 USD / 25 EUR. This plugin adds a little icon in the footer section, 
> telling that you are a friend of Jenkins. You can install this to your 
> Jenkins to show off that you’ve helped us”*. De facto, we have not been 
> doing so in the recent years. There are a few problems associated with the 
> plugin.
>
> *First of all*, you can become a “Friend of Jenkins” only by donating 
> money. IMO it goes against open source values, we should equally appreciate 
> all kinds of contributions and avoid promoting money donations 
> specifically. *Secondly*, the plugin is private source at the moment. It 
> is weird to send a private source plugin to anyone, especially as 
> appreciation. *Thirdly*, the plugin is dated. It has not been updated for 
> a while, and it does not use modern build/test pipelines. For example the 
> code still targets Jenkins 1.396 as the build target. Even if the code is 
> tiny, it is not good to send such a questionable build to Jenkins users and 
> suggest its installation. *Last but not least*, sending private builds in 
> email is flawed on its own due to the risk of various social engineering 
> attacks.
>
> I suggest that we completely tear down the “Friend of Jenkins” program:
>
>- We remove sections about “Friend of Jenkins” from the Donations page
>- Instead of sending the plugin, the Jenkins Governance Board will 
>focus on sending appreciation letters and recognizing donations through 
>Jenkins social media. It should help us to build relationships with donors 
>and hopefully get them involved in the community.
>
>
> Later actions (no specific timeline):
>
>- We (as community) open source the plugin as the standard Jenkins 
>plugin on https://github.com/jenkinsci, update it to the modern 
>development pipelines.
>- We update the plugin to reference https://www.jenkins.io/participate/ 
>instead of donations.  We might add “Donate” as a type of participation to 
>the list 
>- We release the plugin as 2.0, without changing the artifact ID. Any 
>user of the older private source version, if any, will be able to update 
>via the update center. Any Jenkins user will be also able to install it 
> via 
>the plugin manager, no preconditions.
>- We reference the plugin from the install wizard suggestions (not 
>installed by default), and other places.
>
> There were also some discussions about building signed versions of the 
> plugin and somehow allowing to verify the “Friend of Jenkins” status. 
> Although I proposed it, now I do not think it is really needed. We can 
> discuss it for future iterations.
>
> Would appreciate any feedback, and I suggest discussing that at the next 
> Governance meeting.
>
> Best regards,
> Oleg Nenashev
> Jenkins Governance Board
>
>

-- 
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/790a8d83-e939-4e96-adbe-98ca24f266dfn%40googlegroups.com.

Re: HTMLUnit DefaultCssErrorHandler

2021-05-10 Thread Angélique Jard

spam for me, but it could be silenced by default and enabled in specific 
use case maybe ?

On Monday, May 10, 2021 at 11:44:19 AM UTC+2 jn...@cloudbees.com wrote:

> Hi all,
>
> The jenkins-test-harness uses the default HTMLUnit CSS Error handle which 
> logs two  warning for every CSS error it encounters.
>
> Does anyone actually care about these errors?  I am about to file a PR to 
> silence them, but thought someone may care and may have a use for them?
>
> For example the warnings seem to be coming from core jenkins css files:
>
>  0.006 [id=1451] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer: 
> Running on http://localhost:34751/jenkins/
>0.170 [id=1464] INFO jenkins.InitReactorRunner$1#onAttained: Started 
> initialization
>0.171 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: Listed 
> all plugins
>0.376 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: Prepared 
> all plugins
>0.388 [id=1464] INFO jenkins.InitReactorRunner$1#onAttained: Started 
> all plugins
>4.407 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: Augmented 
> all extensions
>4.445 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: System 
> config loaded
>4.456 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: System 
> config adapted
>4.456 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: Loaded 
> all jobs
>4.457 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: 
> Configuration for all jobs updated
>4.475 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: Completed 
> initialization
>4.558 [wf-1620192393655 #1] Started
>4.558 [wf-1620192393655 #1] Running in Durability level: 
> MAX_SURVIVABILITY
>4.658 [wf-1620192393655 #1] [Pipeline] Start of Pipeline
>4.658 [wf-1620192393655 #1] [policy] The following policy will be 
> validated:
>4.658 [wf-1620192393655 #1]   Policy 
> [f222cdd7-a217-4922-aa06-d1c52da71bb7] containing rules:
>4.658 [wf-1620192393655 #1] [Agent Timeout] with properties ["Max 
> Timeout": "120 MINUTES"]
>4.809 [wf-1620192393655 #1] [Pipeline] stage
>4.859 [wf-1620192393655 #1] [Pipeline] { (NORMAL Stage)
>4.859 [wf-1620192393655 #1] [Pipeline] timeout
>4.860 [wf-1620192393655 #1] Timeout set to expire in 1 hr 0 min
>4.860 [wf-1620192393655 #1] [Pipeline] {
>4.860 [wf-1620192393655 #1] [Pipeline] input
>4.910 [wf-1620192393655 #1] Deploy to Production?
>4.910 [wf-1620192393655 #1] Proceed or Abort
>6.024 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [11:3] Error in style rule. (Invalid token "-". Was expecting one of: 
> , , , "}", ";", "*".)
>6.024 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
> warning: '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [11:3] Ignoring the following declarations in this rule.
>6.029 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [397:21] Error in expression. (Invalid token " ". Was expecting one of: 
> , "inherit", , , , , , , 
> , , , , , 
> , , , , , , 
> , , , , , 
> , , , , "progid:".)
>6.030 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [426:23] Error in expression. (Invalid token " ". Was expecting one of: 
> , "inherit", , , , , , , 
> , , , , , 
> , , , , , , 
> , , , , , 
> , , , , "progid:".)
>6.039 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1550:17] Error in class selector. (Invalid token "only". Was expecting: 
> .)
>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
> warning: '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1550:17] Ignoring the whole rule.
>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1569:33] Error in class selector. (Invalid token "only". Was expecting: 
> .)
>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
> warning: '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1569:33] Ignoring the whole rule.
>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1588:49] Error in class selector. (Invalid token "only". Was expecting: 
> .)
>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
> warning: '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1588:49] Ignoring the whole rule.
>6.059 [id=1451] WARNING c.g.h.DefaultCssE

Re: HTMLUnit DefaultCssErrorHandler

+1 for silencing them by default. Would be nice to have a method in 
WebClient for those methods which really check the web layouts and hence 
care bout CSS

On Monday, May 10, 2021 at 11:44:19 AM UTC+2 jn...@cloudbees.com wrote:

> Hi all,
>
> The jenkins-test-harness uses the default HTMLUnit CSS Error handle which 
> logs two  warning for every CSS error it encounters.
>
> Does anyone actually care about these errors?  I am about to file a PR to 
> silence them, but thought someone may care and may have a use for them?
>
> For example the warnings seem to be coming from core jenkins css files:
>
>  0.006 [id=1451] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer: 
> Running on http://localhost:34751/jenkins/
>0.170 [id=1464] INFO jenkins.InitReactorRunner$1#onAttained: Started 
> initialization
>0.171 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: Listed 
> all plugins
>0.376 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: Prepared 
> all plugins
>0.388 [id=1464] INFO jenkins.InitReactorRunner$1#onAttained: Started 
> all plugins
>4.407 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: Augmented 
> all extensions
>4.445 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: System 
> config loaded
>4.456 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: System 
> config adapted
>4.456 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: Loaded 
> all jobs
>4.457 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: 
> Configuration for all jobs updated
>4.475 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: Completed 
> initialization
>4.558 [wf-1620192393655 #1] Started
>4.558 [wf-1620192393655 #1] Running in Durability level: 
> MAX_SURVIVABILITY
>4.658 [wf-1620192393655 #1] [Pipeline] Start of Pipeline
>4.658 [wf-1620192393655 #1] [policy] The following policy will be 
> validated:
>4.658 [wf-1620192393655 #1]   Policy 
> [f222cdd7-a217-4922-aa06-d1c52da71bb7] containing rules:
>4.658 [wf-1620192393655 #1] [Agent Timeout] with properties ["Max 
> Timeout": "120 MINUTES"]
>4.809 [wf-1620192393655 #1] [Pipeline] stage
>4.859 [wf-1620192393655 #1] [Pipeline] { (NORMAL Stage)
>4.859 [wf-1620192393655 #1] [Pipeline] timeout
>4.860 [wf-1620192393655 #1] Timeout set to expire in 1 hr 0 min
>4.860 [wf-1620192393655 #1] [Pipeline] {
>4.860 [wf-1620192393655 #1] [Pipeline] input
>4.910 [wf-1620192393655 #1] Deploy to Production?
>4.910 [wf-1620192393655 #1] Proceed or Abort
>6.024 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [11:3] Error in style rule. (Invalid token "-". Was expecting one of: 
> , , , "}", ";", "*".)
>6.024 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
> warning: '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [11:3] Ignoring the following declarations in this rule.
>6.029 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [397:21] Error in expression. (Invalid token " ". Was expecting one of: 
> , "inherit", , , , , , , 
> , , , , , 
> , , , , , , 
> , , , , , 
> , , , , "progid:".)
>6.030 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [426:23] Error in expression. (Invalid token " ". Was expecting one of: 
> , "inherit", , , , , , , 
> , , , , , 
> , , , , , , 
> , , , , , 
> , , , , "progid:".)
>6.039 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1550:17] Error in class selector. (Invalid token "only". Was expecting: 
> .)
>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
> warning: '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1550:17] Ignoring the whole rule.
>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1569:33] Error in class selector. (Invalid token "only". Was expecting: 
> .)
>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
> warning: '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1569:33] Ignoring the whole rule.
>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
> '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1588:49] Error in class selector. (Invalid token "only". Was expecting: 
> .)
>6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
> warning: '
> http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
> [1588:49] Ignor

Re: Backporting has started and the RC is scheduled for 19th May

2021-05-10 Thread Daniel Beck

On Mon, May 10, 2021 at 11:35 AM Oleg Nenashev 
wrote:

> Thanks to Raihaan for stepping up as the release lead for 2.289.1!
> So far the changes look good. We might have a few extra backports to do
> before the deadline, and everyone is welcome to expedite potential
> backports into the tomorrow's weekly.
>
> I wonder whether we should also create a Remoting 4.8 backport this time:
> https://github.com/jenkinsci/remoting/releases/tag/remoting-4.8
> There are 2 bugfixes which seem important though we could also just embed
> 4.8 into the LTS line. THere is one performance RFE and one minor feature
> added, so just backporting the version looks safe enough
>

Which bug fixes specifically would you consider important enough to
backport this early, creating a risk of regressions? Are they regression
fixes?

The exact timeline and interaction between changes is unclear to me, but
IIUC, a "late backport" created half of the mess with 2.277.x.

Folks who want the latest & greatest features and non-critical bug fixes
can always choose the weekly release line; LTS is for stability. As long as
each line isn't worse than the one before (~regressions), we shouldn't try
to force unproven changes into it last minute.

-- 
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/CAMo7PtKRzpmSr7NOOa87OF2pykAhpo2s8Yi7ieJJOABhPqPP-Q%40mail.gmail.com.

Applying JavaScript and CSS on f:select

2021-05-10 Thread Daniel Akua

Hi all,
In my plugin I have a  element with the multiple attribute 
(multi-select) that is changing according to another field.
My problem is that I want to apply JavaScript and CSS to it to make it look 
better than the standard multi-select element.

it currently looks like this:
[image: before.png]

and I want it to look something like this:
[image: after.PNG]

I have the required JS and CSS files and it is working on a normal  
element but not on .

How do I apply JavaScript and CSS on ?
Is there some guide on how to do it?

Tips or links will be appreciated.

-- 
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/5c068520-dace-47bf-beff-5fbdc7392038n%40googlegroups.com.

HTMLUnit DefaultCssErrorHandler

2021-05-10 Thread jn...@cloudbees.com

Hi all,

The jenkins-test-harness uses the default HTMLUnit CSS Error handle which 
logs two  warning for every CSS error it encounters.

Does anyone actually care about these errors?  I am about to file a PR to 
silence them, but thought someone may care and may have a use for them?

For example the warnings seem to be coming from core jenkins css files:

 0.006 [id=1451] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer: 
Running on http://localhost:34751/jenkins/
   0.170 [id=1464] INFO jenkins.InitReactorRunner$1#onAttained: Started 
initialization
   0.171 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: Listed all 
plugins
   0.376 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: Prepared 
all plugins
   0.388 [id=1464] INFO jenkins.InitReactorRunner$1#onAttained: Started all 
plugins
   4.407 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: Augmented 
all extensions
   4.445 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: System 
config loaded
   4.456 [id=1465] INFO jenkins.InitReactorRunner$1#onAttained: System 
config adapted
   4.456 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all 
jobs
   4.457 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: 
Configuration for all jobs updated
   4.475 [id=1466] INFO jenkins.InitReactorRunner$1#onAttained: Completed 
initialization
   4.558 [wf-1620192393655 #1] Started
   4.558 [wf-1620192393655 #1] Running in Durability level: 
MAX_SURVIVABILITY
   4.658 [wf-1620192393655 #1] [Pipeline] Start of Pipeline
   4.658 [wf-1620192393655 #1] [policy] The following policy will be 
validated:
   4.658 [wf-1620192393655 #1]   Policy 
[f222cdd7-a217-4922-aa06-d1c52da71bb7] containing rules:
   4.658 [wf-1620192393655 #1] [Agent Timeout] with properties ["Max 
Timeout": "120 MINUTES"]
   4.809 [wf-1620192393655 #1] [Pipeline] stage
   4.859 [wf-1620192393655 #1] [Pipeline] { (NORMAL Stage)
   4.859 [wf-1620192393655 #1] [Pipeline] timeout
   4.860 [wf-1620192393655 #1] Timeout set to expire in 1 hr 0 min
   4.860 [wf-1620192393655 #1] [Pipeline] {
   4.860 [wf-1620192393655 #1] [Pipeline] input
   4.910 [wf-1620192393655 #1] Deploy to Production?
   4.910 [wf-1620192393655 #1] Proceed or Abort
   6.024 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
'http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
[11:3] Error in style rule. (Invalid token "-". Was expecting one of: 
, , , "}", ";", "*".)
   6.024 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
warning: 
'http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
[11:3] Ignoring the following declarations in this rule.
   6.029 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
'http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
[397:21] Error in expression. (Invalid token " ". Was expecting one of: 
, "inherit", , , , , , , 
, , , , , 
, , , , , , 
, , , , , 
, , , , "progid:".)
   6.030 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
'http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
[426:23] Error in expression. (Invalid token " ". Was expecting one of: 
, "inherit", , , , , , , 
, , , , , 
, , , , , , 
, , , , , 
, , , , "progid:".)
   6.039 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
'http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
[1550:17] Error in class selector. (Invalid token "only". Was expecting: 
.)
   6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
warning: 
'http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
[1550:17] Ignoring the whole rule.
   6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
'http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
[1569:33] Error in class selector. (Invalid token "only". Was expecting: 
.)
   6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
warning: 
'http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
[1569:33] Ignoring the whole rule.
   6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
'http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
[1588:49] Error in class selector. (Invalid token "only". Was expecting: 
.)
   6.040 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#warning: CSS 
warning: 
'http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
[1588:49] Ignoring the whole rule.
   6.059 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
'http://localhost:34751/jenkins/static/5cda859e/jsbundles/base-styles-v2.css' 
[3322:26] Error in expression. (Invalid token " ". Was expecting one of: 
, "inherit", , , , , , , 
, , , , , 
, , , , , , 
, , , , , 
, , , , "progid:".)
   6.354 [id=1451] WARNING c.g.h.DefaultCssErrorHandler#error: CSS error: 
'http://localhost:34751/jenkins/stati

Re: Backporting has started and the RC is scheduled for 19th May