Jenkins 2.217 out-of-order release post-mortem

[Oleg Nenashev]

Hi all,

Today we had an out-of-order release of Jenkins 2.217
. This release fixes the major
regression in localization files (JENKINS-60822
), and it also includes
the extension finder regression fix (JENKINS-60816
). Thanks a lot to Jon
Brohauge and Jesse Glick for the fixes!

You may have noticed that the release includes a number of other changes
including the beta Websocket support and a major rework of the JavaScript
packaging (now we use Webpack!). Basically we released all the changes
integrated into the master branch. It is not a common approach for out of
order releases when we usually release regression fixes.I would like to
explain the reasons:

   - There might be a security release on Jan 29th (TBA by the security
   team if it happens), usually such releases target .2 LTS which is expected
   to land on that date. We want to have a stable Weekly release by this time
   - There were important changes like Websocket Beta support in Remoting
   (JEP-222), and we would rather want to get some user feedback before the
   next LTS baseline selection on Feb 26th
   - There is FOSDEM on Feb 01-02. Daniel Beck, Mark Waite and me will be
   traveling, And the next common weekly dates (Jan 26 and Feb 02) are not the
   best time for major changes. Delaying releases till Feb 09 drastically
   reduces the window before the new LTS baseline selection
   - Last but not least, the changes were already in master and set
   expectations about a soon release. It is on me, because over the past
   months I switched from doing merges on Thursday/Friday to a more CI-alike
   approach with merging changes after getting sufficient reviews and 24hrs
   merge timeout. It caused mis-alignment with the security release process
   which expected merges later on the week/

Given all these factors, I asked Kohsuke to release a standard weekly ahead
of the schedule. It will give us enough time to react if any new
regressions happen. The release looks good so far! I will also make sure to
document the current weekly integration process and to follow-up on
aligning it with the security release. Since we onboard more maintainers to
the Jenkins core, we need to move many established practices to the
documented form.

I also suggest skipping the weekly on Jan 26 or at least minimizing the
scope of the changes to low-risk changes and improvements. If you have
write access to the Jenkins core repo, I kindly ask to be careful with
merges. JENKINS-57888  is
one of the fixes I would consider for it, but the PR is yet to be
submitted. If you see any other changes which should land in the weekly,
let's discuss them in this thread.

Sorry for any inconvenience,
Oleg

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBoSGw1ZiV5YLZaD-bdZw7A%3DJUQzjRscnDi-N%2BD9fe0uQ%40mail.gmail.com.

CDF Annual report + how to get involved

[Tracy Miranda]

Hi all,

CD Foundation has just published its first annual report
https://cd.foundation/annual-report-2019/, please take a look.

Also here's a post listing some ways to get involved with CDF
https://cd.foundation/blog/2020/01/10/we-can-do-it-get-involved-in-2020/

We all continue to find ways to work better together and communicate well.
(In general the cd.foundation blog and @cdeliveryfdn twitter are improving
massively). Please always feel free to reach out if you have
questions/comments/suggestions.

Regards,
Tracy

-- 
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/CACTaz6rMUTtJtXDSeU7w-vxe4Jgg-Kq6zfFcBW2b1R%2BzFqmNpA%40mail.gmail.com.

Re: JIRA Sign Up Issues

[Tim Jacomb]

p.s. thanks to all involved,

Oleg, olblak, halkeye, tyler and daniel and anyone I missed :)

On Thu, 23 Jan 2020 at 20:24, Tim Jacomb  wrote:

> Hi David
>
> That should be fixed now (I was able to create an account after deploying
> the fix)
>
> Thanks
> Tim
>
> On Wed, 22 Jan 2020 at 16:35, Olblak  wrote:
>
>> Hi David,
>>
>> Thanks for reporting this, It seems the problem is not gone.
>> I give it another look
>>
>>
>> ---
>> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
>> ---
>>
>>
>> On Wed, Jan 22, 2020, at 3:53 PM, Marky Jackson wrote:
>>
>> Currently there is an issues being worked on with LDAP
>>
>> On Jan 22, 2020, at 1:33 AM, David Hodgkinson <
>> david.hodgkin...@outplay.com> wrote:
>>
>> Hi there,
>>
>> When attempting to sign up for an account here:
>> https://accounts.jenkins.io/signup in order to open a bug report with a
>> plugin I get the following error:
>>
>> HTTP ERROR 500
>>
>> Problem accessing /doSignup. Reason:
>>
>> Server Error
>>
>>
>> Caused by:
>>
>> javax.servlet.ServletException: javax.servlet.ServletException: 
>> javax.naming.NoPermissionException: [LDAP: error code 50 - no write access 
>> to parent]; remaining name 'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
>>  at 
>> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
>>  at 
>> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
>>  at org.eclipse.jetty.server.Server.handle(Server.java:503)
>>  at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364)
>>  at 
>> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)
>>  at 
>> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
>>  at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
>>  at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)
>>  at 
>> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
>>  at 
>> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
>>  at 
>> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
>>  at 
>> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
>>  at 
>> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
>>  at 
>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
>>  at 
>> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
>>  at java.lang.Thread.run(Thread.java:748)
>> Caused by: javax.servlet.ServletException: 
>> javax.naming.NoPermissionException: [LDAP: error code 50 - no write access 
>> to parent]; remaining name 'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
>>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:784)
>>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864)
>>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)
>>  at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>>  at 
>> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:857)
>>  at 
>> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
>>  at 
>> org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:215)
>>  at 
>> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
>>  at 
>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)
>>  at 
>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
>>  at 
>> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>>  at 
>> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
>>  at 
>> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
>>  at 
>> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
>>  at 
>> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
>>  at 
>> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)
>>  at 
>> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
>>  at 
>> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)
>>  at 
>> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)
>>  at 
>> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
>>  at 
>> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242)
>>  at 
>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
>>  at 
>> 

Re: JIRA Sign Up Issues

[Tim Jacomb]

Hi David

That should be fixed now (I was able to create an account after deploying
the fix)

Thanks
Tim

On Wed, 22 Jan 2020 at 16:35, Olblak  wrote:

> Hi David,
>
> Thanks for reporting this, It seems the problem is not gone.
> I give it another look
>
>
> ---
> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
>
>
> On Wed, Jan 22, 2020, at 3:53 PM, Marky Jackson wrote:
>
> Currently there is an issues being worked on with LDAP
>
> On Jan 22, 2020, at 1:33 AM, David Hodgkinson <
> david.hodgkin...@outplay.com> wrote:
>
> Hi there,
>
> When attempting to sign up for an account here:
> https://accounts.jenkins.io/signup in order to open a bug report with a
> plugin I get the following error:
>
> HTTP ERROR 500
>
> Problem accessing /doSignup. Reason:
>
> Server Error
>
>
> Caused by:
>
> javax.servlet.ServletException: javax.servlet.ServletException: 
> javax.naming.NoPermissionException: [LDAP: error code 50 - no write access to 
> parent]; remaining name 'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
>   at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
>   at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
>   at org.eclipse.jetty.server.Server.handle(Server.java:503)
>   at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364)
>   at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)
>   at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
>   at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
>   at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)
>   at 
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
>   at 
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
>   at 
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
>   at 
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
>   at 
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.servlet.ServletException: 
> javax.naming.NoPermissionException: [LDAP: error code 50 - no write access to 
> parent]; remaining name 'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
>   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:784)
>   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864)
>   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)
>   at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:857)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
>   at 
> org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:215)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>   at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
>   at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220)
>   at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
>   ... 15 more
> Caused by: 

Re: What is the best approach for mutually exclusive permissions - re: proposed Jenkins.CONFIGURE and Jenkins.SYSTEM_READ permissions

[Tim Jacomb]

(replies inline)



On Wed, 22 Jan 2020 at 01:24, Michael Cirioli 
wrote:

> (moving this discussion from https://github.com/jenkinsci/jep/pull/261 in
> order to have more visibility)
>
>- Both proposals expect plugins to override getRequiredPermission() in
>order to determine what should be shown to a user.  The intention of
>JEP- is that _most_ items would be shown (read-only) to a user,   This
>will potentially create a conflict with JEP-223, as a user may be shown
>things that can be changed by a user with Jenkins.CONFIGURE, but the
>changes may not be persisted because of the Jenkins.SYSTEM_READ changes.
>- If a user has both Jenkins.CONFIGURE and Jenkins.SYSTEM_READ, should
>they be able to view some things they can't configure, and being able to
>change some things that a user who only has Jenkins.SYSTEM_READ would
>normally only be able to view?
>
> I don't currently have a proposal on how to best address this, but I do
> have some ideas
>
>- Provide a mean for permissions to specify precedence (ie. CONFIGURE
>is less restrictive than SYSTEM_READ).  This is different than the current
>*implies(...)* because an administrator may not want a user with the
>CONFIGURE permission to automatically also have SYSTEM_READ
>
> I think that configure should just be above system read, but I don't know
how that would affect the UX of CONFIGURE

>
>- Add logic to the matrix-auth plugin such that some permission types
>are mutually exclusive.  ie. if you grant CONFIGURE, you can't also grant
>SYSTEM_READ.
>
> Hopefully unneeded

>
>- Allow getRequiredPermission() to return a list of permissions, and
>tailor the user experience for any given plugin with custom logic.  This
>may be more error prone to maintain, and would need to be well thought out
>enough so that any plugins that are unaware of the new permissions behave
>in a predictable way.
>
> Another thought I had was updating the jelly tags to allow to take an
array, and add a method called 'hasAnyPermission', which would at least
solve the view part

> Although the above thoughts are focused on the two new permissions
> currently being proposed, an ideal solution should support any additional
> permissions that may find their way into Jenkins in the future.
>
> --
> 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/1088605f-a0fc-460b-8a44-7f07a4eb7b2b%40googlegroups.com
> 
> .


On Wed, 22 Jan 2020 at 15:28, Jesse Glick  wrote:

> On Tue, Jan 21, 2020 at 8:24 PM Michael Cirioli 
> wrote:
> > Consider the case where a user has both Jenkins.CONFIGURE and
> Jenkins.SYSTEM_READ - what would the expected experience be?
> >
> > ..a user may be shown things that can be changed by a user with
> Jenkins.CONFIGURE, but the changes may not be persisted because of the
> Jenkins.SYSTEM_READ changes.
>
> If you split parts of the `/configure` page into an `/administer`
> page, rather than conditionally hiding them, then I think this could
> be solved in a different way that feels more in line with existing
> patterns:
>

I'm not sure this would work well for read only support, what items on the
existing configure page would you not want to expose?

>
> · If you have `ADMINISTER`, `/administer` has a *Save* (and *Apply*)
> button. Else, if you have `SYSTEM_READ`, it does not. If you have
> neither, it cannot be displayed at all.
> · If you have `CONFIGURE`, `/configure` has *Save*. If you have
> `VIEW_CONFIGURATION` (at global scope?), it does not. If you have
> neither, it cannot be displayed at all.
>
> an ideal solution should support any additional permissions that may find
> their way into Jenkins in the future
>
> Do we really want to be adding complex new permission options? The
> Jenkins permission system is way too complex as it stands, making for
> a poor UX, and as for Jenkins developers, I at least can barely keep
> the intended behavior straight in my head. Many advanced use cases
> would be better handled via `configuration-as-code` plus other
> tooling, processes, or policies (GitHub’s `CODEOWNERS`, for example).
>
>
Absolutely agree with handling configuration via `configuration-as-code` or
other tools, but I do think we're missing a lot of information that is
useful to users
to either:
1. contribute to the plugins / configuration of their instance.
2. debug why their build has an issue
3. debug / solve an issue faster with why their agent isn't starting (cloud
logs, agent startup logs etc)

Just thinking of ci.jenkins.io if some of the information above 

JEPs & BDFL ~ KK

[Jesse Glick]

Shall

https://github.com/jenkinsci/jep/tree/master/jep/1#bdfl

be amended somehow, to not assume KK has time to get involved? For
example to cut out the BDFL layer between JEP editors/reviewers and
the governance meeting? Also

https://github.com/jenkinsci/jep/tree/master/jep/9#specification

As a practical matter,

https://github.com/jenkinsci/jep/tree/master/jep/1#jep-review

has never been followed very consistently in my experience;
implementations get merged and released following regular hosting
and/or code review processes, while the JEP is still officially a
“draft”, and the “accepted” and “final” phases are skipped or a
formality. Maybe it is time for a streamlined process.

-- 
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/CANfRfr3vvd_MN5YBd%2B4bz%3DDZXEYZ-Brz6TUggpUgkbc7SBnpLQ%40mail.gmail.com.

Kohsuke's next chapter

[Kohsuke Kawaguchi]

Hi folks,

2020 is going to be a year of change for me. I just posted this
 to explain
what that means.

The past few years saw a rise of the new wave of leaders. So I'm making
this move with peace knowing that this project is in good hands

It was a true joy and pleasure to see this project grow over the years. I
met so many people because of this, many of them became my lifelong
friends. It's not an overstatement to say it defined a key part of my life.
Thank you for being a part of that journey, and looking forward to more
awesome things that come out of this project in the future.

Cheers!
-- 
Kohsuke Kawaguchi

-- 
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/CAN4CQ4ypLEGkxW6Uq9pbwsRjtcfPWjDk4HvBr4V1UKOZP%3DOj%2BQ%40mail.gmail.com.

Re: Dash / DevDocs docset for Jenkins

[Chris Kilding]

1. Job DSL is not part of Jenkins core so it would have a separate docset.
2. When we have a Jenkins server to hand we do generally try to use the 
Pipeline syntax / snippet generator. But sometimes we’re dealing with Jenkins 
servers that may be behind firewalls - or fixing non-functional servers - such 
that we can’t use the interactive documentation. Lots of developers also just 
don’t know about the interactive docs. As a result we still often use the 
static pipeline docs.

Chris

On Wed, 22 Jan 2020, at 6:01 PM, Jesse Glick wrote:
> On Wed, Jan 22, 2020 at 10:43 AM Chris Kilding
>  wrote:
> > Jenkins admins in my company utilise the Pipeline DSL reference and the 
> > JobDSL reference quite heavily - these are the things we’d most like to 
> > have in an offline docset.
> 
> Not sure offhand about `job-dsl`, but the Pipeline DSL is better
> referenced within the product itself, e.g.
> 
> https://ci.jenkins.io/pipeline-syntax/
> 
> which takes into account the precise versions of installed plugins,
> and gives much more information than the static HTML could.
> 
> -- 
> 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/CANfRfr3aK%2BPPwadfPpDKHHyFLY_F5gqKM%3DiBus9VKyH2U5n3HQ%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/a73741b8-8ad3-4b98-9c06-bd82e6cb75f3%40www.fastmail.com.

Re: Support List on jenkins.io?

[Tim Jacomb]

Why not setup required reviews?
There can be a small group of people who can bypass if necessary but most
people will need review

On Thu, 23 Jan 2020 at 11:12, Oleg Nenashev  wrote:

> Code Owners does not prevent merges by other contributors with Write
> permissions. We could combine CODEOWNERS with required reviews
> ,
> but it will apply to the entire Jenkins repository.
> I am not sure this is what we want, but happy to discuss it. Setting up
> permissions on the repo level is easier that wrangling with a new repo and
> the delivery pipeline patches
>
>
> On Thu, Jan 23, 2020 at 12:07 PM Tim Jacomb  wrote:
>
>> Is there a problem with using code owners for those files?
>>
>> On Thu, 23 Jan 2020 at 11:05, Oleg Nenashev 
>> wrote:
>>
>>> Hi all,
>>>
>>> Thanks to everyone involved in this discussion. I would also like to
>>> move the page and to improve its look Moving the Commercial
>>> Support 
>>> and Approved Trademark Usage
>>> 
>>> pages is in my backlog for Wiki migration. This pages are not easy to
>>> migrate IMO, because jenkins.io grants a wide access for managing these
>>> pages (Copy Editors, SIG leaders, GSoC team, etc.). Such access is supposed
>>> to be restricted IMO, especially for the trademarks page. Access in Wiki
>>> was also restricted at some point.
>>>
>>> My plan for these pages is/was to...
>>>
>>>- Create a new public repository within Jenkins Infra for the
>>>sensitive content. Write permissions will be restricted to the Jenkins
>>>Infra team and to the Jenkins Board
>>>- Repository will include sensitive content, including Commercial
>>>Support, Trademarks, and maybe Governance docs in the future (once under
>>>https://jenkins.io/project/).
>>>- For Commercial Support and Approved Trademarks we will use
>>>separate Asciidoc pages for each entry.
>>>- jenkins.io builder will pull this resource and include pages into
>>>jenkins.io, similar to how it happens with currently generated
>>>content
>>>
>>> Would appreciate feedback about such process.
>>>
>>> P.S: I will make sure to create a JIRA entry for it if someone wants to
>>> contribute
>>>
>>>
>>> On Thursday, January 23, 2020 at 6:22:29 AM UTC+1, Marky Jackson wrote:

 I like the idea of waiting for the advocacy meeting but that doesn’t
 mean we can’t get started on a WIP pr

 > On Jan 22, 2020, at 9:21 PM, 'Gavin Mogan' via Jenkins Developers <
 jenkin...@googlegroups.com> wrote:
 >

>>> --
>>> 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/6cc34bcb-d4b6-4f5a-a293-8c8b6f03356e%40googlegroups.com
>>> 
>>> .
>>>
>> --
>>
> 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/vjLgQtpz06Y/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/CAH-3BidZWKWSGL3xAbuGhkHtp02JjvFE0ze9SLag5dNuEgZ-OA%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/CAPfivLB_059-YyxN%3DP-RNPm48euCLYk61oUJDv_aMAyOkcuyMw%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-3Bifo%2BRub_7DSzO5-DtXUMAuCkpEbFDQnuFL9Gv4-kj-f9g%40mail.gmail.com.

ANN: Moving Event/JAM discussions to Advocacy SIG channels

[Oleg Nenashev]

Dear all,

As it was agreed at the Jan 15th Jenkins Governance Meeting (discussion in
the dev list
),
we will be moving Jenkins-related event and meetup conversations to
Advocacy
SIG  and Continuous
Delivery Foundation channels. We plan to archive the Jenkins Area Meetup
mailing list  and
Events mailing lists (jenkins-events
,
jenkins-fosdem ,
jenkins-scale ).
The ETA is to be defined, but please consider this channels as deprecated.

For Jenkins-related discussions please use the Advocacy SIG
resources. Topic examples: Jenkins Online Meetup, help with promoting
events/blogs, discussing events and conferences (FOSDEM/SCaLE), looking for
speakers, etc. SIG members will be happy to help. Quick links:

   - Mailing list
   
   - Gitter chat 
   - Regular SIG meetings
   


For Jenkins X events please use Jenkins X Community channels
. For meetup.com operations (creation of
meetup pages, moving meetups to CDF, etc.), please use the CDF CI/CD meetup
channels: Documentation on GitHub ,
#meetups channel in the CDF Slack (documentation / signup links
).

If you have any questions, please reach out to us in the AdvocacyOutreach
SIG chat or mailing list. Also see the WEBSITE-713
 EPIC to get more info
about the ongoing Jenkins Area Meetup program update. We will be happy to
get more feedback, and we encourage everyone to organize Jenkins events in
their cities!

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/CAPfivLDqSF988M18eaQJ2j%3D-o8govRYQm7y5W5pC%2BQv6Bsk4jA%40mail.gmail.com.

Re: Support List on jenkins.io?

[Oleg Nenashev]

Code Owners does not prevent merges by other contributors with Write
permissions. We could combine CODEOWNERS with required reviews
,
but it will apply to the entire Jenkins repository.
I am not sure this is what we want, but happy to discuss it. Setting up
permissions on the repo level is easier that wrangling with a new repo and
the delivery pipeline patches


On Thu, Jan 23, 2020 at 12:07 PM Tim Jacomb  wrote:

> Is there a problem with using code owners for those files?
>
> On Thu, 23 Jan 2020 at 11:05, Oleg Nenashev 
> wrote:
>
>> Hi all,
>>
>> Thanks to everyone involved in this discussion. I would also like to move
>> the page and to improve its look Moving the Commercial Support
>>  and Approved
>> Trademark Usage
>>  pages
>> is in my backlog for Wiki migration. This pages are not easy to migrate
>> IMO, because jenkins.io grants a wide access for managing these pages
>> (Copy Editors, SIG leaders, GSoC team, etc.). Such access is supposed to be
>> restricted IMO, especially for the trademarks page. Access in Wiki was also
>> restricted at some point.
>>
>> My plan for these pages is/was to...
>>
>>- Create a new public repository within Jenkins Infra for the
>>sensitive content. Write permissions will be restricted to the Jenkins
>>Infra team and to the Jenkins Board
>>- Repository will include sensitive content, including Commercial
>>Support, Trademarks, and maybe Governance docs in the future (once under
>>https://jenkins.io/project/).
>>- For Commercial Support and Approved Trademarks we will use separate
>>Asciidoc pages for each entry.
>>- jenkins.io builder will pull this resource and include pages into
>>jenkins.io, similar to how it happens with currently generated content
>>
>> Would appreciate feedback about such process.
>>
>> P.S: I will make sure to create a JIRA entry for it if someone wants to
>> contribute
>>
>>
>> On Thursday, January 23, 2020 at 6:22:29 AM UTC+1, Marky Jackson wrote:
>>>
>>> I like the idea of waiting for the advocacy meeting but that doesn’t
>>> mean we can’t get started on a WIP pr
>>>
>>> > On Jan 22, 2020, at 9:21 PM, 'Gavin Mogan' via Jenkins Developers <
>>> jenkin...@googlegroups.com> wrote:
>>> >
>>>
>> --
>> 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/6cc34bcb-d4b6-4f5a-a293-8c8b6f03356e%40googlegroups.com
>> 
>> .
>>
> --
> 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/vjLgQtpz06Y/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/CAH-3BidZWKWSGL3xAbuGhkHtp02JjvFE0ze9SLag5dNuEgZ-OA%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/CAPfivLB_059-YyxN%3DP-RNPm48euCLYk61oUJDv_aMAyOkcuyMw%40mail.gmail.com.

Re: Support List on jenkins.io?

[Tim Jacomb]

Is there a problem with using code owners for those files?

On Thu, 23 Jan 2020 at 11:05, Oleg Nenashev  wrote:

> Hi all,
>
> Thanks to everyone involved in this discussion. I would also like to move
> the page and to improve its look Moving the Commercial Support
>  and Approved
> Trademark Usage
>  pages
> is in my backlog for Wiki migration. This pages are not easy to migrate
> IMO, because jenkins.io grants a wide access for managing these pages
> (Copy Editors, SIG leaders, GSoC team, etc.). Such access is supposed to be
> restricted IMO, especially for the trademarks page. Access in Wiki was also
> restricted at some point.
>
> My plan for these pages is/was to...
>
>- Create a new public repository within Jenkins Infra for the
>sensitive content. Write permissions will be restricted to the Jenkins
>Infra team and to the Jenkins Board
>- Repository will include sensitive content, including Commercial
>Support, Trademarks, and maybe Governance docs in the future (once under
>https://jenkins.io/project/).
>- For Commercial Support and Approved Trademarks we will use separate
>Asciidoc pages for each entry.
>- jenkins.io builder will pull this resource and include pages into
>jenkins.io, similar to how it happens with currently generated content
>
> Would appreciate feedback about such process.
>
> P.S: I will make sure to create a JIRA entry for it if someone wants to
> contribute
>
>
> On Thursday, January 23, 2020 at 6:22:29 AM UTC+1, Marky Jackson wrote:
>>
>> I like the idea of waiting for the advocacy meeting but that doesn’t mean
>> we can’t get started on a WIP pr
>>
>> > On Jan 22, 2020, at 9:21 PM, 'Gavin Mogan' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>> >
>>
> --
> 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/6cc34bcb-d4b6-4f5a-a293-8c8b6f03356e%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-3BidZWKWSGL3xAbuGhkHtp02JjvFE0ze9SLag5dNuEgZ-OA%40mail.gmail.com.

Re: Support List on jenkins.io?

[Oleg Nenashev]

Hi all,

Thanks to everyone involved in this discussion. I would also like to move 
the page and to improve its look Moving the Commercial Support 
 and Approved 
Trademark Usage 
 pages is 
in my backlog for Wiki migration. This pages are not easy to migrate IMO, 
because jenkins.io grants a wide access for managing these pages (Copy 
Editors, SIG leaders, GSoC team, etc.). Such access is supposed to be 
restricted IMO, especially for the trademarks page. Access in Wiki was also 
restricted at some point.

My plan for these pages is/was to...

   - Create a new public repository within Jenkins Infra for the sensitive 
   content. Write permissions will be restricted to the Jenkins Infra team and 
   to the Jenkins Board
   - Repository will include sensitive content, including Commercial 
   Support, Trademarks, and maybe Governance docs in the future (once under 
   https://jenkins.io/project/).
   - For Commercial Support and Approved Trademarks we will use separate 
   Asciidoc pages for each entry. 
   - jenkins.io builder will pull this resource and include pages into 
   jenkins.io, similar to how it happens with currently generated content

Would appreciate feedback about such process.

P.S: I will make sure to create a JIRA entry for it if someone wants to 
contribute


On Thursday, January 23, 2020 at 6:22:29 AM UTC+1, Marky Jackson wrote:
>
> I like the idea of waiting for the advocacy meeting but that doesn’t mean 
> we can’t get started on a WIP pr 
>
> > On Jan 22, 2020, at 9:21 PM, 'Gavin Mogan' via Jenkins Developers <
> jenkin...@googlegroups.com > wrote: 
> > 
>

-- 
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/6cc34bcb-d4b6-4f5a-a293-8c8b6f03356e%40googlegroups.com.

Re: How does a stapler work with select tag

[Ullrich Hafner]

select is a standard HTML tag that is not processed at all. You need to use a 
 tag. 

> Am 23.01.2020 um 08:26 schrieb Nikhil Bhoski :
> 
> i have below entry in config.jelly for BuildWrapper class 
> 
>   
> 
>   
> 
>value="${installation.name}">${installation.name} 
>
>
>   
> 
>  
> 
> 
> 
> I am trying to validate the dropdown using doCehck method in the same 
> descriptor with below signature
> 
> public FormValidation doCheckMRoot(@QueryParameter final String mRoot) {
>   
> if(mRoot==null) {
>   return FormValidation.error("No Root selected");
> }else {
>   return FormValidation.warning("root is set");
> }
> }
> 
> 
> doCheck method does not get executed is there a different way that validation 
> for  tag works ? 
> 
> 
> 
> -- 
> 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/13f8f0a5-85e2-475c-a053-75b739ae4ea7%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/EFA6B8BB-9B97-4DEF-9161-DDEF4609DF04%40gmail.com.