Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modify Github Workflow to trigger on new tags matching pattern #498

Closed
4 tasks
placek opened this issue Mar 18, 2024 · 0 comments · Fixed by #519
Closed
4 tasks

Modify Github Workflow to trigger on new tags matching pattern #498

placek opened this issue Mar 18, 2024 · 0 comments · Fixed by #519

Comments

@placek
Copy link
Contributor

placek commented Mar 18, 2024

Scenario:

As a developer,

I want to adjust our current GitHub deployment

so that it can be triggered by the creation of new tags matching a specific pattern, while still retaining the option to manually trigger the workflow.

Summary:

The task at hand involves modifying an existing GitHub workflow. that deploys branch dev on a development server, to ensure that it is activated automatically when a new tag is created in the repository and matches a defined pattern.

Additionally, the workflow should remain selectable for manual activation by the user as needed. This customization aims to enhance automation and streamline processes when specific criteria are met within the repository.

Acceptance Criteria:

  • Update the GitHub workflow configuration file to include a trigger that activates when a new tag is created matching the specified pattern.
  • Configure the workflow to distinguish between automated triggering on tag creation and manual activation by the user.
  • Test the workflow to ensure that it properly responds to the creation of tags following the defined pattern, triggering the workflow automatically.
  • Verify that manual triggering of the workflow is possible as per the existing functionality.
@placek placek self-assigned this Mar 18, 2024
placek added a commit that referenced this issue Mar 20, 2024
…tag is created (from a specific pattern)

The existing GitHub workflow has been modified to introduce automated
triggering for deployments to the `dev` branch on the development server
upon the creation of a new tag that matches the pattern
`refs/tags/dev-`. The workflow can now distinguish between automated
activation triggered by specific tag creation and manual activation by
the user. By adding a new workflow configuration file,
`.github/workflows/deploy-dev-from-tag.yml`, the automation process for
deployments has been enhanced to react promptly to tag creation events
following the specified pattern.

Changes:
- Created a new GitHub workflow configuration file,
  `deploy-dev-from-tag.yml`, to facilitate automated deployment
  activation based on tag creation matching the predefined pattern
  `refs/tags/dev-`.
- Configured the workflow to differentiate between automated triggering
  upon tag creation and manual activation.
- Updated the workflow to respond effectively to tag creation events
  following the specified pattern, ensuring seamless deployment
  processes and providing the flexibility of manual activation as
  required.
placek added a commit that referenced this issue Mar 20, 2024
…tag is created (from a specific pattern)

The existing GitHub workflow has been modified to introduce automated
triggering for deployments to the `dev` branch on the development server
upon the creation of a new tag that matches the pattern
`refs/tags/dev-`. The workflow can now distinguish between automated
activation triggered by specific tag creation and manual activation by
the user. By adding a new workflow configuration file,
`.github/workflows/deploy-dev-from-tag.yml`, the automation process for
deployments has been enhanced to react promptly to tag creation events
following the specified pattern.

Changes:
- Created a new GitHub workflow configuration file,
  `deploy-dev-from-tag.yml`, to facilitate automated deployment
  activation based on tag creation matching the predefined pattern
  `refs/tags/dev-`.
- Configured the workflow to differentiate between automated triggering
  upon tag creation and manual activation.
- Updated the workflow to respond effectively to tag creation events
  following the specified pattern, ensuring seamless deployment
  processes and providing the flexibility of manual activation as
  required.
placek added a commit that referenced this issue Mar 21, 2024
…tag is created (from a specific pattern)

The existing GitHub workflow has been modified to introduce automated
triggering for deployments to the `dev` branch on the development server
upon the creation of a new tag that matches the pattern
`refs/tags/dev-`. The workflow can now distinguish between automated
activation triggered by specific tag creation and manual activation by
the user. By adding a new workflow configuration file,
`.github/workflows/deploy-dev-from-tag.yml`, the automation process for
deployments has been enhanced to react promptly to tag creation events
following the specified pattern.

Changes:
- Created a new GitHub workflow configuration file,
  `deploy-dev-from-tag.yml`, to facilitate automated deployment
  activation based on tag creation matching the predefined pattern
  `refs/tags/dev-`.
- Configured the workflow to differentiate between automated triggering
  upon tag creation and manual activation.
- Updated the workflow to respond effectively to tag creation events
  following the specified pattern, ensuring seamless deployment
  processes and providing the flexibility of manual activation as
  required.
placek added a commit that referenced this issue Mar 21, 2024
…flow-to-trigger-on-new-tags-matching-pattern

[#498] Modify Github Workflow to trigger on new tags matching pattern
@l-br1 l-br1 added this to Govtool all Apr 2, 2024
@MSzalowski MSzalowski moved this to In staging in Govtool all Apr 8, 2024
@MSzalowski MSzalowski moved this from In staging to Blocked in Govtool all Apr 8, 2024
@bosko-m bosko-m moved this from Blocked to Done in Govtool all Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant