Hi,
I've been trying to fix a bug in the scmSkip plugin where pipeline job is
marked as aborted, but does not actually stop. I found 4 ways to stop a
WorkflowRun
* calling interrupt on either executor (getExecutor or getOneOffExecutor)
-- effectively what the plugin does right now, it does not
> I didn't remember there were so many
Most of the dependent plugins listed in
https://plugins.jenkins.io/aws-java-sdk/dependencies/ are unreleased for 4+
years though.
On Thursday 21 March 2024 at 18:33:17 UTC+1 Vincent Latombe wrote:
> Thank you both for your inputs,
>
> I made a list of repo
Thanks for all those suggestions. I will apply them and will return to you
for further guidance.
piątek, 22 marca 2024 o 11:53:49 UTC+1 db...@cloudbees.com napisał(a):
> On Fri, Mar 22, 2024 at 11:12 AM DuMaM wrote:
>
>> My work environment requires from me to give users privileges to create
On Fri, Mar 22, 2024 at 11:12 AM DuMaM wrote:
> My work environment requires from me to give users privileges to create
> new jobs, but I need to lock creation of non pipeline jobs.
> I could take a solution proposed a long time ago by Daniel Beck, but I
> fought that maybe it's a good place for
Your problem with the restart is because you configure it in the constructor.
But this is an Extension which is only created once at startup and not every
time a check is performed.
So you will need to fill the projectTypes list in the filter method (and don't
make it a class field).
You might a
Hi,
I'm looking for some answers to questions which pop out during plugin
development.
https://github.com/DuMaM/lock-project-plugin
My work environment requires from me to give users privileges to create new
jobs, but I need to lock creation of non pipeline jobs.
I could take a solution propose
