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

Actions #58

Merged
merged 11 commits into from
Dec 9, 2020
Merged
Show file tree
Hide file tree
Changes from 5 commits
Commits
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
34 changes: 34 additions & 0 deletions .github/workflows/main.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
# Builds using docker
---
name: Build

on:
push:
pull_request:
schedule:
- cron: '0 0 * * 0'

jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Set up Python ${{ matrix.python }}
uses: actions/setup-python@v2
with:
python-version: ${{ matrix.python }}
- name: Add variable
run: |
run: |
echo "COMPOSE_FILE=docker-compose.yml:volumes.yml" >> $GITHUB_PATH
- name: Set up
run: |
mkdir /tmp/omero-app
cp -r . /tmp/omero-app/.omero
- name: Build
run: |
cd /tmp/omero-app
.omero/compose up -d
.omero/compose down
.omero/persist.sh backup
.omero/persist.sh --restore backup
30 changes: 0 additions & 30 deletions .travis.yml

This file was deleted.

10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,11 @@ OMERO Test Infra
for projects that are built on OMERO.server or OMERO.web.

Any repository that relies on an existing OMERO installation
can depend on this directory whether for testing in travis
can depend on this directory whether for testing in CI system
or locally.

The are a number of [examples](#examples) which are run
regularly by Travis CI.
regularly by CI.

Setup
-----
Expand Down Expand Up @@ -56,7 +56,7 @@ It is also possible to combine several application e.g.
but each of the applications must pass when it is run alone as well.

These commands should be invoked by the `script` step in the project's
.travis.yml file. Set any environment variables as necessary.
.omero_plugin.yml file. Set any environment variables as necessary.
jburel marked this conversation as resolved.
Show resolved Hide resolved

Extension mechanisms
--------------------
Expand Down Expand Up @@ -156,7 +156,7 @@ Run the linter, install, run tests
Remember, you may need to set some environment variables to ensure your plugin
is discovered and tested correctly.

If you are modifying an existing plugin see `.travis.yml` for the required variables.
If you are modifying an existing plugin see `.omero_plugin.yml` for the required variables.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you mean for the file in this repo to be named "omero_plugin.yml" rather than "main.yml"? (Also, don't need the leading dot)


Trouble-shooting
----------------
Expand Down Expand Up @@ -198,5 +198,5 @@ Examples
- https://github.com/ome/scripts

You can find more examples by searching for
"[openmicroscopy/omero-test-infra filename:.travis.yml](https://github.com/search?q=openmicroscopy%2Fomero-test-infra+filename%3A.travis.yml&type=Code)"
"[ome/omero-test-infra filename:.omero_plugin.yml](https://github.com/search?q=openmicroscopy%2Fomero-test-infra+filename%3A.omero_plugin.yml&type=Code)"
jburel marked this conversation as resolved.
Show resolved Hide resolved
on GitHub.com.