Re: Retire some of my old plugins

['Gavin Mogan' via Jenkins Developers]

Okay, only 2 months later...

https://github.com/jenkins-infra/repository-permissions-updater/pull/3915
should remove me from everything
I also added deprecated label to the two dead ones

Plugin site seems updated

thanks ya'll

On Tue, Mar 19, 2024 at 5:27 AM 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

>
>
> On Sun, Mar 17, 2024 at 9:01 AM 'Alexander Brandes' via Jenkins Developers
>  wrote:
>
>> To mark the plugins as EOL, I recommend adding the “deprecated” topic to
>> the GitHub repositories, adding a note to the README that the plugin is
>> EOL, closing open PRs and archiving the GH repository.
>>
>
> In both cases it looks like continued distribution makes no real sense, so
> I recommend
> https://github.com/jenkins-infra/update-center2/?tab=readme-ov-file#removing-plugins-from-distribution
> in addition to the above.
>
>
>> Finally, you can remove yourself from the repository-permission-updater
>> file.
>>
>
> To clarify (as this has been a problem in the past): Keep the file, just
> remove your 'developers' list entry (likely resulting in `developers: []`
> for valid YAML).
>
> --
> 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/CAMo7PtLjLhc_5RtfWU1hgUSs2JjuF13busQWiesve8xGMQw6sA%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_Dutn2DKh_tyPhH5qBE-pJ4i94JrTzaRUshqW_rpe8tU%2BEg%40mail.gmail.com.

Re: Modernize device-watcher-plugin

['Gavin Mogan' via Jenkins Developers]

You need write access to the repository to affect the build. Its mostly
done for security to prevent builds from doing random things on the public
infra...ish

I believe someone with write access can kick off a build for your pr, but I
can't remember.

If the plugin is up for adoption you could take over.

On Sun, Apr 7, 2024, 12:58 a.m. Srikanth Jana 
wrote:

> Hi,
> Iam trying modernize device-watcher-plugin. I added Jenkinsfile to it and
> raise PR but seems the build is not triggered.
> Can some suggest what could be wrong?
>
> PR: https://github.com/jenkinsci/device-watcher-plugin/pull/2
>
> Thanks,
> Jana
>
> --
> 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/CAJxAiNBXFy%2BpJTxhjiL6iUGQvuAq7B0n%2BG0QS_XrJ_gXad6umg%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_DusnCzKZgnNmk%3DuUSnYmVBGH5cFrt8KFix-doYMh%2BDGbFg%40mail.gmail.com.

Re: Windows-arm64 native support

['Gavin Mogan' via Jenkins Developers]

As much as I find the response verbose and a little aggressive, I'm going
to have to agree, especially after the big XZ backdoor found in linux this
week. No binary in source control, libs need to be built.

As much as I agree, that a CI project shouldn't use a competitors CI
project, I think asking a new contributor to find someone who can help them
build a build pipeline on a server they don't have access to is pretty huge
ask and unfair. Thats essentially saying no.

The options should be either create a build pipeline on your own install of
jenkins (what I usually did), or build a ci pipeline in github actions in a
fork, and then submitting it as a PR.

On Wed, Apr 3, 2024 at 9:00 PM Basil Crow  wrote:

> On Thu, Mar 28, 2024 at 11:16 PM Pierrick Bouvier
>  wrote:
> > Thanks for your help, I'll take a look at this.
>
> And thanks for your interest! Unfortunately I think
> https://github.com/jenkinsci/winp/pull/112 is premature, as the
> repository is not currently in a state where _any_ outside
> contributions to the native C++ code can be accepted, as the Jenkins
> CI build uses precompiled binaries rather than building the C++ code
> from scratch.
>
> In order for us to be able to accept contributions to the native code
> like yours, we first need to set up a proper build environment with no
> pre-compiled binaries, a CI build (ideally Jenkins CI) that compiles
> both the Java code and the native code and runs the tests, and
> (ideally) a CD process on GitHub Actions that compiles both the Java
> code and the native code and performs the release. Our existing CI/CD
> infrastructure is heavily Maven-centric, so it would be preferred to
> use Maven as the entrypoint into the process and then to vector into
> the native code compilation from within Maven.
>
> My strong preference is for the above work to be done as a
> prerequisite to adding ARM support. The status quo is already
> untenable, even without taking into consideration the changes needed
> to add ARM support. I am a -1 on using GitHub Actions for CI, and I am
> a -1 on adding ARM support using the existing status quo of prebuilt
> binaries before solving the existing technical debt of the incomplete
> CI/CD process. The reason for this is that I believe there will not be
> a strong incentive to work on the long-term CI/CD process once the ARM
> support is added. Therefore I am against adding any new features,
> including ARM support, before the existing technical debt is
> addressed.
>
> Since commit access is required to test Jenkinsfile changes on
> ci.jenkins.io, I would propose to first add you as a winp committer
> alongside the Jenkins core team (but not a committer on any other
> repositories). This would allow you to test Jenkinsfile changes on
> ci.jenkins.io.
>
> The next steps after that, in this proposal, would be for you to
> develop two PRs, the first PR updating the Jenkinsfile to compile the
> native code as part of the Maven build rather than using pre-built
> binaries, and the second PR implementing CD with GitHub Actions. The
> first of these will require collaboration with the Jenkins
> infrastructure team to provide an appropriate stateless build
> environment. Once this is working, your commit access can be removed,
> and the core maintainers can click the CD button to perform a release
> from the sources without any prebuilt binaries. Since this release
> will have been compiled entirely on Jenkins infrastructure with no
> prebuilt binaries, it can be trusted and adopted by Jenkins core. At
> this point, the technical debt would be solved and the repository
> would become open to new features again.
>
> Unfortunately there is no existing maintainer to complete this
> prerequisite work. But after this is all said and done, you can
> proceed with your original PR to add ARM support, which should be easy
> for any core maintainer to approve and release (with CD) once the
> repository has no more prebuilt binaries and a working CI/CD 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/CAFwNDjpc_seOUNK9wKtkz7g3wkWcOwzBJWAxsjr62EaVjsobmg%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_DuuMyu%2B%2BsyMJ0yKQgF67gf-30BcxAoviA-NV-qDQJKKzJw%40mail.gmail.com.

Looking for new owners for plugins - lighthouse && digitalocean

['Gavin Mogan' via Jenkins Developers]

As I don't run jenkins at work or myself for a few years now, and
essentially been hands off on my other commitments, I want to make sure
some of my plugins find new homes. I've marked them up for adoption, but
before I remove myself from the maininter list, I want to see if anyone
else is interested.

https://plugins.jenkins.io/digitalocean-plugin/
Has some outstanding PRs from people. If someone does want to take over, I
can probably get them some free credits to test with.

https://plugins.jenkins.io/lighthouse-report/
Just works
Maybe should get lighthouse npm module updated from time to time to get the
latest report data, but just works

Gavin

-- 
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_Duumm0oX2TWAzg6YdPH-SCG-%2BWwizbe_meCm7S6N%3DXW6OA%40mail.gmail.com.

Retire some of my old plugins

['Gavin Mogan' via Jenkins Developers]

https://plugins.jenkins.io/html5-notifier-plugin/ - Code wasn't updated for
html to div project, nobody complained. The html5 notifications apis have
changed. While I do have a working branch, there's been no complaints, so I
think we should just archive the plugin

https://plugins.jenkins.io/graphql-server/ - Failed attempt at trying to
create graphql interface for jenkins. Graphql just doesn't handle class
inheritance well enough for it to work nicely with all the plugin
interfaces. Someone could take it over, but since its an incomplete
prototype, I think its worth archiving them.

Is there any objections? Also how would I go about officially marking them
depreciated/achieved?

-- 
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_DutK1ArKbCo3JbaPOz1V9DYFL_jtzeV4Cv4t5fMAdz%3D0uw%40mail.gmail.com.

Re: February 19, 2024 Governance Board Agenda

['Gavin Mogan' via Jenkins Developers]

If Jenkins needs more AI processing, Digital Ocean (sponsor) has
https://www.digitalocean.com/products/paperspace

Would recommend the super long running issues (eg, retiring chinese site)
gets broken up into issues somewhere so multiple people can work on it, I
know there's some super enthusiastic students looking to help out.

On Mon, Feb 19, 2024 at 9:19 AM Mark Waite 
wrote:

> The Jenkins board meeting starts at 7:00 PM UTC (about 6 hours from now).
> Zoom  link is
> https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09
>
> Here is the draft agenda:
>
> News
>
>- Ampere Computing  has lent 2 servers
>to the Jenkins project
>   - Special thanks
>  - Bruno Verachten arranged the loan to the Jenkins project
>  - Aaron Williams
>   arranged the
>  loan from Ampere Computing
>  - Mark Waite is hosting the machines at his house (donating
>  electricity and networking)
>  - CloudBees will be asked to donate disc drives and other
>  components as needed
>   - Next generation of the Jenkins project involvement with ARM64
>  - Oracle Cloud confirmed in 2021
>  
> 
>  that
>  Jenkins works well with ARM64
>  - Jenkins infrastructure continues transition to ARM64 servers
>  
> 
>
> Action Items
>
>- Basil create the attribution entries for the downloads page
>   - Jenkins sponsors have changed
>  - DigitalOcean donated over $20k USD last year and has donated
>  $20k in 2024
>  - AWS donation request has been submitted. Answer in 30 days. If
>  no donation, then should remove AWS from root page
>  
>   - Kevin Martens retire the Chinese Jenkins site
>   - Mark needs to do more Kubernetes setup, then Kevin and Mark will
>   meet with Damien
>   - More work after FOSDEM
>- Stefan Spieker to join the core-pr-reviewer team:
>https://groups.google.com/g/jenkinsci-dev/c/Wkhrs3nNEEU @NotMyFault
>
>   - Per the maintainer's doc, the board can vote on the decision:
>   
> https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#ladder
>   - @NotMyFault  is in favor, he has
>   been a great help reviewing core PRs and contributing to core before
>   - @MarkEWaite is in favor
>   - @basil is in favor
>
> Community
> activity
>
>- Contributor summit results
>   - Slides
>   
> 
>  from
>   the summit
>   - @kmartens27 preparing a summary blog post
>   - @MarkEWaite extend the Java 2+2+2 support plan JEP
>    with results from summit
>- Java 11, 17, and 21 in Jenkins - Mark Waite
>   - Contributor summit provided additional information
>  - HPI plugin has been extended to prepare for Java 11 end of
>  life - PR-578
>   from
>  Vincent Latombe
> - HPI plugin not yet released with the change
>  - 2+2+2 Java support plan - Jenkins enhancement proposal
>   
> 
>submitted
>  - Include the steps of the Java migration as part of the JEP
>  (work estimate, tasks, etc.)
> - Mark has much more work to do here
>- Dropping support for a Java version (refer to Java 11
>for ideas)
>- Adding a Java version (use Java 21 addition as the
>pattern)
>- Making a Java version the recommended version (use Java
>17 as the pattern)
> - Further refinements to be done in the JEP
>  - Key dates
>  - Oct 2, 2024 - Last Jenkins LTS release to support Java 11
>  - Oct 30, 2024 - First Jenkins LTS to require Java 17
>  - Oct 31, 2024 - end of Java 11 support by Jenkins project
>
> Governance
> Topics
>
>- Jenkins awards - Mark Waite
>   - Nominations close today, 19 Feb 2024
>   - Overview of the Jenkins awards
>  - CDF hosts the nominations
>  - Most valuable advocate
>   -
>  speaking, promoting, training, 

Re: January 8, 2024 Governance Board Agenda

['Gavin Mogan' via Jenkins Developers]

> Linux Foundation ticket IT-26276

opened
to request alternatives and their recommendation

is that alternatives to locking it down?

> Mark Waite submit jenkins.io pull request to combine subprojects and SIGs
into a single concept - “working groups
- > Kevin Martens retire the Chinese Jenkins site

Is there blockers other than time? its been on the agenda for many many
many months.


On Mon, Jan 8, 2024 at 10:17 AM Mark Waite 
wrote:

>
>
> Here is the draft agenda
>
> Action Items
>
>
>- Basil create the attribution entries for the downloads page
>   - Jenkins sponsors have changed
>  - Red Hat is no longer a member of the Continuous Delivery
>  Foundation. Remove from root page ?
>  - DigitalOcean donated over $20k USD last year and has donated
>  $20k in 2024
>  - AWS donation request has been submitted. Answer in 30 days. If
>  no donation, then should remove AWS from root page
>  
>   - Mark Waite submit jenkins.io pull request to combine subprojects
>and SIGs into a single concept - “working groups”
>   - Still no progress.
>- Kevin Martens retire the Chinese Jenkins site
>- License policy and phrasing changes
>   - What license should be used for a library plugin? (Mailing list
>   thread
>   
>   )
>  - Soft recommendation
>   has been
>  merged to Jenkins plugin publishing documentation
>  
> 
>  - If wrapper contains significant code, then use MIT license
>  - If wrapper does not contain significant code, then use license
>  of wrapped library
>
> Community
> activity
>
>-
>
>Artifactory bandwidth reduction project
> - Mark Waite
>- Results of production deployment
>   - Weekend surprises with artifact caching proxy not responding
>  - @NotMyFault reported issue-3890
>  
>  - @MarkEWaite reported issue-3889
>  
>   - Artifact caching proxies were reset earlier today
>-
>
>Java 11, 17, and 21 in Jenkins - Mark Waite
>- 2+2+2 Java support plan - Jenkins enhancement proposal
>   
> 
>submitted
>  - Include the steps of the Java migration as part of the JEP
>  (work estimate, tasks, etc.)
> - Mark has much more work to do here
>- Adding a Java version (use Java 21 addition as the
>pattern)
>- Making a Java version the recommended version (use Java
>17 as the pattern)
>- Dropping support for a Java version (refer to Java 11
>for ideas)
> - Further refinements to be done in the JEP
>  - Key dates
>  - Oct 2, 2024 - Last Jenkins LTS release to support Java 11
>  - Oct 30, 2024 - First Jenkins LTS to require Java 17
>  - Oct 31, 2024 - end of Java 11 support by Jenkins project
>
> Governance
> Topics
>
>-
>
>Defaced issue reports - help desk 3851
>
>- Jira database restored from backup to Dec 6, 2023 state
>  - Changes lost between Dec 6, 2023 and Dec 18, 2023
>   - Linux Foundation ticket IT-26276
>   
>  
> opened
>   to request alternatives and their recommendation
>  - Jenkins status page
>   for
>  Dec 18, 2023 restore
>   -
>
>Attribution request
> for
>downloads page from JFrog
>- Basil has submitted a draft pull request
>    for a
>   sponsors page
>  - Proposes multiple levels
> - Original proposal
>- Anchor
>- Premier
>- Partner
>- Supporter
>- Associate
>- Mirror
> - Alternate proposal (Olympic medals + 2 extra)
>- Anchor
>- Gold
>- Silver
>- Bronze
>- Mirror
> - 

UI/Website Feedback on top bar

['Gavin Mogan' via Jenkins Developers]

https://github.com/jenkins-infra/jenkins-io-components/pull/118

I've always felt that clicking the top left logo always goes to the root of
the site (so plugins.jenkins.io) and not to a different domain. I don't
actually know what the experience is across multiple domains.

Does anyone have some strong opinions? Changing this to always go to
jenkins.io affects all sites (plugins, accounts, stories, contributors,
www, etc)

Otherwise I'll go ahead and merge in a few days.

-- 
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_DuvTsXSUyb6%2BxR7C_aQwT6_F%3DVAmT56aQVaTFn1j7m-55w%40mail.gmail.com.

Re: Hosting New Jenkins plugin on Jenkins

['Gavin Mogan' via Jenkins Developers]

After you do a release, It should show up in update center first (inside of
jenkins) within a few minutes, and plugins.jenkins.io up to 3 hours later
(depending on when last run was)

On Fri, Nov 17, 2023 at 11:18 AM Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> wrote:

> Hello,
>
> The hosting process timing is not really long if there is no major issues
> found. The sooner you start it the better.
> For the availability of the plugin in the update center (what you called
> the market place I believe), you totally control that: once your hosting
> request is completed, you can release the plugin whenever you want which
> will add it to the update center.
>
> So again, start your hosting process as soon as possible, because this is
> the only thing that you don't totally control.
>
> Best regards,
>
> Le ven. 17 nov. 2023, 19:35, naveen sharma  a écrit :
>
>> Hi Team,
>>
>> We built new plugin and ready to create hosting request. Can someone
>> please help how much time it take to approve and can we select specific
>> date for plugin to available in marketplace.
>>
>> Please suggest.
>>
>> Regards,
>> Naveen
>>
>> --
>> 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/6f9f8476-a944-4ee4-9216-c712566294dbn%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/CAKwJSvw0J0zVAti0AEJQ5A%2BitRmfYBf50_i8ciD4yXwuqtoNnQ%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_Dus1n8O3%2BHz%3DW8k%3DYFw1dbW4%3DSDz%3DSp5USuf-Mih-RZ8kw%40mail.gmail.com.

Re: Plug-in adoption

['Gavin Mogan' via Jenkins Developers]

i was gonna be snarky and say "warm body"
honestly the willing to do it goes most of the way, review open issues,
close what needs to be closed
most functionally can be done with basic functions and basic html
complex stuff you ask for help/advice.

On Thu, Oct 26, 2023 at 1:21 PM Mark Waite 
wrote:

> Not much. I am a manager that was a C programmer many years ago.  I have
> learned Java and Maven as part of Jenkins plugin maintenance and a little
> experience before Jenkins.
>
> If you are interested in learning and are willing to learn, you can adopt
> a plugin.
>
> Technical questions to the developer list frequently get good answers.  If
> you'd like others to review your changes,  I am sure we can find people
> willing to answer questions and review changes
>
> On Thu, Oct 26, 2023, 1:11 PM STEVEN CORREA  wrote:
>
>> Hello everyone -
>>
>> What is the minimum level of development experience needed to adopt a
>> plug-in?
>>
>> Regards,
>> Steve
>>
>> --
>> 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/566a1ed2-1118-412c-a67d-d568aaf6df4en%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/CAO49JtHpD5RomKdNUJ6SJ9WOwBAX6SXBRjzboCgzrxizn2SLPQ%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_DuuQvqyPzFLqhJiN85sq-1Q6WXCn92xxUEvO2rJMUtwmKw%40mail.gmail.com.

Re: creating link on index page

['Gavin Mogan' via Jenkins Developers]

I would suspect your question is too vague so most people don't have a
quick easy answer to provide.

I would say you have 2 options
1) Make a new doThing function, and goto /action/thing and render a new
template with your stacktrace
2) Render the stacktrace in your html, hide it with css, and toggle showing
it with javascript
(`document.querySelector("selector").classList.toggle("show")`)

On Wed, Sep 13, 2023 at 11:52 PM Nikhil Bhoski 
wrote:

> Anybody any suggestion please ! I am kinda stuck on this feature in my
> plugin
>
> On Tuesday, 12 September 2023 at 11:45:06 UTC+5:30 Nikhil Bhoski wrote:
>
>> Hi I have table displayed like below which is rendering from my
>> index.jelly and which has Action class implementing Action class. I want to
>> show failure stack trace on click on FAILED link. How can i implement that ?
>> BulDArtifact.java is my action class
>>
>> https://github.com/mathworks/jenkins-matlab-plugin/blob/buildartifact/src/main/java/com/mathworks/ci/BuildArtifactAction.java
>>
>> Below is my index.jelly
>>
>>
>> https://github.com/mathworks/jenkins-matlab-plugin/blob/buildartifact/src/main/resources/com/mathworks/ci/BuildArtifactAction/index.jelly
>>
>>
>> [image: build.PNG]
>>
> --
> 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/9c8ce6b7-00da-47b1-b0d6-4d2e9913117an%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/CAG%3D_DuuC2zQC9SRWoGzvZeHwLd%2B-1o4ZQjNExAJ%2BjT%3DQQZdOTg%40mail.gmail.com.

Re: adopt Plugin - Nexus Artifact Uploader

['Gavin Mogan' via Jenkins Developers]

You may want to follow the actual template, from
https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/#plugins-marked-for-adoption
so people don't have to guess and look up information.

On Thu, Sep 7, 2023 at 7:49 AM Owen Rubel  wrote:

> Hey All,
> Was going to start my pipeline and noticed quite a few plugins needing
> help. Immediately I needed to upload stuff to Nexus (which I am already
> doing) and thought I could help out with this and actively test.
>
> Let me know back.
>
> --
> 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/d97185db-f1ad-4e3f-bfe0-885fb4817f7dn%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/CAG%3D_DutRbgiHNmx4f0h9iu%2BUkXuA6Q_6f59TU5AdhoeGa78NHA%40mail.gmail.com.

Re: Request for Status Update on Parasoft Findings Plugin 10.6.3 Release

['Gavin Mogan' via Jenkins Developers]

What are you expecting that didn't happen?

On Fri, Sep 1, 2023, 1:38 PM Yuqian Shi  wrote:

> Hi,
>
> This is Yuqian from Parasoft.
>
> I attempted to release the Parasoft Findings Plugin 10.6.3 using "mvn
> release:prepare" and "mvn release:perform." Both commands were successful,
> and I created a corresponding tag:
>
>
> https://github.com/jenkinsci/parasoft-findings-plugin/releases/tag/parasoft-findings-10.6.3
>
> Could you kindly confirm the progress of this release? It's been two days
> since I initiated it, and I'd appreciate an update.
>
> Thank you.
>
>
> Best regards,
>
> Yuqian Shi
>
> --
> 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/99eab28f-f544-4277-bc78-d6944c1c8549n%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/CAG%3D_DutB2wcr4LBM7zRVM2DNNsNV_9m%3De3_6heiKn%2BkQVGp4XA%40mail.gmail.com.

Re: Renaming the plugin and repo

['Gavin Mogan' via Jenkins Developers]

I'm sure it everything is in order it can be done pretty quickly, but since
everyone is volunteering there's no guarantees

On Wed, Aug 23, 2023, 11:00 AM Vladimir Belousov 
wrote:

> Agree
> We are also thinking about this option.
> If we will the ready code, will it be possible to publish the plugin in
> 2-3 working days?
>
> On Wed, Aug 23, 2023, 8:57 PM 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> just to be clear, changing the plugin id makes it a new plugin, which is
>> doable, but you'll lose all upgrade paths.
>> Its probably better if you are going to change everything, to just make a
>> new plugin and depreciate the old one, it'll be a lot less work.
>>
>> On Wed, Aug 23, 2023 at 10:07 AM 'Alexander Brandes' via Jenkins
>> Developers  wrote:
>>
>>> You can change the name of the GitHub repository and friendly name
>>> ( in the pom.xml) for sure. GitHub handles redirects. You may change
>>> them in documentation sources, such as the README.md too, if applicable.
>>> Renaming the GitHub repository is achieved by opening a pull request,
>>> modifying your permission file at the repository permission updater (
>>> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-redhat-codeready-dependency-analysis.yml
>>> ).
>>>
>>> Changing the plugin ID is not possible at this state anymore.
>>>
>>> Best regards,
>>> Alex
>>>
>>> On 23. Aug 2023, at 18:51, Vladimir Belousov 
>>> wrote:
>>>
>>> Hi,
>>> We are working on plugin
>>> https://plugins.jenkins.io/redhat-codeready-dependency-analysis/
>>>
>>> For some reason, we want to rename the plugin and change the repository
>>> name where it is hosted
>>>
>>> Will it work?
>>> What are the possible side effects?
>>>
>>> Thanks!
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/0ccc74b5-d410-4ce3-a76a-e684f1193f13n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/0ccc74b5-d410-4ce3-a76a-e684f1193f13n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>>
>>> --
>>> 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/2597D663-338D-4DAD-A996-42325E315D30%40notmyfault.dev
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/2597D663-338D-4DAD-A996-42325E315D30%40notmyfault.dev?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> 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/kzURQHNJUS8/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/CAG%3D_Duv_CZ7ueP3qw%2Bp5gKP6_ByBujE2DNpJDZoa8i2j52L6Xg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duv_CZ7ueP3qw%2Bp5gKP6_ByBujE2DNpJDZoa8i2j52L6Xg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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/CABcQtm9wLzezcor1bk2kthD3atkfCzwjz9x8vLVjmGem7TEheA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CABcQtm9wLzezcor1bk2kthD3atkfCzwjz9x8vLVjmGem7TEheA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

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

Re: Renaming the plugin and repo

['Gavin Mogan' via Jenkins Developers]

just to be clear, changing the plugin id makes it a new plugin, which is
doable, but you'll lose all upgrade paths.
Its probably better if you are going to change everything, to just make a
new plugin and depreciate the old one, it'll be a lot less work.

On Wed, Aug 23, 2023 at 10:07 AM 'Alexander Brandes' via Jenkins Developers
 wrote:

> You can change the name of the GitHub repository and friendly name (
> in the pom.xml) for sure. GitHub handles redirects. You may change them in
> documentation sources, such as the README.md too, if applicable.
> Renaming the GitHub repository is achieved by opening a pull request,
> modifying your permission file at the repository permission updater (
> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-redhat-codeready-dependency-analysis.yml
> ).
>
> Changing the plugin ID is not possible at this state anymore.
>
> Best regards,
> Alex
>
> On 23. Aug 2023, at 18:51, Vladimir Belousov  wrote:
>
> Hi,
> We are working on plugin
> https://plugins.jenkins.io/redhat-codeready-dependency-analysis/
>
> For some reason, we want to rename the plugin and change the repository
> name where it is hosted
>
> Will it work?
> What are the possible side effects?
>
> Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/0ccc74b5-d410-4ce3-a76a-e684f1193f13n%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/2597D663-338D-4DAD-A996-42325E315D30%40notmyfault.dev
> 
> .
>

-- 
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_Duv_CZ7ueP3qw%2Bp5gKP6_ByBujE2DNpJDZoa8i2j52L6Xg%40mail.gmail.com.

Re: Maven Release Plugin

['Gavin Mogan' via Jenkins Developers]

This sounds like a thread for users mailing list or forums. Actually
probably more of a maven question. All jenkins development is done on
GitHub so no svn involved.

On Thu, Aug 10, 2023, 12:21 PM D Kern  wrote:

> Hello, yes I did, I've attached them. I did notice that once I create my
> branch through Jenkins, the HEAD tag turns into the name of the branch...
> Hopefully that's not an issue, and is expected.
>
> On Thursday, August 10, 2023 at 2:05:01 PM UTC-5 p.r...@gmx.net wrote:
>
>> Can you tell more about your SCM urls? Did you rewrote them to git
>> instead of svn?
>>
>> Kind regards
>>
>> Peter Rader
>> --
>> Fachinformatiker AE / IT Software Developer
>>
>>
>>
>> Gesendet: Donnerstag, 10. August 2023 um 20:16 Uhr
>> Von: "D Kern" 
>> An: "Jenkins Developers" 
>> Betreff: Maven Release Plugin
>> I'm having issues with the maven release plugin after migrating from SVN
>> to GIT. This seems to be a known issue (
>> https://jira.codehaus.org/browse/MRELEASE-812 ,
>> https://groups.google.com/g/jenkinsci-dev/c/qkmbl3HrYgk[https://groups.google.com/g/jenkinsci-dev/c/qkmbl3HrYgk]
>> ,
>> https://stackoverflow.com/questions/15166781/mvn-releaseprepare-not-committing-changes-to-pom-xml?noredirect=1=1#comment130269452_20657721[https://stackoverflow.com/questions/15166781/mvn-releaseprepare-not-committing-changes-to-pom-xml?noredirect=1=1#comment130269452_20657721]
>> ,
>> https://www.mail-archive.com/iss...@maven.apache.org/msg88067.html[https://www.mail-archive.com/iss...@maven.apache.org/msg88067.html]
>> 
>> ). I have a multi module project and my pom for the release plugin
>> configuration is below:
>>
>> org.apache.maven.plugins
>> maven-release-plugin
>> 3.0.0-M1
>> 
>> 
>> org.apache.maven.scm
>> maven-scm-provider-gitexe
>>
>> 1.13.0
>> 
>> 
>> org.apache.maven.scm
>> maven-scm-api
>> 1.13.0
>> 
>> 
>>
>> When I run release:prepare  release:perform, it checks out the project,
>> then proceeds to tag the version with a -SNAPSHOT and deploys to my Nexus
>> snapshot repo. It works fine on SVN. I’ve tried setting the language to
>> English, I’ve used different versions of the SCM’s and release plugin. If I
>> go to 3.0.1 of the release plugin, I do get API errors within my build. I
>> have searched for a solution for a MULTI-MODULE project, and all versions
>> variations do not seems to be working. I can get successful build each
>> time, but again it just goes to the snapshot repo. Are there any
>> alternative, or solutions for this issue?
>>
>>
>> Thank you
>>
>> --
>> 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[mailto:
>> jenkinsci-de...@googlegroups.com].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/d4330475-3959-4551-a3e4-88a14237cf90n%40googlegroups.com[https://groups.google.com/d/msgid/jenkinsci-dev/d4330475-3959-4551-a3e4-88a14237cf90n%40googlegroups.com?utm_medium=email_source=footer]
>> .
>>
>>
> --
> 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/0c267e47-92b8-4ffa-ba28-3aa094a088d8n%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/CAG%3D_Dut-i5bkxrCR06_hbUZT9z_y2yNnVVdVZAkE0-ZyE6cRPA%40mail.gmail.com.

Re: Adopting the remote-jobs-view-plugin plugin

['Gavin Mogan' via Jenkins Developers]

https://www.jenkins.io/doc/developer/publishing/releasing-manually/ has all
the details.

On Mon, Jul 31, 2023 at 2:23 AM Kris Stern  wrote:

> Hi Swamy,
>
> According to Daniel you should be able to create a new release on your
> own. Can you check if that is indeed the case?
>
> Best,
> Kris
>
> --
> *From:* jenkinsci-dev@googlegroups.com 
> on behalf of Swamy M S 
> *Sent:* 31 July 2023 16:22
> *To:* jenkinsci-dev@googlegroups.com 
> *Subject:* Re: Adopting the remote-jobs-view-plugin plugin
>
> I have made a fix for the XML parser security fix now can someone guide me
> about the review and release
>
> On Mon, 31 Jul, 2023, 13:40 'Daniel Beck' via Jenkins Developers, <
> jenkinsci-dev@googlegroups.com> wrote:
>
>
> On Sun, Jul 30, 2023 at 11:16 AM Swamy M S  wrote:
>
> Can we enable this plugin wiki and release this plugin in jenkins again?
>
>
> Distribution will be restored once there is a fix for the security
> vulnerability that caused distribution to be suspended, and a release has
> been made. The last release is from 2015, so that hasn't happened yet. It
> looks like you already have permissions to create a new release.
>
> --
> 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/CAMo7PtJ6t9K0LuFdqXHUnWt4SFeXtGMMt7-QWvZTgePCH9qSJg%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/CAOd9OxDQxzFaQA904uez%2BwO-RpbnJv3AdYfqCH%3DPZo3SL60S%2Bw%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/OS3P286MB1431F06C67B83AF9451D2078A105A%40OS3P286MB1431.JPNP286.PROD.OUTLOOK.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_DuuxgmJY180SE1Ep6YECkjssNPK_PTCbWaLOd%3DTgeA2Gug%40mail.gmail.com.

Re: Accelerated end of life for Red Hat Enterprise Linux 7, CentOS 7, etc.

['Gavin Mogan' via Jenkins Developers]

I can't wait for the forum posts "Jenkins says my OS is bad, how do i fix?"

On Thu, May 25, 2023 at 4:16 PM Mark Waite 
wrote:

> Jenkins 2.407 will be the first weekly release to warn users about
> operating system end of life.  Warnings will be displayed immediately for:
>
> * Alpine Linux 3.14
> * CentOS Linux 7
> * Oracle Linux 7
> * Red Hat Enterprise Linux 7
> * Scientific Linux 7
> * Ubuntu Linux 18.04
>
> The next LTS baseline (after 2.401.x) will include the warning.
>
> Mark Waite
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/47488417-5e36-4995-9d3b-6fbed01f0b6dn%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/CAG%3D_DutPWSZW7f5EwroUy5NrpznTw7xqYXi0KsTda%3Da4Twq-5w%40mail.gmail.com.

Re: Did Tippy.js add Popper2 to Jenkins core?

['Gavin Mogan' via Jenkins Developers]

Unless i'm mistaken, that would keep the same problem, but move it
elsewhere. 

Re: Did Tippy.js add Popper2 to Jenkins core?

['Gavin Mogan' via Jenkins Developers]

I don't know.

I now checked https://weekly.ci.jenkins.io/ as well.

curl -s -L https://weekly.ci.jenkins.io/ | grep popper -c
0

On Wed, May 24, 2023 at 9:57 AM Basil Crow  wrote:

> On Tue, May 23, 2023 at 10:18 AM 'Gavin Mogan' via Jenkins Developers
>  wrote:
> > I tried accessing "Popper.createPopper" on ci.jenkins.io and it doesn't
> seem to be defined, so I don't think its exposed?
>
> Then why was https://github.com/jenkinsci/bootstrap5-api-plugin/pull/213
> needed?
>
> --
> 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/CAFwNDjqd2pooJbPtZkfeVKN%2Byu4xE%2Bf7ZD2w8aMVpyfS5hxEuw%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_Dut9vOAMN61Wj0paVQOj1c%2BfYoOP%2BPMqH993cqtDSsD5uQ%40mail.gmail.com.

Re: Did Tippy.js add Popper2 to Jenkins core?

['Gavin Mogan' via Jenkins Developers]

I totally agree for jenkins components to be exposed, but not artifacts of
those ui components because it leads to the 15 years of trying to get rid
of prototype because people used it directly.

On Tue, May 23, 2023 at 11:57 AM Ullrich Hafner 
wrote:

> >
> >> I think that users also will benefit from views that do not load the
> same
> >> library multiple times (loading time of a page). Also it duplicates the
> >> development effort if we create a plugin API for each JS library that
> we are
> >> using in core.
> >
> > These are indeed benefits, but I think the maintenance costs of exposing
> core
> > libraries to plugins are higher. This is a serious problem in every
> modular
> > system that fails to hide its internal implementation details from
> consumers;
> > see, for example:
> >
> >
> http://dtrace.org/blogs/wesolows/2014/04/10/libsunw_ssl-or-how-smartos-avoids-sadness/
> >
>
> I’m a little biased as a plugin developer but for me Jenkins core is not a
> system on its own that needs to be encapsulated. Jenkins core should
> provide all required components to create rich user interface for plugins.
> Providing the same JS libraries for my plugins feels a little bit like
> providing my own core to create value for my users. When we create new form
> elements in core (and tooltips like tippy) I want to use them in my plugins
> as well. That means core should be the basis for all other development and
> not a parallel component side by side with plugins.
>
> --
> 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/1A740EFF-B3BA-4891-AEF0-9F3804B63A8B%40gmail.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_Duvx%2BdamT5QFvKoyOO4Og7FFkD1rELW%2BUF%2BfFNyNHh7zCw%40mail.gmail.com.

Re: Did Tippy.js add Popper2 to Jenkins core?

['Gavin Mogan' via Jenkins Developers]

> Can Webpack be made to build a library under a hidden (shaded) namespace,
with core consuming the private version?

You explicitly have to configure things to make bundled libraries global.
by default require("") statements are localized, so `const $ =
require('jquery')` would not make it public.

looking at
https://github.com/atomiks/tippyjs/blob/ad85f6feb79cf6c5853c43bf1b2a50c4fa98e7a1/src/createTippy.ts#L1
if tippy is being required, it should be properly self contained, but if
its being loaded as a generic 

Re: GSoC 2023 Building jenkins.io with alternative tools project feedback solicitation

['Gavin Mogan' via Jenkins Developers]

Having been around for a number of the GSOC projects, and a number of the
migration projects. I'm very worried about half finished state that nobody
finishes. And honestly spent a lot of time cleaning up content on jenkins.io
(some were .html, some were .md, some were .txt)

So to me, jenkins.io shouldn't be cut over to the new system, until the new
system is fully populated.
As basil mentioned, antoria is really good at what it does, and shouldn't
be used for other things.
The web components was effort to make uniform theming across all sites,
instead of trying to merge everything into one site that tries to do a
dozen different things.

So my suggestion based on me trying to convert jenkins.io to gatsby a while
ago and realizing its just too big
1) docs.jenkins.io (versioned, antora)
2) guides.jenkins.io (versioned, antora, but less likely to update?)
3) news.jenkins.io (out of scope of gsoc i think) aka blog. hook up a
headless cms like netlifycms (all javascript + github), or maybe even
strapi (really nice headless cms, we could have webhooks that update the
repo)
4) Leave everything else on www.jenkins.io

Antora has really nice alogila support, so we can have versioned docs.
Gatsby does too, but its a little more custom. Docsearch is nice, but it
requires scraping the site all the time, so the more we can make structured
and uploaded the better.
It also makes a clear migration plan. We can make docs/tutorials live when
the content is fully pulled out. No half measures.

I recently had to go look at version 2.x of the ember docs. I was able to
pick my version, then search, and the whole thing remembered i was on 2.x
and answered accordingly. see
https://api.emberjs.com/ember/2.17/functions/@ember%2Fservice/inject


On Thu, May 18, 2023 at 2:29 PM Basil Crow  wrote:

> The calculus of this decision seems different when it comes to the
> documentation portions of the site (e.g., the end user documentation
> and developer documentation) vs the regular content (e.g., the blog,
> changelogs, and other static content). I think there may be a sweet
> spot in using Antora for the end user documentation and developer
> documentation while using another tool for the blog, changelogs, and
> other static content.
>
> For the documentation portions of the site, Antora seems like a
> perfect fit because it is specifically designed for documentation
> sites and features first-class support for branching/versioning
> documentation for multiple releases, combining multiple repositories
> into a single site, etc. There has been a real need for versioned
> documentation for multiple releases when working on e.g. Java Platform
> support and other projects. I imagine the long-term maintenance cost
> of Antora for the documentation portions of the site would be low:
> just keeping the build running and keeping the templates up-to-date.
> In contrast it seems that more effort would be required to use e.g.
> Gatsby for a versioned/branched documentation site. Even with e.g. the
> Rocketseat docs theme as a source of inspiration, it seems that Gatsby
> offers less support for the versioned documentation use case
> out-of-the-box and that custom code would need to be written and then
> maintained in order to fully accommodate the versioned documentation
> use case.
>
> In contrast, Antora was not designed for blogs, and Antora issue #444
> makes it clear that the maintainers do not intend to support blog-like
> functionality in Antora. Using Antora for anything other than a
> documentation site seems ill-advised, as this is not Antora's intended
> use case.
>
> While it might be possible to use e.g. Gatsby for everything
> (including the blog and documentation portions of the site), my sense
> is that the benefits of using Antora for the documentation portions of
> the site (both from an initial development and maintenance
> perspective) may be more compelling.
>
> --
> 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/CAFwNDjqHDVdiwDTLiUAEtYF-3Pw4mb_Go9JDg2Ts%2B5LG%3DW7yPQ%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_DusMa-3WKNinkwRr2face3ZPxDzL%2BqWmn6KLU5_FfPr49w%40mail.gmail.com.

Re: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:javac: invalid flag: --release

['Gavin Mogan' via Jenkins Developers]

totally fair, i didn't notice the timestamps, sorry for that

On Thu, May 11, 2023 at 9:02 AM Basil Crow  wrote:

> On Thu, May 11, 2023 at 8:55 AM 'Gavin Mogan' via Jenkins Developers
>  wrote:
> >
> > I think the PR in question is doing exactly that
> https://github.com/jenkinsci/bmc-cfa-plugin/pull/42/files#diff-e6ffa5dc854b843b3ee3c3c28f8eae2f436c2df2b1ca299cca1fa5982e390cf8R4-R5
>
> Those lines were not present in the PR at the time of the original
> post. They were just committed, presumably after reading the blog post
> I mentioned.
>
> --
> 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/CAFwNDjp9ziTungzxCWApmn6GZ-zZJNA-HqcAwNf%2BibE161%2BMdA%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_DuvbWmepYi4%3DWsADwm8UTvaq_yN2X7a092Cf3k8BiY8iHA%40mail.gmail.com.

Re: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:javac: invalid flag: --release

['Gavin Mogan' via Jenkins Developers]

I think the PR in question is doing exactly that
https://github.com/jenkinsci/bmc-cfa-plugin/pull/42/files#diff-e6ffa5dc854b843b3ee3c3c28f8eae2f436c2df2b1ca299cca1fa5982e390cf8R4-R5

On Thu, May 11, 2023 at 8:23 AM Basil Crow  wrote:

> Please read Jenkins plugin development requires Java 11 or newer
> .
>
> --
> 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/CAFwNDjpB8Nw-XDUjQ46tgfY%3DGMYabDN4CwtgTUG%3Dt-c%3DqRQsFQ%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_Dushqc4juFOg97WR8-n4EhT4pN-KbR44G1smF229Q9mC9A%40mail.gmail.com.

Re: Jenkinsci Cloudevents plugin

['Gavin Mogan' via Jenkins Developers]

plugins.jenkins.io builds from
https://updates.jenkins.io/current/update-center.actual.json every 3 hours.

so confirm your stuff is in the json, then wait a bit :)

On Tue, Apr 25, 2023 at 9:30 AM 'Gerard McMahon' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hi
>
> I think we have completed all the steps and published to artifactory. We
> still do not see the plugin on plugins.jenkins.io and we are unsure if we
> have missed a step. Would someone with knowledge be able to take a look and
> let us know. I would appreciate and help.
>
> Thanks
>
> Ger
>
> On Tuesday, April 25, 2023 at 9:26:07 AM UTC+1 Gerard McMahon wrote:
>
>> Hi All
>>
>> I think we are on the last step so we can release the plugin. We are
>> looking to get this PR approved 
>> https://github.com/jenkinsci/cdevents-plugin/pull/1
>>
>>  and then we should be able to push to jenkins artifactory where i think
>> it then will get pulled to plugins.jenkins.io
>>
>> Thanks
>>
>> Ger
>>
>> On Monday, April 24, 2023 at 10:09:27 AM UTC+1 jamie@fmr.com wrote:
>>
>>> Thanks Alex and everyone for helping us get to this point!
>>>
>>> I will follow the above guide to close out the release to
>>> plugins.jenkins.io
>>>
>>> See you in Vancouver :)
>>>
>>> Jamie
>>>
>>> On Saturday, April 22, 2023 at 11:12:46 AM UTC+1 gerard@fmr.com
>>> wrote:
>>>
 Thanks Alex. We will try that out and hopefully Monday will get
 completed. Very exciting

 Sent from Outlook for iOS 

>>> *From:* jenkin...@googlegroups.com  on
 behalf of Alexander Brandes 
 *Sent:* Saturday, April 22, 2023 11:04:46 AM

 *To:* Jenkins Developers 
 *Subject:* Re: Jenkinsci Cloudevents plugin
 NOTICE: This email is from an external sender - do not click on links
 or attachments unless you recognize the sender and know the content is
 safe.

 > Do you know what the next steps are to get the plug-in formally
 pulled into the jenkins project on GitHub and being available on the
 plugin.jenkins.io page? I don’t know if that is a process or something
 more simple?

 It's as simple as cutting a release of the plugin. Take a look at the
 guide
 
  on
 how to set up your machine to cut a successful release.
 plugins.jenkins.io refreshes every 2 hours, if I recall correctly, so
 you'll see your plugin there timely.

 > Also we will be in Vancouver for cdCon if others are. We would love
 to meet up.

 Awesome, I'll be there too \o/

 ~ Alex

 On Saturday, 22 April 2023 at 11:59:08 UTC+2 gerard@fmr.com wrote:

 Thank you Alexander and it is great to be onboard and we look forward
 to further contributions and participation.

 Do you know what the next steps are to get the plug-in formally pulled
 into the jenkins project on GitHub and being available on the
 plugin.jenkins.io page? I don’t know if that is a process or something
 more simple?

 Also we will be in Vancouver for cdCon if others are. We would love to
 meet up.

 Thanks

 Ger

 Sent from Outlook for iOS 
 --
 *From:* jenkin...@googlegroups.com  on
 behalf of Alexander Brandes 
 *Sent:* Saturday, April 22, 2023 10:23:22 AM
 *To:* Jenkins Developers 
 *Subject:* Re: Jenkinsci Cloudevents plugin

 NOTICE: This email is from an external sender - do not click on links
 or attachments unless you recognize the sender and know the content is
 safe.

 Hey Gerard,

 I've finished my investigation and didn't find new blockers. Thanks for
 addressing my outstanding concerns and welcome aboard!

 I'm excited to see the CDEvents plugin being included in the printings.

 BR,
 Alexander Brandes

 On Friday, 21 April 2023 at 16:12:56 UTC+2 gerard@fmr.com wrote:

 Hi


 I first wanted to thanks you all for the help and support on this, our
 teams first major contribution. I think we have made great progress on the
 feedback received to date and we are hoping the lastest push closes out all
 the findings.


 I wanted to share that there is somewhat of a time consideration to
 having the plugin publicly available and accessible. The CDF are planning
 to announce the plugin within some upcoming press releases and at CDCon on
 May 8th alongside other contribution projects related to CDEvents. All the
 marketing materials for the press releases and CDCon have to be submitted
 next week for print etc. We are looking to include the Jenkins CDEvents
 Plugin within the press release and at CDCon and wanted to include all the
 Jenkins URL's for gihub and plugin.jenkins.io.



 Do you think this is 

Re: Reimbursement for code signing certificate

['Gavin Mogan' via Jenkins Developers]

I would argue this discussion should happen before the spending not after.

But +1 from me

On Tue, Apr 18, 2023 at 12:04 PM Tim Jacomb  wrote:

> +1
>
> On Tue, 18 Apr 2023 at 19:32, Basil Crow  wrote:
>
>> On Tue, Apr 18, 2023 at 11:23 AM 'Gavin Mogan' via Jenkins Developers
>>  wrote:
>> > Shouldn't this be submitted via expensify and approved in the board
>> > mailing list?
>>
>> From JEP-15 (at revision b8bfe17), § 3.3.2 ("Use of donations"), lines
>> 177-178:
>>
>> > Budget requests should be submitted to the developer mailing list and
>> > discussed there, the Governance meeting will be doing a formal
>> > approval/rejection based on the community feedback.
>>
>> --
>> 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/CAFwNDjpHawAfD7141y-_TxgOThzrMH_g7Z9x8To2p9vQHPM5Bw%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-3Bif%2Bm%2BaUJYNW1F5xQTz6DCm1jj5qWj%2B%3D_go1vq4Z0hVOyA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bif%2Bm%2BaUJYNW1F5xQTz6DCm1jj5qWj%2B%3D_go1vq4Z0hVOyA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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_DuvDX0_sQ8CMpxRuQP9qEb8TST-BMS-3mKo94CWgdvrVdw%40mail.gmail.com.

Re: Reimbursement for code signing certificate

['Gavin Mogan' via Jenkins Developers]

Shouldn't this be submitted via expensify and approved in the board mailing
list?

On Tue, Apr 18, 2023 at 11:19 AM Mark Waite 
wrote:

> As part of the code signing certificate renewal process for the Jenkins
> MSI installer and the Jenkins WAR file, we spent $1536.00 to purchase the
> certificate.  I sent the notice of that purchase in Feb 2023.  The charge
> has now appeared on my credit card and I'd like to be reimbursed.
>
> I can provide the receipt from the purchase on request.
>
> Mark Waite
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/23dd03f2-7939-4b3c-bb0e-0dee0ce0d398n%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/CAG%3D_Duu79RkbyKU9WPiWQJ5eENk2o-56SO6UvG3fP5YcZCg9kA%40mail.gmail.com.

Re: Looking for assistants on jenkins.io ui decisions

['Gavin Mogan' via Jenkins Developers]

Thanks so much for helping out.

All my github notifications get marked as spam, so now i can only review
them really at the end of the day, so i'm way behind on things.

As for groups, I kinda gave access to plugin-site group, but it can
probably be given to a better group. I've been trying to tag @copy-editors
for copy changes, like navigation

On Fri, Apr 14, 2023 at 9:36 AM Alexander Brandes 
wrote:

> Hey Gavin,
>
> I'm already reviewing PRs and contributing to several component-like
> repositories. I plan to keep up on that. Don't hesitate to mention me in a
> PR if you're looking for an additional pair of eyes.
> If we have a team for that, you can add me to one for sure, to keep your
> workload surveyable. Whatever works the best for you!
>
> ~ Alex
>
> On Monday, 27 February 2023 at 01:28:32 UTC+1 kris...@outlook.com wrote:
>
>> Hi Gavin,
>>
>> I would like to help out on such tasks if possible.
>>
>> Best,
>> Kris
>> --------------
>> *From:* ga...@gavinmogan.com  on behalf of 'Gavin
>> Mogan' via Jenkins Developers 
>> *Sent:* 27 February 2023 08:18
>> *To:* Jenkins Developers 
>> *Subject:* Looking for assistants on jenkins.io ui decisions
>>
>> So I am the "official maintainer" of plugins, i guess stories, and the
>> web components for header and footer.
>>
>> I have no problem with reviewing PRs for technical items and bugs, but
>> for behavior, I have low motivation. I don't use jenkins at work, and since
>> getting covid in january, i've been trying to be off my personal computer
>> more, and it looks like the ramp up for gsoc is getting more and more small
>> behavior PRs coming though (fixes to support mobile viewing).
>>
>> I know kevin and mark "own" the content of jenkins.io
>> <https://jpn01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjenkins.io%2F=05%7C01%7C%7Cef50024bc1714f4df0d708db185830cb%7C84df9e7fe9f640afb435%7C1%7C0%7C638130539281100141%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=xF5ToNRE%2BfEhNyKpfa5PTLQRMes26ukKF817fKid2B0%3D=0>,
>> but is there anyone interested in owning/being primary for behavior of the
>> sites?
>>
>> https://github.com/jenkins-infra/jenkins-io-components/pull/71
>> <https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins-io-components%2Fpull%2F71=05%7C01%7C%7Cef50024bc1714f4df0d708db185830cb%7C84df9e7fe9f640afb435%7C1%7C0%7C638130539281100141%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=2BwROLXhSYXvQbsLg260hBhdPrTKvZ5L6749%2BcgNsKs%3D=0>
>> - Show links to books in the footer.
>> https://github.com/jenkins-infra/jenkins-io-components/pull/63
>> <https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins-io-components%2Fpull%2F63=05%7C01%7C%7Cef50024bc1714f4df0d708db185830cb%7C84df9e7fe9f640afb435%7C1%7C0%7C638130539281100141%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=TOxE7TbO1mcKR2TalRGT9xV8a5PqiIQ4CW3sjhsiK8I%3D=0>
>> - overflow of menu links on mobile
>> https://github.com/jenkins-infra/plugin-site/pull/1277
>> <https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fplugin-site%2Fpull%2F1277=05%7C01%7C%7Cef50024bc1714f4df0d708db185830cb%7C84df9e7fe9f640afb435%7C1%7C0%7C638130539281100141%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=y%2BmXJCzc10sl5h6Ku9tSWWJuJ7a0J43mCt%2Fv6e1yRgo%3D=0>
>> - Changing of alignment on search on plugins site
>> https://github.com/jenkins-infra/plugin-site/pull/1276
>> <https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fplugin-site%2Fpull%2F1276=05%7C01%7C%7Cef50024bc1714f4df0d708db185830cb%7C84df9e7fe9f640afb435%7C1%7C0%7C638130539281100141%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=CUcplAnx%2F05TbOL%2BCZn24Hol80I%2B1%2Fh4pJqylHDhR6k%3D=0>
>> - Show more page numbers on larger screen
>>
>> All seem fine from a technical point of view, and the two plugin ones
>> sound good are probably wins, i just know myself and my ADHD, its hard to
>> motivate myself to deal with them.
>>
>> So looking for assistance, mostly on the why/if we should, not the code,
>> i can handle the code.
>>
>>
>> Gavin
>>
>> --
>> You received this message because you are subscribed to the Googl

Re: requesting access to blueocean-plugin

['Gavin Mogan' via Jenkins Developers]

Unless you are planning on taking over full ownership for that repo, I
would recommend you fork the repo, and submit a pull request, at least
until you are comfortable making changes. Its a big visible project with
some maintainers.

That being said, depending on what changes you are trying to make, there
might be better more maintained repos to contribute fixes to like
https://community.jenkins.io/t/blue-ocean-but-in-classic-ui/96

On Tue, Apr 11, 2023 at 10:51 AM 'Gobinath Durairaj' via Jenkins Developers
 wrote:

> I am making some enhancements to this plugin. While pushing, I realized
> that I do not have write access. Can someone grant me access to this
> repository - https://github.com/jenkinsci/blueocean-plugin?
>
> Thanks
> Gobi
>
> *The content of this e-mail is confidential and is intended solely for the
> use of the individual or entity to whom it is addressed. If you have
> received this e-mail by mistake, please reply to this e-mail and follow
> with its deletion. If you are not the intended recipient, please note that
> it shall be considered unlawful to copy, forward or in any manner reveal
> the contents of this e-mail or any part thereof to anyone. Although
> Freshworks has taken reasonable precautions to ensure no malware is present
> in this e-mail, Freshworks cannot accept responsibility for any loss or
> damage arising from the use of this e-mail or attachments.*
>
> --
> 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/788211df-aabe-457c-816a-4d93411a2bf5n%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/CAG%3D_DusJZaWqMP_EUjvOwAX074p%3Df%2BDTUCkMEDfpHmCDTS7c4Q%40mail.gmail.com.

Re: Apr 3, 2023 Governance Board Agenda

['Gavin Mogan' via Jenkins Developers]

> Mark Waite and Gavin “halkeye” Mogan archive the governance meeting notes
to a GitHub repository, use the Google doc as the working document, then
publish final notes


I'm no longer interested in working on this, its been way to long to keep
my interest. I can dig up the google docs => markdown export I did a while
ago if someone else wants it, but it was just using a free google docs
plugin.



On Mon, Apr 3, 2023 at 9:53 AM Mark Waite  wrote:

> The Jenkins governance board meets at 6:00 PM UTC today.  Zoom URL is
> https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09
>
> Agenda:
>
>-
>
>Claim from BMC to GitHub Trust and Safety (update center PR 692
>)
>-
>
>   Claim rescinded, plugin distribution restored, special thanks to
>   Daniel Beck
>   -
>
>News
>-
>
>   Jenkins 2.387.2 and 2.398 release this week
>   -
>
>   PGP repository signing key expired March 30, 2023 for deb and rpm
>   packages, new key for 2.397 and 2.387.2
>   -
>
>  Announced in
>
>
>-
>
>Jenkins blog  including its RSS feed
>
>-
>
>Jenkins LinkedIn account
>
>-
>
>Jenkins twitter account 
>-
>
>Jenkins weekly changelog  and its RSS
>feed 
>-
>
>Top level Jenkins page  has a rotating
>announcement that links to the blog post
>-
>
>Gitter chat channel
>
>
>
>-
>
>Action Items
>-
>
>   EasyCLA to be documented by Oleg
>   -
>
>  No progress, no requests pending, pick it up if there are CLA
>  submissions
>  -
>
>   Mark Waite submit jenkins.io pull request to combine subprojects
>   and SIGs into a single concept - “working groups”
>   -
>
>  No progress, Mark to complete
>  -
>
>  Roadmap update pull requests, make it current for April 12 CDF
>  TOC presentation
>  -
>
>   Retire the Chinese Jenkins site
>   -
>
>  Chinese site link removed from www.jenkins.io header
>  -
>
>  Rick recommends that we redirect the chinese pages to English
>  equivalents
>  -
>
>  Kevin Martens (Docs Officer) tracking help desk ticket
>   to
>  replace the Chinese pages with redirects to the English pages
>  -
>
> Need a redirect from https://www.jenkins.io/zh/ to
> https://www.jenkins.io/ 
> -
>
>   Mark Waite and Gavin “halkeye” Mogan archive the governance meeting
>   notes to a GitHub repository, use the Google doc as the working 
> document,
>   then publish final notes
>   -
>
>  Gavin has prepared the archive, need a destination repository
>  -
>
>  Alexander Brandes has something in mind on how to structure
>  things.
>  -
>
>  Infra team raised about the repository location as a question
>  -
>
>  Oleg prefers jenkinsci rather than jenkins-infra for a
>  governance repository (this is not about the archive repository!)
>  -
>
> Mark check the infra team preference, discuss if not jenkinsci
>
> -
>
>CDF topics
>-
>
>   Digicert code signing certificate renewal in progress
>   -
>
>  Proposed to stop building Jenkins MSI installer until new code
>  signing certificate is available and configured
>  -
>
> Mark Waite sent note to Jenkins officers today with the
> proposal
> -
>
> PR-356  in
> the release repository
> -
>
> PR-384  in
> the packaging repository
> -
>
>   Jenkins project presentation to the CDF Technical Oversight
>   Committee April 12, 2023
>   -
>
>  Mark Waite prepare and present Jenkins status report
>  -
>
> Mark create presentation, share it with this group, invite
> comments, corrections
> -
>
> Last TOC confirmed that they are OK with a project review
> that looks at participation in addition to technical topics
> -
>
>   LFX Tools working group starting based on last CDF TOC meeting
>   -
>
>  Noted that devstats.cd.foundation
>  
> 
>

Re: [Jenkins Development Support for IntelliJ IDEA] Release 3.0.0

['Gavin Mogan' via Jenkins Developers]

I would recommend putting something in the "showing off" (maybe should be
renamed showcase?) category on the forums -
https://community.jenkins.io/c/using-jenkins/showing-off/9 - so advocacy
group remembers to throw something about this into the next newsletter (
https://www.jenkins.io/node/tags/newsletter/)

On Thu, Mar 16, 2023 at 11:44 PM 'Denys Digtiar' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> When I said, "IntelliJ will warn you", what I meant is below. It just
> popped up for me. I just choose "Yes" and then go to the "Project
> Structure" and remove the old facet altogether.
> [image: 2023-03-17-stapler-facet-warning.png]
>
> On Friday, March 17, 2023 at 1:38:40 PM UTC+10 Denys Digtiar wrote:
>
>> GitHub Release Notes of 3.0.0
>> 
>>
>> Items of note:
>> * Unused Stapler Facet is removed (#121) @jgreffe
>> * Add 'since' attribute to the 'attribute' tag of the Stapler tag library
>> (#141) @NotMyFault
>> * i18n with single-quote exception "Argument rangeInElement (9,25)
>> endOffset must not exceed descriptor text range (38, 62) length (24)"
>> (#127) @jgreffe
>>
>> Another significant improvement from @jgreffe finally gets a release.
>> There used to be Stapler Facet
>>  which was probably
>> added based on the example plugin but was only used as a flag enabling the
>> Jexl Inspection. It is now removed because there was no apparent need for
>> it. If you ever configured it, which is unlikely, the IntelliJ will warn
>> you that it cannot be read anymore, and you can then safely remove it from
>> the modules. You might also notice warnings about JEXL expressions.
>>
>> --
> 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/d24cbb1d-5652-47a7-a5f7-da2105b3f6c5n%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/CAG%3D_DuvMO0C2azxy3XFq%2BbfZvZ1RU2KMDothFKTArJa_ZbBShA%40mail.gmail.com.

Re: Prototype.js replacing JSON.stringify

['Gavin Mogan' via Jenkins Developers]

My knowledge of core is pretty out dated, but as far as I know, a lot of
the behaviors are defined using YUI and Prototypejs
I think the first steps would be to remove as many of those references from
core before detaching the plugin and making it optional

For example, the Ajax.Request would need to be re-written
https://github.com/jenkinsci/jenkins/blob/a4447db3d88fd883b99ff3925a5ea90864794367/core/src/main/resources/lib/form/link/link.js#L15
https://github.com/jenkinsci/jenkins/blob/a4447db3d88fd883b99ff3925a5ea90864794367/core/src/main/resources/lib/layout/breadcrumbs.js#L168

I'm sure there's lots of other legacy items left behind.

Talking about it is good, but unless people actually make PRs, it'll never
actually get replaced.

On Sat, Mar 11, 2023, 8:01 PM 'Rahul Somasunderam' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Is it possible to turn it into its own plugin and treat it as an implicit
> dependency for plugins relying on older versions of Jenkins, but remove it
> later?
>
>
> On Mar 11, 2023, at 15:37, Ullrich Hafner 
> wrote:
>
> I think I also have some problems with this ugly dependency. Seems that
> other JS libraries that rely on JSON stringify (datatables, echarts) break
> in some places as well :-(
>
> But this JS code is so deeply nested in Jenkins UI code that I have no
> clue on how to fix that...
>
>
> Am 02.03.2023 um 23:15 schrieb 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com>:
>
> I vaguely remember some javascript code somewhere deleting
> Object.prototype.toJSON() or something
>
> A quick search found
> https://github.com/jenkinsci/jenkins/blob/e41aeaacf434b9ff93c8848f8eddbfcbb27ed462/war/src/main/js/util/jenkins.js#L20-L54
> In theory that makes JSON.stringify work again, but would make the other
> prototype js fail, so would have to be done temporarily.
>
>
> On Thu, Mar 2, 2023 at 1:59 PM Ullrich Hafner 
> wrote:
>
>>
>> Hi!
>> I was looking at some javascript that was behaving differently on Jenkins
>> than it does on other apps. I boiled it down to the simplest reproducible
>> test case.
>> It turned out that serialization was behaving differently when calling
>> JSON.stringify.
>>
>> This is the sample code you can run on the Chrome DevTools
>>
>> JSON.stringify({ a: [1, 2, 3] });
>>
>> On Jenkins, this is the behavior
>>
>> '{"a":"[1, 2, 3]"}'
>>
>> On other apps, this is the behavior
>>
>> '{"a":[1, 2, 3]}'
>>
>> When I attempt to debug the code, stepping into `JSON.stringify` on
>> Jenkins takes me to prototype.js.
>>
>> I've seen some threads here attempting not to rely on prototype.js for
>> functionality, but how far are we from removing it?
>>
>>
>> Very far. A couple of years ago I even tried to upgrade prototype.js to
>> the latest version but failed, since some plugins are depending on
>> prototype.js as well. All UI stuff is tightly coupled to prototype.js, this
>> will be very hard to remove.
>>
>>
>> - Rahul
>>
>> --
>> 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/708c6498-e0d4-481e-9ad7-e0a8e5af65ffn%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/708c6498-e0d4-481e-9ad7-e0a8e5af65ffn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>>
>>
>> --
>> 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/76FFAC15-B00C-4528-8AB1-68ED0E6D7055%40gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/76FFAC15-B00C-4528-8AB1-68ED0E6D7055%40gmail.com?utm_medium=email_source=footer>
>> .
>>
>
> --
> 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_Duv8NOUT%2BzGfEoww2bf11kdNAkkT8HCwG%3DUoRuCB6J5ktQ%40

Re: Prototype.js replacing JSON.stringify

['Gavin Mogan' via Jenkins Developers]

I vaguely remember some javascript code somewhere deleting
Object.prototype.toJSON() or something

A quick search found
https://github.com/jenkinsci/jenkins/blob/e41aeaacf434b9ff93c8848f8eddbfcbb27ed462/war/src/main/js/util/jenkins.js#L20-L54
In theory that makes JSON.stringify work again, but would make the other
prototype js fail, so would have to be done temporarily.


On Thu, Mar 2, 2023 at 1:59 PM Ullrich Hafner 
wrote:

>
> Hi!
> I was looking at some javascript that was behaving differently on Jenkins
> than it does on other apps. I boiled it down to the simplest reproducible
> test case.
> It turned out that serialization was behaving differently when calling
> JSON.stringify.
>
> This is the sample code you can run on the Chrome DevTools
>
> JSON.stringify({ a: [1, 2, 3] });
>
> On Jenkins, this is the behavior
>
> '{"a":"[1, 2, 3]"}'
>
> On other apps, this is the behavior
>
> '{"a":[1, 2, 3]}'
>
> When I attempt to debug the code, stepping into `JSON.stringify` on
> Jenkins takes me to prototype.js.
>
> I've seen some threads here attempting not to rely on prototype.js for
> functionality, but how far are we from removing it?
>
>
> Very far. A couple of years ago I even tried to upgrade prototype.js to
> the latest version but failed, since some plugins are depending on
> prototype.js as well. All UI stuff is tightly coupled to prototype.js, this
> will be very hard to remove.
>
>
> - Rahul
>
> --
> 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/708c6498-e0d4-481e-9ad7-e0a8e5af65ffn%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/76FFAC15-B00C-4528-8AB1-68ED0E6D7055%40gmail.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_Duv8NOUT%2BzGfEoww2bf11kdNAkkT8HCwG%3DUoRuCB6J5ktQ%40mail.gmail.com.

Looking for assistants on jenkins.io ui decisions

['Gavin Mogan' via Jenkins Developers]

So I am the "official maintainer" of plugins, i guess stories, and the web
components for header and footer.

I have no problem with reviewing PRs for technical items and bugs, but for
behavior, I have low motivation. I don't use jenkins at work, and since
getting covid in january, i've been trying to be off my personal computer
more, and it looks like the ramp up for gsoc is getting more and more small
behavior PRs coming though (fixes to support mobile viewing).

I know kevin and mark "own" the content of jenkins.io, but is there anyone
interested in owning/being primary for behavior of the sites?

https://github.com/jenkins-infra/jenkins-io-components/pull/71 - Show links
to books in the footer.
https://github.com/jenkins-infra/jenkins-io-components/pull/63 - overflow
of menu links on mobile
https://github.com/jenkins-infra/plugin-site/pull/1277 - Changing of
alignment on search on plugins site
https://github.com/jenkins-infra/plugin-site/pull/1276 - Show more page
numbers on larger screen

All seem fine from a technical point of view, and the two plugin ones sound
good are probably wins, i just know myself and my ADHD, its hard to
motivate myself to deal with them.

So looking for assistance, mostly on the why/if we should, not the code, i
can handle the code.


Gavin

-- 
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_Dus1UmUJrkOvrV_YLEe59mae1mahhuLmGOWRQ%3DBtO9sY2w%40mail.gmail.com.

Can someone delete https://plugins.jenkins.io/packageversion/

['Gavin Mogan' via Jenkins Developers]

26 installs, xss warning and still targeting 1.x. It showed up when I
looked up plugins for "version"
and I was wondering why we are keeping it around?

Gavin

-- 
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_DuspVaW9i9AuxHQ3sp6sfxrNR6VxkVUfJa5%3DCfDMXpbjBA%40mail.gmail.com.

Re: Shared pipeline library "infra.runMaven" now using Artifact Caching Proxy

['Gavin Mogan' via Jenkins Developers]

\o/

On Wed, Feb 15, 2023, 2:55 AM 'Herve Le Meur' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hello,
>
> As https://github.com/jenkins-infra/pipeline-library/pull/592 has been
> merged, the "infra.runMaven" function from the shared pipeline library is
> now using the artifact caching proxy.
>
> See https://github.com/jenkins-infra/helpdesk/issues/3369 for details
> about the artifact caching proxy use, and
> https://github.com/jenkins-infra/helpdesk/issues/2752 about its
> (re)introduction.
>
> As a consequence, you might notice additional log messages in your build
> logs if your pipelines are using this function (should concern less than
> ten repositories on the jenkinsci GitHub organisation)
>
> If you encounter any issue, please let us know by opening an help desk
> issue at https://github.com/jenkins-infra/helpdesk/issues/new/choose
>
> Kind regards,
>
> Hervé, for the Jenkins Infrastructure team
>
> --
> 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/CAL-LwjzxQd105KtR2qMy%3D8YNNx%3DxRR-THOeEPg%3DA1pwBd8iqCg%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_DuuNU19sSdDiTArQqoP2XP4ean4eqG4d4-vNmFD%3DKu2OPQ%40mail.gmail.com.

Press Contacts

['Gavin Mogan' via Jenkins Developers]

Re
https://github.com/jenkins-infra/jenkins.io/blob/master/content/press.adoc#press-contacts

I'm planning on a putting in a PR to remove myself from the contacts. In
the almost two years of me being on the list, i've never had a legitimate
email, its all spam about having sponsored posts.

I also think most (maybe 50%) of the people listed are no longer actively
engaged with the project, so probably not the best to a filter for press.

My vote is to just drop the contacts section and use the forum or
something. Private communication isn't really great for the projectanyways.

Gavin

-- 
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_DuuKa%2Boqh-O-xinqv1K2T%2BietBgtoNe%2B75Au2_mmvgZSkQ%40mail.gmail.com.

Re: How does /monitoring skip starting splash page?

['Gavin Mogan' via Jenkins Developers]

Can you share code? I would assume a root action with no auth wouldn't care
about ... wait when you say splash screen, do you mean the "jenkins is
starting up" or the "welcome wizard"? I would assume a root action wouldn't
care about the welcome wizard, but the starting up screen my only guess is
you have to have some sort of init hook that changes the order of things.

https://github.com/jenkinsci/prometheus-plugin/blob/master/src/main/java/org/jenkinsci/plugins/prometheus/rest/PrometheusAction.java
says unprotecetedrootaction, which probably means it doesn't wait for
auth/acl to startup

But these are just guesses

On Tue, Feb 7, 2023 at 11:47 AM Michael Carter 
wrote:

> Short version I've got a custom prometheus stats page for my plugin.  But
> I want to make it available early.  How does the /monitoring plugin skip
> the starting splash page?  Want to do the same thing?
>
> --
> 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/dc9615d5-8840-4c30-b3f2-da956124d281n%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/CAG%3D_Duu84SYmrCTGgbvoyN6w-8-puiAKEvZUAxv_cwuG_L7Wng%40mail.gmail.com.

Re: Renaming a plugin

['Gavin Mogan' via Jenkins Developers]

If it has spaces it's just the pretty name.

You can rename it with the  section of pom.xml then do a new release

On Wed, Dec 28, 2022, 4:18 AM Marit M  wrote:

> I'm pretty sure that the plugins have no users.
>
> Can you please guide how to do it, or maybe make the necessary changes in
> a different branch?
>
> The plugins that needs to be changed are:
>
>- BMC DevOps for CFA  > *BMC AMI DevOps for Application
>Checkpoint Analysis - *0 installs
>- BMC DevOps for AMI Change Manager for IMS TM > *BMC AMI DevOps
>for Change Manager for IMS TM - *2 installs
>
>
> Thank you,
> Marit.
> ב-יום רביעי, 21 בדצמבר 2022 בשעה 22:23:07 UTC+2, mc.ca...@gmail.com כתב/ה:
>
>> Great idea! I rejected PRs attempting to modify their path before.
>>
>> I submitted
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3047 to
>> make it obvious that altering specific components is highly discouraged.
>>
>> On Wednesday, 21 December 2022 at 17:45:20 UTC+1 jgl...@cloudbees.com
>> wrote:
>>
>>> On Sun, Dec 18, 2022 at 7:47 AM Alexander Brandes 
>>> wrote:
>>>
 take a look at the RPU documentation
 
  how
 to do that.

>>>
>>> I think this doc should be made to emphasize that you *really really*
>>> should not ever do this unless you are pretty sure your plugin has no users
>>> under its existing name.
>>>
>>> Changing the `name` (display name) is fine at any time. Changing the
>>> `groupId` will break any Maven dependencies from other plugins, which may
>>> or may not be an issue. But changing the `artifactId` means changing the
>>> identifier by which the Jenkins plugin manager differentiates this plugin
>>> from others, and will cause mayhem for users who have already installed it
>>> under the old name.
>>>
>> --
> 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/7f213569-8614-4223-839b-e8e106829ad8n%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/CAG%3D_Duu9N-9WSH%2BoToX6ffgDhk7nXW0WxOr-GAHjPgzHQAhvyg%40mail.gmail.com.

Re: Dec 12, 2022 Governance Board Agenda

['Gavin Mogan' via Jenkins Developers]

I slept in so I'm going to miss this one.

I have the previous minutes exported to markdown, but there's a debate
around repo name.

Otherwise I think I gave ulli and Alex all needed access.

I think that's my final action items

On Mon, Dec 12, 2022, 8:33 AM Mark Waite  wrote:

> The governance board meets today at 5:00 PM UTC.  Draft agenda is
> available in the meeting notes
> .
> All are welcome to attend.  See https://www.jenkins.io/events/
>
> Agenda:
>
>-
>
>News
>-
>
>   Jenkins 2.375.1 released Wednesday, Nov 30, 2022
>   -
>
>Action items
>-
>
>   Require active community/SIG/Office/board/etc. Members as manager
>   or owner for all project, SIG and community mailing lists - Alex
>   -
>
>   Create and hand out election nominee and voter badge for 2021 and
>   2022 elections on the forums - Alex
>   -
>
>  No badges have been handed out for 2021 elections - Didn’t we
>  want to do that?
>  -
>
>  Alex has no permissions to create new badges
>  -
>
>   Mark Waite create an empty agenda entry for the next meeting after
>   each meeting
>   -
>
>   Mark Waite submit jenkins.io pull request to combine subprojects
>   and SIGs into a single concept - “working groups”
>   -
>
>   Oleg Nenashev send proposal to Rick to retire the Chinese Jenkins
>   site
>   -
>
>   Mark Waite and Gavin Mogan archive the governance meeting notes to
>   a GitHub repository, use the Google doc as the working document, then
>   publish final notes
>   -
>
>  Agenda is published after the meeting in community.jenkins.io
>  -
>
> Historical copies are not on community.jenkins.io (don’t lose
> them)
> -
>
> Proposed using the agenda, once published to
> community.jenkins.io, remove from Doc
> -
>
>   Kevin Martens  to use community.jenkins.io for the Jenkins Docs SIG
>   mailing list
>   -
>
>   EasyCLA to be documented by Oleg
>   -
>
>   Mark Waite to propose a pull request documenting the web
>   application server policy
>   
> 
>   -
>
>  Done by Basil Crow (Thanks Basil)
>  -
>
>Elections
>-
>
>   Mark Waite opened Jenkins developer discussion of proposed rule
>   changes for next year
>   -
>
>  Allow up to 2 elected board members from a single company
>  
> 
>  -
>
>  GitHub pull request
>  
>  -
>
>Governance board meeting time and date - Mark Waite send a Doodle poll
>to board members and others that regularly attend board meeting
>-
>
>CDF Outreach Reboot
>-
>
>   Dec 14, 2022 10:30 AM EST meeting to restart the outreach committee
>   -
>
>CDF Topics -
>-
>
>Community forum - Gavin Mogan
>
> --
> 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/b26a5afe-04a5-465c-ad7a-bbeeecdc8538n%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/CAG%3D_DutJrQ5Ln3q3fKm%3Dz2GVgfkSf-YcmEmfURpkRA2aZ3dvwg%40mail.gmail.com.

Re: Servlet container support (was: Nov 28, 2022 Governance Board Agenda)

['Gavin Mogan' via Jenkins Developers]

I think slide has also found out that csrf tokens are also broken,
something about ips not being passed properly.

On Mon, Nov 28, 2022 at 8:47 AM 'Jesse Glick' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> On Mon, Nov 28, 2022 at 9:29 AM Mark Waite 
> wrote:
>
>> Mark Waite to propose a pull request documenting the web application
>> server support policy […]
>>
>>-
>>   -
>>  -
>>
>>  Many people are saying that “should work” but we don’t test them
>>  […]
>> -
>>
>> All web containers moved to tier 2 except bundled web
>> container
>>
>>
> Not sure if there was a thread somewhere in which this topic was discussed
> in writing, but my personal recommendation would be to formally drop
> support for running in a general servlet container, so that you could only
> use the bundled Winstone/Jetty via `java -jar jenkins.war` (we could even
> drop aspects of the WAR packaging not needed by `executable.Main`).
>
> The obvious thing that does not work in other containers is WebSocket
> support:
> https://github.com/jenkinsci/jep/blob/master/jep/222/README.adoc#non-jetty-containers
>
> I do not agree that the situation is analogous to the web browser, OS, or
> Java support policy. We do not bundle a pretested web browser, JVM, or
> operating system with Jenkins (except insofar as the latter two are
> supplied by the Docker image).
>
> --
> 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/CANfRfr15_NQxx4k_dOawaPx%2B5MnhL4BaUJOPvB%2BptQ06NN%2BSwA%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_DuujppbcfCVNfYNsK6UsOm6i0RG0_Qj8tzK8L8hWSwtivQ%40mail.gmail.com.

Re: Pipeline scoped to its subdirectory/branch in a (mono)repo

['Gavin Mogan' via Jenkins Developers]

We generally don't discuss how to use jenkins on the developers mailing
list. This is for managing the project itself. If you want to develop a
plugin this is the right place to ask.

There is the users mailing list, community forums, or the chatrooms for
more usage help.

On Sat, Nov 5, 2022 at 8:53 AM firm...@gmail.com  wrote:

> What is Jenkins' answer to the following GitHub Actions' featureset
>
> When using the push and pull_request events, you can configure a
> pipeline/workflow to run based on what file paths are changed. Path filters
> are not evaluated for pushes of tags.
>
>
> https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore
>
> When using the pull_request and pull_request_target events, you can
> configure a pipeline/workflow to run only for pull requests that target
> specific branches.
>
>
> https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore
>
>
>
>
>
>
> --
> 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/6d958dec-9c34-4443-a99b-a60355f988e5n%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/CAG%3D_DuvnzXkQTz0cRLRdXv4sPFS73w7bJDwKu9HmwddfA1tg%2Bw%40mail.gmail.com.

Re: Plugin is shown as released but not visible on Jenkins plugins page

['Gavin Mogan' via Jenkins Developers]

Plugins.jenkins.io gets generated every 3 hours. You should be able to see
the last run timestamp in the footer.
It depends on other jobs and other reports.

Realistically it should be less than 3 hours but with all the moving parts
I wouldn't be concerned until 6 hour mark

On Fri, Nov 4, 2022, 7:53 AM 'Michael Dailey' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Thanks for the prompt response, Mark. That makes sense... I will exercise
> some patience here then. I was not aware of the release delay. Does this
> also apply to updates made in future releases or just the initial release?
>
> Thank you,
> Michael
>
> On Friday, November 4, 2022 at 9:51:09 AM UTC-5 Mark Waite wrote:
>
>> It can take 6-8 hours between the release of a plugin and its visibility
>> on plugins.jenkins.io.
>>
>> The plugin is listed on https://updates.jenkins.io/latest/ as well,
>> which confirms that the infrastructure knows about the plugin.
>>
>> On Friday, November 4, 2022 at 8:48:25 AM UTC-6
>> michael...@provartesting.com wrote:
>>
>>> Hello all,
>>>
>>> I recently got my first Jenkins plugin through approvals and have set up
>>> CD for it. I created a PR and performed a merge manually to trigger the
>>> release process.
>>> I can see on the repo home here
>>>  that it has
>>> successfully created an automated release. However, the plugin itself is
>>> not visible from the available plugins yet or listed here: Search
>>> Results | Jenkins plugin
>>> 
>>> I do see it on the Artifactory page
>>> ,
>>> and I believe I have followed all of the necessary steps to release the
>>> plugin.
>>>
>>> Am I missing something obvious here or is there an hourly sync that
>>> takes place and I just need to be patient?
>>>
>>> Thank you,
>>> Michael
>>>
>> --
> 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/fca5658e-c8b3-403f-ac6d-416f01200438n%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/CAG%3D_Duv4mrriRWYeyjtvQpnD4jCDhjBdtSSWciYK51Gomx8iVQ%40mail.gmail.com.

Re: Folder Credential by credentialId not found using credentials API

['Gavin Mogan' via Jenkins Developers]

Its been a long time since i touched this api, but wouldn't you want
return findCredentials(credentialsId, Jenkins.get());
not null?

On Sun, Oct 30, 2022 at 1:34 PM Arnold van Wijnbergen 
wrote:

> Hi Jenkins Developers,
>
> We are currently busy with adding a new feature to OSS code signing
> plugin. In the current situation we store credentials (username/password)
> as global in Jenkins as credentials provider. For this we use the
> credentials plugin.
>
> This works well, but we want to improve this to support
> FolderCredentialsProvider used in combination with the Role strategy
> plugin.  Currently this works okay.
>
> 1) First step we moved UI code  to the simplebuildStep. This works and we
> can choose and save the folder based 'global' credential. We can see this
> credential in the dropdown list. So this UI and persistence part works.
>
> Now the second part is where we see some problems occur when we execute
> the job. The job is inside the folder we created the credentials.
>
> 2) When we now execute the job we use following code to lookup the
> credential by credentialId.
>
>  @Nullable
> public static StandardUsernamePasswordCredentials
> findCredentials(String credentialsId) {
> return findCredentials(credentialsId, null);
> }
>
> @Nullable
> public static StandardUsernamePasswordCredentials
> findCredentials(String credentialsId, Item item) {
> if (StringUtils.isBlank(credentialsId)) {
> return null;
> }
> return CredentialsMatchers.firstOrNull(
> CredentialsProvider.lookupCredentials(
> StandardUsernamePasswordCredentials.class,
> item,
> ACL.SYSTEM,
> Collections.emptyList()),
> CredentialsMatchers.allOf(
> CredentialsMatchers.withId(credentialsId),
> CredentialsMatchers.anyOf(
>
> CredentialsMatchers.instanceOf(StandardUsernamePasswordCredentials.class;
> }
>
> This code executes but throws an exception (as defined by us) that  the
> credentialID is not found. I can see that this ID corresponds to the folder
> based credential.
>
> When updating the configuration with a Jenkins global credential
> everything works.
>
> To summarise : Seems that we currently still only can see Jenkins global
> credentials instead of folder global credentials we want to include as well.
>
> We already tried to look deeper into credentials API, but don't find a
> good hint, so looking for a suggestion here. The job is started by an admin
> user and running as SYSTEM.
>
> How can we include both Jenkins and folder provider credentials in the
> lookup, so both can be matched ? Currently the folder credentials are not
> found.
>
> Any help here is welcome. I think we just oversee something here
>
>
> --
> 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/a33f9274-b484-4f74-ae0d-384c0ff3ba85n%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/CAG%3D_DutXtca99WrHnwBQuBfq%2Buzi4%3DP7NkKeV6eX9u6TziQzSg%40mail.gmail.com.

Oct 31st Governance Board Agenda

['Gavin Mogan' via Jenkins Developers]

As with last time, I welcome all who want to come (see
https://www.jenkins.io/events/), and anyone who wants to add topics to the
agenda (see https://www.jenkins.io/project/governance-meeting/).


Agenda as it stands today:

   -

   News
   -

  LTS 2.361.3 will release November 2, 2022
  -

   Action items
   -

  Mark Waite to use community.jenkins.io for the Jenkins Docs SIG
  mailing list
  -

 Announce the change and make the existing list read-only
 -

 Gavin investigated importing a mailing list, export is easy,
 import requires that we ask for help from the Discourse,
complicated set of
 steps
 -

Not worth the effort
-

  EasyCLA needs to be documented by Oleg
  -

 No new news this week
 -

 Needs to discuss more with linux foundation before writing up docs
 -

   Upcoming elections
   -

  Current proposal
  

  for Elections by Damien, want to confirm timeline/key dates &
open positions
  -

  December for completion
  -

  Gavin and Ewelina up for re-election
  -

   CDF topics - Oleg
   -
  -

   Forums and community topics - Gavin
   -

  Hacktoberfest is continuing

-- 
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_DuvnK22TE%3DbJCSQDGCJ4pgQM64ef0w%2BYSROOwSwb9%2B_Rhg%40mail.gmail.com.

Re: Jenkins Wiki CSS issues

['Gavin Mogan' via Jenkins Developers]

So we were able to deploy my new web component to this, so now
wiki.jenkins.io has our standard nav bar / toolbar on every page, should
help get people to the right place (www.jenkins.io).

On Thu, Oct 6, 2022 at 4:25 AM Alexander Brandes 
wrote:

> Nice work everyone, the banner is really suitable!
>
> On Thursday, 6 October 2022 at 13:09:11 UTC+2 jamie...@gmail.com wrote:
>
>> Great stuff, thanks for picking this up!
>>
>> On Thu, 6 Oct 2022, 11:52 'Herve Le Meur' via Jenkins Developers, <
>> jenkin...@googlegroups.com> wrote:
>>
>>> The version with the deprecation banner has been deployed:
>>> https://wiki.jenkins-ci.org/JENKINS/index.html
>>>
>>> --
>>>
>> 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/c01fa1b6-20bb-4c29-9eb2-6667fc3f89e1n%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/c5e02491-dfbb-4fb7-9a62-abaf25b0d5dfn%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/CAG%3D_DutaF6Qvm_J53_JU5M%2Bt%2BgkXghuAzU8c17vrU%2BbSckJDJw%40mail.gmail.com.

Re: How to create a release of one plugin?

['Gavin Mogan' via Jenkins Developers]

Looks like your build did not pass CI

https://github.com/jenkinsci/basic-branch-build-strategies-plugin/runs/8964092869

says something about a junit test failing.

Following it to ci.jenkins.io, and looking at the test results, it says the
FormBindingTest test is failing.
https://ci.jenkins.io/job/Plugins/job/basic-branch-build-strategies-plugin/job/master/59/testReport/jenkins.branch.buildstrategies.basic/FormBindingTest/windows_8___Build__windows_8jenkins_branch_buildstrategies_basic_FormBindingTest/

If jenkins can't finish the build, it won't be doing a release.

On Tue, Oct 18, 2022 at 10:32 AM Jack Zhang  wrote:

> Hi all,
>
> I struggled to create a new release for this plugin,
> https://github.com/jenkinsci/basic-branch-build-strategies-plugin. But
> failed.
>
> https://github.com/jenkinsci/basic-branch-build-strategies-plugin/releases/tag/67.va_92d1fcf98f2
>
> Do I need to download the artifacts in incrementals repo and deploy them
> in release repo manually?
>
> Could you give me some suggestions?
>
> I have enabled cd following this guide,
> https://www.jenkins.io/doc/developer/publishing/releasing-cd/. And it did
> publish the artifacts to
> https://repo.jenkins-ci.org/ui/repos/tree/General/incrementals/org/jenkins-ci/plugins/basic-branch-build-strategies/67.va_92d1fcf98f2
> .
>
> But it cannot be detected by Jenkins plugin update center. I compared with
> credentials plugin, and find there are credentials artifacts created in
> release repository as well.
>
> https://repo.jenkins-ci.org/ui/artifactSearchResults?name=credentials-1189.vf61b_a_5e2f62e.hpi=artifacts
>
> I tried to go through the source code of credentials plugin, there is no
> difference from basic-branch-build-strategies plugin.
>
> https://github.com/jenkinsci/credentials-plugin/blob/master/.github/workflows/cd.yaml
>
> https://github.com/jenkinsci/basic-branch-build-strategies-plugin/tree/master/.github/workflows
>
> Thanks for your time.
>
>
> --
> 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/364fc357-4fc6-4724-b3d6-f56bf8301d94n%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/CAG%3D_Dut1qFDXd5VF%3DcdjVROOhEyWqduuozOnwC%3DhMU9nqqc3mA%40mail.gmail.com.

Re: Proposal: Alexander Brandes (@NotMyFault) to join the Core team

['Gavin Mogan' via Jenkins Developers]

Nobody on the governance meeting was against it

On Mon, Oct 17, 2022 at 10:14 AM Oleg Nenashev 
wrote:

> +1, thanks for all contributions @NotMyFault!
>
> P.S: On behalf of the exclusive weekly release trainwreck club, please
> make sure to tweet "Not my fault" the first time you break the weekly
> release :P
>
>
> On Saturday, October 15, 2022 at 7:58:15 PM UTC+2 adrien.lec...@gmail.com
> wrote:
>
>> of course +1.
>>
>>
>> Le sam. 15 oct. 2022 à 18:31, Alexander Brandes  a
>> écrit :
>>
>>> Thanks everyone, I'd be very happy to join the core team :)
>>>
>>> On Friday, 14 October 2022 at 13:48:48 UTC+2 hle...@cloudbees.com wrote:
>>>
 +1

 On Fri, Oct 14, 2022 at 1:18 PM James Nord  wrote:

> +1
>
> On Thu, 13 Oct 2022 at 20:16, Pedro Amaral  wrote:
>
>> +1
>>
>> On Thu, Oct 13, 2022 at 10:12 AM 'Kevin Martens' via Jenkins
>> Developers  wrote:
>>
>>> +1 from me too!
>>>
>>> On Thu, Oct 13, 2022 at 5:52 AM 'Olblak' via Jenkins Developers <
>>> jenkin...@googlegroups.com> wrote:
>>>
 +1  :)

 On Thu, Oct 13, 2022, at 11:39 AM, 'Stephane Merle' via Jenkins
 Developers wrote:

 +1 for me too
 good luck Alexander

 On Thu, Oct 13, 2022 at 9:44 AM 'Daniel Beck' via Jenkins
 Developers  wrote:



 On Thu, Oct 13, 2022 at 9:11 AM Tim Jacomb 
 wrote:

 I would like to propose Alexander Brandes (@NotMyFault
 ) to join the Jenkins Core team.


 +1


 --
 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/CAMo7PtJFQvvfqtNixCGOk34quz7Fm_bu0as_QNOVxX%2BXY5jvwA%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-de...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CAO%2B-N1qxoBRFwKk4%3DJdVY%2B_gns%2BCaMd8J_DC9xuWnRqzEfYDZA%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-de...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/b67d978b-bc39-4cb4-a2a3-3ad69cdf621c%40app.fastmail.com
 
 .

>>>
>>>
>>> --
>>> Kevin Martens
>>> Technical Content Developer
>>> CloudBees, Inc.
>>>
>>>
>>> E: kmar...@cloudbees.com
>>>
>>> Pronouns: He/Him/His
>>>
>>> --
>>> 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/CAP92yNdJ5WrfjJith1bzawZiEsEJw%2BhG4SDv6GxLhVHT6fmjGA%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-de...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAHnkEpkxT9pBagcAJszwL5Pw5RoSp26myuBC4sntO-GAq5J2sg%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because 

Re: Jenkins Governance Meeting - Oct 17

['Gavin Mogan' via Jenkins Developers]

Last call for topics (except ones added during the meeting)

On Thu, Oct 13, 2022 at 11:51 AM Gavin Mogan  wrote:

> As Mark is away for the next meeting, I'm chairing it. I don't have the
> breath of insight into the project that mark does, so I'm calling on
> officers, sig leads and other board members to add any topics worth
> mentioning/discussing.
>
> Thanks,
>
> Gavin
>
> At time of writing, I have:
> https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#
> October 17, 2022
>
> Recording:
>
> Participants:
>
> Agenda:
>
>-
>
>News
>-
>
>Action items
>-
>
>   Mark Waite to use community.jenkins.io for the Jenkins Docs SIG
>   mailing list
>   -
>
>  Announce the change and make the existing list read-only
>  -
>
>  Gavin investigated importing a mailing list, export is easy,
>  import requires that we ask for help from the Discourse, complicated 
> set of
>  steps
>  -
>
> Not worth the effort
> -
>
>   EasyCLA needs to be documented by Oleg
>   -
>
>Upcoming elections
>-
>
>   December for completion
>   -
>
>   Gavin and Ewelina up for re-election
>   -
>
>CDF topics - Oleg
>-
>   -
>
>Forums and community topics - Gavin
>-
>
>   Hacktoberfest is continuing
>   -
>
>  JMM has been keeping stats (fill in around meeting start time)
>
>

-- 
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_DuuKYeTrzD3BU8CPcBxp%3D%2BtfpwZi0ho2wa1btYbbHyfKtw%40mail.gmail.com.

Jenkins Governance Meeting - Oct 17

['Gavin Mogan' via Jenkins Developers]

As Mark is away for the next meeting, I'm chairing it. I don't have the
breath of insight into the project that mark does, so I'm calling on
officers, sig leads and other board members to add any topics worth
mentioning/discussing.

Thanks,

Gavin

At time of writing, I have:
https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#
October 17, 2022

Recording:

Participants:

Agenda:

   -

   News
   -

   Action items
   -

  Mark Waite to use community.jenkins.io for the Jenkins Docs SIG
  mailing list
  -

 Announce the change and make the existing list read-only
 -

 Gavin investigated importing a mailing list, export is easy,
 import requires that we ask for help from the Discourse,
complicated set of
 steps
 -

Not worth the effort
-

  EasyCLA needs to be documented by Oleg
  -

   Upcoming elections
   -

  December for completion
  -

  Gavin and Ewelina up for re-election
  -

   CDF topics - Oleg
   -
  -

   Forums and community topics - Gavin
   -

  Hacktoberfest is continuing
  -

 JMM has been keeping stats (fill in around meeting start time)

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

Re: Adoption Maintenance plug-in upload-pgyer-plugin

['Gavin Mogan' via Jenkins Developers]

Adding the maintainer to the thread

On Tue, Oct 11, 2022, 8:06 p.m. '◇╭ァ傷℡↙' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> pgyer official wants to maintain the uploading-PGyer-plugin, which needs
> to be updated due to the update of pgyer's official api. However, pgyer
> submitted PR but failed to get the control's maintainer to merge and
> update, and contacted the plug-in developer, but no response was received.
> jenkins plugin could not be updated officially, so it was proposed to adopt
> and maintain the plugin
>
>
> Plug-in link:  https://github.com/jenkinsci/upload-pgyer-plugin
>
>
> Plug-in state: adoption
>
>
> pull requests: https://github.com/jenkinsci/upload-pgyer-plugin/pull/5
>
>
> GitHub id: https://github.com/manongxiaoyun
>
>
> Jenkins infrastructure account id: Caoxy
>
>
> Repository Permission Update link:
> https://github.com/jenkins-infra/repository-permissions-updater/pull/2841
>
>
>
> thanks
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/tencent_B7A668B4BEA67B578A8CCA81B9ABEAECD305%40qq.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_DuswzEw1VxYW%2BiEB%2ByP2R7WH0cTdOepyuJpL7WrM5w-KZg%40mail.gmail.com.

Re: Hosting

['Gavin Mogan' via Jenkins Developers]

I think you'll have to request via helpdesk permissions for
https://github.com/orgs/jenkins-infra/teams/hosting/members

On Sun, Oct 9, 2022 at 9:07 AM Alexander Brandes 
wrote:

> Hey,
>
> I'd be up to assist with handling the RPU too.
>
> Best regards,
> Alex
>
> On Sunday, 9 October 2022 at 17:53:13 UTC+2 slide wrote:
>
>> I can help with that. I know the process is different from when I was
>> doing it before, but I can come up to speed.
>>
>> On Sat, Oct 8, 2022, 21:11 'Gavin Mogan' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>>> I'm looking for someone interested in replacing me. Right now it seems
>>> to just be tim and myself. Tim's been amazing and processing all the new
>>> plugin requests. Wrote tooling to help verify things, etc. He's already
>>> doing a ton of other things, so I've been trying to help out with the
>>> maintainer change request approvals, but the process is so fuzzy its just
>>> draining me, which dumps more on him.
>>>
>>> The job entails monitoring PRs on
>>> https://github.com/jenkins-infra/repository-permissions-updater
>>> Making sure the request is either approved from an existing maintainer,
>>> the plugin is labeled adopt this plugin, or the takeover process has been
>>> followed.
>>>
>>> Gavin
>>>
>>> On Thu, Aug 26, 2021 at 2:24 AM Baptiste Mathus  wrote:
>>>
>>>> I am ready to help again on hosting.
>>>>
>>>> Similar to how Gavin phrased it, I'll help move tickets through the
>>>> pipe.
>>>>
>>>> Cheers
>>>>
>>>> Le jeu. 26 août 2021 à 08:23, Tim Jacomb  a écrit :
>>>>
>>>>> You can just click leave team
>>>>>
>>>>> On Wed, 25 Aug 2021 at 22:33, Slide  wrote:
>>>>>
>>>>>> I should probably be removed from that team as well.
>>>>>>
>>>>>> On Wed, Aug 25, 2021 at 1:18 PM Tim Jacomb 
>>>>>> wrote:
>>>>>>
>>>>>>> Oleg has permissions on the team or Olivier:
>>>>>>> https://github.com/orgs/jenkins-infra/teams/hosting/members
>>>>>>>
>>>>>>>
>>>>>>> On Wed, 25 Aug 2021 at 21:03, Slide  wrote:
>>>>>>>
>>>>>>>> Those are the basics, just the bot checker (jenkins-admin: check
>>>>>>>> HOSTING-) in the jenkins-hosting channel.
>>>>>>>>
>>>>>>>> On Wed, Aug 25, 2021 at 12:20 PM 'Gavin Mogan' via Jenkins
>>>>>>>> Developers  wrote:
>>>>>>>>
>>>>>>>>> Okay, making it official. If nobody else speaks up as wanting to
>>>>>>>>> take over as lead before end of week (Friday night pacific time) I'll 
>>>>>>>>> take
>>>>>>>>> over and make sure hosting requests get moving.
>>>>>>>>>
>>>>>>>>> I think i've fixed my irc client so I should stay in the channels
>>>>>>>>> now.
>>>>>>>>> Can I get invited to the hosting github teams as well?
>>>>>>>>>
>>>>>>>>> Is there anything else that might be needed for transition?
>>>>>>>>>
>>>>>>>>> Gavin
>>>>>>>>>
>>>>>>>>> On Wed, Aug 25, 2021 at 8:07 AM wfoll...@cloudbees.com <
>>>>>>>>> wfoll...@cloudbees.com> wrote:
>>>>>>>>>
>>>>>>>>>> Thank you very much Alex for the effort you invested on this
>>>>>>>>>> area. This is a really important piece of the process for the 
>>>>>>>>>> security
>>>>>>>>>> perspective. The fact that you did the preliminary security checks 
>>>>>>>>>> and if
>>>>>>>>>> something was weird, to ask the security team to make a more complete
>>>>>>>>>> audit, was of a great help for us.
>>>>>>>>>>
>>>>>>>>>> I cannot ask you Gavin to do more than what you are proposing to
>>>>>>>>>> do as if you are not proposing this it will be mainly nothing being 
>>>>>>>>>> done,
>>>>>>>>

Re: Hosting

['Gavin Mogan' via Jenkins Developers]

I'm looking for someone interested in replacing me. Right now it seems to
just be tim and myself. Tim's been amazing and processing all the new
plugin requests. Wrote tooling to help verify things, etc. He's already
doing a ton of other things, so I've been trying to help out with the
maintainer change request approvals, but the process is so fuzzy its just
draining me, which dumps more on him.

The job entails monitoring PRs on
https://github.com/jenkins-infra/repository-permissions-updater
Making sure the request is either approved from an existing maintainer, the
plugin is labeled adopt this plugin, or the takeover process has been
followed.

Gavin

On Thu, Aug 26, 2021 at 2:24 AM Baptiste Mathus  wrote:

> I am ready to help again on hosting.
>
> Similar to how Gavin phrased it, I'll help move tickets through the pipe.
>
> Cheers
>
> Le jeu. 26 août 2021 à 08:23, Tim Jacomb  a écrit :
>
>> You can just click leave team
>>
>> On Wed, 25 Aug 2021 at 22:33, Slide  wrote:
>>
>>> I should probably be removed from that team as well.
>>>
>>> On Wed, Aug 25, 2021 at 1:18 PM Tim Jacomb  wrote:
>>>
>>>> Oleg has permissions on the team or Olivier:
>>>> https://github.com/orgs/jenkins-infra/teams/hosting/members
>>>>
>>>>
>>>> On Wed, 25 Aug 2021 at 21:03, Slide  wrote:
>>>>
>>>>> Those are the basics, just the bot checker (jenkins-admin: check
>>>>> HOSTING-) in the jenkins-hosting channel.
>>>>>
>>>>> On Wed, Aug 25, 2021 at 12:20 PM 'Gavin Mogan' via Jenkins Developers <
>>>>> jenkinsci-dev@googlegroups.com> wrote:
>>>>>
>>>>>> Okay, making it official. If nobody else speaks up as wanting to take
>>>>>> over as lead before end of week (Friday night pacific time) I'll take 
>>>>>> over
>>>>>> and make sure hosting requests get moving.
>>>>>>
>>>>>> I think i've fixed my irc client so I should stay in the channels now.
>>>>>> Can I get invited to the hosting github teams as well?
>>>>>>
>>>>>> Is there anything else that might be needed for transition?
>>>>>>
>>>>>> Gavin
>>>>>>
>>>>>> On Wed, Aug 25, 2021 at 8:07 AM wfoll...@cloudbees.com <
>>>>>> wfollon...@cloudbees.com> wrote:
>>>>>>
>>>>>>> Thank you very much Alex for the effort you invested on this area.
>>>>>>> This is a really important piece of the process for the security
>>>>>>> perspective. The fact that you did the preliminary security checks and 
>>>>>>> if
>>>>>>> something was weird, to ask the security team to make a more complete
>>>>>>> audit, was of a great help for us.
>>>>>>>
>>>>>>> I cannot ask you Gavin to do more than what you are proposing to do
>>>>>>> as if you are not proposing this it will be mainly nothing being done, 
>>>>>>> so
>>>>>>> anything is better than nothing :-) In the case where you are not sure
>>>>>>> about a plugin, if you are seeing something weird, do not hesitate to 
>>>>>>> ping
>>>>>>> Daniel Beck and me in the HOSTING ticket, requesting an audit from us.
>>>>>>>
>>>>>>> Wadeck
>>>>>>>
>>>>>>> On Wednesday, August 25, 2021 at 5:58:20 AM UTC+2
>>>>>>> ga...@gavinmogan.com wrote:
>>>>>>>
>>>>>>>> If nobody else is able to step up, I can take it, but I won't be
>>>>>>>> code reviewing and as quickly as possible switch it from jira+irc to
>>>>>>>> https://github.com/jenkins-infra/repository-permissions-updater +
>>>>>>>> issue bot
>>>>>>>> All i'll be doing is "Is there another plugin that sounds similar?
>>>>>>>> Does it pass the checks? approved"
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Aug 24, 2021 at 8:21 PM Slide  wrote:
>>>>>>>>
>>>>>>>>> Hi Everyone,
>>>>>>>>>
>>>>>>>>> I sent the group an email a while back about not having time for
>>>>>>>>> managing hosting requests and was looking for someone to step up and 
>>>>

Re: Jenkins Wiki CSS issues

['Gavin Mogan' via Jenkins Developers]

I kinda like it unstyled. It highlights the wiki is old and "broken" (it's
now just a bunch of static files in. GitHub repo)

On Mon, Oct 3, 2022, 3:46 a.m. Jamie Tanna  wrote:

> Hey folks,
>
> Not sure if I've missed a conversation elsewhere, but looks like, in
> Firefox (Nightly 104.0a1 (2022-07-13) (64-bit)) the CSS on the Wiki is
> broken.
>
> There's a browser warning:
>
> > The stylesheet
> https://wiki.jenkins-ci.org/display/JENKINS/styles/site.css was not
> loaded because its MIME type, “text/plain”, is not “text/css”.
>
> Also seeing this on Chromium (Version 105.0.5195.102 (Official Build))
>
> Thought I'd flag it for visibility if no one's reported / aware of it.
>
> --
> 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/f30a8a0f-6435-4926-9568-bf1b94eabae6n%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/CAG%3D_DuusL2Kh4pPwCbWrPfyZAO3%3DjT1SRxhbK-%3Dz8CRcqi%2BP2w%40mail.gmail.com.

Re: Hacktoberfest Preptember

['Gavin Mogan' via Jenkins Developers]

NM, that tool no longer works. I will try to fix it up when i have a minute.

On Thu, Sep 29, 2022 at 12:00 PM Gavin Mogan  wrote:

> For anyone who is maintaining an older repo that doesn't have all the
> "newer" labels synced up (great for the default release drafter setup)
>
> I have https://plugins-self-service-3ir4b.ondigitalocean.app/ which can
> copy labels from  (Huh, the PR never got merged, but
> https://github.com/jenkinsci/.github/pull/27 pr which has all the
> standard labels)
>
> On Thu, Sep 29, 2022 at 10:20 AM Jean-Marc Meessen <
> jean-m...@meessen-web.org> wrote:
>
>> Hi Jamie,
>>
>> Thank you to point this out: obviously the opt-in requirement has been
>> relaxed. The exact wording is
>>
>> *YOUR PR/MRS MUST BE IN A REPO TAGGED WITH THE “HACKTOBERFEST” TOPIC, OR
>> BE LABELED “HACKTOBERFEST-ACCEPTED.”*
>> *Hacktoberfest is now opt-in for maintainers, so only contribute to
>> projects that indicate they’re looking for Hacktoberfest PR/MRs.*
>>
>>
>>
>> *Once your PR/MR has passed this check, we won’t check this again (unless
>> your PR/MR fails a check before this, such as it being marked as
>> spammy).(in https://hacktoberfest.com/participation/#pr-mr-details
>> )*
>>
>> There is also "*Add the “hacktoberfest” topic to your repository to
>> OPT-IN TO HACKTOBERFEST and indicate you’re looking for contributions.*"
>>
>> But, as Jamie hints, it is important that maintainers monitor the
>> submitted PR to see whether they qualify for hacktoberfest and tag them
>> accordingly.
>>
>> /- Jmm
>>
>>
>>
>> Le jeu. 29 sept. 2022 à 12:59, Jamie Tanna  a
>> écrit :
>>
>>> And if anyone doesn't want to opt the whole repo in (maybe too much work
>>> required over the month) you can still tag PRs as `hacktoberfest-accepted`
>>> so it counts, but means fewer potential drive-by/low quality contributions
>>>
>>> On Thu, 29 Sept 2022, 17:45 Jean-Marc Meessen, <
>>> jean-m...@meessen-web.org> wrote:
>>>
 We are now at 109 participating repositories: 10 in the jenkins-infra org
 and 99 in the jenkinsci org.

 Are you sure that your project is counted? Are your proposed issues
 tagged?

 This is an example of an alternative query (requires GH): gh search
 repos --owner=jenkinsci --topic=hacktoberfest --include-forks=true  -L 150


 /- Jmm


 Le mer. 28 sept. 2022 à 14:01, Jean-Marc Meessen <
 jean-m...@meessen-web.org> a écrit :

> Hello,
>
> Just a friendly reminder: Hacktoberfest is getting closer everyday.
>
> We currently have 72 projects participating in the "jenkinsci" and the
> "jenkins-infra" organisation. Are you sure that your project is counted?
> Are your proposed issues tagged?
>
> To check if your repository is marked as participating, you can use
> this query:
> https://github.com/search?p=2=org%3Ajenkinsci+org%3Ajenkins-infra+org%3Astapler+topic%3Ahacktoberfest=Repositories
>
> /- Jmm
>
> Le lun. 19 sept. 2022 à 08:19, Jean-Marc Meessen <
> jean-m...@meessen-web.org> a écrit :
>
>> Hello,
>>
>>
>> As you know, Hacktoberfest  starts in
>> two weeks. And the Jenkins community will participate again
>>  in this
>> month-long celebration of open-source.
>>
>> As maintainer you can prepare by
>>
>>-
>>
>>Reviewing and flag issues on your repos (hacktoberfest and/or
>>newbie-friendly)
>>-
>>
>>Flagging your repositories as accepting pull requests counting
>>for Hacktoberfest. This year is explicit "opt in". You can do this by
>>adding the topic "hacktoberfest" to your GitHub repository.
>>
>>
>> As usual, be kind and remember how you felt with your first
>> contribution.
>>
>> During October, for Pull Requests to be counted towards the
>> hacktoberfest swag threshold, they must be flagged as "hacktoberfest",
>> merged or flagged as "hacktoberfest-approved" (if merge will happen 
>> later).
>>
>> If you feel that a PR is spammy or invalid, flag it as such. Any user
>> with two or more spammy PR/MRs will be disqualified.
>>
>> See the PR handling details on hacktoberfest.com
>> .
>>
>> /- Jmm
>>
>> Jean-Marc Meessen
>>
>> Jenkins developer relations
>>
>> --
 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/CABLvyXw5tHmg_QyNuhFccEfqWmtVdynuUFM495iiRZNn8fk80A%40mail.gmail.com
 

Re: Hacktoberfest Preptember

['Gavin Mogan' via Jenkins Developers]

For anyone who is maintaining an older repo that doesn't have all the
"newer" labels synced up (great for the default release drafter setup)

I have https://plugins-self-service-3ir4b.ondigitalocean.app/ which can
copy labels from  (Huh, the PR never got merged, but
https://github.com/jenkinsci/.github/pull/27 pr which has all the standard
labels)

On Thu, Sep 29, 2022 at 10:20 AM Jean-Marc Meessen <
jean-m...@meessen-web.org> wrote:

> Hi Jamie,
>
> Thank you to point this out: obviously the opt-in requirement has been
> relaxed. The exact wording is
>
> *YOUR PR/MRS MUST BE IN A REPO TAGGED WITH THE “HACKTOBERFEST” TOPIC, OR
> BE LABELED “HACKTOBERFEST-ACCEPTED.”*
> *Hacktoberfest is now opt-in for maintainers, so only contribute to
> projects that indicate they’re looking for Hacktoberfest PR/MRs.*
>
>
>
> *Once your PR/MR has passed this check, we won’t check this again (unless
> your PR/MR fails a check before this, such as it being marked as
> spammy).(in https://hacktoberfest.com/participation/#pr-mr-details
> )*
>
> There is also "*Add the “hacktoberfest” topic to your repository to
> OPT-IN TO HACKTOBERFEST and indicate you’re looking for contributions.*"
>
> But, as Jamie hints, it is important that maintainers monitor the
> submitted PR to see whether they qualify for hacktoberfest and tag them
> accordingly.
>
> /- Jmm
>
>
>
> Le jeu. 29 sept. 2022 à 12:59, Jamie Tanna  a
> écrit :
>
>> And if anyone doesn't want to opt the whole repo in (maybe too much work
>> required over the month) you can still tag PRs as `hacktoberfest-accepted`
>> so it counts, but means fewer potential drive-by/low quality contributions
>>
>> On Thu, 29 Sept 2022, 17:45 Jean-Marc Meessen, 
>> wrote:
>>
>>> We are now at 109 participating repositories: 10 in the jenkins-infra org
>>> and 99 in the jenkinsci org.
>>>
>>> Are you sure that your project is counted? Are your proposed issues
>>> tagged?
>>>
>>> This is an example of an alternative query (requires GH): gh search
>>> repos --owner=jenkinsci --topic=hacktoberfest --include-forks=true  -L 150
>>>
>>>
>>> /- Jmm
>>>
>>>
>>> Le mer. 28 sept. 2022 à 14:01, Jean-Marc Meessen <
>>> jean-m...@meessen-web.org> a écrit :
>>>
 Hello,

 Just a friendly reminder: Hacktoberfest is getting closer everyday.

 We currently have 72 projects participating in the "jenkinsci" and the
 "jenkins-infra" organisation. Are you sure that your project is counted?
 Are your proposed issues tagged?

 To check if your repository is marked as participating, you can use
 this query:
 https://github.com/search?p=2=org%3Ajenkinsci+org%3Ajenkins-infra+org%3Astapler+topic%3Ahacktoberfest=Repositories

 /- Jmm

 Le lun. 19 sept. 2022 à 08:19, Jean-Marc Meessen <
 jean-m...@meessen-web.org> a écrit :

> Hello,
>
>
> As you know, Hacktoberfest  starts in two
> weeks. And the Jenkins community will participate again
>  in this
> month-long celebration of open-source.
>
> As maintainer you can prepare by
>
>-
>
>Reviewing and flag issues on your repos (hacktoberfest and/or
>newbie-friendly)
>-
>
>Flagging your repositories as accepting pull requests counting for
>Hacktoberfest. This year is explicit "opt in". You can do this by 
> adding
>the topic "hacktoberfest" to your GitHub repository.
>
>
> As usual, be kind and remember how you felt with your first
> contribution.
>
> During October, for Pull Requests to be counted towards the
> hacktoberfest swag threshold, they must be flagged as "hacktoberfest",
> merged or flagged as "hacktoberfest-approved" (if merge will happen 
> later).
>
> If you feel that a PR is spammy or invalid, flag it as such. Any user
> with two or more spammy PR/MRs will be disqualified.
>
> See the PR handling details on hacktoberfest.com
> .
>
> /- Jmm
>
> Jean-Marc Meessen
>
> Jenkins developer relations
>
> --
>>> 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/CABLvyXw5tHmg_QyNuhFccEfqWmtVdynuUFM495iiRZNn8fk80A%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and 

So what to do with html5-notifier-plugin?

['Gavin Mogan' via Jenkins Developers]

:wave: hey ya'll

I have this plugin, one of the first I adopted, that hasn't worked for a
couple years now. The APIs changed and you couldn't create popups the same
anymore. I did convert it to html 5 notifications, which required https,
and I decided to switch it to the SSE library instead of polling.

But as I got closer to releasing it, the less comfortable I was with the
new dependency, especially since the library isn't really used outside of
blueocean (see https://plugins.jenkins.io/sse-gateway/#dependencies).

Then it broke for real with tables-to-div, and nobody really complained.
The one person that did decided they rather uninstall than help test a new
version.

Tonight I got curious, and tried it again. Somewhere along the lines the
javascript broke, but updating it to see-gateway 1.26 seemed to fix it.

So question for everyone, considering its been very broken for a while, is
it better to somehow depreciate the plugin, and archive it? Do the new
release with sse-gateway dependancy? Leave the PR open and make it
adopt-this-plugin? Some combo of things?

Gavin

-- 
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_Duu-4SgKHZgCHomEv55ZpGOv1AOiSJTdB-xhgGEP_8oK%3Dg%40mail.gmail.com.

Re: Request/How to send invite to join team?

['Gavin Mogan' via Jenkins Developers]

There's no officialness when it comes to managing those teams. There's some
proposals but nothing formalized yet.

You can either do one of 3 things.
1) Reply to the list with the new github username, and one of the hosting
team members can add it
2) You can create a ticket on https://github.com/jenkins-infra/helpdesk and
one of the hosting team or infra team members will take care of it.
3) You can submit a PR to
https://github.com/jenkins-infra/repository-permissions-updater/ which
manages release permissions, but we also give github permissions at the
same time.

Gavin

On Thu, Sep 15, 2022 at 1:17 PM 'jsupun' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> I'm looking to add a co-worker to "keeper-secrets-manager-plugin
> Developers." If I need to make a request, I'd like to send an email
> directly to a maintainer with the user's github account/email.
>
> Thanks,
> John
>
> --
> 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/30a399bd-059a-40af-becb-9c51735eb906n%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/CAG%3D_DusgXbihFR0c9et78EwQdvPrGkKou4NOVc13Uw5LeWvjiw%40mail.gmail.com.

Re: Trying to automate release of Plugin

['Gavin Mogan' via Jenkins Developers]

> I didn't know I needed a Jenkinsfile, or what it was for :)

Just for my curiosity, as a plugin maintainer, do you not know what a
jenkinsfile is for in general? or specifically in this context for your
plugin?

If in general, I would recommend reviewing the pipeline docs (
https://www.jenkins.io/doc/book/pipeline/) as it's a pretty core concept of
Jenkins these days.

If in this specific case \o/ is there anything that could be done to
improve this discoverability for you?


On Mon, Sep 12, 2022 at 12:02 PM Karl Henselin  wrote:

>
> Thanks so much all of you for your help!
> I didn't know I needed a Jenkinsfile, or what it was for :)
> I see that step running now when I make pull requests, and I think that CD
> will work too.
> I wouldn't have gotten it without your help!
> Thanks,
> Karl
> On Friday, September 9, 2022 at 3:09:01 PM UTC-5 ga...@gavinmogan.com
> wrote:
>
>> Looks like your plugin is pretty old. You may want to look through the
>> archetypes repo to see what other files you should bring in (like
>> incrementals)
>>
>>
>> https://github.com/jenkinsci/archetypes/blob/master/common-files/Jenkinsfile
>> is the standard jenkinsfile though
>>
>> I would recommend generating a new plugin via archetype, and then
>> comparing pom and other files.
>>
>> On Fri, Sep 9, 2022 at 11:21 AM 'Jesse Glick' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>>> On Fri, Sep 9, 2022 at 1:13 PM Karl Henselin  wrote:
>>>
 I followed the CD automation guide for Jenkins plugins, and I think
 that I was successful with all the steps.
 However, when I make a pull request, it never releases a new version.
 I tried running the CD job with debug logging turned on, but I can't
 understand the logs to know what might be wrong.

>>>
>>> `verify-ci-status` fails, because there is no CI status—you have no
>>> `Jenkinsfile`.
>>>
>>> --
>>> 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/CANfRfr0dJb684HVsg1ak%3DAmEkpQxnbvs%2B%3DTtkuqdqWapz1Jxxw%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/31d08e6c-d804-491b-9201-ff3566abb552n%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/CAG%3D_DuuZX9BcNvDNkK9zL%3DkRaJ6VA6AHAXfjhhX0Cd-TGhvLGA%40mail.gmail.com.

Re: Trying to automate release of Plugin

['Gavin Mogan' via Jenkins Developers]

Looks like your plugin is pretty old. You may want to look through the
archetypes repo to see what other files you should bring in (like
incrementals)

https://github.com/jenkinsci/archetypes/blob/master/common-files/Jenkinsfile
is the standard jenkinsfile though

I would recommend generating a new plugin via archetype, and then comparing
pom and other files.

On Fri, Sep 9, 2022 at 11:21 AM 'Jesse Glick' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> On Fri, Sep 9, 2022 at 1:13 PM Karl Henselin  wrote:
>
>> I followed the CD automation guide for Jenkins plugins, and I think that
>> I was successful with all the steps.
>> However, when I make a pull request, it never releases a new version.
>> I tried running the CD job with debug logging turned on, but I can't
>> understand the logs to know what might be wrong.
>>
>
> `verify-ci-status` fails, because there is no CI status—you have no
> `Jenkinsfile`.
>
> --
> 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/CANfRfr0dJb684HVsg1ak%3DAmEkpQxnbvs%2B%3DTtkuqdqWapz1Jxxw%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_Duv%2BvnO_xgSwqCjN6Zk6i42VwHJy_4mShWtUSaN%3DiQQEzw%40mail.gmail.com.

Re: Governance meeting - September 5, 2022

['Gavin Mogan' via Jenkins Developers]

Updating plugin governance to allow for 0 maintainers to be considered
adoptable - https://github.com/jenkins-infra/jenkins.io/pull/5416

On Mon, Sep 5, 2022 at 9:42 AM Mark Waite  wrote:

> Governance meeting starts in about 20 minutes at 5:00 PM UTC.   Agenda
> items
> 
>  include:
>
> Agenda:
>
>-
>
>News
>-
>
>   LTS 2.361.1 release September 7, 2022
>   - Action items
>   -
>
>  Mark Waite to find and finish Linux Foundation transfers from
>  GSoC 2021
>  - Mark Waite to use community.jenkins.io for the Jenkins Docs
>  SIG mailing list
>  - Mark Waite to create blog post summary of the Contributor
>  Summit at cdCon
>  -
>
>  Mark Waite request full access to the CDF Zoom account for
>  Jenkins
>  -
>
>   Upcoming elections
>   -
>
>  Timeline
>  - Prefer to use the same process as last year
>  -
>
> Register to vote at community.jenkins.io
> -
>
>Organize list of candidates
>-
>
> Voting through the Condorcet system at Cornell University
> -
>
>If hosting is needed outside the University, Gavin has
>access to resources
>-
>
>   CDF topics
>   -
>
>   Jenkins.io website improvements
>   -
>
>  Pipeline steps reference improvements from Google Summer of Code
>  -
>
>  Look and feel improvements from Jan Faracik
>  -
>
>   Forums and community topics
>
> --
> 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/146428f5-6e22-44c9-bb01-b49e6069c322n%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/CAG%3D_DuvcCAg550me5SNhirWxqGsSKMrY0jxwQUs26sZAK5jONg%40mail.gmail.com.

[Plugin development] output flushing for long running Launcher commands

['Gavin Mogan' via Jenkins Developers]

https://community.jenkins.io/t/plugin-development-output-flushing-for-long-running-launcher-commands/3395

-- 
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_DushYVfepevT-0Fp-kb7aUx4yxa-Y3No4XoOOVjkhYriTw%40mail.gmail.com.

Re: Change the root fork of an existing plugin

['Gavin Mogan' via Jenkins Developers]

You can ask github to break that link (so github doesn't say its forked),
and then your development can be on a fork.

You can probably ask them to change the source as well.

Advantage of jenkins being the source is that github search will work org
wide for it.

On Fri, Aug 26, 2022 at 9:07 AM Aurélien Bourdon 
wrote:

> Hello,
>
> We recently did some changes in our Github organisation (CerberusTesting
> ) and would like to spread changes to
> existing forks that now use deprecated root repositories, as our Jenkins
> plugin.
>
> The concerned plugin is the following:
> https://github.com/jenkinsci/cerberus-testing-plugin
> This plugin is a fork of the now deprecated
> https://github.com/abourdon/cerberus-jenkins-plugin repository.
>
> Would it be possible to re-recreate the repository by now forking the
> repository in the CerberusTesting organisation:
> https://github.com/cerberustesting/cerberus-cicd-jenkins-plugin?
> As this is not strictly a new plugin creation, and the
> identification/configuration is the same as the "previous" one, I guess
> it's possible to re-create the repo easily on your side?
>
> Thank you
> Aurélien
>
> --
> 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/ec2871eb-3f7a-4d6b-9a29-ec4894acf3c0n%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/CAG%3D_DuvgmpnfZqeetQOsgDBtd47JOUxa2t57DqwJefcZA2doTw%40mail.gmail.com.

Re: Maintainer access to UiPath plugin

['Gavin Mogan' via Jenkins Developers]

[image: image.png]
you should see a change in about an hour or so, as
https://reports.jenkins.io/maintainers.index.json seems to be updated

On Wed, Aug 24, 2022 at 10:07 PM Ganesh Borle 
wrote:

> Hi Basil,
>
> Thanks a lot :)
> Though, I have a question regarding the maintainers. I can still see the
> old names which should have been updated with my name, am I
> missing something for this update?
>
> Package Url: https://plugins.jenkins.io/uipath-automation-package/
> 
>
>
> [image: image.png]
>
> Thanks
> Ganesh B
>
> On Wed, Aug 24, 2022, 11:07 PM Basil Crow  wrote:
>
>> Hi Ganesh, looks like your permissions request was approved and merged
>> 2 hours ago. Welcome aboard!
>>
>> --
>> 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/bt-tkQSBIw8/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/CAFwNDjrkBRXRsJWs5-kNH069P2%2BvbKHiSpeaQo5UdPVUnM3J0g%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/CA%2B9cPEsLFwKzeR2t2vyyZi5OcSV0ab7CReUjcxFD7n6%3DCbSJ2w%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_DuuQOfXeqK6S4nvo3d8O3uSXRoDhSfaBQnEPR%2B2WHygz-g%40mail.gmail.com.

Re: Plugin adoption for remote-terminal-access

['Gavin Mogan' via Jenkins Developers]

Plugin is up for adoption, so no concerns from me. I'm going to go ahead
and merge the PR

On Tue, Aug 23, 2022 at 11:35 AM 'Kevin Martens' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hello there,
>
> I am looking to adopt the Remote Terminal Access plugin
> .
> It is currently up for adoption and has no maintainers at this time.
> My github username is kmartens27 / https://github.com/kmartens27
> My ci.jenkins.io is also kmartens27
> Here is the PR for the permissions updater,
> https://github.com/jenkins-infra/repository-permissions-updater/pull/2731
>
> Original maintainers: none currently listed.
>
> Other information:
>
> Hello,
>
> I'm looking to adopt the Remote Terminal Access plugin, so that I can work
> on modernizing and updating the plugin ahead of DevOps world. This would be
> two-fold, as it is also to ensure that the plugin adoption process is clear
> and thorough. Since the plugin is older and has a low count of installs, I
> thought it would be a good place to go through the modernization process
> without major interruptions.
>
> Please let me know if there's anything else needed before adopting
>
> Thanks!
> --
> Kevin Martens
> Technical Content Developer
> CloudBees, Inc.
>
>
> E: kmart...@cloudbees.com
>
> Pronouns: He/Him/His
>
> --
> 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/CAP92yNc4PAsxZa06KZT8FXwzPCZr4iJdjMLwjhDNbF7efiZKPQ%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_Duu677gzmQS6n-5cUUXNyN6huaowCXxcqSRiboEzxtxfXg%40mail.gmail.com.

Re: Plugin Adoption for kryptowire-plugin

['Gavin Mogan' via Jenkins Developers]

So what you've done is a start. You should be CC'ing any of the current
maintainers. Also recommend creating a PR or issue that tags them. Thirdly
make a PR
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-kryptowire.yml

Once that's all done, we wait 2 weeks for a response, if that times out,
then we go ahead and give you access.

> We are about to go through a re-branding process at our Company and have
iterated on the version of the Plugin the RedHat guys first developed,

Just be careful not to update the artifact id, otherwise it'll prevent
existing installs from upgrading.

On Thu, Aug 18, 2022 at 1:58 PM Chris Downey  wrote:

> Hello,
>
> I am reaching out to this Group email in the hopes of starting the
> Adoption process for the kryptowire-plugin in the jenkinsci Project.
> Relevant details are as follows.
>
> Plugin in jenkinsci repo:  https://github.com/jenkinsci/kryptowire-plugin
> Plugin on Plugins site:  https://plugins.jenkins.io/kryptowire/
> My ci.jenkins.io Username:  crdkw
> My Github Username:  cdowney-kryptowire
> Original Contributor Github Username:  odra
>
> Other Info:
>
> I am a Senior PM at Kryptowire.  We collaborated with some developers from
> RedHat for the initial version of the Plugin for which they were
> responsible engaging the project for acceptance and maintaining the first
> version.  My colleague CC’d here, Brian Schulte may be listed as an Admin
> for the Plugin, but I don’t think the process of transferring full
> ownership to us was ever completed after the Plugin was first developed in
> mid-2018.  We are about to go through a re-branding process at our Company
> and have iterated on the version of the Plugin the RedHat guys first
> developed, but without full ownership haven’t been able to update the
> official Jenkins version.
>
> Can you please let me know what the Adoption process should be to take
> full ownership of the project in jenkinsci?  If we need to, I can try to
> contact the original developers.
>
> Regards,
>
> Chris Downey
> Senior Product Manager
> E: cdow...@kryptowire.com
> M:+1 512.791.4315
>
> --
> 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/55D5672A-1303-4CDC-BEC8-1712C85E4B9B%40kryptowire.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_Duu4j5ShbTV7Usj9%3DnTeJJkYOztceijH1nFEZboFppBfug%40mail.gmail.com.

Re: Forked repositories in GitHub

['Gavin Mogan' via Jenkins Developers]

So it's just all the old repos at once they have issues with? They are
still okay with one off requests to fix a repo?

I wonder if they have a private API we could use that would prevent us from
having to download then upload to prevent the fork

On Tue, Aug 16, 2022, 10:42 p.m. Tim Jacomb  wrote:

> It currently still forks although there’s instructions telling people to
> delete their repo or raise a support ticket if it gets messed up
>
> On Wed, 17 Aug 2022 at 00:29, 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> This is a one time operation for all past repos? What happens to all the
>> new ones? Is the script pushing a new repo now (I forgot)?
>>
>> Totally on board with fixing all the old repos, not being able to search
>> them kinds sucks.
>>
>> On Tue, Aug 16, 2022 at 4:05 PM Mark Waite 
>> wrote:
>>
>>> +1 from me
>>>
>>> On Tue, Aug 16, 2022, 2:32 PM Tim Jacomb  wrote:
>>>
>>>> GitHub support have offered to make the jenkinsci organisation the root
>>>> of all of the fork networks
>>>>
>>>> See
>>>>
>>>> https://github.com/jenkins-infra/helpdesk/issues/2272#issuecomment-1216867119
>>>>
>>>>
>>>> Any objections or +1s?
>>>>
>>>> Thanks
>>>> Tim
>>>>
>>>> On Wed, 4 Aug 2021 at 16:52, Tim Jacomb  wrote:
>>>>
>>>>> I replied with Daniel's support ticket number (569994)
>>>>>
>>>>> and got this back:
>>>>>
>>>>> Hi Tim,
>>>>>
>>>>> Thanks for your patience here. I checked internally once more and
>>>>> found that we can, in fact, do this for you. We've gone ahead and detached
>>>>> the repository into its own fork network.
>>>>>
>>>>> Feel free to reach out if you have any additional questions about this!
>>>>>
>>>>> On Wed, 28 Jul 2021 at 17:38, Slide  wrote:
>>>>>
>>>>>> It would be super ideal to do transferring if we could figure out a
>>>>>> good process for it, we lose GitHub Issues and some other things when we
>>>>>> fork as is.
>>>>>>
>>>>>> On Wed, Jul 28, 2021 at 8:33 AM Tim Jacomb 
>>>>>> wrote:
>>>>>>
>>>>>>> Wouldn't creating a repo and pushing the code instead of forking
>>>>>>> work during the hosting process?
>>>>>>>
>>>>>>>
>>>>>>> On Wed, 28 Jul 2021 at 15:02, Jesse Glick 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> On Wed, Jul 28, 2021 at 2:48 AM timja...@gmail.com <
>>>>>>>> timjaco...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Seem's like GitHub won't break the fork relationship anymore
>>>>>>>>> without both sides agreeing to it?
>>>>>>>>>
>>>>>>>>
>>>>>>>> This could be a real problem for us. We still have a bunch of repos
>>>>>>>> with misleading fork status, like
>>>>>>>> https://github.com/jenkinsci/plugin-pom rather prominently. There
>>>>>>>> should be some provision by which a “fork” which has way more activity 
>>>>>>>> than
>>>>>>>> the “origin” can unilaterally break the relationship. Of course you can
>>>>>>>> delete and recreate the repo with Git history intact but you will lose 
>>>>>>>> all
>>>>>>>> PR history, which is intolerable.
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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/SkKoCccPrOc/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/CANfRfr1XZbUvJER_5-LMFd8i1d1RTaFy6JPLhwq9pG9uLE_ZVg%40mail.gmail.c

Re: Forked repositories in GitHub

['Gavin Mogan' via Jenkins Developers]

This is a one time operation for all past repos? What happens to all the
new ones? Is the script pushing a new repo now (I forgot)?

Totally on board with fixing all the old repos, not being able to search
them kinds sucks.

On Tue, Aug 16, 2022 at 4:05 PM Mark Waite 
wrote:

> +1 from me
>
> On Tue, Aug 16, 2022, 2:32 PM Tim Jacomb  wrote:
>
>> GitHub support have offered to make the jenkinsci organisation the root
>> of all of the fork networks
>>
>> See
>>
>> https://github.com/jenkins-infra/helpdesk/issues/2272#issuecomment-1216867119
>>
>>
>> Any objections or +1s?
>>
>> Thanks
>> Tim
>>
>> On Wed, 4 Aug 2021 at 16:52, Tim Jacomb  wrote:
>>
>>> I replied with Daniel's support ticket number (569994)
>>>
>>> and got this back:
>>>
>>> Hi Tim,
>>>
>>> Thanks for your patience here. I checked internally once more and found
>>> that we can, in fact, do this for you. We've gone ahead and detached the
>>> repository into its own fork network.
>>>
>>> Feel free to reach out if you have any additional questions about this!
>>>
>>> On Wed, 28 Jul 2021 at 17:38, Slide  wrote:
>>>
 It would be super ideal to do transferring if we could figure out a
 good process for it, we lose GitHub Issues and some other things when we
 fork as is.

 On Wed, Jul 28, 2021 at 8:33 AM Tim Jacomb 
 wrote:

> Wouldn't creating a repo and pushing the code instead of forking work
> during the hosting process?
>
>
> On Wed, 28 Jul 2021 at 15:02, Jesse Glick 
> wrote:
>
>> On Wed, Jul 28, 2021 at 2:48 AM timja...@gmail.com <
>> timjaco...@gmail.com> wrote:
>>
>>> Seem's like GitHub won't break the fork relationship anymore without
>>> both sides agreeing to it?
>>>
>>
>> This could be a real problem for us. We still have a bunch of repos
>> with misleading fork status, like
>> https://github.com/jenkinsci/plugin-pom rather prominently. There
>> should be some provision by which a “fork” which has way more activity 
>> than
>> the “origin” can unilaterally break the relationship. Of course you can
>> delete and recreate the repo with Git history intact but you will lose 
>> all
>> PR history, which is intolerable.
>>
>> --
>> 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/SkKoCccPrOc/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/CANfRfr1XZbUvJER_5-LMFd8i1d1RTaFy6JPLhwq9pG9uLE_ZVg%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-3Bie4r6MsTyNum4R57DSe3eMO7yNSVt1qbndVZviE%3D57Eug%40mail.gmail.com
> 
> .
>


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

 --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Developers" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVf5HMgWmy%2BrQbnTH1p02Ngo9dXfqtR19SG%3DcxR_NLyWxw%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-3Bid6aSGqdh_JCMjvmANiin4TVbvOnMRLKGbF%2B89uM5iDFg%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 

Re: [Stapler Framework Support for IntelliJ] To be renamed to Jenkins Development Support?

['Gavin Mogan' via Jenkins Developers]

https://www.jenkins.io/project/trademark/

You shouldn't need approval for most cases though looking over the examples
I'm not sure how they could apply for you.

"Idea plugin for Jenkins development" feels like it is along those lines

On Sun., Aug. 14, 2022, 11:18 p.m. 'Denys Digtiar' via Jenkins Developers, <
jenkinsci-dev@googlegroups.com> wrote:

> https://github.com/jenkinsci/idea-stapler-plugin/issues/43
> I kept this issue In Progress for almost a year now 
> It is not hard to do and brings nothing functional to you. It just aligns
> the name more with what this plugin should probably do, i.e. include any
> feature useful for Jenkins or Jenkins plugin development.
> That said, Jenkins is a trademark, so does it mean such rename would need
> a trademark clearance and attribution?
> Any opinions, ideas, suggestions?
>
> --
> 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/8f66b83e-747a-4cfe-8cc2-18116aea8e5bn%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/CAG%3D_Duu8oc98WU_ohY5E%2BEoRrBZDxba7ojChXyuZZLrAHWG%2BdA%40mail.gmail.com.

Re: Storing the results for git cache maintenance tasks

['Gavin Mogan' via Jenkins Developers]

Don't rrds just store a timestamp and an integer?

My vote is keep it consistent with XML. It's not hard in Jenkins to
serialize an object. A standard interface like the jep would eventually
allow plugins to store using different mechanisms like a db

As for limited time and count, it seems like a list would be pretty simple
and serializable unless your talking about many many per second.

Shove onto the end of the list. If it's too long, delete from the start. If
first entry is too old, delete from list.

This is assuming you want to keep structured data. If it's just a long, the
standard logging interfaces sound like a good bet.

On Sat., Aug. 13, 2022, 12:01 a.m. P0512 Hrushikesh, <
hrushikesh20thegr...@gmail.com> wrote:

> Implementation of execution of maintenance task is complete on the Jenkins
> controller. Currently I am working on a way to store the execution data
> into a log file and display it in the UI.
> To do this I'll need a way to write and read from the file in real time to
> show the status of execution.
>
> Data to be stored in log file are -
> 1) Git repo name
> 2) Size of the repo
> 3) Type of maintenance task
> 3) Previous maintenance execution timestamp
> 4) Current Status
> 5) Execution time
>
> We were looking at various options. We came across rrd files (Round robin
> database). I don't think rrd is suitable for current requirements. We can
> however use it for analysis of maintenance tasks over a period of time.
> Is there any plugin in Jenkins which I can refer so that I can write to a
> file and display the results in the maintenance UI as a table?
>
> Hrushikesh Rao
>
>
>
>
> On Friday, August 12, 2022 at 11:28:44 PM UTC+5:30 jgl...@cloudbees.com
> wrote:
>
>> On Thu, Aug 11, 2022 at 11:49 PM Mark Waite  wrote:
>>
>>> effective and reasonable ways to store the most recent results of a task
>>> and present the most recent results of tasks to the administrator
>>>
>>
>> There is no standard technique for this. Branch indexing copies a bunch
>> of code from `Run` and implements its own log storage (no history). Would
>> make sense to define a convenience API for build-like logs, especially as
>> that could be a single place to implement https://jenkins.io/jep/207 and
>> so on.
>>
> --
> 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/d303650d-0724-48df-9813-0bd6ed94383dn%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/CAG%3D_DuuWzy22upT8EJbbd77HbRtKW7GHY%3DN1YxQaWSfbdw48og%40mail.gmail.com.

Re: Prettier for formatting supported languages in Jenkins core

['Gavin Mogan' via Jenkins Developers]

I know i said I had issues with prettier being opinionated, but my
issue wasn't the opinions it had, just that it wasn't very flexible.
My personal projects I usually import one of the opinionated rulesets
to eslint and have it done, but eslint is infinitely configurable,
while my experience, at least when I last used it, prettier was
frustrating to manage. I'm all about tooling being opinionated.

So absolutely not against prettier, just more of a "have you look at
eslint instead? it also has the ability to keep an eye on other things
like using undefined variables"

On Tue, Aug 9, 2022 at 3:31 PM Basil Crow  wrote:
>
> On Tue, Aug 9, 2022 at 2:46 AM 'wfoll...@cloudbees.com' via Jenkins 
> Developers  wrote:
> >
> > I think it's the key point about the complaints again Prettier, it's a very
> > opinionated, meaning that it's not about our subjectivity, but reusing the
> > one from its author. There is no truth about what must be done or not around
> > this kind of style, hence the desire to have this discussion, to find a
> > consensus about the "community subjectivity" instead of relying on someone
> > else['s] opinion.
>
> Please read my previous post about this topic if you have not already. Ceding 
> control of some subjective preferences to an opinionated tool with few (if 
> any) configuration options can be uncomfortable at first, but in my 
> experience the benefits outweigh the disadvantages in the long term. These 
> benefits include never having to deal with a PR that includes a mix of 
> formatting and logic changes (faster code reviews), being able to write code 
> more quickly without having to make formatting decisions, and being able to 
> read code more easily when it is all written in a consistent style.
>
> I have implemented automatic formatting in large organizations many times in 
> my career, and in all cases people complained a little at first but then grew 
> to like it. I myself disliked some of the opinions of the authors of the 
> tools I was putting in place, but putting my own advice into practice I 
> decided to set aside my own opinions for the sake of group cohesion and the 
> benefits described above.
>
> --
> 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/CAFwNDjpz6ieWaXWQx8coavENczXDTDTkr3ei7dq86Q4XdXZrgw%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_DuvtX1pat5VdtsoN7QrLa%2BTfbDr%2B8u0DFxpGwP3%2BCQXHqg%40mail.gmail.com.

Re: How to align a checkbox with an optionalBlock vertically?

['Gavin Mogan' via Jenkins Developers]

You can run with a different version of jenkins `mvn hpi:run
-Djenkins.version=2.332.3`

On Fri., Aug. 12, 2022, 3:48 a.m. Nikhil Bhoski, 
wrote:

> sure Thanks i will try it
>
> On Friday, 12 August 2022 at 15:48:25 UTC+5:30 shih...@gmail.com wrote:
>
>> Can you try packaging it and installing it to a later version of Jenkins
>> server?
>>
>> On Fri, Aug 12, 2022 at 3:26 PM Nikhil Bhoski 
>> wrote:
>>
>>> Yes i am using 2.164.3 it automatically pics that with my hpi:run
>>>
>>> On Friday, 12 August 2022 at 14:48:03 UTC+5:30 shih...@gmail.com wrote:
>>>
 Anything we did to fix the issue from Plugin side was unsuccessful. So
 we kept as it is. However, this issue is fixed in later versions of Jenkins
 (Eg:  2.332.3 ). What is the version are you
 using? Is it an older version?

 On Friday, August 12, 2022 at 12:35:08 PM UTC+5:30 nikhil...@gmail.com
 wrote:

> Any input on this would be appreciated. Is it a Bug in Jenkins Jelly
> format that optional block and simple checkbox are not alined vertically 
> in
> UI
>
> Regards
> Nikhil
>
> On Thursday, 11 August 2022 at 13:01:10 UTC+5:30 Nikhil Bhoski wrote:
>
>> I am stuck with same situation , With optional block if checkboxes
>> are used then on UI both these checkboxes are looking non aligned .
>> any solution on this would be appriciated. @shih let me know how did
>> you handle this.
>>
>> Regards
>> Nikhil
>>
>>
>>
>> On Thursday, 31 January 2019 at 13:06:10 UTC+5:30 shih...@gmail.com
>> wrote:
>>
>>> Hi all,
>>>
>>> I want to align a checkbox with an optionalBlock vertically. How can
>>> I do it? Does jenkins support styles?
>>>
>>> [image: 123.png]
>>>
>>> --
>>> 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/3dfcc9b3-6cbd-4b23-a179-b7d8ba2c6cabn%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/57ea5edd-feb5-4273-a1cf-95b39c0dc8b8n%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/CAG%3D_DutfT2UWNaJ0o%3DPp_J6wNFgovWeBmytFSU%2BuxqZv2-tnnQ%40mail.gmail.com.

Re: unable to perform jenkins release

['Gavin Mogan' via Jenkins Developers]

https://github.com/jenkins-infra/repository-permissions-updater/search?q=aiq

There is no aiq plugin I can see. If this is a new plugin you need to go
through the hosting process. If this is a rename, which I don't recommend,
you need to go update the files in that repository

Also remember everyone here is volunteers so it seems pretty rude to spam
the mailing list asking for an update after only 30 min.


On Thu., Aug. 11, 2022, 2:53 a.m. Nikhil Bhoski, 
wrote:

> Your Error code says your user name and password for Jenkins maven repo is
> invalid. Can you try logging in into the Jenkins maven repo with the same
> user name and password that you may have in your settings.xml . Also as per
> Jenkins doc they suggest you to run preare and perform on one single line
> and not to run as separate commands. Hope this helps
>
> Nikhil
>
> On Thursday, 11 August 2022 at 13:40:40 UTC+5:30 db...@cloudbees.com
> wrote:
>
>>
>>
>> On Thu, Aug 11, 2022 at 9:29 AM 'Mohammad Jameel Uddin' via Jenkins
>> Developers  wrote:
>>
>>> I am unable to perform mvn release:perform, getting error like this
>>>
>>>  Failed to execute goal
>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
>>> on project aiq: Failed to deploy artifacts: Could not transfer artifact
>>> io.jenkins.aiq:1.21 from/to central (
>>> https://repo.jenkins-ci.org/releases): authentication failed for
>>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/aiq/1.21/aiq-1.21.hpi,
>>> status: 401 Unauthorized -> [Help 1]
>>>
>>>
>>>
>>
>> See
>> https://www.jenkins.io/doc/developer/publishing/releasing-manually/#troubleshooting
>>
> --
> 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/682eb200-7c75-459e-a816-3a529d8c7eabn%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/CAG%3D_DusGPfHrRV3XMgpgpO6tB84Twkg1G3YpO9Lx_5zWEnFZrw%40mail.gmail.com.

Re: Prettier for formatting supported languages in Jenkins core

['Gavin Mogan' via Jenkins Developers]

I've always found prettier very opinionated and frustrating to use.

Personally I prefer eslint --fix, which lets you have very fine
control on a lot of things.

But no matter what, I'm 100% in favor of automated tools managing code style.

On Mon, Aug 8, 2022 at 1:15 PM Basil Crow  wrote:
>
> First of all, huge thank you to Tim for working on this effort!
>
> +1 from me. I think a consistent and automatically applied set of
> formatting rules will make it easier to read and edit these files in
> the future.
>
> The most significant objections I have heard so far were that Prettier
> poorly formats "if" statements without braces and that applying any
> kind of formatting change will make security backports more difficult.
> The first of these is being addressed systematically in
> https://github.com/jenkinsci/jenkins/pull/6974 by preformatting the
> codebase to add curly braces everywhere, and I understand that Tim
> plans to address the second objection by backporting the formatting
> change to all active branches. I can also volunteer to help address
> merge conflicts that arise from the integration of this change, if
> that would be helpful.
>
> Two other objections were raised: line length and the removal of
> unnecessary parentheses around arithmetic expressions. These are
> subjective preferences, and one of the reasons to adopt autoformatting
> is to eliminate debate around such subjective preferences in order to
> focus collaboration on content (logic) rather than presentation
> (formatting). In other words, I acknowledge these objections, but in
> my opinion the benefit (being able to effortlessly read and write code
> without worrying about formatting) is worth the cost (giving up
> control over some subjective preferences for the sake of cohesion).
>
> --
> 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/CAFwNDjp-b3bg%2BtNJhJuGFnUBEQCTrEobciJzyjjDoQ_5G5T0%2Bw%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_Dus-9%3Dbt0qF4mV9f_nyJ%3DPSB6LNm0GHPzoctNbne1ibpsg%40mail.gmail.com.

[community.jenkins.io] Indicating breaking changes in plugins with automated releases

['Gavin Mogan' via Jenkins Developers]

I should figure out how to automate this

https://community.jenkins.io/t/indicating-breaking-changes-in-plugins-with-automated-releases/3285

Chris is asking for help with how to indicate a breaking change.
There's probably a bunch of people on dev list who would know more.

-- 
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_DuvxFrZ9DPybWb7_7ntFN07K%2Bp0tppUF9_Zpy_FRP9Wzjg%40mail.gmail.com.

Re: Governance meeting - July 25, 2022

['Gavin Mogan' via Jenkins Developers]

Since there hasn't been any objections? Can the event get updated?
That way I can get it onto my work calendar.

On Mon, Jul 25, 2022 at 1:00 PM Mark Waite  wrote:
>
>
>
> On Monday, July 25, 2022 at 10:43:25 AM UTC-6 Gavin Mogan wrote:
>>
>> *puts on board hat* I'm able to make this weeks meeting.
>>
>> Looking at my new team's schedule. I'd love to see this meeting a week
>> an hour or two earlier, or an hour later. As it stands now the
>> meeting is at 11am and smack in the middle of my morning, which makes
>> it hard to plan around.
>
>
> Ewelina , Basil Crow, Bruno Verachten, Kevin Marten and I all confirmed 
> during the meeting today that we'd be glad to move the meeting one hour 
> earlier.
>
> Oleg Nenashev, would one hour earlier work for you?
>
> Mark Waite
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/1679d84a-e1be-4c78-b568-bdb6f37c04f7n%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/CAG%3D_Duv51%2BvNQYhoPLNfqthY9FXhm-8Cf4sWVVwD%3DWaV9D%3DmqQ%40mail.gmail.com.

Re: Action disappears after restart

['Gavin Mogan' via Jenkins Developers]

What type of action is it?  Something extending a transientaction won't persist.
You shoudn't need to, especially since it'll be done after a build
finishes, but you could call build.save()
How are you confirming the action has disappeared?

On Mon, Jul 25, 2022 at 2:33 PM Nozim Islamov
 wrote:
>
> Hello everyone, hope you guys having a good day, I have a question, I have an 
> action, this action is added during build step, it adds up new action to the 
> build, and after Jenkins restart, all added actions disappear, what could be 
> a solution to keep added actions even after restart?
>
> --
> 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/7226673c-6f0e-4429-a557-ac4789abea8cn%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/CAG%3D_Duvuk3Fev2B8VBfUPk42BQwWrh7Ba502SA623Vgyx8O%2Baw%40mail.gmail.com.

Re: Governance meeting - July 25, 2022

['Gavin Mogan' via Jenkins Developers]

*puts on board hat* I'm able to make this weeks meeting.

Looking at my new team's schedule. I'd love to see this meeting a week
an hour or two earlier, or an hour later.  As it stands now the
meeting is at 11am and smack in the middle of my morning, which makes
it hard to plan around.

Gavin


On Mon, Jul 25, 2022 at 9:32 AM Mark Waite  wrote:
>
> Governance meeting starts in about 90 minutes at 6:00 PM UTC.
>
> Agenda items include:
>
> News
>
> Action items
>
> Blue ocean status statement proposal
>
> Embeddable build status plugin no longer bundles proprietary font
>
> Forums and community topics
>
> --
> 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/ba54329a-89c8-41ac-8255-5443944f729cn%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/CAG%3D_Dusm9hQeWMXV%3DXebMLhoSb9yHJb%2Bimz%2BPuP5%3Dwx6P4fO6A%40mail.gmail.com.

Re: Frontend unit tests in core

['Gavin Mogan' via Jenkins Developers]

For lazy(mobile) people like me

https://issues.jenkins.io/browse/JENKINS-68975
https://issues.jenkins.io/browse/JENKINS-69070

The first feels like the jquery package just doesn't export a cjs file. So
possibly just needs updating. I probably could rewrite it to use modern js
and no jquery.

I'm totally 100% in favor of removing all the @jenkins-cd modules that were
created for blueocean. They are a frustrating mess.

Also on a side note, does the project have access to that scope? I'm going
to be making a helpdesk ticket soon to see if I can get access to one of
the Jenkins npm accounts/orgs



On Fri., Jul. 22, 2022, 9:39 a.m. Basil Crow,  wrote:

> The frontend in core has exactly two (2) unit tests:
>
> war/src/test/js/pluginSetupWizard.spec.js
> war/src/test/js/widgets/config/tabbar.spec.js
>
> Both of these date from 2016. They use an old version of Jest from
> https://jestjs.io and @jenkins-cd/js-test from
> https://github.com/jenkinsci/js-test which has not been updated since
> 2016. Newer versions of Jest require significant changes in consumers
> as described in JENKINS-68975. @jenkins-cd/js-test has many
> problematic transitive dependencies as described in JENKINS-69070.
>
> I could not find any usages of the @jenkins-cd/js-test framework in
> plugins beside Blue Ocean, which is not being actively developed and
> dates back to the same time period.
>
> The status quo does not seem sustainable to me. While resolving
> JENKINS-68975 and JENKINS-69070 are not out of the question, I wonder
> whether we feel that the expected value to be gained is worth the
> trouble. Recall that there are only two such tests in core, so I feel
> the value being provided by them is minimal.
>
> Perhaps it is time to declare the end of this particular journey and
> delete these two tests, the use of Jest in core, and the use of
> @jenkins-cd/js-test in core. If such a framework is desired, it might
> be easier to start over rather than to modernize the existing
> framework. The advantage would be a much simpler dependency tree and
> easier maintenance. The disadvantage would be losing these two tests,
> one for the setup wizard and one for some sort of tab bar.
>
> I am inclined to vote in favor of ripping this out, unless someone
> wants to take on JENKINS-68975 and JENKINS-69070. Does anyone have any
> thoughts about this?
>
> --
> 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/CAFwNDjpsBCRAptHcou6nreTUU4UTy%2BwifV2pc9U-YXnhNdNZUA%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_Duseg%3DEMeEFXPPEkxfnZX1TXjFjO0Q6Tf%2BbAeqsfmMCFYQ%40mail.gmail.com.

Re: Grant timja immediate permissions to commons-lang3-api plugin

['Gavin Mogan' via Jenkins Developers]

your first link doesn't actually goto
https://issues.jenkins.io/browse/JENKINS-69034

I'm very much +1 with the mess of that sshd plugin has caused all day.
I've been redirecting threads and issues and stuff.

Gavin

On Mon, Jul 18, 2022 at 8:31 PM Mark Waite  wrote:
>
> A release of the Apache mina API plugins (core and common) have exposed a 
> cyclic dependency between the mina plugins, configuration as code, and other 
> plugins.  Details are into from 
> https://issues.jenkins.io/browse/JENKINS-69034 .  A workaround is available, 
> but a fix would be much better for users than the workaround.
>
> The preferred fix needs a new release of the commons-lang3-api plugin.  The 
> current maintainer has not responded to previous requests nor to the current 
> request that asks to grant Tim Jacomb permission to maintain the plugin.
>
> The usual process would require a 2 week wait for the adoption request to 
> "time out".  I propose an exception in this case based on the need to deliver 
> a new release of the commons-lang3-api-plugin.  Tim is the Jenkins release 
> officer, a long-standing contributor to the Jenkins project, and a strong 
> contributor.
>
> I propose that Tim be granted permission immediately to maintain the  
> commons-lang3-api plugin as requested in the RPU pull request.
>
> Mark Waite
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/d7ca0365-4600-4097-8dd4-d3c9f93e5327n%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/CAG%3D_Dusji%2B10cuJwT6E78tOSS4bjTg9hQg1F8werY6e3599AVw%40mail.gmail.com.

Re: Let renovate handle dependency updates in jenkinsci/jenkins

['Gavin Mogan' via Jenkins Developers]

I'm a big fan of renovate, so I think its a good idea, but I also
don't touch core, so have no idea what the impact would be.

On Mon, Jul 18, 2022 at 1:19 PM Alexander Brandes  wrote:
>
> Small ammandment: The semantic commit messages on the PoC can be turned off, 
> but are picked up, because recent (my) commits use them.
>
> On Monday, 18 July 2022 at 22:15:32 UTC+2 Alexander Brandes wrote:
>>
>> Hey everyone,
>>
>> dependabot does a good job at handling single artifacts, but it does a bad 
>> to no job handling modules of monorepos, see babel -cli, -core, -env, etc. 
>> for example.
>>
>> This typically leads me to moving several submodule dependency update PRs 
>> into a single PR, before reviewing, considering updating one part of a 
>> dependency without the other often doesn't work out well.
>> See #6878 and #6879 landing in #6877 for such a case.
>> This is just one example, there are more dependencies that fall into this 
>> category.
>>
>> I create a PoC of using renovate over dependabot on core available on 
>> https://github.com/NotMyFault/jenkins-renovate-poc
>> renovate is very well able to create these kinds of "merged" PRs for 
>> submodules of a dependency, see #4 for example.
>>
>> For the reasons outlined above, I'd like to see renovate to handle 
>> dependency updates in core in the future.
>>
>> Kind regards
>> Alex
>
> --
> 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/456baae8-e49f-4d87-8d3e-0038257ea5d4n%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/CAG%3D_DuusFce4CdvXeoxb6Hck_t2kiOs77%3DoE5Hz8J6H%2BM0ZxsA%40mail.gmail.com.

Re: Releasing a new plugin fails due to 'Check interesting categories' failure

['Gavin Mogan' via Jenkins Developers]

gh api /repos/jenkinsci/bmc-change-manager-imstm-plugin/releases
10++ jq -e -r '.[] | select(.draft == true and .name == "next") | .body'
11++ egrep '[⚠]|:(boom|tada|construction_worker):'

Seems like it gets "releases" for the plugin, looks for a draft named
"next" and then checks for any of those emojis/phrases

I'm also not seeing a failure, just that it says there's no
interesting items in the release notes.


On Mon, Jul 18, 2022 at 12:22 PM Marit M  wrote:
>
> https://github.com/jenkinsci/bmc-change-manager-imstm-plugin/runs/7396269153?check_suite_focus=true
>
> Though I added an appropriate category label ( enhancement) to the PR before 
> merging.https://github.com/jenkinsci/bmc-change-manager-imstm-plugin/pull/2
>
> Please advise how to proceed.
> Thanks,
> Marit.
>
> --
> 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/2a4e7dc6-e7ce-4890-ab7a-ac5289babc2an%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/CAG%3D_DuvBqU%3D%3DRw00fEGoXiO2LnNN0zK6b5_nF5LXADYxx8pHUQ%40mail.gmail.com.

Re: New member of jenkins.io triage team

['Gavin Mogan' via Jenkins Developers]

No objections by me.

On Tue, Jul 5, 2022 at 2:01 PM Mark Waite  wrote:
>
> Kevin Martens has been running Jenkins Docs office hours (Europe) and 
> contributing to Jenkins documentation.  I'd like to add him to the jenkins.io 
> triage team in preparation for him eventually becoming a copy editor.
>
> The process that has been outlined previously is that we first assign people 
> to the triage team, then mentor them for a time.  Once there is a pattern of 
> contributed reviews, then the docs officer or the contributor proposes that 
> they be added to the copy editors team.
>
> I propose that the following regular attendees at Docs office hours be added 
> to the jenkins.io triage team:
>
> Kevin Martens  - Changelog and upgrade guide for 2.346.1, Docs office hours 
> (Europe) leader, screenshot update pull requests, helped with docs projects 
> in She Code Africa Contributnon
>
> During the mentoring period, he will need to submit an individual contributor 
> license agreement and become a member of the jenkins-infra organization.  
> Once the mentoring period is complete and the ICLA's have been submitted, 
> we'll propose that he be made a copy editor.
>
> Mark Waite
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/d4a01ebe-d437-4ef1-bb29-33170f249674n%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/CAG%3D_Dus_Gg%2BTykcPYDk8bHhhdfryg0-sv0pHvD2%3DqEspBUZQ9w%40mail.gmail.com.

Re: New plugin for showing dynamic header across Jenkins

['Gavin Mogan' via Jenkins Developers]

   - Header content will be dynamic and easy to update for administrators.

Easier than the existing system notice box? What does dynamic mean in this
case
[image: image.png]

   - Header content will have an expiry date and post expiry it would not
   be shown.

I could potentially see that useful

   - Header content will support HTML elements.

I recommend against explicitly supporting HTML, your plugin will get
flagged by security allowing XSS and other exploit types. Recommend you use
the jenkins sanitization system, which supports allowing raw html, but also
(by default) supports safe html only, or markdown (like my above screenshot
says).

I personally don't see me using the plugin as my jenkins install is just
mine, so take my comments as you will

On Thu, Jun 30, 2022 at 10:16 PM Anil Kumar  wrote:

> Attaching the screenshots for better visibility...
>
> On Friday, July 1, 2022 at 10:43:31 AM UTC+5:30 Anil Kumar wrote:
>
>> Hello everyone,
>>
>> We recently updated our Jenkins to display a common header across Jenkins
>> that helps in communicating with the users.
>>
>> It serves in notifying users for a variety of use cases like sharing
>> updates about ongoing system outages or maintenance windows, sharing
>> product updates and announcements, and collecting user feedback as well.
>>
>> We could not find any plugin which does this and would like to create a
>> plugin and open source it.
>>
>> Let us know your thoughts.
>>
>> *Plugin brief*
>>
>>- Include a common header across Jenkins.
>>- Header content will be dynamic and easy to update for
>>administrators.
>>- Header content will have an expiry date and post expiry it would
>>not be shown.
>>- Header content will support HTML elements.
>>
>> *Sample screenshots[image: Screenshot 2022-07-01 at 10.41.47 AM.png]*
>>
>> *[image: Screenshot 2022-07-01 at 10.39.03 AM.png][image: Screenshot
>> 2022-07-01 at 10.40.31 AM.png]*
>>
>> Thanks,
>> Anil Kumar
>>
> --
> 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/1b4a6508-7a51-45df-b9d0-10daf37fc195n%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/CAG%3D_DuvBEkCrsaQbOLRiEnEtR3tvxfwcTboa%3DnTM2QSK4AVtEg%40mail.gmail.com.

Re: 401 unauthorized when attempting plugin release

['Gavin Mogan' via Jenkins Developers]

I see you are enabling cd so I guess this is moot now but did you have the
actual error message including url?

On Wed., Jun. 22, 2022, 7:43 a.m. Philip Madden, 
wrote:

> Plugin: https://github.com/jenkinsci/hashicorp-vault-pipeline-plugin
> Release Tag:
> https://github.com/jenkinsci/hashicorp-vault-pipeline-plugin/tree/hashicorp-vault-pipeline-1.4
> maven version: 3.8.4
>
> After following the instructions here
> ,
> i'm currently receiving a 401 unauthorized error when attempting to run mvn
> release:perform from my new machine.
>
> I can confirm i can log into artifactory (https://repo.jenkins-ci.org) as
> I used this to generate my maven settings file (I have tried both encrypted
> and plain text passwords in my .m2/settings.xml file) but I am unable to
> publish artifacts.
>
> I also have permissions in the "repository-permissions-updater" repo
> 
> .
>
> Can someone please advise?
>
> Regards
>
> Phil M
>
> --
> 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/a95b42a2-3eaa-44f7-927c-d465a1dadef4n%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/CAG%3D_DutJQEGJv-PzDPOSF5ChV%2Bh%3DNfp%2BO9MH7XxTm%2BWRreNWDw%40mail.gmail.com.

Re: Button onclick change value of on Jelly Action

['Gavin Mogan' via Jenkins Developers]

Can't you make the dropdown and button (though switch it to an input
type=button) and wrap them both in a form. Then you don't need to do any
onclick and JavaScript stuff.

Otherwise you want document.queryElement("some selector that targets your
button").addEventListener("click"...)

On Tue., Jun. 21, 2022, 10:44 p.m. Nozim Islamov, <
mukhammadnozim.isla...@gmail.com> wrote:

> Greetings everyone,
> I want to create a button where whenever it clicks it takes the value of
> dropdown that I have and set it as  on the same page, can anyone help
> with this one?
> Action class code:
>
> package io.jenkins.plugins.sample;
>
> import hudson.model.Run;
> import hudson.util.ListBoxModel;
> import jenkins.model.RunAction2;
> import org.kohsuke.stapler.DataBoundConstructor;
> import org.kohsuke.stapler.DataBoundSetter;
>
> public class PipelinePromotionAction implements RunAction2 {
>
> private transient Run r;
> private String status;
>
> @DataBoundConstructor
> public PipelinePromotionAction(String status) {
> this.status = status;
> }
>
> public String getStatus() {
> return status;
> }
>
> @DataBoundSetter
> public void setStatus(String status) {
> this.status = status;
> }
>
> @Override
> public void onAttached(Run r) {
> this.r = r;
> }
>
> @Override
> public void onLoad(Run r) {
> this.r = r;
> }
>
> public Run getR() {
> return r;
> }
>
> @Override
> public String getIconFileName() {
> return "star.png";
> }
>
> @Override
> public String getDisplayName() {
> return "Manual Promotion";
> }
>
> @Override
> public String getUrlName() {
> return "promotion";
> }
> }
>
> And here is the jelly code:
>
> 
>  xmlns:st="jelly:stapler" xmlns:f="/lib/form">
> 
> 
> 
> 
> 
> 
> Status: ${it.status}
> 
> 
> 
> 
> Promoted
> Not promoted
> 
> 
> Click me
> 
> 
> 
> 
>
> --
> 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/ef12d8a7-b242-413f-90b8-6148f150f343n%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/CAG%3D_Duv9adDpg5oxBPxvHQv1EdoSXS0whwtP%3DPfLNX3WhdVgzw%40mail.gmail.com.

Re: Pipeline RunAction2 class integration to side-panel

['Gavin Mogan' via Jenkins Developers]

I believe the hello-world archetype has a pipeline step already
integrated. Does that not cover what you need?

On Tue, Jun 14, 2022 at 2:54 PM Nozim Islamov
 wrote:
>
> Greetings, I'm facing an issue related to pipelines, I have a class that 
> implements RunAction2, I want to run it on pipelines, I integrated checkbox 
> whether to show it or not using JobProperty and on freestyle job it runs 
> perfectly fine with perform method of JobProperty, is there any way to 
> convert it to pipeline? Git: https://github.com/M1ZoN/promoted
>
> Thanks in advance for any help provided.
>
> If possible, can anyone recommend any hello-world-plugin like tutorials, like 
> this one: https://www.jenkins.io/doc/developer/tutorial/prepare/, but for 
> pipelines?
>
> Best regards,
>
> --
> 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/a821acb3-9d3c-4f17-a93f-dde79ce6fdfdn%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/CAG%3D_DutmUNLrrpcDrHwDZWGEORNo%2B-n8RNTWZ4jEVebFpZvbKw%40mail.gmail.com.

Re: Promotional build failing to pick up credentails

['Gavin Mogan' via Jenkins Developers]

Same response. That bug is years old. If you think it's a bug you
should open a issue in the issue tracker for that plugin.

On Tue, Jun 14, 2022 at 4:02 PM Varma Jampana  wrote:
>
> It's similar to what is mentioned here 
> https://issues.jenkins.io/browse/JENKINS-23977,  where we are not able to 
> pass the credentials to the promotion build from the credentials plugin with 
> the error " ERROR: Could not find credentials entry with ID 'blah blah'. This 
> gets passed fine in the regular build job. The issues says it is resolved 
> though. Any help is appreciated.
>
> On Monday, May 30, 2022 at 5:17:53 PM UTC-5 ga...@gavinmogan.com wrote:
>>
>> if you think its a regression, open a new bug
>>
>> On Fri, May 27, 2022 at 1:01 PM Damodara Devops
>>  wrote:
>> >
>> > When we trigger build its successful with the credentials used. When the 
>> > promotional build is triggered with the same credentials its failing.
>> > This is the similar issue we are seeing.
>> > https://issues.jenkins.io/browse/JENKINS-14169
>> >
>> > We checked on our plugin, which is supporting promotional builds.
>> >
>> > We need help how to move forward.
>> >
>> > Thanks,
>> >
>> > --
>> > You received this message because you are subscribed to the Google Groups 
>> > "Jenkins Developers" group.
>> > To unsubscribe from this group and stop receiving emails from it, send an 
>> > email to jenkinsci-de...@googlegroups.com.
>> > To view this discussion on the web visit 
>> > https://groups.google.com/d/msgid/jenkinsci-dev/93d5050c-1c1c-4ba4-a68e-fe432f72b41fn%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/9f9cc478-0b5c-41cd-8386-ae1fdb2aa50bn%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/CAG%3D_Duut%2B%2B3pQQxX7Bbd2%2B1gN49K4t5jg8aMVyhP0qeMCKBuQQ%40mail.gmail.com.

Re: Jenkins 2.346.1 LTS RC testing started

['Gavin Mogan' via Jenkins Developers]

Btw https://www.jenkins.io/events/ says it's going out this week, so
someone who has calendar access should update it to the 22nd

On Thu., Jun. 9, 2022, 11:50 a.m. Alexander Brandes, 
wrote:

> Hey everyone,
>
> as discussed here
> ,
> the RC of the second backporting is now available at
> https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.346.1-rc32359.d78ef251ec52/jenkins-war-2.346.1-rc32359.d78ef251ec52.war
>
> Per request of the security team and with the approval of the release
> officer, the final release date has been delayed by one week and is now
> scheduled for the 2022-06-22.
>
> ~ Alex
>
> On Wednesday, 18 May 2022 at 08:59:20 UTC+2 Alexander Brandes wrote:
>
>> Hello everyone,
>>
>> Latest LTS RC was made public and it is ready to be tested. Final release
>> is scheduled for 2022-06-15.
>>
>> Please, report your findings in this thread.
>>
>> Download the release from:
>> https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.346.1-rc32347.b_d1d3f7d0eff/jenkins-war-2.346.1-rc32347.b_d1d3f7d0eff.war
>>
>> ~ Alex
>>
> --
> 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/b631b417-8aa4-4b5d-b299-006d6195935fn%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/CAG%3D_DusapKuMnWAg37VidDbWqyX0xBw0%2BoD9jHpG%2B2CyXsH%2B-w%40mail.gmail.com.

Re: Governance meeting - June 1, 2022

['Gavin Mogan' via Jenkins Developers]

Oleg says that its going away anyways in a move to using bevy -
https://groups.google.com/g/jenkins-advocacy-and-outreach-sig/c/PGQV0v4_Yrs

On Thu, Jun 2, 2022 at 6:19 AM Jean-Marc Meessen
 wrote:
>
> Having issues to use the Jenkins Zoom account too.
>
> Hope  we get this sorted out soon.
>
> /- Jmm
>
> Le mer. 1 juin 2022 à 22:01, 'Gavin Mogan' via Jenkins Developers 
>  a écrit :
>>
>> So I've lost access to the jenkins zoom account. Hopefully someone
>> else who does have access can start this meeting.
>>
>> On Wed, Jun 1, 2022 at 4:49 AM Mark Waite  wrote:
>> >
>> > I'm unavailable to attend the governance meeting June 1, 2022.
>> >
>> > Basil Crow has assembled a draft agenda for the meeting at 
>> > https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit?usp=sharing
>> >
>> > Thanks,
>> > Mark Waite
>> >
>> > --
>> > You received this message because you are subscribed to the Google Groups 
>> > "Jenkins Developers" group.
>> > To unsubscribe from this group and stop receiving emails from it, send an 
>> > email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> > To view this discussion on the web visit 
>> > https://groups.google.com/d/msgid/jenkinsci-dev/c82b0fb2-5534-4fd8-9657-f8dda14e2b3en%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/CAG%3D_DuuFu6EWq8fDXp7kRmSNiBoF1Z1%3D91aCgF%3DkEqt_LfWdBA%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/CABLvyXwcsadj8u_erWHBq9qBa6SyuDhtXkp%2BpG1RezyfuqSBNw%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_DutfoNZ8soeBqJ0vF_8yj_hUhYcK%3D2_tKQUwx-huortLtQ%40mail.gmail.com.

Re: Trying to use the warnings-ng-plugin-devenv

['Gavin Mogan' via Jenkins Developers]

"docker compose" is v2 which is the version now documented @
https://docs.docker.com/compose/install/
"docker-compose" is v1 and python, and no longer documented, and
probably soon the package managers will update

On Thu, Jun 2, 2022 at 2:10 AM Ullrich Hafner  wrote:
>
> Yes, the script is from the time before the integration of docker-compose 
> into docker.
>
> I tried to replace docker-compose with docker compose in the script but it 
> seems that the implementation is different and does not update the Jenkins 
> version to the latest one so I finally did not change it. If you find a way 
> to make that working without docker-compose please let me know!
>
> Am 02.06.2022 um 01:26 schrieb 'Gavin Mogan' via Jenkins Developers 
> :
>
> Docker compose v2 is a docker plugin instead of a standalone CLI.
>
> I personally recommend upgrading the cli as its way faster but you could 
> probably edit the scripts to the gym he hypenated one
>
>
> On Wed., Jun. 1, 2022, 4:01 p.m. Simon Matthews,  
> wrote:
>>
>> I forked the warnings-ng-plugin-devenv and cloned it locally. Then I ran  
>> ./clone-repos.sh, which completed successfully, however, when I try to run 
>> "jenkins.sh", I get:
>> alpine: Pulling from jenkins/jenkins
>> Digest: 
>> sha256:a7dd40264e04592ba0d759f7d75fb52fdd5f0fcb9ae5939fef7cbf23b4a6a944
>> Status: Image is up to date for jenkins/jenkins:alpine
>> docker.io/jenkins/jenkins:alpine
>> docker: 'compose' is not a docker command.
>> See 'docker --help'
>> Running docker compose with user ID 1010:441
>> docker: 'compose' is not a docker command.
>> See 'docker --help'
>>
>> This is on an unbuntu 22.04 with "docker-compose" installed. I think the 
>> command should be:
>> docker-compose build
>> not docker compose build
>> Simon
>>
>>
>> --
>> 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/6dedab15-7c78-48d6-89c4-6bc97b4b9e26n%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/CAG%3D_DusVHsOSZ1oBiKZaQeB2Mmz8sp7jtu41QTkRc9qm8L_wnQ%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/C353BAFF-38D1-4DCA-A7EF-CB7413E7B108%40gmail.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_DuvyMC0NHKpudJ7dL8srEACuEJ%3D9Sv%2BPdBek8o2gjf3_KA%40mail.gmail.com.

Re: Trying to use the warnings-ng-plugin-devenv

['Gavin Mogan' via Jenkins Developers]

Docker compose v2 is a docker plugin instead of a standalone CLI.

I personally recommend upgrading the cli as its way faster but you could
probably edit the scripts to the gym he hypenated one


On Wed., Jun. 1, 2022, 4:01 p.m. Simon Matthews, 
wrote:

> I forked the warnings-ng-plugin-devenv and cloned it locally. Then I ran
> ./clone-repos.sh, which completed successfully, however, when I try to run
> "jenkins.sh", I get:
> alpine: Pulling from jenkins/jenkins
> Digest:
> sha256:a7dd40264e04592ba0d759f7d75fb52fdd5f0fcb9ae5939fef7cbf23b4a6a944
> Status: Image is up to date for jenkins/jenkins:alpine
> docker.io/jenkins/jenkins:alpine
> docker: 'compose' is not a docker command.
> See 'docker --help'
> Running docker compose with user ID 1010:441
> docker: 'compose' is not a docker command.
> See 'docker --help'
>
> This is on an unbuntu 22.04 with "docker-compose" installed. I think the
> command should be:
> docker-compose build
> not docker compose build
> Simon
>
> --
> 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/6dedab15-7c78-48d6-89c4-6bc97b4b9e26n%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/CAG%3D_DusVHsOSZ1oBiKZaQeB2Mmz8sp7jtu41QTkRc9qm8L_wnQ%40mail.gmail.com.

Re: Governance meeting - June 1, 2022

['Gavin Mogan' via Jenkins Developers]

So I've lost access to the jenkins zoom account. Hopefully someone
else who does have access can start this meeting.

On Wed, Jun 1, 2022 at 4:49 AM Mark Waite  wrote:
>
> I'm unavailable to attend the governance meeting June 1, 2022.
>
> Basil Crow has assembled a draft agenda for the meeting at 
> https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit?usp=sharing
>
> Thanks,
> Mark Waite
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/c82b0fb2-5534-4fd8-9657-f8dda14e2b3en%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/CAG%3D_DuuFu6EWq8fDXp7kRmSNiBoF1Z1%3D91aCgF%3DkEqt_LfWdBA%40mail.gmail.com.

Re: Promotional build failing to pick up credentails

['Gavin Mogan' via Jenkins Developers]

if you think its a regression, open a new bug

On Fri, May 27, 2022 at 1:01 PM Damodara Devops
 wrote:
>
> When we trigger build its successful with the credentials used. When the 
> promotional build is triggered with the same credentials its failing.
> This is the similar issue we are seeing.
> https://issues.jenkins.io/browse/JENKINS-14169
>
> We checked on our plugin, which is supporting promotional builds.
>
> We need help how to move forward.
>
> Thanks,
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/93d5050c-1c1c-4ba4-a68e-fe432f72b41fn%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/CAG%3D_DuuVAYeqHUpFuRkaZes%3Deera-FYBmGrp1w4YX50u3rXb_A%40mail.gmail.com.

Re: Request team membership for the following groups

['Gavin Mogan' via Jenkins Developers]

> Please add me to the Github reviewers list, so I can learn and contribute to 
> the Cloud-bees community :)

So I'm not a member of these teams, so I can't say what the exact
requirements are, but by being added you essentially can commit code
(submit PR with secondary account, then approve and merge with your
main one). So my recommendation is to start doing reviews without
being a member of the team so you have some .. for lack of a better
word rep.
If you've already done that, then listing some of your reviewed PRs
would be a good addition to this email.

Also, as a member of the board and non cloudbees employee, I would
like to point out that cloudbees is a part of jenkins community,
jenkins isn't part of cloudbees community.

Gavin

On Sun, May 29, 2022 at 12:08 PM Hamsalekha venkatesh
 wrote:
>
> Hi All,
>
> I am reaching out to this amazing Jenkins Community asking if I can also part 
> of the peer reviewers group for reviewing documentation, Jenkins libraries 
> and modules.
>
> I am an active user of Jenkins CI at work and I have about 7 years of 
> industrial experience and I have used Jenkins for more than 2 years now,. 
> Please add me to the Github reviewers list, so I can learn and contribute to 
> the Cloud-bees community :)
>
> Requesting permission to the following groups:
> 1. Editors Team
> 2. Core reviewers Team
> 3. Code reviewers.
>
> My personal GH handle: Hamsalekha-Venkatesh
>
>
>
> --
> 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/3326d425-0f7e-4f2a-b383-43f1ee12a188n%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/CAG%3D_DuutdsZGVB0_0DdN9S55XKU%3DRCJ_jnf86ejkep8uVxVH%3Dg%40mail.gmail.com.

Re: Issue with BluePageDecorator extension

['Gavin Mogan' via Jenkins Developers]

Blueocean as been pretty abandoned so the amount of people who know
how to work with it is pretty low. Also if I remember correctly the
extension system was never really setup so lots of stuff is hard
coded, not sure its extendable.

That being said, looking at your first screenshot, I think blueocean
is a react app that binds itself to #root, with absolute positioning.
You might be able to get it on top with z-index and absolute
positioning.

Gavin

On Wed, May 25, 2022 at 8:37 PM Anil Kumar  wrote:
>
> Hey everyone,
>
> I am using the BluePageDecorator extension point to add a custom header to 
> all the blue ocean pages in my Jenkins instance. I have included my custom 
> content in the header.jelly file as per the documentation.
>
> But the content is not being displayed or hidden on the build details page. I 
> can see the div appended to html but for some reason, it is not displayed. It 
> is being rendered correctly on the home page and job list page.
>
> I am attaching the screenshots and code snippets below.
>
> Can someone guide and suggest to me if I am doing anything incorrectly?
>
> Thanks in advance,
> Anil Kumar
>
> --
> 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/e187d832-9acb-4dda-b308-65daa37a6910n%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/CAG%3D_Dut%2BEjCjcuRi-vLpuuhUz%2BdAk1_rG_W5rXK%2BZ4pvDV0WHQ%40mail.gmail.com.

Re: Building an hpi file?

['Gavin Mogan' via Jenkins Developers]

>From the last time I looked into this, the recommendation is to use
https://github.com/uhafner/warnings-ng-plugin-devenv (which is linked
from one or more of the readmes)

On Wed, May 25, 2022 at 1:17 PM Simon Matthews
 wrote:
>
> I am trying to add another parser. The intent is that the warnings-ng plugin 
> will show (and use) my new additional parser and I believe that they way to 
> achieve that is through adding the parser to analysis-model.
>
> Simon
>
> On Wednesday, May 25, 2022 at 12:33:46 PM UTC-7 bma...@gmail.com wrote:
>>
>> analysis-model is a jar, not a plugin. So it will create a jar as expected.
>> It is used by other plugins I think (cannot check just now).
>>
>> What are you trying to achieve?
>>
>> Le mer. 25 mai 2022 à 21:18, Simon Matthews  a écrit :
>>>
>>> I am attempting to build a modified version of the analysis-model plugin.I 
>>> think that I need to create an hpi file which I can then install in my 
>>> jenkins installation, but if this is not correct, please tell me.
>>>
>>> It's not clear to me how to do this from the command line: I think it has 
>>> changed over time, so there are plenty of old pages that are now incorrect.
>>>
>>> I think that I need to use maven to build the "hpi:hpi" target, but this 
>>> may be wrong. In any case, attempts to do this result in an error: I have 
>>> tried other targets, such as "package" and "install". They appear to 
>>> complete the build successfully, but don't create an hpi file.
>>>
>>> Running:
>>> ~/bin/apache-maven-3.8.5/bin/mvn hpi:hpi
>>> results in:
>>> [ERROR] Failed to execute goal 
>>> org.jenkins-ci.tools:maven-hpi-plugin:3.29-rc1263.227a_29289ce3:hpi 
>>> (default-cli) on project analysis-model: Failed to determine Jenkins 
>>> version this plugin depends on. -> [Help 1]
>>> I have tried adding the following to my pom.xml file:
>>> 2.332.3
>>> but it doesn't help.
>>>
>>> What am I doing wrong?
>>>
>>> Simon
>>>
>>> --
>>> 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/549954d3-3d28-46dd-a3b8-2d450474c87an%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/1a70187a-1ead-4607-bce9-acdcf2348819n%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/CAG%3D_DutiQnW8_X1w1F0qTR7VtWM%2BohjqU%2B_YCtp8tT7j06jXwQ%40mail.gmail.com.

Re: 409 errr on plugin release

['Gavin Mogan' via Jenkins Developers]

Be patient man. Not only do things take time to run but people have other
responsibilities than just Jenkins. Within 3 hours of a release things
should be fully updated.

As for releasing, I don't think you can have ci releasing and manual
version numbers. Its one or the other


On Wed., May 25, 2022, 11:12 a.m. priya jagyasi, 
wrote:

> I see that Github action released 1.038 version of plugin ~40 minutes ago
> here
> https://github.com/jenkinsci/lightstep-incident-response-plugin/releases/tag/1.038.va_c2181133b_79
> .
> However, on the plugins site, I still see 1.036 version
> https://plugins.jenkins.io/lightstep-incident-response/#documentation. Am
> I missing something? I believe if it is released from Github action, the
> plugin should have an updated version?
>
> On Wednesday, May 25, 2022 at 11:17:00 PM UTC+5:30 priya jagyasi wrote:
>
>> This
>> https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/6 is
>> for fully automated versioning. In our plugin, we do not want fully
>> automated versioning. Would the pom file still need any correction to make
>> plugin CD enabled?
>>
>> On Wednesday, May 25, 2022 at 1:22:35 AM UTC+5:30 Jesse Glick wrote:
>>
>>> https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/6
>>>
>> --
> 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/4fa7eeff-1610-44cb-b98d-27b14d533345n%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/CAG%3D_Duvi-HBLR_UZjy44ehor3NN2igbRgGaZpJAzMEku4nkCRQ%40mail.gmail.com.

Re: Hosting

['Gavin Mogan' via Jenkins Developers]

So last ticket is now closed.

On Sun, Apr 10, 2022 at 1:16 PM Gavin Mogan  wrote:
>
> Looks like its mostly waiting for security
> https://issues.jenkins.io/browse/HOSTING-1160
>
> On Sun, Apr 10, 2022 at 12:40 PM Alex Earl  wrote:
> >
> > Anything I can do to help get that one over the finish line?
> >
> > On Fri, Apr 8, 2022 at 9:10 AM 'Gavin Mogan' via Jenkins Developers 
> >  wrote:
> >>
> >> We have one left mostly waiting on security
> >>
> >> On Fri., Apr. 8, 2022, 9:08 a.m. Tim Jacomb,  wrote:
> >>>
> >>> It was kept while we processed the remaining stragglers in Jira, I think 
> >>> those have finished now so we can remove the code.
> >>>
> >>> The checker and hosted was copied into the RPU repo
> >>>
> >>> On Fri, 8 Apr 2022 at 15:30, slide  wrote:
> >>>>
> >>>> Since I have been out of the loop for a while, I was reviewing the 
> >>>> new(ish) hosting requirements documentation here: 
> >>>> https://www.jenkins.io/doc/developer/publishing/requesting-hosting/#open-hosting-request.
> >>>>
> >>>> Does this mean we can remove the hosting checker and such from the 
> >>>> ircbot, or has it been updated for the new flow to check the PRs?
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Alex
> >>>>
> >>>> --
> >>>> 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/3bf1914e-98ef-4132-8b27-afc3b3ac5f4en%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-3BifBUNEsO44SHA88h3WQ1OeptC074n9TPBhH4OyRZyCYsA%40mail.gmail.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/O8ZKRm6x6Fc/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/CAG%3D_DuscTzOfvrkD9LX86mKA21WEZqyGCJPOegGwKxvRE6DsBg%40mail.gmail.com.
> >
> >
> >
> > --
> > Website: http://earl-of-code.com
> >
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to jenkinsci-dev+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdLb%2BU_9y_Kyp%2BH6XdTT4ea4CiL1X8AwuVuHiNp-9o4LA%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_DusgusdKj1V63OF2MGJqvcMaL9Mg6rjRB4S9q3JfH4VcOA%40mail.gmail.com.