search

tabeyti / jenkins-jack

Jack into your Jenkins to execute Pipeline scripts, provide Pipeline step autocompletions, pull Shared Library step documenation, run console groovy scripts across multiple nodes, and more! Honestly, not that much more.
Other
97 stars 32 forks source link

Filter pipelines & jobs by subfolder #40

Open nlaplante opened 3 years ago

nlaplante commented 3 years ago

I added the subfolder in the connection url:

http://JENKINS_HOST/some/subfolder/here but Jenkins Jack lists every pipeline from every other folder on the Jenkins host. There are several dozens of them and I only wish to see the ones under the folder in the Jenkins host url. Is that doable?

tabeyti commented 3 years ago

Hey @nlaplante

This is now added in 1.1.1. If you could please validate it's working for you, I'd appreciate it.

tabeyti commented 3 years ago

Fixed issue with feature in 1.1.2. You can find how to use the filter here.

Inetov commented 3 years ago

@tabeyti I've trying use folderFilter at version 1.1.2 and it's doesn't work. My config: изображение

But Jack creates jobs at root directory.

tabeyti commented 3 years ago

Hey @Inetov ,

First thing I notice is that the connection config isn't active: true, but that may on purpose for for your example.

What type of errors are you getting with the folderFilter in place?

Inetov commented 3 years ago

What type of errors are you getting with the folderFilter in place?

I don't see any errors, just the job creates in Jenkins root. The directory 'Jack_tests' is exists but remains empty.

tabeyti commented 3 years ago

@Inetov this should all be fixed for in 1.1.3 Here is a quick tutorial for creating a pipeline, allowing you to specify a folder to create your job under: https://github.com/tabeyti/jenkins-jack/blob/master/TUTORIAL.md#creating-a-pipeline

VeteranCoder commented 2 years ago

Hello. I see this is still open, which is good because I am having this problem. I'm on v1.2.1 and adding a filter to the connection causes a connection failure after edit, although I can still use the panel. That tells me there was a failure on the update, but it can still connect.

I also use the multi-branch pipeline, and I figure it doesn't show up in the pipeline list because it still isn't supported. This could also be the cause of the filter error because my pipeline isn't even in the list. Since most of the useful features come through the pipeline, this plugin is of limited use to me, but I really want to use it.

The job list, also huge for me, doesn't recognize the filter. If the filter does not depend on the presence of a pipeline, then this feature is still broken. In fact, if it does require a matching pipeline, then I think it should be enhanced to separate this into two filter algorithms.

I would be surprised if most mid to large companies were not using multi-branch pipeline, so I personally think it is an important feature to add. I added my support to the feature request issue.

Inetov commented 2 years ago

@Inetov this should all be fixed for in 1.1.3

I forgot to check when you wrote, sorry! now this feature works for me on version v1.2.1