container-builder merge requestshttps://code.ornl.gov/olcf/container-builder/-/merge_requests2018-09-12T20:08:16Zhttps://code.ornl.gov/olcf/container-builder/-/merge_requests/26checkout singularity by release tag; update to v2.6.02018-09-12T20:08:16ZCarlyle, Adamcheckout singularity by release tag; update to v2.6.0https://code.ornl.gov/olcf/container-builder/-/merge_requests/25Provisioning Updates for Singularity 2.52018-05-10T01:54:50ZCarlyle, AdamProvisioning Updates for Singularity 2.5- Provision script needs `libarchive-dev` package for Singularity 2.5
- Ability for CI to deploy only OpenStack VMs (i.e. prevent CLI installations)- Provision script needs `libarchive-dev` package for Singularity 2.5
- Ability for CI to deploy only OpenStack VMs (i.e. prevent CLI installations)https://code.ornl.gov/olcf/container-builder/-/merge_requests/24Updates Singularity version to 2.5.02018-05-09T13:33:08ZMorrison, JackUpdates Singularity version to 2.5.0This MR will help bring the Builder version of Singularity in line with that of Chester.This MR will help bring the Builder version of Singularity in line with that of Chester.https://code.ornl.gov/olcf/container-builder/-/merge_requests/23Cleans Spack build area of failed build remnants.2018-01-31T15:53:42ZBelhorn, Mattbelhornmp@ornl.govCleans Spack build area of failed build remnants.Spack builds that fail can sometimes leave staged source files and CMake
caches in the build area. These are cleaned up when builds are
successful, but are left around when builds fail to allow for
post-mortem analysis of the build error...Spack builds that fail can sometimes leave staged source files and CMake
caches in the build area. These are cleaned up when builds are
successful, but are left around when builds fail to allow for
post-mortem analysis of the build errors.
There is a small possibility that new builds will have the same unique
hash as previous builds, even if details of the build have changed. In
this case, old source and CMake caches from the previous faild build
attempt may be re-used for the new build. This is almost always
undesired.
We can just go ahead and clean the spack build staging directory of any
cruft prior to attempting a new build to avoid this, while also keeping
these staged artifacts after build failures for study.
Latest versions of spack can clean the staging directory with the
command:
```
spack clean --stage --misc-cache
```
but older versions used the command:
```
spack purge --stage --misc-cache
```
in case this error re-appears when using older Spack v0.10 or earlier.
This commit also adds annotation to the deployment scripts explaining
the purpose of each of the spack setup and build steps.https://code.ornl.gov/olcf/container-builder/-/merge_requests/22Callback hell2018-01-06T02:25:36ZSimpson, Adam BCallback hellRemove coroutines as the support didn't seem great :*(Remove coroutines as the support didn't seem great :*(https://code.ornl.gov/olcf/container-builder/-/merge_requests/21Websockets2017-12-28T21:22:16ZSimpson, Adam BWebsocketsUse new boost beast websocketsUse new boost beast websocketshttps://code.ornl.gov/olcf/container-builder/-/merge_requests/20Pin to a version of Spack that is known to work2017-12-18T20:21:42ZFrench, RobertPin to a version of Spack that is known to workhttps://code.ornl.gov/olcf/container-builder/-/merge_requests/19Use coroutine2017-12-11T21:09:41ZFrench, RobertUse coroutinehttps://code.ornl.gov/olcf/container-builder/-/merge_requests/18Key is called 'ContainerBuilderKey'2017-12-08T17:02:13ZFrench, RobertKey is called 'ContainerBuilderKey'https://code.ornl.gov/olcf/container-builder/-/merge_requests/16Do not clobber unrelated VMs when tearing down queue. Fixes #152017-12-04T15:02:04ZFrench, RobertDo not clobber unrelated VMs when tearing down queue. Fixes #15Attempt to fix #15 Attempt to fix #15 https://code.ornl.gov/olcf/container-builder/-/merge_requests/14Move spack package to repo; setup tests2017-12-04T15:01:26ZFrench, RobertMove spack package to repo; setup testsSet up the spack package as a repo that can be added to an existing spack instance. Add a single test to make sure this repo can be added to a spack instance and that ContainerBuilder can be built correctly.Set up the spack package as a repo that can be added to an existing spack instance. Add a single test to make sure this repo can be added to a spack instance and that ContainerBuilder can be built correctly.https://code.ornl.gov/olcf/container-builder/-/merge_requests/12Ignore creds and build artifacts2017-12-04T15:01:14ZFrench, RobertIgnore creds and build artifactsKeeps openrc.sh and container keys from accidentally being tracked in version controlKeeps openrc.sh and container keys from accidentally being tracked in version controlhttps://code.ornl.gov/olcf/container-builder/-/merge_requests/17Use CMAKE_INSTALL_PREFIX. Fixes #102017-12-04T15:00:46ZFrench, RobertUse CMAKE_INSTALL_PREFIX. Fixes #10Per the docs, this mafaka got two L's:
https://cmake.org/cmake/help/v3.0/variable/CMAKE_INSTALL_PREFIX.htmlPer the docs, this mafaka got two L's:
https://cmake.org/cmake/help/v3.0/variable/CMAKE_INSTALL_PREFIX.html