---
- job:
    name: "elastic+elasticsearch+%BRANCH%+triggers/{periodic-job}-trigger"
    display-name: "{periodic-job}-trigger"
    description: "Scheduled trigger for {periodic-job}"
    node: master
    scm: []
    properties: []
    parameters: []
    publishers: []
    triggers:
      - timed: "{cron}"
    builders:
      - shell: |
          #!/usr/bin/env bash
          set -o pipefail

 * either express or implied. See the License for the specific language
 * governing permissions and limitations under the License.
 */
package org.codelibs.fess.exception;

/**
 * This exception is thrown when a scheduled job fails.
 */
public class ScheduledJobException extends FessSystemException {

    private static final long serialVersionUID = 1L;

    /**
     * Constructor.
     * @param message Exception message.

  private val tasksExecutor = Executors.newCachedThreadPool(threadFactory("TaskFaker"))

  /**
   * True if this task faker has ever had multiple tasks scheduled to run concurrently. Guarded by
   * `this`.
   */
  var isParallel = false

  /** Number of calls to [TaskRunner.Backend.execute]. Guarded by `this`. */
  var executeCallCount = 0

import org.junit.jupiter.api.Test;

@Tag("it")
public class SchedulerTests extends CrudTestBase {

    private static final String NAME_PREFIX = "schedulerTest_";
    private static final String API_PATH = "/api/admin/scheduler";
    private static final String LIST_ENDPOINT_SUFFIX = "settings";
    private static final String ITEM_ENDPOINT_SUFFIX = "setting";

    private static final String KEY_PROPERTY = "name";

    @Override

        () -> {
          totalCalls.incrementAndGet();
          // Make sure that no other tasks are scheduled to run while this is running.
          assertFalse(fakePool.hasNext());
        };

    assertFalse(fakePool.hasNext());
    e.execute(intCounter);
    // A task should have been scheduled
    assertTrue(fakePool.hasNext());
    e.execute(intCounter);
    // Our executor hasn't run any tasks yet.

    * Specifically the new controller watches the API server for scheduled pods. It processes each pod and ensures that any volumes that implement the volume Attacher interface are attached to the node their pod is scheduled to.

            deleteMethod("/api/admin/crawlinginfo/log/" + elem.get("id"));
        }

        // Clean up schedulers
        for (String sId : getSchedulerIds(NAME_PREFIX)) {
            deleteMethod("/api/admin/scheduler/setting/" + sId);
        }

        // Clean up web configs
        for (String wId : getWebConfigIds(NAME_PREFIX)) {
            deleteMethod("/api/admin/webconfig/setting/" + wId);
        }

            deleteMethod("/api/admin/crawlinginfo/log/" + elem.get("id"));
        }

        // Clean up schedulers
        for (String sId : getSchedulerIds(NAME_PREFIX)) {
            deleteMethod("/api/admin/scheduler/setting/" + sId);
        }

        // Clean up web configs
        for (String wId : getWebConfigIds(NAME_PREFIX)) {
            deleteMethod("/api/admin/webconfig/setting/" + wId);
        }

                    if (logger.isDebugEnabled()) {
                        logger.debug("Scheduled job is running: id={}", scheduledJob.getId());
                    }
                    counter.incrementAndGet();
                } else if (logger.isDebugEnabled()) {
                    logger.debug("Scheduled job is not running: id={}", scheduledJob.getId());
                }
            }
        });

    <jsp:include page="/WEB-INF/view/common/admin/sidebar.jsp">
        <jsp:param name="menuCategoryType" value="system"/>
        <jsp:param name="menuType" value="scheduler"/>
    </jsp:include>
    <main class="content-wrapper">
        <div class="content-header">
            <div class="container-fluid">
                <div class="row mb-2">
                    <div class="col-sm-6">