search

tkkawa / twitter-manifests

0 stars 0 forks source link

Create GitHub Actions workflow #2

Open tkkawa opened 9 months ago

tkkawa commented 9 months ago

Summary

In the Twitter clone project, our strategy involves leveraging GitHub Actions to seamlessly transfer a compiled image from the application repository to the manifest repository. My goal is to establish a workflow that accomplishes this task while concurrently exploring and implementing the necessary steps.

References

repository

Notes

None

tkkawa commented 8 months ago

Work time

3.5h

Report

I've initiated the development of a GitHub Actions workflow dedicated to building a Docker image. In this phase, I've successfully incorporated the capability to log in to Docker Hub and construct a Docker image. In the future, my plan includes implementing a workflow to create pull requests in the manifest repository, and subsequently, updating the Docker image build process by incorporating Bazel.

tkkawa commented 7 months ago

Work time

2.5h

Report

I enhanced the code by implementing features that allow for passing output to subsequent steps and relocating certain steps to a different directory.

Although it required some time and effort, I successfully implemented relocating steps by consulting the following documents.

In the future, I intend to implement a workflow to create pull requests in the manifest repository.

tkkawa commented 6 months ago

Work time

2h

Report

I spent this week implementing the functionality to edit a manifest file in GitHub Actions. I verified that the GitHub Actions workflow file I developed successfully modified the manifest file.

Moving forward, my plan is to create a workflow for generating pull requests and to delve into exploring the utilization of Bazel.

tkkawa commented 6 months ago

Work time

2h

Report

This week, I dedicated my time to implementing the functionality for creating a pull request to edit a manifest file within GitHub Actions. I opted to utilize the gh command for creating the pull request instead of hub due to encountering the error message hub command not found.

Reference

tkkawa commented 4 months ago

Work time

2.5h

Report

This week, I dedicated my efforts to integrating Bazel into the image building process within GitHub Actions. Initially, I delved into Bazel, gaining a comprehensive understanding of its functionality. Subsequently, I incorporated it into our GitHub Actions workflow. I still think this code resembles Rakuten's code, I plan to refactor a section of the action using Go as part of future enhancements.

Reference

tkkawa commented 4 months ago

Work time

2.5h

Report

This week, I dedicated my time to integrating Dagger with my GitHub Actions workflow, aiming to rewrite actions in Go. I conducted thorough research and completed a simple tutorial. Although I encountered a few errors along the way, I managed to resolve them by changing the Dagger version.

During this exploration, I discovered the versatility of Dagger, realizing its potential for various tasks. Therefore, in the upcoming week, I plan to introduce how to push the image to Docker Hub using Dagger.

References

tkkawa commented 4 months ago

Work time

2.5h

Report

This week, my focus was on implementing the feature to publish a Docker image using Dagger. I delved into the process, integrating it seamlessly into my GitHub Actions workflow. While I successfully published the Docker image from my local environment, encountering an authorization issue prevented it from functioning properly within GitHub Actions. Therefore, in the upcoming week, my plan is to further investigate and resolve this issue.

References