Skip to content
This repository has been archived by the owner on Oct 22, 2024. It is now read-only.

Use vagrant boxes for self-hosted runners #5

Closed
mducle opened this issue Feb 8, 2021 · 1 comment · Fixed by #11
Closed

Use vagrant boxes for self-hosted runners #5

mducle opened this issue Feb 8, 2021 · 1 comment · Fixed by #11
Assignees
@wardsimon
Labels
enhancement New feature or request

Comments

@mducle
Copy link
Member

mducle commented Feb 8, 2021

We're planning to use github self-hosted runners for continuous integration. (The runners, have to be self-hosted because we need to use Matlab.)

This implies a security issue if the repository is public. One way around this is to use containers where a fresh instance of the container is used for each job. One idea for doing this is with vagrant boxes which are packaged virtual machines. Hopefully we can run Linux, Windows and Mac OS instances from a single (Linux) server.

The workflow would be:

  1. Manually start boxes for each OS.
  2. They run the self-hosted runner server and wait for a job request.
  3. Run the CI job.
  4. At the end of the job, trigger a web-hook
  5. Web-hook triggers the shutdown of the current instance and launches another instance.
  6. New instance runs self-hosted runner server and waits for a job request.
@mducle mducle mentioned this issue Feb 8, 2021
Open
@wardsimon
Copy link
Collaborator

The demo page https://github.com/spinw/Vagrant_Example is up and running for linux and the README contains all the info. This is ready for demo on Monday and can be put in review.

Note that a running example needs my server running, so not 100% guaranteed outside demo time

@wardsimon wardsimon added the enhancement New feature or request label Feb 17, 2021
@wardsimon wardsimon linked a pull request Feb 17, 2021 that will close this issue
Create vagrant workflow #11
Merged
krishnakumarg1984 added a commit that referenced this issue Mar 4, 2021
@krishnakumarg1984 @mducle
# This is a combination of 6 commits.
3133056 
# This is the 1st commit message:

updates the descriptive comments for the biquadratic hamiltonia constructor to be consistent with updated argument names

# This is the commit message #2:

Update swfiles/+sw_classes/biquadratic_hamiltonian.m

Use more descriptive names for the biquadratic hamiltonian constructor

Co-authored-by: Anders Markvardsen <[email protected]>
# This is the commit message #3:

Renames the arguments of the hamiltonian class constructor to better
reflect its meaning

# This is the commit message #4:

Wrote a brief description of the variable 'nChunks'

# This is the commit message #5:

adds a description of nHkl as a comment

# This is the commit message #6:

Update swfiles/+sw_classes/magnetic_structure.m

Provides a brief comment on the 'magnetic_structure' class

Co-authored-by: Duc Le <[email protected]>
mducle added a commit that referenced this issue Apr 1, 2021
@krishnakumarg1984 @mducle
# This is a combination of 6 commits.
7a54d51 
# This is the 1st commit message:

updates the descriptive comments for the biquadratic hamiltonia constructor to be consistent with updated argument names

# This is the commit message #2:

Update swfiles/+sw_classes/biquadratic_hamiltonian.m

Use more descriptive names for the biquadratic hamiltonian constructor

Co-authored-by: Anders Markvardsen <[email protected]>
# This is the commit message #3:

Renames the arguments of the hamiltonian class constructor to better
reflect its meaning

# This is the commit message #4:

Wrote a brief description of the variable 'nChunks'

# This is the commit message #5:

adds a description of nHkl as a comment

# This is the commit message #6:

Update swfiles/+sw_classes/magnetic_structure.m

Provides a brief comment on the 'magnetic_structure' class

Co-authored-by: Duc Le <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@wardsimon wardsimon

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Create vagrant workflow SpinW/spinw4
2 participants
@wardsimon @mducle