On Wed, Sep 6, 2017 at 1:36 PM, Shaun Thompson wrote:
> This happens after Jenkins notes that it's fully up and running.
Then I have no clue; try to create a minimal, self-contained,
reproducible test case that a core dev could analyze.
--
You received this message because
This happens after Jenkins notes that it's fully up and running.
On Tue, Sep 5, 2017 at 5:07 PM Jesse Glick wrote:
> Perhaps you are attempting to schedule the build early during Jenkins
> startup, before state is actually initialized? Just a guess.
>
> --
> You received
Perhaps you are attempting to schedule the build early during Jenkins
startup, before state is actually initialized? Just a guess.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails
I have a WorkflowJob that I've created dynamically on the installation of
my custom plugin. I'm running into the issue noted in the subject when
scheduling a build after a restart of Jenkins - testing locally.
```
workflowJob.scheduleBuild2(0, new SomeAction());
```
I thought the job would