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

[CES-51] Azure DevOps pipelines migrated into GitHub Actions #79

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

mamu0
Copy link

@mamu0 mamu0 commented Oct 3, 2024

List of Changes

The two workflows on Azure DevOps

  • code-review
  • deploy-pipelines

have been recreated in the form of GitHub Actions, but deploy-pipelines is now divided into two actions one for the web app deploy on azure and one for npm publish sdk.

They have been inserted in the .github/workflows folder.

Added pre-commit configuration.

Added infra folder with identity and repository infrastructure, and added branch protection on master (already applied).

Edited .gitignore and CODEOWNER files.

Motivation and Context

Since all the pipelines on Azure DevOps are gradually being decommissioned, it was decided to recreate them on the different repos such as GitHub Actions.

How Has This Been Tested?

Currently they have been tested by inserting

push:
  branches:
    - CES-51-devops-decommissioning

so as to execute them automatically at each test push.
To do the Deploy test for deploy-pipelines action i've used this step only to check if all will be called correctly:

      - name: Deploy
        run: |
          az webapp up \
            --dryrun \
            --resource-group ${{ inputs.resource_group_name }} \
            --name ${{ inputs.app_name }} \

Screenshots (if appropriate):

Types of changes

  • Chore (nothing changes by a user perspective)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

@mamu0 mamu0 requested a review from a team as a code owner October 3, 2024 08:07
Copy link

github-actions bot commented Oct 3, 2024

Jira Pull Request Link

This Pull Request refers to the following Jira issue CES-51

Copy link

sonarqubecloud bot commented Oct 3, 2024

* @pagopa/io-backend-contributors
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we can use @pagopa/io-communication-backend instead cc @lucacavallaro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants