Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
A
argopkgs
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
argo
argopkgs
Commits
3ea8bc88
Commit
3ea8bc88
authored
Sep 26, 2019
by
Valentin Reis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Readme update
parent
f8827aa9
Pipeline
#8570
passed with stages
in 56 minutes and 29 seconds
Changes
1
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
30 additions
and
9 deletions
+30
-9
README.md
README.md
+30
-9
No files found.
README.md
View file @
3ea8bc88
...
...
@@ -24,15 +24,34 @@ rolling dependency for continuous integration.
get nix through your package manager or
`curl https://nixos.org/nix/install |
sh`
## usage
## usage
(reccomended)
talk to @vreis, or
talk to @vreis, or
:
use
`argopkgs`
as a channel:
```
$ git clone git@xgitlab.cels.anl.gov:argo/argopkgs.git
```
That local clone can be used to build components:
```
$ nix-build /path/to/argopkgs -A <packagename>
```
And install packages:
```
$ nix-env -f /path/to/argopkgs -iA <packagename>
```
It's reccomended you read
`pkgs/default.nix`
for a list of available packages.
## usage (old way - use as a channel)
You can also use
`argopkgs`
as a channel. It's not reccomended, because usage of
`nix-env -i <packagename>`
evaluates
all derivations to get their
`name`
attribute - which in the case of argopkgs involves cloning a few repositories.
```
nix-channel --add https://xgitlab.cels.anl.gov/argo/argopkgs/-/archive/master/argopkgs-master.tar.gz argopkgs
nix-channel --update argopkgs
$
nix-channel --add https://xgitlab.cels.anl.gov/argo/argopkgs/-/archive/master/argopkgs-master.tar.gz argopkgs
$
nix-channel --update argopkgs
```
which lets you install packages:
...
...
@@ -55,7 +74,7 @@ $ nix-shell ~/.nix-defexpr/channels/argopkgs -A candle
if your key is already on the runners, you can redeploy them with:
```
$ g clone git@xgitlab.cels.anl.gov:argo/argopkgs.git
$ g
it
clone git@xgitlab.cels.anl.gov:argo/argopkgs.git
$ cd argopkgs/deployments
$ nix-shell
[nix-shell]$ ./deploy-runners.sh
...
...
@@ -63,7 +82,7 @@ $ nix-shell
or reboot/restart their gitlab-runner daemon with:
```
$ g clone git@xgitlab.cels.anl.gov:argo/argopkgs.git
$ g
it
clone git@xgitlab.cels.anl.gov:argo/argopkgs.git
$ cd argopkgs/deployments
$ ./restart-runners.sh
$ ./reboot-runners.sh
...
...
@@ -75,8 +94,10 @@ these are deployed via NixOps:
-
defined in file
[
deployments/ci.nix
](
deployments/ci.nix
)
-
deployment state is in
`deployments/argo.nixops`
.
-
there are four shell scripts in
[
deployments/
](
deployments/
)
that can be used to redeploy, reboot, and restart systemd services.
-
access is granted to all keys in
[
deployment/keys
](
deployment/keys
)
so submit a pull request and ask someone to redeploy if you need access.
-
there are four shell scripts in
[
deployments/
](
deployments/
)
that can be used
to redeploy, reboot, and restart systemd services.
-
access is granted to all keys in
[
deployment/keys
](
deployment/keys
)
so submit
a pull request and ask someone to redeploy if you need access.
The gitlab-runner service is called "gitlabrunner" on the machines. That
systemd service registers runners on ExecStart and unregisters them on
...
...
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