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
2. Test the image interactively (type `exit` to exit)
41
41
42
42
```bash
43
-
docker run -it --entrypoint /bin/bash sar-pipeline
43
+
docker run -it --entrypoint /bin/bash sar-pipeline-isce3-rtc
44
44
```
45
45
46
46
1. Set the following minimum environment credentials in a `.env` file. At minimum we require earthdata *OR* Coperniucs Space Data Ecosystem (CDSE) credentials to download from the Alaska Satelite Facility (ASF) or CDSE respectively. These can be created here for the [ASF](http://urs.earthdata.nasa.gov/) and [CDSE](https://dataspace.copernicus.eu/).
@@ -57,13 +57,13 @@ mkdir data
57
57
```
58
58
59
59
```bash
60
-
docker run --env-file .env -v ${PWD}/data:/home/rtc_user/working sar-pipeline \
60
+
docker run --env-file .env -v ${PWD}/data:/home/rtc_user/working sar-pipeline-isce3-rtc \
1. Branch off from main to develop new features for a planned release.
6
6
2. Run the end-to-end tests locally on the branch with proposed changes. Note the local run requires sufficient compute and credentials to be set.
7
7
8
8
```bash
9
-
# test command line tools
10
-
pixi run test-aws-cli
11
-
12
-
# test docker image build and test run
13
-
pixi run test-full-aws-docker-run
9
+
# tests that don't require credentials
10
+
pixi run test-pipeline-no-creds
11
+
# tests to download data from sources. Requires credentials in .env
12
+
pixi run test-scene-data-source-queries
13
+
# full test of isce3 rtc pipeline. Note may take a few hours as the docker image is
14
+
# built and run for a few products. Requires credentials in .env
15
+
pixi run test-isce3-rtc
14
16
```
17
+
15
18
3. If successful raise a PR for review and merge branch into main
16
19
4. Create new release on GitHub and increment the tag:
17
20
- Images prior to an initial release should be of for, `v0.X.X`.
18
21
- Test images should be of form `vX.X.X_betaX`
19
22
- For small changes the tag should be incremented by `0.0.1`. For example, `v1.0.1` -> `v1.0.2`.
20
23
- Major changes should increment the first or second number, depending on the impact of the change.
21
-
5. When the release made, the `push-image-to-ecr.yaml` github action will be run. A new image will be built, tagged and pushed to ECR according to the release tag. E.g. `sar_pipeline:v1.0,1`
24
+
5. The release should trigger the workflow [push-image-to-ecr](../../.github/workflows/push-image-to-ecr.yaml) that will build and push the updated image to the AWS ECR repository.
25
+
6. If the automated build and push fails, manually tag and upload the docker image to the ECR repository:
26
+
27
+
```bash
28
+
# set credentials with write to the ECR repo, or use access tool
0 commit comments