Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change theme and add some more content #1

Merged
merged 25 commits into from
Mar 4, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
5146516
update theme page and add section in README
shahzebsiddiqui Feb 29, 2024
0d42a4c
adding a Features section
shahzebsiddiqui Feb 29, 2024
ab1fc5d
add layout and style sheet and url for slack
shahzebsiddiqui Feb 29, 2024
4a11663
add repository_url
shahzebsiddiqui Mar 1, 2024
7754338
add logo
shahzebsiddiqui Mar 1, 2024
c1bedfc
commit everything for a redesigned home page
shahzebsiddiqui Mar 1, 2024
5b097a0
add image
shahzebsiddiqui Mar 1, 2024
891cc24
add everything
shahzebsiddiqui Mar 4, 2024
f7abc3a
Create CNAME
shahzebsiddiqui Mar 4, 2024
014f093
add CNAME
shahzebsiddiqui Mar 4, 2024
e250ea8
Merge branch 'add_more_stuff_to_main_page' of github.com:buildtesters…
shahzebsiddiqui Mar 4, 2024
a64a8c7
Delete CNAME
shahzebsiddiqui Mar 4, 2024
700996d
Create CNAME
shahzebsiddiqui Mar 4, 2024
f0ebeac
add github workflow
shahzebsiddiqui Mar 4, 2024
b540396
Merge branch 'add_more_stuff_to_main_page' of github.com:buildtesters…
shahzebsiddiqui Mar 4, 2024
52ab72f
run on push
shahzebsiddiqui Mar 4, 2024
f6e7878
debug
shahzebsiddiqui Mar 4, 2024
2f472e6
trying a new github workflow
shahzebsiddiqui Mar 4, 2024
bbf62d3
remove CNAME file
shahzebsiddiqui Mar 4, 2024
9773529
remove github workflow
shahzebsiddiqui Mar 4, 2024
0540e94
add github workflow
shahzebsiddiqui Mar 4, 2024
bf0a300
update readme
shahzebsiddiqui Mar 4, 2024
681f5db
update events to push and workflow_dispatch
shahzebsiddiqui Mar 4, 2024
90bd14c
update workflow
shahzebsiddiqui Mar 4, 2024
7046cf3
add target branch for 'gh-pages'
shahzebsiddiqui Mar 4, 2024
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions .github/workflows/build.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
name: Testing the GitHub Pages publication

on:
push

jobs:
jekyll:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2

# Use GitHub Actions' cache to shorten build times and decrease load on servers
- uses: actions/cache@v2
with:
path: vendor/bundle
key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile') }}
restore-keys: |
${{ runner.os }}-gems-

# Standard usage
- uses: helaili/jekyll-action@v2
with:
token: ${{ secrets.GITHUB_TOKEN }}
target_branch: 'gh-pages'
16 changes: 16 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
*.gem
*.sublime-project
*.sublime-workspace
.bundle
.DS_Store
.jekyll-cache
.jekyll-metadata
.sass-cache
_asset_bundler_cache
_site
codekit-config.json
example/_site
Gemfile.lock
node_modules
npm-debug.log*
vendor/bundle
18 changes: 18 additions & 0 deletions Gemfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
source "https://rubygems.org"

gem "jekyll"
gem "minimal-mistakes-jekyll"

# If you have any plugins, put them here!
group :jekyll_plugins do
gem "jekyll-paginate"
gem "jekyll-sitemap"
gem "jekyll-gist"
gem "jekyll-feed"
gem "jemoji"
gem "jekyll-include-cache"
gem "jekyll-algolia"
gem "jekyll-sass-converter", "~> 2.0"
end

gem "webrick", "~> 1.7"
71 changes: 3 additions & 68 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,73 +1,8 @@
# Buildtest

Welcome to buildtest home page. This page provides documentation on how to use buildtest and how to contribute to the project.
Welcome to buildtest home page. This repository is used to publish buildtest website using GitHub Pages.

## What is buildtest?

buildtest is a HPC testing framework that provides a flexible way to test software stack on HPC systems.
buildtest is designed to be a generic framework that can be used to test any software stack. Test are written
in YAML format called **buildspecs** that is used to describe test configuration. buildtest will translate the
configuration into a valid test script that can be executed on the system.

## Installation

Buildtest requires Python 3.8 or higher. You can [Install Python](https://www.python.org/downloads/) or use
[Anaconda](https://www.anaconda.com/) to manage python installation.

Buildtest is simple to install, just clone the repo and source the setup script. We recommend you create a python
virtual environment. Shown below are the instructions assuming you have cloned the repo in your home directory.

```console
git clone https://github.com/buildtesters/buildtest.git
python3 -m venv $HOME/.pyenv/buildtest
source $HOME/.pyenv/buildtest/bin/activate
source $HOME/buildtest/setup.sh
```

## Features

Buildtest

## Example Test

An example test configuration can be shown below, typically a test will start off with declaration of **buildspecs** followed
by name of test name ``systemd_default_target``. The ``executor`` field is used to specify the executor to use to run the test.
The ``type`` field is used to determine which schema type to use for validating schema. The ``description`` is used to provide
a description of the test. The ``run`` field is used to provide the test script to run. The ``tags`` field is used to classify
so they can be run by a tagname.

```yaml
buildspecs:
systemd_default_target:
executor: generic.local.bash
type: script
tags: [system]
description: check if default target is multi-user.target
run: |
if [ "multi-user.target" == `systemctl get-default` ]; then
echo "multi-user is the default target";
exit 0
fi
echo "multi-user is not the default target";
exit 1
```
## Running Test

The ``buildtest build`` command is used to build test scripts from buildspecs. Typically
one would specify path to file using ``-b`` option which can be used to specify a file or directory path.
The `-b` option can be appended multiple times to specify multiple buildspecs.

```console
buildtest build -b /path/to/buildspecs.yml
buildtest build -b /path/to/directory
buildtest build -b <dir1> -b <dir2> -b <file1>
```

## References

- [buildtest Documentation](https://buildtest.readthedocs.io/en/latest/)
- [buildtest GitHub](https://github.com/buildtesters/buildtest)
- [buildtest Slack](https://buildtesters.slack.com)
- [Join buildtest Slack](https://communityinviter.com/apps/hpcbuildtest/buildtest-slack-invitation)

This site is based on Jekyll multi-page site
using the awesome [minimal-mistakes](https://mmistakes.github.io/minimal-mistakes/).

Loading
Loading