Am Mi., 15. Apr. 2020 um 08:16 Uhr schrieb Boyka Zhu :
> Hi,
>
> I wrote a Jenkins plugin, and installed(plugin manager advance ->uploaded)
> in Jenkins.
> When I have new version, I upload the new hpi, It will upgrade to new
> version automatically.
>
use mvn hpi:run
to start a local jenkis inst
Could it be that this affects the latest release of cmakebuilder, too?
Version 2.6.3 was release about 2 week ago but is not even showing up
at https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/cmakebuilder/
Am Do., 21. Nov. 2019 um 12:39 Uhr schrieb Akram Ben Aissi
:
>
> it was done alr
2017-07-09 15:40 GMT+02:00 'Nikolas Falco' via Jenkins Developers
:
> @15knots this issue is not caused by the envinject plugin (I had try this
> when I got the issue).
Sorry, I have to disagree here. If I uninstall or disable the
envinject plugin, the issue is gone.
>
> As you can see in the JIR
2017-07-06 13:45 GMT+02:00 15 knots :
> 2017-07-06 0:27 GMT+02:00 Jesse Glick :
>> On Wed, Jul 5, 2017 at 3:43 PM, Martin Weber
>> wrote:
> ...
>>> Maybe one of the plugins installed on my production Jenkins interferes here?
>>
>> Conceivable.
>
> F
2017-07-06 0:29 GMT+02:00 Daniel Beck :
>
>> On 6. Jul 2017, at 00:27, Jesse Glick wrote:
>>
>> Uh, really? Is this reproducible in a minimal self-contained test
>> case?
>
> FWIW I remember a really old bug report about that, maybe this is "known"
> already.
Quite new: https://issues.jenkins-ci
2017-07-06 0:27 GMT+02:00 Jesse Glick :
> On Wed, Jul 5, 2017 at 3:43 PM, Martin Weber
> wrote:
...
>> Maybe one of the plugins installed on my production Jenkins interferes here?
>
> Conceivable.
Found the culprit: Environment Injector Plugin
Should I file a bug report?
--
You received this m
