Re: Filename too long issues in https://ci.jenkins.io/ on Windows workers

[Tim Jacomb]

Apart from the other suggestions shortening the name would help, from the
above example you should be able to remove both Jenkins and plugin

The reg key fix would hopefully solve this though

On Tue, 14 Sep 2021 at 18:34, Slide  wrote:

> Yes, it would need to be added to the images for the infra.
>
> On Tue, Sep 14, 2021 at 10:22 AM 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> Isn't all the advice specific to building locally? The problem was stated
>> on CI.jenkins
>>
>> So I'm guessing an infra ticket/pr to enable the Reg key?and maybe agents
>> should be on the root instead of users Jenkins work?
>>
>> On Tue., Sep. 14, 2021, 9:53 a.m. Slide,  wrote:
>>
>>> You could try this when building the images for Windows:
>>>
>>> reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
>>> /v LongPathsEnabled /t REG_DWORD /d 1
>>>
>>> This should enable long file names in the OS itself
>>>
>>> On Tue, Sep 14, 2021 at 9:09 AM Mark Waite 
>>> wrote:
>>>
 I've not found a technique that resolves the issue for all cases.  Some
 of the techniques we've tried with varying levels of non-success have
 included:

- Shorten the job name and file path as much as possible (C:\J
instead of C:\Users\Jenkins\Work) (helps, but doesn't fix it, could be
applied to ci.jenkins.io configuration and our Windows image
generation )
- Git config system level core.longpaths true (seems to help in
some cases, but doesn't fix it in all cases
) (this change
could be applied in the Windows image generation for ci.jenkins.io,
since we have that in code now
)
- Git config repository level core.longpaths true (helps in cases
where the initial clone and checkout was successful but later operations
failed, can be implemented in the tests of the plugin)

 Some of the references that provide more information about the issue:

- Git for windows open issue -
https://github.com/git-for-windows/git/issues/2576
- Example using repository level config -
https://github.com/jenkinsci/git-client-plugin/pull/595
- Attempt to create that configuration in the git client plugin -
https://github.com/jenkinsci/git-client-plugin/pull/523
- Second attempt to create that configuration in the git client
plugin - https://github.com/jenkinsci/git-client-plugin/pull/537


 On Tue, Sep 14, 2021 at 9:54 AM Victor Martinez <
 victormartinezru...@gmail.com> wrote:

> Hi all,
>
> Is there any specific configuration I could apply permanently to avoid
> the below error that happens in https://ci.jenkins.io/ when running
> the tests on Windows?
>
>  > git.exe init
> C:\Users\jenkins\Work\workspace\gins_opentelemetry-plugin_PR-167\target\tmp\j
> h927479030425102413\workspace\co-3 # timeout=10
> Fetching upstream changes from
> https://github.com/jenkinsci/opentelemetry-plugin
> ...
> [Pipeline] }
> [Pipeline] // stage
> [Pipeline] }
> [Pipeline] // node
> [Pipeline] End of Pipeline
> hudson.plugins.git.GitException: Command "git.exe checkout -f
> a1479a055ebb33d6abf48ce9238fb586edc97203" returned status code 1:
> stdout:
> stderr: error: unable to create file
> src/main/resources/io/jenkins/plugins/opentelemetry/JenkinsOpenTelemetryPluginConfiguration/help-exportOtelConfigurationAsEnvironmentVariables.html:
> Filename too long
>
> I've been shorting the pipeline names for the time being, but I think
> the workaround doesn't work anymore.
>
> Thanks so much.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/e9e92f22-2b38-48fb-86ac-7e216d67db61n%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/CAO49JtF8rg%3D43JRe1NQt%3Dxv8Pyhqe9dVeehUmrWWh_L4vyFfGQ%40mail.gmail.com
 

Re: Is an explicit dependency on jenkins-test-harness now needed?

[Tim Jacomb]

Why do you need to use the embedded version of maven?

I use IntelliJ and have no problem setting it to use my local maven 3.8.x.

On Tue, 14 Sep 2021 at 13:35, Jesse Glick  wrote:

> On Tue, Sep 14, 2021 at 5:55 AM Oleg Nenashev 
> wrote:
>
>> it is time [to] include JCasC test harness […] into Jenkins Test Harness
>>
>
> Not possible. It depends on plugins.
>
>
>> or to Plugin POM
>>
>
> No. If you want to depend on JCasC the `bom` sets up versions for you.
> (For most cases you should not need to explicitly mention JCasC in your
> plugin since you should just be defining settings using simple, plain
> idioms that work automatically in any context—GUI forms, Pipeline, JCasC.
> It is necessary however when you are forced into weird Java structures for
> compatibility reasons.)
>
> The correct solution here is to update the parent POM as Tim says, or use
> an older version of JCasC. If your IDE does not let you run a current
> version of a tool, run it from a shell instead, or use a different IDE to
> run local tests. As a workaround you could specify an explicit
> `jenkins-test-harness.version` in your POM pending a parent update, or even
> try to add an `exclusion` from
> `io.jenkins.configuration-as-code:test-harness` and hope that JCasC was not
> actually relying on recently introduced features.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1D_njA0r2EJi-%3D8E3wCNPGFRZNToBohO2TmsC8nLygUA%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-3BifJF%3DPFb8c4FQxViAfRjA7LFARAcXu297t_1ie1KZtupg%40mail.gmail.com.

Re: Filename too long issues in https://ci.jenkins.io/ on Windows workers

[Slide]

Yes, it would need to be added to the images for the infra.

On Tue, Sep 14, 2021 at 10:22 AM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Isn't all the advice specific to building locally? The problem was stated
> on CI.jenkins
>
> So I'm guessing an infra ticket/pr to enable the Reg key?and maybe agents
> should be on the root instead of users Jenkins work?
>
> On Tue., Sep. 14, 2021, 9:53 a.m. Slide,  wrote:
>
>> You could try this when building the images for Windows:
>>
>> reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
>> /v LongPathsEnabled /t REG_DWORD /d 1
>>
>> This should enable long file names in the OS itself
>>
>> On Tue, Sep 14, 2021 at 9:09 AM Mark Waite 
>> wrote:
>>
>>> I've not found a technique that resolves the issue for all cases.  Some
>>> of the techniques we've tried with varying levels of non-success have
>>> included:
>>>
>>>- Shorten the job name and file path as much as possible (C:\J
>>>instead of C:\Users\Jenkins\Work) (helps, but doesn't fix it, could be
>>>applied to ci.jenkins.io configuration and our Windows image
>>>generation )
>>>- Git config system level core.longpaths true (seems to help in some
>>>cases, but doesn't fix it in all cases
>>>) (this change
>>>could be applied in the Windows image generation for ci.jenkins.io,
>>>since we have that in code now
>>>)
>>>- Git config repository level core.longpaths true (helps in cases
>>>where the initial clone and checkout was successful but later operations
>>>failed, can be implemented in the tests of the plugin)
>>>
>>> Some of the references that provide more information about the issue:
>>>
>>>- Git for windows open issue -
>>>https://github.com/git-for-windows/git/issues/2576
>>>- Example using repository level config -
>>>https://github.com/jenkinsci/git-client-plugin/pull/595
>>>- Attempt to create that configuration in the git client plugin -
>>>https://github.com/jenkinsci/git-client-plugin/pull/523
>>>- Second attempt to create that configuration in the git client
>>>plugin - https://github.com/jenkinsci/git-client-plugin/pull/537
>>>
>>>
>>> On Tue, Sep 14, 2021 at 9:54 AM Victor Martinez <
>>> victormartinezru...@gmail.com> wrote:
>>>
 Hi all,

 Is there any specific configuration I could apply permanently to avoid
 the below error that happens in https://ci.jenkins.io/ when running
 the tests on Windows?

  > git.exe init
 C:\Users\jenkins\Work\workspace\gins_opentelemetry-plugin_PR-167\target\tmp\j
 h927479030425102413\workspace\co-3 # timeout=10
 Fetching upstream changes from
 https://github.com/jenkinsci/opentelemetry-plugin
 ...
 [Pipeline] }
 [Pipeline] // stage
 [Pipeline] }
 [Pipeline] // node
 [Pipeline] End of Pipeline
 hudson.plugins.git.GitException: Command "git.exe checkout -f
 a1479a055ebb33d6abf48ce9238fb586edc97203" returned status code 1:
 stdout:
 stderr: error: unable to create file
 src/main/resources/io/jenkins/plugins/opentelemetry/JenkinsOpenTelemetryPluginConfiguration/help-exportOtelConfigurationAsEnvironmentVariables.html:
 Filename too long

 I've been shorting the pipeline names for the time being, but I think
 the workaround doesn't work anymore.

 Thanks so much.

 --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Developers" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/e9e92f22-2b38-48fb-86ac-7e216d67db61n%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/CAO49JtF8rg%3D43JRe1NQt%3Dxv8Pyhqe9dVeehUmrWWh_L4vyFfGQ%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 

Re: Filename too long issues in https://ci.jenkins.io/ on Windows workers

['Gavin Mogan' via Jenkins Developers]

Isn't all the advice specific to building locally? The problem was stated
on CI.jenkins

So I'm guessing an infra ticket/pr to enable the Reg key?and maybe agents
should be on the root instead of users Jenkins work?

On Tue., Sep. 14, 2021, 9:53 a.m. Slide,  wrote:

> You could try this when building the images for Windows:
>
> reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
> /v LongPathsEnabled /t REG_DWORD /d 1
>
> This should enable long file names in the OS itself
>
> On Tue, Sep 14, 2021 at 9:09 AM Mark Waite 
> wrote:
>
>> I've not found a technique that resolves the issue for all cases.  Some
>> of the techniques we've tried with varying levels of non-success have
>> included:
>>
>>- Shorten the job name and file path as much as possible (C:\J
>>instead of C:\Users\Jenkins\Work) (helps, but doesn't fix it, could be
>>applied to ci.jenkins.io configuration and our Windows image
>>generation )
>>- Git config system level core.longpaths true (seems to help in some
>>cases, but doesn't fix it in all cases
>>) (this change
>>could be applied in the Windows image generation for ci.jenkins.io,
>>since we have that in code now
>>)
>>- Git config repository level core.longpaths true (helps in cases
>>where the initial clone and checkout was successful but later operations
>>failed, can be implemented in the tests of the plugin)
>>
>> Some of the references that provide more information about the issue:
>>
>>- Git for windows open issue -
>>https://github.com/git-for-windows/git/issues/2576
>>- Example using repository level config -
>>https://github.com/jenkinsci/git-client-plugin/pull/595
>>- Attempt to create that configuration in the git client plugin -
>>https://github.com/jenkinsci/git-client-plugin/pull/523
>>- Second attempt to create that configuration in the git client
>>plugin - https://github.com/jenkinsci/git-client-plugin/pull/537
>>
>>
>> On Tue, Sep 14, 2021 at 9:54 AM Victor Martinez <
>> victormartinezru...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> Is there any specific configuration I could apply permanently to avoid
>>> the below error that happens in https://ci.jenkins.io/ when running the
>>> tests on Windows?
>>>
>>>  > git.exe init
>>> C:\Users\jenkins\Work\workspace\gins_opentelemetry-plugin_PR-167\target\tmp\j
>>> h927479030425102413\workspace\co-3 # timeout=10
>>> Fetching upstream changes from
>>> https://github.com/jenkinsci/opentelemetry-plugin
>>> ...
>>> [Pipeline] }
>>> [Pipeline] // stage
>>> [Pipeline] }
>>> [Pipeline] // node
>>> [Pipeline] End of Pipeline
>>> hudson.plugins.git.GitException: Command "git.exe checkout -f
>>> a1479a055ebb33d6abf48ce9238fb586edc97203" returned status code 1:
>>> stdout:
>>> stderr: error: unable to create file
>>> src/main/resources/io/jenkins/plugins/opentelemetry/JenkinsOpenTelemetryPluginConfiguration/help-exportOtelConfigurationAsEnvironmentVariables.html:
>>> Filename too long
>>>
>>> I've been shorting the pipeline names for the time being, but I think
>>> the workaround doesn't work anymore.
>>>
>>> Thanks so much.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/e9e92f22-2b38-48fb-86ac-7e216d67db61n%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/CAO49JtF8rg%3D43JRe1NQt%3Dxv8Pyhqe9dVeehUmrWWh_L4vyFfGQ%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/CAPiUgVe8abek4JJrgsz-MxrFnG9-DsxaWnotn2ytFfzEpBGORw%40mail.gmail.com
> 

Re: Filename too long issues in https://ci.jenkins.io/ on Windows workers

[Slide]

You could try this when building the images for Windows:

reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
/v LongPathsEnabled /t REG_DWORD /d 1

This should enable long file names in the OS itself

On Tue, Sep 14, 2021 at 9:09 AM Mark Waite 
wrote:

> I've not found a technique that resolves the issue for all cases.  Some of
> the techniques we've tried with varying levels of non-success have included:
>
>- Shorten the job name and file path as much as possible (C:\J instead
>of C:\Users\Jenkins\Work) (helps, but doesn't fix it, could be applied to
>ci.jenkins.io configuration and our Windows image generation
>)
>- Git config system level core.longpaths true (seems to help in some
>cases, but doesn't fix it in all cases
>) (this change
>could be applied in the Windows image generation for ci.jenkins.io,
>since we have that in code now
>)
>- Git config repository level core.longpaths true (helps in cases
>where the initial clone and checkout was successful but later operations
>failed, can be implemented in the tests of the plugin)
>
> Some of the references that provide more information about the issue:
>
>- Git for windows open issue -
>https://github.com/git-for-windows/git/issues/2576
>- Example using repository level config -
>https://github.com/jenkinsci/git-client-plugin/pull/595
>- Attempt to create that configuration in the git client plugin -
>https://github.com/jenkinsci/git-client-plugin/pull/523
>- Second attempt to create that configuration in the git client plugin
>- https://github.com/jenkinsci/git-client-plugin/pull/537
>
>
> On Tue, Sep 14, 2021 at 9:54 AM Victor Martinez <
> victormartinezru...@gmail.com> wrote:
>
>> Hi all,
>>
>> Is there any specific configuration I could apply permanently to avoid
>> the below error that happens in https://ci.jenkins.io/ when running the
>> tests on Windows?
>>
>>  > git.exe init
>> C:\Users\jenkins\Work\workspace\gins_opentelemetry-plugin_PR-167\target\tmp\j
>> h927479030425102413\workspace\co-3 # timeout=10
>> Fetching upstream changes from
>> https://github.com/jenkinsci/opentelemetry-plugin
>> ...
>> [Pipeline] }
>> [Pipeline] // stage
>> [Pipeline] }
>> [Pipeline] // node
>> [Pipeline] End of Pipeline
>> hudson.plugins.git.GitException: Command "git.exe checkout -f
>> a1479a055ebb33d6abf48ce9238fb586edc97203" returned status code 1:
>> stdout:
>> stderr: error: unable to create file
>> src/main/resources/io/jenkins/plugins/opentelemetry/JenkinsOpenTelemetryPluginConfiguration/help-exportOtelConfigurationAsEnvironmentVariables.html:
>> Filename too long
>>
>> I've been shorting the pipeline names for the time being, but I think the
>> workaround doesn't work anymore.
>>
>> Thanks so much.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/e9e92f22-2b38-48fb-86ac-7e216d67db61n%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/CAO49JtF8rg%3D43JRe1NQt%3Dxv8Pyhqe9dVeehUmrWWh_L4vyFfGQ%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/CAPiUgVe8abek4JJrgsz-MxrFnG9-DsxaWnotn2ytFfzEpBGORw%40mail.gmail.com.

Re: Filename too long issues in https://ci.jenkins.io/ on Windows workers

[Mark Waite]

I've not found a technique that resolves the issue for all cases.  Some of
the techniques we've tried with varying levels of non-success have included:

   - Shorten the job name and file path as much as possible (C:\J instead
   of C:\Users\Jenkins\Work) (helps, but doesn't fix it, could be applied to
   ci.jenkins.io configuration and our Windows image generation
   )
   - Git config system level core.longpaths true (seems to help in some
   cases, but doesn't fix it in all cases
   ) (this change could
   be applied in the Windows image generation for ci.jenkins.io, since we
   have that in code now )
   - Git config repository level core.longpaths true (helps in cases where
   the initial clone and checkout was successful but later operations failed,
   can be implemented in the tests of the plugin)

Some of the references that provide more information about the issue:

   - Git for windows open issue -
   https://github.com/git-for-windows/git/issues/2576
   - Example using repository level config -
   https://github.com/jenkinsci/git-client-plugin/pull/595
   - Attempt to create that configuration in the git client plugin -
   https://github.com/jenkinsci/git-client-plugin/pull/523
   - Second attempt to create that configuration in the git client plugin -
   https://github.com/jenkinsci/git-client-plugin/pull/537


On Tue, Sep 14, 2021 at 9:54 AM Victor Martinez <
victormartinezru...@gmail.com> wrote:

> Hi all,
>
> Is there any specific configuration I could apply permanently to avoid the
> below error that happens in https://ci.jenkins.io/ when running the tests
> on Windows?
>
>  > git.exe init
> C:\Users\jenkins\Work\workspace\gins_opentelemetry-plugin_PR-167\target\tmp\j
> h927479030425102413\workspace\co-3 # timeout=10
> Fetching upstream changes from
> https://github.com/jenkinsci/opentelemetry-plugin
> ...
> [Pipeline] }
> [Pipeline] // stage
> [Pipeline] }
> [Pipeline] // node
> [Pipeline] End of Pipeline
> hudson.plugins.git.GitException: Command "git.exe checkout -f
> a1479a055ebb33d6abf48ce9238fb586edc97203" returned status code 1:
> stdout:
> stderr: error: unable to create file
> src/main/resources/io/jenkins/plugins/opentelemetry/JenkinsOpenTelemetryPluginConfiguration/help-exportOtelConfigurationAsEnvironmentVariables.html:
> Filename too long
>
> I've been shorting the pipeline names for the time being, but I think the
> workaround doesn't work anymore.
>
> Thanks so much.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/e9e92f22-2b38-48fb-86ac-7e216d67db61n%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/CAO49JtF8rg%3D43JRe1NQt%3Dxv8Pyhqe9dVeehUmrWWh_L4vyFfGQ%40mail.gmail.com.

Filename too long issues in https://ci.jenkins.io/ on Windows workers

[Victor Martinez]

Hi all,

Is there any specific configuration I could apply permanently to avoid the 
below error that happens in https://ci.jenkins.io/ when running the tests 
on Windows?

 > git.exe init 
C:\Users\jenkins\Work\workspace\gins_opentelemetry-plugin_PR-167\target\tmp\j 
h927479030425102413\workspace\co-3 # timeout=10
Fetching upstream changes from 
https://github.com/jenkinsci/opentelemetry-plugin
...
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
hudson.plugins.git.GitException: Command "git.exe checkout -f 
a1479a055ebb33d6abf48ce9238fb586edc97203" returned status code 1:
stdout: 
stderr: error: unable to create file 
src/main/resources/io/jenkins/plugins/opentelemetry/JenkinsOpenTelemetryPluginConfiguration/help-exportOtelConfigurationAsEnvironmentVariables.html:
 
Filename too long

I've been shorting the pipeline names for the time being, but I think the 
workaround doesn't work anymore.

Thanks so much.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e9e92f22-2b38-48fb-86ac-7e216d67db61n%40googlegroups.com.

Re: Is an explicit dependency on jenkins-test-harness now needed?

[Jesse Glick]

On Tue, Sep 14, 2021 at 5:55 AM Oleg Nenashev 
wrote:

> it is time [to] include JCasC test harness […] into Jenkins Test Harness
>

Not possible. It depends on plugins.


> or to Plugin POM
>

No. If you want to depend on JCasC the `bom` sets up versions for you. (For
most cases you should not need to explicitly mention JCasC in your plugin
since you should just be defining settings using simple, plain idioms that
work automatically in any context—GUI forms, Pipeline, JCasC. It is
necessary however when you are forced into weird Java structures for
compatibility reasons.)

The correct solution here is to update the parent POM as Tim says, or use
an older version of JCasC. If your IDE does not let you run a current
version of a tool, run it from a shell instead, or use a different IDE to
run local tests. As a workaround you could specify an explicit
`jenkins-test-harness.version` in your POM pending a parent update, or even
try to add an `exclusion` from
`io.jenkins.configuration-as-code:test-harness` and hope that JCasC was not
actually relying on recently introduced features.

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

Re: Is an explicit dependency on jenkins-test-harness now needed?

[Chris Kilding]

> IMHO it is time to make one step forward and to include JCasC test harness 
> and into Jenkins Test Harness or to Plugin POM by default. There is wide 
> adoption of JCasC test automation thanks to so many contributors, and IMHO 
> there is no particular point in making users to explicitly define it these 
> days. Opinions?

+1 from my perspective, as a plugin developer who uses them. (Though the people 
that maintain them may have a different view.)

Chris

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4bd1fabd-0ba4-412f-9093-00c0dffacb9c%40www.fastmail.com.

Re: Is an explicit dependency on jenkins-test-harness now needed?

[Chris Kilding]

I'm a bit stuck on that as parent POM 4.20+ requires Maven 3.8.1+. IntelliJ's 
embedded Maven is only 3.6.2 at the moment which leads to build troubles inside 
the IDE.

I emailed Jetbrains support to ask if they can bump the embedded Maven version 
to at least 3.8.1 - but that'll be a while coming. If they're going to do it 
we're probably looking this landing in IDEA 2022.1.

I believe there is a ticket for this on Youtrack that can be upvoted: 
https://youtrack.jetbrains.com/issue/IDEA-274703

Chris

On Tue, 14 Sep 2021, at 11:27 AM, Tim Jacomb wrote:
> Yeah that happens when JCasC bumps the parent pom, you need to bump your 
> parent pom as well
> 
> On Tue, 14 Sept 2021 at 10:55, Oleg Nenashev  wrote:
>> I'd guess it is a temporary issue caused by JCasC test dependency being 
>> higher than your current version of Plugin POM. JCasC test harness depends 
>> on JTH explicitly.
>> 
>> IMHO it is time to make one step forward and to include JCasC test harness 
>> and into Jenkins Test Harness or to Plugin POM by default. There is wide 
>> adoption of JCasC test automation thanks to so many contributors, and IMHO 
>> there is no particular point in making users to explicitly define it these 
>> days. Opinions?
>> On Tuesday, September 14, 2021 at 11:44:57 AM UTC+2 Chris Kilding wrote:
>>> Hi, 
>>> 
>>> I've seen the following dependency error in 2 plugins regarding 
>>> jenkins-test-harness: 
>>> 
>>> Require upper bound dependencies error for 
>>> org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 paths to 
>>> dependency are: 
>>> 22:20:04 
>>> +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT 
>>> 22:20:04 +-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 
>>> 22:20:04 and 
>>> 22:20:04 
>>> +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT 
>>> 22:20:04 +-io.jenkins.configuration-as-code:test-harness:1.52 
>>> 22:20:04 +-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 
>>> (managed) <-- org.jenkins-ci.main:jenkins-test-harness:1589.vc23fca066d5c 
>>> 
>>> Both projects use CasC, so they have been inheriting the actual 
>>> jenkins-test-harness dependency transitively through config-as-code test 
>>> harness. This was fine until BOM 937.v51fde92016ed, when the error started. 
>>> 
>>> Is it now necessary to include an explicit jenkins-test-harness dependency 
>>> in a project's POM (to fix this), and if so is this stated anywhere? 
>>> 
>>> Regards, 
>>> 
>>> Chris 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/033ceeaf-187a-4012-9f7a-c576d172fdfcn%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-3BidX-c4%3DBZaDaeXh%3D1L2LL4xq0TMCbwCncG%3DuRi_MKTiCQ%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/6ac125fa-6f6e-44a8-bae5-625d3e1e1e4f%40www.fastmail.com.

Re: Is an explicit dependency on jenkins-test-harness now needed?

[Tim Jacomb]

Yeah that happens when JCasC bumps the parent pom, you need to bump your
parent pom as well

On Tue, 14 Sept 2021 at 10:55, Oleg Nenashev  wrote:

> I'd guess it is a temporary issue caused by JCasC test dependency being
> higher than your current version of Plugin POM. JCasC test harness depends
> on JTH explicitly.
>
> IMHO it is time to make one step forward and to include JCasC test harness
> and into Jenkins Test Harness or to Plugin POM by default. There is wide
> adoption of JCasC test automation thanks to so many contributors, and IMHO
> there is no particular point in making users to explicitly define it these
> days. Opinions?
>
> On Tuesday, September 14, 2021 at 11:44:57 AM UTC+2 Chris Kilding wrote:
>
>> Hi,
>>
>> I've seen the following dependency error in 2 plugins regarding
>> jenkins-test-harness:
>>
>> Require upper bound dependencies error for
>> org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 paths to
>> dependency are:
>> 22:20:04
>> +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT
>> 22:20:04 +-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33
>> 22:20:04 and
>> 22:20:04
>> +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT
>> 22:20:04 +-io.jenkins.configuration-as-code:test-harness:1.52
>> 22:20:04 +-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33
>> (managed) <-- org.jenkins-ci.main:jenkins-test-harness:1589.vc23fca066d5c
>>
>> Both projects use CasC, so they have been inheriting the actual
>> jenkins-test-harness dependency transitively through config-as-code test
>> harness. This was fine until BOM 937.v51fde92016ed, when the error started.
>>
>> Is it now necessary to include an explicit jenkins-test-harness
>> dependency in a project's POM (to fix this), and if so is this stated
>> anywhere?
>>
>> Regards,
>>
>> Chris
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/033ceeaf-187a-4012-9f7a-c576d172fdfcn%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-3BidX-c4%3DBZaDaeXh%3D1L2LL4xq0TMCbwCncG%3DuRi_MKTiCQ%40mail.gmail.com.

Re: Jenkins Election 2021 Proposal

[Oleg Nenashev]

Hello. Sorry for the delay, I finally got some time to work on my community 
backlog.
Thanks to Olivier for stepping up and leading the election process this 
year!

On Thursday, September 2, 2021 at 10:38:13 AM UTC+2 Olblak wrote:

> Hi Everybody,
>
> As you may guess with the title, I am looking for feedback regarding the 
> upcoming election.
> I would like to validate this process by next week's Governance meeting
>
> Feel free to add your suggestion or feedback on community.jenkins.io 
> 
>
> Cheers
>

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

Re: Hacktoberfest CI Load

[Oleg Nenashev]

It is a good question to discuss with the Infra Team. I have added it to 
the contributor summit logistics Google Doc, because this is the weekend 
when the load is expected to spike the 
most. 
https://docs.google.com/document/d/1QLWXNG23ui-LvQXth3UREzOvLYgTMSZcv-El0H141a4/edit#heading=h.jhodwcaw6jcl

FTR last year we did not have serious issues with CI, because we did not 
promote the event too much. In 2019 we had a massive CI outage in the 
beginning of the event, so James definitely has a point. We are interested 
to keep our CI stable to provide good contributor experience, whether they 
participate in Hacktoberfest or not



On Friday, September 10, 2021 at 7:06:55 PM UTC+2 ga...@gavinmogan.com 
wrote:

> ooh maybe use some of our digital ocean credits to expand build capacity
>
> On Fri, Sep 10, 2021 at 10:00 AM Jesse Glick  wrote:
>
>> On Fri, Sep 10, 2021 at 11:32 AM jn...@cloudbees.com  
>> wrote:
>>
>>> I at least hope to find some time to get the ATH to zero failures at 
>>> some point.
>>>
>>
>> That would be great!
>>
>> Is there a plan to increase the capacity (temporarily or not)
>>>
>>
>> or INFRA-1633  
>>
>> -- 
>> You received this message because you are 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/CANfRfr1ZvaDVX-MyDgF2CtDD5eNSAcxeMVSr4uk_5RPgCEyt1A%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/65a1b306-0777-4ffd-8418-f1cb60edcf39n%40googlegroups.com.

Re: Is an explicit dependency on jenkins-test-harness now needed?

[Oleg Nenashev]

I'd guess it is a temporary issue caused by JCasC test dependency being 
higher than your current version of Plugin POM. JCasC test harness depends 
on JTH explicitly.

IMHO it is time to make one step forward and to include JCasC test harness 
and into Jenkins Test Harness or to Plugin POM by default. There is wide 
adoption of JCasC test automation thanks to so many contributors, and IMHO 
there is no particular point in making users to explicitly define it these 
days. Opinions?

On Tuesday, September 14, 2021 at 11:44:57 AM UTC+2 Chris Kilding wrote:

> Hi,
>
> I've seen the following dependency error in 2 plugins regarding 
> jenkins-test-harness:
>
> Require upper bound dependencies error for 
> org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 paths to 
> dependency are:
> 22:20:04 
> +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT
> 22:20:04 +-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33
> 22:20:04 and
> 22:20:04 
> +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT
> 22:20:04 +-io.jenkins.configuration-as-code:test-harness:1.52
> 22:20:04 +-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 
> (managed) <-- org.jenkins-ci.main:jenkins-test-harness:1589.vc23fca066d5c
>
> Both projects use CasC, so they have been inheriting the actual 
> jenkins-test-harness dependency transitively through config-as-code test 
> harness. This was fine until BOM 937.v51fde92016ed, when the error started.
>
> Is it now necessary to include an explicit jenkins-test-harness dependency 
> in a project's POM (to fix this), and if so is this stated anywhere?
>
> Regards,
>
> Chris
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/033ceeaf-187a-4012-9f7a-c576d172fdfcn%40googlegroups.com.

Is an explicit dependency on jenkins-test-harness now needed?

[Chris Kilding]

Hi,

I've seen the following dependency error in 2 plugins regarding 
jenkins-test-harness:

Require upper bound dependencies error for 
org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 paths to dependency 
are:
22:20:04  +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT
22:20:04+-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33
22:20:04  and
22:20:04  +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT
22:20:04+-io.jenkins.configuration-as-code:test-harness:1.52
22:20:04  +-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 
(managed) <-- org.jenkins-ci.main:jenkins-test-harness:1589.vc23fca066d5c

Both projects use CasC, so they have been inheriting the actual 
jenkins-test-harness dependency transitively through config-as-code test 
harness. This was fine until BOM 937.v51fde92016ed, when the error started.

Is it now necessary to include an explicit jenkins-test-harness dependency in a 
project's POM (to fix this), and if so is this stated anywhere?

Regards,

Chris

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e6219bea-d623-43d4-b488-727841b10bbc%40www.fastmail.com.