Re: [Question]: Where can I find guidelines for contributing on JUnit Plugin?

[Sanjeet Malhotra]

Thanks a lot for guiding. I will surely discuss my ideas after looking at 
the resources you mentioned.

On Tuesday, June 2, 2020 at 1:49:04 AM UTC+5:30, Mark Waite wrote:
>
> Great to have you interested in helping!
>
> https://plugins.jenkins.io/junit/ shows that the plugin is at 
> https://github.com/jenkinsci/junit-plugin .
>
> I didn't see any specific contributing guidelines in the plugin.  I assume 
> it is similar to most plugins.  Discuss your idea here, refine it, provide 
> an implementation as a pull request, discuss the implementation in the pull 
> request.
>
> Javadoc for the plugin is located at 
> https://javadoc.jenkins-ci.org/plugin/junit/ .  You may want to consider 
> creating the added functionality as a separate plugin so that users can 
> choose to install the new capabilities with an independent plugin, rather 
> than upgrading the junit plugin.
>
> Mark Waite
>
> On Monday, June 1, 2020 at 1:06:54 PM UTC-6, Sanjeet Malhotra wrote:
>>
>> Hi, 
>> I wanted to contribute to JUnit Plugin by making more trends in addition 
>> to one being currently displayed right now. I was planning to make trends 
>> like one for test flappers, number of tests taking longer time based on 
>> various metrics, etc. I just wanted to know where I can find guidelines for 
>> contributing to JUnit Plugin and any advice is most welcomed. TIA.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/cc7824ba-5700-4f17-81dd-2b38b4e878bd%40googlegroups.com.

Re: GitHub App installations on jenkinsci

[Oleg Nenashev]

No specific reason except everyone being busy with other stuff.
Since nobody voted against, I enabled it in the jenkinsci GitHub
organization and added Custom Jenkins Distribution build service to the
repo.
Also invited Ulli to the jenkinsci org on Codacy so that I could share
permissions there.

Best regards,
Oleg




On Mon, Jun 1, 2020 at 9:04 PM Sladyn Nunes  wrote:

> I wanted to explore using Codacy in my project as well, it really helps
> with analysis. Any specific reason why is this stalled ?
>
> --
> 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/HM6s8KwNTlw/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/e1842d07-fec4-4c43-9203-ddf7b36c67c8%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/CAPfivLD0rSaEcmKLH%3D1F2uKfGSQOeJw9q48g953kBcXWw6fjng%40mail.gmail.com.

Re: [Question]: Where can I find guidelines for contributing on JUnit Plugin?

[Mark Waite]

Great to have you interested in helping!

https://plugins.jenkins.io/junit/ shows that the plugin is at 
https://github.com/jenkinsci/junit-plugin .

I didn't see any specific contributing guidelines in the plugin.  I assume 
it is similar to most plugins.  Discuss your idea here, refine it, provide 
an implementation as a pull request, discuss the implementation in the pull 
request.

Javadoc for the plugin is located at 
https://javadoc.jenkins-ci.org/plugin/junit/ .  You may want to consider 
creating the added functionality as a separate plugin so that users can 
choose to install the new capabilities with an independent plugin, rather 
than upgrading the junit plugin.

Mark Waite

On Monday, June 1, 2020 at 1:06:54 PM UTC-6, Sanjeet Malhotra wrote:
>
> Hi, 
> I wanted to contribute to JUnit Plugin by making more trends in addition 
> to one being currently displayed right now. I was planning to make trends 
> like one for test flappers, number of tests taking longer time based on 
> various metrics, etc. I just wanted to know where I can find guidelines for 
> contributing to JUnit Plugin and any advice is most welcomed. TIA.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f1e4ebd7-f9ed-4d06-81e2-c29c7dea6487%40googlegroups.com.

[Question]: Where can I find guidelines for contributing on JUnit Plugin?

[Sanjeet Malhotra]

Hi, 
I wanted to contribute to JUnit Plugin by making more trends in addition to 
one being currently displayed right now. I was planning to make trends like 
one for test flappers, number of tests taking longer time based on various 
metrics, etc. I just wanted to know where I can find guidelines for 
contributing to JUnit Plugin and any advice is most welcomed. TIA.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1b28519d-82af-49a8-a60d-d63e5385b4ef%40googlegroups.com.

Re: GitHub App installations on jenkinsci

[Sladyn Nunes]

I wanted to explore using Codacy in my project as well, it really helps 
with analysis. Any specific reason why is this stalled ? 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e1842d07-fec4-4c43-9203-ddf7b36c67c8%40googlegroups.com.

Re: GitHub App installations on jenkinsci

[Sladyn Nunes]

I wanted to explore using Codacy in my project as well, it really helps 
with analysis. Any specific reason why is this stalled ? 

On Sunday, March 22, 2020 at 8:31:09 PM UTC+5:30, Ullrich Hafner wrote:
>
> I'm currently using Codacy (https://www.codacy.com/) to validate PRs on 
> my Jenkins repositories to check for CheckStyle and PMD warnings. Up to now 
> I can activate this app on a per repository basis. 
>
> But they now switch the integration and are now available as a GitHub App. 
> So when I want to enable the App for my repository I get the following 
> dialog:
>
>
>
> In this dialog I cannot enable the access for an individual repository, I 
> just can create a `request`. Is someone of our GitHub admins receiving such 
> requests? Or where are these requests routed to?
>
> I also wanted to enable the Settings App (
> https://probot.github.io/apps/settings/) to set the labels of all of my 
> repositories to the same set of labels. Here I have the same problem: I can 
> activate them for my repositories in my account (i.e. uhafner/*) but not 
> for a repository in jenkinsci. 
>
> Is it possible to grant individual users a permission to enable apps in 
> their repositories? Or is this something that needs to be done for the 
> whole org?
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e62f72c3-72ab-4c31-bf80-3e8a62503cdf%40googlegroups.com.

Re: I see that there is a new version of blue ocean plugin. How do I upgrade?

[Marlene Cote]

So sorry for messing up and asking here.  thank you for responding and 
directing me to the right place.

On Monday, June 1, 2020 at 1:18:10 PM UTC-4, Marlene Cote wrote:
>
> I don't see it in my available updates list.  I tried to download and 
> upload the hpi and now I have a mess of dependencies that won't load or 
> upgrade.
> Help!!!
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/cd8efe19-e81b-4063-81f9-6af90a16d265%40googlegroups.com.

Re: BlueOcean Plugin Re: I see that there is a new version of blue ocean plugin. How do I upgrade?

['Gavin Mogan' via Jenkins Developers]

As mark said, you need to be using the jenkinsci-users mailing list.

But also using the cloudbees version you should be talking to cloudbees not
open source volunteers.

On Mon., Jun. 1, 2020, 10:33 a.m. Marlene Cote, 
wrote:

> I am running the latest cloudbees jenkins distribution.
>
> On Monday, June 1, 2020 at 1:18:10 PM UTC-4, Marlene Cote wrote:
>>
>> I don't see it in my available updates list.  I tried to download and
>> upload the hpi and now I have a mess of dependencies that won't load or
>> upgrade.
>> Help!!!
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/e1777e79-ad11-4f71-9935-816e5259c617%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_DusGteU6WQKHtCejuwNGzUgw5NGQw79uPFj-pDJ8xUvvfA%40mail.gmail.com.

BlueOcean Plugin Re: I see that there is a new version of blue ocean plugin. How do I upgrade?

[Marlene Cote]

I am running the latest cloudbees jenkins distribution.

On Monday, June 1, 2020 at 1:18:10 PM UTC-4, Marlene Cote wrote:
>
> I don't see it in my available updates list.  I tried to download and 
> upload the hpi and now I have a mess of dependencies that won't load or 
> upgrade.
> Help!!!
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e1777e79-ad11-4f71-9935-816e5259c617%40googlegroups.com.

Re: I see that there is a new version of blue ocean plugin. How do I upgrade?

[Mark Waite]

This is a topic for the Jenkins users list, not the Jenkins developers
list.  The Jenkins developers list is for the development of Jenkins.
Questions related to plugin upgrades and Jenkins administration are better
handled on the Jenkins users list.

If you know which plugin hpi files you uploaded and have the earlier
copies, you should be able to replace that plugin with the earlier version
and restart your Jenkins server.  Then you can use the Jenkins Plugin
Manager to perform the upgrade.

On Mon, Jun 1, 2020 at 11:18 AM Marlene Cote  wrote:

> I don't see it in my available updates list.  I tried to download and
> upload the hpi and now I have a mess of dependencies that won't load or
> upgrade.
> Help!!!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/6c91bdb0-c12b-44d5-937d-ab5e2ebe1171%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/CAO49JtHzKv0%3DoFZG3_tTd06LpsjXXgCrTGV%3DAbxOiL%3D5umxh_Q%40mail.gmail.com.

I see that there is a new version of blue ocean plugin. How do I upgrade?

[Marlene Cote]

I don't see it in my available updates list.  I tried to download and 
upload the hpi and now I have a mess of dependencies that won't load or 
upgrade.
Help!!!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6c91bdb0-c12b-44d5-937d-ab5e2ebe1171%40googlegroups.com.

Re: Adding Downloadables to Jenkins

[Tim Van Holder]

Ah, so it's just a matter of filing a PR there? Cool.

Thanks. Now to teach myself enough Groovy for my purposes :)

On Mon, 1 Jun 2020 at 18:16, Daniel Beck  wrote:

>
>
> > On 1. Jun 2020, at 14:56, Tim Van Holder 
> wrote:
> >
> > The second is still a question mark. I found one page somewhere about
> needing to write a scraper to generate the file, but that did not go into
> details on what that would look like, or how to get an update center to use
> it.
> >
>
> https://github.com/jenkins-infra/crawler/ is periodically executed in
> Jenkins project infrastructure.
>
> Results are placed in https://updates.jenkins.io/updates/
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/D374727B-862F-45CB-A373-65F144A4A290%40beckweb.net
> .
>

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

Re: Adding Downloadables to Jenkins

[Daniel Beck]

> On 1. Jun 2020, at 14:56, Tim Van Holder  wrote:
> 
> The second is still a question mark. I found one page somewhere about needing 
> to write a scraper to generate the file, but that did not go into details on 
> what that would look like, or how to get an update center to use it.
> 

https://github.com/jenkins-infra/crawler/ is periodically executed in Jenkins 
project infrastructure.

Results are placed in https://updates.jenkins.io/updates/

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/D374727B-862F-45CB-A373-65F144A4A290%40beckweb.net.

Re: Proposal: Windows support policy for Jenkins

[Oleg Nenashev]

Hi Tim,

Thanks for your feedback! One thing to mention is that we are not dropping
support for x86, at least for the time being. Latest edition of the policy
in https://github.com/jenkins-infra/jenkins.io/pull/3295 says that it is
"Level 3 - Patches considered". *Support may have limitations and extra
requirements. We do not test compatibility, and we may drop support if
there is a need. We will consider patches if they do not put Level 1/2
support at risk and if they do not create maintenance overhead*. So we will
be still supporting x86, to some extent.

Splitting the policy to masters and agents would make sense, but
unfortunately all key features have to run on both of them. I was unable to
identify any use-case where "supporting only on an agent" would make
difference w.r.t the maintenance overhead.

Best regards,
Oleg


On Mon, Jun 1, 2020 at 5:17 PM Tim Van Holder 
wrote:

> On Friday, 10 April 2020 14:26:51 UTC+2, Oleg Nenashev wrote:
>>
>> Dear all,
>>
>> As you probably know, Jenkins core and some plugins contain native code,
>> and hence they rely on operating systems and platforms. In principle
>> Jenkins can run everywhere where you can run Java 8 or Java 11, but in
>> practice there are some limitations. Notably we use Java Native Access  and
>> Java Native Runtime libraries which provide wide support for platforms, but
>> there are other components. In the case of Windows platforms we use Windows
>> Service Wrapper (WinSW)  and Windows
>> Process Management Library (WinP) ,
>> which depend on Windows versions and, in the case of windows services, on
>> .NET Framework.
>>
>> In the Jenkins Platform SIG  we have
>> an open topic about Windows support policy in Jenkins. Currently we have no
>> documented support policy for Windows, and it becomes an obstacle for
>> maintainers of Windows-focused components and plugins in the
>> Jenkins project. As a maintainer of WinSW and WinP, I have to be very
>> conservative about Windows support. But it comes at a cost to users, not
>> just maintenance overhead. At the end of the day it also blocks us from
>> adopting new Windows features and making Jenkins more stable/maintenable on
>> modern Windows platforms.
>>
>> I know for sure that there are Jenkins users running on Windows XP, but
>> IMHO it becomes more and more legacy use-case. Last popular industry
>> version had EoL in 2019 (WinXP Exmbedded POSReady
>> ),
>> and IMO it is time to drop WinXP support in new Jenkins releases. Same goes
>> to 32bit systems and non-mainstream architectures like Itanium, we could
>> at least reduce the support level there.
>>
>> I suggest the following policy:
>>
>>- All installers and service wrappers require Windows 7 / Windows
>>Server 2012 or above (and .NET framework 4.0+). They support 64bit
>>platforms only. Support for other platforms are provided via manual
>>jenkins.war deployment
>>- Jenkins master runtime requires Windows 7 / Windows Server 2012 or
>>above. It may work on older versions, but we do not guarantee 
>> compatibility
>>- Jenkins agent runtime requires Windows 7 / Windows Server 2012 or
>>above. It may work on older versions, but we do not guarantee 
>> compatibility
>>- For all Windows service installations .NET Framework 4.0 or above
>>is required. It is a default version in Windows versions specified above
>>- Jenkins master and agent Docker images are not required to provide
>>images for the supported platforms. They can move ahead as maintainers
>>prefer
>>- Plugins can define their own support policy, but they are strongly
>>advised to align their Windows support policy with the Jenkins Core
>>versions.
>>   - We have no way to communicate potential Windows support issues
>>   via update center at the moment, so following the Jenkins core 
>> requirements
>>   is what we can recommend as the best option
>>- Custom Jenkins packaging may have different requirements
>>(Jenkinsfile Runner, WARs built by Custom WAR Packager)
>>
>> Would appreciate feedback from maintainers and Windows users! Any
>> comments and change suggestions are welcome.
>>
>> If other Plaftorm SIG folks agree with me, I would suggest to add this
>> area to the Jenkins Roadmap . I
>> also created a JENKINS-61865
>>  EPIC to track
>> changes there. I will create tasks in the EPIC once there is a consensus in
>> this thread.
>>
>> Best regards,
>> Oleg Nenashev
>> Platform SIG
>>
>>
> I only started working on a sort-of-Windows-oriented plugin
> (dotnet-sdk-plugin), so I did not see this earlier. Going to add my EUR0.02
> anyway.
>
> While dropping support for XP seems perfectly sensible to 

Re: Proposal: Windows support policy for Jenkins

[Tim Van Holder]

On Friday, 10 April 2020 14:26:51 UTC+2, Oleg Nenashev wrote:
>
> Dear all,
>
> As you probably know, Jenkins core and some plugins contain native code, 
> and hence they rely on operating systems and platforms. In principle 
> Jenkins can run everywhere where you can run Java 8 or Java 11, but in 
> practice there are some limitations. Notably we use Java Native Access  and 
> Java Native Runtime libraries which provide wide support for platforms, but 
> there are other components. In the case of Windows platforms we use Windows 
> Service Wrapper (WinSW)  and Windows 
> Process Management Library (WinP) , 
> which depend on Windows versions and, in the case of windows services, on 
> .NET Framework.
>
> In the Jenkins Platform SIG  we have 
> an open topic about Windows support policy in Jenkins. Currently we have no 
> documented support policy for Windows, and it becomes an obstacle for 
> maintainers of Windows-focused components and plugins in the 
> Jenkins project. As a maintainer of WinSW and WinP, I have to be very 
> conservative about Windows support. But it comes at a cost to users, not 
> just maintenance overhead. At the end of the day it also blocks us from 
> adopting new Windows features and making Jenkins more stable/maintenable on 
> modern Windows platforms.
>
> I know for sure that there are Jenkins users running on Windows XP, but 
> IMHO it becomes more and more legacy use-case. Last popular industry 
> version had EoL in 2019 (WinXP Exmbedded POSReady 
> ),
>  
> and IMO it is time to drop WinXP support in new Jenkins releases. Same goes 
> to 32bit systems and non-mainstream architectures like Itanium, we could 
> at least reduce the support level there.
>
> I suggest the following policy:
>
>- All installers and service wrappers require Windows 7 / Windows 
>Server 2012 or above (and .NET framework 4.0+). They support 64bit 
>platforms only. Support for other platforms are provided via manual 
>jenkins.war deployment
>- Jenkins master runtime requires Windows 7 / Windows Server 2012 or 
>above. It may work on older versions, but we do not guarantee compatibility
>- Jenkins agent runtime requires Windows 7 / Windows Server 2012 or 
>above. It may work on older versions, but we do not guarantee compatibility
>- For all Windows service installations .NET Framework 4.0 or above is 
>required. It is a default version in Windows versions specified above
>- Jenkins master and agent Docker images are not required to provide 
>images for the supported platforms. They can move ahead as maintainers 
>prefer
>- Plugins can define their own support policy, but they are strongly 
>advised to align their Windows support policy with the Jenkins Core 
>versions.
>   - We have no way to communicate potential Windows support issues 
>   via update center at the moment, so following the Jenkins core 
> requirements 
>   is what we can recommend as the best option
>- Custom Jenkins packaging may have different requirements 
>(Jenkinsfile Runner, WARs built by Custom WAR Packager)
>
> Would appreciate feedback from maintainers and Windows users! Any comments 
> and change suggestions are welcome.
>
> If other Plaftorm SIG folks agree with me, I would suggest to add this 
> area to the Jenkins Roadmap . I also 
> created a JENKINS-61865 
>  EPIC to track 
> changes there. I will create tasks in the EPIC once there is a consensus in 
> this thread.
>
> Best regards,
> Oleg Nenashev
> Platform SIG
>
>
I only started working on a sort-of-Windows-oriented plugin 
(dotnet-sdk-plugin), so I did not see this earlier. Going to add my EUR0.02 
anyway.

While dropping support for XP seems perfectly sensible to me, I'm not as 
sure about dropping support for x86.
There, I would take guidance from what Microsoft still supports for the 
.NET SDKs (given that those are used for building, they seem a relevant 
data point for a CI server).
Looking at the most bleeding-edge versions, and discounting ARM for now, 
they support only x64 for Linux and macOS, but both x64 and x86 for Windows.
Source: https://dotnet.microsoft.com/download/dotnet/5.0
That would suggest that there is enough of a user/install base to make that 
relevant for them, which in turn seems like it should make it relevant for 
Jenkins.

Note: I would see less of an issue having different support levels for a 
master node and slave nodes; requiring x64 for master may not be 
unreasonable, but almost dropping support for x86 slaves seems eminently 
less so.

Disclaimer: I'm personally running only x64 machines, and I'm not sure the 
company I work for has any x86 slaves 

Adding Downloadables to Jenkins

[Tim Van Holder]

Hi all,

I am working on a plugin (https://github.com/jenkinsci/dotnet-sdk-plugin) 
which includes a tool installer.

Currently, I am using json files as resources as a basis of this installer; 
this is because I ran into two roadblocks:

   - the existing DownloadFromUrlInstaller assumes architecture-independent 
   processing and therefore:
  - does not offer label configuration
  - uses a very simple flat list of install packages (and a simple 'id' 
  value)
 - there are currently over 1000 SDK packages for .NET, so a flat 
 list really is not workable
  - while there is code available in Jenkins core and plugins that uses 
   DownloadFromUrlInstaller or Downloadable, it is rather unclear to me how 
   the downloadable file gets on the update center to begin with (for example, 
   the ANt plugin does not seem to include any code that looks on 
   ant.apache.org for the available downloads)
   

The first issue is easily overcome by writing a custom installer, which I 
have done.

The second is still a question mark. I found one page somewhere about 
needing to write a scraper to generate the file, but that did not go into 
details on what that would look like, or how to get an update center to use 
it.

So, I would appreciate if you could point me to a document describing 
what's involved in getting one or more Downloadables(*), or if no such 
document exists, the steps required.
I would prefer having this in place before my 1.0 release.


(*) is Downloadable intended strictly for ToolInstallers only? I have two 
other JSON files, now as resources, used as source for auto-completion. 
They too would benefit from being kept up to date outside of a plugin 
release cycle.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ca767f7e-d5d8-4c99-973e-976199564e87%40googlegroups.com.

Re: 2.222.x LTS missing backport of JENKINS-61197

[Oliver Gondža]

On 01/06/2020 10.03, Raihaan Shouhell wrote:

Hey all,

I've recently upgraded masters to the 2.222.x line and ran into an issue 
where a build that was using a filesystem root workspace will throw a 
null pointer exception.


Some quick investigation revealed 
https://issues.jenkins-ci.org/browse/JENKINS-61197 which states 
2.222.1-fixed but the bug exists in my instance running 2.222.3,


Inspecting the 2.222.1 tag reveals that the bug still exists and was not 
backported 
https://github.com/jenkinsci/jenkins/blob/d66bd8595e531749e842274a806eabab5cc16a32/core/src/main/java/hudson/model/AbstractBuild.java#L866-L869


Hello, thanks for bringing this up. I probably mislabeled the issue. The 
set of backported patches, changelog and upgrade guidelines seems to be 
in sync - that this is not fixed in 2.222.1.


Fixing the issue labels.
--
oliver

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1fd2038a-7be5-02b7-f8de-e38a0989870a%40gmail.com.

2.222.x LTS missing backport of JENKINS-61197

[Raihaan Shouhell]

Hey all,

I've recently upgraded masters to the 2.222.x line and ran into an issue 
where a build that was using a filesystem root workspace will throw a null 
pointer exception.

Some quick investigation revealed 
https://issues.jenkins-ci.org/browse/JENKINS-61197 which states 
2.222.1-fixed but the bug exists in my instance running 2.222.3,

Inspecting the 2.222.1 tag reveals that the bug still exists and was not 
backported 
https://github.com/jenkinsci/jenkins/blob/d66bd8595e531749e842274a806eabab5cc16a32/core/src/main/java/hudson/model/AbstractBuild.java#L866-L869

Cheers,
Raihaan

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/cf75cc3f-4d91-4822-a61c-f0706e8e85fa%40googlegroups.com.