Fix - Concurrent jobs launch: start several cron expressions at the same time #44
Conversation
|
I'm having the exact same issue described / solved in this pull-request. |
|
same problem here! can this pull request get some love? 🙏 |
|
I'm having the same issue too, hope this PR can be merged. |
|
Same issue as described, please merge |
|
Hi everyone, I'm the current maintainer of this plugin. TBH with myself, I lack the time to maintain this plugin, so if somebody can take over the maintenance, I'll be happy to hand it over. Process: https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/ Thanks! |
| @@ -28,14 +29,20 @@ | |||
|
|
|||
| @Test | |||
| public void create() throws Exception { | |||
| ParameterizedCronTabList testObject = ParameterizedCronTabList.create("* * * * *%foo=bar"); | |||
There was a problem hiding this comment.
This second test should be split into a new test
|
@yevhen-hryhorevskyi are you still interested in this PR? |
|
@res0nance Considering the number of comments to merge this PR, yes I'm still interested in it. Let me take care of the comments & merge conflicts later today |
Do you have time to still work on this? Would you like me to continue with this? |
@res0nance , can you please kindly share the schedule of the next release of this plugin? It's been 4 months since last and I am still waiting for the functionality that this PR provides - #47 |
Probably releasing this today because i just wrote PR #105 to supersede this. Once merged there shouldn't be anything else outstanding. |
yevhen-hryhorevskyi
deleted the
fix/multiple-jobs-in-same-minute-start
branch
Hi there,
I liked the plugin and idea of setting up multiple cron expressions with different parameters. I looked through readme and found an image where two jobs (#18, #19) were launched at the same time. That was exactly what I needed.
But, unfortunately, I was not able to setup configuration to run different periodical cron expressions at the same time.
Digging into the code, I realized that this plugin worked differently:
Based on the documentation and real implementation, I concluded that there was a bug in code, or it was the desired behavior and misleading documentation.