geomag tag added to jobs
Merged
requested to merge ghsc/contractors/nshavers/geomag-algorithms:127-geomag-runner-tags into master
Addresses the need for control over runners by use of geomag tag. #127 (closed)
Merge request reports
Activity
requested review from @erigler
assigned to @nshavers
'geomag' tag was added to appropriate runners by @bgeels, so all should be good to go.
added 2 commits
- Some runners are unable to be modified, so an alternative tag [staging01] is used in those cases.
- Default tag value is [geomag]
- Removed stale code.
Edited by Shavers, Nicholas H- I'm not able to follow/understand a lot of this, and @bgeels has been involved more in the discussion, so I transferred the review to him.
Summary:
- We added a tag to our runners called 'geomag'. This allows us to have more control over which runners pick up our jobs.
- In our YML file, we then added a variable called GEOMAG_TAG.
- This variable is set to 'geomag', or if not an upstream path, it's set to 'staging01'
- This variable is passed as an additional tag for jobs who use Docker, and/or Swarm.
- The conditional logic is executed under workflow ensuring the variable updates.
- The logic is consistent with other logic in the yml for determining whether we are in a developmoent, staging, or production environment.
- Deploy and Swarm Tags removed from Templates.
- The templates tags were being overridden, so its not necessary to add tags to the templates. Removed them to avoid further confusion.
Edited by Shavers, Nicholas Hmentioned in commit 9ae7ab99
Please register or sign in to reply