♻️ 💅 Cleanup/polish the code to automatically cascade images from the server -> server dependencies #1082

shankari · 2024-08-12T21:39:50Z

MukuFlash03 · 2024-09-20T18:23:53Z

MukuFlash03 · 2024-09-20T18:29:07Z

The order I plan to work on these:
DONE - A. CI/CD: 7, 6, 2, 8, 5, 4, 3, 1
B. Core: 2, 1
C. Core + CI/CD: 1, 2

Tasks A: CI/CD - Completed [10/08]

First round of changes (comment): A-2, 6, 7, 8
Second round of changes (comment): A- 4, 5
Third round of changes (comment): A- 4, 5

MukuFlash03 · 2024-09-20T18:39:09Z

Task A-7: Certificates location - External or Internal?

Fixed as a part of the redesign changes itself.

Added certificates externally only in server repo (commit)
Only need them in images that need to connect to the AWS Document DB (comment)

Dashboard repos are based on server image so they will have certificates.
Node.js based images do not need them.

Since the same base server image is used by the server image dependent containers (webapp, analysis, admin-dash, public-dash-notebook), we have added it right at the source image which is the external server image. This way it is ensured that the certificates are present in all the cascading images.

Based on comment below, added them to internal and removed from external.

shankari · 2024-09-20T18:46:14Z

@MukuFlash03 right we have implemented this. But I am suggesting that we revisit that decision

Discuss where to put in the cert configuration. We originally had it in the internal repos, then we moved it to the external repos. But now that we have one internal dockerfile per external dockerfile, maybe we can have it be internal after all. It doesn't actually hurt anything to be external, but it is unnecessary in the external repo.

MukuFlash03 · 2024-09-20T18:50:38Z

Task A-6: Switching from $GITHUB_ENV to step outputs using GITHUB_OUTPUT

Shankari's comments

Consider switching from $GITHUB_ENV to step outputs. I think that the step outputs are the recommended approach to pass values from one step to another, but we should verify

I couldn’t find any official statement on which is the recommended approach.
But I did see this warning that says “set-output” is deprecated, switch to using environment files

Note that this doesn’t say that “steps.output” is deprecated; it says “set-output” is deprecated.
So, step outputs are still valid and we essentially have to choose between: GITHUB_ENV and GITHUB_OUTPUT

One argument in favor of GITHUB_OUTPUT is this:

This comment mentions that Environment variables are only available in the same job.
Right now we do have just one job in the dashboard build workflows.
GITHUB_OUTPUT documentation mentions that job outputs available to all dependent downstream jobs.
But in the future if we have more jobs, then GITHUB_OUTPUT could be more suited.

MukuFlash03 · 2024-09-20T20:37:50Z

Task A-2: Avoid uploading date as Artifacts -> Use .env file instead?

Shankari's comments

Explore whether we can stop uploading the date of of the run as an artifact since we are using an .env file in the dashboards. Can't this just be an output of the run?

REST API endpoints

I looked at some REST API endpoints to see if we can access outputs of jobs/steps in a run outside of the workflow run.
We can then use them directly in the internal script to pull all tags.

Not Suitable

Get a workflow run
I did not find an API endpoint to directly reference outputs inside in a job.
This endpoint gets details about a workflow run but does not have info on outputs.
List jobs for a workflow run
This lists all jobs and steps but it only lists their completion status, time of execution and not outputs or any details.
Download workflow run logs
I did however find an API endpoint that allows downloading workflow run logs.
This does give the outputs but it also gives everything from the logs as seen in the UI.
This is a lot of redundant information that we will need to parse to only fetch the outputs.
It downloads logs a zip file which would again be another hassle to: download -> extract -> read / parse -> clean up files.

Optimal Approach

Get repository content
This endpoint allows to directly read contents of a file, in our case .env files containing tags.
For instance, this API response is from my forked repo where I've stored the tags in a .env file.
The API response has the file content in base64 encoded format:

...
 "download_url": "https://raw.githubusercontent.com/MukuFlash03/em-public-dashboard/cleanup-cicd/.env",
  "type": "file",
  "content": "Tk9URUJPT0tfSU1BR0VfVEFHPTIwMjQtMDktMjAtLTEzLTM2CkZST05URU5E\nX0lNQUdFX1RBRz0yMDI0LTA5LTIwLS0wNC0zOApTRVJWRVJfSU1BR0VfVEFH\nPTIwMjQtMDktMjAtLTA5LTEwCg==\n",
...

Decoding this base64 data (for decoding, the newline characters '\n\ need to be removed and combine the entire encoded string)

NOTEBOOK_IMAGE_TAG=2024-09-20--13-36
FRONTEND_IMAGE_TAG=2024-09-20--04-38
SERVER_IMAGE_TAG=2024-09-20--09-10

MukuFlash03 · 2024-09-20T21:05:00Z

Task A-2: Avoid uploading date as Artifacts -> Use .env file instead? [Contd.]

With the API endpoint mentioned above, we can directly read contents of files.

Proposed Approach

To have a separate .env file in each of the repositories: server, join-page, admin-dash, public-dash.
This file would contain the image tags of the latest uploaded images.
Server image tag is needed in the dashboard repos' .env files since the Dockerfiles use the server tag as an ARG

In server repo: SERVER_IMAGE_TAG
In join-page repo: JOIN_IMAGE_TAG
In admin-dash repo: ADMIN_DASH_IMAGE_TAG, SERVER_IMAGE_TAG
In public-dash: PUBLIC_DASH_NOTEBOOK_IMAGE_TAG, PUBLIC_DASH_FRONTEND_IMAGE_TAG, SERVER_IMAGE_TAG

Pros of this approach:

Greatly reduces code in internal script to pull tags
- We don't have to fetch latest workflow runs as we can simply read the file contents of a file available in a public repository.
Need only one file .env in each repo that can store all image tags relevant to the repository.
- Currently in public-dash we have two .env files (.env for server tag, .env.repoTags for frontend tag).
Will not need to keep track of Server image tag in the dependent dashboard repos since we will be reading the SERVER_IMAGE_TAG from the .env file in server repo directly.
- Can use this API endpoint in the dashboard workflows as well as internal script.
- This would mean we would no longer have to check the separate PUSH and WORKFLOW_DISPATCH events related to server tag. For public-dash, still need the checks as frontend tag depends on event type.

shankari · 2024-09-21T02:56:05Z

why use something complicated which retrieves the file as a base64 encoded string instead of just reading the files directly using the raw option?

MukuFlash03 · 2024-09-21T03:10:31Z

why use something complicated which retrieves the file as a base64 encoded string instead of just reading the files directly using the raw option?

I just thought of sticking to using Github REST API and was looking for options within that.

But reading the raw contents as text is a much simpler option indeed.
It also does not require any headers, authorization token for the request which is valid since it is publicly available data anyways.
Will switch out the URLs and remove the base64 code.
Thank you for pointing that out!

Refer to details in cleanup issue: Task A-6: e-mission/e-mission-docs#1082 (comment)

Refer to details in cleanup issue: Task A-2: e-mission/e-mission-docs#1082 (comment) Added .env file initialized with the current latest tag of admin-dash and server image. Internal script can read docker image tags directly from .env.tags using curl to fetch raw file contents. Storing server tag as well since admin-dash Dockerfile uses it. Removed workflow dispatch inputs No longer need inputs since reading from .env.tags in server repo directly ------ Read raw file contents directly instead of using REST API REST API endpoint returns base64 encoded data which then needs to be decoded. Can simply read the Raw file contents from the publicly available file. ------ Also changed tag name to match tag name in internal repository This way we can directly use the tag name without having extra fields like envVar in the internal script. ----- For now not removing artifacts until the internal script is updated to handle this change.

…ternal Task A-8: Prefixing branch name to the docker tag along with the date. In the internal script we will not need to maintain the different branch lists as the images will be completely tagged in the external workflows themselves. We can simply use the tags without modifications then. For now, not prefixing the tag to the artifact since we will be removing the artifact anyways. And current internal script works with artifacts. Once I update the internal script, will come back and remove artifacts. Also removing prefixed branch name from frontend image artifact in case of workflow dispatch event since it uses the existing frontend image tag generated during push event which already has prefixed branch name In Dockerfile, removing hardcoded branch name, since in this change, we are already included the branch name in image tag. ---------- Task A-7: Certifcates added to internal Dockerfiles. Refer to issue comment for details: Task A-7: e-mission/e-mission-docs#1082 (comment) The certificates are relevant to our internal AWS configuration and not needed externally. They can be present externally too without having any major effect. But removing them helps keeping the base image clean. Additionally, anyone working with the code can customize with their own certificates if needed or adopt an approach which doesn't even need certificates in the first place.

Refer to details in cleanup issue: Task A-6: e-mission/e-mission-docs#1082 (comment)

Refer to details in cleanup issue: Task A-2: e-mission/e-mission-docs#1082 (comment) Storing latest tag as well so that artifacts are not needed. For now not removing artifacts until the internal script is updated to handle this change. ---- Task A-8: Prefixing branch name to the docker tag along with the date. In the internal script we will not need to maintain the different branch lists as the images will be completely tagged in the external workflows themselves. We can simply use the tags without modifications then. For now, not prefixing the tag to the artifact since we will be removing the artifact anyways. And current internal script works with artifacts. Once I update the internal script, will come back and remove artifacts.

Refer to details in cleanup issue: Task A-6: e-mission/e-mission-docs#1082 (comment)

Refer to details in cleanup issue: Task A-2: e-mission/e-mission-docs#1082 (comment) Added .env file initialized with the current latest tag of admin-dash and server image. Internal script can read docker image tags directly from .env.tags using curl to fetch raw file contents. Storing server tag as well since admin-dash Dockerfile uses it. Removed workflow dispatch inputs No longer need inputs since reading from .env.tags in server repo directly ------ Read raw file contents directly instead of using REST API REST API endpoint returns base64 encoded data which then needs to be decoded. Can simply read the Raw file contents from the publicly available file. ----- For now not removing artifacts until the internal script is updated to handle this change.

…ternal Task A-8: Prefixing branch name to the docker tag along with the date. In the internal script we will not need to maintain the different branch lists as the images will be completely tagged in the external workflows themselves. We can simply use the tags without modifications then. For now, not prefixing the tag to the artifact since we will be removing the artifact anyways. And current internal script works with artifacts. Once I update the internal script, will come back and remove artifacts. In Dockerfile, removing hardcoded branch name, since in this change, we are already included the branch name in image tag. ---------- Task A-7: Certifcates added to internal Dockerfiles. Refer to issue comment for details: Task A-7: e-mission/e-mission-docs#1082 (comment) The certificates are relevant to our internal AWS configuration and not needed externally. They can be present externally too without having any major effect. But removing them helps keeping the base image clean. Additionally, anyone working with the code can customize with their own certificates if needed or adopt an approach which doesn't even need certificates in the first place.

Refer to details in cleanup issue: Task A-6: e-mission/e-mission-docs#1082 (comment)

Refer to details in cleanup issue: Task A-2: e-mission/e-mission-docs#1082 (comment) Storing server tag as well so that artifacts are not needed. Can also remove image tag passed as input in Workflow dispatch POST request. Workflow input also removed in dashboard workflows For now not removing artifacts until the internal script is updated to handle this change. ---- Task A-8: Prefixing branch name to the docker tag along with the date. In the internal script we will not need to maintain the different branch lists as the images will be completely tagged in the external workflows themselves. We can simply use the tags without modifications then. For now, not prefixing the tag to the artifact since we will be removing the artifact anyways. And current internal script works with artifacts. Once I update the internal script, will come back and remove artifacts.

…ally Refer to issue comment for details: Task A-7: e-mission/e-mission-docs#1082 (comment) The certificates are relevant to our internal AWS configuration and not needed externally. They can be present externally too without having any major effect. But removing them helps keeping the base image clean. Additionally, anyone working with the code can customize with their own certificates if needed or adopt an approach which doesn't even need certificates in the first place.

MukuFlash03 · 2024-09-23T22:36:49Z

Task A-8: Stored tag format changed to branch_name-timestamp

Currently the docker images are tagged as <branch_name>_ but the artifact tags only had the timestamp.
The branch names are hardcoded in the internal scripts and are prefixed to the retrieved timestamps.

However, this causes a problem if the docker image upload is done from a different branch in the external GitHub workflow, since the complete returned tag in the internal script would still have the default hardcoded branch_name but latest timestamp.

Hence now storing the same tag that the docker image is tagged with including both the branch_name and timestamp.

MukuFlash03 · 2024-09-23T23:36:19Z

All PRs tracker (comment)

First set of cleanup PRs added for Tasks A-2, 6, 7, 8.

PRs: e-mission-server, join-page, admin-dash, public-dash

MukuFlash03 · 2024-09-30T00:29:14Z

Task A-5: Reusable workflows for unifying workflows to reduce duplicated code

Shankari's comments

we currently have two copies of the cascading code (in the two dashboard repos). We should explore unifying them. Maybe nested workflows?

Initially, I thought that only the dashboard workflows would be affected. But after the first round of changes for this cleanup issue, the join repo workflow is also almost identical to the dashboard repo workflows.

Reusable workflows are the perfect way to achieve DRY.
It essentially works like a function call in normal programming.
I'm storing the reusable workflow in the e-mission-server repo.

I have added conditional checks that check for the repo name in the reusable workflow file that determine which statements to execute depending on for which repo the workflow is running.

This is used for both push events specific to a repo as well as for the workflow dispatch events triggered on pushes to server repo.

Advantages of reusable workflows:

No repeated code the image build process. All the other repos (join, admin-dash, public-dash) reuse the same workflow file.
For any future changes related to GitHub actions workflow file, will no longer need to have 3 additional PRs for each repo (join, admin-dash, public-dash). Can simply modify the reusable workflow file as this is the core “function” workflow that is being called.

Testing done
Workflow runs: Server, Join, Admin-dash, Public-dash

MukuFlash03 · 2024-09-30T00:36:16Z

Highlighting some problems faced while implementing and approaches to resolve them:

1. git push failing in Github Actions workflow file

Default GitHub Token is used if no token specified in actions/checkout (documentation)
But then the "git push" command was failing as it was unable to access files in other repos. This was because the reusable workflow is located in the server repo but it was trying to make changes to contents of other repos.
And the default GITHUB_TOKEN is scoped to the current repository, hence it does not authorize this.

Hence, I passed in the existing fine-grained token while checking out:

      - name: Checkout repository
        uses: actions/checkout@v4
        with:
          repository: e-mission/${{ inputs.repo }}
          ref: ${{ inputs.branch }}
          token: ${{ secrets.GH_FG_PAT_TAGS }}

2. After solving the above problem, adding fine-grained token resulted in infinite workflow runs

So we have the initial trigger which is either a normal commit / push OR triggered via workflow dispatch by the server.
Now, infinite workflow calls result because the "git push" in the workflow file to update the .env file is also in fact a push event and this triggers yet another workflow, which in turn triggers another workflow and runs infinitely.

    - name: Add, Commit, Push changes to .env file
      run: |
        git config --local user.email "[email protected]"
        git config --local user.name "Github Actions bot to update .env with latest tags"
        if git diff --quiet; then
          echo "Latest timestamp already present in .env file, no changes to commit"
        else
          git add .env
          git commit -m "Updated docker image tag in .env file to the latest timestamp"
          git push origin 
        fi

Now, the question I asked myself was - why isn't this happening in the current codebase where the exact same workflow file was there? We haven't seen infinite workflow runs due to the commits by GitHub actions to update the .env files.

The answer is that currently, in the dashboard workflows that update the .env file, we are using the default GITHUB_TOKEN which has a built-in mechanism to avoid recursive workflow calls documentation.
Confirmed from another developer on stackoverflow (link).

Dilemma

Now, due to Problem 1, we need to use fine-grained token with access to write to other repos.
But due to Problem 2, default GITHUB_TOKEN is needed to avoid infinite workflow runs.

Resolution

1. Authorize git push from another repo's workflow using fine-grained token with additional permission

Can still use Fine-grained token with permission to update repository contents set as Read and Write.
These are the permissions for the current fine-grained token in use as noted by Shankari (comment).
Need to add the Contents: Write permission as well (documentation)

The reason we did not need it currently is because the "git push" to update the .env file is in a workflow file that is in the same repository as the .env file for the dashboard repos.
But with the reusable workflow, the workflow is in the server repository while it attempts to update the .env files in the dashboard repositories.

2. Prevent infinite workflow runs by checking for latest commit message details

In the reusable workflow, these are the git user details used:

      - name: Add, Commit, Push changes to .env file
        run: |
          git config --local user.email "[email protected]"
          git config --local user.name "Github Actions bot to update .env with latest tags"

In the caller workflows in the join repository and the dashboard repositories, I am now checking for the username:

jobs:
  build:  
    if: ${{ !contains(github.event.head_commit.author.name, 'Github Actions bot to update .env with latest tags') }}
    uses: e-mission/e-mission-server/.github/workflows/reusable_image_build_push.yml@master

How the process would look now:

So, for a normal push or workflow dispatch, the commit would be made by a developer.
The workflow would run for this commit as it currently does.
Now, this also triggers another workflow due to the push event to update the .env file.
However with the check in place, it prevents the workflow from running if the last commit was the automated commit with the predefined username.

MukuFlash03 · 2024-09-30T01:31:19Z

Task A-4: Run image_build_push only after tests pass successfully

Approach:

Convert test-with-docker and test-with-manual-install to reusable workflows.
Add them as jobs in image_build_push workflow.
Build job in this workflow needs these test jobs as dependencies assuring that image build occurs after test jobs are successful.

Test Workflow runs

End to end run with tests, server build, dispatch: server, join, admin-dash, public-dash
Both tests success (run)
Docker success, Manual install failure (run)
Docker failure, Manual install success (run)

Details

Github actions didn't have out of the box solution for running a workflow based on results of multiple workflows where ALL workflows must have completed successfully.
We need this since both the test-with-docker and test-with-manual-install must pass.
So this needs an AND logic.

workflow_run is there but this triggers the dependent workflow when either of the workflow dependencies defined as prerequisites are completed.
So this has an OR logic.

Found an alternative suggestion here.
This suggests converting the pre-requisite workflows into reusable workflows.

These workflows can then be called in jobs in the workflow that needs these workflows to be run before.
Finally, these jobs can be added as dependencies for the image build job.

jobs:
  test-with-docker:
    uses: e-mission/e-mission-server/.github/workflows/test-with-docker.yml@master

  test-with-manual-install:
    uses: e-mission/e-mission-server/.github/workflows/test-with-manual-install.yml@master

  build:
    runs-on: ubuntu-latest
    needs: [test-with-docker, test-with-manual-install]

Also, removed the push trigger from the two test workflows since the image_build_push workflow would also be triggered on a push event which in its workflow triggers these two test workflows.
Thus if not removed, each test workflow would run twice.

MukuFlash03 · 2024-09-30T01:51:34Z

All PRs tracker (comment)

Second set of cleanup PRs added for Tasks A-4, 5.

PRs: e-mission-server, join-page, admin-dash, public-dash

MukuFlash03 · 2024-10-08T19:48:55Z

Task A-1: Switch to storing images in GHCR

This was a fairly easy switch following the documentation.

Will need to check the following once the first image is deployed to GHCR:

Documentation says that default visibility for GHCR packages is private on first time push.
If so, then for each repository, will need to go to Packages -> Package Settings -> Change Visibility (at the bottom).

1. Changes to Dockerfile

Needed to add LABEL layer to ensure that the docker image is connected to the correct repository.
For dashboard images that are dependent on the server image, changed to pull from GHCR.

2. Workflow file

Login action used to login to GHCR.
Building, Renaming, Pushing images with GHCR tag.
Appropriate version tag names used depending on whether trigger event was release or workflow_dispatch.

MukuFlash03 · 2024-10-08T19:53:26Z

Task A-3: Image build/push on release instead of on every push

This was a sort of complex change since I had to handle the two different event triggers (workflow_dispatch, release) and how the version tags would need to be updated separately for each of these event types.

Converting the main image_build_push workflow to a reusable workflow was a great idea as it saved a lot of time. Else, I would have to repeat the same code and steps and checks for all the repositories.

Sample Runs passed: server, join, admin-dash, public-dash

Run: Retriggered through UI for creating frontend package

The major changes as a part of this task:

1. Re-building on releases instead of tags

Earlier I had set the trigger event as tags but this would mean any time we create a new tag the workflow would be triggered.
Instead, we are actually creating releases and not tags through the UI.
Hence changed the trigger event to releases, specifically “published” releases.

2. Both Tests and Build will happen for push events

Tests: We need tests to confirm everything works before merging.
Build: Similarly, even though tests might pass, the image build could fail due to issues in Dockerfile or any files used in Dockerfile.
If not building on push:branch event, even though image won’t be pushed to dockerhub / Ghcr since build failed; but we would still have created a new release in GitHub that contains code that would lead to a failed build.
Hence to ensure that the final image that is pushed is correctly built, and we can have a correct version released, running both tests and build for push events.

3. Dispatch only runs on releases identified by ref_type == tag.

Dispatch job depends on build job and since we now have build job running for both push and release events, dispatch job would also run for both.
Hence restricting dispatch to run only on release events by using the ref_type check which has the value tag for releases and branch for pushes on any branch.

4. Additional version increment steps + Creating incremented version tags and releases in workflow

Creating release (documentation)
Creating tags (Video was helpful in understanding SemVer, Git tags)

Manually creating new release through UI would trigger the workflows for all the repos and the new tag would be updated to the tag version set in the UI. This would be updated in the .env files as well.
But for the workflow_dispatch as well, we need to handle creating a new tag and release for the dependent cascading images in the dashboard repositories.
For this, I’m fetching the latest and 2nd latest server releases and checking for the type of SemVer release (major/minor/patch). Based on the type, similar version increment would occur for the dependent images.
Depending on the event type (release / workflow_dispatch), either the tag created through the UI or the incremented tag version would be chosen as the new tag, respectively for each of the two trigger event types.
This new tag is also written to the .env file.
Finally, a new release is created based on this newly created tag in the workflow.

MukuFlash03 · 2024-10-08T22:55:26Z

Listing reasoning behind certain approaches taken

Fetching latest and 2nd latest server tags

Earlier had decided to read raw .env files contents directly but this would only give the current server tag.
Server latest and 2nd latest tags are needed to find whether update was major/minor/patch.
Hence switched to using different REST API endpoint.

Latest release: documentation, link
List all tags: documentation, link
List all releases: documentation, link

Of these, "list all releases" is the correct one for this use case as we want to fetch the releases and not tags.
Depending on the type of server version upgrade, similar version upgrade made to dependent repositories.

Added more event_name checks for push release and workflow_dispatch for updating tags with either

Latest tag via UI generated on push:tags release events, or,
Bumped up tag on workflow_dispatch event via server’s push:tags release event.

Approaches used for fetching sorted server tags

A. Using git describe - NOT USING

Using simpler way to get latest and 2nd latest tag
GitHub discussions post
Points to stack overflow post

Latest tag: 
$ git describe --abbrev=0 --tags
- Fetches tags only from current branch, which is good.

2nd latest tag: 
$ git describe --abbrev=0 --tags --exclude="$(git describe --abbrev=0 --tags)"
- Fetches tags only from current branch, which is good.

$ git describe --abbrev=0 --tags `git rev-list --tags --skip=1 --max-count=1`
- Fetches tags across all branches; we should limit only to current branch.

Might need to specify fetch-depth: 0 for actions/checkout to ensure all commits history is fetched.

Run failed; will added fetch-depth and check again.
Run failed again after adding improved “git describe”; need to add fetch-depth it seems.

Reasons for not using this

The git describe commands work only for current repo.
They fetched latest tags for join, dashboard repos and set them as server tag.
Now for dashboard repos when docker build / compose is run, it couldn’t find the server image tag.
So instead of fetching tags for current repo, we need to fetch for server repo in the cascading workflows.

MukuFlash03 · 2024-10-08T22:58:55Z

B. Using GitHub REST API endpoints

Discussions / Posts: Git tags sort discussion, Github issues

As discussed in this comment, using the list of all releases API endpoint.

Need jq since we want to fetch specific .ref key from json response.

Also need to handle the fact that response contains an array.
Stackoverflow post, post
This solution works for arrays

$ jq -r '.[].username'

Sorting tags: Blog post, Stackoverflow post

$ git tag -l : Does an alphabetical sort. 0.2.11 will be before 0.2.2
$ git tag --sort=version:refname : Solves this problem by arranging them in correct numeric order. However this gets the tags from all branches.
$ git tag -l | sort -V --reverse : Sorts in reverse order.

These commands work in current repo however, whereas we want to sort the tags received from curl response from the server release tags.

tail and head commands can be used (post, post)

So for our case would look like:

tags=$(echo "$response" | jq -r '.[].tag_name')
current_server_release_tag=$(echo "$tags" | sort -V | tail -n 1)
previous_server_release_tag=$(echo "$tags" | sort -V | tail -n 2 | head -n 1)

MukuFlash03 · 2024-10-08T23:05:33Z

All PRs tracker (#1082 (comment))

Third set of cleanup PRs added for Tasks A - 1, 3

PRs: e-mission-server, join-page, admin-dash, public-dash

This was referenced Aug 12, 2024

Redesign Build Deployment Process (External) e-mission/e-mission-server#961

Merged

Fix for redesigned CI/CD pipeline failure e-mission/em-public-dashboard#144

Merged

shankari mentioned this issue Sep 8, 2024

Unify buid and deploy processes across the various components of OpenPATH #1048

Closed

shankari mentioned this issue Sep 22, 2024

Refactor load_mongodump.sh script e-mission/em-public-dashboard#150

Merged

MukuFlash03 pushed a commit to MukuFlash03/em-public-dashboard that referenced this issue Sep 23, 2024

Task A-6: Switching to step outputs instead of GITHUB_ENV

fb2b096

Refer to details in cleanup issue: Task A-6: e-mission/e-mission-docs#1082 (comment)

MukuFlash03 pushed a commit to MukuFlash03/nrel-openpath-join-page that referenced this issue Sep 23, 2024

Task A-6: Switching to step outputs instead of GITHUB_ENV

991e369

Refer to details in cleanup issue: Task A-6: e-mission/e-mission-docs#1082 (comment)

MukuFlash03 pushed a commit to MukuFlash03/op-admin-dashboard that referenced this issue Sep 23, 2024

Task A-6: Switching to step outputs instead of GITHUB_ENV

652edcb

Refer to details in cleanup issue: Task A-6: e-mission/e-mission-docs#1082 (comment)

MukuFlash03 pushed a commit to MukuFlash03/e-mission-server that referenced this issue Sep 23, 2024

Task A-6: Switching to step outputs instead of GITHUB_ENV

33bd8d5

Refer to details in cleanup issue: Task A-6: e-mission/e-mission-docs#1082 (comment)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

♻️ 💅 Cleanup/polish the code to automatically cascade images from the server -> server dependencies #1082

♻️ 💅 Cleanup/polish the code to automatically cascade images from the server -> server dependencies #1082

shankari commented Aug 12, 2024 •

edited

Loading

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

shankari commented Sep 20, 2024

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

shankari commented Sep 21, 2024 •

edited

Loading

MukuFlash03 commented Sep 21, 2024 •

edited

Loading

MukuFlash03 commented Sep 23, 2024 •

edited

Loading

MukuFlash03 commented Sep 23, 2024 •

edited

Loading

MukuFlash03 commented Sep 30, 2024 •

edited

Loading

MukuFlash03 commented Sep 30, 2024 •

edited

Loading

MukuFlash03 commented Sep 30, 2024

MukuFlash03 commented Sep 30, 2024 •

edited

Loading

MukuFlash03 commented Oct 8, 2024

MukuFlash03 commented Oct 8, 2024 •

edited

Loading

MukuFlash03 commented Oct 8, 2024 •

edited

Loading

MukuFlash03 commented Oct 8, 2024

MukuFlash03 commented Oct 8, 2024

♻️ 💅 Cleanup/polish the code to automatically cascade images from the server -> server dependencies #1082

♻️ 💅 Cleanup/polish the code to automatically cascade images from the server -> server dependencies #1082

Comments

shankari commented Aug 12, 2024 • edited Loading

MukuFlash03 commented Sep 20, 2024 • edited Loading

MukuFlash03 commented Sep 20, 2024 • edited Loading

MukuFlash03 commented Sep 20, 2024 • edited Loading

Task A-7: Certificates location - External or Internal?

shankari commented Sep 20, 2024

MukuFlash03 commented Sep 20, 2024 • edited Loading

Task A-6: Switching from $GITHUB_ENV to step outputs using GITHUB_OUTPUT

MukuFlash03 commented Sep 20, 2024 • edited Loading

Task A-2: Avoid uploading date as Artifacts -> Use .env file instead?

MukuFlash03 commented Sep 20, 2024 • edited Loading

shankari commented Sep 21, 2024 • edited Loading

MukuFlash03 commented Sep 21, 2024 • edited Loading

MukuFlash03 commented Sep 23, 2024 • edited Loading

Task A-8: Stored tag format changed to branch_name-timestamp

MukuFlash03 commented Sep 23, 2024 • edited Loading

MukuFlash03 commented Sep 30, 2024 • edited Loading

Task A-5: Reusable workflows for unifying workflows to reduce duplicated code

MukuFlash03 commented Sep 30, 2024 • edited Loading

MukuFlash03 commented Sep 30, 2024

Task A-4: Run image_build_push only after tests pass successfully

MukuFlash03 commented Sep 30, 2024 • edited Loading

MukuFlash03 commented Oct 8, 2024

Task A-1: Switch to storing images in GHCR

MukuFlash03 commented Oct 8, 2024 • edited Loading

Task A-3: Image build/push on release instead of on every push

MukuFlash03 commented Oct 8, 2024 • edited Loading

MukuFlash03 commented Oct 8, 2024

MukuFlash03 commented Oct 8, 2024

shankari commented Aug 12, 2024 •

edited

Loading

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

MukuFlash03 commented Sep 20, 2024 •

edited

Loading

shankari commented Sep 21, 2024 •

edited

Loading

MukuFlash03 commented Sep 21, 2024 •

edited

Loading

MukuFlash03 commented Sep 23, 2024 •

edited

Loading

MukuFlash03 commented Sep 23, 2024 •

edited

Loading

MukuFlash03 commented Sep 30, 2024 •

edited

Loading

MukuFlash03 commented Sep 30, 2024 •

edited

Loading

MukuFlash03 commented Sep 30, 2024 •

edited

Loading

MukuFlash03 commented Oct 8, 2024 •

edited

Loading

MukuFlash03 commented Oct 8, 2024 •

edited

Loading