Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
10
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
Open sidebar
Nektar
Nektar
Commits
146a4111
Commit
146a4111
authored
Feb 26, 2016
by
Dave Moxey
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix missing buildbot info
parent
6ec10e89
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
0 deletions
+10
-0
CONTRIBUTING.md
CONTRIBUTING.md
+10
-0
No files found.
CONTRIBUTING.md
View file @
146a4111
...
...
@@ -62,6 +62,16 @@ You should also test your branch on the
the code against a number of Linux, Mac and Windows operating systems, both 32-
and 64-bit. If your tests don't pass, we can't merge the code into master.
Testing is presently manually executed. You should:
1.
Go to the buildbot site and navigate to the
*Builders*
page.
2.
Scroll to the bottom of the page in the section
*Force all builds*
3.
Enter your details. If you're working on a fork, then the
*
Suffix to repo
url
*
box should be changed to
`username/nektar`
.
4.
Hit the
*Force build*
button.
5.
Check the output in the
*Grid*
page -- hopefully everything should be green!
Tests can take up to two hours to run.
## Documentation
Nektar++ has a fairly comprehensive user guide and a developer guide that is
presently very incomplete. The following are rough guidelines for what you
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment