Skip to content
This repository was archived by the owner on Dec 8, 2025. It is now read-only.

Conversation

@olsova
Copy link
Contributor

@olsova olsova commented Jan 31, 2025

add a yaml file to allow using atc as a GH action

test run: https://github.com/olsova/atc-test/actions/runs/19860330864

@afdesk
Copy link
Collaborator

afdesk commented Feb 4, 2025

@olsova is it still a draft?

@olsova olsova marked this pull request as ready for review February 4, 2025 05:21
action.yaml Outdated
fi
echo "Config file found: ${{ inputs.type }}"

- name: Build and Run Docker Container
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we don’t need the Docker container anymore.

Previously (before the GitHub Action), we used a GitHub App for atc.
It was supposed to always run and listen for webhooks. When we received a push event, we checked the config file, compared versions, etc.

But now we don’t need this.
Users will use the push trigger, so we just need to compare versions and push tags (if needed).

So what we need to build the binary + run the built binary with CI_MODE env

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does the regular mod (with webhooks) work for this dockerfile?

Copy link
Collaborator

@DmitriyLewen DmitriyLewen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you create test repo with lock file (e.g. package.json or pom.xml) and test this action?

action.yaml Outdated
shell: bash
run: |
go build -o atc ./
chmod +x atc
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

atc is already executable, no?

action.yaml Outdated
- name: Build Automated Tag Creator
shell: bash
run: |
go build -o atc ./
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@olsova olsova force-pushed the add-action branch 3 times, most recently from 5128bf7 to 95ac33e Compare December 2, 2025 12:35
@olsova olsova force-pushed the add-action branch 3 times, most recently from 3635b25 to 22200b0 Compare December 2, 2025 12:58
@olsova
Copy link
Contributor Author

olsova commented Dec 3, 2025

@DmitriyLewen I don't have merge access. Could you merge this PR?

@DmitriyLewen DmitriyLewen merged commit 8565c69 into smartforce-io:master Dec 3, 2025
1 check passed
@olsova olsova deleted the add-action branch December 3, 2025 12:26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants