Lines Matching full:build
17 * This class manages the build of code snippets with doxygen for cross referencing.
19 * Job: A build job is a single code snippet.
21 * Task: A build task has one or multiple build jobs.
24 * The build is executed in build tasks that are either directly executed or scheduled with
27 * should then try to build the code snippet again.
29 * Depending on the used tag files for doxygen, each build can both take long and be ressource
31 * is enforced with a lock that indicates if doxygen is running or not. In case of immediate build
32 * tasks through tryBuildNow() the buildmanager will then try to schedule the build task.
34 * If a build with the same TaskID is already running, a new TaskID will be randomly created.
88 * Add a build job to the task runner builder and create or update a build task if necessary.
90 * This function adds a new build job to the Jobs table in sqlite.
91 …* Each build job corresponds to a build task. If no build task exists for the build job it will cr…
94 * If the build task for this build job is existing it will try to
96 …* If the build task is already running, we don't want to interfere the doxygen build process. In t…
97 * we create a new build task for this build job with a random taskID.
99 * @param String $jobID Identifier for this build job
102 * @return Bool If adding the build job was successful
119 // this means that the build directory probably was already deleted
120 … // we can just recreate the directory or put our job into the existing build directory
178 * Try to immediately build a code snippet.
181 * In that case we try to add the build job to the build queue (if sqlite is available).
183 * @param String $jobID Identifier for this build job
187 * @return Bool If build or adding it to the build queue as a build job was successful
195 // we cannot build now because only one doxygen instance is allowed at a time!
203 // no doxygen instance is running - we can immediately build the file!
205 …// TODO: should we also create entries for Task and Job in sqlite if we directly build the snippet?
231 * Get the state of a build task from the Tasks table in sqlite.
235 * @param String $id TaskID of the build task
255 * Get the state of a build job.
257 * Here we first lookup the corresponding build task for the build job and then lookup
260 * @param String $jobID JobID for this build job
283 * Return the doxygen relevant build task configuration of a build task.
290 * @param String $taskID TaskID for this build task
310 * Return the doxygen relevant build task configuration configuration of a build job.
339 * Get the HTML relevant configuration of a build job.
423 * Execute a doxygen task runner build task.
425 * We obtain the build task from the Tasks table in sqlite.
426 * The build task row includes used tag files from the snippet syntax.
428 * We then load the tag file configuration for those tag files and try to execute the build.
430 * After the doxygen process exited we update the build task state in sqlite.
432 * @param String $taskID TaskID for this build task
468 // this just returns the build dir if already existent
565 // now extract the XML files from the build directory
627 * Delete the temporary build task directory.
629 * @param String $dirPath Build directory where doxygen is executed.
641 * Create the source file in the build directory of the build task.
644 * First we try to create the temporary build directory.
646 * We than place the content of the code snippet in a source file in the build directory.
652 * @param String $jobID JobID for this build job
665 … // we expect a cache filename (md5) - the xml output from the build job will have this filename
679 * Get a list of scheduled build tasks from the Tasks table in sqlite.
681 * @param Num $amount Amount of build tasks to return.
682 * @return Array Build tasks
686 // get build tasks from SQLite
688 // first one is the one currently built or the next one do build
711 * task runner build from the syntax). Here we filter those values out.