You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Consider using larger runners or machines with greater resources for possible analysis time improvements.
14
+
CodeQL-Scanning:
15
+
30
16
runs-on: ubuntu-latest
31
-
timeout-minutes: 360
17
+
32
18
permissions:
33
-
# required for all workflows
19
+
contents: read
34
20
security-events: write
21
+
pull-requests: read
35
22
36
-
# required to fetch internal or private CodeQL packs
37
-
packages: read
38
-
39
-
strategy:
40
-
fail-fast: false
41
-
matrix:
42
-
include:
43
-
- language: go
44
-
build-mode: autobuild
45
-
# CodeQL supports the following values keywords for 'language': 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift'
46
-
# Use `c-cpp` to analyze code written in C, C++ or both
47
-
# Use 'java-kotlin' to analyze code written in Java, Kotlin or both
48
-
# Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
49
-
# To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
50
-
# see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
51
-
# If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
52
-
# your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
# If you wish to specify custom queries, you can do so here or in a config file.
64
-
# By default, queries listed here will override any specified in a config file.
65
-
# Prefix the list here with "+" to use these queries and those in the config file.
66
-
67
-
# For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
68
-
# queries: security-extended,security-and-quality
69
-
70
-
# If the analyze step fails for one of the languages you are analyzing with
71
-
# "We were unable to automatically build your code", modify the matrix above
72
-
# to set the build mode to "manual" for that language. Then modify this step
73
-
# to build your code.
74
-
# ℹ️ Command-line programs to run using the OS shell.
75
-
# 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
76
-
- name: Autobuild
77
-
uses: github/codeql-action/autobuild@v3
78
-
# - if: matrix.build-mode == 'manual'
79
-
# shell: bash
80
-
# run: |
81
-
# echo 'If you are using a "manual" build mode for one or more of the' \
82
-
# 'languages you are analyzing, replace this with the commands to build' \
Copy file name to clipboardExpand all lines: README.md
+9Lines changed: 9 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -143,6 +143,15 @@ Links to specific sections are provided below.
143
143
144
144
If you see any issues in documentation please create an issue or PR [here](https://github.com/Layr-Labs/eigenlayer-docs)
145
145
146
+
## Integration Testing
147
+
Integration testing uses Anvil to generate a reproducible state for the network to be tested against.
148
+
149
+
### Forge & Anvil
150
+
The CLI package leverages tooling from the [eigensdk-go](https://github.com/Layr-Labs/eigensdk-go) to run [Forge](https://github.com/foundry-rs/foundry/tree/master/crates/forge) tests against an [Anvil](https://github.com/foundry-rs/foundry/tree/master/crates/anvil) server based on a predefined network state.
151
+
This allows the tests to run against a reproducible environment. See the [Run anvil chain](https://github.com/Layr-Labs/eigenlayer-cli/blob/master/.github/workflows/integration-test.yml#L28-L30)
152
+
step in the integration test workflow. See the [eigensdk-go README.md - Anvil](https://github.com/Layr-Labs/eigensdk-go/blob/dev/README.md)
153
+
for further discussion on how this environment state is generated and stored.
154
+
146
155
## Release Process
147
156
To release a new version of the CLI, follow the steps below:
148
157
> Note: You need to have write permission to this repo to release new version
0 commit comments