Archives/ohwgiles_laminar
1
0
Fork 0
mirror of https://github.com/ohwgiles/laminar.git synced 2025-06-13 12:54:29 +00:00
Code Issues Projects Releases Wiki Activity
d51c4ae6f7
ohwgiles_laminar/src/context.h

41 lines
1.2 KiB
C
Raw Normal View History

Initial commit
2015-09-13 20:25:26 +00:00
///
allow contexts to specify accepted jobs using a glob expression, the same way jobs can specify contexts. This allows more flexibility in situations where there are many jobs sharing limited contexts because it may obviate the need to create a conf file for each job. resolves #124
2020-11-13 00:47:02 +00:00
/// Copyright 2015-2020 Oliver Giles
Initial commit
2015-09-13 20:25:26 +00:00
///
/// This file is part of Laminar
///
/// Laminar is free software: you can redistribute it and/or modify
/// it under the terms of the GNU General Public License as published by
/// the Free Software Foundation, either version 3 of the License, or
/// (at your option) any later version.
///
/// Laminar is distributed in the hope that it will be useful,
/// but WITHOUT ANY WARRANTY; without even the implied warranty of
/// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
/// GNU General Public License for more details.
///
/// You should have received a copy of the GNU General Public License
/// along with Laminar. If not, see <http://www.gnu.org/licenses/>
///
Replace nodes/tags with contexts The nodes/tags system has not been particularly successful, it's not as intuitive as it could be, and in an attempt to be a single feature to address many use cases, ends up addressing none of them particularly well. This commit replaces nodes and tags with contexts. Each job may define which context(s) the job may be associated with. Laminar will only pop the job off the waiting queue when it can be assigned to a context. A context defines an integer number of executors, which represents how many runs can be simultaneously assigned to it. A context may provide extra environment variables. Essentially, a context replaces a node, and tags are gone. You just assign jobs to contexts directly, and you can use a glob expression. This should be more intuitive. For grouping jobs in the WebUI, a separate mechanism called "groups" is provided.
2019-12-13 08:42:22 +00:00
#ifndef LAMINAR_CONTEXT_H_
#define LAMINAR_CONTEXT_H_
Initial commit
2015-09-13 20:25:26 +00:00
#include <string>
support for job and node tags
2015-09-24 20:02:11 +00:00
#include <set>
Initial commit
2015-09-13 20:25:26 +00:00
class Run;
Replace nodes/tags with contexts The nodes/tags system has not been particularly successful, it's not as intuitive as it could be, and in an attempt to be a single feature to address many use cases, ends up addressing none of them particularly well. This commit replaces nodes and tags with contexts. Each job may define which context(s) the job may be associated with. Laminar will only pop the job off the waiting queue when it can be assigned to a context. A context defines an integer number of executors, which represents how many runs can be simultaneously assigned to it. A context may provide extra environment variables. Essentially, a context replaces a node, and tags are gone. You just assign jobs to contexts directly, and you can use a glob expression. This should be more intuitive. For grouping jobs in the WebUI, a separate mechanism called "groups" is provided.
2019-12-13 08:42:22 +00:00
// Represents a context within which a Run will be executed. Allows applying
// a certain environment to a set of Jobs, or setting a limit on the number
// of parallel Runs
class Context {
Initial commit
2015-09-13 20:25:26 +00:00
public:
Replace nodes/tags with contexts The nodes/tags system has not been particularly successful, it's not as intuitive as it could be, and in an attempt to be a single feature to address many use cases, ends up addressing none of them particularly well. This commit replaces nodes and tags with contexts. Each job may define which context(s) the job may be associated with. Laminar will only pop the job off the waiting queue when it can be assigned to a context. A context defines an integer number of executors, which represents how many runs can be simultaneously assigned to it. A context may provide extra environment variables. Essentially, a context replaces a node, and tags are gone. You just assign jobs to contexts directly, and you can use a glob expression. This should be more intuitive. For grouping jobs in the WebUI, a separate mechanism called "groups" is provided.
2019-12-13 08:42:22 +00:00
Context() {}
Initial commit
2015-09-13 20:25:26 +00:00
std::string name;
int numExecutors;
int busyExecutors = 0;
allow contexts to specify accepted jobs using a glob expression, the same way jobs can specify contexts. This allows more flexibility in situations where there are many jobs sharing limited contexts because it may obviate the need to create a conf file for each job. resolves #124
2020-11-13 00:47:02 +00:00
std::set<std::string> jobPatterns;
Initial commit
2015-09-13 20:25:26 +00:00
};
Replace nodes/tags with contexts The nodes/tags system has not been particularly successful, it's not as intuitive as it could be, and in an attempt to be a single feature to address many use cases, ends up addressing none of them particularly well. This commit replaces nodes and tags with contexts. Each job may define which context(s) the job may be associated with. Laminar will only pop the job off the waiting queue when it can be assigned to a context. A context defines an integer number of executors, which represents how many runs can be simultaneously assigned to it. A context may provide extra environment variables. Essentially, a context replaces a node, and tags are gone. You just assign jobs to contexts directly, and you can use a glob expression. This should be more intuitive. For grouping jobs in the WebUI, a separate mechanism called "groups" is provided.
2019-12-13 08:42:22 +00:00
#endif // LAMINAR_CONTEXT_H_
Reference in New Issue Copy Permalink