On 11/06/17 17:42, Daniel Beck wrote:
>> However, I still see some dependencies which seem bogus to me.
>
> All of those plugins implement features to support their use in
> Pipeline, so have a dependency on them.
Thank you.
Pipeline is dependent on them, or they are dependent on Pipeline? If t
> On 7. Nov 2017, at 00:57, CLOSE Dave wrote:
>
> However, I still see some dependencies which seem bogus to me.
All of those plugins implement features to support their use in Pipeline, so
have a dependency on them.
--
You received this message because you are subscribed to the Google Group
On 11/06/17 13:46, Daniel Beck wrote:
>> But the instance which concerns me at the moment says Token Macro
>> Plugin is dependent on Pipeline.
>
> token-macro 2.2 had the dependency, it was dropped in 2.3. Which are
> the versions you're using.
Thank you. I was using 2.2. I had deferred updates
> On 6. Nov 2017, at 21:52, CLOSE Dave wrote:
>
> But the instance which concerns me at the moment says Token Macro Plugin is
> dependent on Pipeline.
token-macro 2.2 had the dependency, it was dropped in 2.3. Which are the
versions you're using.
--
You received this message because you are
On 11/03/17 18:27, Stephen Connolly wrote:
>> Every one of the Pipeline plugins, all 23 of them, claim to be dependent
>> on some other plugins. None offer the option to disable. The chain seems
>> endless. And many of the plugins asserted to be dependent are ones I want
>> to keep, such as Pipeli
On 11/04/17 05:08, Daniel Beck wrote:
>> Look for the list entry just called 'Pipeline' (or search for
>> pipeline-aggregator in the search box).
> Oops -- used to be called workflow, so workflow-aggregator.
>> Try to disable it. If the checkbox is disabled and you cannot, file
>> a bug against
> On 4. Nov 2017, at 13:02, Daniel Beck wrote:
>
> Look for the list entry just called 'Pipeline' (or search for
> pipeline-aggregator in the search box).
Oops -- used to be called workflow, so workflow-aggregator.
> Try to disable it. If the checkbox is disabled and you cannot, file a bug
>
> On 3. Nov 2017, at 18:22, CLOSE Dave wrote:
>
> Every one of the Pipeline plugins, all 23 of them, claim to be dependent
> on some other plugins. None offer the option to disable. The chain seems
> endless. And many of the plugins asserted to be dependent are ones I
> want to keep, such as Pip
Out of this thread but related to the attached screenshot, please obfuscate
the jenkins url :)
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+
On Fri 3 Nov 2017 at 19:21, CLOSE Dave
wrote:
> >> Every one of the Pipeline plugins, all 23 of them, claim to be
> >> dependent on some other plugins. None offer the option to disable.
> >> The chain seems endless. And many of the plugins asserted to be
> >> dependent are ones I want to keep, su
That's odd, according to the pom [1] the only non-test dependency is on the
structs plugins.
Can you show a screenshot or something that shows this dependency info?
1 -
https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/pom.xml#L82
On Fri, Nov 3, 2017 at 10:23 AM CLOSE Dave
wro
On 11/03/17 03:05, Daniel Beck wrote:
> If you're not using Declarative (or even Pipeline), I'd start
> disabling things there. (On the plugins manager UI, disabling plugins
> enables checkboxes of plugins that can then be disabled because
> nothing else depends on them, etc. -- much easier than de
> On 3. Nov 2017, at 02:17, CLOSE Dave wrote:
>
> I think part of the trouble with the seemingly endless dependency chain
> may be the Pipeline plugins. Most if not all of the other plugins seem
> to define the other plugins on which they are dependent. The Pipeline
> plugins, in contrast, defin
Daniel Beck wrote:
> Without a list of plugins (and versions) on the other instance it's
> impossible to say why might these differ.
Ok. Here's another instance with 73 plugins listed below. Again, the
Graphviz dot file is attached.
Ant Plugin 1.2
Apache HttpComponents Client 4.x API Plugin
> On 3. Nov 2017, at 00:41, CLOSE Dave wrote:
>
> I know that the dependencies are broken because I have another Jenkins
> instance with nearly all the same plugins but without Docker Commons
> Plugin.
Without a list of plugins (and versions) on the other instance it's impossible
to say why mi
I have a Jenkins server (2.87) with quite a few plugins installed. 95,
actually. I don't actually need some of them and I like to clean things
up a bit. But that doesn't seem practical.
Here's the list of installed plugins.
Ant Plugin 1.7
Audit Trail 2.2
Authentication Tokens API Plugin 1.3
16 matches
Mail list logo
